Sound not working after kernel upgrade

krimson · 07-07-2004, 02:02 PM

I recently upgraded my Slackware installation from 9.1 to 10.0, everything went smooth. I then decided to take it a step further and try out the packaged 2.6.7 kernel. That install also went smooth, however, I noticed I lost my sound. I installed the new alsa driver package that came with the kernel, ran alsoconf, detected my sound card, etc, etc. Still no sound. I removed and reinstalled the package, ran alsaconf again. Again, it found and installed my sound card. Still no sound. I've researched this a bit and did not find any information regarding this issue with any kernels newer than 2.4.6. Any help/suggestions/comments would be greatly appreciated.

Modules and audio devices:

Code:

isofs                  30008  0
zlib_inflate           21248  1 isofs
snd_pcm_oss            49704  0
snd_mixer_oss          17408  3 snd_pcm_oss
snd_intel8x0           32940  3
snd_ac97_codec         64644  1 snd_intel8x0
snd_pcm                80904  2 snd_pcm_oss,snd_intel8x0
snd_timer              21764  1 snd_pcm
snd_page_alloc         10888  2 snd_intel8x0,snd_pcm
gameport                3712  1 snd_intel8x0
snd_mpu401_uart         6912  1 snd_intel8x0
snd_rawmidi            21028  1 snd_mpu401_uart
snd_seq_device          7304  1 snd_rawmidi
snd                    48484  11 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               6752  3 snd
ipv6                  212064  8
ohci_hcd               18436  0
joydev                  8000  0
intel_agp              16540  1
eth1394                16904  0
uhci_hcd               27920  0
ehci_hcd               27012  0
hw_random               4500  0
i8xx_tco                5524  0
b44                    17924  0
mii                     4096  1 b44
ohci1394               29828  0
ieee1394               89528  2 eth1394,ohci1394
ds                     13572  2
yenta_socket           17536  0
pcmcia_core            52676  2 ds,yenta_socket
evdev                   7168  0
agpgart                26920  1 intel_agp
psmouse                17544  0
ext3                  106088  0
jbd                    47256  1 ext3

Code:

ls -l /dev/sound
total 0
crw-rw--w-  1 root audio 14, 12 2004-07-07 09:14 adsp
crw-rw--w-  1 root audio 14,  4 2004-07-07 09:14 audio
crw-rw--w-  1 root audio 14,  3 2004-07-07 09:14 dsp
crw-rw--w-  1 root audio 14,  0 2004-07-07 09:14 mixer

Code:

lrwxrwxrwx  1 root root 10 2004-07-07 09:14 /dev/adsp -> sound/adsp 
lrwxrwxrwx  1 root root 9 2004-07-07 09:14 /dev/dsp -> sound/dsp 
lrwxrwxrwx  1 root root 11 2004-07-07 09:14 /dev/audio -> sound/audio 
lrwxrwxrwx  1 root root 11 2004-07-07 09:14 /dev/mixer -> sound/mixer

bulliver · 07-07-2004, 02:16 PM

Did you use alsamixer to unmute all the channels?

krimson · 07-07-2004, 02:19 PM

Yes, all the channels that I need are unmuted and volume is at a normal level.

bulliver · 07-07-2004, 02:41 PM

Is your user in the audio group?

krimson · 07-07-2004, 02:53 PM

Not 100% sure, how would I check and/or correct that? Also, sound does not work as root either.

deloptes · 07-07-2004, 03:58 PM

Code:

cat /etc/group | grep audio

I didn't see amixer somewhere in /dev - I wrote a brief howto on ALSA - how I did the setup - check it out

some people said it's helpful, though not too verbouse ...
http://213.47.57.130/~deloptes/linux...ort_2.4.X.html

hope that it helped

bulliver · 07-08-2004, 05:06 AM

Quote:

Also, sound does not work as root either.

If it won't work for root then there is something fundamentally wrong. In this case I would start with the basics...is everything cabled properly? Don't laugh or just shrug it off...look, because it even happens to experts every once in a while. Is the soundcard seated properly in the pci slot? Check all the physical connections.

krimson · 07-08-2004, 07:52 AM

Can't, it's a laptop, onboard sound, etc. But, the sound worked basically up until kernel upgrade, so I'm not sure what happened. I'm in the process of backing up my home directory so I can blow the install away. I've noticed some other issues going on that I didn't before, so I think there is something else going on. Thanks for all of your replies.

deloptes · 07-08-2004, 11:32 AM

well could you tell us please what kind of kernel and so you use, so we could help, may be chipset or driver you are using

krimson · 07-08-2004, 11:58 AM

Sure, I'm going to try again with the 2.6.7. I know everything works flawlessly with 2.4.26, but I'd like to attain the same with 2.6.7.

deloptes · 07-08-2004, 02:30 PM

I'm not familiar with 2.6.X kernels, I think I can not help you

From which version are you upgrading, were you using 2.6.X before this

post the output of amixer

see what alsamixer -c 0 shows

krimson · 07-08-2004, 02:37 PM

That's alright dude, I'm starting over fresh. I was running Slackware 9.1 with 2.4.26, I then upgraded to Slackware 10.0 with 2.4.26. Then went up to 2.6.7. I'm going to do a fresh install of 10.0 with 2.6.7 and see if I can get it to work.

deloptes · 07-08-2004, 05:36 PM

if you wish try recrateing the device files and check the drivers loaded, may be you have to update some scripts I did in modules.conf to have the alsa architecture to work properly ... at least I did it and it worked...

did you use alsa before or oss.

I use debian and there is script that recreates teh files under /dev if necessary at boot time, very handy thing

After all you can try recompile and install your own kernel ... it should save you more time as installing and configuring a hole system again

why this ms-windows mentality?

krimson · 07-08-2004, 08:04 PM

Yes, I ran alsa prior. I've already checked all the scripts and triple checked everything was loading properly. And as I stated earlier, I have since run into more issues than just the sound not working, so there is something else going on.

What do you mean "ms-windows mentality", it's only a laptop I use to mess around and test things on.

deloptes · 07-09-2004, 11:38 AM

sorry about the ms mentality -it means reisntall everything again
If I want to test a new distro I do install it on different partition, I do check it and after I am sure it works I replace my distro, though I made this just one time, because I did upgrade from stable to testing and than I tried to downgrade, what was obiously too brave. Since than (more than 2 years) I use only woody stable and compile the few apps I need, the kernel and alsa too with regular upgrades from the distro itself.
I tried the 2.6 , but it's not stable enough to satisfy my expectations and I use only 2.4 the latest patches appplied - no problems. I tried on my other partition few other distros, but I still have one where I'm sure I can boot on and work.
This way I can really enjoy 100% the power of my machine and really spend time working and not configuring all the time and posting questions to LinuxQuestions.org

Another windows symptom is "upgrade now" and "new version available" and so on.

Why should I upgrade if somthing works already to something I don't know if it works.

Next time copy your system to a free partition
boot from this partition
make the upgrade there
reboot and test the upgrade
IF ITS OK
replace your old system with the new one
Note_
Mostly if you have customly installed apps (compiled and so), keep a track of them and test them (usually you should recompile and reinstall them

Anyway you seem to be smart and I'm sure wou'll find your own way to manage linux.

regards