Red Hat Bugzilla – Bug 175290
snd_intel8x0 module correctly loaded for SiS 00:02.7 but no snd devices created
Last modified: 2015-01-04 17:23:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8) Gecko/20051129 Fedora/1.5-1 Firefox/1.5
Description of problem:
I have a Ahtlon64 desktop (Fujitsu Esprimo C) with following sound card:
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
Subsystem: Fujitsu Siemens Computer GmbH: Unknown device 109c
Flags: medium devsel, IRQ 58
I/O ports at 1400 [size=256]
I/O ports at 1000 [size=128]
Capabilities:  Power Management version 2
It seems it gets detected properly (in spite of the Unknown device above) because snd_intel8x0 kernel module is loaded). Apriopriate /dev/dsp device is not, however. The following dmesg snippet mat be relevant:
ACPI: PCI Interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 58
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
codec_ready: codec is not ready [0x340000]
ACPI: PCI interrupt for device 0000:00:02.7 disabled
Intel ICH: probe of 0000:00:02.7 failed with error -5
Version-Release number of selected component (if applicable):
Steps to Reproduce:
/dev/dsp doesn't get created by the ALSA module for the soundcard; it gets
created by the OSS emulation module, snd-pcm-oss. The ALSA module creates the
ALSA device nodes in /dev/snd.
I apologise for my ignorance. However, there is very little in /dev/snd either:
# ls -l /dev/snd/
crw------- 1 pawsa root 116, 1 Dec 8 16:21 seq
crw------- 1 pawsa root 116, 33 Dec 8 16:21 timer
1. 2.6.14-1.1749_FC5 behaves the same.
2. pci=routeirq does not change a thing.
3. http://who.is.free.fr/wiki/?SiS suggest it may be a conflict with the
suggests that the old OSS kernel driver i810-audio does not have the problem in
contrast to snd-intel8x0
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.