Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
20.09.2014 22:16, Erich Titl пишет: Hi Andrew at 20.09.2014 20:13, Andrew wrote: 20.09.2014 14:07, Erich Titl пишет: ... Right. Modules aren't userland. So modules are splitted from userland initrd. I would probably argue that initrd isn't userland at all in my mindmap. For me initrd is a way to allow a system to be booted and IMHO every trace of it should disappear in the later boot process. But again, this is just an opinion. Initrd - is userland stuff. There is no difference how we obtain a rootfs at boot - by mounting partition or by using any kind of ramdisk (initrd/initramfs). In any case it contains just a minimal piece of base system. 2) for embedded platforms where there is a single userland for arch, and multiple kernels (even with different versions - if there is a proprietary patch w/o ports to other versions, and even w/o boot-time modules for some platforms - if there is a fixed configuration of boot-time modules, they may be linked into kernel as static). If we had that there would be no need for initmod. Right. For one platform. Another platform with same arch (for ex., ARMv7) can be booted from SD card/USB - and will have modules (because USB drives aren't necessary). So it'll be good to have universal initrd, and initmods for different platforms (if they are needed). Also it helps to easily update userspace w/o kernel or kernel w/o userspace (they are almost independent now). As they should be but I iterate here, modules are not userland ( I have been made aware of this on this proper list ;-) If loader doesn't support multiple initrd, 2 pieces can be easily concatenated into one w/o repacking. I understand the idea of separating the kernel from userland, but modules are alway kernel dependent. Right, and they are also separated from userland. Now you can just place kernel with initmod and moddb.lrp/modules.tgz into your distro - and voila, you have old stable userland with bleeding-edge kernel. Even building multiple different self contained initrd for single kernels are no problem as we have a initrd build procedure which may vebuild multiple different architecture initrd files. As you say, as they are cpio archives they can easily be put together, so why not just do it. cpio is useful for x86; for embedded with on-board flash - we even may use squashfs with tmpfs on top (for saving valuable RAM). I think this will be done in 5.2 Then it might be more difficult to fix it if needed. I would just be glad if leaf was not such a moving target, so I could get some development done. . There winll be no big difference - just additional option to initrd format for platform, and handling squashfs root if it's present. Also, almost all boot loaders suport multiple ramdisks. So I don't think that it's actual trouble. M... I have not seen this for grub, but then I am not using grub2 need to investigate. cheers Erich Grub (at least latest versions) supports multiple initrds: http://forum.slitaz.org/topic/grub4dos-usbflash-slitaz-30-is-ok-slitaz-40-dont-boot-rootfsgz-x4 Grub2 - now also supports: http://savannah.gnu.org/bugs/?35238 -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
21.09.2014 21:56, Andrew пишет: 20.09.2014 22:16, Erich Titl пишет: Hi Andrew at 20.09.2014 20:13, Andrew wrote: 20.09.2014 14:07, Erich Titl пишет: Also, almost all boot loaders suport multiple ramdisks. So I don't think that it's actual trouble. M... I have not seen this for grub, but then I am not using grub2 need to investigate. cheers Erich Grub (at least latest versions) supports multiple initrds: http://forum.slitaz.org/topic/grub4dos-usbflash-slitaz-30-is-ok-slitaz-40-dont-boot-rootfsgz-x4 Grub2 - now also supports: http://savannah.gnu.org/bugs/?35238 Sorry, you're right - grrub4dos supports multiple initrds, grub - no. grub2 - should support. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hi Andrew at 19.09.2014 20:39, Andrew wrote: 19.09.2014 15:04, Erich Titl пишет: Hi at 19.09.2014 10:35, kp kirchdoerfer wrote: Am Donnerstag, 18. September 2014, 18:59:40 schrieb Timothy Wegner: David wrote: ... Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It is needed with the newer kernel in 5.1. You may add it grom the modules tarball to initmod.lrp. See http://bering-uclibc.zetam.org/wiki/Bering-uClibc_5.x_-_User_Guide_-_Advanced_Topics_-_Modifying_initrd.lrp how to modify initmod.lrp (It's written for initrd, but it's also valid for initmod). For what it's worth, I never understood the rationale behind splitting initrd, except for a few cycles on the server building it. It makes life miserable for anyone using a boot loader which does not support multiple initrd files. It probably needs more space for initrd storage and makes debugging more difficult. I vote to go back to single initrd files. cheers Erich It's for 1) completely separating userland from kernel - that will allow us to maintaindifferent kernel branches in single release and I don't understand this statement, modules are not userland. 2) for embedded platforms where there is a single userland for arch, and multiple kernels (even with different versions - if there is a proprietary patch w/o ports to other versions, and even w/o boot-time modules for some platforms - if there is a fixed configuration of boot-time modules, they may be linked into kernel as static). If we had that there would be no need for initmod. Also it helps to easily update userspace w/o kernel or kernel w/o userspace (they are almost independent now). As they should be but I iterate here, modules are not userland ( I have been made aware of this on this proper list ;-) If loader doesn't support multiple initrd, 2 pieces can be easily concatenated into one w/o repacking. I understand the idea of separating the kernel from userland, but modules are alway kernel dependent. Even building multiple different self contained initrd for single kernels are no problem as we have a initrd build procedure which may very well build multiple different architecture initrd files. As you say, as they are cpio archives they can easily be put together, so why not just do it. The missing module(s) in this case thread is probably not due to separation, just porting to different boot loaders may be an issue here. cheers Erich -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
20.09.2014 14:07, Erich Titl пишет: Hi Andrew at 19.09.2014 20:39, Andrew wrote: 19.09.2014 15:04, Erich Titl пишет: Hi at 19.09.2014 10:35, kp kirchdoerfer wrote: Am Donnerstag, 18. September 2014, 18:59:40 schrieb Timothy Wegner: David wrote: ... Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It is needed with the newer kernel in 5.1. You may add it grom the modules tarball to initmod.lrp. See http://bering-uclibc.zetam.org/wiki/Bering-uClibc_5.x_-_User_Guide_-_Advanced_Topics_-_Modifying_initrd.lrp how to modify initmod.lrp (It's written for initrd, but it's also valid for initmod). For what it's worth, I never understood the rationale behind splitting initrd, except for a few cycles on the server building it. It makes life miserable for anyone using a boot loader which does not support multiple initrd files. It probably needs more space for initrd storage and makes debugging more difficult. I vote to go back to single initrd files. cheers Erich It's for 1) completely separating userland from kernel - that will allow us to maintaindifferent kernel branches in single release and I don't understand this statement, modules are not userland. Right. Modules aren't userland. So modules are splitted from userland initrd. 2) for embedded platforms where there is a single userland for arch, and multiple kernels (even with different versions - if there is a proprietary patch w/o ports to other versions, and even w/o boot-time modules for some platforms - if there is a fixed configuration of boot-time modules, they may be linked into kernel as static). If we had that there would be no need for initmod. Right. For one platform. Another platform with same arch (for ex., ARMv7) can be booted from SD card/USB - and will have modules (because USB drives aren't necessary). So it'll be good to have universal initrd, and initmods for different platforms (if they are needed). Also it helps to easily update userspace w/o kernel or kernel w/o userspace (they are almost independent now). As they should be but I iterate here, modules are not userland ( I have been made aware of this on this proper list ;-) If loader doesn't support multiple initrd, 2 pieces can be easily concatenated into one w/o repacking. I understand the idea of separating the kernel from userland, but modules are alway kernel dependent. Right, and they are also separated from userland. Now you can just place kernel with initmod and moddb.lrp/modules.tgz into your distro - and voila, you have old stable userland with bleeding-edge kernel. Even building multiple different self contained initrd for single kernels are no problem as we have a initrd build procedure which may very well build multiple different architecture initrd files. As you say, as they are cpio archives they can easily be put together, so why not just do it. cpio is useful for x86; for embedded with on-board flash - we even may use squashfs with tmpfs on top (for saving valuable RAM). I think this will be done in 5.2. Also, almost all boot loaders suport multiple ramdisks. So I don't think that it's actual trouble. The missing module(s) in this case thread is probably not due to separation, just porting to different boot loaders may be an issue here. cheers Erich -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hi Andrew at 20.09.2014 20:13, Andrew wrote: 20.09.2014 14:07, Erich Titl пишет: ... Right. Modules aren't userland. So modules are splitted from userland initrd. I would probably argue that initrd isn't userland at all in my mindmap. For me initrd is a way to allow a system to be booted and IMHO every trace of it should disappear in the later boot process. But again, this is just an opinion. 2) for embedded platforms where there is a single userland for arch, and multiple kernels (even with different versions - if there is a proprietary patch w/o ports to other versions, and even w/o boot-time modules for some platforms - if there is a fixed configuration of boot-time modules, they may be linked into kernel as static). If we had that there would be no need for initmod. Right. For one platform. Another platform with same arch (for ex., ARMv7) can be booted from SD card/USB - and will have modules (because USB drives aren't necessary). So it'll be good to have universal initrd, and initmods for different platforms (if they are needed). Also it helps to easily update userspace w/o kernel or kernel w/o userspace (they are almost independent now). As they should be but I iterate here, modules are not userland ( I have been made aware of this on this proper list ;-) If loader doesn't support multiple initrd, 2 pieces can be easily concatenated into one w/o repacking. I understand the idea of separating the kernel from userland, but modules are alway kernel dependent. Right, and they are also separated from userland. Now you can just place kernel with initmod and moddb.lrp/modules.tgz into your distro - and voila, you have old stable userland with bleeding-edge kernel. Even building multiple different self contained initrd for single kernels are no problem as we have a initrd build procedure which may vebuild multiple different architecture initrd files. As you say, as they are cpio archives they can easily be put together, so why not just do it. cpio is useful for x86; for embedded with on-board flash - we even may use squashfs with tmpfs on top (for saving valuable RAM). I think this will be done in 5.2 Then it might be more difficult to fix it if needed. I would just be glad if leaf was not such a moving target, so I could get some development done. . Also, almost all boot loaders suport multiple ramdisks. So I don't think that it's actual trouble. M... I have not seen this for grub, but then I am not using grub2 need to investigate. cheers Erich -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
at 18.09.2014 20:38, Timothy Wegner wrote: David wrote: If you do press Enter to activate this console are you able to mount the USB drive manually? If not then it is probably a Driver (i.e. missing Module) issue; if you can always mount it manually then it's normally a timing issue, and usb_wait should help. You might need usb_wait=4 or more, I guess, if 3 is not working. In the console I don't see any device like sda1 in /dev, so I would presume I can't mount manually. I think the hypothesis that there is a missing module is a good guess. Eric wrote (off list): And here is the failing command line from 5.1.x no LEAFCGF [0.00] Kernel command line: reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 Alas, no, there was just some funny white space, LEAFCFG is there. Here's the (very long) line from a more recent bad boot: [0.00] Kernel command line: reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 intel_idle.max_cstate=0 processor.max_cstate=1 BOOT_IMAGE=/syslinux/linux initrd=/initrd.lrp,/initmod.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda1:vfat OK, then it seems that the device cannot be mounted as others suggested. Can you unpack the modules from the initrd files and see what is there. So syslinux.cfg is read properly. So ... right after LINUXRC: Looking for leaf.cfg... The bad boot 5.1 has: LINUXRC: Generating default dirs... The good boot 5.0.4 has: LINUXRC: Mounting /dev/sda1 on /var/lib/lrpkg/mnt as vfat Yes, because it has software to deal with your usb device. So somehow /dev/sda1 is never mounted, and it does not appear to be a problem with syslinux.cfg. Assuming there is a missing module, how to diagnose and fix? This would be very tedious, but I can make sure that all the modules in modules.lrp of the good boot are in the modules.lrp for 5.1.1RC. Would that work? (I know *.lrp is really *.tar.gz so I can add modules by hand under Linux.) You need to have the usb modules somewhere in the initram disk to be able to mount the device and read all the other modules from disk. I bet there is something missing in the initrd for you. cheers Erich -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Am Donnerstag, 18. September 2014, 18:59:40 schrieb Timothy Wegner: David wrote: I guess take a look at the output from 'lsmod' on your working system and compare with what you get after the press Enter prompt. lsmod of course reports a boatload of modules that are loaded later after a successful boot process. So I renamed leaf.cfg to leaf.not so the good 5.0.4 boot would fail at more or less the same place as the bad 5.1 boot, and I then executed lsmod in the console. The result of lsmod (not in order) is: ehci_hcd 35937 0 - Live 0xa020c000 sd_mod 28104 0 - Live 0xa029a000 usb_storage 35661 0 - Live 0xa028b000 usb_libusual 10431 1 usb_storage, Live 0xa0281000 x pcspkr 1740 0 - Live 0xa0274000 x ahci 21028 0 - Live 0xa025f000 x libahci 18695 1 ahci, Live 0xa0255000 x ohci_hcd 18053 0 - Live 0xa00e6000 x libata 159100 2 ahci,libahci, Live 0xa0219000 x scsi_mod 136275 3 sd_mod,usb_storage,libata, Live 0xa018f000 x usbcore 124366 5 usb_storage,usb_libusual,ehci_hcd,ohci_hcd, Live 0xa002e000 x usb_common 827 1 usbcore, Live 0xa0022000 x vfat 9704 0 - Live 0xa001c000 x fat 46900 1 vfat, Live 0xa000a000 x isofs 23733 0 - Live 0xa000 [...] Thanks everyone, I *think* I'm making progress! Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It is needed with the newer kernel in 5.1. You may add it grom the modules tarball to initmod.lrp. See http://bering-uclibc.zetam.org/wiki/Bering-uClibc_5.x_-_User_Guide_-_Advanced_Topics_-_Modifying_initrd.lrp how to modify initmod.lrp (It's written for initrd, but it's also valid for initmod). hth kp -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hi at 19.09.2014 10:35, kp kirchdoerfer wrote: Am Donnerstag, 18. September 2014, 18:59:40 schrieb Timothy Wegner: David wrote: ... Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It is needed with the newer kernel in 5.1. You may add it grom the modules tarball to initmod.lrp. See http://bering-uclibc.zetam.org/wiki/Bering-uClibc_5.x_-_User_Guide_-_Advanced_Topics_-_Modifying_initrd.lrp how to modify initmod.lrp (It's written for initrd, but it's also valid for initmod). For what it's worth, I never understood the rationale behind splitting initrd, except for a few cycles on the server building it. It makes life miserable for anyone using a boot loader which does not support multiple initrd files. It probably needs more space for initrd storage and makes debugging more difficult. I vote to go back to single initrd files. cheers Erich -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
kp wrote: Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It This worked with Bering-uClibc_5.1.1-rc1! Thanks! My Soekris net6501 now runs Bering-uClibc_5.1.1-rc1 like a champ! While I am perfectly happy to manually add ehci-pci.ko.gz initmod.lrp as needed in the future, would I be correct that ehci-pci.ko.gz will be added to initmod.lrp in future releases? (I would think so.) Thanks again. Final note. I had a problem when I upgraded from 5.0.4 to 5.0.5 that I hadn't mentioned before. This problem is also cleaned up with 5.1rc1. I honestly don't know if this problem had to do with Leaf or (just as likely) some configuration change I made. But I'll briefly describe it here: After upgrading to 5.0.5, I noticed that some websites were glacially slow (I was using the 6501 box as my firewall/router). Finally I ran speedtest.net, only to find that while the download speed was very fast, the benchmark could not even run the upload test, and was stuck on connecting. The site's documentation said this might be a firewall issue. This is very strange because other than the slowness, I had been using 5.0.5 for a week or so and everything else worked. When I downgraded to Leaf to 5.0.4 the problem went away. And, as I said, when I upgraded from 5.0.4 to 5.1.1 rc1 just now, the problem also went away. I confess to having limited scientific curiosity about this since the symptoms are gone, just mentioning for completeness. Thanks to all who participated in this thread. Great support! Tim -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
19.09.2014 15:04, Erich Titl пишет: Hi at 19.09.2014 10:35, kp kirchdoerfer wrote: Am Donnerstag, 18. September 2014, 18:59:40 schrieb Timothy Wegner: David wrote: ... Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It is needed with the newer kernel in 5.1. You may add it grom the modules tarball to initmod.lrp. See http://bering-uclibc.zetam.org/wiki/Bering-uClibc_5.x_-_User_Guide_-_Advanced_Topics_-_Modifying_initrd.lrp how to modify initmod.lrp (It's written for initrd, but it's also valid for initmod). For what it's worth, I never understood the rationale behind splitting initrd, except for a few cycles on the server building it. It makes life miserable for anyone using a boot loader which does not support multiple initrd files. It probably needs more space for initrd storage and makes debugging more difficult. I vote to go back to single initrd files. cheers Erich It's for 1) completely separating userland from kernel - that will allow us to maintaindifferent kernel branches in single release and 2) for embedded platforms where there is a single userland for arch, and multiple kernels (even with different versions - if there is a proprietary patch w/o ports to other versions, and even w/o boot-time modules for some platforms - if there is a fixed configuration of boot-time modules, they may be linked into kernel as static). Also it helps to easily update userspace w/o kernel or kernel w/o userspace (they are almost independent now). If loader doesn't support multiple initrd, 2 pieces can be easily concatenated into one w/o repacking. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Am Freitag, 19. September 2014, 11:12:09 schrieb Timothy Wegner: kp wrote: Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing. It This worked with Bering-uClibc_5.1.1-rc1! Thanks! My Soekris net6501 now runs Bering-uClibc_5.1.1-rc1 like a champ! While I am perfectly happy to manually add ehci-pci.ko.gz initmod.lrp as needed in the future, would I be correct that ehci-pci.ko.gz will be added to initmod.lrp in future releases? (I would think so.) Yes, it worked for me when testing, and I waited for your confirmation that it also fixes your issue. It's clearly a bug, while updating the kernel version for 5.1. The fix has already committed to our repository for the next version. kp Thanks again. Final note. I had a problem when I upgraded from 5.0.4 to 5.0.5 that I hadn't mentioned before. This problem is also cleaned up with 5.1rc1. I honestly don't know if this problem had to do with Leaf or (just as likely) some configuration change I made. But I'll briefly describe it here: After upgrading to 5.0.5, I noticed that some websites were glacially slow (I was using the 6501 box as my firewall/router). Finally I ran speedtest.net, only to find that while the download speed was very fast, the benchmark could not even run the upload test, and was stuck on connecting. The site's documentation said this might be a firewall issue. This is very strange because other than the slowness, I had been using 5.0.5 for a week or so and everything else worked. When I downgraded to Leaf to 5.0.4 the problem went away. And, as I said, when I upgraded from 5.0.4 to 5.1.1 rc1 just now, the problem also went away. I confess to having limited scientific curiosity about this since the symptoms are gone, just mentioning for completeness. Thanks to all who participated in this thread. Great support! Tim -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hi Jürgen, If you do press Enter to activate this console are you able to mount the USB drive manually? If not then it is probably a Driver (i.e. missing Module) issue; if you can always mount it manually then it's normally a timing issue, and usb_wait should help. You might need usb_wait=4 or more, I guess, if 3 is not working. davidMbrooke On 17 Sep 2014, at 21:24, Timothy Wegner wrote: Jürgen wrote: syslinux.cfg is not enough. To put a getty on a serial line, you need inittab too. Of course you are right. I have the appropriate lines in inittab. Probably I picked them up by re-using a configdb.lrp from a serial version of Leaf. I appreciate the tip about re-using a configdb.lrp from a serial Geode version, I may try that if I get nervous about re-using old configdb.lrp. Erich wrote: - have you verified you are loading _both_ initram files? How can I verify this? - if so, have you verified that the running system stub is capable to read from your storage? I found problems with fast CF in the past. I am using a SanDisk Cruzer Fit. Works with Bering 5.0.4 but not 5.1. Here is the tail end of the boot messages with 5.1 (doesn't work) START LINUXRC: Looking for leaf.cfg... LINUXRC: Generating default dirs... LINUXRC: Creating /tmp /var/log partitions ... LINUXRC: PKGPATH is empty or unset. Can not install packages. LINUXRC: LRP= is empty or unset. Can not install packages. Running stage2 depmod after loading: moddb Running stage2 module loading LINUXRC: chown and chmod /dev... LINUXRC: Loaded Packages LINUXRC: Creating new rootfs... LINUXRC: Switch_root into new rootfs... can't run '/etc/init.d/rcS': No such file or directory Please press Enter to activate this console. END Here is the same portion of the boot messages from 5.0.4 that works: START LINUXRC: Looking for leaf.cfg... LINUXRC: Mounting /dev/sda1 on /var/lib/lrpkg/mnt as vfat LINUXRC: Sourcing leaf.cfg from /dev/sda1 LINUXRC: Generating default dirs... LINUXRC: Creating /tmp /var/log partitions ... LINUXRC: Setting up ZRAM swap ... Setting up swapspace version 1, size = 58716160 bytes //END So you see it does look like the USB drive doesn't get mounted. Thanks again. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
David wrote: If you do press Enter to activate this console are you able to mount the USB drive manually? If not then it is probably a Driver (i.e. missing Module) issue; if you can always mount it manually then it's normally a timing issue, and usb_wait should help. You might need usb_wait=4 or more, I guess, if 3 is not working. In the console I don't see any device like sda1 in /dev, so I would presume I can't mount manually. I think the hypothesis that there is a missing module is a good guess. Eric wrote (off list): And here is the failing command line from 5.1.x no LEAFCGF [0.00] Kernel command line: reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 Alas, no, there was just some funny white space, LEAFCFG is there. Here's the (very long) line from a more recent bad boot: [0.00] Kernel command line: reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 intel_idle.max_cstate=0 processor.max_cstate=1 BOOT_IMAGE=/syslinux/linux initrd=/initrd.lrp,/initmod.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda1:vfat So syslinux.cfg is read properly. So ... right after LINUXRC: Looking for leaf.cfg... The bad boot 5.1 has: LINUXRC: Generating default dirs... The good boot 5.0.4 has: LINUXRC: Mounting /dev/sda1 on /var/lib/lrpkg/mnt as vfat So somehow /dev/sda1 is never mounted, and it does not appear to be a problem with syslinux.cfg. Assuming there is a missing module, how to diagnose and fix? This would be very tedious, but I can make sure that all the modules in modules.lrp of the good boot are in the modules.lrp for 5.1.1RC. Would that work? (I know *.lrp is really *.tar.gz so I can add modules by hand under Linux.) Thanks again. Tim -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
On 18 Sep 2014, at 19:38, Timothy Wegner wrote: David wrote: If you do press Enter to activate this console are you able to mount the USB drive manually? If not then it is probably a Driver (i.e. missing Module) issue; if you can always mount it manually then it's normally a timing issue, and usb_wait should help. You might need usb_wait=4 or more, I guess, if 3 is not working. In the console I don't see any device like sda1 in /dev, so I would presume I can't mount manually. I think the hypothesis that there is a missing module is a good guess. Hi Tim, Yep, definitely sounds like a missing module. I guess take a look at the output from 'lsmod' on your working system and compare with what you get after the press Enter prompt. davidMbrooke -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
at 18.09.2014 20:38, Timothy Wegner wrote: David wrote: If you do press Enter to activate this console are you able to mount the USB drive manually? If not then it is probably a Driver (i.e. missing Module) issue; if you can always mount it manually then it's normally a timing issue, and usb_wait should help. You might need usb_wait=4 or more, I guess, if 3 is not working. In the console I don't see any device like sda1 in /dev, so I would presume I can't mount manually. I think the hypothesis that there is a missing module is a good guess. Eric wrote (off list): And here is the failing command line from 5.1.x no LEAFCGF [0.00] Kernel command line: reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 Alas, no, there was just some funny white space, LEAFCFG is there. Here's the (very long) line from a more recent bad boot: [0.00] Kernel command line: reboot=bios usb_wait=3 console=ttyS0,19200n8 VERBOSE=1 intel_idle.max_cstate=0 processor.max_cstate=1 BOOT_IMAGE=/syslinux/linux initrd=/initrd.lrp,/initmod.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda1:vfat OK, then it seems that the device cannot be mounted as others suggested. Can you unpack the modules from the initrd files and see what is there. So syslinux.cfg is read properly. So ... right after LINUXRC: Looking for leaf.cfg... The bad boot 5.1 has: LINUXRC: Generating default dirs... The good boot 5.0.4 has: LINUXRC: Mounting /dev/sda1 on /var/lib/lrpkg/mnt as vfat Yes, because it has software to deal with your usb device. So somehow /dev/sda1 is never mounted, and it does not appear to be a problem with syslinux.cfg. Assuming there is a missing module, how to diagnose and fix? This would be very tedious, but I can make sure that all the modules in modules.lrp of the good boot are in the modules.lrp for 5.1.1RC. Would that work? (I know *.lrp is really *.tar.gz so I can add modules by hand under Linux.) You need to have the usb modules somewhere in the initram disk to be able to mount the device and read all the other modules from disk. I bet there is something missing in the initrd for you. cheers Erich -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
David wrote: I guess take a look at the output from 'lsmod' on your working system and compare with what you get after the press Enter prompt. lsmod of course reports a boatload of modules that are loaded later after a successful boot process. So I renamed leaf.cfg to leaf.not so the good 5.0.4 boot would fail at more or less the same place as the bad 5.1 boot, and I then executed lsmod in the console. The result of lsmod (not in order) is: ehci_hcd 35937 0 - Live 0xa020c000 sd_mod 28104 0 - Live 0xa029a000 usb_storage 35661 0 - Live 0xa028b000 usb_libusual 10431 1 usb_storage, Live 0xa0281000 x pcspkr 1740 0 - Live 0xa0274000 x ahci 21028 0 - Live 0xa025f000 x libahci 18695 1 ahci, Live 0xa0255000 x ohci_hcd 18053 0 - Live 0xa00e6000 x libata 159100 2 ahci,libahci, Live 0xa0219000 x scsi_mod 136275 3 sd_mod,usb_storage,libata, Live 0xa018f000 x usbcore 124366 5 usb_storage,usb_libusual,ehci_hcd,ohci_hcd, Live 0xa002e000 x usb_common 827 1 usbcore, Live 0xa0022000 x vfat 9704 0 - Live 0xa001c000 x fat 46900 1 vfat, Live 0xa000a000 x isofs 23733 0 - Live 0xa000 The ones marked with x were also present in the failed 5.1 boot. So (maybe) I need to enable these: ehci_hcd 35937 0 - Live 0xa020c000 sd_mod 28104 0 - Live 0xa029a000 usb_storage 35661 0 - Live 0xa028b000 usb_libusual 10431 1 usb_storage, Live 0xa0281000 Where are these normally loaded, and where should I put them to load? I can probably answer this myself by seeing where they are located in my 5.0.4 usb, but any comments appreciated. Thanks everyone, I *think* I'm making progress! Tim -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hi syslinux.cfg is not enough. To put a getty on a serial line, you need inittab too. Juergen On 16. September 2014 23:30:32 MESZ, Timothy Wegner tweg...@swbell.net wrote: Jurgen wrote: 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 No, I have always used the 486 image (Bering-uClibc_5.1_i486_syslinux_serial.tar.gz) with the older 4801. I should add I tried the 486 serial image with the newer 6501 but that did not solve the problem. Theoretically the 486 image should work just fine. I did not use a Geode image with any Soekris boxes. I am sure Geode is not what I need for the Soekris net6501 since it uses an Intel atom chip, and for the Soekris net4801 box the 486 images have always worked. 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. With the Soekris net6501 the Bering-uClibc_5.0.4_x86_64_syslinux_vga.tar.gz image with syslinux.cfg modified for serial works perfectly. I haven't found the lack of a serial package for x86-64 to be a problem since all I have had to do is use a vga version and edit syslinux.cfg to support serial. At least that worked for 5.0.4 and 5.0.5. I believe my problem is not serial support because I can see the first part of the boot messages up until boot fails. I suspect some module is missing, but I'm not sure how to tell. Since Leaf 5.0.4 works, maybe there's a way I can study the working configuration to get things working with 5.1. Thanks again. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ Mit freundlichen Grüßen Jürgen Northe --- Diese Nachricht wurde von meinem Mobiltelefon mit K-9 Mail gesendet. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
17.09.2014 00:30, Timothy Wegner пишет: Jurgen wrote: 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 No, I have always used the 486 image (Bering-uClibc_5.1_i486_syslinux_serial.tar.gz) with the older 4801. I should add I tried the 486 serial image with the newer 6501 but that did not solve the problem. Theoretically the 486 image should work just fine. I did not use a Geode image with any Soekris boxes. I am sure Geode is not what I need for the Soekris net6501 since it uses an Intel atom chip, and for the Soekris net4801 box the 486 images have always worked. i486 image (like Geode one) is used for legacy i486/pentium-compatible boxes. It lacks some drivers for devices that are present on fresh platforms. It lacks SMP. But it's more lightweight. Generic images are i686 and x86_64. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hi bit late to chime in, can't remember everything you tried but - have you verified you are loading _both_ initram files? - if so, have you verified that the running system stub is capable to read from your storage? I found problems with fast CF in the past. - if you can read from your storage and you are loading all necessary modules then it probably is inittab cheers Erich -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Jürgen wrote: syslinux.cfg is not enough. To put a getty on a serial line, you need inittab too. Of course you are right. I have the appropriate lines in inittab. Probably I picked them up by re-using a configdb.lrp from a serial version of Leaf. I appreciate the tip about re-using a configdb.lrp from a serial Geode version, I may try that if I get nervous about re-using old configdb.lrp. Erich wrote: - have you verified you are loading _both_ initram files? How can I verify this? - if so, have you verified that the running system stub is capable to read from your storage? I found problems with fast CF in the past. I am using a SanDisk Cruzer Fit. Works with Bering 5.0.4 but not 5.1. Here is the tail end of the boot messages with 5.1 (doesn't work) START LINUXRC: Looking for leaf.cfg... LINUXRC: Generating default dirs... LINUXRC: Creating /tmp /var/log partitions ... LINUXRC: PKGPATH is empty or unset. Can not install packages. LINUXRC: LRP= is empty or unset. Can not install packages. Running stage2 depmod after loading: moddb Running stage2 module loading LINUXRC: chown and chmod /dev... LINUXRC: Loaded Packages LINUXRC: Creating new rootfs... LINUXRC: Switch_root into new rootfs... can't run '/etc/init.d/rcS': No such file or directory Please press Enter to activate this console. END Here is the same portion of the boot messages from 5.0.4 that works: START LINUXRC: Looking for leaf.cfg... LINUXRC: Mounting /dev/sda1 on /var/lib/lrpkg/mnt as vfat LINUXRC: Sourcing leaf.cfg from /dev/sda1 LINUXRC: Generating default dirs... LINUXRC: Creating /tmp /var/log partitions ... LINUXRC: Setting up ZRAM swap ... Setting up swapspace version 1, size = 58716160 bytes //END So you see it does look like the USB drive doesn't get mounted. Thanks again. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
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 tweg...@swbell.net 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Jurgen wrote: 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 No, I have always used the 486 image (Bering-uClibc_5.1_i486_syslinux_serial.tar.gz) with the older 4801. I should add I tried the 486 serial image with the newer 6501 but that did not solve the problem. Theoretically the 486 image should work just fine. I did not use a Geode image with any Soekris boxes. I am sure Geode is not what I need for the Soekris net6501 since it uses an Intel atom chip, and for the Soekris net4801 box the 486 images have always worked. 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. With the Soekris net6501 the Bering-uClibc_5.0.4_x86_64_syslinux_vga.tar.gz image with syslinux.cfg modified for serial works perfectly. I haven't found the lack of a serial package for x86-64 to be a problem since all I have had to do is use a vga version and edit syslinux.cfg to support serial. At least that worked for 5.0.4 and 5.0.5. I believe my problem is not serial support because I can see the first part of the boot messages up until boot fails. I suspect some module is missing, but I'm not sure how to tell. Since Leaf 5.0.4 works, maybe there's a way I can study the working configuration to get things working with 5.1. Thanks again. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
Re: [leaf-user] Can anyone run Bering 5.1.x on Soekris net6501?
Hello Tim, some weeks ago I had similar problems with the new PC Engines APU board, I suppose you took the Bering-uClibc_5.1_x86_64_syslinux_vga.tar.gz which does not use the serial console. So I took the configdb.lrp from the Bering-uClibc_5.1_geode_syslinux_serial.tar.gz and modified the syslinux.cfg file to read like this: /syslinux/syslinux.cfg SERIAL 0 115200 DISPLAY syslinux.dpy TIMEOUT 0 APPEND reboot=bios usb_wait=3 console=ttyS0,115200n8 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 However, I suppose we are missing a version for 64bit systems with only a serial console ?! Regards Juergen Am Mo. 15. Sep. 2014 00:03 CEST, Timothy Wegner tweg...@swbell.net schrieb: I am running the x86-64 version of Bering 5.0.4 very successfully on a Soekris net6501 used as a router. I was able to upgrade (mostly) successfully to 5.0.5. However I cannot get 5.1 or 5.1.1 RC1 to boot. I am booting with a Sandisk 16gb USB using Syslinux 4.0.5. The tail end of the boot message is quoted below. (The error about can't load module pata_legacy is apparently moot because I get that message even when the boot is successful with 5.0.4.) The error below is similar to the error mentioned in the documentation in Bering-uClibc 5.x - User Guide - Appendices - Upgrading from Bering-uClibc 4.x but that cites the problem of using an older Syslinux version, which I am not. Also, I have tried the 486 and 686 versions of Bering with the same results. I would appreciated any suggestions or reports that others have gotten 5.1 to work with the Soekris net6501 and if so, how it was done. I have been running Leaf for a very long time on a variety of boxen and have until now always managed to upgrade. Thanks, Tim Wegner Tail end of boot messages via the serial console follow: [4.660769] ata2: SATA max UDMA/133 abar m1024@0xa0004400 port 0xa0004580 irq 40 [4.965168] ata1: SATA link down (SStatus 0 SControl 300) [5.270116] ata2: SATA link down (SStatus 0 SControl 300) [5.494156] Clocksource tsc unstable (delta = 686979561 ns) [5.527693] Switching to clocksource refined-jiffies [5.735242] scsi2 : pata_legacy [5.754691] ata3: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14 [5.972054] scsi3 : pata_legacy [5.979077] ata4: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15 modprobe: can't load module pata_legacy (pata_legacy.ko.gz): No such device LINUXRC: Looking for leaf.cfg... LINUXRC: Generating default dirs... LINUXRC: Creating /tmp /var/log partitions ... LINUXRC: PKGPATH is empty or unset. Can not install packages. LINUXRC: LRP= is empty or unset. Can not install packages. Running stage2 depmod after loading: moddb Running stage2 module loading LINUXRC: chown and chmod /dev... LINUXRC: Loaded Packages LINUXRC: Creating new rootfs... LINUXRC: Switch_root into new rootfs... can't run '/etc/init.d/rcS': No such file or directory Please press Enter to activate this console. -- 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net 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=157508191iu=/4140/ostg.clktrk leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
