Kernel: gentoo-sources-2.6.24-r7 I have an IDE DVD/CD writer, and it works just fine with the older IDE subsystem (AMD_IDE, according to http://hardware4linux.info/). All my apps work with it. Includes data discs that need to be mounted as well as playing audio discs and DVDs. However, when I try switching to the newer libata subsystem, enabling the proper kernel options for SCSI disk support as well as the "correct" driver for AMD/nVidia PATA disks, my drive can't really read things properly anymore. The weird thing is that /dev/sr0 does exist in /dev (cdrom1, cdrw1, dvdrw1 etc. are all symlinked to it), and applications can see the drive itself. Mostly. I insert an audio CD, and it pops up on my desktop. Audio players see the disc, fetche info from CDDB and display it, but can't actually play it. No audio app can. I don't seem to be getting any helpful error messages either, despite enabling SCSI verbose error reporting in my kernel. Same story for DVDs -- they can be mounted, and the icon appears on the desktop, but they can't actually be played. Yes, I've told mplayer the correct device to look for. If it's just a data disc, I can mount it and open files, etc. Sometimes this works, sometimes it doesn't. It seems to work for most plain data discs. That's some good news, at least. lspci snippet: # lspci ... 00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1) 00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) 00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) 00:05.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) ... dmesg snippet: Note that it contains both actual SATA hard drive info and the IDE optical drive info; it looks like it might be getting confused about what to do. I'm pretty sure there's not a configuration error on my end. # dmesg ... SCSI subsystem initialized libata version 3.00 loaded. ... Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods scsi0 : sata_nv scsi1 : sata_nv ata1: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc000 irq 21 ata2: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xc008 irq 21 ata1: SATA link down (SStatus 0 SControl 300) ata2: SATA link down (SStatus 0 SControl 300) ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:05.1[B] -> Link [LSA1] -> GSI 20 (level, low) -> IRQ 20 PCI: Setting latency timer of device 0000:00:05.1 to 64 scsi2 : sata_nv scsi3 : sata_nv ata3: SATA max UDMA/133 cmd 0xbc00 ctl 0xb880 bmdma 0xb400 irq 20 ata4: SATA max UDMA/133 cmd 0xb800 ctl 0xb480 bmdma 0xb408 irq 20 ata3: SATA link down (SStatus 0 SControl 300) ata4: SATA link down (SStatus 0 SControl 300) ACPI: PCI Interrupt Link [LSA2] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:05.2[C] -> Link [LSA2] -> GSI 23 (level, low) -> IRQ 23 PCI: Setting latency timer of device 0000:00:05.2 to 64 scsi4 : sata_nv scsi5 : sata_nv ata5: SATA max UDMA/133 cmd 0xb080 ctl 0xb000 bmdma 0xa800 irq 23 ata6: SATA max UDMA/133 cmd 0xac00 ctl 0xa880 bmdma 0xa808 irq 23 ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5.00: ATA-7: SAMSUNG HD160JJ, WU100-33, max UDMA/100 ata5.00: 312581808 sectors, multi 16: LBA48 ata5.00: configured for UDMA/100 ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata6.00: ATA-7: SAMSUNG HD160JJ, WU100-33, max UDMA/100 ata6.00: 312581808 sectors, multi 16: LBA48 ata6.00: configured for UDMA/100 scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD160JJ WU10 PQ: 0 ANSI: 5 sd 4:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sda4 sd 4:0:0:0: [sda] Attached SCSI disk scsi 5:0:0:0: Direct-Access ATA SAMSUNG HD160JJ WU10 PQ: 0 ANSI: 5 sd 5:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 5:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sdb2 sdb3 sdb4 sd 5:0:0:0: [sdb] Attached SCSI disk pata_amd 0000:00:04.0: version 0.3.10 PCI: Setting latency timer of device 0000:00:04.0 to 64 scsi6 : pata_amd scsi7 : pata_amd ata7: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14 ata8: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15 ata7.00: ATAPI: TSSTcorpCD/DVDW SH-S182M, SB01, max UDMA/33 ata7.00: configured for UDMA/33 ata8: port disabled. ignoring. scsi 6:0:0:0: CD-ROM TSSTcorp CD/DVDW SH-S182M SB01 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 32x/40x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 6:0:0:0: Attached scsi CD-ROM sr0 kernel config: http://dev.gentoo.org/~nightmorph/misc/config-2.6.24-r7.txt
Hi Josh, does setting "Device drivers->SCSI device support->SCSI generic support" fix it? If not then could you please try strace'ing a process that plays from a CD. For example, if you have mplayer installed, use the following command: "strace -otrace.log mplayer cdda://". The log will probably be quite large, so you may want to zip it before adding it here.
Please feel free to reopen once you've had a chance to try the steps in comment #1.
Reopening with testing notes.
Well, I tried adding SCSI generic options as shown; no joy. I fired up Decibel Audio Player to get some strace output; it's attached. I also tried switching to kernel 2.6.25-r6, now stable on amd64, but that had no result either. Config is at http://dev.gentoo.org/~nightmorph/misc/config-2.6.24-r7.txt
Created attachment 159755 [details] strace of decibel audio player Here's the strace log while trying to play an audio CD using Decibel Audio Player. Note that it works perfectly (substituting /dev/hda for /dev/sr0) as long as I'm using the ol' IDE subsystem and not libata.
Okay, an update: It seems mplayer will now play DVDs and even audio CDs, once I reemerged it with the "cddb" and "cdparanoia" USE flags enabled. However, the audio for the CDs was terribly scratchy and poppy, with frequent hiccups and freezes. Basically, using it for CDs is completely impossible, and I don't see these noise issues on Decibel or any other audio player (such as audacious). Of further interest is that I can mount regular CDs in the hard drive now, such as ISOs, and browse their contents. What still doesn't work? Decibel Audio Player, and Totem, and gnome-cd-player. What's common to all three? GSTREAMER. Yes, Gstreamer. I'm wondering if this has something to do with it. Especially since Decibel can see CDs, fetch their info from CDDB/freedb, but can't play them. Gstreamer refuses to acknowledge that there is a CD in the drive, and gnome-cd-player offers to edit the device path, but though it displays the proper device name in the dropdown (as reported via HAL), it can't actually play anything; it's still looking for /dev/hda. No further configuration is possible. Oh, and there's one other thing that's not working with mplayer: when switching to libata, dvdnav:// no longer works. Apparently /dev/dvd used to be created and symlinked automatically to /dev/hda with the old IDE subsystem, but no longer. Fortunately, manually symlinking /dev/dvd to /dev/sr0 works, though it is a bit weird that each subsystem adds and removes different symlinks; libata adds quite a few new ones. Just not the ones I need. So to sum up: there are a few more things working, but it seems that at least some gstreamer apps definitely aren't? I'm hesitant to blame this on gstreamer so soon, though.
It sounds like you are having a udev rules problem, for starters. That is what should be taking care of setting up symlinks. I think it would be a good idea to get that sorted out first. If you are lucky it might fix some of your other problems (such as gstreamer trying to use the wrong device). I suggest first *backing up* then deleting this file: /etc/udev/rules.d/70-persistent-cd.rules When you reboot it should be recreated. Hopefully you will then have all the usual symlinks (/dev/cdrom, /dev/dvd, etc) pointing to the correct device. If anything goes horribly wrong just restore the old copy. After your symlinks are sorted do gstreamer apps still have problems?
(In reply to comment #7) > After your symlinks are sorted do gstreamer apps still have problems? Yes. While the backup & removal procedure restored a fresh copy of the udev rules file -- the old one had duplicate entries that referred to the drive by PCI ID as both IDE and SCSI; the new one just has SCSI -- I still have playback errors. Specifically, while I can play all the audio CDs I've tried so far, I can't play past track 9, or occasionally past track 11. Also, gstreamer-based Gnome playback applications such as Totem and gnome-cd-player simply do not work with CDs, period. They still look for /dev/hda, but offer no configuration changes; they stubbornly refuse to update themselves, even if they refer to the drive by name in the dropdown device selector. They still want to see it as /dev/hda. In the case of Totem, it doesn't believe there's anything in the drive at all; the option to "play audio CD" is grayed out and cannot be clicked. I'm wondering if I have something odd in my kernel config as far as SCSI scanning goes, or possibly some other related option. I've changed to the 2.6.25-r6 kernel to see if it helps. My config is available at: http://dev.gentoo.org/~nightmorph/misc/config-2.6.24-r7.txt Could this be a symptom of a dying hard drive, Gnome being stupid, Gstreamer being stupid, or a combination of the three? I bought a SATA DVD burner; it should arrive in the next few days, so I will report back with the results for a native SATA drive that *should* be using libata, instead of this 2-year-old IDE drive that apparently doesn't like the framework.
(In reply to comment #8) > My config is available at: > http://dev.gentoo.org/~nightmorph/misc/config-2.6.24-r7.txt Sorry, that's http://dev.gentoo.org/~nightmorph/misc/config-2.6.25-r6.txt
OK, so it seems you have two (probably) unrelated issues. One with applications looking in the wrong place for the CD-ROM entirely. Another with playing CDs from applications that are looking in the right place. As to the first, just out of interest, how do you know they are looking at /dev/hda? I have an IDE DVD drive here too and I've tested and found mixed results trying to play audio CDs from it. Decibel works perfectly. However, totem doesn't work at all and gnome-cd sees the right device but doesn't recognize the CD, same as for you. I straced gnome-cd and it is talking to the right device, just not very successfully. As to the second issue, I've done some googling and a couple of things came up. First, a similar problem was reported by a kernel developer to lkml. The cause was found and fixed but for a different driver to yours. You should be able to test whether your problem is related by booting with the following parameter: libata.dma=1 Second, there are a number of reports of problems with this or similar models that were fixed by firmware upgrades. However, none that I saw that sound like your problem. Upgrading the firmware is a dangerous operation that could break the drive completely, so be careful if you try it. You may want to try the above first and/or wait until your new drive arrives, at least. See here for more info: https://bugs.launchpad.net/linux/+bug/75295/comments/97
(In reply to comment #10) > OK, so it seems you have two (probably) unrelated issues. One with applications > looking in the wrong place for the CD-ROM entirely. Another with playing CDs > from applications that are looking in the right place. > > As to the first, just out of interest, how do you know they are looking at > /dev/hda? I have an IDE DVD drive here too and I've tested and found mixed > results trying to play audio CDs from it. Decibel works perfectly. However, > totem doesn't work at all and gnome-cd sees the right device but doesn't > recognize the CD, same as for you. I straced gnome-cd and it is talking to the > right device, just not very successfully. Yay! It's reproduceable! :) Anyway, I can tell that it's /dev/hda for gnome-cd-player at least because when I first try to start it up with a CD in the drive, an error dialog pops up that says something to the effect of /dev/hda is not working; either it does not exist or you need to change it to the correct device. At that point, it offers the dropdown window with the drive name (not the path, but the name), but it still doesn't work. I admit that I'm just guessing that Totem has the same problem, since it's a Gnome app too. I'll try stracing later. > As to the second issue, I've done some googling and a couple of things came up. > First, a similar problem was reported by a kernel developer to lkml. The cause > was found and fixed but for a different driver to yours. You should be able to > test whether your problem is related by booting with the following parameter: > libata.dma=1 Thanks, I'll try this. > Second, there are a number of reports of problems with this or similar models > that were fixed by firmware upgrades. However, none that I saw that sound like > your problem. Upgrading the firmware is a dangerous operation that could break > the drive completely, so be careful if you try it. You may want to try the > above first and/or wait until your new drive arrives, at least. See here for > more info: > https://bugs.launchpad.net/linux/+bug/75295/comments/97 One thing that's making all this harder to strace and test is that the 2.6.25 kernel series sucks so much that it locks up my machine every other boot; any other kernel version doesn't have this problem. I do recall hearing reports even from the kernel devs that .25 is not exactly a shining piece of work. I went through and tested my hardware with various LiveCD utilities and such, and they all report no errors, so I surmise that it is the kernel that doesn't want to cooperate. I'll probably have to jump to .26-rc* and get more straces with that series.
Alright, I installed my new Asus SATA DVDRW drive today. Fired the thing up, loaded up Decibel, put a CD in, and it fetched the correct info from CDDB. It can see the disc. I click "play", and nothing happens; it thinks none of the tracks are playable. Same errors for gnome-cd-player, Totem, you name it. No progress. Now I'm wondering if the nVidia drivers for the MCP55 SATA controllers just completely suck. They work for my SATA hard disks, but optical drives are just right out. What gives? I can't seem to find any working app that can correctly access the drive if anything besides data is in it. I can browse data discs like ISOs or other backups correctly, but not DVDs or CDs. Arg. Something about accessing those types of discs . . . What kind of output do you need?
I'm experiencing the same problems with the same (MCP55) chipset and an SATA DVD burner (SAMSUNG). My dmesg output is here http://pastebin.com/m5b255ab3 and the kernel config is here: http://pastebin.com/m16659aab My kernel version is 2.6.25-gentoo-r6 #7 SMP PREEMPT on x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ AuthenticAMD GNU/Linux RipperX works, yet the described applications Josh mentioned produce exactly the same errors for me. (In reply to comment #12) > Alright, I installed my new Asus SATA DVDRW drive today. Fired the thing up, > loaded up Decibel, put a CD in, and it fetched the correct info from CDDB. It > can see the disc. I click "play", and nothing happens; it thinks none of the > tracks are playable. > > Same errors for gnome-cd-player, Totem, you name it. No progress. > > Now I'm wondering if the nVidia drivers for the MCP55 SATA controllers just > completely suck. They work for my SATA hard disks, but optical drives are just > right out. > > What gives? I can't seem to find any working app that can correctly access the > drive if anything besides data is in it. I can browse data discs like ISOs or > other backups correctly, but not DVDs or CDs. Arg. Something about accessing > those types of discs . . . > > What kind of output do you need? >
I'm using an Asus M2N-E with a MCP55 chipset and a Lite-On SATA DVDRW 00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1) 00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3) 00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3) 00:05.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3) [2:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1L BL05 /dev/sr1 Linux version 2.6.25-gentoo-r6 (root@death) (gcc version 4.3.1 (Gentoo 4.3.1 p1.0) ) #1 SMP Wed Jul 2 01:02:24 EDT 2008 No problems here playing CDs via xine. gnome-cd-player wouldn't let me select a device to use (I also have a SCSI CDROM, but it wouldn't let me select either),so it just kept giving me a drive error kernel config http://www.krwtech.com/ken/linux/config-2.6.25-gentoo-r6
I just thought maybe - if it is a problem that exists because of nvidias sata drivers, the hard discs have also changed? Maybe they are working slower than usual? I think my hard drives still work at the same speed they used to, but just to narrow the choices down: could you check that, Josh? My drives are as follows (sda => SATA2,320GB,16MB cache; sdb => SATA, 160GB, 8MB cache) talathar apps # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 1828 MB in 2.00 seconds = 914.27 MB/sec Timing buffered disk reads: 166 MB in 3.02 seconds = 55.06 MB/sec talathar apps # hdparm -tT /dev/sdb /dev/sdb: Timing cached reads: 1286 MB in 2.00 seconds = 643.14 MB/sec Timing buffered disk reads: 248 MB in 3.00 seconds = 82.63 MB/sec If it isn't the driver, it must be the applications, right? Maybe Sound-Juicer, Banshee, Totem use a different way of accessing the drive than for example RipperX does?
(In reply to comment #15) > I just thought maybe - if it is a problem that exists because of nvidias sata > drivers, the hard discs have also changed? Maybe they are working slower than > usual? I think my hard drives still work at the same speed they used to, but > just to narrow the choices down: could you check that, Josh? Nope, I haven't noticed any HDD performance changes from the <=.24 series to >=.25. I should mention that I've always used libata for the SATA hard disks; as I stated earlier, I switched the *IDE* cdrom drive to libata, not the SATA HDDs. Those have always worked just fine with libata. > If it isn't the driver, it must be the applications, right? Maybe Sound-Juicer, > Banshee, Totem use a different way of accessing the drive than for example > RipperX does? Very likely. It seems to be a combination of kernel driver issues and applications that aren't talking to the hardware correctly, regardless of the kernel. Basically, apps that aren't gstreamer-based have a better chance of working with the drive. Mplayer, Xine, RipperX, alsaplayer, and audacious have all been mentioned as "working" (well, with better results, at least).
Changed kernel to 2.6.26-rc8-zen1.0 and changed kernel config as follows: # # SCSI device support # CONFIG_RAID_ATTRS=m CONFIG_SCSI=y CONFIG_SCSI_DMA=y # CONFIG_SCSI_NETLINK is not set # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=y CONFIG_CHR_DEV_SCH=y # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # CONFIG_SCSI_MULTI_LUN=y # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # CONFIG_SCSI_SCAN_ASYNC is not set CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=y # CONFIG_SCSI_FC_ATTRS is not set CONFIG_SCSI_ISCSI_ATTRS=y # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set # CONFIG_SCSI_LOWLEVEL is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y CONFIG_SATA_PMP=y # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set # CONFIG_ATA_PIIX is not set CONFIG_SATA_NV=y # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ACPI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_SCH is not set CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # CONFIG_FUSION is not set Unfortunately still no change in the behaviour of sound-juicer and similar apps. Drive speeds are a little faster, though ;)
Problem fixed in new gstreamer version, synced yesterday, compiled perfect, works superb. Can't say which of the libraries/programs specifically did the trick, but it must be something that has changed between Gnome 2.20 and 2.22.3. As there were many changes with gst-plugins-* et al, it seems as if that is where the problem is/was.
Josh, Have you had the same results as Martin reported in comment #18 ?
(In reply to comment #19) > Have you had the same results as Martin reported in comment #18 ? Somewhat. I do notice that gstreamer-based apps can play CDs now. However, judging by the speed at which CDs are read or written, dma is turned off -- I have to boot with libata.dma=1 to get any use out of the drive. Still, with this option on, I get about medium reading and writing speeds, and CD/DVD playback works, so I guess I'm fairly happy with the results so far. I'm actually on 2.6.25-gentoo-r7, since I tried gentoo-sources-2.6.26, and that fails to work entirely. Not even the gstreamer improvements let me use the drive; .26 is a complete piece o' shi*-heezy. I hope there will be a new revision of the .26 series soon to fix this. In other news, I still can't use libata even with my new Asus SATA optical drive. However, there is some possibility that the fault lies with the SATA cables themselves; will test later today, since the replacements just arrived.
I'm a little confused, but.. shouldn't dma be selected automatically, especially with an SATA drive? You could try the zen-sources, available in the sunrise overlay, if you feel like experimenting, Josh ;)
(In reply to comment #21) > I'm a little confused, but.. shouldn't dma be selected automatically, > especially with an SATA drive? > You could try the zen-sources, available in the sunrise overlay, if you feel > like experimenting, Josh ;) The drive is an IDE drive. Since it's using libata, yes, DMA should be turned on. However, this is not the case unless I boot with the option enabled. Also, I don't plan on doing zen-sources - that thing's full of stuff I don't need or want; doesn't look like there are any relevant patches for my issues here. And no, zen-sources is not in Sunrise. Definitely not. I've swapped out my SATA cables for the Asus SATA dvd drive, and though now the i/o errors have disappeared from my logs, the drive still doesn't work with libata. Discs inserted can be seen; as always, the disc info is pulled from CDDB, but *nothing* can actually play the disc. No error messages of any kind in the apps, or in /var/log/messages or dmesg. I'm really at a loss here. It's the same issue I'm seeing in the .26 kernel: no error message on why the disc cannot be played.
Josh, Sorry I haven't been very helpful here. Would you consider taking this problem upsteam to bugzilla.kernel.org
(In reply to comment #23) > Josh, > > Sorry I haven't been very helpful here. Would you consider taking this problem > upsteam to bugzilla.kernel.org I would, but unfortunately I have no way of testing now. The MCP55 motherboard has since died a complete, terrible death. And anyway, the drive did seem to be working for the later .25 and .26 versions. The only thing libata won't work with is sata_nv, when attempting to use SATA HDDs and a SATA optical drive. However, the fault there may just be for sata_nv, not libata. Anyway, you can resolve this to whichever you want. I'm now using a newer board that properly supports AHCI for all devices, which libata likes very much.
ok, resolving for now.
