On Thursday 18 November 2004 08:41 am, Benjamin Lutz wrote: > On Monday 15 November 2004 20:29, John Baldwin wrote: > > On Tuesday 09 November 2004 12:47 pm, ALeine wrote: > > > I installed FreeBSD 5.3-RELEASE from the ISO CD image, but it won't > > > boot: > > > > > > F1 DOS > > > F2 Linux > > > F3 FreeBSD > > > > > > Default: F3 > > > > > > _ > > > int=00000006 err=00000000 efl=00000282 eip=000947cf > > > eax=000000c1 ebx=0000273b ecx=fe510821 edx=00000000 > > > esi=00000006 edi=00098db6 ebp=00090000 esp=00000000 > > > cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 > > > cs:eip=f0 2b 92 00 00 00 00 bc-89 00 00 af f1 e6 f8 00 > > > 00 00 00 00 00 00 00 00-00 54 3d 00 00 00 00 00 > > > ss:esp=2b 00 00 01 1b f6 13 50-08 19 f6 f4 f7 f3 c3 f9 > > > 6f 91 6c 2c f8 ef 0d 6c-10 f2 7b 77 08 59 2e f9 > > > BTX halted > > > > > > This was with the HDD as ad0. I changed it to ad2 and used my > > > other drive with FreeBSD 4.10 as ad0 to see what was going on. > > > Here's the beef: > > > > Your BIOS is in lala land perhaps. Note that the stack pointer is 0, > > so it's hard to tell how it got into such a funk. I'm not sure how you > > can debug this, except perhaps to try turning off things like network > > cards as boot devices and turning off DMA mode in the BIOS for your > > hard drives. > > I got an error like this when I accidentally tried to use FreeBSD/amd64 on > an i386-only machine. That type of dump would have different instructions at cs:eip (probably an amd64-specific instruction). > Maybe the BIOS is broken, but the chance that using vmware instead of his > native hardware would produce the same error is low, isn't it? I don't know how vmware is implemented, but it would probably not have the same problem since it probably has a much simpler BIOS. -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.orgReceived on Mon Nov 22 2004 - 21:12:22 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:23 UTC