Re: No sound from Lenovo 3000 N100

2007-06-06 Thread Silla Rizzoli
On Wednesday 06 June 2007 18:09, Chuck Ebbert wrote: > On 06/06/2007 11:47 AM, Silla Rizzoli wrote: > > I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked > > before, unless I disable ACPI. > > Contents of /proc/interrupts might help. Oops, it was 2.6.21, I reverted the

Re: No sound from Lenovo 3000 N100

2007-06-06 Thread Chuck Ebbert
On 06/06/2007 11:47 AM, Silla Rizzoli wrote: > I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked > before, > unless I disable ACPI. > Contents of /proc/interrupts might help. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

No sound from Lenovo 3000 N100

2007-06-06 Thread Silla Rizzoli
I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked before, unless I disable ACPI. dmesg (ALSA debug messages are enabled): ACPI: PCI interrupt for device :00:1b.0 disabled ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21 PCI: Setting latency timer of

No sound from Lenovo 3000 N100

2007-06-06 Thread Silla Rizzoli
I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked before, unless I disable ACPI. dmesg (ALSA debug messages are enabled): ACPI: PCI interrupt for device :00:1b.0 disabled ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 21 PCI: Setting latency timer of

Re: No sound from Lenovo 3000 N100

2007-06-06 Thread Chuck Ebbert
On 06/06/2007 11:47 AM, Silla Rizzoli wrote: I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked before, unless I disable ACPI. Contents of /proc/interrupts might help. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to

Re: No sound from Lenovo 3000 N100

2007-06-06 Thread Silla Rizzoli
On Wednesday 06 June 2007 18:09, Chuck Ebbert wrote: On 06/06/2007 11:47 AM, Silla Rizzoli wrote: I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked before, unless I disable ACPI. Contents of /proc/interrupts might help. Oops, it was 2.6.21, I reverted the 2.6.22-rc3