Re: IDE Card

[Thomas Dodd <ted cypress com>]

"Mugleston, Brad" wrote:
> 
> Mark, Richard and everyone else,
> 
> Thanks for the replies - we've established that the SCSI card I see under
> windows that I have my CD's connected to is the same device I see under
> Linux in the /proc/pci file.
> 
> Now how do I mount my CD's?   I made a directory called (cdu - for CD upper)
> and did a mount /dev/hd* /cdu and got an error (it was late last night and I
> didn't write it down, sorry -something like that device isn't there).  I
> tried all kinds of combinations to replace the * (c, c1, c2, d, d1, d2, b,
> b1, b2...) but I got the same error (no I didn't really use a *, just the
> replacements).


Did you load a driver/module for the addin card ?

/proc/pci is not well maintained, use lspci instead
both only show what the kernel sees on the PCI bus.
It says nothing about what drivers are being used.

check the output from dmesg or /var/log/messages for
the IDE detection. I get:

ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14
ide1 at 0x170-0x177, 0x376 on irq 15

They are also listed in /proc/ioports
and /proc/interrupts.

> > -----Original Message-----
> > From: redhat-install-list-admin redhat com


> > >       Vendor id=1103. Device id=4.

checking the PCI database for lspci,
/usr/share/pci.ids this is an HPT366
controler.

> > >   Bus  0, device  14, function  0:
> > >       Medium devsel.  IRQ 11.  Master Capable.  Latency=248.  Min
> > >       I/O at 0xdcd8 [0xdcd9].
> > >       I/O at 0xdcd0 [0xdcd1].
> > >       I/O at 0xd800 [0xd801].
> > >   Bus  0, device  14, function  1:
> > >       Medium devsel.  IRQ 11.  Master Capable.  Latency=248.  Min
> > >       I/O at 0xdcc8 [0xdcc9].
> > >       I/O at 0xdcd4 [0xdcd5].
> > >       I/O at 0xd400 [0xd401].


you should see ide? and ide? with a matching address on irq 11
in dmesg, /proc/ioports, and /proc/interrupts.

If not there is no driver for the devices, so you cannot access them.

The kernel from Red Hat might not have support for this card
either. Install the kernel-sources rpm (not src.rpm!)
and look at /usr/src/linux-2.4/configs/ for
the kernel you have installed. See if 
CONFIG_BLK_DEV_HTP366=y is there. If you see

#CONFIG_BLK_DEV_HTP366 is not set

Then you need to build a new kernel with support.
If you want to BOOT from a device on that disk
read /usr/src/linux-2.4/Configure.help
and search for HTP366 in the file.

	-Thomas