Date: Sat, 18 Nov 1995 08:36:59 +1100 From: Bruce Evans <bde@zeta.org.au> To: julian@ref.tfs.com, nbc@vulture.dmem.strath.ac.uk Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: Re IDE/eIDE issues Message-ID: <199511172136.IAA24331@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>>No, this is where you are wrong..
>>it would work
>>as long as the 'a' subdivision of the FBSD slice was below Cyl 1024
>>the rest doesn't matter..
>Either my computer is a fussy bugger or I took too much LDS in the seventies ;-)I tried it; it seems a fairly obvious thing to do, after all, and it did not
>work. I recall a boot message saying something like "partition is out of
>reach of BIOS", whereas if it is completely out of reach of the BIOS
>you get a "missing operating system message", or something like that.
That's interesting. The -current boot loader contains no such message.
The -stable boot loader should be identical with the current one. The
2.0.5 boot loader does contain such a message, and has a stricter check:
2.0.5: the whole boot partition must be below cylinder 1024
-current: the kernel and all metadata pointing to it must be below
cylinder 1024 (but don't configure boot partitions that
don't lie below cylinder 1024, because you have little
control over where the kernel and its metadata gets
written). The boot partition is normally the 'a' partition.
Please report literal error messages in bug reports, not "something like"
them.
>Either way, it most definately utterly sure-as-the-sun-rises-in-the-morning
>did not work. Perhaps having two other OS's on the disk confused the issue;
Perhaps your boot partition is too large.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511172136.IAA24331>