Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
02-28-2006, 06:35 PM
|
#16
|
Member
Registered: Apr 2004
Location: Arkansas
Distribution: Ubuntu 8.10
Posts: 365
Rep:
|
Quote:
Originally Posted by cwwilson721
If you read everything, you would see he compiled it against 2.4. When he switches to 2.6, no sound. Ergo, compile alsa against 2.6
The alsa utils must be compiled against the 2.6 kernel also. Basically, everything alsa has to be compiled against the kernel you are using.
The OP could also use the alsa in /linux-2.6.13 in cd2. That would work too
|
Only the ALSA drivers need to be compiled for the particular kernel you are using. ALSA utils, libs and oss aren't kernel specific.
Later,
MMYoung
|
|
|
03-01-2006, 12:27 PM
|
#17
|
Senior Member
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 15.0, Slackwarearm 14.2
Posts: 1,158
|
Quote:
Originally Posted by MMYoung
Only the ALSA drivers need to be compiled for the particular kernel you are using. ALSA utils, libs and oss aren't kernel specific.
Later,
MMYoung
|
That's why I was confused when he couldn't make it work by compiling in-kernel ALSA. Something else must have been wrong (which broke USB, too). Anyway, it's all sorted out now  .
|
|
|
03-13-2006, 11:26 PM
|
#18
|
Member
Registered: Nov 2005
Location: California
Distribution: ubuntu 10
Posts: 162
Original Poster
Rep:
|
Quote:
Originally Posted by gbonvehi
Can you post the output of: lsmod
and grep SND .config && grep SOUND .config (Of course, run this on your kernel's source directory)
|
Alas, I cannot. My *nix box has no internet access, no floppy drive, no internal cd burner, no usb support; and my nforce4 hardware completely broke the windows xp I was dual-booting.
In other news, I finally was able to compile the alsa-driver package against my 2.6 kernel, and just to be on the safe side recompiled the utilities and libraries packages. I still get that "no libao" message.
I'll try using Mr. Volkerding's .config file.
|
|
|
03-13-2006, 11:27 PM
|
#19
|
Member
Registered: Nov 2005
Location: California
Distribution: ubuntu 10
Posts: 162
Original Poster
Rep:
|
double post.
|
|
|
03-14-2006, 12:01 AM
|
#20
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
Quote:
Originally Posted by gbonvehi
Can you post the output of: lsmod
and grep SND .config && grep SOUND .config (Of course, run this on your kernel's source directory)
Quote:
Originally Posted by djeikyb
Alas, I cannot. My *nix box has no internet access, no floppy drive, no internal cd burner, no usb support; and my nforce4 hardware completely broke the windows xp I was dual-booting.
|
|
You shoud have run it in the console:
$lsmod (shows loaded modules)
$cd /usr/src/your-linux-kernel-version
$grep SND .config && grep SOUND .config (shows your sound config)
|
|
|
03-14-2006, 01:01 AM
|
#21
|
Member
Registered: Nov 2005
Location: California
Distribution: ubuntu 10
Posts: 162
Original Poster
Rep:
|
I can very easily type the commands and gaze at the output. Problems manifest when I try to post the output to this thread without going through the painstaking process of accurately copying the screens output to a piece of paper by hand, and then typing it into a text box. Hmmm. I suppose I could take screenshots with my digital camera. That'd be more accurate even than copying and pasting output to a text file.
|
|
|
03-14-2006, 01:29 AM
|
#22
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
Wait. You don't need it. Do this:
$lsmod > lsmod.txt
Then you will get lsmod.txt file where the output of lsmod will reside. Post its contents.
Read: http://slackbook.org/html/shell-comm...ND-LINE-PIPING
|
|
|
All times are GMT -5. The time now is 06:40 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|