Edit Package nvidia-gfxG04

nvidia-gfxG04

No description set
Refresh
Refresh
Source Files
Filename Size Changed
README 0000000562 562 Bytes over 6 years
Xwrapper 0000001173 1.15 KB about 6 years
_constraints 0000000109 109 Bytes almost 2 years
_service 0000000601 601 Bytes about 2 months
alternate-install-present 0000000258 258 Bytes over 7 years
check-build.sh 0000000166 166 Bytes over 14 years
generate-service-file.sh 0000001642 1.6 KB about 4 years
kernel-5.18-ix86.patch 0000003386 3.31 KB 20 days
kernel-5.18.patch 0000004870 4.76 KB 20 days
kmp-filelist 0000001082 1.06 KB 9 months
kmp-post.sh 0000005183 5.06 KB 24 days
kmp-postun.sh 0000000393 393 Bytes over 2 years
kmp-pre.sh 0000000085 85 Bytes almost 5 years
kmp-preun.sh 0000000582 582 Bytes 24 days
kmp-trigger.sh 0000003641 3.56 KB 24 days
kmp-triggerpostun.sh 0000000320 320 Bytes over 1 year
modprobe.nvidia 0000000086 86 Bytes over 5 years
modprobe.nvidia.install 0000001452 1.42 KB almost 2 years
modprobe.nvidia.install.non_uvm 0000000906 906 Bytes over 4 years
my-find-supplements 0000001205 1.18 KB 10 months
nvidia-gfxG04.changes 0000093021 90.8 KB 20 days
nvidia-gfxG04.rpmlintrc 0000000804 804 Bytes 10 months
nvidia-gfxG04.spec 0000013227 12.9 KB 20 days
nvidia-settings.desktop 0000000152 152 Bytes over 15 years
pci_ids-390.151 0000007684 7.5 KB about 2 months
pci_ids-390.151.legacy 0000002492 2.43 KB about 2 months
pci_ids-390.151.new 0000002910 2.84 KB about 2 months
preamble 0000000847 847 Bytes 25 days
x11-video-nvidiaG04.changes 0000091562 89.4 KB 20 days
x11-video-nvidiaG04.spec 0000026206 25.6 KB 24 days
Comments 93

Anonymous User's avatar

_nobody_ wrote over 4 years ago

This comment has been deleted


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

Sure. On my TODO list.


Mariusz Fik's avatar

Fisiu wrote over 4 years ago

Building nvidia-gfxG04.spec fails with:

[  196s] RPM build errors:
[  196s]     Invalid version (double separator '-'): 4.14.15-1-default

Chema Ollés's avatar

pepetops wrote over 4 years ago

Hi... Same error here


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

Against which repository are you building the package?


Mariusz Fik's avatar

Fisiu wrote over 4 years ago

Tumbleweed. I suspect recent rpm update.


Chema Ollés's avatar

pepetops wrote over 4 years ago

Tumbebleed with last update, 20180128


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

I believe this is also related to bsc#1076393. Let's see.


Chema Ollés's avatar

pepetops wrote over 4 years ago

Thanks for the information


Chema Ollés's avatar

pepetops wrote over 4 years ago

Hi... I check last osc build -k . openSUSE_Tumbleweed x86_64 nvidia-gfxG04.spec and see that the compilation of the drivers is done over the kernel 4.15.5-1.3 when the last TW kernel to date is the kernel-default-4.15.6-1.4... Is this normal? Other times that I have done it, basically to rule out that there is an error when doing zypper dup and change the kernel, the kernel was always the same one that I was going to install with zypper dup... As I see you have changed the not doing weak-updates, can this be the cause? Thank you


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

It could be possible if you haven't installed the kernel devel package for this new kernel I would say.


Chema Ollés's avatar

pepetops wrote over 4 years ago

when I run osc build I don't need to install anything, all are installed automatically


Chema Ollés's avatar

pepetops wrote over 4 years ago

I delete /var/tmp/osbuild-packagecache to force download the last kernel but osc continues downloading kernel-default-devel-4.15.5-1.3.x86_64.rpm and kernel-devel-4.15.5-1.3.noarch.rpm


Chema Ollés's avatar

pepetops wrote over 4 years ago

With the last osc up and yours changes, today kernels updates to 4.15.6-1.5


Chema Ollés's avatar

pepetops wrote over 4 years ago

Hi again... I'm sorry but I do not understand what happened. I have updated TW to the last kernel:kernel-default-4.15.6-1 and the /lib/modules/kernel-4.15.6-1-default directory has been re-created weak-updates ... I understood that you had changed and that it was not going to create more for now ...


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

Well, kernel packages also run weak-updates. Hope the directory is empty.


Chema Ollés's avatar

pepetops wrote over 4 years ago

weak-updates/ dir has updates/ dir with 4 symlink to @nvidia-drm.ko @nvidia-modeset.ko @nvidia-uvm.ko and @nvidia.ko Regards


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

Where are these symlinks going to? Are the modules working?


Chema Ollés's avatar

pepetops wrote over 4 years ago

goes to /lib/modules/4.15.2-1-default/updates/ and yes, the nvidia modules works, if not, we would not be talking now about symbolic links but because the compilation of them has failed ... Do not you think? Regards


Stefan Dirsch's avatar

sndirsch wrote over 4 years ago

Ok. Maybe the modules in .../4.15.2-1-default/updates/ were still from an older KMP build. But as long as the kABI doesn't change (and weak-updates should detect this and if it breaks no longer create such links) this shouldn't matter then.


Chema Ollés's avatar

pepetops wrote over 4 years ago

OK,thanks you


Chema Ollés's avatar

pepetops wrote about 4 years ago

Seems need install this path for works with kernel 4.16: --- a/kernel/common/inc/nv-linux.h~ 2018-01-25 06:09:41.000000000 +0100 +++ b/kernel/common/inc/nv-linux.h 2018-03-05 13:58:17.746725638 +0100 @@ -1209,6 +1209,7 @@ static inline NvU32 nv_alloc_init_flags( static inline NvBool nv_dma_maps_swiotlb(struct pci_dev dev) { NvBool swiotlb_in_use = NV_FALSE; +#if 0 #if defined(CONFIG_SWIOTLB) #if defined(NV_DMA_OPS_PRESENT) || defined(NV_GET_DMA_OPS_PRESENT) / @@ -1251,7 +1252,7 @@ static inline NvBool nv_dma_maps_swiotlb swiotlb_in_use = (swiotlb == 1); #endif #endif - +#endif return swiotlb_in_use; }

From: https://devtalk.nvidia.com/default/topic/1030082/linux/kernel-4-16-rc1-breaks-latest-drivers-unknown-symbol-swiotlb_map_sg_attrs-/


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

Could you open a bugreport for this,please? Thanks!


Chema Ollés's avatar

pepetops wrote about 4 years ago

Someone did it before


Chema Ollés's avatar

pepetops wrote about 4 years ago

It seems 396.18 Nvidia beta driver's version is compatible with kernel 4.16



Chema Ollés's avatar

pepetops wrote about 4 years ago

Lats osc install show this message: unresolvable: nothing provides kernel-default-devel = 4.16.2-1 needed by kernel-syms I think we must wait for this,isn't it? Regards


Chema Ollés's avatar

pepetops wrote about 4 years ago

I'm sorry, want to say Last and not Lats...


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

Hmm. "osc build openSUSE_Factory x86_64" works for me. Maybe this was a temporary issue.


Chema Ollés's avatar

pepetops wrote about 4 years ago

I think it could be a problem related to this: https://lists.opensuse.org/opensuse-factory/2018-04/msg00670.html


Chema Ollés's avatar

pepetops wrote about 4 years ago

problem solved with the new update


Alexander Ahjolinna's avatar

ahjolinna wrote about 4 years ago

is 396.24 update coming soon? (its compatible with xorg 1.20 and even runs on kernel 4.17+) https://devtalk.nvidia.com/default/topic/1032986/unix-graphics-announcements-and-news/-linux-solaris-and-freebsd-driver-396-24/


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

That's from the a short lived branch, which we do not package.


Alexander Ahjolinna's avatar

ahjolinna wrote about 4 years ago

I would understand that logic for LEAP but not tumbleweed or at least provide both, but then again this isn't the first time you guys have these weird "principles"..but the again who I'm to judge I'm just more of a user/gamer ...sigh.

btw. as the xorg 1.20 update is around the corner and with nvidia releasing monthly driver updates (if any at summer time), are you just going to add some ugly patch and hope it works... well "c'est la vie"


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

Well, we'll see when xorg-server 1.20 will be released, when I'm updating to it in TW and when long lived branch of the NVIDIA driver will support it. I'm not allowed to talk about the NVIDIA driver schedule.


Alexander Ahjolinna's avatar

ahjolinna wrote about 4 years ago

the X.Org Server 1.20 has now been released https://lists.x.org/archives/xorg-announce/2018-May/002893.html are you going to patch the current driver or wait? (I think beta driver is coming next month then month after that the LTS driver, not 100% sure)

btw. the current 390.25 has many performance and rendering issues (that also causes kde/kwin to crash easily), but it can be fixed by adding to your xorg conf file this: Option "UseNvKmsCompositionPipeline" "false"

source: https://devtalk.nvidia.com/default/topic/1029484/linux/-various-all-distros-numerous-performance-amp-rendering-issues-on-390-25/post/5255627/#5255627

can't say if this issue has been fixed in the newer 396.24 driver


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

Interesting, but are you still using 390.25? I mean 390.48 is the latest driver release ...


Alexander Ahjolinna's avatar

ahjolinna wrote about 4 years ago

I meant .48 (which I'm using), the problem has been in whole 390.xx ...apparently


Alexander Ahjolinna's avatar

ahjolinna wrote about 4 years ago

it seems Nvidia already did release 390.59 (LTS) https://devtalk.nvidia.com/default/topic/1035485/b/t/post/5260307/#5260307 its just too bad that its so broken release in general. It would be nice if users could get to choose from this one repo between long-term and short-term releases (maybe even beta drivers), at least for gamers this is more important


Chema Ollés's avatar

pepetops wrote about 4 years ago

Hi.Last kernel update (4.16.8) create lib/modules/4.16.8-1-default/updates dir with all 4 nvidia modules and also /lib/modules/4.16.8-1-default/weak-updates/updates dir with 4 links to lib/modules/4.16.0-1-default/updates (see the number kernel error). I must changed by hand. Regards


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

This should not happen.

Wed Feb 28 13:51:59 UTC 2018 - sndirsch@suse.com - do not run weak-updates on TW, since it creates more harm than benefit (boo#1082704)


Chema Ollés's avatar

pepetops wrote about 4 years ago

I don't run weak-updates at all... zypper dup does it as allways, and that's why I do not understand that just with this new kernel this error has appeared, when it has not done it before Regards


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

So this didn't happen before with previous kernel updates? Maybe I need to remove nvidia modules in weak-updates/ directories for TW in trigger scripts for kernel-default-devel/kernel-pae-devel in nvidia packages in the end ...


Chema Ollés's avatar

pepetops wrote about 4 years ago

New TW update with kernel 4.16.9-1-default make weak-updates dir disappear Thanks


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

Thanks! Nice to hear this!


Christophe Giboudeaux's avatar

cgiboudeaux wrote about 4 years ago

Can you document how you create the pci_ids files ? Trying to build a local package for 396.24 locally, it looks like they removed the x86 archive. I also had to change ftp to https in generate-service-file.sh before running the script. Looks like download.nvidia.com only serves http requests.


Torin Woltjer's avatar

SesameStreetThug wrote about 4 years ago

Whats the status on getting this updated to the 396 driver?


Stefan Dirsch's avatar

sndirsch wrote about 4 years ago

There are no plans to replace the Long Lived Branch version with a Short Lived Branch version.


Torin Woltjer's avatar

SesameStreetThug wrote about 4 years ago

I'm disappointed to hear this, but thank you for the response regardless.


Jehferson Mello's avatar

VileLasagna wrote almost 4 years ago

Any plans for adding an SLB alternative to live concurrently?

I'm looking into this right now as I'm sort of leading migration to OpenSuSE at work (RIP Ubuntu, you won't be missed) and due to CUDA being as finicky as it is (oh boy) we need 396. We've been installing through nVidia's run package, which works, but is fiddly, especially for the peeps who ain't too comfy in Linux yet. (and it prevents me from packaging CUDA itself properly as I can't depend on the correct drivers)

If there isn't, I'm happy to make use of your work on the LLB one and try and get our own package building. Would also be happy to share back my tweaks if I get it working (which I'm hoping will be more or less trivial with this as a starting point)


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

There are currently no plans to create RPMs for SLB in addition to the ones for LLB. And, the next LLB will be released very soon. Unfortunately I'm not allowed to tell you more details about the planned schedule for it.


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

With next LLB I mean one with a higher version number than 396.xx! ;-)


Jehferson Mello's avatar

VileLasagna wrote almost 4 years ago

Thanks for the info, mate. That'd be really good and can't help but think that with 20-series just around the corner there's some new drivers coming. Will see around here if I'm given the opportunity to wait for those as my hand is being forced on my end (already getting some opportunistic "let's just go back to windows" talk over this =( ). Otherwise, still getting to grips with the OBS environment and seeing if I can hack an RPM to keep people happy for the next couple weeks or something =P


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

In case you don't use Leap 15/Tumbleweed and are interested in RPMs for 396.xx you may want to use packages created and provided by NVIDIA themselves. http://developer.download.nvidia.com/compute/cuda/repos/


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

Chech this out. https://build.opensuse.org/package/show/X11:Drivers:Video/nvidia-gfxG05 Version 410.57 is still considered Beta, but an UDA release will be available very soon. And shortly after there will be prebuilt RPMs available via the known repository at NVIDIA.


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

Chech this out. https://build.opensuse.org/package/show/X11:Drivers:Video/nvidia-gfxG05 Version 410.57 is still considered Beta, but an UDA release will be available very soon. And shortly after there will be prebuilt RPMs available via the known repository at NVIDIA.


Alexander Ahjolinna's avatar

ahjolinna wrote almost 4 years ago

Nvidia finally released 390.77 (LTS) which should fix these latest major crashing/rendering issues, for example the kwin one https://devtalk.nvidia.com/default/topic/1037553/unix-graphics-announcements-and-news/linux-solaris-and-freebsd-driver-390-77-long-lived-branch-release-/


Alexander Ahjolinna's avatar

ahjolinna wrote almost 4 years ago

NVIDIA 390.87(LTS) backports important (vulkan/opengl) performance fix https://www.nvidia.com/download/driverResults.aspx/137276/en-us


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

Thanks. On my TODO list now.


Rogério Leiro's avatar

RLFontan wrote almost 4 years ago

Hey, what's up?

Please take a look on this post on openSUSE forum:

https://forums.opensuse.org/showthread.php/533061-Official-pack-for-nVidia-396?p=2880390#post2880390

We are talking about the importance of having 396.x NVIDIA drivers on openSUSE. Maybe you could help.

Thanks!


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

There are currently no plans to create RPMs for short-lived-branch drivers in addition to the ones for long-lived branch versions. And, the next long-lived branch (with a higher version number than 396.xx!) will be released very soon. Unfortunately I'm not allowed to tell you more details about the planned schedule for it.


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

In case you don't use Leap 15/Tumbleweed and are interested in RPMs for 396.xx you may want to use packages created and provided by NVIDIA themselves. http://developer.download.nvidia.com/compute/cuda/repos/


Rogério Leiro's avatar

RLFontan wrote over 3 years ago

Thats amazing!!! Ty!


Stefan Dirsch's avatar

sndirsch wrote almost 4 years ago

Chech this out. https://build.opensuse.org/package/show/X11:Drivers:Video/nvidia-gfxG05 Version 410.57 is still considered Beta, but an UDA release will be available very soon. And shortly after there will be prebuilt RPMs available via the known repository at NVIDIA.


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

I've built the packages locally, nothing exploded yet \o/ There were a couple harmless warnings because bison and flex are not required at build time. It doesn't have any visible consequence afaics.


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

Thanks! Good to hear this! :-)


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

The build is disabled for the whole repo, is it expected ?


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

Sure, due to legal reasons the .run files are missing in the repo, so the builds would always fail. Check README file for building the RPMs on your machine locally.


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

I'll ask differently, after enabling the X11:Drivers/Video repo, the G03 and G04 packages are available with vendor=obs://build.suse.de/Proprietary/X11:Drivers. can the G05 ones be made available there?


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

build.suse.de is an internal repo for SUSE employees. G05 RPMs will be available for everybody shortly after it's no longer Beta. I'm not allowed to talk about the release schedule. So please don't ask when.


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

ok, found an issue with nvidia-uvm, the module doesn't load and dmesg mentions: nvidia_uvm: Unknown symbol __pcpu_unique_interrupt_thread_context (err 0)

No idea where it's coming from, grep didn't help.


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

Couldn't reproduce this issue. Tried with latest TW kernel 4.18.12-1-default.


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

Any pointer? __pcpu_unique_interrupt_thread_context isn't in /boot/System.map-4.18.12-1-default


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

I don't. :-(


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

Thanks. looks like only my desktop computer has this issue. Even if I try to reinstall the G04 package, this symbol exists in nvidia-uvm.ko... but only on my desktop station, the laptop doesn't have it.

Now I'll try installing the G05 packages on both and copy the module file until I find why this symbol appears only in one module.


Christophe Giboudeaux's avatar

cgiboudeaux wrote over 3 years ago

Alright, found the issue: on the desktop computer, I changed the ld alternative to use gold. If I switch back to ld.bfd, the symbol isn't visible anymore.


Xu Zhao's avatar

nuklly wrote over 3 years ago

The installed dkms.conf is problematic. It contains "DKMS_MODULES" and other stuff not understood by the dkms. In the Nvidia blob, the binary nvidia-installer will modify the original dkms.conf by expanding the "DKMS_MODULES" macros and deploy the modified dkms.conf into the system. We should also install the modified dkms.conf instead of the original one into the system.



Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

Well, dkms.conf is only installed to /usr/src/kernel-modules/nvidia-$version-$flavor - together with all driver "sources". I doubt the system is interested in reading this file, even if you have some dkms package installed. So just a cosmetic issue ...


Hans-Peter Jansen's avatar

frispete wrote over 3 years ago

Hi Stefan,

TW is on kernel 4.20, and systems, that depend on this driver are quite unhappy since a few days...


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

Just added a patch to this project, which fixes the build against Kernel 4.20 of factory/TW. Will be fixed in NVIDIA's repository with the next update ...


Chema Ollés's avatar

pepetops wrote over 3 years ago

Hi I update to kernel 4.20 now and have an error... The new modules 4.20 want to link with olds 4.19.11 I doesn't have and then I have NO 4.20 nvidia modules.


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

See the reply to @frispete above ...


Chema Ollés's avatar

pepetops wrote over 3 years ago

Hi I update to kernel 4.20 now and have an error... The new modules 4.20 want to link with olds 4.19.11 I doesn't have and then I have NO 4.20 nvidia modules. If I compile from this build (osc) I have no problem to create the differents rpms files


Stefan Dirsch's avatar

sndirsch wrote over 3 years ago

Yes, I fixed the build in this repository already. ;-)


Chema Ollés's avatar

pepetops wrote over 3 years ago

It runs with the new 4.20.2 but not on previous 4.20.0 Thanks


Chema Ollés's avatar

pepetops wrote over 3 years ago

How can I force /usr/src/kernel-modules/nvidia-390.87-default compile against /lib/modules/4.20.0-1-default?


Chema Ollés's avatar

pepetops wrote about 3 years ago

Hi. Problems with kernel 5.1.2 Patch for 390.116 driver? Or better change to nvidia-gfxG05? Thanks


Chema Ollés's avatar

pepetops wrote about 3 years ago

Hi again. I patched the driver and compile the modules but I don't know how to create the new boot that knows nvidia modules are there. What rpm scripts runs when modules are compiled? Thanks



Chema Ollés's avatar

pepetops wrote about 3 years ago

Last kernel's update, 5.1.3 works perfectly with yours changes. Also compiled with the old 1.5.2 version. Thanks


Stefan Dirsch's avatar

sndirsch wrote about 3 years ago

You're welcome. Unfortunately the repos on NVIDIA server have not been updated yet.

openSUSE Build Service is sponsored by