SATA DVD drive not detected in Jaunty (testing)

[gtdaqua]

Ever since testing Jaunty on my Dell Optiplex 740, the SATA DVD drive is not detected.
Updated the Dell BIOS and issue persists.

Also, a Lite-On iHOS104-08 SATA BD-ROM drive exhibiting the same problem in Karmic 9.10.

[gtdaqua (gtdaquitaine)]

Here is the dmesg output

[code]
[ 3.492191] ata2.00: ATAPI: PBDS DVD+/-RW DS-8W1P, BD1A, max UDMA/33
[ 3.492201] ata2.00: applying bridge limits
[ 3.524206] ata2.00: configured for UDMA/33
[ 8.524024] ata2.00: qc timeout (cmd 0xa0)
[ 8.524028] ata2.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 9.404041] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9.460210] ata2.00: configured for UDMA/33
[ 14.460023] ata2.00: qc timeout (cmd 0xa0)
[ 14.460026] ata2.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 14.460029] ata2: limiting SATA link speed to 1.5 Gbps
[ 14.460032] ata2.00: limiting speed to UDMA/33:PIO3
[ 15.340041] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 15.396210] ata2.00: configured for UDMA/33
[ 20.396023] ata2.00: qc timeout (cmd 0xa0)
[ 20.396026] ata2.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 20.396028] ata2.00: disabled
[ 20.396038] ata2: hard resetting link
[ 21.276039] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 21.276045] ata2: EH complete
[ 21.338514] sata_nv 0000:00:0f.0: PCI INT A -> Link[APSJ] -> GSI 22 (level, low) -> IRQ 22
[ 21.338517] sata_nv 0000:00:0f.0: Using SWNCQ mode
[ 21.338567] sata_nv 0000:00:0f.0: setting latency timer to 64
[ 21.338723] scsi2 : sata_nv
[ 21.338855] scsi3 : sata_nv
[ 21.339071] ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xcc00 irq 22
[ 21.339074] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xcc08 irq 22
[ 22.070434] ata3: SATA link down (SStatus 0 SControl 300)
[ 22.802431] ata4: SATA link down (SStatus 0 SControl 300)
[/code]

I am running 2.6.28-9-generic.

[gtdaqua (gtdaquitaine)]

uname -a:

Linux aquitaine 2.6.28-9-generic #31-Ubuntu SMP Wed Mar 11 15:43:58 UTC 2009 i686 GNU/Linux

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

[gtdaqua (gtdaquitaine)]

Jaunty is out but the problem still exists! If this distro wont see SATA-DVD in Dell Optiplex 740, then I will have to switch to Intrepid.

[gtdaqua (gtdaquitaine)]

Guys, this problem is still not sorted! I have reverted to 8.04 now!

I have upgraded the firmware of the DVD drive to the latest but the problem persists. Looks like kernel 2.6.26 and above are having the same issue because Debian 5.0.1 Lenny also will not see the drive!

[totoro (ton-ami-totoro)]

Hi
I have the same problem but with a other dvd player, can you give us the result of a lshw command. So It's look to be somthing other than the dvd player
Thank you

mine is here:
http://pastebin.com/f39a0cac7

and an other bug report for the same problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/344128

[gtdaqua (gtdaquitaine)]

I installed Ubuntu Karmic Alpha 4 and the SATA DVD drive was detected without any problems!

I am happy that I can move away from Hardy 8.04. Back on the bleeding-edge distro!

Kernel:
Linux trust 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:48:18 UTC 2009 i686 GNU/Linux

dmesg.log file attached. The output related to SATA DVD in the dmesg is here (no errors reported relating to SATA DVD)

[ 1.283789] Using IPI No-Shortcut mode
[ 1.283969] PM: Resume from disk failed.
[ 1.283984] registered taskstats version 1
[ 1.284133] Magic number: 5:777:11
[ 1.284145] misc pktcdvd!control: hash matches
[ 1.284251] rtc_cmos 00:04: setting system clock to 2009-08-17 05:02:10 UTC (1250485330)
[ 1.284255] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.284257] EDD information not available.
[ 1.286967] sda5 sda6 sda7 >
[ 1.314515] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.380044] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.412199] ata2.00: ATAPI: PBDS DVD+/-RW DS-8W1P, BD1C, max UDMA/33
[ 1.412209] ata2.00: applying bridge limits
[ 1.452208] ata2.00: configured for UDMA/33
[ 1.456104] scsi 1:0:0:0: CD-ROM PBDS DVD+-RW DS-8W1P BD1C PQ: 0 ANSI: 5
[ 1.467147] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
[ 1.467150] Uniform CD-ROM driver Revision: 3.20
[ 1.467314] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 1.467448] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 1.477931] ata4: SATA link down (SStatus 0 SControl 300)
[ 1.477964] Freeing unused kernel memory: 536k freed
[ 1.478361] Write protecting the kernel text: 4548k
[ 1.478397] Write protecting the kernel read-only data: 1828k
[ 1.564212] Linux agpgart interface v0.103
[ 1.587584] [drm] Initialized drm 1.1.0 20060810
[ 1.693018] usb 2-4: new full speed USB device using ohci_hcd and address 2
[ 1.898126] tg3.c:v3.99 (April 20, 2009)
[ 1.898519] ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16

Hope the 2.6.31 and higher kernels keeps this drive alive.

[Gregory Moyer (syphr42)]

I don't think this is fixed, but if I am mistaken, please let me know and I will open a new bug.

I'm running 9.10 Karmic, up-to-date, and I am having what seems to be the same problem with a LiteOn iHOS104-08 SATA BD-ROM drive.

Here is the relevant part of my dmesg:

[ 1.180349] ata5.00: ATAPI: ATAPI iHOS104, WL0B, max UDMA/100
[ 1.220179] ata5.00: configured for UDMA/100
[ 6.220071] ata5.00: qc timeout (cmd 0xa0)
[ 6.220076] ata5.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 6.380063] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 6.440174] ata5.00: configured for UDMA/100
[ 11.440069] ata5.00: qc timeout (cmd 0xa0)
[ 11.440074] ata5.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 11.440077] ata5: limiting SATA link speed to 1.5 Gbps
[ 11.440081] ata5.00: limiting speed to UDMA/100:PIO3
[ 11.600080] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 11.660174] ata5.00: configured for UDMA/100
[ 16.660049] ata5.00: qc timeout (cmd 0xa0)
[ 16.660054] ata5.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 16.660056] ata5.00: disabled
[ 16.660069] ata5: hard resetting link
[ 16.660071] ata5: nv: skipping hardreset on occupied port
[ 16.820063] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 16.820071] ata5: EH complete
[ 16.980063] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 17.000164] ata6.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB01, max UDMA/33
[ 17.000175] ata6.00: applying bridge limits
[ 17.040178] ata6.00: configured for UDMA/33
[ 17.041472] scsi 5:0:0:0: CD-ROM TSSTcorp CD/DVDW SH-S183L SB01 PQ: 0 ANSI: 5
[ 17.048623] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 17.048627] Uniform CD-ROM driver Revision: 3.20
[ 17.048713] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 17.048760] sr 5:0:0:0: Attached scsi generic sg1 type 5

As you can see, the drive on "ata5" fails (that's the Blu-Ray), but the SATA DVD burner on "ata6" is detected properly and works as expected. However, the BIOS detects the drive and I can even partially boot a live CD from the Blu-Ray (I get the language selection and I can choose to boot the live disk, but it dies during boot because it can no longer find the drive). Also, note that where is says "err_mask=0x4" I have also seen "err_mask=0x5".

The motherboard is an EVGA 680i SLI (at current BIOS - P33). From the dmesg output (a little earlier than the snippet above), I believe the driver in use is "sata_nv".

I have tried many things to work around this issue:

1) Moved the Blu-Ray to different SATA ports, including the known good ones where my hard disk and DVD burner are connected.
2) Booted with "noapic", "acpi=off", "irqpoll", and "hpet=disable"
3) Disabled HPET and APIC (separately and together) in the BIOS
4) Booted from a 9.04, 9.10, and current daily build of 10.04 live CD (all with the same result)

I am currently downloading the live CD for Fedora 12 to see if that shows any different result. I will report back when I know either way.

Also, if it helps, it looks like someone else reported the same problem with the same drive in the forums back in July.
http://ubuntuforums.org/showthread...

[Gregory Moyer (syphr42)]

i tested Fedora 12 from the current live CD and I get the same result as Ubuntu.

I have also tried installing the mailine kernel 2.6.32 for AMD64 (available here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/). This gives the same error, as I would expect since the daily build of 10.04 Lucid uses 2.6.32rc8 and that didn't work either.

[Gregory Moyer (syphr42)]

I was finally able to test this drive on a Windows XP 32-bit machine and the drive does work as expected.

I have also tried a Gentoo 10.0 live dvd and I get the same problem as with Ubuntu and Fedora.

[Gregory Moyer (syphr42)]

Today, I got word from Lite-On that they tested the drive with Mandriva 2007. I assumed they meant 2007.0 and so I got a copy and tried it. Sure enough, the drive is detected. That distribution uses the 2.6.17 kernel. I'm not sure if this is certainly a kernel issue, but if it is (or the sata_nv driver), it is a regression between 2.6.17 and 2.6.31.

[gaz2373 (gr-hopkins)]

I can report the same error with the Lite-On iHOS104-08 SATA BD-ROM drive on previous 8.10 (Intrepid Ibex) also.

Mother board GeForce 6100 Nvidia MCP61P chipset.

Will try Mandriva to see if it works and update.

[gaz2373 (gr-hopkins)]

Tried Mandriva 2010 with same error message
uses Sata_nv 3.5 and kernel 2.6.31.
Will download Mandriva 2007 to compare.
Update to follow.

[gaz2373 (gr-hopkins)]

As above drive works with Mandriva 2007
Sata_nv version appears to be 0.8 on the Mandriva with kernel 2.6.17
As above regression works

[Gregory Moyer (syphr42)]

Apparently someone else is having this issue as well. I found this at gossamer threads:

http://www.gossamer-threads.com/lists/linux/kernel/1170613

The person in that thread reported the drive working on a different chipset (VIA). More evidence to suggest that sata_nv is to blame.

[Gregory Moyer (syphr42)]

Update from the kernel mailing list: there is a patch now that gets the drive working (swncq-polling-pio.patch from the list archive link above). Someone else on that thread has reported success, however low performance (UDMA/33). I have built 2.6.31-19 using the latest Ubuntu 9.10 sources as of 02/21/2010 with all three patches from the kernel thread and I can report the same experience. The drive was detected, but only after a few errors and at a reduced speed (33). Also, I am unsure if all of them are necessary or just the one referenced in this comment.

[Terracotta (terracotta-deactivatedaccount)]

Lucid alpha 3 has the same problem with the iHOS104 BD-rom drive.
The drive works as expected under windows 7.

[markofealing (mark-ferns16)]

Just updated Kubuntu 9.10 (64-bit) to latest kernel 2.6.31-17-generic
, now K3B just burns around half the disk and the DVD R/W drive drops out totally, not even visible in Dolphin. The drive is brand new Pioneer IDE, just before the upgrade it was working fine. Log file extract below

2010-03-05 21:59:26 Kubuntu64 kernel [ 363.971865] Disabling IRQ #23
2010-03-05 22:09:01 Kubuntu64 CRON[2534] (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
2010-03-05 22:09:21 Kubuntu64 kernel [ 959.012539] ata5: lost interrupt (Status 0x50)
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682553] INFO: task hald-addon-stor:1450 blocked for more than 120 seconds.
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682562] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682568] hald-addon-st D 0000000000000000 0 1450 1100 0x00000000
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682579] ffff880061cf3c28 0000000000000082 ffffffff81130180 0000000000015880
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682588] ffff8800648b03b0 0000000000015880 0000000000015880 0000000000015880
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682596] 0000000000015880 ffff8800648b03b0 0000000000015880 0000000000015880
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682604] Call Trace:
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682620] [<ffffffff81130180>] ? __pollwait+0x0/0xf0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682632] [<ffffffff81528847>] __mutex_lock_slowpath+0xd7/0x160
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682642] [<ffffffff8114d1d0>] ? blkdev_open+0x0/0xc0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682649] [<ffffffff81528746>] mutex_lock+0x26/0x50
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682656] [<ffffffff8114ce58>] __blkdev_get+0x38/0x3a0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682663] [<ffffffff8114d1d0>] ? blkdev_open+0x0/0xc0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682670] [<ffffffff8114d1cb>] blkdev_get+0xb/0x10
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682676] [<ffffffff8114d23c>] blkdev_open+0x6c/0xc0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682685] [<ffffffff8111d2a6>] __dentry_open+0xe6/0x2e0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682692] [<ffffffff8111d5a7>] nameidata_to_filp+0x57/0x70
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682701] [<ffffffff8112cbfa>] do_filp_open+0x2ca/0xac0
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682708] [<ffffffff8113479b>] ? iput+0x2b/0x70
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682716] [<ffffffff8113893b>] ? mntput_no_expire+0x2b/0x100
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682725] [<ffffffff8127cf02>] ? __strncpy_from_user+0x22/0x60
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682732] [<ffffffff81137672>] ? alloc_fd+0x102/0x150
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682740] [<ffffffff8111d074>] do_sys_open+0x64/0x160
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682747] [<ffffffff8111d19b>] sys_open+0x1b/0x20
2010-03-05 22:09:23 Kubuntu64 kernel [ 960.682757] [<ffffffff81012002>] system_call_fas...

[N (nathaniel7)]

This occurs with a Intel D915GRV and a iHOS104, so I think the issue is with this drive. This board allows me to set the PIO and DMA mode for this drive. Do the error codes have anything to do with those? Here is relevant dmesg and full is attached. Thank you.

[ 4.790284] ata3.00: ATAPI: ATAPI iHOS104, WL0B, max UDMA/100
[ 4.834561] ata3.01: ATA-7: ST3160812AS, 3.AAE, max UDMA/133
[ 4.834566] ata3.01: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 4.870221] ata3.00: configured for UDMA/100
[ 4.942842] ata3.01: configured for UDMA/133
[ 5.320012] usb 2-2: new full speed USB device using uhci_hcd and address 2
[ 5.501487] usb 2-2: configuration #1 chosen from 1 choice
[ 9.940020] ata3.00: qc timeout (cmd 0xa0)
[ 9.940027] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 10.200210] ata3.00: configured for UDMA/100
[ 10.273677] ata3.01: configured for UDMA/133
[ 15.270018] ata3.00: qc timeout (cmd 0xa0)
[ 15.270025] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 15.270029] ata3.00: limiting speed to UDMA/100:PIO3
[ 15.530210] ata3.00: configured for UDMA/100
[ 15.604525] ata3.01: configured for UDMA/133
[ 20.600018] ata3.00: qc timeout (cmd 0xa0)
[ 20.600024] ata3.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 20.600027] ata3.00: disabled
[ 20.600044] ata3: soft resetting link
[ 20.902055] ata3.01: configured for UDMA/133
[ 20.902060] ata3: EH complete

[markofealing (mark-ferns16)]

My particular problem seems to be caused by the VIA VT8251 controller causing errors on the SATA bus and the SATA bus dropping back to UDMA/33. See editied version of Kernel log below:

2010-04-25 16:42:12 [ 1705.688583] ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x580100 action 0x6 frozen
2010-04-25 16:42:12 [ 1705.688589] ata3.00: irq_stat 0x08000000, interface fatal error
2010-04-25 16:42:12 [ 1705.688594] ata3: SError: { UnrecovData 10B8B Dispar Handshk }
2010-04-25 16:42:12 [ 1705.688604] ata3.00: cmd 35/00:00:1f:59:fa/00:04:16:00:00/e0 tag 0 dma 524288 out
2010-04-25 16:42:12 [ 1705.688605] res 50/00:00:1e:59:fa/00:00:16:00:00/e0 Emask 0x10 (ATA bus error)
2010-04-25 16:42:12 [ 1705.688609] ata3.00: status: { DRDY }
2010-04-25 16:42:12 [ 1705.688615] ata3: hard resetting link
2010-04-25 16:42:13 [ 1706.212549] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2010-04-25 16:42:13 [ 1706.332620] ata3.00: configured for UDMA/133

2010-04-25 16:46:34 [ 1968.012445] ata3.00: limiting speed to UDMA/100:PIO4
2010-04-25 16:46:34 [ 1968.012457] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x180000 action 0x6 frozen
2010-04-25 16:46:34 [ 1968.012467] ata3: SError: { 10B8B Dispar }
2010-04-25 16:46:34 [ 1968.012484] ata3.00: cmd 35/00:00:9f:e2:81/00:04:17:00:00/e0 tag 0 dma 524288 out
2010-04-25 16:46:34 [ 1968.012486] res 40/00:00:6e:08:7b/00:00:17:00:00/e0 Emask 0x4 (timeout)
2010-04-25 16:46:34 [ 1968.012493] ata3.00: status: { DRDY }
2010-04-25 16:46:34 [ 1968.012520] ata3: hard resetting link
2010-04-25 16:46:35 [ 1968.540878] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
2010-04-25 16:46:35 [ 1968.644397] ata3.00: configured for UDMA/100
2010-04-25 16:46:35 [ 1968.644424] ata3: EH complete

2010-04-25 16:49:14 [ 2128.010067] ata3.00: limiting speed to UDMA/33:PIO4
2010-04-25 16:49:14 [ 2128.010078] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x180000 action 0x6 frozen
2010-04-25 16:49:14 [ 2128.010088] ata3: SError: { 10B8B Dispar }
2010-04-25 16:49:14 [ 2128.010104] ata3.00: cmd 35/00:00:47:a5:8a/00:04:17:00:00/e0 tag 0 dma 524288 out
2010-04-25 16:49:14 [ 2128.010107] res 40/00:00:3e:9d:8a/00:00:17:00:00/e0 Emask 0x4 (timeout)
2010-04-25 16:49:14 [ 2128.010114] ata3.00: status: { DRDY }
2010-04-25 16:49:14 [ 2128.010123] ata3: hard resetting link
2010-04-25 16:49:15 [ 2128.542591] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
2010-04-25 16:49:15 [ 2128.634875] ata3.00: configured for UDMA/33
2010-04-25 16:49:15 [ 2128.634907] ata3: EH complete

This appears to be similar to the above problem although with a different SATA controller.

See my blog http://tinyurl.com/2v5cnpu for more info.

I think this bug and Bug #282536 are similar if not the same, and possibly Bug #190492.

[Gregory Moyer (syphr42)]

Tejun over on the LKML has created a patch that solved the issue for me. I recommend anyone having this problem try the patch and report directly to the kernel list on whether or not it fixed the issue. Hopefully the change will be put into the upstream code and this bug can be closed.

Here is the link again to the discussion:

http://www.gossamer-threads.com/lists/linux/kernel/1170613

[Jeremy Foshee (jeremyfoshee)]

Gregory,
    Glad to hear this is getting some attention. is there an upstream bug we can watch here to keep us all on the same track?

Thanks!

~JFo

[Gregory Moyer (syphr42)]

No, I don't believe there is an upstream bug log, but I can do one better. I just read Linus' release note for 2.6.35-rc2 and I came across this:

...
Tejun Heo (5):
     sata_via: magic vt6421 fix for transmission problems w/ WD drives
     sata_nv: don't diddle with nIEN on mcp55
     SCSI: implement sd_unlock_native_capacity()
     libata: use the enlarged capacity after late HPA unlock
     libata: implement on-demand HPA unlocking
...

That second line is the patch I mentioned in comment #26, so it looks like this fix will be part of 2.6.35 and a recent announcement stated that that will be Maverick's kernel version.

https://wiki.ubuntu.com/KernelTeam/Specs/KernelMaverickVersion

[benpicco (benpicco)]

May it be possible that this fix (2 lines changed) gets backported to the current lucid kernel?

http://lkml.org/lkml/2010/7/1/552

[benpicco (benpicco)]

I've just noticed that this patch is part of the 2.6.32.16 update, so it probably will reach ubuntu soon.

http://lkml.org/lkml/2010/7/5/218

[Josh Schlenker (jschlenk23)]

I'm having the identical problem with the lite-on blu-ray IOS104 blu-ray drive on an ASUS M4N68T (nvidia mcp61 chipset) motherboard with fedora 12 (2.6.31.5).

I tried upgrading to 2.6.32.19 to take advantage of this patch, but this *does not* fix the problem for me. I also tried to boot the maverick alpha 3 live cd from this drive so I could try 2.6.35, but no luck there either. After the initial bootup by the bios the drive is lost when the kernel is loaded. Similar to what others have reported, I am able to boot mandriva 2007.0 from the drive w/o problems.

I looked closer at the patch and it is only for mcp5x chipsets which explains why this is still an issue for me on the latest kernels.

I was wondering if it would be possible to compile the version of nv_sata used in mandriva 2007 with the kernel in fedora and boot with this modified kernel whenever I needed to use the drive as a work around until this gets fixed for my hardware. Would there be conflicts between of an old nv_sata and a new kernel? I am a linux noobie and have never tried compiling the kernel before, so I have no idea how feasible this is or how to try it myself.

[lotusalive (thundergirl1234)]

Jaunty 9.04 for about a year, Bios suddenly is not detecting 'cdrom' at all ! Can someone direct me to a fix ?

[Joseph P (joseph13)]

I'm using a SATA PCI card VT6421 chipset with two Western Digital drives. Supposedly issues with communication between the card and drives has been solved as mentioned above. I have installed kernel 2.6.37 on Ubuntu Maveric 10.10 and have also used Ubuntu Knatty Alpha 1.0 and am still having issues. Any help?
(See my post http://ubuntuforums.org/showthread.php?t=1665984)

[cubik (s-cubik)]

Hello,
I've the exact same problem with my Lite-on iHAS124 (dvd writer).
I'm using Linx Mint 10 64bits (based on ubuntu).
I've tried changing the sata cable. Changing the sata port.
I can boot on it and it works fine on windows.
I've tried updating my kernel (2.6.37RC3, 2.6.37RC8, 2.6.38RC1) but it still doesn't detect my drive.

[cubik (s-cubik)]

For information, after a lot of search in multiple forums, a solution has been found, at least for me.
My drive was set to IDE in the bios.
After switching it to AHCI, my drive appeared in linux and works just fine.

[etnba (g9417717)]

Hi All,

I have a similar problem in Ubuntu 10.10(Marevrick).

I meet the same situation when I plug a DVD drive to SATA 3.0 port and set SATA controlloer to IDE mode.

If I plug DVD drive to SATA 2.0 port and set SATA controlloer to IDE mode, DVD drive can be detected.

If I plug DVD drive to SATA 3.0 port and set SATA controlloer to AHCI mode, DVD drive can be detected, too.

I am failed to file a bug. Can somebody help me?

Thanks

dmesg:
[ 1.892198] ata1: SATA max UDMA/133 cmd 0x3098 ctl 0x30ac bmdma 0x3070 irq 19
[ 3.309652] ata1.01: failed to resume link (SControl 0)
[ 3.469636] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 3.469777] ata1.01: SATA link down (SStatus 4 SControl 0)
[ 3.469899] ata1.01: link offline, clearing class 3 to NONE
[ 3.489703] ata1.00: ATAPI: HL-DT-ST DVDRAM GH22NS40, NL02, max UDMA/100
[ 3.529740] ata1.00: configured for UDMA/100
[ 8.526759] ata1.00: qc timeout (cmd 0xa0)
[ 8.526872] ata1.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 9.945970] ata1.01: failed to resume link (SControl 0)
[ 10.105952] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 10.106074] ata1.01: SATA link down (SStatus 4 SControl 0)
[ 10.106188] ata1.01: link offline, clearing class 3 to NONE
[ 10.165978] ata1.00: configured for UDMA/100
[ 15.163063] ata1.00: qc timeout (cmd 0xa0)
[ 15.163171] ata1.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 15.163277] ata1.00: limiting SATA link speed to 1.5 Gbps
[ 15.163382] ata1.00: limiting speed to UDMA/100:PIO3
[ 16.582272] ata1.01: failed to resume link (SControl 0)
[ 16.742249] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 16.742371] ata1.01: SATA link down (SStatus 4 SControl 0)
[ 16.742486] ata1.01: link offline, clearing class 3 to NONE
[ 16.802290] ata1.00: configured for UDMA/100
[ 21.799369] ata1.00: qc timeout (cmd 0xa0)
[ 21.799478] ata1.00: TEST_UNIT_READY failed (err_mask=0x4)
[ 21.799583] ata1.00: disabled
[ 21.799693] ata1.00: hard resetting link
[ 22.149176] ata1.01: hard resetting link
[ 23.218581] ata1.01: failed to resume link (SControl 0)
[ 23.378554] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 23.378676] ata1.01: SATA link down (SStatus 4 SControl 0)
[ 23.378790] ata1.01: link offline, clearing class 3 to NONE
[ 23.378793] ata1: EH complete

lspci:
00:1f.2 IDE interface: Intel Corporation Cougar Point 4 port SATA IDE Controller (rev 04) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Intel Corporation Cougar Point 4 port SATA IDE Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 19
Region 0: I/O ports at 3098 [size=8]
Region 1: I/O ports at 30ac [size=4]
Region 2: I/O ports at 3090 [size=8]
Region 3: I/O ports at 30a8 [size=4]
Region 4: I/O ports at 3070 [size=16]
Region 5: I/O ports at 3060 [size=16]
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] PCI Advanced Features
AFCap...

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.