Re: problem with sound (esound) since a few days
On Thu, 28 Oct 2004 13:50:09 +0200, Uwe Dippel wrote:
> Though I didn't change anything on purpose; just the usual upgrades, I
> lost my sound a few days ago.
> Finally, the lspci -v gives me:
>
> 0000:00:1f.5 Multimedia audio controller:
> Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
> (rev 01)
> Subsystem: Dell: Unknown device 0139
> Flags: bus master, medium devsel, latency 0, IRQ 7 I/O ports at
> d800 [size=256]
> I/O ports at dc40 [size=64]
> Memory at faeff800 (32-bit, non-prefetchable) [size=512] Memory at
> faeff400 (32-bit, non-prefetchable) [size=256] Capabilities: [50]
> Power Management version 2
Firstly, thanks to all of your helpful advices in this friendly community !
The problem is 'solved'. To me it's no solution, since - as I wrote in the
OP - I hadn't done any changes. Running for months and just apt-get
update / upgrade. And then it *must not* break on Sarge.
This is what I found in dmesg:
ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 7 (level, low) -> IRQ 7
unable to grab IRQ 7
Intel ICH: probe of 0000:00:1f.5 failed with error -16
And /proc/interrupts were identical; showing IRQ 7 to be occupied by
LPT0:, contrary to what lspci makes me believe.
I rebooted and disabled the Parallel Port at reboot and now everything is
back to normal. Better said: 'normal'; because there is no inherent
necessity to load the audio controller to IRQ7; and neither does it
complain; I ask you to read the dmesg properly: ACPI has its problems with
it.
This is how it looks when working properly:
ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 7 (level, low) -> IRQ 7
0: 66676279 XT-PIC timer
1: 22 XT-PIC i8042
2: 0 XT-PIC cascade
7: 170589 XT-PIC Intel 82801DB-ICH4, Intel 82801DB-ICH4 Modem
8: 4 XT-PIC rtc
9: 0 XT-PIC acpi
11: 9023557 XT-PIC eth0, ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd, y
enta, yenta, ohci1394
12: 58 XT-PIC i8042
14: 182138 XT-PIC ide0
Since I don't need the local LPT0:, I shall leave this 'solution' in place.
But someone else might hit this bug / trap elsewhere; so beware !
Thanks again,
Uwe
Reply to: