Announcement

Collapse
No announcement yet.

[solved: libata kernel patch] Feisty can't find CDROM and DVD writer

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [solved: libata kernel patch] Feisty can't find CDROM and DVD writer

    I have my HP dvd writer dvd200i and MTRP 56x CDROM om my box, kernel 2.6.20-8, latest updates. During boot feisty booting very looooong time, trying to probe ata drives. Here are some logs from dmesg:

    dmesg | grep ata

    [ 0.000000] BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
    [ 29.068133] Memory: 509292k/524224k available (1903k kernel code, 14296k reserved, 849k data, 324k init, 0k highmem)
    [ 29.068158] .data : 0xc02dbfa3 - 0xc03b0434 ( 849 kB)
    [ 33.323096] libata version 2.00 loaded.
    [ 33.500185] ata_piix 0000:00:1f.1: version 2.00ac7
    [ 33.500368] ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
    [ 33.500465] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
    [ 33.500490] scsi0 : ata_piix
    [ 63.788223] ata1.00: ATAPI, max MWDMA2
    [ 63.952340] ata1.01: ATAPI, max UDMA/33
    [ 64.116060] ata1.00: configured for MWDMA2
    [ 64.279827] ata1.01: configured for UDMA/33
    [ 64.279854] scsi1 : ata_piix
    [ 64.455210] pata_pdc2027x 0000:02:01.0: version 0.74-ac5
    [ 64.554419] pata_pdc2027x 0000:02:01.0: PLL input clock 16549 kHz
    [ 64.589368] ata3: PATA max UDMA/133 cmd 0xE08C17C0 ctl 0xE08C1FDA bmdma 0xE08C1000 irq 18
    [ 64.589426] ata4: PATA max UDMA/133 cmd 0xE08C15C0 ctl 0xE08C1DDA bmdma 0xE08C1008 irq 18
    [ 64.589447] scsi2 : pata_pdc2027x
    [ 64.750433] ata3.00: ATA-7, max UDMA/100, 234493056 sectors: LBA48
    [ 64.750440] ata3.00: ata3: dev 0 multi count 16
    [ 64.758331] ata3.01: ATA-7, max UDMA/133, 320173056 sectors: LBA48
    [ 64.758335] ata3.01: ata3: dev 1 multi count 16
    [ 64.766316] ata3.00: configured for UDMA/100
    [ 64.774300] ata3.01: configured for UDMA/133
    [ 64.774330] scsi3 : pata_pdc2027x
    [ 65.742899] EXT3-fs: mounted filesystem with ordered data mode.
    [ 94.625326] ata1.00: qc timeout (cmd 0xa0)
    [ 94.625346] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
    [ 94.625352] ata1.00: (BMDMA stat 0x65)
    [ 94.625361] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
    [ 101.614877] ata1: port is slow to respond, please be patient (Status 0xd8)
    [ 124.596471] ata1: port failed to respond (30 secs, Status 0xd8)
    [ 124.596483] ata1: soft resetting port
    [ 154.887208] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x1)
    [ 154.887216] ata1.00: revalidation failed (errno=-5)
    [ 154.887225] ata1: failed to recover some devices, retrying in 5 secs
    [ 159.883729] ata1: soft resetting port
    [ 190.503026] ata1.00: configured for MWDMA2
    [ 190.666773] ata1.01: configured for UDMA/33
    [ 190.666822] ata1: EH complete
    [ 220.656817] ata1.00: qc timeout (cmd 0xa0)
    [ 220.656839] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
    [ 220.656844] ata1.00: (BMDMA stat 0x65)
    [ 220.656853] ata1.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 254 in
    [ 227.646367] ata1: port is slow to respond, please be patient (Status 0xd8)
    [ 250.627965] ata1: port failed to respond (30 secs, Status 0xd8)
    [ 250.627978] ata1: soft resetting port
    [ 256.606893] EXT3-fs: mounted filesystem with ordered data mode.
    [ 256.632801] EXT3-fs: mounted filesystem with ordered data mode.
    [ 256.683813] EXT3-fs: mounted filesystem with ordered data mode.
    [ 256.933135] EXT3-fs: mounted filesystem with ordered data mode.
    [ 256.947070] EXT3-fs: mounted filesystem with ordered data mode.
    [ 256.977834] EXT3-fs: mounted filesystem with ordered data mode.
    [ 280.910881] ata1.00: revalidation failed (errno=-2)
    [ 280.910893] ata1: failed to recover some devices, retrying in 5 secs
    [ 285.907219] ata1: soft resetting port
    [ 316.526584] ata1.00: configured for MWDMA2
    [ 316.690452] ata1.01: configured for UDMA/33
    [ 316.690490] ata1: EH complete


    My lspci:

    00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 03)
    00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP Bridge (rev 03)
    00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 12)
    00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 12)
    00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 12)
    00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 12)
    00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 12)
    00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 12)
    00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 Audio (rev 12)
    01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon 7500]
    02:01.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02)
    02:05.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)


    cdrecord dev=help :

    Supported SCSI transports for this platform:

    Transport name: sg
    Transport descr.: Generic transport independent SCSI
    Transp. layer ind.:
    Target specifier: bus,target,lun
    Target example: 1,2,0
    SCSI Bus scanning: supported
    Open via UNIX device: not supported

    Transport name: ATA
    Transport descr.: ATA Packet specific SCSI transport
    Transp. layer ind.: ATAPI:
    Target specifier: bus,target,lun
    Target example: ATAPI:1,2,0
    SCSI Bus scanning: supported
    Open via UNIX device: not supported

    Transport name: ATA
    Transport descr.: ATA Packet specific SCSI transport using sg interface
    Transp. layer ind.: ATA:
    Target specifier: bus,target,lun
    Target example: 1,2,0
    SCSI Bus scanning: supported
    Open via UNIX device: not supported

    Transport name: RSCSI
    Transport descr.: Remote SCSI
    Transp. layer ind.: REMOTE:
    Target specifier: rscsi@host:bus,target,lun
    Target example: REMOTE:rscsi@host:1,2,0
    SCSI Bus scanning: supported
    Open via UNIX device: not supported


    scsiadd -p :

    Attached devices:
    Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: E-IDE Model: CD-ROM 56X/AKH Rev: A80
    Type: CD-ROM ANSI SCSI revision: 05
    Host: scsi0 Channel: 00 Id: 01 Lun: 00
    Vendor: HP Model: DVD Writer 200j Rev: 1.36
    Type: CD-ROM ANSI SCSI revision: 05
    Host: scsi2 Channel: 00 Id: 00 Lun: 00
    Vendor: ATA Model: SAMSUNG SP1203N Rev: TL10
    Type: Direct-Access ANSI SCSI revision: 05
    Host: scsi2 Channel: 00 Id: 01 Lun: 00
    Vendor: ATA Model: Maxtor 6Y160P0 Rev: YAR4
    Type: Direct-Access ANSI SCSI revision: 05

    But I can't find any sr0, sr1, sg0 or sg1 in my /dev!

    It looks like that ata modules are corrupted or not well developed. I did some research on kernel forums and found that work on new ata ide modules not finished yet. Moreover, the same issue from time to time happens on dupper drake and edgy. I tried to install 2.6.17 kernel to see what happend, but can't do it regardless of udev version which is newer.
    I can't understand is it kernel problem or udev? Who has some kind of receipt on this?

    #2
    Re: ata port is slow to respond

    BTW, I've just downloaded and installed new 2.6.20-9 kernel, but it doesn't resolve this problem.

    Comment


      #3
      Re: ata port is slow to respond

      Wow, I found the solution!!!!

      The problem was the follows (from http://www.thinkwiki.org/wiki/Proble...not_recognized):

      "The ata_piix SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the ide driver is compiled as a module and loaded after ata_piix, the DVD drive will not be recognized by either driver."

      I've just did:

      echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u

      After reboot my cdrom and dvd drives were recognized correctly, I have them as /dev/hda and /dev/hdb.

      Life is beautiful!!!

      Comment


        #4
        Re: Problem with CDROM and DVD writer

        I have to say that I jumped to conclusion before time. Only once my drives was recognized correctly and never after. I even tried to compile new 2.6.21-rc1 kernel from kernel.org but situation happened again. Nobody has the same or similar problem?

        Comment


          #5
          Re: Feisty can't find CDROM and DVD writer

          Any suggestions? Help me, pls!!!

          Comment


            #6
            Re: Feisty can't find CDROM and DVD writer

            I really don't understand what is going on with my box. Today I ran Herd 5 live cd and everything was cool - cd and dvd drives was recognized as hda and hdb. But (!) after installing on hard drive they are disappeared and annoying messages like "ata1: port is slow to respond, please be patient (Status 0xd8)" appeared again and again!!! I only discovered that cdrom drives on Herd 5 live cd activated by ide_cdrom module in kernel.

            Guys, can anybody tell a couple of sophisticated words about that?

            Comment


              #7
              Re: Feisty can't find CDROM and DVD writer

              Hmmm, it looks like the same bug as I have: https://launchpad.net/ubuntu/+source....15/+bug/53754
              but with 2.6.15 kernel. And here is a thread on ubuntu-mailing list with the same problem: https://lists.ubuntu.com/archives/ke...ch/025438.html. Still no solution. The only way to solve is rmmod ati_piix and then depmod ati_piix. After that cd and dvd drives become recognized. But start k3b takes still a very long time due to hardware probing (starting hald device manager and then udevs).

              Comment


                #8
                Re: Feisty can't find CDROM and DVD writer

                I discovered that I have also messages like: intel_rng: FWH not detected. I blacklisted intel_rng module and after reboot I've seen my cd and dvd drives after some time (what a ...?). What was a reason for that? It is unclear for me. But scary messages still appear:

                [ 1052.762322] ata3: port is slow to respond, please be patient (Status 0xd8)
                [ 1075.743913] ata3: port failed to respond (30 secs, Status 0xd8)
                [ 1075.743927] ata3: soft resetting port
                [ 1076.227231] ata3.01: failed to IDENTIFY (I/O error, err_mask=0x1)
                [ 1076.227239] ata3.01: revalidation failed (errno=-5)
                [ 1076.227249] ata3: failed to recover some devices, retrying in 5 secs
                [ 1081.223750] ata3: soft resetting port
                [ 1081.870978] ata3.00: configured for UDMA/33
                [ 1082.034741] ata3.01: configured for PIO2
                [ 1082.034787] ata3: EH complete

                I think it is not a solution. Something else must be a reason for it.

                Comment


                  #9
                  Re: Feisty can't find CDROM and DVD writer

                  Note to ubuntu developers:

                  Please see the thread on linux-ide list: http://www.spinics.net/lists/linux-ide/msg08815.html or full massages: http://www.spinics.net/lists/linux-i...ads.html#08815

                  The resume is as follows:

                  My CDROM drive works just fine in PIO mode with pdc202xx_new
                  IDE driver (it doesn't support ATAPI DMA at the moment) and fails
                  with pata_pdc2027x libata (even with DMA blacklist patch from Albert).

                  So, to make it available on my box I had to disable ata_piix, configure the IDE pdc202xx_new driver and remove the libata pata_pdc2027x driver from kernel config, and recompile kernel.
                  After that I've got my drives as /dev/hda and /dev/hdh.

                  I think it is good idea to wait a little and do not enable new libata modules in the new kernels for feisty. I hope that ubuntu developers read this forum from time to time.



                  Comment


                    #10
                    Re: Feisty can't find CDROM and DVD writer

                    I'm suffering the same problem, I believe. In Edgy, the same Asus ATA CD/DVD drive functioned perfectly, and it runs fine under Elive, so I know the hardware is fine. Here's what gnomebaker pukes up when I try to burn a CD:

                    wodim: No write mode specified.
                    wodim: Asuming -tao mode.
                    wodim: Future versions of wodim may have different drive dependent defaults.
                    scsidev: '0,1,0'
                    scsibus: 0 target: 1 lun: 0
                    TOC Type: 3 = CD-ROM XA mode 2
                    scsidev: 'ATA:0,1,0'
                    devname: 'ATA'
                    scsibus: 0 target: 1 lun: 0
                    wodim: No such file or directory.
                    Cannot open SCSI driver!
                    For possible targets try 'wodim --devices' or 'wodim -scanbus'.
                    For possible transport specifiers try 'wodim dev=help'.
                    For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
                    the wodim documentation.

                    In System Settings, the CD ROM drive is "enabled" and shows no signs of a problem. For some reason it is mounted at /proc -- is that where Ubuntu wants it? I'm surprised it is not at /media with the hard drives. Oh well, I don't think that matters.

                    I'll be alert for a fix to this. Good thing I have elive on the other drive!

                    Comment


                      #11
                      Re: Feisty can't find CDROM and DVD writer

                      No, it definitely shouldn't be mounted under /proc. Try making a fstab entry for it or mounting it by going to media:/ in Konqueror.
                      For external use only.

                      Comment


                        #12
                        Re: [partially solved] Feisty can't find CDROM and DVD writer

                        Well, after series of tests here is the final opinion from linux-ide people:

                        http://bugzilla.kernel.org/show_bug.cgi?id=8244

                        --> begin>
                        Albert Lee wrote:
                        > > Hi Yarema,
                        > >
                        > > Thanks for the detailed log.
                        > > It looks like the bad INQUIRY command
                        > > "CDB (4:0,1,0) 12 01 00 00 fe 00 00 00 00" (INQUIRY, length=254, EVPD=1)
                        > > is coming from the user space, not the SCSI mid-layer.
                        > >
                        > > I guess two problems together caused this bug:
                        > > 1. Ubuntu Linux issues an incorrect INQUIRY command to the drive.
                        > > (Other distros seem to have the INQUIRY correct.)
                        > > 2. The incorrect INQUIRY happens to cause the AOpen drive frozen.
                        > > (The HP drive is immune from the incorrect INQUIRY command.
                        > > "check condition" is returned for the bad INQUIRY.)
                        > >
                        > > We have two possible solutions here:
                        > > a. Patch Ubuntu, such that the incorrect INQUIRY is fixed.
                        > > b. Patch kernel, such that the AOpen drives are blacklisted.
                        > > Each INQUIRY is inspected for the blacklisted drives.
                        > > If the INQUIRY looks wrong, the INQUIRY is rejected.
                        > >
                        > > I guess a. is the preferred solution...

                        I second Albert's opinion. Please report this to ubuntu people so that
                        the origin of the problem can be fixed.

                        Thanks a lot. I admire your ability and patience in tracking these
                        difficult issues. :-)
                        --> end>


                        My question to k/ubuntu developers : Can you figure out how to find solution of this problem?



                        Comment


                          #13
                          Re: [partially solved] Feisty can't find CDROM and DVD writer

                          I suggest filing a bug report over at Launchpad.
                          Please include a link to the bug report you filed at bugzilla.kernel.org! It'll be very helpful to the guys at Launchpad.
                          For external use only.

                          Comment


                            #14
                            Re: [partially solved] Feisty can't find CDROM and DVD writer

                            I did it, thanks. Let's wait

                            Comment


                              #15
                              Re: [partially solved] Feisty can't find CDROM and DVD writer

                              I have the same problem, and have submitted Bug Report 96286 accordingly.

                              Comment

                              Working...
                              X