LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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
 
Search this Thread
Old 12-05-2003, 01:55 AM   #1
todesengel
Member
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 54

Rep: Reputation: 15
alsa not working after slackware 2.4.23 security upgrade?


Hey all,

I just upgraded my kernel to 2.4.23 using the slackware.com security upgrade procedures. I installed their kernel, their alsa upgrades, etc, and followed their instructions to the letter. Now, after a reboot, my computer works perfectly except alsa isn't working. When I try to go in to alsamixer, I get this error:
alsamixer: function snd_ctl_open failed for default: No such device.
When I try alsaconf, it says I have no supported sound card.

I'm not sure what's going on, because my SB Live! modules are loaded, and appear to be working. /dev/dsp is fine, and I haven't changed anything else since kernel upgrade.

If anyone has any suggestions on how to get my sound back up, I'd be very grateful

Thanks
 
Old 12-05-2003, 02:13 AM   #2
C.Loko
LQ Newbie
 
Registered: Jul 2003
Posts: 27

Rep: Reputation: 15
well i also updated kernel to 2.4.33 and alsa drivers,oss,modules,utils but i get this error:

Informational - artsmessage (window title)

Sound server informational message:
Error while initializing the sound driver:
device /dev/dsp can't be opened(No such device)
The sound server will continue using the null output device

So i'd like to hear some suggestion for solution 2 this problem too
 
Old 12-05-2003, 02:16 AM   #3
todesengel
Member
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 54

Original Poster
Rep: Reputation: 15
Yea, when I'm loading up XMMS, I get that too.
 
Old 12-05-2003, 03:37 AM   #4
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
If your /etc/modules.conf is a big zero, that's the problem, C.Loko. The *ahem* 'upgrade' kills it. I had no idea what the posting at slackware.com meant about backing up files - *which* files? So I fscked it up. Fortunately, I've got Slack on another box now - offline where there are *no* kernel exploits - so I copied mine from there - after a looong bout of high-volume cussing and so on. I dunno how you've got your modules loading, todesengel, so I don't know what the problem is - I don't see how your modules are loading unless you somehow didn't get zeroed.

I'm all for Slackers being gung-ho on the diy and self-reliance crap but it wouldn't kill anyone to be a little more verbose in the security update/install instructions. And why the fsck does it overwrite the file (and who knows what else I haven't discovered yet) in the first place? I couldn't even run alsaconf. Shit. Total shit. This exploit was known months ago. Why the hell'd everybody release this 2.4.22 kernel and all these new distro versions so we could zero our modules.conf's months later upgrading the crap? I guess this is supposed to make 2.6 look real good but, quite frankly, I'm getting fscking sick of screwing around with the system.

If this isn't your actual problem, ignore the rant.
 
Old 12-05-2003, 03:47 AM   #5
todesengel
Member
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 54

Original Poster
Rep: Reputation: 15
Yea, my /etc/modules.conf it empty. But, it was empty before, so I don't think that's it. If I'm not mistaken, slack loads up it's modules via the /etc/rc.d/ files, right?
 
Old 12-05-2003, 03:55 AM   #6
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
Yeah - /etc/rc.d/rc.alsa - but it allows that modules may be defined in modules.conf and, in my case, they definitely were. Seems to load a very basic setup that didn't do me any good without specifics. Such as my crap i810 onboard sound, without which I get no damn sound. Maybe different for different folks, especially those with real cards. *shrug*

I don't know. The longer I use Linux the dumber I get and the less I know - and that ain't easy.
 
Old 12-05-2003, 04:08 AM   #7
C.Loko
LQ Newbie
 
Registered: Jul 2003
Posts: 27

Rep: Reputation: 15
well i am a bit confused now..
i tried to run sndconfig but i can't.
Are we f**k up ?
 
Old 12-05-2003, 04:41 AM   #8
nvn
Member
 
Registered: Apr 2003
Location: Sweden
Distribution: Slackware
Posts: 242

Rep: Reputation: 30
I'm veeeeery tired now, so please excuse any incomprehensible blah-blah from my part... ..but, have you tried reinstalling ALSA? Since ALSA is not a part of the 2.4 kernel, new modules will not be compiled when you recompile the kernel, and if you 'make clean' I guess the ALSA modules might go bye-bye...

Edit: Hmm, perhaps you upgraded your kernel by installing a pre-compiled one (horrible thought!)? In that case, the above solution might not be what you're looking for...

Last edited by nvn; 12-05-2003 at 04:43 AM.
 
Old 12-05-2003, 10:37 AM   #9
Misel
Member
 
Registered: Mar 2003
Location: Berlin
Distribution: Slackware current
Posts: 310

Rep: Reputation: 30
Quote:
Originally posted by nvn
I'm veeeeery tired now, so please excuse any incomprehensible blah-blah from my part... ..but, have you tried reinstalling ALSA? Since ALSA is not a part of the 2.4 kernel, new modules will not be compiled when you recompile the kernel, and if you 'make clean' I guess the ALSA modules might go bye-bye...

Edit: Hmm, perhaps you upgraded your kernel by installing a pre-compiled one (horrible thought!)? In that case, the above solution might not be what you're looking for...
Slackware 9.1 comes with precompiled Alsa modules. But they're compiled for the 2.4.22 kernel and that's why they won't work with 2.4.23.

If you want to keep 2.4.23 you have to recompile alsa - they have newer sources at the Als-Project anyway. Or you could continue to use 2.4.22 and wait till the 2.6 series will be out because Alsa will be integrated in there.
 
Old 12-05-2003, 11:07 AM   #10
C.Loko
LQ Newbie
 
Registered: Jul 2003
Posts: 27

Rep: Reputation: 15
well the alsa updates in slack's homepage are compiled for kernel 2.4.23

PS: to me xmms is not working either.
 
Old 12-05-2003, 11:39 AM   #11
ZiGiE
Member
 
Registered: Oct 2003
Location: ex USSR, Canada
Posts: 58

Rep: Reputation: 15
My suggestion - recompile your kernel, and your modules. Don't use pre-compiled. Plus if you really want, you might as well compile alsa v.1.0.0rc1 while you're at it. It's not that hard.

Cheers
 
Old 12-05-2003, 01:18 PM   #12
Misel
Member
 
Registered: Mar 2003
Location: Berlin
Distribution: Slackware current
Posts: 310

Rep: Reputation: 30
Quote:
Originally posted by C.Loko
well the alsa updates in slack's homepage are compiled for kernel 2.4.23

PS: to me xmms is not working either.
well, I was actually wondering how it would have worked with a custom 2.4.22 and the precompiled libraries anyway

As ZiGiE posted: recompile it. I already gave you the link
 
Old 12-05-2003, 04:16 PM   #13
todesengel
Member
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 54

Original Poster
Rep: Reputation: 15
You guys think that uninstalling ALSA packages, then compiling from source would do it?

By the way, I hate compiling my own kernel. I've done it many times, and it's not a matter of experience, but I'd much rather use pre-tested, pre-compiled kernels.
 
Old 12-05-2003, 04:26 PM   #14
Tino27
Member
 
Registered: Aug 2003
Location: Akron, OH
Distribution: SuSE 8.2, Slackware current, OpenBSD 3.5-3.8, Fedora Core 2
Posts: 400

Rep: Reputation: 30
Misel -- let me get this straight... If I skip the 2.4.23 upgrade and go right to 2.6.0-test11, ALSA is compiled into the kernel, right? Does that mean I could uninstall ALSA in my present kernel (2.4.22), compile and boot into the 2.6.0 kernel and still get sound through ALSA?
 
Old 12-05-2003, 05:24 PM   #15
Misel
Member
 
Registered: Mar 2003
Location: Berlin
Distribution: Slackware current
Posts: 310

Rep: Reputation: 30
Todesengel, then just use the latest alsa-packages with the new kernel. The alsa-drivers are updated as well - at least they have the same date as the new kernel.

Tino27 - ALSA will be integrated into the new kernel series so you will not be bothered with the drivers. You will need the alsa-utils however in order to control them. But they seem to be compatible between their versions. e.g.
 
  


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
Redhat 7.2 upgrade/security advice stoke Red Hat 2 03-21-2005 05:29 AM
ound not working after upgrade slackware 9.1 to 10 alitrix Linux - Hardware 5 12-29-2004 03:12 AM
ALSA wont detect sound card after Slackware 10 upgrade coffeedemon Slackware 3 11-15-2004 07:29 PM
DHCLIENT Stops working after upgrade kernel from 2.4.20 to 2.4.22 in Slackware curdanet Linux - Networking 5 11-01-2003 12:57 PM
kernel upgrade and alsa stops working seppe Linux - Hardware 1 10-02-2003 11:03 AM


All times are GMT -5. The time now is 01:19 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