Comment 145 for bug 755791
Revision history for this message
| Ian McMichael (ian-sigma-uk) wrote | #145 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
OK, I spoke too early in my last post. The machine was working fine all day Thursday with the official 3.0.0-13-generic kernel. Then when I booted it on Friday morning, lightdm displayed fine but the UI froze logging into any account with a background bitmap and mouse cursor. Unity did not display, and apart from using CTRL+ALT+F1 to switch to another console, the GUI was completely unusable.
Thinking I may have an ecryptfs issue, I booted off a USB stick with the live Oneric i386 image on it. This gave the same error. I removed the hard disk from the machine and tried again to completely remove any existing configuration or broken file-system causes. The result was the same, the GUI froze.
Next I downloaded a Natty i386 CD image and put this on the flash drive. This release had never caused me any issues on the HP Compaq 6715b. However, this now caused the same GUI freeze trying to launch Unity.
Eventually, I went back to the Lucid LTS i386 image with Gnome and everything booted fine and I was able to use the GUI from the flash drive. I used this UI to download the patched kernel I have posted in this bug and copied it back to my system. I booted back into the hard-drive installation, switched to console 1 with CTRL+ALT+F1 and used dpkg to re-install my 3.0.0.13 kernel with the AMD patches. After a reboot I was again able to log in and the Unity interface displays again. However, the horrific lagging and general lack of usability of the interface on this machine remain.
Does the RS690M have some sort of firmware the kernel can corrupt? The Canonical 3.0.0-13-generic kernel is the first time on this particular machine I have ever had a complete show-stopper bug where the UI fails to display. (This is after running Natty for 6 months on the same machine previously!) I now believe we may have two bugs here. One that corrupts the firmware in some way and actually stops the RS690M working on these machines, and another (maybe Compiz) that causes the horrendous lag and lack of usability.
What do others experiencing these issues think?