IDE-CD and VT8235 issue!!!
Hi, I have this chip on a MSI KT4 Ultra (KT400 and VT8235) and an
Athlon 2400+.
I have noe the kernel 2.4.19 and all works fine, but 2.4.19 don't support this chip (so no DMA & Co) and I've decided to upgrade to 2.4.20 to get it working. I've compiled in the Debian Way ( kernel-package) and installed the kernel, then I've rebooted it.
During the startup progress it have initialized the HDs fine , but when he had reached the first CDROM ( a NEC DVD READER) it locked up with this message:
hdc: DMA disabled
hdc: drive is not ready for command
ide1: reset: success!
and it repeats this messages in an infinite loop , I don't know how to solve this , there isn't a patch or something else?
The kernel that I've tried (without success) are:
kernel 2.4.20 (original)
kernel 2.4.20 -ac2
kernel-source-2.4.20 package by debian + patches
kernel-2.5.50-ac1(doesen't boot)
kernel-2.5.53 (doesen't compiles)
Please help
Thank u
Byez
Hi!
Same problem here. I have addressed this issue several times...so far no solution.
My specs:
MSI KT3 Ultra2 (VT8235)
TOSHIBA DVD-ROM SD-M1302
YAMAHA CRW8424E
Kernel 2.4.19:
The one I'm currently using. It doesn't detect the VT8235 and therefore I have no dma. But I can access/mount my DVD without a problem.
Kernel 2.4.20:
Detects the VT8235 at boot but hangs with my DVD Rom (hdc) --> doesn't boot. I have posted my problem here an Alan Cox suggested that I should try the -ac tree.
Kernel 2.4.20-ac2:
Some improvements - It detects the VT8235 at boot, also my DVD and CDRW. It boots fine and I have DMA on all my discs. But as soon as I try to mount a CD/DVD (mount /cdrom) the system hangs and I get this:
hdc: status timeout: status=0xd1 { Busy }
hdc: status timeout: error=0x60LastFailedSense 0x06
hdc: DMA disabled
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: ATAPI reset timed-out, status=0xd1
ide1: reset: success
hdc: status timeout: status=0x80 { Busy }
hdc: status timeout: error=0x01IllegalLengthIndicationend_request: I/O error, dev 16:00 (hdc), sector 0
hdc: status timeout: status=0xd0 { Busy }
and so on...
My guess is the DVD-drive. I know many people with the same southbridge (VT8235), who have dma since 2.4.20 an no problem at all at boot-time or mounting a CD/DVD.
Any hints?
Patrick
Quoted 39 lines · Patrick Petermair
Hi!
Same problem here. I have addressed this issue several times...so far no solution.
My specs:
MSI KT3 Ultra2 (VT8235)
TOSHIBA DVD-ROM SD-M1302
YAMAHA CRW8424EKernel 2.4.19:
The one I'm currently using. It doesn't detect the VT8235 and therefore I have no dma. But I can access/mount my DVD without a problem.Kernel 2.4.20:
Detects the VT8235 at boot but hangs with my DVD Rom (hdc) --> doesn't boot. I have posted my problem here an Alan Cox suggested that I should try the -ac tree.Kernel 2.4.20-ac2:
Some improvements - It detects the VT8235 at boot, also my DVD and CDRW. It boots fine and I have DMA on all my discs. But as soon as I try to mount a CD/DVD (mount /cdrom) the system hangs and I get this:hdc: status timeout: status=0xd1 { Busy }
hdc: status timeout: error=0x60LastFailedSense0x06
hdc: DMA disabled
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: ATAPI reset timed-out, status=0xd1
ide1: reset: success
hdc: status timeout: status=0x80 { Busy }
hdc: status timeout: error=0x01IllegalLengthIndicationend_request: I/O error, dev 16:00 (hdc), sector 0
hdc: status timeout: status=0xd0 { Busy }and so on...
My guess is the DVD-drive. I know many people with the same southbridge (VT8235), who have dma since 2.4.20 an no problem at all at boot-time or mounting a CD/DVD.
Any hints?
Quoted 10 lines
Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Please, anyone help us, I can't live with a 6 MB HD bandwith!!!:-D
Ciao
Here the "kern.log" file in the loading of the ide support, so you can examine better the problem, Thank you very much, Bye
PS= The load of ide-cd is at the end, because I've load it after the system start.
Dec 11 00:05:36 valinor kernel: klogd 1.4.1#11, log source = /proc/kmsg started. Dec 11 00:05:36 valinor kernel: Inspecting /boot/System.map-2.4.20 Dec 11 00:05:36 valinor kernel: Loaded 14676 symbols from /boot/System.map-2.4.20. Dec 11 00:05:36 valinor kernel: Symbols match kernel version 2.4.20. Dec 11 00:05:36 valinor kernel: Loaded 72 symbols from 4 modules. Dec 11 00:05:36 valinor kernel: Linux version 2.4.20 (root@valinor) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Tue Dec 10 23:56:37 CET 2002 Dec 11 00:05:36 valinor kernel: BIOS-provided physical RAM map: Dec 11 00:05:36 valinor kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Dec 11 00:05:36 valinor kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Dec 11 00:05:36 valinor kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Dec 11 00:05:36 valinor kernel: BIOS-e820: 0000000000100000 - 000000001fff0000 (usable) Dec 11 00:05:36 valinor kernel: BIOS-e820: 000000001fff0000 - 000000001fff8000 (ACPI data) Dec 11 00:05:36 valinor kernel: BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS) Dec 11 00:05:36 valinor kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) Dec 11 00:05:36 valinor kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) Dec 11 00:05:36 valinor kernel: BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) Dec 11 00:05:36 valinor kernel: 511MB LOWMEM available. Dec 11 00:05:36 valinor kernel: On node 0 totalpages: 131056 Dec 11 00:05:36 valinor kernel: zone(0): 4096 pages. Dec 11 00:05:36 valinor kernel: zone(1): 126960 pages. Dec 11 00:05:36 valinor kernel: zone(2): 0 pages. Dec 11 00:05:36 valinor kernel: Kernel command line: auto BOOT_IMAGE=Linux ro root=305 video=vesa:ywrap,mtrr Dec 11 00:05:36 valinor kernel: Initializing CPU#0 Dec 11 00:05:36 valinor kernel: Detected 2255.176 MHz processor. Dec 11 00:05:36 valinor kernel: Console: colour dummy device 80x25 Dec 11 00:05:36 valinor kernel: Calibrating delay loop... 4495.76 BogoMIPS Dec 11 00:05:36 valinor kernel: Memory: 516504k/524224k available (990k kernel code, 7332k reserved, 377k data, 80k init, 0k highmem) Dec 11 00:05:36 valinor kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Dec 11 00:05:36 valinor kernel: Inode cache hash table entries: 32768 (order: 6, 262144 bytes) Dec 11 00:05:36 valinor kernel: Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) Dec 11 00:05:36 valinor kernel: Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Dec 11 00:05:36 valinor kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Dec 11 00:05:36 valinor kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) Dec 11 00:05:36 valinor kernel: CPU: L2 Cache: 256K (64 bytes/line) Dec 11 00:05:36 valinor kernel: Intel machine check architecture supported. Dec 11 00:05:36 valinor kernel: Intel machine check reporting enabled on CPU#0. Dec 11 00:05:36 valinor kernel: CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000 Dec 11 00:05:36 valinor kernel: CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000 Dec 11 00:05:36 valinor kernel: CPU: AMD Athlon(tm) XP 2400+ stepping 01 Dec 11 00:05:36 valinor kernel: Enabling fast FPU save and restore... done. Dec 11 00:05:36 valinor kernel: Enabling unmasked SIMD FPU exception support... done. Dec 11 00:05:36 valinor kernel: Checking 'hlt' instruction... OK. Dec 11 00:05:36 valinor kernel: POSIX conformance testing by UNIFIX Dec 11 00:05:36 valinor kernel: mtrr: v1.40 (20010327) Richard Gooch ([email protected]) Dec 11 00:05:36 valinor kernel: mtrr: detected mtrr type: Intel Dec 11 00:05:36 valinor kernel: PCI: PCI BIOS revision 2.10 entry at 0xfdaf1, last bus=1 Dec 11 00:05:36 valinor kernel: PCI: Using configuration type 1 Dec 11 00:05:36 valinor kernel: PCI: Probing PCI hardware Dec 11 00:05:36 valinor kernel: PCI: Using IRQ router default [1106/3177] at 00:11.0 Dec 11 00:05:36 valinor kernel: PCI: Hardcoded IRQ 14 for device 00:11.1 Dec 11 00:05:36 valinor kernel: Linux NET4.0 for Linux 2.4 Dec 11 00:05:36 valinor kernel: Based upon Swansea University Computer Society NET3.039 Dec 11 00:05:36 valinor kernel: Initializing RT netlink socket Dec 11 00:05:36 valinor kernel: Starting kswapd Dec 11 00:05:36 valinor kernel: devfs: v1.12c (20020818) Richard Gooch ([email protected]) Dec 11 00:05:36 valinor kernel: devfs: boot_options: 0x1 Dec 11 00:05:36 valinor kernel: vesafb: framebuffer at 0xd8000000, mapped to 0xe0800000, size 65536k Dec 11 00:05:36 valinor kernel: vesafb: mode is 1024x768x32, linelength=4096, pages=1 Dec 11 00:05:36 valinor kernel: vesafb: protected mode interface info at c000:b7d0 Dec 11 00:05:36 valinor kernel: vesafb: pmi: set display start = c00cb815, set palette = c00cb89a Dec 11 00:05:36 valinor kernel: vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da Dec 11 00:05:36 valinor kernel: vesafb: scrolling: ywrap using protected mode interface, yres_virtual=16384 Dec 11 00:05:36 valinor kernel: vesafb: directcolor: size=8:8:8:8, shift=24:16:8:0 Dec 11 00:05:36 valinor kernel: Console: switching to colour frame buffer device 128x48 Dec 11 00:05:36 valinor kernel: fb0: VESA VGA frame buffer device Dec 11 00:05:36 valinor kernel: pty: 256 Unix98 ptys configured Dec 11 00:05:36 valinor kernel: Real Time Clock Driver v1.10e Dec 11 00:05:36 valinor kernel: Uniform Multi-Platform E-IDE driver Revision: 6.31 Dec 11 00:05:36 valinor kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Dec 11 00:05:36 valinor kernel: VP_IDE: IDE controller on PCI bus 00 dev 89 Dec 11 00:05:36 valinor kernel: PCI: Hardcoded IRQ 14 for device 00:11.1 Dec 11 00:05:36 valinor kernel: VP_IDE: chipset revision 6 Dec 11 00:05:36 valinor kernel: VP_IDE: not 100%% native mode: will probe irqs later Dec 11 00:05:36 valinor kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Dec 11 00:05:36 valinor kernel: VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1 Dec 11 00:05:36 valinor kernel: ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:DMA Dec 11 00:05:36 valinor kernel: ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA Dec 11 00:05:36 valinor kernel: hda: QUANTUM FIREBALLP AS30.0, ATA DISK drive Dec 11 00:05:36 valinor kernel: hdb: MAXTOR 6L060J3, ATA DISK drive Dec 11 00:05:36 valinor kernel: hdc: _NEC DV-5800A, ATAPI CD/DVD-ROM drive Dec 11 00:05:36 valinor kernel: hdd: PCRW804, ATAPI CD/DVD-ROM drive Dec 11 00:05:36 valinor kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Dec 11 00:05:36 valinor kernel: ide1 at 0x170-0x177,0x376 on irq 15 Dec 11 00:05:36 valinor kernel: blk: queue c0293364, I/O limit 4095Mb (mask 0xffffffff) Dec 11 00:05:36 valinor kernel: hda: 58633344 sectors (30020 MB) w/1902KiB Cache, CHS=3649/255/63, UDMA(100) Dec 11 00:05:36 valinor kernel: blk: queue c02934b0, I/O limit 4095Mb (mask 0xffffffff) Dec 11 00:05:36 valinor kernel: hdb: 117266688 sectors (60041 MB) w/1819KiB Cache, CHS=7299/255/63, UDMA(133) Dec 11 00:05:36 valinor kernel: Partition check: Dec 11 00:05:36 valinor kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 p6 p7 p8 > Dec 11 00:05:36 valinor kernel: /dev/ide/host0/bus0/target1/lun0: p1 p2 < p5 > p3 Dec 11 00:05:36 valinor kernel: NET4: Linux TCP/IP 1.0 for NET4.0 Dec 11 00:05:36 valinor kernel: IP Protocols: ICMP, UDP, TCP, IGMP Dec 11 00:05:36 valinor kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes Dec 11 00:05:36 valinor kernel: TCP: Hash tables configured (established 32768 bind 32768) Dec 11 00:05:36 valinor kernel: reiserfs: checking transaction log (device 03:05) ... Dec 11 00:05:36 valinor kernel: Using r5 hash to sort names Dec 11 00:05:36 valinor kernel: ReiserFS version 3.6.25 Dec 11 00:05:36 valinor kernel: VFS: Mounted root (reiserfs filesystem) readonly. Dec 11 00:05:36 valinor kernel: Mounted devfs on /dev Dec 11 00:05:36 valinor kernel: Freeing unused kernel memory: 80k freed Dec 11 00:05:36 valinor kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Dec 11 00:05:36 valinor kernel: Adding Swap: 506036k swap-space (priority -1) Dec 11 00:05:36 valinor kernel: Adding Swap: 506036k swap-space (priority -2) Dec 11 00:05:36 valinor kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled Dec 11 00:05:36 valinor kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A Dec 11 00:05:36 valinor kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A Dec 11 00:05:36 valinor kernel: reiserfs: checking transaction log (device 03:01) ... Dec 11 00:05:36 valinor kernel: Using r5 hash to sort names Dec 11 00:05:36 valinor kernel: ReiserFS version 3.6.25 Dec 11 00:05:36 valinor kernel: reiserfs: checking transaction log (device 03:06) ... Dec 11 00:05:36 valinor kernel: Using r5 hash to sort names Dec 11 00:05:36 valinor kernel: ReiserFS version 3.6.25 Dec 11 00:05:36 valinor kernel: reiserfs: checking transaction log (device 03:07) ... Dec 11 00:05:36 valinor kernel: Using r5 hash to sort names Dec 11 00:05:36 valinor kernel: ReiserFS version 3.6.25 Dec 11 00:05:36 valinor kernel: reiserfs: checking transaction log (device 03:08) ... Dec 11 00:05:36 valinor kernel: Using r5 hash to sort names Dec 11 00:05:36 valinor kernel: ReiserFS version 3.6.25 Dec 11 00:05:36 valinor kernel: Journalled Block Device driver loaded Dec 11 00:05:36 valinor kernel: kjournald starting. Commit interval 5 seconds Dec 11 00:05:36 valinor kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,67), internal journal Dec 11 00:05:36 valinor kernel: EXT3-fs: mounted filesystem with ordered data mode. Dec 11 00:05:36 valinor kernel: kjournald starting. Commit interval 5 seconds Dec 11 00:05:36 valinor kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,69), internal journal Dec 11 00:05:36 valinor kernel: EXT3-fs: mounted filesystem with ordered data mode. Dec 11 00:05:51 valinor kernel: SCSI subsystem driver Revision: 1.00 Dec 11 00:05:56 valinor kernel: hdc: status timeout: status=0xd0 { Busy } Dec 11 00:05:56 valinor kernel: hdc: DMA disabled Dec 11 00:05:56 valinor kernel: hdc: drive not ready for command Dec 11 00:06:26 valinor kernel: hdc: ATAPI reset timed-out, status=0x80 Dec 11 00:06:31 valinor kernel: ide1: reset: success Dec 11 00:06:31 valinor kernel: hdc: status timeout: status=0x80 { Busy } Dec 11 00:06:31 valinor kernel: hdc: drive not ready for command Dec 11 00:06:43 valinor kernel: Kernel logging (proc) stopped. Dec 11 00:06:43 valinor kernel: Kernel log daemon terminating.
Quoted 21 lines · AnonimoVeneziano
Quoted 19 lines · Patrick Petermair
Hi!
Same problem here. I have addressed this issue several times...so far no solution.
My specs:
MSI KT3 Ultra2 (VT8235)
TOSHIBA DVD-ROM SD-M1302
YAMAHA CRW8424EKernel 2.4.19:
The one I'm currently using. It doesn't detect the VT8235 and therefore I have no dma. But I can access/mount my DVD without a problem.Kernel 2.4.20:
Detects the VT8235 at boot but hangs with my DVD Rom (hdc) --> doesn't boot. I have posted my problem here an Alan Cox suggested that I should try the -ac tree.
Quoted 7 lines
Quoted 6 lines
Kernel 2.4.20-ac2:
Some improvements - It detects the VT8235 at boot, also my DVD and CDRW. It boots fine and I have DMA on all my discs. But as soon as I try to mount a CD/DVD (mount /cdrom) the system hangs and I get this:Please, anyone help us, I can't live with a 6 MB HD bandwith!!!:-D
You're not alone with this problem. I suspect some fishy stuff in the vt8235, because the driver programs it exactly the same as vt8233a, but while the vt8233a doesn't seem to have problems with DVDs and CDs, the vt8235 fails for many people.
It might be some new DVD drive, though.
Can you send me 'hdparm -i' of the drive?
I'll try to make a patch to circumvent the problem ...
Thanks.
Signature · 2 lines
Vojtech Pavlik SuSE Labs
Quoted 38 lines · Vojtech Pavlik
Quoted 19 lines · AnonimoVeneziano
Quoted 15 lines · Patrick Petermair
Hi!
Same problem here. I have addressed this issue several times...so far no solution.
My specs:
MSI KT3 Ultra2 (VT8235)
TOSHIBA DVD-ROM SD-M1302
YAMAHA CRW8424EKernel 2.4.19:
The one I'm currently using. It doesn't detect the VT8235 and therefore I have no dma. But I can access/mount my DVD without a problem.Kernel 2.4.20:
Detects the VT8235 at boot but hangs with my DVD Rom (hdc) --> doesn't boot. I have posted my problem here an Alan Cox suggested that I should try the -ac tree.Quoted 10 lines
Quoted 4 lines
Kernel 2.4.20-ac2:
Some improvements - It detects the VT8235 at boot, also my DVD and CDRW. It boots fine and I have DMA on all my discs. But as soon as I try to mount a CD/DVD (mount /cdrom) the system hangs and I get this:Please, anyone help us, I can't live with a 6 MB HD bandwith!!!:-D
You're not alone with this problem. I suspect some fishy stuff in the vt8235, because the driver programs it exactly the same as vt8233a, but while the vt8233a doesn't seem to have problems with DVDs and CDs, the vt8235 fails for many people.
Quoted 10 lines
It might be some new DVD drive, though.
Can you send me 'hdparm -i' of the drive?
I'll try to make a patch to circumvent the problem ...
Thanks.
Here the hdparm -i of my first ATAPI drive.
I don't know if my Cd-recorder have the same problem, It have never tried to initialize it.
Byez
/dev/hdc:
Model=_NEC DV-5800A, FwRev=1.90, SerialNo=
Config={ Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=0kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 IORDY=yes, 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=no
Vojtech Pavlik:
Quoted 4 lines
You're not alone with this problem. I suspect some fishy stuff in the vt8235, because the driver programs it exactly the same as vt8233a, but while the vt8233a doesn't seem to have problems with DVDs and CDs, the vt8235 fails for many people.
Thanks for the info ... like I expected ...
Quoted 1 line
Can you send me 'hdparm -i' of the drive?
starbase:/# hdparm -i /dev/hdc
/dev/hdc:
Model=TOSHIBA DVD-ROM SD-M1302, FwRev=1006, SerialNo=X900304741 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=256kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 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=no
Thanks for all your effort here. It's great to see such a good community.
Patrick
Quoted 26 lines · Patrick Petermair
Vojtech Pavlik:
Quoted 4 lines
You're not alone with this problem. I suspect some fishy stuff in the vt8235, because the driver programs it exactly the same as vt8233a, but while the vt8233a doesn't seem to have problems with DVDs and CDs, the vt8235 fails for many people.
Thanks for the info ... like I expected ...
Quoted 1 line
Can you send me 'hdparm -i' of the drive?
starbase:/# hdparm -i /dev/hdc
/dev/hdc:Model=TOSHIBA DVD-ROM SD-M1302, FwRev=1006, SerialNo=X900304741 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=256kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 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=no
Quoted 2 lines
Thanks for all your effort here. It's great to see such a good community.
If you can, please try 2.4.20 with this patch.
Signature · 2 lines
Vojtech Pavlik SuSE Labs
Quoted 27 lines · Vojtech Pavlik
Quoted 26 lines · Patrick Petermair
Vojtech Pavlik:
Quoted 4 lines
You're not alone with this problem. I suspect some fishy stuff in the vt8235, because the driver programs it exactly the same as vt8233a, but while the vt8233a doesn't seem to have problems with DVDs and CDs, the vt8235 fails for many people.
Thanks for the info ... like I expected ...
Quoted 1 line
Can you send me 'hdparm -i' of the drive?
starbase:/# hdparm -i /dev/hdc
/dev/hdc:Model=TOSHIBA DVD-ROM SD-M1302, FwRev=1006, SerialNo=X900304741 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=256kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 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=no
Quoted 4 lines
Quoted 2 lines
Thanks for all your effort here. It's great to see such a good community.
If you can, please try 2.4.20 with this patch.
Patch attached now.
Signature · 2 lines
Vojtech Pavlik SuSE Labs
[email protected], 2002-12-16 11:00:04+01:00, [email protected]
Workaround problems with vt8235 and certain CD/DVD-ROMs.
via82cxxx.c | 20 ++++++++++++-------- 1 files changed, 12 insertions(+), 8 deletions(-)
drivers/ide/pci/via82cxxx.c +12 -8
@@ -67,6 +67,7 @@#define VIA_SET_FIFO 0x040/* Needs to have FIFO split set */ #define VIA_NO_UNMASK 0x080/* Doesn't work with IRQ unmasking on */ #define VIA_BAD_ID 0x100/* Has wrong vendor ID (0x1107) */ +#define VIA_NO_CMD_AS 0x200/* Don't program command and address setup timings */ /* * VIA SouthBridge chips.
@@ -80,10 +81,10 @@u16 flags; } via_isa_bridges[] = {#ifdef FUTURE_BRIDGES - { "vt8237", PCI_DEVICE_ID_VIA_8237, 0x00, 0x2f, VIA_UDMA_133 }, + { "vt8237", PCI_DEVICE_ID_VIA_8237, 0x00, 0x2f, VIA_UDMA_133 | VIA_NO_CMD_AS }, #endif - { "vt8235", PCI_DEVICE_ID_VIA_8235, 0x00, 0x2f, VIA_UDMA_133 }, - { "vt8233a", PCI_DEVICE_ID_VIA_8233A, 0x00, 0x2f, VIA_UDMA_133 }, + { "vt8235", PCI_DEVICE_ID_VIA_8235, 0x00, 0x2f, VIA_UDMA_133 | VIA_NO_CMD_AS }, + { "vt8233a", PCI_DEVICE_ID_VIA_8233A, 0x00, 0x2f, VIA_UDMA_133 | VIA_NO_CMD_AS }, { "vt8233c", PCI_DEVICE_ID_VIA_8233C_0, 0x00, 0x2f, VIA_UDMA_100 }, { "vt8233", PCI_DEVICE_ID_VIA_8233_0, 0x00, 0x2f, VIA_UDMA_100 }, { "vt8231", PCI_DEVICE_ID_VIA_8231, 0x00, 0x2f, VIA_UDMA_100 },
@@ -292,12 +293,15 @@ {u8 t; -pci_read_config_byte (dev,VIA_ADDRESS_SETUP , &t); - t = (t & ~(3 << ((3 - dn) <<1 ))) | ((FIT (timing->setup,1 ,4 ) -1 ) << ((3 - dn) <<1 )); -pci_write_config_byte (dev,VIA_ADDRESS_SETUP , t); +if (~via_config->flags &VIA_NO_CMD_AS ) { + +pci_read_config_byte (dev,VIA_ADDRESS_SETUP , &t); + t = (t & ~(3 << ((3 - dn) <<1 ))) | ((FIT (timing->setup,1 ,4 ) -1 ) << ((3 - dn) <<1 )); +pci_write_config_byte (dev,VIA_ADDRESS_SETUP , t); -pci_write_config_byte (dev,VIA_8BIT_TIMING + (1 - (dn >>1 )), - ((FIT (timing->act8b,1 ,16 ) -1 ) <<4 ) | (FIT (timing->rec8b,1 ,16 ) -1 )); +pci_write_config_byte (dev,VIA_8BIT_TIMING + (1 - (dn >>1 )), + ((FIT (timing->act8b,1 ,16 ) -1 ) <<4 ) | (FIT (timing->rec8b,1 ,16 ) -1 )); + }pci_write_config_byte (dev,VIA_DRIVE_TIMING + (3 - dn), ((FIT (timing->active,1 ,16 ) -1 ) <<4 ) | (FIT (timing->recover,1 ,16 ) -1 ));
Vojtech Pavlik:
Quoted 1 line
If you can, please try 2.4.20 with this patch.
Wow, that was fast.
The patch works perfect. The kernel boots with no problem, I have dma on all my disk AND I can mount a CD/DVD without any problems. Would be cool to see this patch included in the 2.4.21 kernel.
Thanks,
Patrick
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Vojtech Pavlik
Quoted 7 lines · AnonimoVeneziano
Quoted 7 lines
Quoted 3 lines
Thanks for all your effort here. It's great to see such a good community.
If you can, please try 2.4.20 with this patch.
Quoted 11 lines
Quoted 5 lines
This patch works great!! I've solved with this patch, very good work
Thank you very much Pavlik!
Can you try another patch (on top of the previous one?)? It might still work, and be less intrusive ... (attached)
I don't know what u have changed in this patch, but this work great too. ;-)
Thank you very much again
Byez
Quoted 19 lines · AnonimoVeneziano
Quoted 17 lines · Vojtech Pavlik
Quoted 13 lines · AnonimoVeneziano
Quoted 8 lines
Quoted 4 lines
Thanks for all your effort here. It's great to see such a good community.
If you can, please try 2.4.20 with this patch.
This patch works great!! I've solved with this patch, very good work
Thank you very much Pavlik!
Quoted 7 lines
Quoted 5 lines
Can you try another patch (on top of the previous one?)? It might still work, and be less intrusive ... (attached)
I don't know what u have changed in this patch, but this work great too. ;-) Thank you very much again
One more here, if you can try it (and remove the two previous ones first).
Signature · 2 lines
Vojtech Pavlik SuSE Labs
[email protected], 2002-12-18 10:01:30+01:00, [email protected]
vt82cxxx.c IDE: Never use 1 PCICLK address setup, because new devices choke on it.
via82cxxx.c | 5 ++++- 1 files changed, 4 insertions(+), 1 deletion(-)
drivers/ide/pci/via82cxxx.c +4 -1
@@ -286,6 +286,9 @@* @timing: IDE timing data to use * * via_set_speed writes timing values to the chipset registers +* Note: we never use the fastest ADDRESS_SETUP timing (1 PCICLK), +* because although it is OK with PIO4, many modern ATAPI devices +* choke on it. */ static void via_set_speed (struct pci_dev *dev,u8 dn,struct ide_timing *timing)
@@ -293,7 +296,7 @@u8 t;pci_read_config_byte (dev,VIA_ADDRESS_SETUP , &t); - t = (t & ~(3 << ((3 - dn) <<1 ))) | ((FIT (timing->setup,1 ,4 ) -1 ) << ((3 - dn) <<1 )); + t = (t & ~(3 << ((3 - dn) <<1 ))) | ((FIT (timing->setup,2 ,4 ) -1 ) << ((3 - dn) <<1 ));pci_write_config_byte (dev,VIA_ADDRESS_SETUP , t); pci_write_config_byte(dev, VIA_8BIT_TIMING + (1 - (dn >> 1)),
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · John Reiser
Quoted 2 lines · Vojtech Pavlik
One more here, if you can try it (and remove the two previous ones first).
The earlier vt8235-dvd patch worked for me, but the later vt8235-min did not.
Quoted 11 lines
Mitsumi FX4830T ATAPI CD-ROM, MSI KT3 Ultra2 (KT333) mainboard, vt8235.
-----
kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
kernel: hdc: drive not ready for command
kernel: hdc: status timeout: status=0xd1 { Busy }
kernel: hdc: DMA disabled
kernel: hdc: drive not ready for command
kernel: hdc: ATAPI reset complete
kernel: hdc: status timeout: status=0xd1 { Busy }
kernel: hdc: drive not ready for command
-----
Hunks error? during the patching?
byez
Marcello
Quoted 24 lines · AnonimoVeneziano
Quoted 9 lines · John Reiser
Quoted 2 lines · Vojtech Pavlik
One more here, if you can try it (and remove the two previous ones first).
The earlier vt8235-dvd patch worked for me, but the later vt8235-min did not.
Quoted 12 lines
Mitsumi FX4830T ATAPI CD-ROM, MSI KT3 Ultra2 (KT333) mainboard, vt8235.
-----
kernel: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
kernel: hdc: drive not ready for command
kernel: hdc: status timeout: status=0xd1 { Busy }
kernel: hdc: DMA disabled
kernel: hdc: drive not ready for command
kernel: hdc: ATAPI reset complete
kernel: hdc: status timeout: status=0xd1 { Busy }
kernel: hdc: drive not ready for command
-----
Quoted 5 lines
Hunks error? during the patching?
byez
Marcello
Hi,
The lattest workaround from Vojtech fixed the problem for you ?