Results:
* No warning about thinkpad_acpi at bootup (still one about "Cannot reserve MMIO region" though)
* Network continued for a while after screen blanking, but then still locked up. Again, once the lookup had occurred, I could wake up the screen by moving trackpoint - but then clicking on the 'shutdown' option in the gdm screen caused the machine to hang hard, mouse cursor frozen.
* after reboot, lsmod shows thinkpad_acpi present
* Fn-F5 enables bluetooth (but I still can't see my WWAN card)
So some improved functionality, but no resolution to this lockup problem :-(
Even if it did, I'm not sure I'd be happy running an rc kernel which is 3 clicks ahead of the standard Lucid one...
Trying another kernel, this time: kernel. ubuntu. com/~kernel- ppa/mainline/ v2.6.35- rc1-lucid/ linux-image- 2.6.35- 020635rc1- generic_ 2.6.35- 020635rc1_ i386.deb
http://
(referred to from bug #557736 which is about thinkpad_acpi not loading)
Results:
* No warning about thinkpad_acpi at bootup (still one about "Cannot reserve MMIO region" though)
* Network continued for a while after screen blanking, but then still locked up. Again, once the lookup had occurred, I could wake up the screen by moving trackpoint - but then clicking on the 'shutdown' option in the gdm screen caused the machine to hang hard, mouse cursor frozen.
* after reboot, lsmod shows thinkpad_acpi present
* Fn-F5 enables bluetooth (but I still can't see my WWAN card)
So some improved functionality, but no resolution to this lockup problem :-(
Even if it did, I'm not sure I'd be happy running an rc kernel which is 3 clicks ahead of the standard Lucid one...