I'm using the DELL XPS M2010 laptop, which used to work fine with gentoo for several years. In the last few month linux must have made major changes with its hardware detection, because my keyboard is not detected anymore. To be even more specific: the KEYS are not detected anymore - the touchpad can still be used. To be more specific: the keyboard is detachable, so the laptop uses a kind of bluetooth emulation. You have to pair the keyboard with the laptop using the Windows XP drivers. Afterwards, the keyboard is automatically detected so you are able to use it during the booting process. You are able to enter the bios and use the keyboard with linux. This bug is not gentoo specific. It happens with all newer linux distributions. I tested the the following linve cds: ubuntu 10.04, 10.10, knoppix 5.2. You also can find a very good bug report for SuSE in the novell bulletin board: https://bugzilla.novell.com/show_bug.cgi?id=589329 Reproducible: Always Steps to Reproduce: 1. boot linux 2. same result when using knoppix, ubuntu or suse live cds Actual Results: The keys on the keyboard are not detected Expected Results: keyboard and mouse should be detected by the laptop
Could you attach kernel logs on unplugging/replugging the keyboard ? May it be something similar to bug 344849 ?
The keyboard can be attached the laptop. But that is only for recharging the battery - so the kernel log shows no entries. The connection between the laptop and the keaboard is always established via bluetooth, no matter if the keyboard is attached or detached. If the bluetooth connection is disrupted, I have to install Windows Vista to establish a new connection with the Win XP drivers. I don´t think that it is similar to the bug 344849, because the keyboard works fine without any installed bluetooth packages. I don't know how it works, but the connection is already established even before the operating system is started - otherwise I won`t be able to acces the bios or make a choice in the bootloader.
Please reopen this bug report when there's a specific software package that fixes the issue, so we can assign the bug report properly. You could start by posting your `emerge --info' output in a comment, and attaching dmesg output of the failing bluetooth connection as a file. Until then, there is no specific problem to solve here.
