Re: lilo problem with 2.2.4
H. Peter Anvin (hpa@transmeta.com)
24 Mar 1999 15:28:15 GMT
Followup to: <36F90032.99A1406B@trema.com>
By author: Gianpaolo Carraro <gianpaolo.carraro@trema.com>
In newsgroup: linux.dev.kernel
>
> Hi guys,
>
> I just upgraded my kernel from 2.0.36 to 2.2.4 (i386)
>
> As far as the kernel and modules are concerned everything
> seems fine (at least for now).
> The only problem I had is with lilo. With the new kernel it does
> not behave the same way.
>
> Here is what happened:
>
> I changed my /etc/lilo.conf file to set the new kernel as default
> and here is the msg I got:
>
> >bash# /sbin/lilo
> >Warning: device 0x0805 exceeds 1024 cylinder limit
> >geo_comp_addr: Cylinder number is too big (3085 > 1023)
>
> However, if I boot the system with the older kernel (2.0.36)
> lilo works fine.
>
> I'm not sure what is going on, I just wanted to let you know
> about this issue.
>
> By the way, I didn't try any other 2.2.x kernels,
> so I'm not sure whether it's 2.2.4 specific.
>
You have /boot on a partition that crosses the cylinder 1024
boundary. This is a no-no; as you have found out, each kernel may or
may not work depending on where it is on the disk.
The best solution is to make /boot a separate partition near the
beginning of the disk.
-hpa
--
"The user's computer downloads the ActiveX code and simulates a 'Blue
Screen' crash, a generally benign event most users are familiar with
and that would not necessarily arouse suspicions."
-- Security exploit description on http://www.zks.net/p3/how.asp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/