Sure, I don't mind testing it out on there for you, but, where do I find the pre releases to try then? At least we know it's between 2.13 and 3.00. That narrows it a bit I would think. Mind you, if it jumps up a major revision number, I guess that means a lot of changes went in. On 8/2/05, syslinux-request at zytor.com <syslinux-request at zytor.com> wrote:> Send SYSLINUX mailing list submissions to > syslinux at zytor.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.zytor.com/mailman/listinfo/syslinux > or, via email, send a message with subject or body 'help' to > syslinux-request at zytor.com > > You can reach the person managing the list at > syslinux-owner at zytor.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SYSLINUX digest..." > > > Today's Topics: > > 1. Re: Can't boot Syslinux from HD directly. Can indirectly? (Nazo) > 2. RE: Can't boot Syslinux from HD directly. Can indirect ly? > (Luis.F.Correia) > 3. Re: Can't boot Syslinux from HD directly. Can indirect ly? > (H. Peter Anvin) > > > > ---------- Forwarded message ---------- > From: Nazo <nazosan at gmail.com> > To: syslinux at zytor.com > Date: Mon, 1 Aug 2005 19:36:39 -0500 > Subject: Re: [syslinux] Can't boot Syslinux from HD directly. Can indirectly? > On 8/1/05, H. Peter Anvin <hpa at zytor.com> wrote: > > Nazo wrote: > > > I've installed Syslinux on a somewhat old system. The motherboard is > > > based on an Intel 440GX chipset (specifically it's the Supermicro > > > P6DGE if that means anything.) The harddrive has been split up into > > > partitions of one hidden FAT16 (marked as active) to which syslinux is > > > installed (hda1), one normal FAT32 which has windows and dos (hda2.) > > > It also has an extended partition containing an EXT2 and linux swap > > > partition, however, it didn't originally have these when I first saw > > > the problem so I know they aren't the issue. > > > > > > The issue is that for some reason it won't boot the harddrive > > > directly. It just freezes every time. It shows the word SYSLINUX, > > > the version (3.09) and date (2005-06-17) but stops there. Never > > > clears the screen or any of that either. I have installed it in safe > > > "slow" mode, but, what's more importantly, this same setup worked > > > perfectly fine for several weeks on the previous board I had in that > > > system, an Asus KN-97-X (Intel 440FX.) This leads me to believe it's > > > something weird to do with the bios. > > > > > > Currently I'm having to boot my rescue disc using isolinux and load > > > chain.c32 to manually boot that partition for it to work. When I do > > > this, it boots without a problem. I'd say definitely bios, however, > > > before this latest time I've installed syslinux on there, it was set > > > to boot partition "0" (aka the MBR!) As far as I can tell, it doesn't > > > cross the 1024 boundary (I haven't the vaguest idea how to verify > > > this, but, the FAT16 partition is the first 510 or so MB of a 60GB > > > drive, so it's hard to imagine it would do that.) > > > > > > Any idea what's going on? Is it somehow still past the 1024 boundary? > > > Any way to verify short of knowing how to add up those numbers on the > > > drive (which is such a pain to get to right now I'm not sure it's > > > worth the trouble.) > > > > > > > Do you know if this problem goes away with an older version of syslinux? > > There seems to be some issues with newer syslinuxes on some old > > hardware, which is still unresolved. > > > > -hpa > > > > > > > Yikes. I had just assumed later version = greater compatibility and > gone straight for the latest... Well, I had to go all the way back to > 2.13 (even 3.00 didn't work,) but, it seems to be working alright now. > I guess that it doesn't make much difference if I have to use an old > version in this case, it seems to have all the features I need for > this particular setup. It's strange that I was ok with the latest > version on that older KN-97 though. Still, I can understand better > Asus compatibility than Supermicro (who apparently are actually still > around -- I found a website and it still has archives for the old > products even -- just they aren't exactly concentrating on many > desktop systems anymore.) > > > > > > ---------- Forwarded message ---------- > From: "Luis.F.Correia" <Luis.F.Correia at seg-social.pt> > To: syslinux at zytor.com > Date: Tue, 2 Aug 2005 11:23:05 +0100 > Subject: RE: [syslinux] Can't boot Syslinux from HD directly. Can indirect ly? > Hi! > > > -----Original Message----- > > From: Nazo [mailto:nazosan at gmail.com] > > Sent: Tuesday, August 02, 2005 1:37 AM > > To: syslinux at zytor.com > > Subject: Re: [syslinux] Can't boot Syslinux from HD directly. > > Can indirectly? > > > > > > On 8/1/05, H. Peter Anvin <hpa at zytor.com> wrote: > > > Nazo wrote: > > > > I've installed Syslinux on a somewhat old system. The > > motherboard > > > > is based on an Intel 440GX chipset (specifically it's the > > Supermicro > > > > P6DGE if that means anything.) The harddrive has been > > split up into > > > > partitions of one hidden FAT16 (marked as active) to > > which syslinux > > > > is installed (hda1), one normal FAT32 which has windows and dos > > > > (hda2.) It also has an extended partition containing an EXT2 and > > > > linux swap partition, however, it didn't originally have > > these when > > > > I first saw the problem so I know they aren't the issue. > > > > > > > > The issue is that for some reason it won't boot the harddrive > > > > directly. It just freezes every time. It shows the word > > SYSLINUX, > > > > the version (3.09) and date (2005-06-17) but stops there. Never > > > > clears the screen or any of that either. I have installed it in > > > > safe "slow" mode, but, what's more importantly, this same setup > > > > worked perfectly fine for several weeks on the previous > > board I had > > > > in that system, an Asus KN-97-X (Intel 440FX.) This leads me to > > > > believe it's something weird to do with the bios. > > > > > > > > Currently I'm having to boot my rescue disc using > > isolinux and load > > > > chain.c32 to manually boot that partition for it to work. > > When I do > > > > this, it boots without a problem. I'd say definitely > > bios, however, > > > > before this latest time I've installed syslinux on there, > > it was set > > > > to boot partition "0" (aka the MBR!) As far as I can tell, it > > > > doesn't cross the 1024 boundary (I haven't the vaguest > > idea how to > > > > verify this, but, the FAT16 partition is the first 510 or > > so MB of a > > > > 60GB drive, so it's hard to imagine it would do that.) > > > > > > > > Any idea what's going on? Is it somehow still past the 1024 > > > > boundary? Any way to verify short of knowing how to add up those > > > > numbers on the drive (which is such a pain to get to > > right now I'm > > > > not sure it's worth the trouble.) > > > > > > > > > > Do you know if this problem goes away with an older version > > of syslinux? > > > There seems to be some issues with newer syslinuxes on some old > > > hardware, which is still unresolved. > > > > > > -hpa > > > > > > > > > > > > Yikes. I had just assumed later version = greater > > compatibility and gone straight for the latest... Well, I > > had to go all the way back to 2.13 (even 3.00 didn't work,) > > but, it seems to be working alright now. I guess that it > > doesn't make much difference if I have to use an old version > > in this case, it seems to have all the features I need for > > this particular setup. It's strange that I was ok with the > > latest version on that older KN-97 though. Still, I can > > understand better Asus compatibility than Supermicro (who > > apparently are actually still around -- I found a website and > > it still has archives for the old products even -- just they > > aren't exactly concentrating on many desktop systems anymore.) > > H. Peter would appreciate if you could detect where it did got broken, > Testing all the releases and the pre also... > > Luis Correia > > > > > > ---------- Forwarded message ---------- > From: "H. Peter Anvin" <hpa at zytor.com> > To: "Luis.F.Correia" <Luis.F.Correia at seg-social.pt> > Date: Tue, 02 Aug 2005 11:56:02 -0700 > Subject: Re: [syslinux] Can't boot Syslinux from HD directly. Can indirect ly? > Luis.F.Correia wrote: > >> > >>Yikes. I had just assumed later version = greater > >>compatibility and gone straight for the latest... Well, I > >>had to go all the way back to 2.13 (even 3.00 didn't work,) > >>but, it seems to be working alright now. I guess that it > >>doesn't make much difference if I have to use an old version > >>in this case, it seems to have all the features I need for > >>this particular setup. It's strange that I was ok with the > >>latest version on that older KN-97 though. Still, I can > >>understand better Asus compatibility than Supermicro (who > >>apparently are actually still around -- I found a website and > >>it still has archives for the old products even -- just they > >>aren't exactly concentrating on many desktop systems anymore.) > > > > H. Peter would appreciate if you could detect where it did got broken, > > Testing all the releases and the pre also... > > > > Yes, please. This has seemed to be a *damned* elusive bug, and I'm > utterly puzzled by it. > > -hpa > > > > > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > > >
Nazo wrote:> Sure, I don't mind testing it out on there for you, but, where do I > find the pre releases to try then?http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/> At least we know it's between 2.13 and 3.00. That narrows it a bit I > would think. Mind you, if it jumps up a major revision number, I > guess that means a lot of changes went in.Indeed. I believe (sorry, I'm still not swapped back in really) that someone else indicated 3.00-pre1 was the first one that broke it (note that both 2.20-preX and 3.00-preX are between 2.13 and 3.00). -hpa
Nazo wrote:>Sure, I don't mind testing it out on there for you, but, where do I >find the pre releases to try then? > >http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/
Nazo
2005-Aug-03 04:31 UTC
[syslinux] Can't boot Syslinux from HD directly. Can indirect ly?
Ah, using that copy you sent, the patched pre-pre 3.10 version (0x42f04563 is the precice number it says on there when I boot it) boots up and runs things just fine.
Nazo
2005-Aug-03 07:22 UTC
Fwd: [syslinux] Can't boot Syslinux from HD directly. Can indirect ly?
(Bumped something and it removed the CC, so I just manually copied the e-mail the normal way since I'm supposed to be sending to the list. Sorry. Lol, I am NOT used to mailing lists at all I'm afraid. I'm a forum person.) On 8/3/05, H. Peter Anvin <hpa at zytor.com> wrote:>I just released a syslinux-3.10-pre2. Could you please try it out? > >This is based on a rather wild guess as what the problem might be, >unfortunately. > > -hpaTook a while for them to show the file for that. Downloaded and installed. Unfortunately, it froze with the usual name and version number information. )-: When I tried to chain load it, it said "Load error - Boot failed" and froze.> Nazo wrote: > > > > I can't remember why I wanted Windows/DOS to be on a primary > > partition. I don't guess it'd care if it were extended, but, it'd be > > a pain to change now. > > Well, DOS can't run from a nonprimary. > > Anyway, if you could try the following: > > - Go to a DOS prompt > - Enter: > > debug > a 100 > mov bx,55aa > mov ah,41 > mov dl,80 > int 13 > int 3 > g=100 > > ... and let me know what the output is, I would appreciate it. > > -hpa >Lol, to me that machine code is such gibberish that you could be giving me the code to low level format my HD and I wouldn't know it. Nonetheless, I tried it anyway. ^_^ Here's the output: C:\DOS>debug -a 100 0B95:0100 mov bx,55aa 0B95:0103 mov ah,41 0B95:0105 mov dl,80 0B95:0107 int 13 0B95:0109 int 3 0B95:010A g=100 ^ Error [the carat is under the g if you aren't using a fixed-width font.] 0B95:010A _ I don't THINK I made any typos. I tried to triple check everything. Sorry, I suspect you were expecting a more informative output than an error on the g, but, not only do I know no machine code (well, I know nop, but, that doesn't count) I have also never really used debug before, so I don't know how to get a more informative output.
Nazo
2005-Aug-03 08:09 UTC
Fwd: [syslinux] Can't boot Syslinux from HD directly. Can indirect ly?
On 8/3/05, Bernhard Holzmayer <Holzmayer.Bernhard at foerstergroup.de> wrote:> Am Mittwoch, 3. August 2005 09:22 schrieben Sie: > > 0B95:010A g=100 > > ^ Error [the carat is under the g if you aren't > > using a fixed-width font.] > > 0B95:010A _ > > > > I don't THINK I made any typos. > > Correct. No typo. > Before entering g=100, just press <Return>. > Then apply 'g=100'... > > Just my 2cts. > Bernhard > >I see. Lol, comes from not knowing a darned thing about how debug works I guess. Sorry. Ok, tried again, this time hitting enter before the g=100. The output is this: AX=2100 BX=AA55 CX=0005 DX=0080 SP=FFEE BP=0000 SI=0000 DI=0000 DS=0F01 ES=0F01 SS=0F01 CS=0F01 IP=0109 NV UP DI NG NZ NA PO NC 0F01:0109 CC INT 3 Hope this helps.