public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: IDE CD problems in 2.6.13rc6
Date: Sun, 14 Aug 2005 20:55:35 +0100	[thread overview]
Message-ID: <200508142055.35731.nick@linicks.net> (raw)

Voluspa wrote:

> 
> The "hdparm -I /dev/hdc"
> 
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> de: failed opcode was: 0xec
> 
> Is present on all kernels that I have locally (oldest 2.6.11.11)
> so it is not related to the threadstarters problems, it seems.

Hi all,

Maybe teaching you all to suck eggs here, but I used to get this a lot on my 
CD's - KDE ran some probe and as the CD[s] where empty logs filled up rapidly 
with that error.  I thought the[a] drive was duff, so bought a new CD-RW.

Made no difference :-/  I then investigated further, and read that instead of 
the SCSI emulation, it was superceded by IDE-CD.

kernel 2.6.12.3

Kernel command line: BOOT_IMAGE=Nicks ro root=303 hdc=ide-cd hdd=ide-cd

Fixed the issue for me.  But as I say, teaching to suck eggs, but I thought I 
would mention it.

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

             reply	other threads:[~2005-08-14 19:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 19:55 Nick Warne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-15 18:30 IDE CD problems in 2.6.13rc6 Nick Warne
2005-08-14 22:51 Voluspa
2005-08-15  0:37 ` Alan Cox
2005-08-15  0:53   ` Voluspa
2005-08-14 20:10 Nick Warne
2005-08-14 19:30 Voluspa
2005-08-14 17:43 Voluspa
2005-08-13 23:29 Dave Jones
2005-08-14  0:26 ` Con Kolivas
2005-08-14  0:30   ` Con Kolivas
2005-08-14 13:53     ` Alan Cox
2005-08-14 11:35 ` Bartlomiej Zolnierkiewicz
2005-08-14 13:46   ` Alan Cox

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=200508142055.35731.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=linux-kernel@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