similar to: "isolinux.bin missing or corrupt" when booting USB flash drive in old PC

On 03/18/2017 03:02 PM, Thomas Schmitt via Syslinux wrote: > Hi, > > David Christensen wrote: >> I use this USB flash drive for bootable installer images; I do not >> attempt to mount it. I don't know that I could, even if I wanted to: > > mkdir /mnt/iso > mount /dev/sdc /mnt/iso > > or, because partition 1 starts at block 0, you may mount it too >

On 03/19/2017 09:42 PM, Martin Str|mberg via Syslinux wrote: > David Christensen wrote: >> This is how I prepared an ADATA USB Flash Drive 4 GB: > ... > install-mbr /dev/sdb > ... > [Rest of very clear description snipped.] > > What's that? That desn't exist in the Debian I'm running. > Otherwise you gave a very good description of what you're doing.

> On 03/19/2017 04:03 PM, David Christensen wrote: > > [ 0.600883] ---[ end Kernel panic - not syncing: VFS: Unable to mount > > root fs on unkonwn-block(0,0) > > Similar kernel panic when booted on Intel DQ67SW i7-2600S. > > > David > That's because your syslinux.cfg is "wrong", but the behavior just proves that SYSLINUX is indeed

syslinux at zytor.com: I have two older computers with Intel D865GBFLK motherboards (~2003) and Pentium 4 HT CPU's. They both have the latest available BIOS installed. I would like to put Debian on them. I have downloaded: http://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-8.7.1-i386-xfce-CD-1.iso When I put debian-8.7.1-i386-xfce-CD-1.iso on a CD-R, it boots correctly.

Hi, David Christensen wrote: > The USB flash drive boots the Debian installer in the old PC! Congrats. > There is no syslinux.cfg on debian-8.7.1-i386-xfce-CD-1.iso: The configuration is named /isolinux/isolinux.cfg. Looks like it is surrounded by a little empire of .cfg files: /isolinux/adgtk.cfg /isolinux/adtxt.cfg /isolinux/exithelp.cfg /isolinux/gtk.cfg

> Hi, > > Ady wrote: > > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > > "handoff.bin > > This does not look like it would tell much of the properties in question. > Nevertheless its print functions might be of interest for an isohybrid > diagnostic MBR. > > > > and at least 2 geodsp*.{bin,img(gz)} > > I am now reading >

On 03/18/2017 04:15 PM, Ady Ady via Syslinux wrote: > >> On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: >>> _ With the USB device connected to (one of) the problematic >>> computer(s), power up the system and get into the BIOS setup. In >>> the BIOS setup screen(s), change the boot order in such way that >>> the USB device is recognized as first

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS

On 03/21/2017 01:14 AM, Thomas Schmitt via Syslinux wrote: > Hi, > > David Christensen wrote: >> Booting the USB flash drive I prepared, the Debian installer runs: >> [...] >> The CD-ROM drive contains a CD which cannot be used for installation. > > Afaik, the software in a Debian ISO looks for particular files to > identify the device with the ISO. > Did you

On 03/19/2017 11:28 PM, David Christensen via Syslinux wrote: > I will try to do an install later, and will report the result. Booting the USB flash drive I prepared, the Debian installer runs: Select a language English Select your location United States Configure the keyboard American English Detect and mount CD-ROM Incorrect CD-ROM detected The CD-ROM drive contains a CD which

On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > Some of the things you should / could (re)test / (re)try: > > _ Verify the md5sum of the ISO image. SHA256 verified for downloaded image and for contents of USB flash drive (see below). > _ Is this particular USB device _still_ capable of booting newer > computers? Yes. > What happens if you would try _again_ to boot a

Hi, i have uploaded a little gz compressed tarball http://scdbackup.webframe.org/block_seq.tgz containing -rwxr-xr-x thomas/thomas 4552 2017-03-21 09:23 block_seq -rw-r--r-- thomas/thomas 315 2017-03-21 09:22 block_seq.c To be unpacked in a suitable directory by tar xvzf block_seq.tgz The binary "block_seq" was compiled on Debian Jessie. If it does not run, do cc -o

On 03/19/2017 01:01 AM, Thomas Schmitt via Syslinux wrote: > David Christensen wrote: >> Is there a way I can build live 32-bit Debian GNU/Linux USB images without >> isohdpfx.S and syslinux.bin? > > You could try > https://www.debian.org/releases/jessie/i386/ch04s03.html.en#usb-copy-flexible This is how I prepared an ADATA USB Flash Drive 4 GB: # cat

Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition

Hi, David Christensen had Martin's MBR write: > C That means the LBA 8444 has to be converted to a Cylinder/Head/Sector address. It would be interesting to learn by which heads/cylinder and sectors/head factors. > 00000000000000000000000000000000 > ... > 00000000000000000000000000000000 Well, this is none of the block contents which was written to the stick. Neither the MBR

Hi, funny or enlightening observation: With my qemu-system-i386 it would work if the detected Heads/Cylinder and Sectors/Head factors would change positions ! The effective read operation seems to use H/C = 32 , S/H = 63. The correct LBA would be addressed by H/C = 63 , S/H = 32. -------------------------------------------------------------------------- Reasoning: I have transplanted the

Hi, David Christensen wrote: > I see the source code for the error message: > .ascii "isolinux.bin missing or corrupt.\r\n" The riddle is why the MBR code does not get to see the expected bytes. > Figuring out why debian-8.7.1-i386-xfce-CD-1.iso works on CD, but doesn't > work on USB, The immediate reason is that from CD the program isolinux.bin is loaded

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read