LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
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 10-13-2003, 03:14 PM   #1
vrillusions
Member
 
Registered: Feb 2003
Location: Ohio, USA
Distribution: Ubuntu, Debian, CentOS
Posts: 99

Rep: Reputation: 25
compiled 9.1 - now sound doesn't work


Subject line says it all. I went through the guide on here to compile it (mainly just wanted to set the arch to i686). That was the only option I changed, but when I recompiled the sound card stopped working. If I try to cat /dev/dsp it gives me a device not found error. Sound worked fine before and lspci still shows it in there. I tried to go back to old kernel and it still didn't work. Could that happen because when I recompilied it did something to that module? This is a laptop and the audio card is ESS Technology ES1978 Maestro 2E (rev 10)
 
Old 10-13-2003, 06:19 PM   #2
320mb
Senior Member
 
Registered: Nov 2002
Location: pikes peak
Distribution: Slackware, LFS
Posts: 2,577

Rep: Reputation: 48
Yes, you might have accidently left out support for loadable modules! Re compile the kernel and look thru everything, leave out what you don't need and watch your P's and Q's LOL..........
all of us have left out something important from the K at one time or another!!
 
Old 10-13-2003, 07:19 PM   #3
MsMittens
Member
 
Registered: Oct 2003
Location: Canada
Distribution: depends on the mood -- these days.. Slack!
Posts: 44

Rep: Reputation: 15
Actually, if I may humbly suggest, don't recompile the Kernel. Go to the ALSA Project, download, then following the instructions here.

I had a similar problem with the ESS 1998 Ver 12. And I've resolved pretty much all of it except getting rid of some old errors. My only guess is that the ALSA 0.9.6 doesn't like to play fully or isn't compiled properly for the sound cards (perhaps not identifying all components).
 
Old 10-13-2003, 08:44 PM   #4
JollyRogers
Member
 
Registered: Sep 2003
Location: Va USA
Distribution: Slackware
Posts: 81

Rep: Reputation: 16
ALSA is not part of kernel 2.4.22 yet. When you do make modules_install it replaces the /lib/modules/2.4.22 directory. Slack 9.1 has packages built for it and when it installs the necessary modules are dropped into the appropriate places in /lib/modules/2.4.22 dir., so if you are still running 2.4.22 then reinstall the ALSA slackware packages and it should work. But if you are running something other then 2.4.22, then Slack's ALSA package will not install those modules into the correct modules directory.... in that case you have to D/L ALSA like MSMittens suggests.

The alsa package is located on cd #1 in the slackware/ap directory. Just mount your cdrom, use the term to cd /mnt/cdrom/slacware/ap and then run installpkg alsa-*.tgz
 
Old 10-14-2003, 10:15 AM   #5
vrillusions
Member
 
Registered: Feb 2003
Location: Ohio, USA
Distribution: Ubuntu, Debian, CentOS
Posts: 99

Original Poster
Rep: Reputation: 25
OK, I first checked the kernel options and that was set fine. I installed the alsa package (there was only one package that got installed) and I'm still getting device not found. so I started going through the /etc/rc.d/rc.alsa file and manually tried all the comands till I got to the following:

/usr/sbin/alsactl restore

and got the error:

/usr/sbin/alsactl: load_state:1134: No soundcards found...

Don't remember seeing that durring the boot sequence, not sure if just went by too fast or what. I also tried to just run rc.alsa and didn't get any errors. Actually, looking at the file again, I think I know what that's happening. It first checks to see if the dir /proc/asound exists, and it doesn't. So it then tries to load the modules and when running the modprobe command that is there, I don't get anything returned, and there is no "unable to load module" message. Added that to it and now I get an unable to load module message. right now my modules.conf file is completely blank, can I add something in there that it would see?

btw, I am using the 2.4.22 kernel that came with slackware.
 
Old 10-14-2003, 12:18 PM   #6
MsMittens
Member
 
Registered: Oct 2003
Location: Canada
Distribution: depends on the mood -- these days.. Slack!
Posts: 44

Rep: Reputation: 15
The ALSA package included with the Slackware 9.1 CDs is 0.9.6. As of Friday, ALSA has released a new version, 0.9.7, that I have found to be more stable and working.

Perhaps try downloading that?
 
Old 10-15-2003, 03:03 PM   #7
vrillusions
Member
 
Registered: Feb 2003
Location: Ohio, USA
Distribution: Ubuntu, Debian, CentOS
Posts: 99

Original Poster
Rep: Reputation: 25
It's working, had to go to L

I was going to remove the packages and reinstall to see if that did it when I noticed that there are 4 packages. In the ap directory there was only one. So I did some searching and found out that the other three are in /l installed all those and it worked fine. Now I just have to figure out why the last compile I did won't show the screen ohh well, that's another topic. Thanks for all the help everyone.

So to summarize all this:
When you recompile the kernel, aparently the alsa modules get removed/overwritten/whatever and no longer exist. To reinstall, mount cdrom into /mnt/cdrom and run the following two commands:

installpkg /mnt/cdrom/slackware/ap/alsa-*.tgz
installpkg /mnt/cdrom/slackware/l/alsa-*.tgz

Reeboot or run /etc/rc.d/rc.alsa and it should be up and running

Last edited by vrillusions; 10-16-2003 at 11:35 AM.
 
Old 10-15-2003, 10:20 PM   #8
JollyRogers
Member
 
Registered: Sep 2003
Location: Va USA
Distribution: Slackware
Posts: 81

Rep: Reputation: 16
vrillusions: good catch, I am so sorry I didn't catch the other ALSA pkg's in the /l directory. Glad you got it though You did mean /mnt/cdrom/slackware/ not mandrake right ??? HAH!

Think framebuffer if you are not seeing the screen during bootup...

Last edited by JollyRogers; 10-15-2003 at 10:24 PM.
 
Old 10-16-2003, 11:39 AM   #9
vrillusions
Member
 
Registered: Feb 2003
Location: Ohio, USA
Distribution: Ubuntu, Debian, CentOS
Posts: 99

Original Poster
Rep: Reputation: 25
Quote:
Originally posted by JollyRogers
You did mean /mnt/cdrom/slackware/ not mandrake right ??? HAH!
$%^*& d'oh, fixed now

Quote:
Originally posted by JollyRogers
Think framebuffer if you are not seeing the screen during bootup...
Don't think that would work, at the end of the startup script I put a `clear`. And I though a clear will clear out the framebuffer as well.
 
  


Reply



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
Can software compiled for old version work well shadkong Slackware 2 09-25-2005 10:50 AM
keyboard won't work with newly compiled kernel dr_zayus69 Linux - Hardware 10 06-05-2005 11:23 AM
Kernel compiled, but doesnt work fckalya Slackware 14 07-02-2004 01:34 PM
new compiled kernel 2.6.6 didnt work karfei00 Linux - General 4 06-09-2004 12:50 AM
Will a program compiled on one distro work on another? Razza2004 Linux - Newbie 1 05-08-2004 01:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

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

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration