No sound after reboot Suse 9.2 using 82801 driver

danielph · 12-04-2004, 01:06 PM

I think this is distro specific as the sound card auto detects and works fine under Knoppix and Mandrake. Under Suse 9.2 Pro however it auto detects and works fine on an Dell Inspiron 8500 laptop, but it is not working after a reboot. Then I have kmix displaying either full volume on the task bar, but not adjustable and blanked out settings in the mixer. No sound is available at this point through any apps. I can delete and reinstall the card without a problem and bingo it all works happily until the next reboot.

I have tried various sound system settings including auto, alsa and oss and even disabling. It makes no difference.

The driver being used is an Intel 82801 DB AC97.

Is this a familiar problem with a familiar solution or am I looking at freshly laid road?
If so, any hints on the right path?

This aside, Suse have done a great job on 9.2

cheers

Dan

pilotgi · 12-04-2004, 08:34 PM

I think this article might help. Always check the SUSE support database for trouble shooting help.

http://portal.suse.com/sdb/en/2004/0...ndsilence.html

danielph · 12-05-2004, 02:19 AM

thanks for that.
Missed that article, but now I have tried it and I have hit a problem. I have removed package kdemultimedia3-mixer as required and then followed the steps below. The the problem seems to be the lack of kamix. I cannot find it in YaST. As I type this I have no sound at all.

Here are the instructions:

rcalsasound stop
rm /etc/asound.state
rcalsasound start
alsactl store
Log the root user out of the console by pressing [Ctrl]+[D].
Enter the command kamix & .
Confirm the pop-up message [KDEInit could not start "CheckHardware".].

with results as follows:

Code:

# rcalsasound stop
Shutting down sound driver                                           done
# rm /etc/asound.state
# rcalsasound start
Starting sound driver:  intel8x0                                     done
No mixer config is found - adjusting default volumes
# alsactl store
# exit
[1]+  Exit 127                kmix
> kamix &
bash: kamix: command not found
[1] 11312
[1]   Exit 127                kamix
>

thanks for you help in advance

pilotgi · 12-05-2004, 08:01 AM

Don't worry about kamix. Run alsaconf as root.

danielph · 12-05-2004, 02:01 PM

I did what you said and used the alsamixer after running alsaconf and left kmix uninstalled. All worked great until the reboot. Same problem back again, but this time in alsamixer. The difference was when I looked in alsamixer it was not displaying intel like kmix was it was showing device as camera. This was mirrored in YaST. When I had the problem before I could only see 1 sound device, now it is showing me a device called camera. This after a little bit of thinking is a webcam that I havent used before that is still plugged into the dock of the laptop. It would appear that on a reboot it picks this up as a sound card (well it has a mic) and runs with it, shutting out the Intel driver.

I tried a few tests on this, by rebooting with the USB Camera pluggged in and unplugged and it was consistant. I also reinstalled all the kde controls including kmix and kmix works fine as long as the camera is not plugged in and the system is not rebooted.

That leaves me with a working sound system and another little project with the camera.

Thanks for your pointers on this. It led me on the right path although I am a little confused as to why the camera should cause this problem and not even show itself as a device. Only when kmix was uninstalled did I see the device as camera and as another sound device. I can understand why it would lock the master sound and leave the mic slider available.

Still a fully working (almost) Suse

cheers

Dan

danielph · 12-06-2004, 07:45 PM

NOTE: After further testing it would seem that kmix still causes problems so now using alsamixer only. This works fine.

If anyone knows if there is an alsa mixer with a taskbar volume control then please let me know.

Dan

shock_ez · 12-31-2004, 07:19 AM

I've had the same problem. I tried the whole "remove the kmix" idea that SuSE suggests, and I also reconfigured ALSA.

aplay confirms that sound will play correctly when I'm using a shell (even when already running X/KDE). However, anything playing in KDE itself doesn't want to make any noise.

Why are my KDE apps not playing sound?

Note that changing the Sound Device in the Sound section of KControl does, unfortunately, nothing

Any ideas?

It's been a while since I was last using Linux and even then I was pretty Newb, so sorry if I'm a little rusty...

Dan: You probably have found this out already but gamix works well and I believe has some sort of taskbar thing.

Manuzzi · 01-19-2005, 03:38 PM

Quote:

Originally posted by danielph

Here are the instructions:

rcalsasound stop
rm /etc/asound.state
rcalsasound start
alsactl store
Log the root user out of the console by pressing [Ctrl]+[D].
Enter the command kamix & .
Confirm the pop-up message [KDEInit could not start "CheckHardware".].
[/B]

Hi,
Had the same problem. Sound driver Intel 82801AA. SuSe 9.2. KDE. The instructions above resulted in starting the sound, but after reboot.: no sound. While booting came the message: " Starting sound driver: already running"
After deleting KDEmultimedia3-mixer with Yast, I didn't get sound anymore with the mediaplayer Amorok. So I installed Alsaplayer. This is working fine.

After taking of my USB Logitech web cam, the problem with the sound was solved.

I am rather new with Linux and Suse. I am sorry to say, it is not very user friendly as far as multimedia concerned.

Herman