i installed red hat 9 and my sound still wont work. Red hat has found a sound driver that "should" work for my intergrated sound card but for some reason mainly this reason:

The i810_audio driver could not be loaded. This soundcard may not be compatible with Red Hat Linux.

that's what happens when i run redhats sound card detection. Also a boot somthing calle imod or somthing like that fails to load (it's hard to read because it moves fast). Anyone have any ideas?

Also note that all the info my on my sound card is correct but it seems like the kernel can run the correct info. This may be because I might be using the same audio driver i used for redhat 8 (the driver didn't work). I also have problems with updating my kernel. It has somthing to do with that same driver's (i think) depenencies.

Hi cprogrck,
can you do this and post the output, please:
open a terminal as root
run the sound card detection
in the terminal issue this command: tail /var/log/messages
This will probably give you (us) more information about the issue at hand.

Thanks,
- drowstar

May 28 10:35:05 x1-6-00-09-5b-0b-8
b-37 rhnsd[1687]: Red Hat Network
Services Daemon starting up.
May 28 10:35:05 x1-6-00-09-5b-0b-8
b-37 rhnsd: rhnsd startup succeede
d
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 kernel: Intel 810 + AC97 Audi
o, version 0.24, 17:27:30 Mar 13 2
003
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 kernel: PCI: No IRQ known for
interrupt pin A of device 00:06.0
. Please try using pci=biosirq.
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 kernel: i810: NVIDIA nForce A
udio found at IO 0xd800 and 0xd400
, MEM 0x0000 and 0x0000, IRQ 0
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 kernel: i810_audio: unable to
allocate irq 0
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 insmod: /lib/modules/2.4.20-8
/kernel/drivers/sound/i810_audio.o
: init_module: No such device
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 insmod: Hint: insmod errors c
an be caused by incorrect module p
arameters, including invalid IO or
IRQ parameters. You may fin
d more information in syslog or th
e output from dmesg
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 insmod: /lib/modules/2.4.20-8
/kernel/drivers/sound/i810_audio.o
: insmod sound-slot-0 failed
May 28 10:38:11 x1-6-00-09-5b-0b-8
b-37 modprobe: modprobe: Can't loc
ate module sound-service-0-3

Hi cprogrck,
the important part is this:
This seems to suggest that your system indeed cannot talk to your soundcard. (There might be a problem with the i810_audio driver. I am not sure, I have tried this driver on a fedora system and it didnt work either. To be honest, I wasnt able to solve the problem then. Worked on SuSE though.)
However, this may just as well be a less difficult problem to solve.
I am astonished about this section:
It seems to suggest that the driver has been loaded.

This needs further investigating. Please do a lsmod and lspci and post the output. (it would also be helpful, if you'd check if the output differs before and after you run the sound card detection program. The crucial part is where the output contains "810" (or "i810" or "Intel 810". "810" is a resonable compromise. You can filter the output by attaching "| grep 810" to either command (e.g.: lspci | grep 810).

One thing you could try right now (without more information) is check, if your sound controls are not muted (this was a problem on fedora core 1.9x, might just be there redhat, too). The command would be alsacntl (I am not completely sure right now. Type "alsa", hit tab and chose the command that seems to be closest). If all controls that show up are on zero, you've got (at least part of) your problem's solution right there. Bring them up to a medium level.

Good luck, I'll respond as soon as I can,
- drowstar

i updated redhat 9 to fedora core 2. It has great driver support, but of course there's always that problem with Wine.

Wine works great for me on Fedora Core 2

cprogrck,
what do you mean: "that problem with Wine"?
Worked for me, when I still used it. (and thats to say a lot, because Fedora had the most issues I have ever experienced on my system)

Anyways, any luck with your sound? and are there any questions about wine I might be able to answer?

Later,
- drowstar

for some reason i had trouble runing wine on fedora core 2 it turns out that there's some kind of error with exec-sheild. At first i thought all was lost. See wine worked fine for me in redhat9 but in fedora you have to run echo 0 > ./proc/sys/kernel/exec-sheild or somthing like that. It has to do with the way red hat tried to prevent buffer overflows by makeing programs run at a certain point in ram (i think). However most windows programs need to run in the same locations.

--------------before
[root@x1-6-00-09-5b-0b-8b-37 root]# wine regedit
Segmentation fault
--------------after
[root@x1-6-00-09-5b-0b-8b-37 root]# echo 0 > /proc/sys/kernel/exec-shield
[root@x1-6-00-09-5b-0b-8b-37 root]# wine regedit
[root@x1-6-00-09-5b-0b-8b-37 root]#
--------------------------------------------------------------------------------------------------------
notice that wine ran regedit after a ran the echo 0 > /proc/sys/kernel/exec-shield command. It's actually a common problem with fedora core 2. I guess some people are lucky.

goto this thread

http://www.linuxquestions.org/questions/history/178011

my error wasn't the same but it works. I can have my sound and my wine too. (ummmm)