[Bug 745149] New: nVidia repo during upgrade 32-bit 11.3 > 12.1, other repo issues
https://bugzilla.novell.com/show_bug.cgi?id=745149 https://bugzilla.novell.com/show_bug.cgi?id=745149#c0 Summary: nVidia repo during upgrade 32-bit 11.3 > 12.1, other repo issues Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: HP OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: tonysu@su-networking.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Affects - Likely all hardware installing or upgrading openSUSE using any nVidia GPU Summary of successful upgrade - zypper refresh, update 11.3 - zypper disable all existing repos - zypper add 12.1 oss, non-oss, update repos - zypper dup - Boot using sysvinit to emergency mode - Add nVidia repo from Community Repos - Manually install nVidia driver - reboot - Remove old desktop widgets, re-create Issues: On my system (HP dv9500) the default video driver does not work. This was true in 11.3 also, is still true in 12.1 so it's critical to be able to install the nVidia driver as easily and early as possible. The exact error returned is a missing Xorg configuration file. 1. Unable to add nVidia repo during install nVidia repo not listed as a Community repo during install (is listed after install) Attempted to add nVidia repo using FTP URI, error displayed is unable to resolve DNS... Exact problem likely is that the repo manifest is expected in a "repo" subdirectory (incorrect) when the subdirectory is actually "repodata" == Possible immediate solution, make the nVidia repo available during install, because the community repo list is dynamically downloaded it can be configured properly. The "repo" subdirectory issue is likely a hardcoded error in Final Release that can't be addressed until the next major release... Also, if repo manifest directories can vary, it should be possible for the User to configure. 2. After install, using YAST the nVidia repo is listed as a Community Repo and is added without issue. However, after adding the nVidia repo, then doing a zypper refresh and update does not install the appropriate driver automatically (which would be expected). Instead, using zypper I had to manually select and install a video driver. 3. Curiously, after installation and when installing a number of Community Repos except for the nVidia repo none could be added immediately, could all of them be down at once? A day later they were all accessible. Since nVidia repo was always accessible, problem was not network related. 4. The Java Community repo is secured with an untrusted certificate. Surprising, can't that be addressed especially since the repo data is dynamically downloaded on demand(I will submit this as a separate bug)? 5. A non-repo comment regarding sysvinit... I assume that this is likely a common issue related to upgrading. When I attempted using systemd, numerous warnings related to deprecated udevd followed by a possible real error related to a custom udev entry(likely related to Release Notes "Custom Service Startup") I created to support Android ADB (Android Device Bridge). Am concerned migration to systemd will be a real issue later if sysvinit support ends and migration issues aren't addressed. Since I used "zypper dup" first (when systemd issues first encountered i also tried the 32-bit ISO without diff), these issues are "current" and not due only to issues related to the ISO release. 6. Add comment regarding sysvinit... Pulseaudio failed during initial install using systemd. After sysvinit was enabled, Pulseaudio was enabled successfully. Subjectively, even using HDintel devices 12.1 there is a substantial sound improvement over 11.3. No change subjectively switching from HDintel to Pulseaudio. 7. A non-repo general comment about Upgrade free space requirements. Don't know if it's my imagination but the upgrade seemed to "discover" a number of applciations I had once installed and then removed, and re-installed those apps. This caused an enormous increase in disk space usage which became worrisome because AFAIK you can't interrupt zypper dup without catastrophic consequences. In my case I seemed to barely escape catastrophe with less than 1GB free space on the root partition, which apparently is only enough to login with root but none of my other User accounts. Bottom line is that a "dry run" option which can properly estimate free space requirements would be extremely useful. May be related to bugtraq #715875 but note that I resolved my problem without the "nomodeset" setting May be related to bugtraq #727055 but note that bug remains unresolved (supposedly the problem is "upstream"). Depending on where "upstream" is, it should be noted that simply installing a driver from the nVidia repo should resolve all typical issues. My personal suspicion is that the problem is the openSUSE implementation, first appeared somewhere between 11.1 and 11.3 and has been carried forward ever since. Reproducible: Always Steps to Reproduce: Upgrading (See convoluted steps to successful install in "Details") Actual Results: No known specialized characteristics, believe these issues would be common to any System Upgrade and a number of normal installations using nVidia GPUs. Expected Results: See "Details" - Includes not only issues but also proposed fixes for several issues. This bug is being submitted with a recommended "Critical" level because I feel most Users might not be able to work out these issues on their own. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c1
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c2
Michael Andres
- zypper refresh, update 11.3 - zypper disable all existing repos - zypper add 12.1 oss, non-oss, update repos - zypper dup
If the nvidia repo is important for you, why didn't you add the 12.1 nvidia repo before doing the 'zypper dup'? If you just disable the repo and do not add a repo to update from, you indicate that the packages installed from this repo are no longer needed. So they may even get deleted if they are involved in some dependency conflict. There should be no need boot some emergency mode just to get the nvidia driver installed.
1. Unable to add nVidia repo during install nVidia repo not listed as a Community repo during install (is listed after install)
Sounds to me as if YAST was used here, not zypper. With zypper you should be able to add any repo you want (all you need is the URL)...
2. After install, ... However, after adding the nVidia repo, then doing a zypper refresh and update does not install the appropriate driver automatically (which would be
'zypper update' updates already installed packages. If the driver is not already installed, this command won't touch it. You can try 'zypper inr' (install-new-recommends). This command can be used to install e.g newly available hardware drivers (provided the hardware is properly detected by the kernel and the driver package correctly indicates the hardware it supports).
3. Curiously, after installation and when installing a number of Community Repos except for the nVidia repo none could be added immediately, could all of them be down at once? A day later they were all accessible. ...
Hard to tell without error messages or logfiles...
4. The Java Community repo is secured with an untrusted certificate. 5. A non-repo comment regarding sysvinit... I assume that this is likely a 6. Add comment regarding sysvinit... Pulseaudio failed during initial
Should be filed as separate bug reports against the Java Community repo, sysvinit and pulseaudio.
7. ....Bottom line is that a "dry run" option which can properly estimate free space requirements would be extremely useful.
Agreed. There are already Bugs filed for this (e.g. 551678 - zypper dup heavily mis-predicting used disk space). ---- Passing it back to the components default assignee as the zypp related issue is already covered. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c3
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c4
--- Comment #4 from Stefan Dirsch
(IMO too may issues for too many components in one report)
- zypper refresh, update 11.3 - zypper disable all existing repos - zypper add 12.1 oss, non-oss, update repos - zypper dup
If the nvidia repo is important for you, why didn't you add the 12.1 nvidia repo before doing the 'zypper dup'?
If you just disable the repo and do not add a repo to update from, you indicate that the packages installed from this repo are no longer needed. So they may even get deleted if they are involved in some dependency conflict.
I can only second that. Actually the old nvidia RPMs need to get uninstalled since kABI changed between Kernels of openSUSE 11.3 and 12.1. But with the 12.1 repo being added the new ones for openSUSE 12.1 would have been installed.
2. After install, ... However, after adding the nVidia repo, then doing a zypper refresh and update does not install the appropriate driver automatically (which would be
'zypper update' updates already installed packages. If the driver is not already installed, this command won't touch it.
You can try 'zypper inr' (install-new-recommends). This command can be used to install e.g newly available hardware drivers (provided the hardware is properly detected by the kernel and the driver package correctly indicates the hardware it supports).
dup of bnc #750440. Already fixed.
3. Curiously, after installation and when installing a number of Community Repos except for the nVidia repo none could be added immediately, could all of them be down at once? A day later they were all accessible. ...
Hard to tell without error messages or logfiles...
This repo is provided by NVIDIA, not by openSUSE. This is likely the reason. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c5
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=745149
https://bugzilla.novell.com/show_bug.cgi?id=745149#c6
kk zhang
participants (1)
-
bugzilla_noreply＠novell.com