DMA CD/DVD Problems in Jaunty

Bug #348241 reported by John Talbot
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

DMA is disabled on Jaunty

Managed to turn it on using the following...

Edit /boot/grub/menu.lst
Then add
pata_ali.atapi_dma=1

To the end of the default menu item, Ie...
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=78f1fb4c-838e-4271-9cf4-595ad7d3c7a1 ro quiet splash pata_ali.atapi_dma=1

Then reseting machine

But now the UDMA is set wrong...

sudo dmesg | grep ata

[ 3.520434] pata_ali 0000:00:16.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 3.520571] scsi4 : pata_ali
[ 3.520633] scsi5 : pata_ali
[ 3.521957] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
[ 3.521960] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
[ 3.684455] ata5.00: ATAPI: PIONEER DVD-RW DVR-110D, 1.17, max UDMA/66
[ 3.700450] ata5.00: configured for UDMA/66

Beyond this I'm not sure what to do??

Related branches

John Talbot (jwtalbot)
description: updated
Revision history for this message
John Talbot (jwtalbot) wrote :

Also hapenin' with my Laptop...

sudo dmesg | grep ata

[ 1.940658] ata_piix 0000:00:1f.2: version 2.12
[ 1.940680] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 1.940685] ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
[ 1.940730] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 1.940840] scsi0 : ata_piix
[ 1.940950] scsi1 : ata_piix
[ 1.943000] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 1.943004] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 2.104394] ata1.00: ATA-7: FUJITSU MHV2060BH PL, 00000029, max UDMA/100
[ 2.104397] ata1.00: 117210240 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 2.120414] ata1.00: configured for UDMA/100
[ 2.300356] ata2.00: ATAPI: TSSTcorpCD/DVDW TS-L632D, TIR0, max UDMA/33
[ 2.332316] ata2.00: configured for UDMA/33
[ 2.517807] Write protecting the kernel read-only data: 1532k
[ 3.716996] EXT4-fs: mounted filesystem with ordered data mode.
[ 10.752510] EXT4-fs: mounted filesystem with ordered data mode.
[ 436.004159] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 436.004173] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 436.004180] ata2.00: status: { DRDY }
[ 441.044025] ata2: link is slow to respond, please be patient (ready=0)
[ 446.028048] ata2: device not ready (errno=-16), forcing hardreset
[ 446.028060] ata2: soft resetting link
[ 446.240354] ata2.00: configured for UDMA/33
[ 446.248742] ata2: EH complete

It is also setting my HD to UDMA100 instead of UDMA133

affects: ubuntu → grub (Ubuntu)
Steve Langasek (vorlon)
affects: grub (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Baron,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 348241

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
John Talbot (jwtalbot) wrote :

Found this is an older bug... 228302

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.