openSUSE and Drivers — Two Pace Lanes, One Approach
A short overview to drivers in Tumbleweed and Leap, with notes on the YaST control centre and the SUSE-specific repositories.
A short overview to drivers in Tumbleweed and Leap, with notes on the YaST control centre and the SUSE-specific repositories.
Tumbleweed is rolling — the kernel and drivers move forward continuously and you get the latest in-tree drivers as the kernel team merges them. Leap is point-release based and tracks SUSE Linux Enterprise, so its kernel and drivers stay stable for the lifetime of each release.
For driver coverage, Tumbleweed is best for very new hardware and Leap is best for systems where you value steady behaviour over the latest features.
YaST is openSUSE's control centre. It exposes the package manager, repository management, and a hardware overview. For drivers, the most useful piece is the repository panel — it lets you add the openSUSE community repositories with a click.
Once those repositories are added, installing the proprietary graphics driver, multimedia codecs, or unusual firmware is a single search-and-install in YaST.
Both Tumbleweed and Leap support Dkms for out-of-tree modules. The pattern is the same as on other Linux distributions — install the package, reboot, and the module rebuilds against new kernels automatically.
For specialty hardware, the openSUSE Build Service often hosts community packages that wrap a vendor module in a proper Rpm — a tidier alternative to manual Dkms in many cases.
Hand-picked articles that pair well with this one.
Plain-English explainers, fix walkthroughs, and concept articles for every part of your system.