Re: [Alsa-user] Intel HDA on Fujitsu: no sound
Brought to you by:
perex
From: Antonio <av...@te...> - 2005-12-14 07:37:44
|
I have installed the drivers from the CVS sources and I have sound (although with a weird background noise). To load the driver on my FS Amilo M 1451G I have to use these parameters: modprobe snd_hda_intel position_fix=1 model=F1734 Anyway the sound card is not autodetected by Alsa (if I don't set the "model" then the sound card doesn't work). Again my PCI info: 0000:00:1b.0 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) Subsystem: Unknown device 1734:1094 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: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 16 Region 0: Memory at ffef8000 (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: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [70] #10 [0091] Note that Linux does not know about this device either. (Unknown device) The sound keys in the laptop (Fn+volume up, Fn+volume down, Fn+volume mute) do not work, but the mixer (KDE mixer) works nice to control volume. Cheers, Antonio Lee Revell wrote: >On Tue, 2005-12-13 at 16:49 +0000, Oak wrote: > > >>Hello Antonio, >> >>I have FS AMILO M3438G with same sound card (you have probably >>same/similalr laptop). After weeks of hard trying, I found out, that the >>soundcard is POWERED OFF! At least it seems it is, studiyng the log from >>commercial OSS driver, which I also tryed. So it might be an ACPI issue. >>That's also explain, why it's completely resistable to any attempt to >>install driver. Strange, it is still visible via "lspci". >> >>Please, could anybody advise, what could be the cause for this? How to >>analyze it? How to try to fix it? >> >> > >This is a driver and/or kernel bug. Please report it to alsa-devel >and/or the ALSA bug tracker: > >https://bugtrack.alsa-project.org/alsa-bug/main_page.php > >Lee > > > > |