Language Selection

English French German Italian Portuguese Spanish

openSUSE 11.4 News

Filed under
SUSE




Nvidia drivers and OpenSUSE

Why does openSUSE make it so difficult to install and use NVidia's video drivers?

While I can understand and appreciate the philosophy of using entirely open source drivers for all of Linux, NVidia's drivers still eat the open source Nouveau video drivers for lunch. I do hope the Nouveau drivers gain performance and stability parity with NVidia's, and, yes, the Nouveau drivers are making very good progress. But until they do achieve parity, I WANT AN EASY TO INSTALL AND CONFIGURE CHOICE in a distribution. Five of my 6 computers at home have NVidia video chipsets.

From what I can see, right now, installing and configuring NVidia's video drivers on the just released openSUSE 11.4 is major surgery. So, all this publicity hoopla regarding the 11.4 release is just falling on deaf ears, in my case.

re: opensuse & nvidia

Well, I guess it depends on perspective, but I thought it was a non-issue. Unlike in Debian, the kernel sources were easy to find and install thru software manager (but may have not been needed cause headers were already installed). Logged out and ran the installer. Rebooted to disable Nouveau, and ran installer again. The installer writes the Nouveau disable file. It also writes a basic xorg.conf file that'd probably work for most folks.

Ok, I cheated a bit, but copied my xorg.conf for dual monitors from Sabayon (that was copied from another install, that was copied from... well, see). But I originally got that xorg.conf from running nvidia-settings and editing a bit. Not the headache it was years ago when I had to do all by hand and trying to startx to test.

Now some distros do provide the drivers automagically, through their software manager, or "hardware drivers" utility. Of course that's much easier, but many don't.

What was unusual about openSUSE for you?

re: re: opensuse & nvidia

Let's see...

1. Download NVidia driver
2. Install kernel sources
3. Log out (and get back to init level 3?) and run the Nvidia install
4. A reboot disables the Nouveau stuff.
5. Then you install Nvidia again.
6. Copy a working xorg.conf file from another machine.
7. Reboot, and you have a working Nvidia install??

Well, this is a simpler procedure than I read about at some other sites for getting the NVidia drivers working with openSUSE, and while it may be better than it was a few years ago, I still think it's not acceptable. A Distro this comprehensive should have this all scripted with a few mouse clicks.

If PCLOS & Texstar or Sabayon with their small development staff can do it, then surely openSUSE could.

And, yes, I too remember pounding away the hours in the old days to get video drivers working. I'm 61 now, and life is getting shorter.

I don't have a lot of experience with openSUSE, so I don't know if I have other issues with it.

The major criticism I've read over the last year or two is that it is sluggish. But, I guess they fixed that one--reports indicate that the 11.4 release is very responsive, and the reviews are largely very favorable.

The depth of the openSUSE repositories is certainly appealing.

Go Lizard!

I'm glad to see OpenSUSE getting some press after their release. Every time I see an article about Wayland I throw up a little in my mouth.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Trisquel 9.0 Development Plans and Trisquel 8.0 Release

  • Trisquel 9.0 development plans
    Just as we release Trisquel 8.0, the development of the next version begins! Following the naming suggestions thread I've picked Etiona, which sounds good and has the fewest search results. We currently do our development in a rented dedicated server in France, and although it is functional it has many performance and setup issues. It has 32 gigs of RAM, which may sound like plenty but stays below the sweet spot where you can create big enough ramdisks to compile large packages without having to ever write to disk during the build process, greatly improving performance. It also has only 8 cores and rather slow disks. The good news is that the FSF has generously decided to host a much larger dedicated build server for us, which will allow us to scale up operations. The new machine will have fast replicated disks, lots of RAM and two 12 core CPUs. Along with renewing the hardware, we need to revamp the software build infrastructure. Currently the development server runs a GitLab instance, Jenkins and pbuilder-based build jails. This combination was a big improvement from the custom made scripts of early releases, but it has some downsides that have been removed by sbuild. Sbuild is lighter and faster and has better crash recovery and reporting.
  • Trisquel 8.0 LTS Flidas
    Trisquel 8.0, codename "Flidas" is finally here! This release will be supported with security updates until April 2021. The first thing to acknowledge is that this arrival has been severely delayed, to the point where the next upstream release (Ubuntu 18.04 LTS) will soon be published. The good news is that the development of Trisquel 9.0 will start right away, and it should come out closer to the usual release schedule of "6 months after upstream release". But this is not to say that we shouldn't be excited about Trisquel 8.0, quite the contrary! It comes with many improvements over Trisquel 7.0, and its core components (kernel, graphics drivers, web browser and e-mail client) are fully up to date and will receive continuous upgrades during Flidas' lifetime. Trisquel 8.0 has benefited from extensive testing, as many people have been using the development versions as their main operating system for some time. On top of that, the Free Software Foundation has been using it to run the Libreplanet conference since last year, and it has been powering all of its new server infrastructure as well!

today's howtos

FOSS Events in Europe: Rust, foss-north, KubeCon + CloudnativeCon Europe 2018

  • Rust loves GNOME Hackfest: Day 1
    This is a report of the first day of the Rust loves GNOME Hackfest that we are having in Madrid at the moment. During the first day we had a round of introductions and starting outlining the state of the art.
  • Madrid GNOME+Rust Hackfest, part 1
    I'm in Madrid since Monday, at the third GNOME+Rust hackfest! The OpenShine folks are kindly letting us use their offices, on the seventh floor of a building by the Cuatro Caminos roundabout. I am very, very thankful that this time everyone seems to be working on developing gnome-class. It's a difficult project for me, and more brainpower is definitely welcome — all the indirection, type conversion, GObject obscurity, and procedural macro shenanigans definitely take a toll on oneself.
  • Five days left
    I use to joke that the last week before foss-north is the worst – everything is done, all that is left is the stress.
  • KubeCon + CloudnativeCon Europe 2018
    The Cloud Native Computing Foundation’s flagship conference will be taking place in Copenhagen from May 2-4. It will cover Kubernetes, Prometheus OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, and other key technologies in cloud native computing.

Programming: Taxonomy of Tech Debt, Python and More

  • A Taxonomy of Tech Debt
    Hi there. I’m Bill “LtRandolph” Clark, and I’m the engineering manager for the Champions team on LoL. I’ve worked on several different teams on League over the past years, but one focus has been consistent: I’m obsessed with tech debt. I want to find it, I want to understand it, and where possible, I want to fix it. When engineers talk about any existing piece of technology - for example League of Legends patch 8.4 - we often talk about tech debt. I define tech debt as code or data that future developers will pay a cost for. Countless blog posts, articles, and definitions have been written about this scourge of software development. This post will focus on types of tech debt I’ve seen during my time working at Riot, and a model for discussing it that we’re starting to use internally. If you only take away one lesson from this article, I hope you remember the “contagion” metric discussed below.
  • 6 Python datetime libraries
    Once upon a time, one of us (Lacey) had spent more than an hour staring at the table in the Python docs that describes date and time formatting strings. I was having a hard time understanding one specific piece of the puzzle as I was trying to write the code to translate a datetime string from an API into a Python datetime object, so I asked for help.
  • Getting started with Anaconda Python for data science
  • How to install the Moodle learning management system
  • Anatomy of a JavaScript Error
  • Is DevOps compatible with part-time community teams?