…is perhaps the least useful error message I’ve seen. Windows boot failures have obscure messages - “Invalid BOOT.INI”, “Cannot find NTLOADER” - but at least they’re unique enough not to crop up in ordinary conversation (and thus Search Engine Result Pages).
For the record, I was trying to install Fedora Core 6 on an Athlon64 single-core 3800-based system; ASUS M2NPV-VM Nvidia-based motherboard; Nvidia-7950 video card; single Western Digital SATA drive. It’s based off the Ars Technica Budget Buyer’s Guide for December 2006, with a couple of upgrades. The solution is not to install the Linux bootloader (”GRUB”) on the master boot record; instead, install it on the first sector of the boot drive. You may need to select an “Advanced Option” check box to see that option.
Currently, it’s installed and downloading some 230 updates to various packages. This introduces a problem I hadn’t thought about; since there’s no single standard Linux build, all of these packages need to explicitly state what code libraries (”Shared Objects” - DLLs in the Windows world) they require. That means that prior to installing those 230 updates the update manager has figure out what libraries are required, installed, and need to be downloaded and installed. That seems to take a while; I wonder if it deals with incompatible versions as well?
Post a Comment