Bug 479329 - NVIDIA kernel module leaves dangling symlinks
Summary: NVIDIA kernel module leaves dangling symlinks
Status: RESOLVED FIXED
: 478436 479588 (view as bug list)
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i586 openSUSE 11.1
: P2 - High : Major with 1 vote (vote)
Target Milestone: ---
Assignee: Michal Marek
QA Contact: E-mail List
URL:
Whiteboard: maint:released:11.1:23633
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 00:44 UTC by Stefan Tittel
Modified: 2009-04-08 07:24 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
fixed weak-modules2 (18.50 KB, text/plain)
2009-03-02 11:27 UTC, Michal Marek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Tittel 2009-02-25 00:44:27 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6

Package nvidia-gfxG02-kmp-pae and others from the NVIDIA repository have been updated to package version 180.29_2.6.27.18_0.3-0.1. These updated packages depend on a kernel version not yet released with openSUSE 11.1, hence the attempt to install these packages will fail due to dependency errors.

This is especially sad for new users/new installations who/which don't have an old version of the NVIDIA driver already installed.

Three possible (mutually exclusive) solutions:

1) Finally release the updated kernel (as I heard on IRC there is an updated kernel in the pipes anyways).

2) Release the modules packages of the new NVIDIA drivers for the kernels currently available in openSUSE 11.1.

3) Remove the new NVIDIA packages and revert to the old ones until the new kernel packages are ready.

Reproducible: Always
Comment 1 Marcus Meissner 2009-02-25 06:59:35 UTC
NVIDIA was too fast putting the new modules online. This is not really controllable from us here.

I hope that we can release the updated kernel today, but we needed to some other fixes to make it install good enough.
Comment 2 Michael McCarthy 2009-02-25 10:40:33 UTC
There should be better coordination between openSUSE and Nvidia.  At least report the bug to them and work on a mutual resolution.
Comment 3 Marcus Meissner 2009-02-25 17:14:09 UTC
*** Bug 479588 has been marked as a duplicate of this bug. ***
Comment 4 Marcus Meissner 2009-02-25 22:56:19 UTC
*** Bug 478436 has been marked as a duplicate of this bug. ***
Comment 5 Marcus Meissner 2009-02-26 15:20:49 UTC
the kernel update that matches this bug was just released and should be available in 1 - 2 hours for everyone, and then it should work :)
Comment 6 Igor Jagec 2009-02-27 00:00:02 UTC
Here's how it works:

# zypper in x11-video-nvidiaG02 nvidia-gfxG02-kmp-default
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
  nvidia-gfxG02-kmp-default x11-video-nvidiaG02 


Overall download size: 13.4 M. After the operation, additional 59.5 M will be used.
Continue? [YES/no]: y
Retrieving package x11-video-nvidiaG02-180.29-0.1.x86_64 (1/2), 11.3 M (48.7 M unpacked)
Retrieving: x11-video-nvidiaG02-180.29-0.1.x86_64.rpm [done (685.8 K/s)]
Installing: x11-video-nvidiaG02-180.29-0.1 [done]
Retrieving package nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64 (2/2), 2.1 M (10.9 M unpacked)
Retrieving: nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64.rpm [startRetrieving: nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64.rpm [20% (Retrieving: nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64.rpm [55% (Retrieving: nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64.rpm [88% (Retrieving: nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64.rpm [done (639.2 K/s)]
Installing: nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1 [error]
Installation of nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: cat: /var/tmp/weak-modules2.AeUIcF/krel-nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1: No such file or directory
/usr/lib/module-init-tools/weak-modules2: line 53: /var/tmp/weak-modules2.AeUIcF/modules-nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1: No such file or directory
/usr/lib/module-init-tools/weak-modules2: line 476: /var/tmp/weak-modules2.AeUIcF/basenames-nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1: No such file or directory
error: %post(nvidia-gfxG02-kmp-default-180.29_2.6.27.18_0.3-0.1.x86_64) scriptlet failed, exit status 1


Abort, retry, ignore? [A/r/i]:
Comment 7 Marcus Meissner 2009-02-27 08:14:30 UTC
this looks bad.

please make sure you have the module-init-tools installed that we released yesterday before proceeding.

what is: rpm -q module-init-tools ?
Comment 8 Igor Jagec 2009-02-27 19:29:52 UTC
# rpm -q module-init-tools
module-init-tools-3.4-56.9.1.x86_64

My system is fully updated.
Comment 9 Michal Marek 2009-03-02 11:18:15 UTC
(In reply to comment #8)
> # rpm -q module-init-tools
> module-init-tools-3.4-56.9.1.x86_64
                               ^^^^^^

Did you tweak your rpm popt config to show the architecture in rpm -q output? The weak-modules2 script does use plain rpm -qa in one place and such a change could indeed cause the failure you are seeing. The nvidia rpm installs fine here btw.
Comment 10 Michal Marek 2009-03-02 11:27:40 UTC
Created attachment 276360 [details]
fixed weak-modules2

Please save this file as /usr/lib/module-init-tools/weak-modules2 and try again.
Comment 11 Stefan Tittel 2009-03-02 13:34:41 UTC
I don't suffer the same problem as Igor. After the updated kernel hit the update repository, the problem I originally reported is fixed for me (using the 2.6.27.19-3.2-pae kernel). Hence I cannot function as the info provider and will therefore change "Info Provider" to Igor.
Comment 12 Igor Jagec 2009-03-02 13:50:43 UTC
Michal, you were right, I tweaked the rpm configuration a little bit by adding the following line into my /etc/rpm/macros:

%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}

Erasing that line did the trick, thank you very much. I guess that tweaking rpm was not a good idea.
Comment 13 Michal Marek 2009-03-02 13:59:51 UTC
OK, thanks for confirming. In the meantime, I submitted the fix from comment #10 to Factory.
Comment 14 Swamp Workflow Management 2009-04-08 07:24:00 UTC
Update released for: module-init-tools
Products:
openSUSE 11.1 (debug, i586, ppc, x86_64)