LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-15-2004, 11:38 PM   #1
dejavu_01
Member
 
Registered: May 2004
Location: Bangkok, Thailand
Distribution: Simply Mepis 8.0 32bit
Posts: 89

Rep: Reputation: 15
soundcard dead after compile kernel


Hello

After I compile kernel 2.4.22 to add ACPI support for my notebook, I found my AC97sound card stop working. Despite runing alsaconf the soundcard is not detected. In makemenuconfig I didn't make any change regarding sound setup. Any solution might help.
 
Old 05-16-2004, 12:02 AM   #2
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
Check first to see if the soundcard driver is compiled into the kernel, or as a module.

The output of /sbin/lsmod will help to see if the driver is currently loaded.

I know that on my slack boxes, if I compile alsa drivers as modules, then alsaconf will pick them up.

Are you sure you did make modules and make modules_install ?

--Shade
 
Old 05-16-2004, 06:45 AM   #3
Nichole_knc
Member
 
Registered: Mar 2004
Location: Georgia
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287

Rep: Reputation: 30
Under kernel version 2.4.## and if you are using alsa you DO NOT compile the sound card into the kernel. All that is required is that you (y) SOUND SUPPORT all else as required should be (m).

Now here is what happened when you re-did your kernel and modules...
Alsa makes a sound directory in the /lib/modules/2.4.##/kernel directory. When you do a make of the kernel and make install the mods WITHOUT changeing yhe EXTRAVERSION option in the Makefile make modules_install wipes the /lib/modules/2.4.## out completely this includes the alsa sound directory.
You must re-install alsa from the cd, nfs or sources or whatever install medimum you may use.
Then follow the standard alsa setup...
alsaconf
alsamixer
alsactl store.

Kernel build tip....
When you have a working kernel and desire to make changes the safest way is to edit the /usr/src/linux/Makefile EXTRAVERSION=YOUR_UNIQUE_NAME_HERE
This way a bzImage-YOUR_UNIQUE_NAME can be cped to /boot/vmLinuz-YOUR_UNIQUE_NAME, System.map and .config both YOUR_UNIQUE_NAME
And when you make modules and make modules_install they will do so as /lib/modules/2.4.##-YOUR_UNIQUE_NAME leaving the former working kernel and related mods intact.
Once you have edited lilo.cont and added the new image= after your working setup and ran lilo you can reboot, test and configure any desired missing elements in the new kernel setup. i.e. alsa would require a re-install to install in the new mods directory. I have found copying them from a working mod source does not work even when it is the 'same' kernel version with only added mods. I consider this an extreme shortfall in the linux kernel as the docs state you can complie mods as needed and insert them on the fly. I does not work. I have found this to be true for mant 3rd party mods that I use.

Using the EXTRAVERSION= allows you to keep your working kernel in case you have an unseen issue with the new kernel build untill boot. This way you may reboot back to a working setup and 'fix' the new build.
Note; when building a kernel it is good to use nohup to have a readable output file for error checking..
syntax below...
nohup make bzImage &
tail -f nohup.out # if you like to watch
# for kernel version < 2.6 open another console and
nohup make modules 1>modules.out 2>modules.err &
# go take a nap
less nohup.out # check for kernel compile time error
less modules.err # check for errors
# if all is well
make modules_install
# and them the usual required kernel moves....

Yes I build lots of 2.4.## kernels as I have many-a-computers. LOL I don't even use xconfig, menuconfig, etc. I directly jed .config and make changes there then make oldconfig, make depends and then the above without problems.
 
Old 05-16-2004, 08:43 AM   #4
dejavu_01
Member
 
Registered: May 2004
Location: Bangkok, Thailand
Distribution: Simply Mepis 8.0 32bit
Posts: 89

Original Poster
Rep: Reputation: 15
thanks a lot. First I'll try reinstall Allsa from slackware CD first, I'll recompile and make sure all soundcards are compiled as module.
 
Old 05-18-2004, 03:05 AM   #5
dejavu_01
Member
 
Registered: May 2004
Location: Bangkok, Thailand
Distribution: Simply Mepis 8.0 32bit
Posts: 89

Original Poster
Rep: Reputation: 15
I made sure only "sound support" is selected (y) in sound section then re-compile and install the kernel. Then I install alsa-driver, alsa-lib for all the nessary sound modules. Despite all this, when reboot the init script shows a long list of faileurs in loading sound modules. Alsaconf run up fine and detect my sound card. I try use xmms to play some sound and got "sound not ready" warning dialogbox. And mixer programs won't start.

strange though in /lib/modules/2.4.22/sound the sound modules in there is in .gz format so I just gunzip them all, but this doesn't help at all. This is on a notebook with Via 82xx AC97 sound card. The sound related modules all fail to load. The only thing I made change to the original kernel is adding ACPI support
 
Old 05-18-2004, 04:27 AM   #6
Nichole_knc
Member
 
Registered: Mar 2004
Location: Georgia
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287

Rep: Reputation: 30
Are you running devfs?
From previous post I would assume you are not...
But it sounds like a /dev issue..

After testing devfs and
When I was having continueing sound problems with alsa I got the sources and did a direct build.
I am using 1.0.4. http://www.alsa-project.org/
You would need
alsa-drivers
alsa-lib
alsa-oss
alsa-utils
make install in that order... alsa-driver contains the docs.
There is a script with the alsa-drvers that you run once you have made and installed the alsa sources. (./snddevices) it rebuilds the /dev for sound...
This was my fix..
NOTE; The .gz in the sound directory are correct.
 
Old 05-21-2004, 05:19 AM   #7
dejavu_01
Member
 
Registered: May 2004
Location: Bangkok, Thailand
Distribution: Simply Mepis 8.0 32bit
Posts: 89

Original Poster
Rep: Reputation: 15
my sound works again !! :-) I collect the alsa package from Slackware9.1 CD then installed them by using tar from / . After some reboot it worked.
 
  


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
How does the kernel detect a dead route? jlinkels Linux - Networking 3 01-21-2005 02:46 PM
keyboard dead with kernel 2.6.4 matrixfx Linux - Hardware 2 03-26-2004 10:06 PM
Squid:2nd Browser access Internet SPEED dead becomes dead slow mwj Linux - Software 1 10-04-2003 01:40 PM
kernel compile thread - dead link itsjustme Slackware 0 09-04-2003 09:05 AM
Is my soundcard dead now? Eits0 General 4 07-01-2002 11:01 AM

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

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