View Single Post
Old 03-24-2013, 03:49 PM   #238
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,903
Karma: 6677559
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Quote:
Originally Posted by eureka View Post
Maybe CD-ROM was recognized as not the /dev/sr1, but as other device (wild guess: /dev/sr0 or dev/scd0).
Yeah, maybe... but then why is it reported wrongly in /proc/sys/dev/cdrom/info? Or - what would the point of the info thingy be, if it reports wrong information?

BTW - I did have a similar (but not identical) issue on MacBook Pro with Kubrick 2.1. There, the info would simply be completely empty (="", meaning no devices found). This was the entire reason behind using a brand-new kernel, and enabling pretty much anything CD-ROM related in it.

But here, the case seems to be that the system *knows* it has a CD drive, but can't use it properly for whichever reason.

Recountryman: do you mind trying again, but instead of shutting down, issuing the following commands:
Code:
ls /dev/sr*
ls /dev/scd*
mount /dev/sr1 /media/cdrom
mount -t iso9660 -o ro /dev/sr1 /media/cdrom
dmesg|tail -n 10
Please post the exact output (or pictures of the screen)... Thanks!
And oh, of course "cat /proc/sys/dev/cdrom/info" would be helpful too

Last edited by ixtab; 03-24-2013 at 04:00 PM.
ixtab is offline   Reply With Quote