2.6.31 rebuild : give me your .configs

[Geoff]

I second the motion for iptables and nfs. I would add a request for more crypto modules, including aes-xts-plain which is the default for cryptsetup. Any modules that can take advantage of the crypto/digest/hashing hardware would be nice. A HID driver so that I can interact with my UPS (battery backup) over USB would also be nice.

[WarheadsSE]

.configs And.. I haven't found a driver for the in-built hash accelerator.

[braklisz]

[...] We're still working on the 3.1+ (now 3.1.10, we're just having to completely rewrite the platform support)

With all due respect WarheadsSE, is that because some new issues have popped up in 3.1.10 or do you refer to the general 3.X+ kernel work-in-progress?

Back on topic, if someone would be kind enough to get WSE his build .configs, would this awesome person also try enabling XTS and/or LRW support in the kernel (these will work as modules)? My TrueCrypt 7.1 compilation complains without them (btw, I can upload the binary if anyone's interested..):

Error: device-mapper: reload ioctl on truecrypt1 failed: Invalid argument
Command failed

Oh oh oh and IPTABLES

God bless you, WarheadsSE!

Code: Select all

Device Drivers --->
  [*] Multiple devices driver support (RAID and LVM) --->
    <*> Device mapper support
    <*>   Crypt target support
  [*] Block Devices --->
    <*> Loopback device support
File systems --->
  <*> FUSE (Filesystem in Userspace) support
[*] Cryptographic API --->
  <*> RIPEMD-160 digest algorithm
  <*> SHA384 and SHA512 digest algorithms
  <*> Whirlpool digest algorithms
  <*> LRW support (EXPERIMENTAL)
  <*> XTS support (EXPERIMENTAL)
  <*> AES cipher algorithms
  <*> Serpent cipher algorithm
  <*> Twofish cipher algorithm


[WarheadsSE]

It's the 3.1+ in general. There are problems with it outright with regards to transiting PLX's "patches" to 3.1 from 2.6. Also, there issues with high memory pressure when running both cores are full.

[EricBetts]

I have a RTL8187 based wifi dongle that I'd like to use with my PogoPlug. I'm not sure if its common enough, but supporting loading it as a module would be nice.

[digitlman]

I'm trying to use my pogoplug "classic" (B02) as a webcam MJPEG streamer (using mjpg-streamer) and I get the following error from mjpg-streamer:

Code: Select all

MJPG Streamer Version.: 2.0
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 640 x 480
 i: Frames Per Second.: 5
 i: Format............: MJPEG
ERROR opening V4L interface: No such file or directory
 Init v4L2 failed !! exit fatal
 i: init_VideoIn failed

I'm new to ALARM, but found the uvcvideo kernel module for the v3.x kernel installed (/lib/modules/3.1.10-3-ARCH/kernel/drivers/media/video/uvc/uvcvideo.ko.gz), but not for the v2.x kernel (alarm 2.6.31.6_SMP_820) which is what I assume everyone else is running as well. So it appears I need the uvcvideo module as well as any dependencies (V4L2?) and any kernel modules required for USB audio (e.g. from a webcam) would be desireable too (though I don't think I can stream the audio with mjpg-streamer, I'll come up with something).

Thanks! With webcam support on the pogolpug, I'm going to be able to make a very cool, inexpensive but high-quality, security camera extension for my home security system!

Thanks in advance,

-Rob

[WarheadsSE]

V4L2 is only in newer kernels, I think. Psst, I have no idea what these dependencies you speak of are.

[digitlman]

V4L2 is only in newer kernels, I think. Psst, I have no idea what these dependencies you speak of are.

According to https://en.wikipedia.org/wiki/Video4Linux, V4L2 started appearing in 2.5.x kernels and according to Wikipedia, the UVC (https://en.wikipedia.org/wiki/USB_video_device_class) driver started appearing in kernel source distrubutions as of 2.6.26.

Regarding dependencies: if you can plug in a UVC-compliant webcam into the pogoplug and get a /dev/video0 device, then I think all the dependencies are met for obtaining *video* from a USB webcam (UVC) - and that's my immediate goal. The dependecies I was referring to are the kernel symbols required by uvcvideo.ko or any other driver modules (e.g. v4l2*.ko) required by uvcvideo. But I'm just speculating, really, I haven't built my own kernel to support UVC and I'm hoping, with your efforts, that I won't have to.

I'm not sure what the requirements for obtaining *audio* from a UVC device are - that was more of a stretch goal for me.

[braklisz]

so since it's quiet on the .config front...

http://www.2shared.com/file/GCdey-3L/configtruecryptandnetfilter.html

Changes from kwave's .config:

1. TrueCrypt 7 related

Device Drivers --->
[*] Block Devices --->
<M> Cryptoloop Support

-*- Cryptographic API --->
{M} GF(2^128) multiplication functions (EXPERIMENTAL)
<M> LRW support (EXPERIMENTAL)
<M> XTS support (EXPERIMENTAL)
<M> RIPEMD-160 digest algorithm
<M> SHA384 and SHA512 digest algorithms
<M> Serpent cipher algorithm
<M> Twofish cipher algorithm

(probably an overkill because PROs don't have that but.. )

[*] Hardware crypto devices --->
<M> Driver HIFN 795x crypto accelerator chips

2. ..and all the netfilter related stuff I could find (so we should be good for NAT and what-not).

BTW, @digitlman - kwave's changes should do what you want to have, guess you'd just have to check if those modules are enough for you.

Could we try the modules out now, WarheadsSE, plz plz plz?

[WarheadsSE]

Because those using a NAND install will need to flash this, I'm going to have to do this as few times as possible