[Bug 444192] Re: xserver / screen resolution not working

[mp]

Just loaded Lucid Beta 2, which cannot boot with standard parameters. It
ends in a screen with no text, some coloured background and a white
square in the middle of the screen. Mouse works, keyboard works, but the
only thing it can do for the user is to go to a console, such as via
CTRL+ALT+F2, where there are many error messages, all referring to the
same thing (which has been a problem since Jaunty for many!!!!):

[603.412359] [drm_radeon_fence_wait] *ERROR* fence (f3a55820:
0x000000115) 516ms time out

[610.972433] [drm_radeon_fence_wait] *ERROR* last signalled fence

[xxx.yyyyyy] [drm_radeon_fence_wait] *ERROR* fence (f3a55820:
0x000000115) 516ms time out going to restart GPU

Where xxx.yyyyyy indicates that these numbers are different for each
error message

The apport report submitted above is done after booting with:

noacpi
noapic
nolapic

With these parameters Lucid Beta 2 boots ok, but as can be seen in the
attached screenshot there is a strange error in the network-manager icon
in the systray

** Attachment added: "screenshot - to show faulty nm icon"
   http://launchpadlibrarian.net/44045205/Screenshot.png

-- 
xserver / screen resolution not working
https://bugs.launchpad.net/bugs/444192
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.