Why no CDrom when upgrading to 2.6.17.13smp kernel?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Why no CDrom when upgrading to 2.6.17.13smp kernel?
A problem revisited.
Having followed previous advice to include myself in /etc/groups I have been able to play CD's in Slackware 11. Ok until today when I upgraded to the 2.6.17.13smp kernel, followed all the instructions, but now I get the following message when I try to play a CD:
CD-Rom read or access error (no disc indrive) when there is
Make sure you have access permissions to /dev/cdrom.
I have used Slackware for 12 maybe 13 years and I used to get around the problem by chmodding /dev/cdrom to root permissions. It's not there any longer so I am stuck.
My box, with dual processor goes like stink since I upgraded, it really would be nice to play my CD's if you can please help me.
It often makes me wonder why I stick with Slackware, I love it, I have the T shirts, it's bloody frustrating when other distros do simple things but in Slackware it has to be fixed. With your help this old geezer will get there.
Which kernel did you upgrade from? Is your cd drive a regular cd drive or cdrw? You may already know, but if you go from 2.4 to 2.6 with a cdrw drive, it's a different device node in /dev. Goes from /dev/sr* to /dev/hd*.
Well this is wrong and you should revert to the original line "cdrom::19:graham,ann". The group name "cdrom" has nothing to do with the device "cdrom" or "hdc" the way you think.
I was wondering, with that 2.6 kernel, did you enable udev? With udev you should have symbolic links automatically pointing to your CDROM device: run
Code:
chmod +x /etc/rc.d/rc.udev
to enable udev on the first reboot of your machine.
/etc/rc.d/rc.udev looks like this -rwxr-xr-x root root etc
/etc/rc.d/rc.udev.new has the same permissions
/dev there are no entries for cdrom, hdc or scd0
I have tried symbolic links like ln -sf scd0 cdrom
I don't know the answer but I think the clue is that I get the same error message when running KDE as root as I do when a user. If I edit a file relating to cdrom, a window pops up and asks what I want to do with the disk in the drive.
I am lost and struggling despite having read the things I considered relevant.
BTW it's a DVD rw don't know if that makes a difference.
Are you running both udev and hotplug? If so, try disabling hotplug and see if that helps.
Also, double check the kernel config to ensure that the support for the device has been compiled in. I know it's a long shot but it's possible that it was missed.
Also, just a personal preference, but in fstab I would change the "owner" to "user"
/etc/rc.d/rc.udev looks like this -rwxr-xr-x root root etc
/etc/rc.d/rc.udev.new has the same permissions
If you have a rc.udev.new that means you upgraded Slackware some time ago, and failed to replace the old rc.udev with the new rc.udev script.
This will seriously break udev functionality.
Try fixing this problem first, and then examine progress on the DVD device.
Also, please check any other .new files against their predecessors - you might miss more functionality than just udev:
It's abviously udev that isn't working, as Alien said. You need to move rc.udev.new to rc.udev, and reboot. You need to make sure /etc/rc.d/rc.udev is executable. If it is, udev will run and hotplug won't. If it isn't, hotplug will run.
I ran lilo.config again using pkgtool and omitted "hdc=ide-scsi" option and /dev/+hdc was created at reboot, the dvd drive is up and running again. Editing this from /etc/lilo.conf, one of the first suggestions didn't achieve the same result.
Thanks again, couldn't have got there without your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.