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 just completed my slackware 9.1 install (first time slackware user). and I updated the system using swaret --update and swaret --upgrade. But now there are a few problems with the system that hadn't occured before (and some that I never got around to fixing). Can anyone shed some light on the situation?
1. The biggest issue at the moment is sound, it worked fine before aside from flash animation on websites where I needed to use 'chmod a+rw /dev/dsp' every time I booted up before it would work (can anyone tell me what config file I need to edit to execute some commands automatically when I log in by the way?) Now after doing my update with swaret (which I know installed some Alsa libs along with other system files, I'm not sure if thats what did it) I get an error as I log into KDE. A message box tagged 'Informational - artsmessage' pops up and gives me the following error.
Sound server informational message:
Error while initializing the sound driver:
device /dev/dsp can't be opened (No such device)
The sound server will continue, using the null output device.
Does anyone know what I can do about that to get my sound back?
2. I am on a laptop with a touchpad as my default input device, but I have a USB mouse that I like to use when I am at a desk. I still have my XF86Config-4 file from my last distro (Mandrake) because I had some problems getting the two input devices to work at the same time with that too. Should I just copy the device entry from that file and change the serverlayout to match?
3. Lastly, I cannot access any of my mounted drives from normal user mode, (ie. windows partition, portable USB hard drive, USB diskonkey).
My original fstab entry for my windows directory was
/dev/hda1 /mnt/windows vfat defaults 1 0
Then I changed it to
/dev/hda1 /mnt/windows vfat auto,users,rw 0 0
then to
/dev/hda1 /mnt/windows vfat auto,owner,rw 0 0
None of those worked, I still get access denied errors when trying to enter from Konqueror.
I don't have fstab entries for my removable media, but I mount them with the command
mount -t vfat /dev/sda1 /mnt/removable
I get the same type of error in this case too. Does anyone have any experience with this problem? thanks
1. When you ran swaret --upgrade it probably didn't update the kernel as well. Go download all the necessary kernel stuff and upgradepkg 'em. Then, after a reboot, run alsaconf and see if your soundcard is detected.
2. That should work. Anyone out there correct me if I'm wrong, please.
3. You might need to add umask=000 to the options on the windows drive in your fstab; this should also work with the removeable drives. But, first, did you create the right directories in /mnt?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.