When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ? But once the USBsyslinux takes over, has IT also got a USB driver? Since my MotherBoard & 2009 Slackware built USBstik syslinux booter were stolen I bought a <WinTel> laptop and USBextender to access my old IDE & SATA disks. With WinTel's new arrangement of not allowing the tail of the sda to be free for linux installation: I've only installed linux to some USBstiks. The attempted reconstruction of the stolen original Slackware BootStik seems valid, but it has no SATA of IDE to be tested with. Apparent correctly specified sdXY give "block (0,0)" errors and invalidly tried sdXY give "block (N,M)" errors - as expected ? Can the syslinux [or a newer version] mount a USB root-partition? == TIA.
>Do you mean boot SYSLINUX from stik-A but then load files like a >kernel/initrd from stikB:partition5? It's possible but only from a >development version of Syslinux that has the multifs patch merged.Yes: before my x86MotherBoard & <syslinux>USBstik were stolen, I could edit the <syslinux prompt> to boot to different partitions of the attatched IDE & SATA. Now I've got a laptop, with a USBextention driving a USB to IDE or SATA adaptor. The 64bitTinyCore/syslinux USBstik looks like: /mnt/sdb1/boot/isolinux/isolinux.bin 24576bytes <-size ISOLINUX 4.05 0x4f92e181 . Copyright (C) 1994-2011 H. Peter Anvin et al .isolinux: .No boot info table, assuming single session disk... .Spec packet missing LBA information, trying to wing it... .Loading spec packet failed, trying to wing it... .Found something at drive = .Looks reasonable, continuing... .Extremely broken BIOS detected, last attempt with drive = .Failed to locate CD- ROM device; boot failed. ..................that's just showing the initial contents & version. So I expect this TinyCore/syslinux to also be able to boot my good-old IDE & SATA installations. Or if I need a new/different USBstik to boot the 32bit IDE / SAT installations: HOW2 ? == TIA
On Mon, May 1, 2017 at 7:45 AM, eas lab via Syslinux <syslinux at zytor.com> wrote:>>Do you mean boot SYSLINUX from stik-A but then load files like a >>kernel/initrd from stikB:partition5? It's possible but only from a >>development version of Syslinux that has the multifs patch merged. > > Yes: before my x86MotherBoard & <syslinux>USBstik were stolen, I could > edit the <syslinux prompt> to boot to different partitions of the > attatched IDE & SATA.Sounds like either chain.c32 or LOCALBOOT was used or you merely passed different parameters to the kernel via its command line, like "root=/dev/sda5".> Now I've got a laptop, with a USBextention driving a USB to > IDE or SATA adaptor. The 64bitTinyCore/syslinux USBstik looks like: > /mnt/sdb1/boot/isolinux/isolinux.bin 24576bytes <-size > ISOLINUX 4.05 0x4f92e181 . Copyright (C) 1994-2011 H. Peter Anvin et al > .isolinux: .No boot info table, assuming single session disk... > .Spec packet missing LBA information, trying to wing it... > .Loading spec packet failed, trying to wing it... > .Found something at drive = .Looks reasonable, continuing... > .Extremely broken BIOS detected, last attempt with drive = .Failed to locate CD- > ROM device; boot failed. > ..................that's just showing the initial contents & version. > > So I expect this TinyCore/syslinux to also be able to boot my good-old > IDE & SATA installations.Probably but there seems to be missing details.> Or if I need a new/different USBstik to boot the 32bit IDE / SAT > installations: HOW2 ? > > == TIA-- -Gene