SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Seems the open source drivers are still lagging behind.
Except (1) during the week after xorg-server-1.18 is released, until the nVidia blobs are updated, and (2) during the years after nVidia withdraws support for your GPU, and (3) on those nVidia GPUs where nVidia's blob is randomly broken (e.g. the embedded MCP78S on which I am typing this). But otherwise, yes, the open source drivers are still lagging behind. Of course they are. And what is the root cause of that? Do I have to spell it out? When people denigrate nouveau, I hear victim-blaming.
Besides, nouveau driver doesn't support GPU computing, so it's pretty much useless for anyone intending to use its Slackware machine for some sort of scientific calculations or, more importantly, development of alike codes.
I'm a 3D animator and the software I use for a living requires proprietary drivers with OpenCL/OpenGL so I simply can't run nouveau. I find -current to be very stable so I don't see a reason not to use it in production. Here's a bit of trivia for you: Security updates on Mac OS X often break the nVidia drivers on OS X as well, since they are tied to a specific kernel version/build.
I dips me lid to all who contributed to this thread.
Having been warned of the breakage by @Lenard Spencer, which I agree with @volkerdi that should not be a brake on development, I followed the advice of @55020 and waited for the release of an updated nVidia driver as signalled by @mats_b_tegner on my desktop with an nVidia GPU. This box is now running with the latest updates to -current and the nVidia proprietary driver(304.131).
From @ReaperX7
Quote:
And yet you guys complain about a proprietary driver that isn't properly supported by the current software packages...
My only complaint with the nVidia proprietary driver is the need to manually create symlinks so that MPlayer will run.
Hmm, Mplayer works for me. Did you use the .run-file directly or did you use Ed Koenig's SlackBuild-scripts? (Which will fix the symlinks for you). Also make sure you have the libvdpau package installed.
I'm reading Phoronix on daily basis. I know that some folks aren't big fans of that site, but I have no problems with it. And thanks to this article, I new perfectly that NVIDIA driver will break with this -current update, by just seeing what is the xorg version in the ChangeLog.
[ 10.209986] noueau [ DEVICE][0000:02:00.0] BOOT0 : 0x092a00a2
[ 10.209992] nouveau [ DEVICE][0000:02:00.0] Chipset: G92 (NV92)
[ 10.209994] nouveau [ DEVICE][0000:02:00.0] Family : NV50
[ 10.324697] nouveau [ VBIOS][0000:02:00.0] using image from PRAMIN
[ 10.324825] nouveau [ VBIOS][0000:02:00.0] BIT signature found
[ 10.324828] nouveau [ VBIOS][0000:02:00.0] version 62.92.84.00.00
[ 10.345402] nouveau E[ VBIOS][0000:02:00.0] 0xdf7e[ ]: unknown opcode 0x9f
[ 10.345441] nouveau E[ DEVINIT][0000:02:00.0] init failed, -22
[ 10.345475] nouveau E[ DRM] failed to create 0x00000080, -22
[ 10.346347] nouveau: probe of 0000:02:00.0 failed with error -22
Linux kernel 4.1.12, GeForce 9800 GT. All I get then is the VESA driver when starting X. Would be nice if nouveau was working, but unfortunately it does not even initialise on my card.
Funny, I have a 9800GT and it works.
Readout of glxinfo
Code:
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV92
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.5
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
Readout of Xorg.0.log
Code:
[ 33.012] (II) LoadModule: "nouveau"
[ 33.012] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[ 33.040] (II) Module nouveau: vendor="X.Org Foundation"
[ 33.041] (II) [drm] nouveau interface version: 1.2.2
[ 33.746] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 33.746] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 38.902] (II) AIGLX: Loaded and initialized nouveau
I tried to include the nouveau module in my initrd, added `nouveau.config=NvBios=PRAMIN' to my kernel command-line (as per http://nouveau.freedesktop.org/wiki/...ing/#index10h3), and even compiled nouveau into the kernel. It all results in the same error. Specifying nouveau in a xorg conf file results in:
Code:
[ 221.817] (EE) [drm] KMS not enabled
[ 221.817] (EE) No devices detected.
[ 221.817] (EE)
Fatal server error:
[ 221.817] (EE) no screens found(EE)
[ 221.817] (EE)
There was a time when nouveau loaded, but this was 2 years ago or so, since then I haven't really tried anyway: I have the habit of starting Live CDs with the `nomodeset' parameter because when nouveau still worked, it meant having an unusable system with borked graphics. My onboard graphics (GeForce 7025) does work with nouveau, though.
I appreciate your help, ReaperX7. But I guess at this point the only way to get this fixed is by reporting it as a bug.
Well, I would start at this:
1. Use the Huge kernel rather than Generic. Huge includes all the necessary drivers internally with only select hardware drivers as modules that are easily handled by udev. This can help greatly as hardware can vary revision to revision requiring extra support that may or may not get loaded correctly. The memory footprint argument on modern systems is moot.
2. Remove all kernel parameters. No nomodeset, nothing. Run it bare with only the options passed by the bootloader.
3. Setup an xorg.conf file and make sure you only have a single screen defined. I have seen instanced where multiple screens defined in xorg.conf can throw a monkey wrench in the works very quickly. Make sure also nouveau is the only defined driver. If it does offer fallbacks, modesetting and fbdev should be the only drivers used for Nvidia cards.
Of course I can't guarantee it'll work for you, but it works for me.
1. Use the Huge kernel rather than Generic. Huge includes all the necessary drivers internally with only select hardware drivers as modules that are easily handled by udev. This can help greatly as hardware can vary revision to revision requiring extra support that may or may not get loaded correctly. The memory footprint argument on modern systems is moot.
Are you sure? A quick diff shows that huge simply has file system stuff built into it, nouveau is still `m'. Maybe I'm overlooking something? I simply diffed both default configs.
Quote:
Originally Posted by ReaperX7
2. Remove all kernel parameters. No nomodeset, nothing. Run it bare with only the options passed by the bootloader.
I need to specify at least root=UUID=XXX since I have two disks, and sda is my backup drive. I also don't think adding quiet hurts much, but who knows.
Quote:
Originally Posted by ReaperX7
3. Setup an xorg.conf file and make sure you only have a single screen defined. I have seen instanced where multiple screens defined in xorg.conf can throw a monkey wrench in the works very quickly. Make sure also nouveau is the only defined driver. If it does offer fallbacks, modesetting and fbdev should be the only drivers used for Nvidia cards.
According to the nouveau FAQ, one should not need a config file; in case nouveau does not get loaded automatically, one should create a config in /etc/X11/xorg.conf.d (e.g. 20-nouveau.conf) instead with the following content:
Code:
Section "Device"
Identifier "n"
Driver "nouveau"
EndSection
Anyway, I'll try your suggestions and report back in case of success.
Are you sure? A quick diff shows that huge simply has file system stuff built into it, nouveau is still `m'. Maybe I'm overlooking something? I simply diffed both default configs.
I need to specify at least root=UUID=XXX since I have two disks, and sda is my backup drive. I also don't think adding quiet hurts much, but who knows.
According to the nouveau FAQ, one should not need a config file; in case nouveau does not get loaded automatically, one should create a config in /etc/X11/xorg.conf.d (e.g. 20-nouveau.conf) instead with the following content:
Code:
Section "Device"
Identifier "n"
Driver "nouveau"
EndSection
Anyway, I'll try your suggestions and report back in case of success.
edit: huge did not work either.
Typically, you can get away with a trimmed xorg.conf.d file, but this is diagnosis, so a full file is better at this point.
Nouveau is built as "m" but it's other kernel drivers that may be needed that might not be getting loaded from the initrd/initramfs.
Disk options should be done by your bootloader (LILO, Grub, etc.) so those are safe, everything is sacrificial.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
