i have RH 9.0 running on very new hardware and have very slow hard
disk access due to not being able to enable DMA. someone has
suggested that my IDE chipset is not being recognized by the
2.4.20 series of kernels. below is the output of lspci; can
someone look at this and tell me what my IDE chipset may be so
that i could possibly find a kernel patch to apply so that this
IDE chipset will be recognized ?

thanks

PCI devices found:
Bus 0, device 0, function 0:
Host bridge: PCI device 8086:2584 (Intel Corp.) (rev 4).
Bus 0, device 1, function 0:
PCI bridge: PCI device 8086:2585 (Intel Corp.) (rev 4).
Master Capable. No bursts. Min Gnt=10.
Bus 0, device 28, function 0:
PCI bridge: PCI device 8086:2660 (Intel Corp.) (rev 3).
Master Capable. No bursts. Min Gnt=2.
Bus 0, device 28, function 1:
PCI bridge: PCI device 8086:2662 (Intel Corp.) (rev 3).
Master Capable. No bursts. Min Gnt=2.
Bus 0, device 29, function 0:
USB Controller: PCI device 8086:2658 (Intel Corp.) (rev 3).
IRQ 9.
I/O at 0xff80 [0xff9f].
Bus 0, device 29, function 1:
USB Controller: PCI device 8086:2659 (Intel Corp.) (rev 3).
IRQ 5.
I/O at 0xff60 [0xff7f].
Bus 0, device 29, function 2:
USB Controller: PCI device 8086:265a (Intel Corp.) (rev 3).
IRQ 3.
I/O at 0xff40 [0xff5f].
Bus 0, device 29, function 3:
USB Controller: PCI device 8086:265b (Intel Corp.) (rev 3).
IRQ 10.
I/O at 0xff20 [0xff3f].
Bus 0, device 29, function 7:
USB Controller: PCI device 8086:265c (Intel Corp.) (rev 3).
IRQ 9.
Non-prefetchable 32 bit memory at 0xffa80800 [0xffa80bff].
Bus 0, device 30, function 0:
PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 211).
Master Capable. No bursts. Min Gnt=2.
Bus 0, device 30, function 2:
Multimedia audio controller: PCI device 8086:266e (Intel Corp.) (rev 3).
IRQ 10.
I/O at 0xec00 [0xecff].
I/O at 0xe8c0 [0xe8ff].
Non-prefetchable 32 bit memory at 0xdffffa00 [0xdffffbff].
Non-prefetchable 32 bit memory at 0xdffff900 [0xdffff9ff].
Bus 0, device 31, function 0:
ISA bridge: PCI device 8086:2640 (Intel Corp.) (rev 3).
Bus 0, device 31, function 1:
IDE interface: PCI device 8086:266f (Intel Corp.) (rev 3).
IRQ 11.
I/O at 0xffa0 [0xffaf].
Bus 0, device 31, function 2:
Class 0106: PCI device 8086:2652 (Intel Corp.) (rev 3).
IRQ 5.
I/O at 0xfe00 [0xfe07].
I/O at 0xfe10 [0xfe13].
I/O at 0xfe20 [0xfe27].
I/O at 0xfe30 [0xfe33].
I/O at 0xfea0 [0xfeaf].
Non-prefetchable 32 bit memory at 0xdffffc00 [0xdfffffff].
Bus 0, device 31, function 3:
SMBus: PCI device 8086:266a (Intel Corp.) (rev 3).
IRQ 10.
I/O at 0xe8a0 [0xe8bf].
Bus 1, device 0, function 0:
VGA compatible controller: PCI device 10de:00fa (nVidia Corporation)
(rev 162).
IRQ 11.
Non-prefetchable 32 bit memory at 0xdd000000 [0xddffffff].
Prefetchable 32 bit memory at 0xc0000000 [0xcfffffff].
Non-prefetchable 32 bit memory at 0xde000000 [0xdeffffff].
Bus 2, device 0, function 0:
Ethernet controller: PCI device 14e4:1677 (Broadcom Corporation) (rev
1).
IRQ 11.
Non-prefetchable 64 bit memory at 0xdcff0000 [0xdcffffff].

metoo <cfdmanW@hotmail.com> wrote in
news:113js3ndvjeom22@corp.supernews.com:

> i have RH 9.0 running on very new hardware and have very slow hard
> disk access due to not being able to enable DMA. someone has
> suggested that my IDE chipset is not being recognized by the
> 2.4.20 series of kernels. below is the output of lspci; can
> someone look at this and tell me what my IDE chipset may be so
> that i could possibly find a kernel patch to apply so that this
> IDE chipset will be recognized ?
>
> thanks
>
> PCI devices found:
> Bus 0, device 0, function 0:
> Host bridge: PCI device 8086:2584 (Intel Corp.) (rev 4).
>(snip)

All this tells me is that you haven't taken those nice PCI device
<vendor>:<device> numbers and and looked them up in a current pci.ids file.
If that fails, and it shouldn't in this case, opening up the machine and
googling the numbers doesn't get you a chipset family, try watching the
system messages before you boot into the OS. The boottime messages or
dmesg should give you an idea what that ide/sata chipset is. Please do
your footwork and follow up on what you have rather than throw your hands
up because you haven't bothered to use available resources.

On second thought, I'll give you a hint. The relevant bits are
PCI device 8086:266f (Intel Corp.) (rev 3).
PCI device 8086:2652 (Intel Corp.) (rev 3).

Also, you might consider a newer kernel in the 2.4 series or move to 2.6.



--
There is nothing life threatening about man pages.
IRS forms, however, are a different story.

metoo wrote:

> i have RH 9.0 running on very new hardware and have very slow hard
> disk access due to not being able to enable DMA. someone has
> suggested that my IDE chipset is not being recognized by the
> 2.4.20 series of kernels. below is the output of lspci; can
> someone look at this and tell me what my IDE chipset may be so
> that i could possibly find a kernel patch to apply so that this
> IDE chipset will be recognized ?
>
> thanks

That is a problem that affects all RH versions including Fedora up to Core
3. Of all my boxes I had that problem only on a Dell Inspiron 8200. On RH9
you may try to kill the automounter (sometimes it works). On Fedora switch
to runlevel 3. This issue has been fixed on EzPlanet One release 2.0
(http://www.ezplanetone.com) that is based partly on Fedora 3, 4 and RH
Enterprise 4. It will look familiar, though bringing several improvements
to the classic Red Hat/Fedora idiosyncrasies.

JB

On Thu, 17 Mar 2005, metoo wrote:

> i have RH 9.0 running on very new hardware and have very slow hard
> disk access due to not being able to enable DMA.

does "hdparm /dev/hda" show using_dma as off? Does "hdparm -d 1 /dev/hda"
turn it on?

--
Yves Bellefeuille
<yan@storm.ca>

metoo wrote:
> i have RH 9.0 running on very new hardware and have very slow hard
> disk access due to not being able to enable DMA. someone has
> suggested that my IDE chipset is not being recognized by the
> 2.4.20 series of kernels. below is the output of lspci; can
> someone look at this and tell me what my IDE chipset may be so
> that i could possibly find a kernel patch to apply so that this
> IDE chipset will be recognized ?

An update to a more recent kernel may be in order, it's hard for an
ancient kernel
Nov 28 2002 ChangeLog-2.4.20
to recognize a chipset any newer than the kernel. The clarvoyance option
wasn't added until 2.4.36. Update to something nice and new and try
again. If 2.4.29 doesn't work post the dmesg output, snipped if it's
really huge.

--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me