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 found another piece of the puzzle. The problem isn't strictly with optical media. The problem appears to affect ALL removable media, including flash devices.
Well, I'll add my 2 cents. I run Slackware64 13.1 and Slackware 13.1 (IDE/PATA controllers, 2.6.33.4-generic), plus Xubuntu and Ubuntu (sata controllers, 10.04 LTS, 2.6.32-22-generic), and I have this issue on all of them. I can automount all DVDs, all commercial pressed CDs, but my burned CDR and CDRW that are known good on Slackware 13.0 don't always automount. I have a 2 year old data CDR that mounts fine, but recently burned CDR (from Slackware 13.0) are about 75% fail to automount. Whether KDE, Xfce, or Gnome is used is not important. Explicitly mounting as root or using fstab works ok. This problem started once I left 2.6.29 series of kernels so its not my disks and it is not my hardware. I also have WinXP, Vista. and Win7 systems that automount all disks just fine. Googling shows a lot of activity with some fixes/work arounds that do not fix the underlying issue
This is a weird bug that I unfortunately no longer have the skills to track down (last code was Z80 assembly on CP/M-80) and it is driving me nuts. Sure, I can do it the "old fashioned way" but why should I not have automounting automation in the 21st century?
tpreitzel, nope, for me every USB stick and external USB hard drive (fat32, ext3 and NTFS) automount just fine here.
I'm willing to bet that the problem of mounting flash devices (internal USB card reader) will rear it's ugly little head in due time. It doesn't happen nearly as often as optical media *, but I've seen it with my own eyes. Simply a fluke? Possibly. I'm certainly tiring of waiting for another kernel in the 2.6.33.x series, though ... Hint, kernel developers.
* Only once so far with flash media in my experience
Well, I'll add my 2 cents. I run Slackware64 13.1 and Slackware 13.1 (IDE/PATA controllers, 2.6.33.4-generic), plus Xubuntu and Ubuntu (sata controllers, 10.04 LTS, 2.6.32-22-generic), and I have this issue on all of them. I can automount all DVDs, all commercial pressed CDs, but my burned CDR and CDRW that are known good on Slackware 13.0 don't always automount. I have a 2 year old data CDR that mounts fine, but recently burned CDR (from Slackware 13.0) are about 75% fail to automount. Whether KDE, Xfce, or Gnome is used is not important. Explicitly mounting as root or using fstab works ok. This problem started once I left 2.6.29 series of kernels so its not my disks and it is not my hardware. I also have WinXP, Vista. and Win7 systems that automount all disks just fine. Googling shows a lot of activity with some fixes/work arounds that do not fix the underlying issue
This is a weird bug that I unfortunately no longer have the skills to track down (last code was Z80 assembly on CP/M-80) and it is driving me nuts. Sure, I can do it the "old fashioned way" but why should I not have automounting automation in the 21st century?
Interesting and unfortunate that you're experiencing the same problem with Ubuntu. It's also interesting that only your recently burned optical discs are failing with automount, but not manual mount. In my case, I have commercially mastered discs failing as well.
Your scenario isn't exactly equivalent to my experience, though. For sure, this bug (bugs?) is driving a considerable number of people over the edge.
all the questions about problems with mounting optical disk
are probably due to the kernel bug.
But it is rather hard to get the kernel bug message in syslog.
So be patient. Sooner or later should be fixed.
OK! Let try to fix your problem:
1. Did you install slackware from CD-ROM ?
a) yes, I did. Ok, my advice: reinstall your system (oh no) but only with
base system (A series) and check if you are able to mount manually CD-ROM
b) no, I did'nt. Ok, try to use the install cd-rom. I guess it will work, then go to the point a)
Last edited by igadoter; 06-25-2010 at 04:44 AM.
Reason: addons - misprinting
all the questions about problems with mounting optical disk
are probably due to the kernel bug.
But it is rather hard to get the kernel bug message in syslog.
So be patient. Sooner or later should be fixed.
OK! Let try to fix your problem:
1. Did you install slackware from CD-ROM ?
a) yes, I did. Ok, my advice: reinstall your system (oh no) but only with
base system (A series) and check if you are able to mount manually CD-ROM
b) no, I did'nt. Ok, try to use the install cd-rom. I guess it will work, then go to the point a)
Oh no! * My 13.1 system has much personal data transferred from BlueWhite64 13.0 so no reinstalling of SW64 13.1 will be done. Upgrading to 13.2 (6 months) is a possibility, but certainly not reinstalling.
Lastly, precisely what kernel bug are you implying? I just upgraded to 2.6.33.6 and the problem remains ... Periodically, I work with Slackware64 13.1 and add software so I won't have to do all that work later when the next version of Slackware64 is released which hopefully will fix this nightmare. My primary system remains BW64 13.0 until this problem is fixed.
* I may try the A series at some point ... maybe. More likely, I'll just periodically update SW64 13.1 until a new version of Slackware is released...
My system once reported a kernel bug. I regret I didn't post it.
I think that at this moment all systems with new kernels 2.6.33.x
should be used carefully, always have up to date backup your
important files.
I know this sound not very nicely, especially in the view of that
slackware is supposed to be stable (for some people it is stable),
but now I am still testing slack 13.1.
At the first time I installed slack on jfs file system, but next decided to reinstall on ext2
(for me it seems to be more safe).
I don't want to blame slackware. I want to use it and I use it.
Fast inspection of the forums for other distros shows that each new release
has quite similar problems (excluding debian, centos etc... they use kernels 2.6.2).
My system once reported a kernel bug. I regret I didn't post it.
I think that at this moment all systems with new kernels 2.6.33.x
should be used carefully, always have up to date backup your
important files.
I know this sound not very nicely, especially in the view of that
slackware is supposed to be stable (for some people it is stable),
but now I am still testing slack 13.1.
At the first time I installed slack on jfs file system, but next decided to reinstall on ext2
(for me it seems to be more safe).
I don't want to blame slackware. I want to use it and I use it.
Fast inspection of the forums for other distros shows that each new release
has quite similar problems (excluding debian, centos etc... they use kernels 2.6.2).
Yeah, I agree that time for testing needs to be extended all across the board, both developers and users. Thanks for your clarification. Something is wrong. Who knows where the bug resides precisely? I'll just keep waiting and updating my SW64 13.1 system as appropriate. Best wishes to you and the people of Poland...
Yeah, I agree that time for testing needs to be extended all across the board, both developers and users. Thanks for your clarification. Something is wrong. Who knows where the bug resides precisely? I'll just keep waiting and updating my SW64 13.1 system as appropriate. Best wishes to you and the people of Poland...
Well, the problem is that "something is wrong" for a subset of Slackware users. (Fine. I guess that you could also state that "something is right" for a different subset of Slackware users. :-P )
I'd say that since Pat V and the set of Slackware maintainers/contributors did not see this issue, then I don't see how they would know the problem existed if the set of folks with the problem didn't whine about it. (Hey, I whine when I have problems with something.)
If you see problems in -current, you really, really, really need to report them. Pat's a nice guy who has some pride in Slackware. Who would want to release a broken distro?
I haven't had time lately to pursue this issue, but I'll say that it is still very much a problem on my system. I have installed the latest stable kernel (2.6.34.1) and same result.
To summarize again:
The problem does not occur on Slackware 13.0, it was introduced with 13.1. Re-install 13.0 and the problem goes away.
It doesn't matter whether you use a supplied (pre-compiled) kernel or compile your own. Every kernel release that I've tried has the same result.
It doesn't matter if you use AHCI or not, same result
It doesn't matter if you have a fstab entry for /dev/sr0 or not.
I, for one, have NO problem mounting audio cd's, USB sticks, or flash cards, just cd's with a filesystem (ISO9660).
There are MANY threads all over the web on this issue, not just Slackware but other distros as well. Nobody appears to have solved it.
yeah, this is a weird one. I just double/triple checked and booted into Slackware64 13.0 multilib and had no problems with any of the CDs. In fact, this is the 1st time automatic mounting in Xfce and KDE didn't work in quite some time. The work around is simple: use "mount" ... well fine ... that "solution" is all over the 'net. However the core issue is still there. I now have issue with Slackware 13.1 (both types, various boxes), Ubuntu, Xubuntu and Absolute Linux. These are all "full" distro installations with the latest updates.
The kicker is its ONLY CDRs in my system and not even all of them: pressed, old, new, burned today, burned whenever. And NONE of these CDs has any problems being automounted on WinXP, Vista or Win7. Something broke along the way to 13.1 Is it the kernel? udev? The driver switch and /dev/srx? consolekit/policykit? Does /etc/rc.d/rc.autofs need to be set executable and if so why do DVDs automatically mount ok?
I don't run a server so a well behaved desktop GUI is important to me. The CDs mount ok manually but that is an extra step I did not need in the past.
I assume the Slackware team is aware of this and that not all of them is so "old school" that they spend all day at the CLI with mount/umount.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.