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.
This problem is just crazy. Keep us posted as you guys and gals find the time and stumble across more information... Extraordinarily frustrating to say the least. Linux simply can't afford to continue down this path. Around 2006, for nearly 6 MONTHS as the kernel team debated various fixes, none of the kernels would boot my VIA based system due to some problem with interrupts. In the long term, I'm done with monolithic kernels. I'm slowly moving to some micro kernel based OS over the next couple of years. In the meantime, I'll continue using Linux and pray for the best.
Now that my wedding anniversary is past (20 yrs whoop!), I did one more test of this automount issue. I have Lite-On CDRW 48x IDE/ATA, LG DVDR-DL 16x IDE/ATA drives. Hard drives are 80 GB WD ATA-100, 120 GB Seagate ATA-100, and 500 GB WD SATA (sata2 drive on a sata1 controller). lspci reports:
WinXP: no issues with any CD, DVD, USB stick or drive
Slackware64 13.0 multilib (stock generic kernel): no issues with any CD, DVD, USB stick or drive
Slackware64 13.1 multilib (stock generic kernel): DVD (data, video), CD-audio, usb stick and drive ok. CDR, CDRW are hit and miss.
Slackware64 13.1:
I have 4 Sony CDRW 650MB disc (2 with data, 2 blank): 2 were not sensed, 1 was sensed in k3b but not in Slackware, 1 as sensed by both k3b and Slackware.
I tested known good CDRs containing data (Memorex, TDK, Maxell). Some mounted ok, some did not, I saw no pattern. These where burned on a variety of systems (Slackware32 12.2, SLAMD6412.1, Slackware64 13.0). 2 observations: (a) CDRs burned with k3b/slackware64 13.1 are always mountable (see below). (b) CDRs that did not mount were sometimes visible in k3b with the correct size, label, etc., just not readable.
I tested Memorex, TDK, Maxell blank CDRs (700 MB, 48x or 52x speeds). Not all blank CDRs were visble in K3B (empty drive), but all those that were visible burned ok and were mountable on this and 2 other Slackware32 13.1 systems.
My regular user login and "root" both have the same issue. As "user" I am in all the correct groups - same ones as needed for Slackware 12.2 to 13.0. This system has been rock solid since Slackware/SLAMD64 11.0.
So there you have it. I think I will drown my sorrows with a few rounds of Urban Terror.
So there you have it. I think I will drown my sorrows with a few rounds of Urban Terror.
Well, I settled for a glass of gewurztraminer, but I came to the same conclusion. I've gone back to 13.0 for now, I still have the downloads so may try later if a solution appears. I did try kernel 2.6.35, same result.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.