On 7/8/19 3:59 PM, Nicolas Chauvet wrote:
Le lun. 8 juil. 2019 à 21:29, Ty Young <youngty1997@xxxxxxxxx> a écrit :
Bug filed: https://bugzilla.rpmfusion.org/show_bug.cgi?id=5307
The driver itself seems perfectly fine in that the system boots and OpenGL works perfectly fine. Games are playable.
How do I output strace to a file directly? It spits out way too much info.
The bug is reproducible by doing a fresh install on a new downloaded ISO but really the likelihood that this is a bug caused by Nvidia is slim to none. Arch Linux(what I primarily use) has the same driver version and everything works perfectly fine.
Regardless of whether or not this specific bug was by a packaging issue or Nvidia, the way Fedora packages the Nvidia drivers is bad:
-nvidia-smi isn't specific to CUDA and is a core Nvidia library interface that should come with the base driver as it does in Windows.
That's moot, but the comparison with nvidia on Windows is not
relevant. if you want nvidia-smi, please install
xorg-x11-drv-nvidia-cuda
Previously nvidia-smi relied on any cuda lib, so it was moved on the
cuda side, but we can re-evaluate this, I take take a RFE.
Arch simply includes it with the driver utils(see
https://www.archlinux.org/packages/extra/x86_64/nvidia-utils/files/).
The most equivalent package in Fedora would be the Nvidia-utils package
in Fedora(see
https://fedora.pkgs.org/30/rpmfusion-nonfree-x86_64/xorg-x11-drv-nvidia-libs-418.56-1.fc30.x86_64.rpm.html)
The main thing is that noone will ever know that nvidia-smi is apart of
the CUDA package without digging through the provides listings.
With that said, the appropriate doc is here:
https://rpmfusion.org/Howto/NVIDIA
It is only mentioned to install akmod-nvidia and xorg-x11-drv-nvidia
that's the interface we rely on. (Everything else should be
auto-detected on purpose).
Also to wait a few for the module to build and install and reboot
(it's explicitly required).
That gets you a working driver but not OpenGL or any of the core Nvidia
driver utils/libs such as nvidia-smi, nvidia-settings, nvidia-xconfig,
etc. If you try to install Steam for example it will blow up real bad.
-nvidia-settings is the Linux alternative to Window's control panel and if not included by default, *should* be included via a "meta" package for desktop users.
It's a separate package, but it is required by the drivers as it's
mandatory indeed. So I don't understand the metapackage thing, it's a
solution for others distros, the Fedora ways is different. (virtual
provides , booleans dependencies, etc).
If memory serves me correctly nvidia-settings *is* silently installed
but not explicitly. In other words, you can see and launch the
application in Gnome 3 without explicitly installing it but doing:
rpm-ostree install nvidia-settings
Will still work and "install" the package despite it already been
installed. I'll have to do another reinstall and install just the driver
to make sure. Could be smoking shrooms here but I remember it being there...
I'd like to pose the question though, is this really a good thing?
People don't like it when you silently install things behind their back.
A meta package(at least in the form I'm thinking of) is different as it
points to other packages and says to install those packages. If you want
more information on what those packages contain you should be able to
lookup what each package provides.
-OpenGL not packaged with the driver(or again, install-able via a meta package)? Who wants a graphics driver without OpenGL/Vulkan support?
Well, some people want to have selectables sub-packages as
appropriate, and the split made by RPM Fusion is carefully minded. But
we still welcome improvements.
...which is fine. A meta package(one that points to many sub packages)
would allow this.
-it isn't clear if the command I posted(above) installs the 32-bit libraries or not. Really, meta packages would go a long way in simplifying GPU driver installs!
In regular Fedora, it will install the 32bit libraries on purpose with
the nvidia driver if you have at least a package that requires 32bit
libGL. (same for cuda-libs).
That doesn't work for 32-bit games though since they don't use the
package manager and Steam does need 32-bit libs if not installed via
Flatpak. Yes, Steam provides many 32-bit libs but as they have said
during the whole Ubuntu 32-bit support mess, they still use system libs.
Which libs? I don't know, they'd probably have a good idea.
It isn't possible to play Proton games using Fedora Steam but is
possible with Flatpak Steam for example which I can only assume is
because of missing 32-bit libs. Installing Wine would probably pull in
the requires 32-bit libs since Proton is Wine...
Neither Windows nor even other Linux distros fragment the driver this much. You'd have to add 32-bit libraries alongside the 64 bit driver and 64 bit libraries to equal Fedora's fragmented driver packaging in some distros. Why?
Well, It could be worst. You could have sub-packages depending on the
need to run headless or without Xorg or without wayland dependencies
etc.
That's constraints you might not have, but a good packaging should
works everywhere.
I've never heard of a situation where you would *just* want the driver
and *not* (at the very least) OpenGL support. Are there any examples?
Can CUDA be used without OpenGL?
With that said the rpm-ostree line you have used is silly with respect
to the need to llst all sub-packages. Can you point me to the
documentation you have used ?
https://fedora.pkgs.org/30/rpmfusion-nonfree-x86_64/
rpm-ostree install akmod-nvidia xorg-x11-drv-nvidia = core working driver
rpm-ostree install xorg-x11-drv-nvidia-libs = OpenGL/Vulkan
rpm-ostree install nvidia-settings = explicitly installed nvidia-settings
rpm-ostree install nvidia-xconfig = x config utility for Nvidia
rpm-ostree install xorg-x11-drv-nvidia-cuda xorg-x11-drv-nvidia-cuda-libs = nvidia-smi
Thx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
