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.
Hello. I'm having trouble getting a hard drive detected. I installed mandrake the other day and went through the learning curve of changing from windows to linux. I'm still trying to get to my feet in respect to handling it.
I've got a gigabyte 7vrxp rev2.0 board with the promise 20276 raid/ide controller. I set it to normal ata in bios, come into mandrake 9.1 and go into harddrake. It shows it up in other devices, as just 20276 and i cant do anything more with it.
How am i ment to access the other hard drive.
Thanks in advance,
Last edited by thepointer; 06-06-2003 at 09:52 PM.
And if the kernel saw the controller, it should output something like this:
fin@orwell:/home$ dmesg | grep 202
PDC20267: IDE controller on PCI bus 00 dev 68
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
[brad@thor brad]$ dmesg | grep 202
PDC20276: IDE controller at PCI slot 00:0f.0
PDC20276: chipset revision 1
PDC20276: not 100% native mode: will probe irqs later
PDC20276: neither IDE port enabled (BIOS)
It says that, makes me think theres something in the bios i have to change, but i 've looked through, and nothing obvious stands out, it shouldnt Have to, because in windows it picks it up straight away, which makes me think its a driver problem or maybe something with the kernel.
Would you mind explaining that command? I usualy remember things better if i know how they work.
Nah, the Promise series doesn't load the BIOS for the card unless there's something hooked up to the card itself. Although there is sometimes an option in the machine BIOS to load the Promise BIOS, it gets kinda silly.
The command, no problem!
"dmesg" is the kernel ring buffer which is a meaningless way of saying its a record of the kernel loading support for everything in order as it loaded, the first thing is the RAM, then the chip, then the PCI bus, etc... Its the first stop for hardware issues. "dmesg" is also only a few hundred lines long so if you get something that spams dmesg with a lot of errors or just debugging info, the top gets pushed out. No matter, all of the same info is logged permanently to /var/log/messages also, for your perusing pleasure.
The pipe: "|" is used to take the output of one command and send it to the next, in the above case, grep.
grep is "get regular expression", the quintensential scripting program from the damn of unix time. It has about two dozen options or so. The argument to it of "202" was what I was telling it to return in its search, any line with "202" in it. Check the man page on grep, its the swiss army knif of search tools.
Also, to get a good look at dmesg: dmesg | less (that'll give it to you a page at a time instead of in one big wham.
I'm never a big fan of using books to learn things, but there's one that rocks and by the time your halfway through it you're ahead of it. That's how good of a book it is: "Running Linux" Matt Welsch.
All well and good, thanks for the command info, but where does that leave me in respect to me being able to access the hard drive i've attached. It detects it when it scans through the raid/ide during bootup (bios) but i'm still lost as to what I'm meant to do now. The raid/ide controller is onboard.
But thanks for the nice explanation, i might check out that book if i get the chance.
PS it detects the hard drive thats connected when it runs through its Detecting Devices, or something. (in the promise detecting part)
Last edited by thepointer; 06-03-2003 at 03:14 AM.
Yes, but it Doesnt detect it. When the second ata controller (raid/ata) goes through detecting devices, it finds the hard drive, and says Master ide enabled, or something to that effect, saying its enabled it. Then in mandrake it still says that the ata/raid isnt started/enabled.
I'm using Slackware 10.1 (Linux kernel 2.4.29) on an MSI 845E Max 2 board with an onboard Promise FastTrak RAID controller also based on the PDC20276, and I have the same:
PDC20276: neither IDE port enabled (BIOS)
problem. Has anyone found a way around this problem already?
The readme on the linux driver download for the FastTrak TX2000 (which I believe is also PDC20276 based) from the Promise site mentions a probable fix:
Linux Kernels 2.4.x misidentify Promise ATA-RAID controllers as simple
IDE controllers. This results in the built-in Linux IDE driver trying to
handle the controller, which can prevent the proper FastTrak ATA RAID driver
being loaded. This status is referred to as "IDE issue".
If you are using Linux kernel 2.4.x, follow installation instructions
a.) through c.).
NOTE: All IDE channels except the first and second one are disabled for the
"IDE issue". It can be enable by removing 'ide2=0 ide3=0 ide4=0 ide5=0
ide6=0 ide7=0 ide8=0 ide9=0' in /etc/lilo.conf or /boot/grub/menu.lst.
a.) "linux ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0
ide5=0 ide6=0 ide7=0 ide8=0 ide9=0"
b.) If using lilo:
append="ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0
ide4=0 ide5=0 ide6=0 ide7=0 ide8=0 ide9=0"
c.) If using grub:
title Red Hat Linux (2.4.20)
kernel /vmlinuz-2.4.20 ro root=/dev/sda1 ide0=0x1f0,0x3f6,14
ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0 ide5=0 ide6=0 ide7=0 ide8=0 ide9=0