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.
I've installed my own kernel 2.6.10 on slack10.1 (pat didn't include my sound card in the generic kernel)
Here's my problem when I try to mount a cdrom
Code:
Could not mount device.
The reported error was:
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
so why can't I mount my cdrom as a normal user???? --> can't burn cds now of course Oh and if I pass scsi emulation 'hdc=ide-scsi' to my grub line, hdc dissappears!
Change the umask=0 to umask=000. You might also want to also change defaults for /mnt/Data to noauto. This way you can mount/unmount when you want, just a suggestion. BTW, I wouldn't even use the umask for a cdrom, but that's a personal preference. Remove it and you should be able to mount/unmount the cdrom as whomever is logged on at the time. Matter of fact your fstab looks a bit "complicated" to me, as an example here's mine:
Everything works JUST like I want it to. You might also want to "clean up" your sda* mounts. The way they are set only the user that mounts them can unmount them, and with defaults that might only be root (I'm not sure on that one).
Quote:
Originally posted by Mr_C Oh and if I pass scsi emulation 'hdc=ide-scsi' to my grub line, hdc dissappears! also my usb devices sda** have dissappeared
While you can use ide-scsi with a 2.6 kernel, the question begs to be asked, "Why?". While the ATAPI driver in the kernel may not be perfect for CD burning right now, it's better than scsi emulation, IMHO. I've been using it since I my first 2.6 compile (2.6.5) and it's worked, barring the 2.6.8 - 2.6.9 thing, like a champ. I'm now using 2.6.11 with no problems. You might also want to look at your kernel config and check out the SCSI and USB section to make sure of your settings. The one thing you DON'T want to use in the USB section is UB, look for this in the USB section:
Quote:
Low Performance USB Block driver
CONFIG_BLK_DEV_UB:
This driver supports certain USB attached storage devices such as flash keys.
Warning: Enabling this cripples the usb-storage driver.
Originally posted by Mr_C change to umask=000 makes no difference.
Still can't mount cdrom, not even root can 'mount /mnt/cdrom'
Looking at your fstab, /mnt/cdrom is "pointing" to /dev/cdrom, which should be a symlink in /dev that points to the actual device node. So there are a couple of things you might want to check.
1.) Make sure you actually have /dev/cdrom.
2.) If you do check to see what it points to by:
actually by removing the umask option, eveything has returned to normal (hmm I didn't have to recomiple my kernel again....) -- keefaz
K3b refused to see the cdrom, so I deleted my user settings and lauched it again and it found my burner.
Also discovered that usb drives are now called uba.
Thanks for the help.
You're right simple is good. --mmyoung
Originally posted by Mr_C Also discovered that usb drives are now called uba.
That means you are using the CONFIG_BLOCK_DEV_UB and your usb-storage is "crippled". You should disable that and recompile your kernel. I mistakenly said it was in the USB section, when actually it's in the Block Devices section. See above post.
Quote:
Originally posted by Mr_C Thanks for the help.
You're right simple is good. --mmyoung
You're welcome. The simpler the better I always say.
Originally posted by Mr_C Uba. Is this bad? I mean I plugged in a usb external harddrive and it was recognized. What do you mean it cripples usb-storage?
The "quote" that I have in post number 2 of this thread is a quote from the CONFIG_BLOCK_DEV_UB help file. Matter of fact it states, "If unsure say NO" in the help file.
UB is a "low performance" USB block driver and not really suitable for the "high performance" USB external HD's. I've not read much about UB, but all that I've read about was bad. Well, bad is such a "bad" word, I shoud say all that I've read about UB is "not good". You might want to check out the help file for UB and see what you think. I did find this, usb-storage and the ub device and 2.6.9 may want to give it a read.
Quote:
from the article
So, it is better for certain things and worse for others. In 2.6.10
there are much larger warnings to Distros not to enable it, as it's not
ready yet. The problem is that if you compile your kernel with
CONFIG_BLK_DEV_UB then the devices it believes it can handle (a subset
of the usb-storage devices), then usb-storage will *not* bind to those
devices even if the ub driver is not loaded. Note though that you can
have one device bound to ub and another to usb-storage on the same
machine without problems as long as ub doesn't believe it should have
that 2nd device.
When I try to mount the cdrom drive, I get the following error:
Quote:
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.