I've had similar experiences with my Acer Powermate 7200 and a HP Omnibook 4150 in regards to stupid cdrom/dvd issues. In both cases, it looks like the manufacturer took a "creative" approach to implementing the atapi standard on the drives. The HP would go into a blocked I/O mode (Indicated by a "D" in the state field in top) from anywhere to 30 seconds to 3 minutes before the cdrom would suddenly just come to life and be okay. My acer just generates lots of errors on the console, (atapi driver complaining that the drive is returning unknown status codes) but it reads (if a bit slowly) just my $.02 Tim. -----Original Message----- From: Trevor Farrell [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 19, 2000 7:59 AM To: [EMAIL PROTECTED] Subject: Re: [expert] cdrecord problem Hoping this adds something to the tracking down of the problem and doesn't muddy the water more... I have an LG (Goldstar) IDE cd burner, similar to Rog's (bios ver 1.05 instead of his 1.07, but otherwise the same) and I get the same error. I also find that after burning a cd, the read light stays on and the CD burner is locked up. The machine keeps trying to reset the scsi line, but can't, so it is slow as a wet week, and the only thing that fixes it is to reboot. If I specify the -eject option to cdrecord, all is well! the cd ejects at the end of the burn, and the burner is ok. I also get a similar error on a Toshiba Satelite Pro 4280 laptop, but it has no cd burner, but a cd/dvd instead. This error just comes up at times when I'm trying to read a cd. Next time it happens I'll try to copy it and mail to the list. I never had this problem with 7.1 on either machine. If it wasn't for KDE2 I would go back to 7.1 this instant! Trevor
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
