linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 12144] optiarc bc-5500A can't read audio cds
Date: Thu, 18 Dec 2008 10:07:21 -0800 (PST)	[thread overview]
Message-ID: <20081218180721.61C2811D108@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12144-11633@http.bugzilla.kernel.org/>

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





------- Comment #21 from manoet.ita@gmail.com  2008-12-18 10:07 -------
I suppose I had to do just a rmmod ata_piix, but anyway, I did how you said and
I had recompiled my kernel.

#cdplay /dev/hda
[   91.441974] ATAPI device hda:
[   91.445955]     Invalid command operation code -- (asc=0x20, ascq=0x00)
[   91.445955]     the failed "play audio msf" packet command was:
[   91.445955]     "47 00 00 00 02 00 28 35 00 00 00 00 00 00 00 00"
cdplay: ioctl cdromplaymsf: Input/output error


#dmesg | grep hda
[    3.932386] hda: Optiarc BD ROM BC-5500A, ATAPI CD/DVD-ROM drive
[    4.604110] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    4.604230] hda: UDMA/33 mode selected
[    5.189033] hda: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
[   75.576637] hda: packet command error: status=0x51 { DriveReady SeekComplete
Error }
[   75.576656] hda: packet command error: error=0x54 { AbortedCommand
LastFailedSense=0x05 }
[   75.577371] ATAPI device hda:
[   91.441485] hda: packet command error: status=0x51 { DriveReady SeekComplete
Error }
[   91.441503] hda: packet command error: error=0x54 { AbortedCommand
LastFailedSense=0x05 }
[   91.441974] ATAPI device hda:


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-12-18 18:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12144-11633@http.bugzilla.kernel.org/>
2008-12-04 14:15 ` [Bug 12144] optiarc bc-5500A can't read audio cds bugme-daemon
2008-12-04 14:40 ` bugme-daemon
2008-12-04 17:13 ` bugme-daemon
2008-12-04 18:18 ` bugme-daemon
2008-12-04 18:19 ` bugme-daemon
2008-12-14 19:11 ` bugme-daemon
2008-12-14 21:16 ` bugme-daemon
2008-12-14 23:27 ` bugme-daemon
2008-12-15  6:13 ` bugme-daemon
2008-12-16 19:12 ` bugme-daemon
2008-12-16 19:14 ` bugme-daemon
2008-12-16 19:27 ` bugme-daemon
2008-12-16 21:27 ` bugme-daemon
2008-12-16 21:28 ` bugme-daemon
2008-12-16 21:29 ` bugme-daemon
2008-12-16 22:02 ` bugme-daemon
2008-12-18 15:24 ` bugme-daemon
2008-12-18 15:45 ` bugme-daemon
2008-12-18 18:07 ` bugme-daemon [this message]
2008-12-22  6:20 ` bugme-daemon
2008-12-22  6:21 ` bugme-daemon
2008-12-22  6:22 ` bugme-daemon
2008-12-22  6:23 ` bugme-daemon
2008-12-26 20:30 ` bugme-daemon
2008-12-26 20:31 ` bugme-daemon
2008-12-27  8:27 ` bugme-daemon
2008-12-27  8:29 ` bugme-daemon
2008-12-27 12:32 ` bugme-daemon
2008-12-27 12:32 ` bugme-daemon
2008-12-27 19:17 ` bugme-daemon
2008-12-28  8:45 ` bugme-daemon
2009-01-17 11:26 ` bugme-daemon
2009-01-18 17:49 ` bugme-daemon
2009-01-18 18:42 ` bugme-daemon
2009-01-19 15:00 ` bugme-daemon
2009-05-29  7:28 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081218180721.61C2811D108@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).