Comment 27 for bug 535653

I have installed Lucid amd64 on a new Thinkpad X100e (model NTS5EUK, dual core Neo L625, BIOS 1.21, 2GB, WLAN and Gobi WWAN). I enabled AMD virtualisation extensions in the BIOS, just because I could :-)

I initially found it crashed on pressing the brightness up/down function keys. As this was during a large apt-get update I reinstalled again from scratch, this time set radeon.modeset=0 in grub config *and* installed the proprietary video driver for good measure, and updated and rebooted.

Now the brightness and volume function keys work, but the machine locks up spontaneously a few minutes after power-up, even if I just leave it on the gdm screen and ssh to it from elsewhere. Mouse cursor won't move, device won't respond to pings over ethernet, needs a hard power-cycle.

I know the modeset flag is working because I get a low-res "Ubuntu o o o o o" instead of a high-res one at startup.

The options I can think of for isolating this are:
* try removing fglrx, rely instead on normal driver and radeon.modeset=0
* try disabling screensaver/auto sleep/power saving
* try without battery (maybe some charging event?)
* try disabling desktop effects
* try compiling new realtek driver
* try disabling virtualisation support in BIOS
* try i386 instead of amd64
* try the memory test, although the laptop appears to work fine with the supplied Windows 7 (32-bit Pro)

Until this is resolved, I have a very unfit-for-purpose laptop. Am wondering now if I should have bought a Macbook instead :-(