Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I would like to start by saying that I do NOT have that problem where I can't boot because of only a few of the letters in "LILO" producing an error message. My computer gets into GNOME fine. What happened is that I bought an old computer and installed Red Hat 7.1 The computer has a Pentium 166mhz, 96mb Ram, 3GB Western Digital hard drive. It had Windows 2000 in it and I did an fdisk and format with a Windows 95 startup disk with format file. Red Hat 7.1 comes with three installation options, Automatic Install, Disk Druid, or the Linux FDISK. I did not want to use the easier Auto install so I tried the FDISK and then the Disk Druid. Both produced a mismatch in the geometry. It is important to mention that both the Hard Disk documentation and the BIOS give the correct geometry. Only Linux is wrong. Cylinders and Heads were wrong but the Sectors were right. I ended up using the Auto install to see if it would correct the problem but installation ended correctly without letting me know what it detected. What command do I enter to see if now it is correct? I know it's probably still wrong. How do I know and what do I do to correct this problem? Did I have to do an fdisk /mbr with the Windows startup disk? How would I do that with Linux's fdisk?
Well, the command you gave me shows the wrong figures just as Linux showed during the attempts to install using Disk Druid and Linux FDISK. It is also wrong when I use the command:
fdisk/dev/hda now that it is installed and running.
I do get the correct C/H/S geometry with this command:
# /sbin/hdparm -i /dev/hda
So even though I'm getting one correct result, I'm gettin more incorrect results.
Someone mentioned that I should uninstall Linux and do an fdisk /mbr with a Windows startup disk since it had Windows on it before I did a regular windows fdisk and then a format. I did not use the /mbr when I did that, though.
One day after above message: Nevermind, I tried the /mbr thing and reinstalled Linux and it's still the same.
Last edited by manny dingo; 07-03-2001 at 06:06 PM.
The answer is no. Someone had some good ideas but they never came to a solution. I even asked Matt Welsh, the author of Running Linux and he said he had heard of the problem before and that it would cause me no problems and to just ignore it and keep moving forward with it. That's not exactly what I wanted to hear but it's better to know that than wonder if you're going to find trouble in the future because of that. For example, the person that gave me some input on that first told me that it did not cause a problem until he wanted to run both Windows and Linux on the same hard drive. Bye
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.