Re: IDE CD problems in 2.6.13rc6

[Nick Warne <nick@linicks.net>]

I just remember a path I took when resolving the issue further to my post 
below.

Here is what man hdparm says on -i and -I:

       -i     Display  the  identification info that was obtained from the 
drive at boot time,
              if available.  This is a feature of modern IDE drives, and may 
not be  supported
              by  older  devices.   The  data returned may or may not be 
current, depending on
              activity since booting the system.  However, the current  
multiple  sector  mode
              count is always shown.  For a more detailed interpretation of 
the identification
              info, refer to AT Attachment Interface for Disk Drives (ANSI ASC 
X3T9.2  working
              draft, revision 4a, April 19/93).

       -I     Request identification info directly from the drive, which is 
displayed in a new
              expanded format with considerably more detail  than  with  the  
older  -i  flag.
              There is a special "no seatbelts" variation on this option, 
-Istdin which cannot
              be combined with any other options, and which  accepts  a  drive  
identification
              block  as  standard  input instead of using a /dev/hd* 
parameter.  The format of
              this block must be exactly the same as that found in  
the  /proc/ide/*/hd*/iden­
              tify  "files".   This  variation  is  designed for use with 
"libraries" of drive
              identification information, and can also be used on ATAPI drives 
which may  give
              media errors with the standard mechanism.

Note the last sentence:

' This  variation  is  designed for use with "libraries" of drive 
identification information, and can also be used on ATAPI drives which may  
give  media errors with the standard mechanism.

Nick

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..."

-------------------------------------------------------

-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/