[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PIIX4 controller support on 2.0.x kernels vs 2.2.9



	Subject: re: PIIX4 controller support on 2.0.x kernels vs 2.2.9
	Date: Tue, Jun 01, 1999 at 08:50:00AM +1000

In reply to:debian

Quoting debian(debian@mail.fairfax.com.au):
> first an example of boot messages from dmesg output;
> 
> Kernel 2.0.34
> 
> ide: i82371 PIIX (Triton) on PCI bus 0 function 57
>     ide0: BM-DMA at 0xf000-0xf007
>     ide1: BM-DMA at 0xf008-0xf00f
> hda: Maxtor 90680D4, 6485MB w/256kB Cache, CHS=826/255/63, UDMA
> hdc: no response (status = 0xd0)
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Floppy drive(s): fd0 is 1.44M
> 
> 
> Now kernel 2.2.9 dmesg output;
> 
> PIIX4: IDE controller on PCI bus 00 dev 39
> PIIX4: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
>     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
> hda: Maxtor 90680D4, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: Maxtor 90680D4, 6485MB w/256kB Cache, CHS=826/255/63, UDMA
> Floppy drive(s): fd0 is 1.44M
> 
> 
> How do I get the 2.2.9 kernel to exactly see what my controller is, and I
> also have problems with hdc device (ATAPI CDROM) under 2.2.9 (ie not
> detected at all)
> 
> So strange... any ideas.. I will do more testing when I have time, but so
> far I don't see any support directly related to PIIX4 in the 2.2.9 make
> menuconfig screens.
> 
> 

In /usr/src/linux/Documentation/sgi-visws.txt There is some mention of
the PIIX4.  Other than that I don't know.  Have tried very hard to
stay away from Intel chipsets.

What does grep -i "ATAPI CDROM"  /usr/src/linux/.config say 

As I don't know what your level of expertise is I won't suggest
anything else until I get an answer.  Or you find the problem yourseld
and let us know.

HTH, YMMV, HAND



-- 
Micro Credo:
 Never trust a computer bigger than you can lift.
_______________________________________________________
Wayne T. Topa <wtopa@mindspring.com>


Reply to: