Hi!
I have a MSI KT3Ultra2 Motherboard with a VT8235 southbridge. I'm currently
running kernel 2.4.19 - unfortunately it doesn't detect the southbridge,
so I cannot enable dma.
I tried the patch from Vojtech Pavlik (via82cxxx), but then it hangs at
boot:
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0x00
hdc: drive not ready for command
hdc: ATAPI reset timed-out, status=0x80
hdd: DMA disabled
ide1: reset: success
hdc: status timeout: status=0x80 { Busy }
hdc: status timeout: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: ATAPI reset timed-out, status=0x80
ide1: reset: success
hdc: status timeout: status=0x80 { Busy }
hdc: status timeout: error=0x01IllegalLengthIndication
end_request: I/O error, dev hdc, sector 0
hdc: drive not ready for command
I tried the last 2.5.x kernels and today the 2.4.20, everytime the same
problem. 2.4.19 boots just fine, but without dma :-(
Btw: hdc ist my dvd drive:
starbase:/# cat proc/ide/hdc/model
TOSHIBA DVD-ROM SD-M1302
starbase:/#
Any hints? It's a real pain to work without dma....
Thanks,
Patrick
On Sat, 2002-11-30 at 00:29, Patrick Petermair wrote:
> Hi!
>
> I have a MSI KT3Ultra2 Motherboard with a VT8235 southbridge. I'm currently
> running kernel 2.4.19 - unfortunately it doesn't detect the southbridge,
> so I cannot enable dma.
> I tried the patch from Vojtech Pavlik (via82cxxx), but then it hangs at
> boot:
>
Try the -ac tree firstly
Alan Cox:
> On Sat, 2002-11-30 at 00:29, Patrick Petermair wrote:
> > Hi!
> >
> > I have a MSI KT3Ultra2 Motherboard with a VT8235 southbridge. I'm
> > currently running kernel 2.4.19 - unfortunately it doesn't detect the
> > southbridge, so I cannot enable dma.
> > I tried the patch from Vojtech Pavlik (via82cxxx), but then it hangs
> > at boot:
>
> Try the -ac tree firstly
Thanks Alan, now dma works perfect!
How come this code isn't in the official 2.4.20 kernel?
The only strange thing now is that uname doesn't know my cpu:
starbase:/# uname -a
Linux starbase 2.4.20-ac1 #1 Sam Nov 30 18:43:15 CET 2002 i686 unknown
unknown GNU/Linux
starbase:/#
But it gets recognized during boot:
starbase:/# dmesg | grep -i AMD
CPU: AMD Athlon(tm) XP 2200+ stepping 00
starbase:/#
starbase:/# cat /proc/cpuinfo | grep -i AMD
vendor_id : AuthenticAMD
model name : AMD Athlon(tm) XP 2200+
starbase:/#
But hey, I can live with that - I have dma now :-)
Just curious, what's causing this.
Thanks so much...
Patrick
commence Patrick Petermair quotation:
> Alan Cox:
>>
>> Try the -ac tree firstly
>
> Thanks Alan, now dma works perfect!
> How come this code isn't in the official 2.4.20 kernel?
>
> The only strange thing now is that uname doesn't know my cpu:
>
> starbase:/# uname -a
> Linux starbase 2.4.20-ac1 #1 Sam Nov 30 18:43:15 CET 2002 i686 unknown unknown GNU/Linux
Are you running Debian unstable, and did you recently dist-upgrade?
The changes to coreutils that display CPU information in place of
"unknown unknown" were reverted in coreutils 4.5.3-1.
--
/ |
[|] Sean Neakums | Questions are a burden to others;
[|] <[email protected]> | answers a prison for oneself.
\ |
Sean Neakums:
> Are you running Debian unstable, and did you recently dist-upgrade?
> The changes to coreutils that display CPU information in place of
> "unknown unknown" were reverted in coreutils 4.5.3-1.
Yup, Debian unstable...and yup, did a upgrade last night.
Thanks.
Patrick
On Sat, 2002-11-30 at 21:27, Patrick Petermair wrote:
> > Try the -ac tree firstly
>
> Thanks Alan, now dma works perfect!
> How come this code isn't in the official 2.4.20 kernel?
Because its still getting a final polish - with luck it will be in
2.4.21
> > > Try the -ac tree firstly
> >
> > Thanks Alan, now dma works perfect!
> > How come this code isn't in the official 2.4.20 kernel?
>
> Because its still getting a final polish - with luck it will be in
> 2.4.21
I'm still having problems with dma on the secondary channel of my
PDC20268. Channel 1 is ok.
# hdparm -Iv /dev/hdg| grep '*u'
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
# hdparm -X68 /dev/hdg
/dev/hdg:
setting xfermode to 68 (UltraDMA mode4)
(no errors logged)
# hdparm -Iv /dev/hdg| grep '*u'
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
There's no such problem w/ 2.4.20 vanilla.
--
Tomas Szepe <[email protected]>