I had analyzed the 3.3.2 kernel configurations from Davygravy. There was a difference between the rescue kernel and the full blown kernel. I think that the rescue kernel supports the ppv4 arcNumber but the full blown kernel does not support it. That is the reason why the NSA320 rootfs can't be used with ppv4 arcNumber. If somebody needs a 3.3.2 kernel from Davygravy with the adaption to suppby shv - Debian
I tried your kernel 2.6.31.14. In comparision to WarheadsSEs kernel 2.6.31.6 your kernel supports more FTDI USB2SERIAL interfaces. The wireless module rt3390sta doesn't work with the integrated wireless module in Pogoplug Pro. I want to compile the driver of the wireless moduel as I did for WarheadsSEs kernel. Where can I find the sources and patches of your 2.6.31.14 kernel for OX820?by shv - uBoot
hyena Wrote: ------------------------------------------------------- > did the apt-get update/install after and it seems > to have done the job fingers crossed :-) deleted > all the 3.2.0-4 files in /boot & lib/modules as a > test and it seemed to boot ok as well :-) Instead of just deleting the old kernel files you should deinstall them. First find out the name of theby shv - Debian
This looks good. With iwconfig you can see which network interfaces are available.by shv - Debian
@chessplayer: What is shown with lsmod command? If the driver is registered it should be in the list.by shv - Debian
And then generate new uImage and uInitrd: mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.5.0-iconnect -d /boot/vmlinuz-3.5.0-hyena-iconnect /boot/uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.5.0-iconnect -d /boot/initrd.img-3.5.0-hyena-iconnect /boot/uInitrdby shv - Debian
The kernel version is 2.6.31.6. So it is the same kernel version as you have with ALARM. You can boot even if you have more than the boot stick connected to the pogoplug. In this case the boot stick must be plugged in the USB connector next to the Enternet connector. Can you please try to download the file again with Firefox or some other download manager? I have no account at Mediafire.by shv - uBoot
@bodhi: I thought that in any case the CPU tries to boot from SATA if a drive is connected even it is not prepared for NAND-bypass. In this case booting from NAND isn't possible if SATA drive is connected. Maybe I am wrong. Can you please give me some more details if booting from NAND with just the rootfs on SATA drive is possible?by shv - uBoot
Possibly something like this? Outside Inside The Pogoplug Pro starts from SATA first without any usage of Flash content (see Link). The uImage which is provided in the tarball must be replaced with a newer one.by shv - uBoot
I think he just needs the kernel headers to compile the sources which are provided from Mediatek/Ralink.by shv - Debian
If you see that the driver is loaded with lsmod you can try the commands I posted in another forum. http://archlinuxarm.org/forum/viewtopic.php?f=29&t=2031&start=100#p25865by shv - Debian
Installing Linaro ARM Cross Toolchain on Ubuntu: apt-get install gcc-arm-linux-gnueabi apt-get install kernel-package You can use the following command to cross compile the kernel and get the necessary .deb file: DEB_HOST_ARCH=armel fakeroot make-kpkg --arch arm --cross-compile arm-linux-gnueabi- --append-to-version=-hyena --revision=1.0 --initrd -j 5 kernel_image I am not sure if thby shv - Debian
@bodhi, Yes I am thinking about running it on Pogoplug V4. I will try to use the ALARM uboot to boot the kernel from one USB drive and to load the rootfs from another drive. If the kernel of the rescue system is to restricted I might replace it with a fully blown kernel if there is enough space. I also compiled davys 3.3.2 kernel with support for the pogoplug devices. How to prevent that a NANDby shv - Debian
Yes, you shoud remove the file 70-persistent-net.rules to prevent problems due to wrong MAC address of the ra0 interface. rm /etc/udev/rules.d/70-persistent-net.rulesby shv - uBoot
Hello bodhi, It is working with a different cross tool chain now. Thank you for providing all necessary configurations an patches. I would like to flash such kernel to the NAND of my Pogoplug E02 and to use sd card or USB3.0 stick, USB2.0 stick or SATA as rootfs. How could I do this? Would the rescue kernel already be able to use the rootfs with USB3.0 or SD card? I think chessplayer has alreaby shv - Debian
Hello bodhi, Yes, I saw this error in serial console during mounting rootfs. I will try to use a clean backup rootfs and the other recommendations next time. If this will not work my next step will be to compile it natively on the device. shvby shv - Debian
Hello bodhi, Your kernel is working fine on Pogoplug E02 and Pogoplug Series 4, thanks. I was not successful with building a working kernel. I get a .deb file but the kernel doesn't get access to /dev/root. How can I setup a working cross toolchain on debian or ubuntu? shvby shv - Debian
Both 3.3.2 kernel configuration files are available from davy's post. You can find a link to the kirkwood-dg config file in the message (config-3.3.2-kirkwood-dg-wide) and the kirkwide config file (linux-3.3.2-wider-config-Buildroot-module-set) in the link to davygravys dropbox (Kirkwood Downloads). The patch file is also available in the dropbox (linux-3.3.2-wider-patch). If I compare bothby shv - Debian
Both 3.3.2 kernel configuration files are available from http://forum.doozan.com/read.php?2,7676,7676#msg-7676. You can find a link to the kirkwood-dg config file in the message (config-3.3.2-kirkwood-dg-wide) and the kirkwide config file (linux-3.3.2-wider-config-Buildroot-module-set) in the link to davygravys dropbox (Kirkwood Downloads). The patch file is also available in the dropbox (linux-3by shv - Debian
Hello bodhi, thank you for uploading the patch file. Can you also provide the kernel configuration file? Thank you in advance. -shvby shv - Debian
@chessplayer: Can you please check which machid is set? You can find the machids which are supported in the following post: Supported machids. This list does not contain dd6 (3542) machid. With the kernel of the rescue system and arcNumber/machid set to 3542/dd6 the LED is controled. The color is green if it is switched on. The same behaviour I have with bodhys kernel 3.2.28. With 3.3.2 kernelby shv - Debian
You could try this out: 1. Shut down the device, remove any drives you have attached 2. On a FAT32 USB drive, create a folder named "revert" 3. Plug this drive into the top USB port, and power on the plug 4. The LED will stay blinking green for a moment, then turn red. This signals that the stock firmware is operating. You should be able to find the device on my.pogoplby shv - uBoot
I tried the kernel on Pogoplug E02 with arcNumber set to 3542 which was done by the script dockstar.debian-squeeze.sh or kirkwood.debian-wheezy.sh. It seams that this arcNumber ist not supported with this kernel and the boot procedure is stopped. It only works if I set the arcNumber to 2097. But I am wondering that the rescue system contains a 3.3.2 kernel with support for the arcNumber 3542.by shv - Debian
The 3.3.2 kernel which is linked in the first post doesn't contain support for Pogoplug devices (arcNumber 3542). But the rescue system contains a 3.3.2 kernel with support for pogoplug devices. Is a 3.3.2 kernel with support for Pogoplug devices (arcNumbers 3542 and 3960) available for download?by shv - Debian
Thank you bodhi for sharing of this kernel. Can you also share the source tree? I might need it if I must compile drivers for some external hardware devices.by shv - Debian
I will try your kernel package possibly next weekend.by shv - uBoot
I tried yesterday to boot with my E02. This didn't work because the series 4 arcNumber=3960 isn't supported. How can I get kernel an modules with Pogo V4 patch? I could also compile them my own.by shv - uBoot
Yes, I have a Pogoplug E02.by shv - uBoot
The problem seams to be that F78 is not supported. Therefore the device can't boot into Debian.by shv - uBoot