ubuntu-x-swat team mailing list archive

[Invader Zim <invasorzim0@xxxxxxxxx>]

As I said before, the fatal error doesn't show up in the log anymore.
There is no fatal error anymore.

I'm gonna attach the only error that show up in messages. And still,
that error only occurs when, after boot up, I login at the console, and
modprobe savagefb.

So there are 2 modules for savage, savage and savagefb.

But the error also happens using xdm, and I can log in normally in xdm.
So the error logged is probably not related.

Also, maybe unrelated, when I press ctrl+alt+f1 on kdm/xdm to go to the
console, the "kubuntu logo splash loading screen" loading dots and the
blue background is still there. I use the console with the dots lighting
up and a blue screen, which makes it hard to use the console. Applies to
all consoles, not just "f1".

To note, the "screen blink" in kdm happens right after the screen is
drawn fully white, and it quickly refreshes to the kdm background, and
only then the screen goes black - as in the X server being restarted.

When I log in using xdm or startx, I can see the same white box being
drawn, but its just occupying 1/4 of the screen, and after that the
desktop background is drawn, along with the rest of it.

** Attachment added: "Messages. Scroll to the end of the file to see the "error"."
   http://launchpadlibrarian.net/49029063/messages

-- 
Lucid fresh install doesn't go beyond login. Possible Savage driver problem.
https://bugs.launchpad.net/bugs/584674
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-savage in ubuntu.