kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #30219
[Bug 107821] Re: no sound with lenovo 3000 n100 0768FEG
** Changed in: alsa-driver
Importance: Unknown => Undecided
** Changed in: alsa-driver
Status: In Progress => New
** Changed in: alsa-driver
Remote watch: ALSA Bug Tracker #3025 => None
** Changed in: alsa-driver
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/107821
Title:
no sound with lenovo 3000 n100 0768FEG
Status in ALSA driver:
Invalid
Status in “linux” package in Ubuntu:
Won't Fix
Status in “linux-source-2.6.20” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: linux-image-2.6.20-15-lowlatency
I own the mentioned laptop and am unable to get sound working in an
up2date feisty installation.
Some stats:
--------------CUT------------
% lspci -vv
[...]
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 02)
Subsystem: Lenovo Unknown device 2066
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at d2400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express Unknown type IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <64ns, L1 <1us
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
Link: Latency L0s <64ns, L1 <1us
Link: ASPM Disabled CommClk- ExtSynch-
Link: Speed unknown, Width x0
[...]
% lspci -nv
[...]
00:1b.0 0403: 8086:27d8 (rev 02)
Subsystem: 17aa:2066
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at d2400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Unknown type IRQ 0
[...]
% aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC861VD Analog [ALC861VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0
% cat /proc/alsa/oss/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.14rc1 emulation code)
Kernel: Linux artio 2.6.20-15-lowlatency #2 SMP PREEMPT Sun Apr 15 06:20:10 UTC 2007 x86_64
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
HDA Intel at 0xd2400000 irq 22
Audio devices:
0: ALC861VD Analog (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
31: system timer
Mixers:
0: Realtek ALC861-VD
% uname -a
Linux artio 2.6.20-15-lowlatency #2 SMP PREEMPT Sun Apr 15 06:20:10 UTC 2007 x86_64 GNU/Linux
--------------CUT------------
dmesg contains some interesting things about device 00:1b.0 (=the soundcard):
--------------CUT------------
[ 44.939043] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
[ 44.939072] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 44.949961] hda_codec: Unknown model for ALC660VD/ALC861VD, trying auto-probe from BIOS...
[ 45.007066] si3054: cannot initialize. EXT MID = 0000
--------------CUT------------
the volume for virtually any channel is at 100%, but everything
remains silent.
This looks similar to bug #39517, but as I am running feisty with
2.6.20, this should not be a problem.
I've also tried to use the latest and greatest alsa-drivers directly
from alsa, but also without success.
any ideas?
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/107821/+subscriptions