LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Upgraded to Slack=current, now no sound! (http://www.linuxquestions.org/questions/slackware-14/upgraded-to-slack%3Dcurrent-now-no-sound-256345/)

Slovak 11-18-2004 05:57 AM

Upgraded to Slack=current, now no sound!
 
Running 2.4.26 kernel, I used swaret to upgrade to current, but made sure that alsa was in my exclude list. After the upgrade and dependency check, I reboot, and no sound. How can that be when I have not touched any sound settings? I ran alsaconf, detected my card just fine, stored it, even ran an alsa restore. Still no sound whatsoever :(
All alsa mixer settings are all the way up, and nothing as far as I can tell is muted anywhere. What the hell is going on here?

root@johnd:~# lsmod
Module Size Used by Not tainted
snd-seq-oss 26048 0 (autoclean) (unused)
snd-seq-midi 3488 0 (autoclean) (unused)
snd-emu10k1-synth 3868 0 (autoclean) (unused)
snd-emux-synth 27516 0 (autoclean) [snd-emu10k1-synth]
snd-seq-midi-emul 4720 0 (autoclean) [snd-emux-synth]
snd-seq-virmidi 2920 0 (autoclean) [snd-emux-synth]
snd-seq-midi-event 3264 0 (autoclean) [snd-seq-oss snd-seq-midi snd-seq-virmidi]
snd-seq 33424 2 (autoclean) [snd-seq-oss snd-seq-midi snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-midi-event]
snd-pcm-oss 37736 0
snd-mixer-oss 12504 0 [snd-pcm-oss]
mousedev 4212 1
keybdev 2052 0 (unused)
usbmouse 2040 0 (unused)
hid 21220 0 (unused)
usbkbd 3448 0 (unused)
input 3200 0 [mousedev keybdev usbmouse hid usbkbd]
printer 7744 0
uhci 24444 0 (unused)
usb-ohci 19240 0 (unused)
ehci-hcd 17580 0 (unused)
usbcore 59308 1 [usbmouse hid usbkbd printer uhci usb-ohci ehci-hcd]
snd-emu10k1 62920 0 [snd-emu10k1-synth]
snd-pcm 56072 0 [snd-pcm-oss snd-emu10k1]
snd-timer 13604 0 [snd-seq snd-pcm]
snd-hwdep 4804 0 [snd-emux-synth snd-emu10k1]
snd-page-alloc 6328 0 [snd-emu10k1 snd-pcm]
snd-util-mem 1136 0 [snd-emux-synth snd-emu10k1]
snd-ac97-codec 49500 0 [snd-emu10k1]
snd-rawmidi 12740 0 [snd-seq-midi snd-seq-virmidi snd-emu10k1]
snd-seq-device 3888 0 [snd-seq-oss snd-seq-midi snd-emu10k1-synth snd-emux-synth snd-seq snd-emu10k1 snd-rawmidi]
snd 30852 0 [snd-seq-oss snd-seq-midi snd-emux-synth snd-seq-virmidi snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-emu10k1 snd-pcm snd-timer snd-hwdep snd-util-mem snd-ac97-codec snd-rawmidi snd-seq-device]
soundcore 3396 10 [snd]
emu10k1-gp 1352 0 (unused)
gameport 1420 0 [emu10k1-gp]
ohci1394 24112 0 (unused)
ieee1394 42276 0 [ohci1394]
pcmcia_core 39972 0
ntfs 51424 1 (autoclean)
ide-scsi 9328 0
tulip 40352 1
crc32 2880 0 [tulip]
agpgart 43940 0 (unused)

Slovak 11-18-2004 05:58 AM

root@johnd:~# lspci
00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 02)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 02)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 02)
00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 NJ [Radeon 9800 XT]
01:00.1 Display controller: ATI Technologies Inc RV350 NJ [Radeon 9800 XT] (Secondary)
02:0a.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
02:0b.0 USB Controller: NEC Corporation USB (rev 41)
02:0b.1 USB Controller: NEC Corporation USB (rev 41)
02:0b.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
02:0e.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
02:0e.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
02:0e.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)

Cedrik 11-18-2004 06:32 AM

Could you explain how do you test sound please ?

phatbastard 11-18-2004 09:52 AM

chances are you upgraded the alsa-drivers for the 2.4.27 kernel and you have the 2.4.26 kernel. Remove the alsa drivers you are using with pkgtools and reinstall your old alsa drivers. You can grab the old alsa drivers from the slackware website.

THEHERO 11-18-2004 05:02 PM

Why not make sure that the kernel and alsa are not in the exclude list and run swaret --update and swaret --upgrade -a

ajbrouwe 11-18-2004 05:08 PM

I hate to say this, but don't use swaret or slapt-get. They are both horrible methods to update your system.

To effectively update your system, follow the changelogs on www.slackware.com, and download the packs from the nearest FTP site.

Many people use swaret, and many people mess up their slack installs because of it. Personally, after it screwed up my first install, I havent' touched it since.

Just a word of advice. If you want to be a true slacker, take control, and do it yourself.

Andrew

Slovak 11-18-2004 06:39 PM

Quote:

Originally posted by Cedrik
Could you explain how do you test sound please ?
Every way I can think of, various types of files, cd's, etc., etc. I have ran alsamixer and turned everything up all the way and unmuted everything, loaded every single audio player/mixer, cranked everything up, no go for sound at all, WTF? I am almost ready to give up on Slack altogether, I can't ever get sound with any kernel, or 3D video. I can do with out 3D, but not sound. I don't even have sound in junk like gaim!

Slovak 11-18-2004 06:49 PM

I don't have sound in Gnome even! all sorts of volume control and mixer errors, no sound in any window manager for that matter! WTF?

tw001_tw 11-18-2004 10:21 PM

If you are running the 2.4.26 kernel (& ver 10.0), what I would do is
use pkgtool to remove the 4 alsa packages, and then reinstall them
from your original install CD's via installpkg (just 'cause I'de think using
installpkg for that would be easiest).

They can be found on disk 1:

/ap/alsa-utils-1.0.5-i486-1.tgz

&

/l/alsa-driver-1.0.5a-i486-2.tgz
/l/alsa-lib-1.0.5-i486-1.tgz
/l/alsa-oss-1.0.5-i486-1.tgz


Post results. gl.
- tw

Slovak 11-18-2004 10:42 PM

Already done, no luck

tw001_tw 11-18-2004 11:24 PM

What I suggested has fixed the same (similar) problem 2 times (maybe only
once - I can't remember).

I can tell you, that some time ago, (although I think it was ver 9.1, not 10, but
it might have been 10 - who knows) the same thing happened to me.

Its not a solution, but I ended up taking out my SB live card (emu10k1), and
enabling my then disabled onboard sound that had a completely different
chipset on it. I have since formatted and reinstalled (due to other reasons),
and my SB card is back and working great.

Wish I could help you...... Got a different sound card?

I too would be interested in hearing the solution to this.
-tw

Slovak 11-19-2004 05:47 AM

No man, I don't have another sound card, or even onboard sound for that matter.

lupin_the_3rd 11-19-2004 03:24 PM

Compile alsa-modules from source using the --with-cards=(name of your card here).
Configure --help within the source for alsa-driver will give you a list of card flags... you may have modules loading with the default alsa configuration from slackware that are hindering your sound (this has happened to me before so I just always compile my own alsa kernel modules)...

not sure what else to tell you...

lupin_the_3rd 11-19-2004 03:30 PM

Quote:

Originally posted by ajbrouwe
I hate to say this, but don't use swaret or slapt-get. They are both horrible methods to update your system.

To effectively update your system, follow the changelogs on www.slackware.com, and download the packs from the nearest FTP site.

Many people use swaret, and many people mess up their slack installs because of it. Personally, after it screwed up my first install, I havent' touched it since.

Just a word of advice. If you want to be a true slacker, take control, and do it yourself.

Andrew

Just b/c you screwed up doesn't mean everyone will... don't spread FUD... it's ok for you to not use swaret or slapt-get and ok for others to use them. My words of advice/opinion for swaret users though... I would always exclude kernel and alsa from upgrades and do as Andrew suggested and read the changelogs closely before (or during) upgrades... there's always kernels of wisdom buried in there;) The beauty of swaret is that you don't have to manually upgrade each .tgz but it is not an excuse to be lazy altogether though...

gbdavidx 11-19-2004 03:33 PM

i could never get swaret to work, where and how would you go about upgrading? for some reason i can't connect to aol or yahoo through kopete or gaim it makes me mad


All times are GMT -5. The time now is 10:08 PM.