SeaBIOS WinXP install

[Myles Watson]

Just for the fun of it I tried installing XP with the old Bochs BIOS and
then booting it with SeaBIOS.  It installs fine, then can't boot with either
BIOS.  With SeaBIOS, it blue screens with the same message as the install
CD.  Here's the log:

Thanks,
Myles

enter handle_18:
  NULL
Booting from CD-Rom...
ata_detect_medium: begin
await_ide: ERROR (TIMEOUT,BSY,!BSY,!BSY_DRQ,!BSY_!DRQ,!BSY_RDY) 3
status=0000005
1 time= 0 timeout= 32000
sectors=296508
579MB medium detected
Booting from 00000000:00007c00
fail handle_1ab10e:127(00000089):
  a=4153b10e b=00000000 c=00000000 d=20491a49 si=00000000 di=00000d34
  ds=0000f000 es=00001a49 ip=000077dd cs=00001000 f=00000246 r=00000cea
fail get_device:608(00000001):
  a=0000153f b=00000000 c=00000002 d=00060082 si=0000146a di=00000000
  ds=00001a49 es=00005023 ip=00005dd4 enter handle_11:
  a=00000000 b=0000000c c=00000040 d=00060000 si=00001338 di=00000000
  ds=00001a49 es=00000040 ip=0000412e cs=00001000 f=00000246 r=00000d06
fail floppy_13XX:709(00000001):
  a=00001507 b=00000003 c=0000000f d=00065000 si=00005026 di=00000000
  ds=00001a49 es=0000504a ip=000055be cs=00001000 f=00000212 r=00000c02

[Kevin O'Connor]

Hi Myles,

On Fri, Jul 25, 2008 at 03:58:05PM -0600, Myles Watson wrote:
> Just for the fun of it I tried installing XP with the old Bochs BIOS and
> then booting it with SeaBIOS.  It installs fine, then can't boot with either
> BIOS.  With SeaBIOS, it blue screens with the same message as the install
> CD.  Here's the log:

The log looks like a CD boot log - was it the same for the hd boot?

A couple of notes:

A "STOP: 0x0000007B" message is an INACCESSIBLE_BOOT_DEVICE error
according to:

http://blogs.technet.com/asksbs/archive/2008/03/30/how-to-troubleshoot-the-s...

I did notice that the last log message always seems to be:
> fail floppy_13XX:709(00000001):
>   a=00001507 b=00000003 c=0000000f d=00065000 si=00005026 di=00000000
>   ds=00001a49 es=0000504a ip=000055be cs=00001000 f=00000212 r=00000c02

you could try enabling the CONFIG_FLOPPY_SUPPORT on your machine.  If
that doesn't work, you could try just enabling a floppy_1315() handler
that always sets regs->ah=0 and calls set_success().

Another thing to try would be to set DEBUG_HDL_13 and DEBUG_HDL_40 to
1 so that you see every call into the bios disk handlers.

BTW, what are you using to log the output from serial?  If something
is sending backspaces - is there a way to capture that?

Also, you reported that Bochs 1.186 is working with ADLO.  Does a more
recent version of Bochs also work?  The seabios code is basically in
synch with the latest bochs (v1.211).

I wish there was more help I could give; unfortunately I'm seeing a
totally different set of failures here.  :-(

-Kevin

[Myles Watson]

> -----Original Message-----
> From: Kevin O'Connor [mailto:[e-mail]]
> Sent: Friday, July 25, 2008 9:49 PM
> To: Myles Watson
> Cc: Coreboot
> Subject: Re: SeaBIOS WinXP install
>
> Hi Myles,
>
> On Fri, Jul 25, 2008 at 03:58:05PM -0600, Myles Watson wrote:
> > Just for the fun of it I tried installing XP with the old Bochs BIOS and
> > then booting it with SeaBIOS.  It installs fine, then can't boot with
>
> either
> > BIOS.  With SeaBIOS, it blue screens with the same message as the
>
> install
> > CD.  Here's the log:
>
> The log looks like a CD boot log - was it the same for the hd boot?

After an install, you have to reboot with the CD.
> A couple of notes:
>
> A "STOP: 0x0000007B" message is an INACCESSIBLE_BOOT_DEVICE error
> according to:
>
> http://blogs.technet.com/asksbs/archive/2008/03/30/how-to-troubleshoot-
> the-stop-error-0x0000007b.aspx
>
> I did notice that the last log message always seems to be:
> > fail floppy_13XX:709(00000001):
> >   a=00001507 b=00000003 c=0000000f d=00065000 si=00005026 di=00000000
> >   ds=00001a49 es=0000504a ip=000055be cs=00001000 f=00000212 r=00000c02
>
> you could try enabling the CONFIG_FLOPPY_SUPPORT on your machine.  If
> that doesn't work, you could try just enabling a floppy_1315() handler
> that always sets regs->ah=0 and calls set_success().

I'll try it.
> Another thing to try would be to set DEBUG_HDL_13 and DEBUG_HDL_40 to
> 1 so that you see every call into the bios disk handlers.
>
> BTW, what are you using to log the output from serial?  If something
> is sending backspaces - is there a way to capture that?

I'm using HyperTerminal.  Thanks for pointing this out.  It shoots my theory
about backspaces, because HyperTerminal logs those.  Any thoughts on where
the disappearing output might go?
> Also, you reported that Bochs 1.186 is working with ADLO.  Does a more
> recent version of Bochs also work?  The seabios code is basically in
> synch with the latest bochs (v1.211).

I can try it.
> I wish there was more help I could give; unfortunately I'm seeing a
> totally different set of failures here.  :-(

Hopefully we'll get to a common case eventually so we can help each other
better.

Thanks,
Myles