>From: fedora-list-bounces@xxxxxxxxxx >[mailto:fedora-list-bounces@xxxxxxxxxx]On Behalf Of Dave Jones >Sent: Wednesday, December 14, 2005 10:28 AM >To: For users of Fedora Core releases >Subject: Re: GAH! Kernel release 2.6.14-1.1653_FC4 caused me problems! > > >On Wed, Dec 14, 2005 at 10:23:52AM -0800, Daniel B. Thurman wrote: > > > > Folks, > > > > I yum updated to kernel 2.6.14-1.1653_FC4, rebooted, and >was not able to > > continue because the error message says: > > > > Error 18: Selected cylinder exceeds maximum supported by BIOS > > Press any key to continue > > > > Selecting the same kernel repeats the error, so I had to >grub-select my > > previous version: 2.6.14-1.1644_FC4 in order to sucessfully boot. > > > > My BIOS and hardware is old (I have a VA Linux Systems 501) >and I may not > > have any BIOS upgrade options and I have updated to latest >BIOS this vendor > > supports. If I am wrong, please let me know. If I am not, >any suggestions are > > appreciated but suggestions to get a new computer is not an >option since I am > > too poor to do so :-( > >Your /boot partition extends past an area that the BIOS can read. >(Probably the ~500MB mark ?) >There's not many good options here. Your best bet is to reinstall and >create a smaller /boot that has all of its space guaranteed to be >in that low cylinder range. > > Dave > >-- I have everything installed in a single large partition. Why is it, that this was not a problem in the previous releases until now? Why the requirement that /boot be in it's own partition? This makes no real sense to me other than to protect partitions from one another or for performance concerns but if I choose to put everything in one partition, why not? Perhaps you are telling me that pervious releases just *happened* to work until the /boot files were no longer guaranteed to be in the lower partition space due to changes and/or kernel updates that it has creeped outside of the BIOS ability to read files beyond a certain size limitiation, i.e. the inodes are outside of it's bit-range? Thanks for responding, Dan -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.13/199 - Release Date: 12/13/2005
