Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 02-17-2005, 07:50 AM   #1
Senior Member
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
Upgrade to 2.6.10 broke /dev/cdrom

I had to upgrade to 2.6.10 to fix a nvidia driver problem, but it has now broke /dev/cdrom it is no longer a valid block device, also a X resolution of 1024x768 is no longer possible.

any ideas

Old 02-17-2005, 08:27 AM   #2
Senior Member
Registered: Feb 2004
Location: England
Distribution: Slackware 14.1
Posts: 1,469

Rep: Reputation: 46

Firstly install the latest version of udev from (do a package search in 'current' and use pkgtool)

In the 2.6 kernel you don't need to enable scsi=ide emulation for cd writers as in the 2.4 kernel. So you might encounter a problem if you are passing this parsmeter in via a boot loader (e.g lilo - /etc/lilo.conf)

Presuming it's an ide cdrom, it should be created as hdb or hdc etc...

OKay, and check your /etc/fstab file. You may find that /mnt/cdrom is trying to mount the wrong device from /dev

go into /dev and run 'ls -l hd*' What's the output?

Othere than that udev can be a bit funny at times. what's the output of 'dmesg |grep -i cdrom' (or similar).

Not sure about you X problem. Have you run the .sh file for Nvidia. I seem to remember that i had to get a moded version as it (the one from Nvidia) didn't work with Kernel 2.6.9. BUt that was a few months back and I presume they have shipped an update.

Bascailly the NVidia driver isn't too hot. IMHO. Have you moded the Xorg.conf file as outlined in the help files?

Anyway, you're not alone with these issues - I've experience a bit of both in the past.
Old 02-17-2005, 08:29 AM   #3
Senior Member
Registered: Feb 2004
Location: England
Distribution: Slackware 14.1
Posts: 1,469

Rep: Reputation: 46
sorry to be more concise, the device should be created as:

/dev/hdb or /dev/hdc (etc).

So you need this in your /etc/fstab file rather than /dev/cdrom which is actually just a symbolic link. Although it might be that udev is just not doing it's job....
Old 02-17-2005, 08:47 AM   #4
Registered: Dec 2004
Distribution: SuSE, RedHat, ubuntu, Debian
Posts: 734

Rep: Reputation: 30
I have a similar problem. I upgraded to 2.6.10-1.766 which I obtained from fedora (stable) and now my cdrw can't be seen. I edited /etc/fstab and even checked storage.policy.fdi, but didn't see anything wrong. fstab-sync keeps deleting my entry even after I run fstab-sync. My cdrw is SCSI. All the modules show loaded and the o/s boot detection showed the drive/controller, etc. My SCSI tape drive works fine though.

With regards to your problem....

What exact kernel did you use [2/6/10.?]?
Where did you get the file(s) [exact ftp/url]?
What kind of update packages did you use?
Where you performing the updates as Super User (root) or user?
What were the commands that you used?
Were there any error messages? If so, please post them.
What version of X-Windows System are you running now (XFree86 or
What model video card do you have, pci/agp 4x/8x?
What version video driver was loaded?
Where did the video driver come from?
Did you try reloading the video driver?
Did you try running the X config?
Did you try editing /etc/fstab ? [you have to reboot or type "mount -a" after you save the changes]
Did you check your XFree86 config?
Did you run the various checks to see if the appropriate drivers and devices are detected or loaded?

Try these commands from a terminal window or console. Each will output the findings to a file with a .messages extension....

uname -a > uname-a.messages
dmesg > dmesg.messages
dmesg | grep bus > bus.messages
lsmod > lsmod.messages
lspci > lspci.messages
cat /proc/interrupts > interrupts.messages
cat /proc/iomem > iomem.messages

If this is a 3D card, also do this command...

glxinfo > glxinfo.messages

Post your /etc/fstab
Old 02-17-2005, 09:36 AM   #5
Senior Member
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Original Poster
Rep: Reputation: 137Reputation: 137
I have got them both working, but some new problems have been noticed.

Satinet, thank you hdd=ide-scsi was in lilo.conf and the link from /dev/cdrom to /dev/hdd was broken.

t3gah, thank you, I had done most of what you suggested, but to fix it I copied over a backup of my xorg.conf file.

The new problem is system freezes, and I have to use the reset button.

Secondly glxgears is sloooooow at around 200fps, it should be around 2400 as it is in mandrake.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
CDROM mounting problem => /dev/cdrom is not a valid block device Vizy Linux - Hardware 8 11-04-2010 05:46 PM
I cannot access EITHER CD drive! And there's no /dev/hdc or /dev/hdd or /dev/cdrom! Dmalic Linux - Hardware 13 11-18-2005 08:11 PM
mounting CD, CDRW... /dev/cdrom -> /dev/hda kersten78 Slackware 9 09-24-2004 12:53 AM
/dev/cdrom & /dev/hdc missing! Lord_Devi Slackware 4 06-25-2004 10:17 AM
mounting 2 ide-scsi devices /dev/cdrom and /dev/cdrom1 issue penguin123 Linux - Hardware 3 09-26-2003 09:36 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:12 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration