Hello Tim, have you upgraded your older 4801 box to version 5.1 with the geode image or also with the Bering-uClibc_5.1_x86_64_syslinux_vga.tar.gz ? Afaik the 4801 does not support 64bit so you it seems you have used the Bering-uClibc_5.1_geode_syslinux_serial.tar.gz image for successfully upgrading it. Due to the fact that there exists no Bering-uClibc_5.1_x86_64_syslinux_SERIAL.tar.gz image for the new generation of SBC's this VGA-image is intended for 64bit computers with vga output which has neither your soerkis nor my PC Engines APU board.
I have forgotten to say, that I have copied the etc.lrp package from the geode image too, cause I was to lazy to modify inittab from Bering-uClibc_5.1_x86_64_syslinux_vga.tar.gz (and maybe other files). ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 For me it worked. Juergen Am Di. 16. Sep. 2014 20:22 CEST, Timothy Wegner <[email protected]> schrieb: > Thanks kp and Juergen for responding. > > kp wrote: > > >Have you tried to add > >usb_wait=3 > >the APPEND line in syslinux.cfg? > > Yes, but no luck. I should add that I *did* successfully upgrade an older and > much slower Soekris net4801 box to 5.1 with no problems. So I am not > surprised that usb wait=3 didn't help on the much faster net6501. The reason > I retired the net4801 as my router is a switched from slow DSL to 100mbs > comcast, and the 4801 could not keep up. I am using the 4801 now as a tiny > public web server in a DMZ. > > Responding to Jurgen: > > You surmised correctly that I started with > Bering-uClibc_5.1_x86_64_syslinux_vga.tar.gz and modified syslinux.cfg for > serial. I tried adding some of the same append options that you did with no > luck. By current syslinux.cfg is: > > SERIAL 0 19200 > DISPLAY syslinux.dpy > > TIMEOUT 0 > APPEND reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 > intel_idle.max_cstate=0 processor.max_cstate=1 > DEFAULT /syslinux/linux initrd=/initrd.lrp,/initmod.lrp rw root=/dev/ram0 > LEAFCFG=/dev/sda1:vfat > > > One question though. Unlike Jurgen, I started with my configdb.lrp from my > successful Leaf 5.0.4 installation. Should I have started with a stock > configdb.lrp? I took a similar approach of using my previous configdb.lrp > with my net4801 upgrade and had no problems. > > Any other suggestions appreciated. I wonder if I am missing a module that I > was somehow picking up with 5.0.4, and if I should manually inspect the > modules I am using with 5.0.4 and see if I can add them to 5.1. > > Thanks much. > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce. > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > ------------------------------------------------------------------------ > leaf-user mailing list: [email protected] > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
