SlackwareThis Forum is for the discussion of Slackware Linux.
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.
and hangs for another 120 seconds. In X11 I have no sound at all even after running alsaconf with no errors. My sound works perfectly in Ubuntu, so it's not a hardware problem. Are the two problems related or are they two separate things? Any help here would be hot.
Last edited by hajatvrc; 07-13-2010 at 01:49 PM.
You probably have a device that is seriously upsetting udev. But I'm guessing it isn't the HDA Intel sound chip. Whatever message appears after the HDA Intel one might help, but again that might not be the actual cause. Can you see a message right after it stops hanging the first time?
I had something exactly like this happen with an older CD-RW drive on an older motherboard. It started with a udev upgrade in Slackware 12.something. The cause was the cdrom_id script it used to probe the device. It hung once early in the boot process, then again at "udevadm trigger". Same 120 second hangs, twice.
As you are also using Ubuntu, then you are probably using GRUB as your bootloader.
If you are chainloading Slackware with LILO on the Slackware root disk, add the string ' pci=nomsi' to the 'append=' string in your /etc/lilo.conf.
Perhaps some helpful person who uses GRUB can suggest an alternative?
to my lilo.conf and the boot process doesn't hang anymore. BUT, there is still no sound. Any other suggestions? I have had this problem in the past where my sound would work right after I installed slack and then it would mysteriously stop working when I rebooted my system. I did a very limited number of things in that time including updating my 64-bit libs with multilib versions and installing gtk-qt-engine. I don't think either of these would cause my sound to stop working. I can't think of anything else that I've done.
I have read the page you linked to and no luck. alsaconf recognizes my hardware just fine and, when I run it, it tells me "Now ALSA is ready to use." I use alsamixer to adjust the volume and then try to play sound in at least 3 different applications with no success.
By default the snd-hda-intel module tries to automatically determine your hardware.
This may not be appropriate for your hardware. http://www.kernel.org/doc/Documentat...dio-Models.txt shows a large number of possible models. You can check your chip by looking at the chip reported by alsamixer.
You can setup a file /etc/modprobe.d/hda-snd-intel.conf and include a specific model.
options snd-hda-intel model=<some model name>
Edit: As the sound is working in Ubuntu, you could check the contents of alsabase.conf, which I believe is where Ubuntu keeps this configuration.
As I have reinstalled slack for other reasons, the problem seems to have resolved itself. I won't know if the sound is going to stop working again until I start to play around a bit. Now it's time to get more edukated about Slackware, every day a new mystery.