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.

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.

Thanks for providing a benefit to the community.

I tried the UPDATE-KERNEL.sh script on your site to upgrade my Guruplug Server Plus to 3.9.0
and my /boot is on an eSATA drive


When I go to that folder with my browser, I don't see a kirkwood-sheevaplug-3.9.0-uImage
but I do see the following:


I need to modify the script to grab this file instead of a uImage?

http://www.xilka.com/kernel/3/3.9/3.9.0/release/3/kirkwood-3.9.0-zImage



What about these?

http://www.xilka.com/kernel/3/3.9/3.9.0/release/3/kirkwood-sheevaplug-3.9.0.dtb

http://www.xilka.com/kernel/3/3.9/3.9.0/release/3/kirkwood-sheevaplug-esata-3.9.0.dtb

http://www.xilka.com/kernel/3/3.9/3.9.0/release/3/kirkwood-guruplug-server-plus-3.9.0.dtb

Which of these is correct one for my device (I want to use it as an AP as well) ?

Console access (via JTAG adapter) or are you booting from an SD? If so, mount your SD in another system and fix your config?

The Dreamplug hung after about 6 hours of moderate use. Seems it's not quite as stable as I would hope. I'll continue to fiddle with this.

Right now, I'm running an AP on mwifiex using the tip of the wireless-testing git repo (version reads as  3.9.0-rc8-wl), the latest firmware from the link nago gave, and WPA2. Note that if you try to use WPA instead of WPA2, the client handshake seems to fail.

I've had it running for a half hour or so of light use - seems stable so far, but time will tell.

Hi,

in my configuration i want to attach an external usb drive to the dreamplug.

If the drive is attached at boot time it is not recognized later on by the linux kernel.
But if i unplug and replug the device, i can use it normally.
if i perform usb start the first time in uboot the harddisk is found
after an usb reset the drive is not found anymore as you can see in my output.
I think uboot messes something up in device initialization.

any idea?

<sup>U-Boot 2011.06-02334-g8f495d9-dirty (May 31 2011 - 02:06:26)
Marvell-DreamPlug

SoC:   Kirkwood 88F6281_A0
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM:  512 MiB
SF: Detected MX25L1606 with page size 256, total 1 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1116 Initialized on egiga0
88E1116 Initialized on egiga1
Hit any key to stop autoboot:  0
Marvell>> usb start
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 5 USB Device(s) found
       scanning bus for storage devices... 3 Storage Device(s) found
Marvell>> usb storage
  Device 0: Vendor: Generic  Rev: 9910 Prod: STORAGE DEVICE
            Type: Removable Hard Disk
            Capacity: 3920.0 MB = 3.8 GB (8028160 x 512)
  Device 1: Vendor: Generic  Rev: 9910 Prod: STORAGE DEVICE
            Type: Removable Hard Disk
            Capacity: 15312.0 MB = 14.9 GB (31358976 x 512)
  Device 2: Vendor: SAMSUNG  Rev: 1AQ1 Prod: HD204UI
            Type: Hard Disk
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
Marvell>> usb reset
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 5 USB Device(s) found
       scanning bus for storage devices... 2 Storage Device(s) found
Marvell>> usb storage
  Device 0: Vendor: Generic  Rev: 9910 Prod: STORAGE DEVICE 
            Type: Removable Hard Disk
            Capacity: 3920.0 MB = 3.8 GB (8028160 x 512)
  Device 1: Vendor: Generic  Rev: 9910 Prod: STORAGE DEVICE 
            Type: Removable Hard Disk
            Capacity: 15312.0 MB = 14.9 GB (31358976 x 512)</sup>

Nope, Linux only 

I was having issues with Mediatomb and my dreamplug, so I flushed my IPTables.  Now I can no longer access my dreamplug.  It does register with my router, but I cannot ssh or telnet in. 

Any ideas?  By default, can I boot from a USB stick?

Thanks
Harry

I may be wrong, but with a 2.6.30 kernel, I think the size limit is 2.2TB. Is this possibly a cause?