AMD 780G chipset major issues 3/3 (btx)
John Baldwin
jhb at freebsd.org
Wed Apr 15 05:38:52 PDT 2009
On Tuesday 14 April 2009 8:55:01 pm Diego Depaoli wrote:
> On Wed, Apr 15, 2009 at 2:23 AM, Jung-uk Kim <jkim at freebsd.org> wrote:
> >
> > That is embarrassing... I thought I had the realmode boot block but I
> > was wrong. I had a screwed-up bsdlabel from sysinstall at some
> > point. When I did 'bsdlabel -B', it failed to install the boot block
> > at all but I ignored the error message, I guess. :-(
>
> Unfortunately that doesn't solve for me.
> I have a drive (ad4, ad6)
> - ad4s1 -> windows
> - ad4s2 -> linux swap
> - ad4s3 -> linux
> - ad4s4 -> FreeBSD
> bootloader is managed through EasyBCD
> Not being an expert I gave
> bsdlabel -B ad4s4
> (is the right command?)
> but after that I get the same result
>
> int=0000000d err=00000000 efl=00030002 eip=000001e8
> eax=00000010 ebx=00000002 ecx=00009e42 edx=0009e7c8
> esi=000003f0 edi=0000036e ebp=000003a8 esp=00000368
> cs=cf00 ds=0040 es=1400 fs=0000 gs=0000 ss=9e42
> cs:eip=0f 22 c0 2e 0f 01 16 85-00 0f 20 c0 0c 01 0f 22
> c0 eb 00 b8 08 00 8e d8-8e c0 8e d0 66 2e a1 5c
> ss:esp=3f 00 c0 96 00 00 00 14-40 00 46 00 02 00 00 00
> f0 03 00 00 a8 03 00 00-94 03 00 00 00 00 00 00
This fault is with the old boot blocks still. 'bsdlabel -B ad4s4' should
update the boot blocks correctly. I'm not sure why you are still getting the
old code. Perhaps /boot/boot has not been updated?
--
John Baldwin
More information about the freebsd-current
mailing list