Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've recently purchased a Dell Dimension E520 (Intel Core Duo 2 @1.86MHz, 1024MB DDR2) and I've installed an additional harddisk (WD 250GB, SATA) to install Fedora Core 6 Linux on. Installation went fine, however, I don't see the GRUB bootloader which should have been installed on /dev/sda. In stead, the machine plainly boots Windows XP MCE.
This particular model only has SATA interfaces available. I haven't changed any of the BIOS settings regarding this, since this is highly recommended unless you *really* know what you're doing. For some reason, Dell has enabled the RAID settings (which I don't use) and I don't want to change this. Who knows what might happen if I do...
Has anyone seen this problem before? If so, what's the solution? Any pointers would be greatly appreciated!
the installation of the bootloader must have failed.
Honestly, I know its the "older" one and all that, but I've NEVER had lilo fail on me. If it isn't going to work, it tells me when I run /sbin/lilo. Look into it.
I've fixed it this way:
I've swapped the Windows harddisk and the Linux harddisk (Linux is now /dev/sda on SATA1, Windows is now /dev/sdb on SATA4), so it successfully boots GRUB from the Linux partition. In the grub.conf I have a section for Windows and in it, I swap the partitions of Windows and Linux in order to get Windows at (hd0,0):
title Windows XP MCE
map (hd0,0) (hd1,1)
map (hd1,1) (hd0,0)
(hd1,1) is naturally my Linux partition. This way, Windows will boot properly and it will see the second drive (/dev/sdb in Linux) as the first one (C: in Windows).
could you be a little more specific about the error message you get?
With respect to the cables: I've physically swapped them. I believe the harddisk is initially connected to SATA1 (the DVD-drive to SATA2). At first, I installed my additional harddisk on SATA4, but then I got all the errors from GRUB. So, I simply swapped the cables so that my Linux drive is on SATA1, my (original) Windows XP drive is on SATA4 and I added the swap lines in my grub.conf (as I posted previously). Please turn to the GRUB documentation for details about this.