Kasperian Moving Parts

kinda like Batman, but with a wife and 3 kids

OpenSUSE 11.1 and nVidia == AWESOME!!

| 10 Comments

Stark contrast to my last post, I know, but I felt it was only fair to blog about the wonders of OpenSUSE 11.1, even/especially with my little nVidia chip. First off, I still think there’s something wonky going on with X and/or nVidia’s driver in taking so long to start that kdm ends up giving up and committing hari kari, but my little workaround in extending ServerAttempts and ServerTimeout in kdmrc seems to be at least good enough to keep me from committing hari kari myself. And quite honestly, that’s about as much time as I want to spend on debugging it. =:/

But I updated to the KDE 4.2 beta2 packages again today and am absolutely loving OpenSUSE 11.1. Things are blazingly fast and well-put-together, and best of all, my faith is totally restored in OpenSUSE after I reinstalled from scratch again. So what changed between my last post and now? A few things:

Yesterday when I installed the KDE 4.2 beta2 packages, I also pulled in the unstable Qt45 packages as well. Maybe that caused some harm? *shrug* All I know is today, I didn’t do that and I’m not seeing any problems.

I think I was using my old xorg.conf file (that worked perfectly well in OpenSUSE 11.0, mind you) yesterday, which still had a bunch of tweaks that I added over the last year to get nVidia to play nicely with KDE4. Today, I am just using the default xorg.conf, as written by sax2, and things are REALLY fast and stable. And based on a few comments I’ve seen (hi jospoortvliet!), it’s very likely that this is the true cause of my problems from yesterday. Here’s what my old Screen stanza looked like. Does anyone know exactly which one of these might be causing nVidia to hurl its little guts out in OpenSUSE 11.1 with xorg 7.4?

Section “Screen”
Identifier     “Screen0”
Device         “Device0”
Monitor        “Monitor0”
DefaultDepth    24
Option         “RenderAccel” “True”
Option         “UseEdidFreqs” “False”
Option         “TwinView” “1”
Option         “TwinViewXineramaInfoOrder” “DFP, CRT”
Option         “AddARGBGLXVisuals” “True”
Option         “DisableGLXRootClipping” “True”
Option         “DamageEvents” “True”
Option         “TripleBuffer” “True”
Option         “UseEvents” “True”
Option         “FlatPanelProperties” “DFP: Scaling = Centered; CRT: Scaling = Centered, Dithering = Enabled”
Option         “OnDemandVBlankInterrupts” “True”
Option         “PixmapCacheSize” “2000000”
Option         “AllowSHMPixmaps” “False”
Option         “BackingStore” “True”
Option         “metamodes” “CRT: 1680×1050 +0+0, DFP: 1680×1050 +0+0”
SubSection     “Display”
Depth       24
EndSubSection
EndSection

So, in addition to things being extremely awesome in general in OpenSUSE 11.1, I am totally thrilled to finally be able to use powerdevil (it is REALLY nice!!!), and really happy to finally have working hotplug/usb-drive mounting working in KDE 4.2!!!! (it failed hard in OpenSUSE 11.0 due to some hal permissions problems that I never figured out), and zypper (package management) seems to be even faster in OpenSUSE 11.1. And these are just a few of the things that I’ve noticed in the last couple of hours of X not crashing. =;)

And, of course, KDE 4.2 is continuing to to shape up and look, feel, and perform absolutely marvelously, and OpenSUSE 11.1’s beta2 packages are a great way of testing it out.

As for me, I’m just thankful to have a functional laptop again and I hope to get some good KPilot testing and bug squashing done during the next few days of Christmas vacation.

Merry <almost> Christmas, all, and to the OpenSUSE 11.1 guys, a huge thanks again for the awesome new distro. You guys just plain rock! =:)

Author: Jason 'vanRijn' Kasper

My name is Jason 'vanRijn' Kasper. I am the ring leader of the amazing Kasper family. I am unashamedly a Christian Nerd. These are our stories....

10 Comments

  1. Just installed Slackware and everything is working out of the box, because there is no unstable things included. Or I boot OS-X, can work after right after booting and don’t need to hope if I have a working laptop when it’s christmas.
    Spend some time with your family and not with beta…

  2. Would you mind posting that lovely xorg.conf generated by sax2? 🙂

  3. Hi,

    after my update I ran into two things: On my laptop with intel grafix I had to disable backingstore. It worked until I opened a konsole window. Xterm was fine but konsole always killed X. On my nvidia (180.16) desktop pc i had the same problem but I do not exactly know if it was the backingstore setting.
    The second thing I had on my desktop pc was that some font had to be moved into x11-fonts from x11-fonts-core. All gtk apps crashed until I installed xorg-x11-fonts (additionally to xorg-x11-fonts-core)

  4. I believe the culprit is: “AllowSHMPixmaps” “False”

    I’d comment that one out.

  5. Awesome with latest drivers only.
    Did you ask about the performance of “legacy” drivers as well?

  6. After reading your post, I moved my xorg.conf out of the way and let SaX2 recreate it for me. Then I added back in some options, and now I’m amazed at how well my laptop is handling KDE 4.1’s desktop effects. In OpenSuse 11.0 I tried them a few times (with the 4.1 packages), and always ended up turning them off because they were too slow to use. But now they actually work fast – it’s like having a new laptop! (My laptop is nearly six years old, so I really wasn’t expecting my old GeForce2Go to be able to work like this!)

  7. I had
    AddARGBGLXVisuals
    and
    BackingStore
    in xorg.conf and had lots of crashes in 11.1.
    I removed them both and everything is sweet now.

    I guess backingstore was the problem since Michael had the same problem with backingstore…

  8. Pingback: Boycott Novell » Do-No-Evil Saturday - Part I: OpenSUSE 11.1 Reviews Trickle In

  9. I am having all sorts of problems with Nvidia on OpeSuSE 11.1. I use four monitors and this works well in 11.0 but fails miserably in 11.1. I used absolute positions in 11.0 and the best I can do in 11.1 is two monitors in TwinView and the third and fourth screens are broken in many different ways the worst being core dumps during start up.

    Does anyone have any suggestions?

  10. I had all sorts of problems as well. I solved mine by adding the following parameters to the boot command line:

    pci=routeirq (needed in my case because of a conflict with a TV Card and the Graphics Card)

    vmalloc=192M

Leave a Reply

Required fields are marked *.