Red Hat Bugzilla – Bug 205603
IBM X60s sound not working.
Last modified: 2015-03-04 20:17:32 EST
Description of problem:
After installing the latest Fedora Core Devel tree i've found that despite the
kernel and the system itself detecting and configuring the soundcard in my IBM
X60s laptop sound doesn't work.
Neither playing nor recording something yields and results.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install latest FC-devel tree
2. Try to play a sound during firstboot sound setup or later in the system
3. Enjoy the silence... :)
Sounds don't play/get recorded
Sounds should play ;)
I've attached the 2 system-config-soundcard debug files that are written when
you claim not to have heard any sounds. Looks like something isn't set up properly.
Created attachment 135779 [details]
S-C-S log of running the play command
Created attachment 135780 [details]
Configuration of the machine with all information
"It works for me"--- Lenovo X60s with FC6 and the 2.6.18 kernels (currently
Please check if the internal Modem is enabled in BIOS. If it is disabled, enable
it and try i again. I mean to remember that this is a BIOS bug.
Did you try using the hardware volume control buttons (if any)
on the keyboard?
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.