[TriLUG] SB Live! audio card recognition
Jason Faulkner
jason at oldos.org
Fri Sep 29 06:03:50 EDT 2006
I'm pretty certain the "SBLive Value" isn't really an SBLive at all.
It's some bastardized thing that doesn't use emu10k1. I don't remember
which one, though.
On 9/29/06, jwheeler at etherealfringe.com <jwheeler at etherealfringe.com> wrote:
> Hey guys,
>
> I have an older box running xUbuntu Dapper with an SB Live! audio card
> installed. For some reason I am getting this strange result from lspci:
>
> 0000:00:14.0 VGA compatible unclassified device: Creative Labs SB Live!
> EMU10k1 (rev 08)
> Subsystem: Creative Labs CT4832 SBLive! Value
> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Interrupt: pin A routed to IRQ 0
> Region 0: I/O ports at 1000 [disabled] [size=32]
> Capabilities: [dc] Power Management version 1
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 0000:00:14.1 Input device controller: Creative Labs SB Live! MIDI/Game
> Port (rev 08)
> Subsystem: Creative Labs Gameport Joystick
> Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64
> Region 0: I/O ports at fff0 [size=8]
> Capabilities: [dc] Power Management version 1
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
>
>
> It's calling it a VGA unclassified device and saying that the I/O is
> disabled for some reason. I can't figure out why. I have the ALSA emu10k1
> drivers installed (snd-emu10k1). They seem to be set up correctly, maybe
> I'm missing something. But as far as I can tell the card is not being
> recognized as an audio interface by the system at all.
>
> This card was supposed to be well supported with the ALSA drivers.
>
> Any ideas as to how I could help it become recognized as a Multimedia
> device? I don't completely understand how all of this works. Any insights
> at all would be great.
>
> lsmod | grep snd
>
> snd_emu10k1_synth 7296 0
> snd_emu10k1 117284 1 snd_emu10k1_synth
> snd_emux_synth 37376 1 snd_emu10k1_synth
> snd_seq_virmidi 7680 1 snd_emux_synth
> snd_seq_midi_emul 7168 1 snd_emux_synth
> snd_seq_dummy 3844 0
> snd_seq_oss 33536 0
> snd_seq_midi 9376 0
> snd_seq_midi_event 7552 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
> snd_seq 51984 9
> snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
> snd_rawmidi 25504 3 snd_emu10k1,snd_seq_virmidi,snd_seq_midi
> snd_ac97_codec 93088 1 snd_emu10k1
> snd_ac97_bus 2304 1 snd_ac97_codec
> snd_pcm_oss 53664 0
> snd_mixer_oss 18688 1 snd_pcm_oss
> snd_pcm 89864 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
> snd_seq_device 8716 8
> snd_emu10k1_synth,snd_emu10k1,snd_emux_synth,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
> snd_timer 25220 3 snd_emu10k1,snd_seq,snd_pcm
> snd_page_alloc 10632 2 snd_emu10k1,snd_pcm
> snd_util_mem 4608 2 snd_emu10k1,snd_emux_synth
> snd_hwdep 9376 2 snd_emu10k1,snd_emux_synth
> snd 55268 13
> snd_emu10k1,snd_emux_synth,snd_seq_virmidi,snd_seq_oss,snd_seq,snd_rawmidi,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
> soundcore 10208 3 sb_lib,sound,snd
>
> -John
>
>
>
>
> --
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>
--
Jason Faulkner
http://oldos.org
More information about the TriLUG
mailing list