LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 07-13-2010, 01:43 PM   #1
hajatvrc
LQ Newbie
 
Registered: Mar 2010
Distribution: Arch Linux
Posts: 13

Rep: Reputation: Disabled
boot process hangs at audio driver, no sound


When my system boots it hangs at
Code:
HDA Intel 0000:01:00.1: PCI INT B-> GSI 17 (level, low) -> IRQ 17
(HDA Intel is my sound card) and eventually moves on after it times out at 120 seconds. It then continues the boot process until it reaches
Code:
triggering udev events: /sbin/udevadm trigger --type=failed
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. Reason: oops
 
Old 07-13-2010, 06:10 PM   #2
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,293

Rep: Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803
My dmesg ouput shows:
Quote:
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: irq 27 for MSI/MSI-X
It may be that your hardware has problems with Message Signaled Interrupts.
Try using the 'pci=nomsi' kernel parameter.
 
Old 07-13-2010, 06:12 PM   #3
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Rep: Reputation: Disabled
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.
 
Old 07-13-2010, 06:58 PM   #4
hajatvrc
LQ Newbie
 
Registered: Mar 2010
Distribution: Arch Linux
Posts: 13

Original Poster
Rep: Reputation: Disabled
Quote:
Try using the 'pci=nomsi' kernel parameter.
Sorry I'm kind of new at this, how do I do this?
Quote:
Can you see a message right after it stops hanging the first time?
I don't know, it goes by really fast. Is there some file that serves as a log for bootup time so I can copy-paste it?
 
Old 07-13-2010, 10:54 PM   #5
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,293

Rep: Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803
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?
 
Old 07-14-2010, 02:35 PM   #6
hajatvrc
LQ Newbie
 
Registered: Mar 2010
Distribution: Arch Linux
Posts: 13

Original Poster
Rep: Reputation: Disabled
Actually, I use lilo exclusively. I added
Code:
append = "pci=nomsi"
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.

Last edited by hajatvrc; 07-14-2010 at 03:00 PM.
 
Old 07-14-2010, 08:03 PM   #7
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,293

Rep: Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803
Glad the boot process has been sorted.
For sound, have you worked through this? http://slackwiki.org/ALSA
 
Old 07-15-2010, 01:26 PM   #8
hajatvrc
LQ Newbie
 
Registered: Mar 2010
Distribution: Arch Linux
Posts: 13

Original Poster
Rep: Reputation: Disabled
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.
 
Old 07-15-2010, 07:31 PM   #9
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,293

Rep: Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803Reputation: 803
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.

Code:
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.

Last edited by allend; 07-15-2010 at 08:47 PM.
 
Old 07-16-2010, 08:02 AM   #10
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
If you need to know which codec your card has, since there are
very many all using HDA Intel, issue:
Code:
cat /proc/asound/card0/codec#* | grep Codec
 
Old 07-16-2010, 02:47 PM   #11
hajatvrc
LQ Newbie
 
Registered: Mar 2010
Distribution: Arch Linux
Posts: 13

Original Poster
Rep: Reputation: Disabled
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.

Thanks for the help!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
My jaunty box hangs during the boot process redhand8888 Ubuntu 1 05-19-2009 07:49 AM
Boot process hangs after LILO completes (-12.0) rshepard Slackware 3 03-11-2008 04:00 PM
My sendmail process hangs on boot up guarriman Fedora 1 11-13-2006 10:07 AM
LILO hangs during the boot process ntoughe Linux - General 3 11-18-2005 10:44 AM
Sound Driver intel8x0 hangs on startup, can only boot from cd. mwaddoups Suse/Novell 4 05-20-2005 02:27 AM


All times are GMT -5. The time now is 07:37 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration