On Thu, 2005-10-20 at 16:15 -0500, Jeff Smelser wrote: > This sounds kinda dumb, but I would pull out a gentoo live CD and see if it > detects it. If it doesnt, there is something bios/hardware wise wrong with > your setup, if it does, we can start going through kernel wise..
Interesting news, here. I booted into the LiveCD and it did not change anything. HOWEVER, I did try once again to enable BIOS ACPI support. I booted, keyboard stopped working, but I checked logs on the next boot and found out that it did bring up both CPU entries - found ACPI and everything. Oct 20 20:23:31 statux ACPI: RSDP (v000 IntelR ) @ 0x000f6bf0 Oct 20 20:23:31 statux ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3040 Oct 20 20:23:31 statux ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff30c0 Oct 20 20:23:31 statux ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff7280 Oct 20 20:23:31 statux ACPI: DSDT (v001 INTELR AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000 Oct 20 20:23:31 statux ACPI: Local APIC address 0xfee00000 Oct 20 20:23:31 statux ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Oct 20 20:23:31 statux Processor #0 15:4 APIC version 20 Oct 20 20:23:31 statux ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Oct 20 20:23:31 statux Processor #1 15:4 APIC version 20 Oct 20 20:23:31 statux ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Oct 20 20:23:31 statux ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Oct 20 20:23:31 statux Using ACPI for processor (LAPIC) configuration information Oct 20 20:23:31 statux Intel MultiProcessor Specification v1.4 Oct 20 20:23:31 statux Virtual Wire compatibility mode. Oct 20 20:23:31 statux OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000 Oct 20 20:23:31 statux I/O APIC #2 Version 17 at 0xFEC00000. Oct 20 20:23:31 statux Enabling APIC mode: Flat. Using 1 I/O APICs Oct 20 20:23:31 statux Processors: 2 I can't test this any further with my disappearing keyboard issue. So now, the problem is: Why does enabling ACPI in the BIOS kill my keyboard sometime after boot. It works before it hits the OS. It's like the PS/2 port drops. Sounds like an interrupt issue. I know, a USB keyboard would possibly solve the issue but I'm interested in solving the issue and not working around it. -- Statux <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part