LinuxQuestions.org - Slackware64-current doesn't read cd-r disks as well as slack 12.1 does(?)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware64-current doesn't read cd-r disks as well as slack 12.1 does(?) (https://www.linuxquestions.org/questions/slackware-14/slackware64-current-doesnt-read-cd-r-disks-as-well-as-slack-12-1-does-801015/)

Slackware64-current doesn't read cd-r disks as well as slack 12.1 does(?)

I have slackware 12.1 installed along with slackware64-current.
I have bunch of old cd-s with data backups. Yesterday i had to copy few files from them, but slackware64-currents hal just ignored the cd-s spitting out some errors in /var/log/messages and /var/log/syslog.

Code:

Apr  8 18:01:11 masin kernel: sr 1:0:0:0: [sr0] Unhandled sense code

Apr  8 18:01:11 masin kernel: sr 1:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08

Apr  8 18:01:11 masin kernel: sr 1:0:0:0: [sr0] Sense Key : 0x3 [current]

Apr  8 18:01:11 masin kernel: sr 1:0:0:0: [sr0] ASC=0x11 ASCQ=0x5

Apr  8 18:01:11 masin kernel: sr 1:0:0:0: [sr0] CDB: cdb[0]=0x28: 28 00 00 05 21 a2 00 00 01 00

/var/log/messages lines 11866-11904/11904 (END)





Apr  8 18:01:11 masin kernel: end_request: I/O error, dev sr0, sector 1345160

Apr  8 18:01:11 masin kernel: Buffer I/O error on device sr0, logical block 336290

/var/log/syslog lines 939-988/988 (END)

I rebooted to slackware 12.1. There, hal detected, mounted these disks with no problem. Copying succeeded also. That's all. What to expect? Can newer software degrade cd/dvd-drives reading performance?

Hi,

I would look at the driver/firmware for the device. Confirm the correct driver is loaded for your device when using '-current'.

@veeall:

This just recently started happening to me after one
of the updates (using -current 32bit). The CDs used
to work just fine and now they do not automount and
I get similar errors in the log.

For me, manually mounting them as root using the
"-t iso9660" option works just fine.

Searching google for:
"kde4 lost automount" and "hal automount util-linux-ng"
comes back with a few hits that seem similar...

But it is still not working here...