Re: 2.0.29 + ATAPI CD ( bug )
Erik Andersen (andersee@et.byu.edu)
Fri, 14 Feb 1997 21:28:06 -0700
On Feb 15, 1997, Spudgun wrote:
> Sorry to bother you all but
> Problem:
>
> I compiled 2.0.29 last night ( while sleeping so i missed any warnings etc)
> make mrproper
> make config
> nice make ; nice make modules ; make modules_install
>
> Today - i woke
> make zlilo
> rebooted to see it work - shutdown and went to work;
> when got home
>
> I had running Workman
> X
> pine
> that's about all
>
> I pressed stop on ( Joe Satriani ) workman and went to watch tv at about 21:24
> when i came back at 22:50 i found my computer writing to disk alot filling
> my syslog with ( about 2 times a second - about how often workman checks
> the cd status )
>
> Feb 14 21:24:01 potato kernel: hdc: media changed
> Feb 14 22:10:39 potato kernel: hdc: packet command error: status=0x51
> Feb 14 22:10:39 potato kernel: hdc: packet command error: error=0x30
> Feb 14 22:10:39 potato kernel: hdc: code: 0x70 key: 0x03 asc: 0x00 ascq: 0x00
> Feb 14 22:10:39 potato kernel: hdc: packet command error: status=0x51
> Feb 14 22:10:39 potato kernel: hdc: packet command error: error=0x50
> Feb 14 22:10:39 potato kernel: hdc: code: 0x70 key: 0x05 asc: 0x00 ascq: 0x00
> Feb 14 22:10:40 potato kernel: hdc: packet command error: status=0x51
> Feb 14 22:10:40 potato kernel: hdc: packet command error: error=0x50
> Feb 14 22:10:40 potato kernel: hdc: code: 0x70 key: 0x05 asc: 0x00 ascq: 0x00
> ........
> Feb 14 22:47:44 potato kernel: hdc: packet command error: status=0x51
> Feb 14 22:47:44 potato kernel: hdc: packet command error: error=0x50
> Feb 14 22:47:44 potato kernel: hdc: code: 0x70 key: 0x05 asc: 0x00 ascq: 0x00
>
-------------snip, snip, snip-------------
In 2.0.29 I made a minor change to the CDROMSTOP ioctl to avoid certain
errors on most ATAPI cdrom drives. Unfortunatly, not all ATAPI drives
do the Right Thing(tm), and a certain number of drives do very different
things. You should try adding the line:
#define IHAVEADOLPHIN
to the file linux/drivers/block/ide-cd.c and see if (after recompiling) your
problems go away. It appears you have a drive that behaves the same way
that the Dolphin does. Defining this adds in a tiny little bit of extra
code that most drives don't need (and which causes errors for others). I
believe this should fix things right up for you. If this doesn't work for
you, please let me know.
-Erik
--
Erik B. Andersen Web: http://www.et.byu.edu/~andersee/
2485 South State St. email: andersee@et.byu.edu or andersee@debian.org
Springville, Ut 84663 phone: (801) 489-1231
--This message was written using 73% post-consumer electrons--