I'm sure you may have noticed that i haven't been frequenting the forum as often. Even though I'm not here too often that doesn't mean that I'm not updating kernels. So I would recommend checking http://www.xilka.com/sheeva/ for the latest version when you decide that you want to update. Just look in http://www.xilka.com/sheeva/3/3.6 (obviously 3.6 will increment as newer versions are released) for the latest supported version and then run the README-*sh script to pull down that version.

I've been busy with CuBox related items, kernel's of course and xbmc on CuBox. I've also upgraded my main server from an AMD X6@3.4 to an FX-8350@4.7. Let me tell you...the FX-8350@4.7 really flies for the type of work (X264 encoding and software compiles) that I do on it.

Hi cbxbiker! (I've always wanted a CBX, but never had the opportunity!)

I tried your 3.6.6 kernel on a GuruPlug that I wanted to use in WiFi-client mode. My first reboot went well, but after I disconnected the Ethernet to run WiFi only, I keep getting kernel oopses when I try to bring up the interface:

I tried Sheeva-3.6.8 from your website...same result. There's a brief pause (1/2 second or so) after "ifconfig mlan0" and before the Oops. The blue light comes on, and after the oops, it goes into a rapid blink. Also, the system never completes the reset after the oops -- I have to press the reset button.

I'm a bit lost now. I'm attempting to get wifi working (station preferably, but I'll take client mode) on my guruplug server plus. Up until 3.5.3 (using cbxbiker61 kernels), this all worked without problems. Seems that as of 3.6, the LIBERTAS_UAP driver is just gone. Alas, after unblacklisting the libertas_sdio driver, even that fails to load the firmware (yes, I do have it in both /lib/firmware/mrvl and lib/firmware/libertas) on 3.6.10.

So, does the mwifiex driver work on the guruplug server plus, or is there some other way to get the wifi working again ?

Or should I just forget about my guruplug and concentrate on my Raspi ?

I just downloaded your 3.8.4 kernel, which behaves much better on the guruplug server plus with the SD8686 wireless. I can now load the libertas_sdio module without errors. Alas, this gives me client mode only.

Any chance you can enable the LIBERTAS_THINFIRM module in the next builds ? I think that with this module enable, we might be able (with the appropriate thin firmware, and hostapd) to use the SD8686 equipped machines as APs (how well, I cannot say, but it seems to work for the XO project)...

I just downloaded your 3.8.4 kernel, which behaves much better on the guruplug server plus with the SD8686 wireless. I can now load the libertas_sdio module without errors. Alas, this gives me client mode only.

Any chance you can enable the LIBERTAS_THINFIRM module in the next builds ? I think that with this module enable, we might be able (with the appropriate thin firmware, and hostapd) to use the SD8686 equipped machines as APs (how well, I cannot say, but it seems to work for the XO project)...

Thanks.

I've just made a 3.8.4 release 2 with LIBERTAS_THINFIRM module. See if that works for you.

OK, well I've been converting to devicetree based kernels for arm. This will allow me to properly support quite a few variations of the kirkwood and dove based devices, others as well (DeviceTree is awesome from a distribution standpoint).

UPDATE-KERNEL.sh will work with the kernel's starting at 3.9.0, for anything prior, continue to use the older scripts.

The UPDATE-KERNEL.sh is a work-in-progress, right now I know it works properly on SheevaPlug's and CuBox's. Theoretically it will work for the other variations as well, feedback would be appreciated.

UPDATE-KERNEL.sh attempts to identify the device based on entries in the /proc filesystem. In those cases where it id's the device correctly, all that is necessary is "sudo ./UPDATE-KERNEL.sh 3.9.0", for devices that aren't id'd correctly "sudo ./UPDATE-KERNEL.sh 3.9.0 device-type" should work.

The earliest version of UPDATE-KERNEL.sh, wasn't optimal (from a distribution standpoint), and I rewrote it to download the zImage and a corresponding .dtb file, that will be the version that you want. You can grab it from http://www.xilka.com/sheeva/tmp/UPDATE-KERNEL.sh (the version in /sheeva should be OK after the web server caches have a chance to update). Keep in mind that I haven't got auto detection setup properly for devices other than SheevaPlug, SheevaPlug-eSATA and CuBox. After you have installed a device-tree kernel, from that point on the auto-detection should work reliably since I can use entries in /proc/device-tree.