Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
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.
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
BTW: I got my shared network printer to print Linux Its on a W2K PC shared. I setup Samba-Swat and then just configured the printer WOW! IT WORKED!!!!!!
do you know what the module is called? if not check the alsa directory on your machine and look for a file with a .o extension, I told you to edit etc/modules.conf, that was a mistake on my part, instead do this:
add line to /etc/rc.d/rc.modules
/sbin/modprobe {your_snd_module}
{your_snd_module} is the file with the .o extension that was created when you compiled the driver
now:
run #chmod /dev/dsp 666
or modify user group privledges im not sure but if that does not work then ive got the syntax wrong and it is chmod 666 /dev/dsp
to start sound run /sbin/modprobe {your_snd_module} at terminal. or reboot
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
Read post 15, I copied the terminal to that post as to what happened. I did the ./configure command that seemed to go ok but the next command make did not work. It gave an error which I copied to post 15. If you read post 15 maybe you can tell me what happened
ahh found your problem, you need to have th full kernel sources installed on your machine, you can either search for it as a package from your distro (the only thing that will work without a kernel recompile) or else you can download a kernel from www.kernel.org (2.4.20) and attempt to configure it manually directions at www.digitalhermit.com/linux/kernel.html
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
So how did I not get a full kernel? I brought RHL 8.0 Boxed from CompUSA. Was it something I didn't install? I can add it from the RHL 8.0 CDs I have. This is turning into a real mess.
you did get a full kernel, what you did not get were full kernel sources, these were likely omitted because they do not expect you to necessarily need it being that redhat is geared towards corporations and end users and it is about 150mb uncompressed. Most actual kernels are 1-2 mb and no more, dont think of this as a big mess think of this as a learning experience you might though just for peace of mind and so that you surely know how to do it as well as being fully up to date want to get the 2.4.20 kernel from www.kernel.org and use that
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
Your kidding me right? so what your saying is with RHL 8.0 if you want to install a sound driver your screwed
Tell me then why does RHL update agent say I'm updated with kernel 2.4.18-26.8.0 if infact I can't install a sound driver with that kernel?
BTW: I did get 2 Source Code CDs with to Boxed RHL set
I also emailed RHL Support, they responded by saying they can't help me because the driver I downloaded from RealTek is not a RHL driver, great huh? The way I see it is if RHL recognized my embedded sound card I wouldn't be going through this.
I find this amazing, all I want is my RHL to recognize my sound card
no no no thats not the way it is at all, what redhat has is the of kernel itself installed, they also have the source code to the kernel on one of the cds, if you tell it to on install it will install that, but normally it is part of the development package normally the kernel will support sound but some sound cards are not supported or the redhat installer did not pick it up correctly normally someone shouldnt have need of the sources if they are either aa newbie or are running a server, but they are an extra package just in case as you can see if it werent for your sound card you wouldnt need the kernel sources and you wouldnt otherwise care
btw once you understand the process this really is no harder than installing a windows driver, and if something goes wrong with a windows driver your most likely just screwed over and it wont even tell you whats wrong
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
Well I install the RHL source-code and the RHL update agent updated the source-code kernel to 2.4.18-26.8.0. It was under the "development tools" package section on the RHL CD.
So now that I have the source-code kernel I will try to install the downloaded driver I have for the RealTek ALC650' AC97 Sound Card.
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
Well I was able to run the "./configure" command that seemed to work ok
then I ran the "make install" this seems to work ok as well except the text from the end of the terminal window
permission to create the directory was denied, you need to either do this as root or from the console type the command su then it will ask you for your root password if you have one, if not it will just go now you have a console that has the same privileges as a root user
Distribution: RedHat Linux 8.0 kernel 2.4.18-26.8.0
Posts: 36
Original Poster
Rep:
I found this text file in the driver directory. It says what to do after I have created the package, but I just want to be sure this is correct?
Advanced Linux Sound Architecture - Driver
==========================================
Installation guide
The ALSA driver replaces the OSS/Free driver. The OSS/Free driver is
present in current Linux kernels (2.2). Since version 0.4.0, ALSA has
supported only 2.2+ kernels. The 2.0 kernels are no longer supported. You
must compile the kernel with sound support (you do not need to select
any of the other sound modules apart from sound support).
Before installing this driver, it will be helpful to read carefully
the documentation for insmod, modprobe, kmod and for the isapnp
module if you have an ISA PnP soundcard.
Module option name change after 0.9.0rc3
========================================
Note that module option names were changed in 0.9.0rc4. The 'snd_' prefix
was removed. You may use script in utils directory (module-options) to
convert your older /etc/modules.conf to newer one.
Quick install
=============
1) You must have full configured source for the Linux kernel which you
want to use for the ALSA drivers. Note that ALSA drivers are part
of the kernel, so there is necessary to resolve all symbol dependencies
between the used kernel and ALSA driver code. Partly installed kernels
(for example from distributor makers) can be unuseable for this action.
2) You must turn on sound support (soundcore module).
3) Run './configure' script.
If you have ISA Plug & Play soundcard, use --with-isapnp=yes switch.
If you want sequencer support, use --with-sequencer=yes switch.
If you do not want OSS/Free emulation, use --with-oss=no switch.
If you want turn on debug mode use --with-debug=full switch.
If you want debug soundcard detection try --with-debug=detect switch.
If you have kernel source code in another directory than /usr/src/linux,
use --with-kernel=<kernel_directory>.
Example: ./configure --with-isapnp=yes --with-debug=full
4) Run 'make install'.
5) Run the './snddevices' script to create new sound devices in /dev directory.
Skip this step, if you have a kernel with the DEVFS support.
6) Edit your /etc/modules.conf (see the kmod support section below).
7) Run 'modprobe snd-xxxx' where xxxx is the name of your card.
Note: If you have a ISA PnP soundcard you need to first run the isapnp
program from isapnptools package to initialize your
soundcard. You can also use the native ISA PnP support by
using the --with-isapnp=yes configuration switch, in which
case you do not need the isapnptools package.
You can also look at the utils/alsasound file. This script is designed for
the RedHat distribution, but it can be used with other distributions which
use System V style rc init scripts.
Note: All mixer channels are muted by default. You must use a native
or OSS mixer program to unmute appropriate channels (for example a
mixer from the alsa-utils package).
Note: This document notices the /etc/modules.conf file. Many current
distributions uses the old /etc/conf.modules file. Both names are
valid.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.