Yes this is the SAME question, that I can't get an answer from a month ago!
I have the files, from a USBstik [now stolen] which I previously could
edit at boot time, to boot any of my IDE or SATA partitions.
Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor
to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk.
The obvious question is: why [if] the old system could boot any IDE/SATA
partition, it can not boot a second USBdevice. The laptop is running 64b.
This is what the good old 32bit USBstik's files look like:------------
-rwxr-xr-x 1 root root 708 Oct 20 2015 message.txt
-rwxr-xr-x 1 root root 906 Oct 20 2015 sylinux.cfg
-rwxr-xr-x 1 root root 1138 Oct 20 2015 syslinux.cfg
-rwxr-xr-x 1 root root 123172 Oct 20 2015 vesamenu.c32
-rwxr-xr-x 1 root root 4940304 Oct 20 2015 vmlinuz
------- message.txt file reads:-----------------------
Welcome to the Slackware Linux custom USB boot stick!
By default, this stick boots a root Linux partition on /dev/sda3 when
you hit ENTER. If you'd like to boot some other partition, use a
command like this on the prompt below:
mount root=/dev/hda15 ro vga=791.
Where "/dev/sda1" is the partition you want to boot, and
"ro" specifies
that the partition should be initially mounted as read-only. If you
wish to mount the partition read-write, use "rw" instead. To set the
video console mode, use the vga= parameter (press F1 to see a table).
You may also add any other kernel parameters you might need depending
on your hardware, and which drivers are included in your kernel.
------------------------ end of file: message.txt -----------------
I suspect that <up-calls> eg. like old INT13, can't be made to access
additional USBports, like they could be to FIXED-LOCATION disk
partitions, eg. /dev/hdb5 ??
Hi, Le 13/06/2017 ? 00:51, eas lab via Syslinux a ?crit :> Yes this is the SAME question, that I can't get an answer from a month ago! > > I have the files, from a USBstik [now stolen] which I previously could > edit at boot time, to boot any of my IDE or SATA partitions. > > Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor > to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk. > > The obvious question is: why [if] the old system could boot any IDE/SATA > partition, it can not boot a second USBdevice. The laptop is running 64b. > This is what the good old 32bit USBstik's files look like:------------ > -rwxr-xr-x 1 root root 708 Oct 20 2015 message.txt > -rwxr-xr-x 1 root root 906 Oct 20 2015 sylinux.cfg > -rwxr-xr-x 1 root root 1138 Oct 20 2015 syslinux.cfg > -rwxr-xr-x 1 root root 123172 Oct 20 2015 vesamenu.c32 > -rwxr-xr-x 1 root root 4940304 Oct 20 2015 vmlinuz > ------- message.txt file reads:----------------------- > Welcome to the Slackware Linux custom USB boot stick! > > By default, this stick boots a root Linux partition on /dev/sda3 when > you hit ENTER. If you'd like to boot some other partition, use a > command like this on the prompt below: > > mount root=/dev/hda15 ro vga=791. > > Where "/dev/sda1" is the partition you want to boot, and "ro" specifies > that the partition should be initially mounted as read-only. If you > wish to mount the partition read-write, use "rw" instead. To set the > video console mode, use the vga= parameter (press F1 to see a table). > You may also add any other kernel parameters you might need depending > on your hardware, and which drivers are included in your kernel. > ------------------------ end of file: message.txt ----------------- > > I suspect that <up-calls> eg. like old INT13, can't be made to access > additional USBports, like they could be to FIXED-LOCATION disk > partitions, eg. /dev/hdb5 ??I don't think that syslinux be in concern here. If I understand well Slackware is installed on a hard disk partition that you want to access through the USB-adaptor to IDE/SATA. To mount /, the initramfs needs to know the partition's name reported by lsblk, that you'd give as a kernel parameter in the command line, as said by message.txt. But that also needs a kernel driver to handle the USB adapter. To find out, you could: _ boot a Slackware installation media _ as soon as you get a prompt type the (fake) login "root" _ then use the available command to identify the / partition of the installed Slackware. For instance type this command: lsblk -o model,name,size,filesystem If you think you have identified the partition, you can check its content mounting it as /mnt, then looking into /mnt. Then reboot, boot off the custom boot stick and indicate this partition's name after root= in the command line. But if the partition is not in lsblk's output, I'm afraid that you are out of luck, unless the support for the USB adapter be provided somehow as an additional module in the initramfs, that you would need to rebuild. Didier -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x60C03EEA.asc Type: application/pgp-keys Size: 1718 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20170613/25c01ce8/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: <http://www.zytor.com/pipermail/syslinux/attachments/20170613/25c01ce8/attachment.sig>
> Yes this is the SAME question, that I can't get an answer from a month ago! > > I have the files, from a USBstik [now stolen] which I previously could > edit at boot time, to boot any of my IDE or SATA partitions.How exactly were you editing (something)? Do you mean that you somehow changed some boot command from the Syslinux boot prompt during boot? In that case, which command you (used to) type in? Or, instead, were you editing the content of some file prior to rebooting? Please clarify.> > Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor > to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk.You seem to be assuming that changing from a direct SATA and IDE connections to some USB adapter would have no impact on how the respective HDDs are recognized/detected by the BIOS. You seem to be assuming that the BIOS from 2 different PCs/Laptops would recognize all your devices in the same exact way and that there would be no changes in behavior or in supported features by the respective BIOS. Generally speaking, these assumptions are not necessarily valid. There might be some particular case(s) in which, by coincidence, your whole hardware is "portable", but this is not a _generic_ situation. There might be some way to overcome potential differences, but we don't have any relevant information at this time in order to guide you in any way. Please also have in mind that this is the Syslinux Mailing List, and there is some practical limit as to how much guidance users can receive here about "whatever boot problem in the world might exist". At this point, there is no detail/information that actually indicates that there is some issue related to Syslinux in your situation; explicit clear information would help. Are you currently able to boot these OSes in any way? When trying your USB boot stick, what exactly do you see? What's the behavior? What do you do and in which way it "fails"? Is your current BIOS recognizing/detecting your disks in any way? Can both, the USB boot stick and the USB-to-SATA adapter, be connected to your laptop at the same time? Are there any additional disks connected in any way to this system, whether internally or externally, while you perform these attempts to boot? When you connect your USB boot stick, can you get to the Syslinux boot prompt or the boot menu using it? (I mean, before actually launching any particular OS, or before chainloading any other boot sector.) At this point, with the information you provided in your last email (I haven't re-read your prior emails), we cannot be sure you were actually using Syslinux in order to boot your OSes in your old (stolen) system in the way you described it. Regards, Ady.
> I don't think that syslinux be in concern here. If I understand well > Slackware is installed on a hard disk partition that you want to access > through the USB-adaptor to IDE/SATA.No. I'm not married to Slak. It's important to distinguish between verbatim/pasteable and what the old-writer merely thinks/remembers. I want to be able to boot ANY installation/partition as I vaguely remember I could do with the old USBstik.> To mount /, the initramfs needs to know the partition's name reported > by lsblk, that you'd give as a kernel parameter in the command line, as > said by message.txt.In the limiting case, there's only the 4 partitons of M$pook & stkA & stikB, which gives only 3 sdX1 to test BLINDLY.> But that also needs a kernel driver to handle the USB adapter.There are 2 separate goals: 1. booting a second USB-stik; 2. perhaps more difficult: booting ID or SATA via the USB-adapter. Apparently the USB-adapter is smart enough to hide the IDE/SATA. Using the principle of "successive refinement": my question was "Can USBstikA boot USBstkB ?". If so, then I'll tackle the IDE/SATA. When running debian7 and the USB adapter: `lsblk` lists all the IDE or SATA partitions. But that's not the question; which is <can syslinux boot USBstkB from USBstikA ?>> To find out, you could: > _ boot a Slackware installation media? with what: GRUB2, original DVD, ...?> _ as soon as you get a prompt type the (fake) login "root" > _ then use the available command to identify the / partition > of the installed Slackware. > For instance type this command: > lsblk -o model,name,size,filesystem> If you think you have identified the partition, you can check > its content mounting it as /mnt, then looking into /mnt. > Then reboot, boot off the custom boot stick and indicate this partition's > name after root= in the command line.> But if the partition is not in lsblk's output, I'm afraid that you are > out of luck, unless the support for the USB adapter be provided somehow > as an additional module in the initramfs, that you would need to rebuild.AFAIK `lsblk` will only be in the fully running linux, which can't tell me the capabilities of syslinux ?> DidierI want a solution based on the theory: the understanding of the HUMAN designed syslinux. It is not BLACKMAGIC to be discover. ==TIA