Date: Fri, 14 Sep 2001 14:03:46 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: Kent Stewart <kstewart@urx.com> Cc: rnordier@FreeBSD.org, msmith@freebsd.org, roam@ringlet.net, freebsd-hackers@freebsd.org Subject: Re: Does boot1 still have a > 1023 cyl limit? Message-ID: <XFMail.010914140346.jhb@FreeBSD.org> In-Reply-To: <3BA26FEB.D701D7EE@urx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14-Sep-01 Kent Stewart wrote: > > > John Baldwin wrote: >> >> On 14-Sep-01 Kent Stewart wrote: >> > >> > >> > rnordier@FreeBSD.org wrote: >> >> >> >> Kent Stewart wrote: >> >> >> >> > Mike Smith wrote: >> >> > > >> >> > > > So.. if I read you right, booting correctly for > 1024 cylinders >> >> > > > works >> >> > > > if boot0 knows about it. Isn't boot0 the one in the MBR, not in >> >> > > > the >> >> > > > fbsd >> >> > > > slice? Does this mean that boot1 and boot2 should work just fine >> >> > > > if >> >> > > > they >> >> > > > are loaded by another kind of MBR loader (say, Grub), and they find >> >> > > > out >> >> > > > that they are placed beyond the 1023th cylinder? >> >> > > >> >> > > This should work, yes. >> >> > >> >> > I tried this with a boot1 from FreeBSD 4.4-rc and get a BTX error. I >> >> > had to go back to the boot1 from 4.3 before I could boot. >> >> >> >> That could be serious. Can you post a brief description of your >> >> hardware, together with the BTX register dump if possible? boot1 was >> >> changed to address some problems with certain hardware, so it is >> >> important to know if other incompatibilities have been introduced. >> > >> > The hardware is Abit VP6 mb w/dual 866 coppermines & 256 MB of PC-133 >> > memory. Disk0 is a Maxtor 30 GB, disk1&2 are on the HPT-370 controller >> > and are also Maxtor 30 GB drives. The 2 HD's on the HPT-370 are >> > identical models. All are rated at ATA-100. The loader has been Win XP >> > Pro since beta2 and runs FreeBSD about half of the time. >> > >> > BTX - Register dump >> > >> > int=00000006 err=00000000 efl=00030216 eip=00000de7 >> > eax=00001d3a ebx=000030ff ecx=0000001f edx=000000ce >> > esi=00000001 edi=00000009 ebp=000003fe esp=000003b1 >> > cs=2364 ds=0000 es=0204 fs=0000 gs=0000 ss=9dc5 >> > cs:eip=0f 00 00 00 70 00 00 00-00 00 00 68 1e 00 00 00 >> > ss:esp=b9 0d 00 00 00 fe 03 c2-03 02 01 80 00 1f 00 01 >> > BTX halted >> >> 00000000 0F0000 sldt [bx+si] >> 00000003 007000 add [bx+si+0x0],dh >> 00000006 0000 add [bx+si],al >> 00000008 0000 add [bx+si],al >> 0000000A 00681E add [bx+si+0x1e],ch >> 0000000D 0000 add [bx+si],al >> >> That doesn't look to be very sane. >> >> Are you sure you haven't mixed an old version of boot2 with a new boot1 or >> vice >> versa? > > Yes, > > coral# mount_msdos /dev/ad0s1 /mnt > coral# cmp /mnt/boot1 /boot/boot1 > coral# > > They test identical. Boot1 was copied to bootsect.bsd, which is > referenced in boot.ini. Umm, ok. Did you do 'disklabel -B' to update the boot blocks on the disk (the boot blocks do _not_ live in the /boot files, they are part of the disklabel) when you updated the boot1 in bootsect.bsd? -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010914140346.jhb>