I hope that you are aware that both patches are from mid of March 2012 if you look on the file dates within the patch folder. The kernel-2.6.31.14-pogoplug3-2012-03-19.tar.bz2 package is based on cloudengines patches and kernel-2.6.31.14-pogoplug3-s-2012-05-20.tar.bz2 is based on Silverstone patches. The last one is not deeply tested due to telzeys posts in the referenced thread. The 3rd variantby shv - uBoot
Telzey provided an untested different patchset based on silverstorne source code in the following thread: http://archlinuxarm.org/forum/viewtopic.php?f=55&t=2594. Some information in this thread might be interesting. He stopped working with OX820 in May 2012. Medion devices are still based on a 2.6.31.14 kernel. The latest source code is from Dec. 2012. (Download: http://www.medion.com/de/seby shv - uBoot
kuleszdl Wrote: ------------------------------------------------------- > @shv: For me it works without the > /dev/null > > You probably inserted the line after "exit 0" in > rc.local, didn't you? No it is before "exit 0". I get these FAIL messages in the seriell console. Did you check this also with the seriell console? Just tried the dist-upgrby shv - uBoot
The rc.local FAIL was caused by the return value of proled. The following replacement solved this: /sbin/proled green > /dev/nul Now it is still necessary to find the reason for the other FAIL message.by shv - uBoot
I built the userland from scratch via doozan skript with Pogoplug E02 which means dbootstrap. Afterwards I used the procedure in the first message of this thread to make it ready for Pogoplug Pro and added the libaccept4.so and preload configuration. I get FAIL messages 2 time at the end of the system startup: [ ok ] Cleaning up temporary files.... [....] startpar: service(s) returned failby shv - uBoot
@kuleszdl: I got Wheezy working. I had some problem with the ethernet but this was caused by a wrong MAC address.by shv - uBoot
It belongs to the availability of OXNAS patches for this kernel. You can get them from there: http://archlinuxarm.org/forum/viewtopic.php?f=29&t=2472&start=10#p15007by shv - uBoot
This sounds that you use the normal 2.6.31.6 Kernel of WarheadsSE. I am providing a bit newer kernel which solves some drawbacks of WarheadsSE Kernel which I had with FTDI Interfaces, PC/SC Cardreaders and USB Sound Cards). This kernel is based on telzeys patches (ALARM Forum) and configured similar to WarheadsSEs Kernel expect PPP and packet readio which I had to disable. http://www.pogoplug.by shv - uBoot
Possibly you could try to delete mtdblock2 and create a new one. I don't know why mtdblock2 already exist in your case. You could use the Debian installation skript again to create a new Debian rootfs on a USB stick. Did you change your flash assignment in the boot environment?by shv - uBoot
Look there: http://forum.doozan.com/read.php?3,12506by shv - Debian
@bodhi, I removed the other kernel (2.6.32) which was still installed beside 2.6.31.6 but kept linux-base. ii linux-base 2.6.32-46 Linux image base package ii linux-image-2.6-kirkwood 2.6.32+29 Linux 2.6 for Marvell Kirkwood (meta-package) ii linux-image-2.6.32-5-kirkwood 2.6.32-46by shv - uBoot
bodhi Wrote: ------------------------------------------------------- > kuleszdl Wrote: > -------------------------------------------------- > ----- > > Hi folks, > > > > I've set up a complete guide on how to create a > > Debian Squeeze rootfs from scratch via > > debootstrap, merging information from this > thread > > and variousby shv - uBoot
The link is on page 5: http://forum.doozan.com/read.php?3,6336,10999#msg-10999.by shv - uBoot
Is the name of the partition "rootfs"?by shv - uBoot
See: http://blog.smartlogicsolutions.com/2009/06/04/mount-options-to-improve-ext4-file-system-performance/by shv - uBoot
dinjo Wrote: ------------------------------------------------------- > Can i use ext4 has bootable drive with debian ? This is not possible with the ALARM kernel 2.6.31.6 in the flash because ext4 is not included but loaded as a module. To use ext4 rootfs you must compile and flash a different kernel.by shv - uBoot
dinjo Wrote: ------------------------------------------------------- > Thanks shiv the file should go to > /etc/udev/rules.d right ? Also i see there is no > mention of ext3 ? The folder is right. It works for ext3 without to mention is seperately.by shv - uBoot
Please find attached an udev automount script.by shv - uBoot
I could provide an udev automount skript next days.by shv - uBoot
Cloning to HDD: Put the Debian boot stick into Linux device and use tar to save and restore its content. Yes, you can return to original FW: http://forum.doozan.com/read.php?3,12506by shv - Debian
I want to revert to the factory uboot of Goflex Net. How can can I read the factory uboot back from flash rootfs partition and write it to flash? Is it necessary to change the uboot environment variables which were changed during installation of new uboot? I don't have any mtdblock devices in /dev. I found out how to do that after Debian was booted from a USB Stick: mknod /dev/mtdblockby shv - uBoot
Because also the 3.8.4 kernel doesn't work flawlessly I am not sure if it is a FW or HW problem. Before I try other things I will try an old Squeeze with an old 2.x.y kernel. Until the device don't work properly I will not change the uboot. There are no problems with SATA but a lot with USB if I use a USB hub.by shv - Debian
@bodhi: Thanks for your recommendations. But if I search the INET for the "EHCI timed out" messages I find some occurrences where other plug computers were affected. Such problems were resolved by uboot changes. The device doesn't boot due to the same problem if I try to boot from a USB stick which is connected with 3 USB harddisks to a USB hub and don't use a SATA boot disk.by shv - Debian
Booting from SATA works well as long as no additional USB harddrive is connected. With additional USB harddrive the Goflex Net does not boot after using the reboot command from first SATA drive anymore even the USB harddrive does not contain a partition labeled with rootfs. Power off/on restart most often works. How to improve the uboot settings that even in this case booting from SATA is possiblby shv - Debian
Could the problem be caused by the following entry in resolv.conf: search fritz.box? But I think this entry should also be overwritten by the dhcpclient.by shv - uBoot
Did you try one of my rootfs from the previous post above yours?by shv - Debian
You can download a rootfs (Debian/Wheezy) with 3.3.2 kernel which is based on Davys kernel with the extension to additionally support Pogoplug E02, Mobile, Series4 arcNumber/machid from the following post: Link.by shv - Debian
Testing of kernels is not a problem because I am using a SATA drive connected to the SATA port. So I don't need to flash any testing kernels.by shv - uBoot
Thanks. In the meantime I was able to compile the WLAN driver. My feedback for your kernel 2.6.31.14 is that USB devices are working well. I tested a FTDI interface and a PCSC cardreader which were not working before. A little badnews is that the troughput for reading and writing of SATA and USB harddrives is 10-20% worse than with WarheadsSEs 2.6.31.6 kernel. Hints to improve the USB and SATAby shv - uBoot
Debian rootfs with kernel 3.3.2 with support for Pogoplug arcNumber/machid: Squeeze-rootfs Wheezy-rootfs The following kernel package is just for completeness because it is alrady contained in the provided rootfs. linux-image-3.3.2-kirkwood-shv_1.0_armel.deb shvby shv - Debian