dma can't be turned on

linoox · 07-22-2004, 02:22 PM

hi all,

having some problem here. I had just installed Slackware 10 using just CD1 - no gnome, no kde on an old laptop. Config as follows:
1) Satellite 330CDT
2) Pentium MMX 266Mhz
3) 4 GB harddisk space (couldn't remember exactly)
4) 64MB RAM

After default installation, I noticed that DMA was not turned on (alert message when booting up).

I did the following

Code:

hdparm -d1 /dev/hda

I got the following message

Code:

setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using _dma = 0 (off)

currently logged in as root.

Any idea? Please help..

auditek747 · 07-22-2004, 03:20 PM

Maybe it can't do it. What does "hdparm -i /dev/hda" say?

linoox · 07-22-2004, 03:33 PM

Here's what it says

Code:

Model=TOSHIBA MK4313MAT, FwRev=J2.12 C, SerialNo=40B70373A
Config={ Fixed }
RawCHS=8944/15/63,  TrkSize=0, SectSize=0, ECCbytes=46
BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=16
CurCHS=8944/15/63, CurSects=8452080, LBA=yes, LBAsects=8452080
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2
UDMA modes: udma0 udma1 udma2
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: device does not report version: 1 2 3 4

* signifies the current active mode

auditek747 · 07-22-2004, 03:44 PM

Don't know Bud,
Have you been able to use udma with this drive/mobo combination
before?

linoox · 07-22-2004, 04:04 PM

i'm not quite sure what you mean by drive/mobo? I tried a couple of linux distro on this laptop and I don't remember seeing that message. Then again, i never did check with hdparm command.

auditek747 · 07-22-2004, 09:11 PM

Perhaps support for your ide controller isn't built into the Slack kernel.

An "lspci" will tell you the chipset, for example:

/home/toadtoe# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
00:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
00:0d.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
00:10.0 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2)

My chipset is the Via VT82C586A.
Burried in my /boot/config I see the line:

CONFIG_BLK_DEV_VIA82CXXX=y

So support for these controllers is built in.

Just something to check.

linoox · 07-23-2004, 12:42 AM

no ide controller found when i ran lspci command. Only 6 items were displayed:

Host Bridge
VGA compatible controller
USB Controller
Communication controller
CardBus bridge (2 x entries)

i'm not very good with hardware eithers, especially what's inside an old laptop.

auditek747 · 07-23-2004, 12:01 PM

Well linoox,
I can only guess at this, but the only time I've seen "operation not permitted"
for setting UDMA is when the "ide bus master" was not supported in the kernel.
I think Toshiba chipsets are proprietary and they don't release info about them.

I hope I'm wrong here.

Anyway, keep asking around, some one may have a better answer.

Franklin · 07-23-2004, 11:01 PM

You may want to try a different kernel from the slack CD.

Intead of bare.i use the ide kernel or vice-versa.

linoox · 07-24-2004, 11:31 AM

i'll give it a try. Thank you all for the advice!

predrag · 07-24-2004, 12:26 PM

I have also had similar problems, then I compiled 2.6.7 and they were solved. Give it a try.

Ikebo · 08-06-2004, 11:42 AM

This problem has probably already been solved here and in other threads but I thought I'd say that I had the same problem when I tired to add support for my controller chipset as a module (2.6.7). Compiling it in the kernel fixed it.