[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sheflug] Soundblaster Live! not working
Ok, I've answered my own question about which IRQ the card uses, IRQ
10. And I am none the wiser. Now I see that the IRQ is not always the
same, in fact currently the devices 00:07.3, 00:07.2 and 00:0b.0 (one of
which I assume is the SBL) are all sharing IRQ 10. So that could be the
problem, I guess. Now how to fix it?? useful that the USB is using IRQ
10 as I am not using any USB devices...and I have 2 USB ports...let me
guess, 00:07.3 and 00:07.2? maybe the reason it works on old system is
that is kernel 2.2.15 or so with no USB support.
sorry about the rambling. Perhaps someone can put me out of my misery
if I am way off target.
Matt.
<from /var/log/messages:>
Jul 7 18:29:09 linux kernel: PCI: Found IRQ 10 for device 00:07.3
Jul 7 18:29:09 linux kernel: PCI: The same IRQ used for device 00:07.2
Jul 7 18:29:09 linux kernel: PCI: The same IRQ used for device 00:0b.0
Jul 7 18:29:09 linux kernel: usb-uhci.c: USB UHCI at I/O 0xc800, IRQ 10
root@pc-62-31-17-175-sh:/home/matt > cat /proc/version
Linux version 2.4.4-4GB (root [at] Pentium.suse.de) (gcc version 2.95.3
20010315 (SuSE)) #1 Fri May 18 14:11:12 GMT 2001
root@pc-62-31-17-175-sh:/home/matt > cat /proc/asound/cards
0 [card1 ]: EMU10K1 - Sound Blaster Live!
Sound Blaster Live! at 0xd000, irq 10
root@pc-62-31-17-175-sh:/home/matt > cat /proc/asound/devices
0: [0] : control
1: : sequencer
6: [0- 0]: mixer
8: [0- 0]: raw midi
9: [0- 1]: seq-virmidi
10: [0- 2]: seq-virmidi
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
25: [0- 1]: digital audio capture
26: [0- 2]: digital audio capture
33: : timer
root@pc-62-31-17-175-sh:/home/matt > lsmod
Module Size Used by
sg 21920 0 (autoclean) (unused)
snd-pcm-oss 18816 1 (autoclean)
snd-pcm-plugin 15024 0 (autoclean) [snd-pcm-oss]
snd-mixer-oss 5120 0 (autoclean) [snd-pcm-oss]
snd-seq-oss 28848 0 (autoclean)
snd-synth-emu10k1 4288 0
snd-synth-emux 26592 0 [snd-synth-emu10k1]
snd-seq-midi-emul 4480 0 [snd-synth-emux]
snd-seq-virmidi 8496 0 [snd-synth-emux]
snd-seq-midi 3568 0 (unused)
snd-seq-midi-event 2992 0 [snd-seq-oss snd-seq-virmidi
snd-seq-midi]
snd-seq 42656 0 [snd-seq-oss snd-synth-emux
snd-seq-virmidi snd-seq-midi snd-seq-midi-event]
snd-card-emu10k1 2320 1
snd-emu10k1 21936 0 [snd-synth-emu10k1 snd-card-emu10k1]
snd-pcm 30560 0 [snd-pcm-oss snd-pcm-plugin
snd-emu10k1]
snd-timer 8560 0 [snd-seq snd-pcm]
snd-emux-mem 1616 0 [snd-synth-emux snd-emu10k1]
snd-rawmidi 9664 0 [snd-seq-midi snd-emu10k1]
snd-ac97-codec 24576 0 [snd-emu10k1]
snd-mixer 24224 0 [snd-mixer-oss snd-emu10k1
snd-ac97-codec]
snd-seq-device 4032 0 [snd-seq-oss snd-synth-emu10k1
snd-synth-emux snd-seq-midi snd-seq snd-card-emu10k1 snd-rawmidi]
snd 34032 1 [snd-pcm-oss snd-pcm-plugin
snd-mixer-oss snd-seq-oss snd-synth-emux snd-seq-virmidi snd-seq-midi
snd-seq-midi-event snd-seq snd-card-emu10k1 snd-emu10k1 snd-pcm
snd-timer snd-emux-mem snd-rawmidi snd-ac97-codec snd-mixer
snd-seq-device]
soundcore 3632 9 [snd]
mousedev 4032 0 (unused)
hid 11760 0 (unused)
input 3168 0 [mousedev hid]
usb-uhci 21840 0 (unused)
usbcore 47120 1 [hid usb-uhci]
ipv6 126272 -1 (autoclean)
af_packet 11648 1 (autoclean)
8139too 11520 1 (autoclean)
ipchains 33408 0 (unused)
reiserfs 156432 2
root@pc-62-31-17-175-sh:/home/matt >
matt fairtlough wrote:
>
> Odd one this. One my old system, this works just fine. But under
> SuSE7.2, not a peep (nor are there any warning messages I can see). So
> it isn't the hardware itself or how it is connected up: I checked and
> haven't altered anything since.
>
> I gather that the driver to use is emu10k1. So I tried (not really
> knowing what modprobe does or what it can break):
>
> root [at] pc-62-31-17-175-sh:/home/matt > modprobe emu10k1
> /lib/modules/2.4.4-4GB/kernel/drivers/sound/emu10k1/emu10k1.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters
> /lib/modules/2.4.4-4GB/kernel/drivers/sound/emu10k1/emu10k1.o: insmod
> /lib/modules/2.4.4-4GB/kernel/drivers/sound/emu10k1/emu10k1.o failed
> /lib/modules/2.4.4-4GB/kernel/drivers/sound/emu10k1/emu10k1.o: insmod
> emu10k1 failed
> root [at] pc-62-31-17-175-sh:/home/matt >
>
> [perhaps you wondered about the odd hostname; I'm coming to that...]
>
> So what is the problem? Well, it could be that the sound card is
> sharing an IRQ with something else (could it?).
>
> >From /var/log/messages I extracted:
>
> Jul 7 16:39:12 linux kernel: PCI: Found IRQ 11 for device 00:07.2
> Jul 7 16:39:12 linux kernel: PCI: The same IRQ used for device 00:07.3
> Jul 7 16:39:12 linux kernel: PCI: The same IRQ used for device 00:0b.0
>
> now how do I find out which devices these are, and if there is a clash,
> I know I have to alter the BIOS settings but I've never understood how
> to manage with apparently too few IRQ numbers.
>
> any suggestions?
>
> thanks,
>
> Matt.
> ---------------------------------------------------------------------
> Sheffield Linux User's Group - http://www.sheflug.co.uk
> To unsubscribe from this list send mail to
> - <sheflug-request [at] vuw.ac.nz> - with the word
> "unsubscribe" in the body of the message.
>
> GNU the choice of a complete generation.
---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word
"unsubscribe" in the body of the message.
GNU the choice of a complete generation.