[KM400]KDE not working after Karmic upgrade

>
> I'm happy to stick around and get this solved completely. But in the
> interim, could somebody suggest a way to get my display back with VESA?
> I don't mind 640x480 resolution etc. while I try to find a solution.
>

Could you please try with the version of the driver available from my
ppa? it is the latest upstream release and fixes many bugs. Thanks.
https://launchpad.net/~atomo64/+archive/ppa/

Raphael, I added your PPA and upgraded to your build of openchrome. No luck :( I still can't get past the login screen and the loading window. Xorg.0.log attached. If you'd like any other logs, please let me know.

From what I could see, dmesg looked the same as earlier.

Thank you.

The problem appears between openchrome svn713 (Ubuntu Jaunty) and svn758 (Ubuntu Karmic Koala).
Please check in which revision this problem appeared.

You can jump between releases, by typing command:

  svn update -r730

More information is available at:
http://www.openchrome.org/trac/ticket/333

It will be very useful in resolve this problem.

I don't know if this helps. But, I downgraded to r713 using https://launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/1:0.2.903+svn713-1ubuntu1/+build/866816/+files/xserver-xorg-video-openchrome_0.2.903+svn713-1ubuntu1_i386.deb

I rebooted for good measure and encountered the same issue :(

In your Xorg.0.log file there is an errors:

(EE) AIGLX error: dlopen of /usr/lib/dri/(null)_dri.so failed (/usr/lib/dri/(null)_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering

Bartosz: The Xorg.0.log file when I was using svn713? That error seems to be present in all log files.

That said, if this driver was working in Jaunty for me, shouldn't reverting to 713 fix the issue? Is the error elsewhere, perhaps?

Many thanks for looking into this.

Bartosz,

Xenophon has a completely different problem from mine. Please
disassociate bug 446316 from his.

regards,

Christopher

Xenophon wrote:
> Bartosz: The Xorg.0.log file when I was using svn713? That error seems
> to be present in all log files.
>
> That said, if this driver was working in Jaunty for me, shouldn't
> reverting to 713 fix the issue? Is the error elsewhere, perhaps?
>
> Many thanks for looking into this.
>

2009/11/1 Xenophon <email address hidden>:
> Raphael, I added your PPA and upgraded to your build of openchrome. No
> luck :( I still can't get past the login screen and the loading window.
> Xorg.0.log attached. If you'd like any other logs, please let me know.

Yes, please attach the Xorg.0.log.old file (try to log in, wait until
you get back to the login screen and then attach that file). It is not
normal that the screen is reinitialised, though.

Xorg.0.log for Raphael. There's a 12KB size difference with the one I attached earlier.

Xorg.0.log.old for Raphael.

I believe that the 12KB difference in #13 is because I booted the system without the monitor switched on.

Try to enable XAA acceleration and check again.

Check if this error still exists on the previous kernel (Linux 2.6.28-16-generic) from Ubuntu 9.04 Jaunty.

the problem is kind of solved for me by using lxde and GDM

no, better yet

by using kde/openbox

Try to disable DRI.

I created the patch which disable DRI (it use swrast instead)

Check if it works for you.
The detail build instruction for Ubuntu/Debian is available at:
https://help.ubuntu.com/community/OpenChrome

Attach your /var/log/Xorg.0.log file.

I disabled DRI and now I can login kde

sorry, the server got slow so I double posted

the resolution goes wrong again when going to krandr

when I said 'krandr' I meant "kcmshell4 display"

Bartosz,

  I'd previously tried the Jaunty kernel to no effect. However, I noticed that there were a bunch of updates for Xorg via apt which I've upgraded to and then tried again. There was also a new minor kernel release which I've also installed.

  NormalUser is my usual account. TempUser is an account I created for testing in case this was happening due to a bum KDE config.

  So, here is what I found:

1. The two Karmic kernels do not allow me to log in and in out of 3 attempts hangs the machine. [both users]
2. Neither kernel allows console logins (via drop-down option) from the login window. [both users]
3. I can get to the recovery root shell. startx loads X and then hangs the system.
4. The Jaunty kernel also does not allow me to log in. [both users]
5. However, I could reach the console via the console login option.
6. startx using NormalUser failed.
7. startx using TempUser succeeded. I used the output from Xorg.0.log to create a xorg.conf file in /etc/X11/. (see attached)
8. startx using NormalUser now succeeded. KDE apps are a little unstable though.
9. Toggling back to the console window shows that DRI was automatically disabled. (see attached)

I noticed on your linked wiki page that there's a binary driver from VIA for 9.04. Will this work with 9.10? Are there plans to add this to the restricted drivers list?

Will you be releasing a .deb with DRI disabled?

Thanks.

BTW this is my xorg.conf in karmic

BTW this is my xorg.conf in karmic

Thanks Karl. I can now log into karmic as well by adding the Module section as per your xorg.conf to my existing xorg.conf. I can however still not log in directly. I need to select "console login" and login via the console using startx. Attempting to log out using KDE also results in the system hanging.

I tried using your xorg.conf as it was. But my display resolutions were wonky. The one I'm using right now works better and in many ways seems a lot sharper than even my Jaunty display for some reason. I don't know if this is due to an improvement in the driver or something to do with the fonts being used.

Cheers!

Try to enable New mode switch by adding "Option ModeSwitchMethod new" to your xorg.conf file (with disabled DRI).
Is it working correctly for your chipset?

Attach your /var/log/Xorg.0.log file.