https://bugzilla.novell.com/show_bug.cgi?id=881723 https://bugzilla.novell.com/show_bug.cgi?id=881723#c9 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #9 from Wolfgang Bauer <wbauer@tmo.at> 2014-06-11 09:15:24 UTC --- (In reply to comment #8)
Well, if you add taboos, all kind of strange dependancy conflicts are to be expected. i386 is no longer well tested either (PAE only exists on i386). Carl Fletcher has a 64bit system anyway. In his case this particular problem was caused by the old SoftLocks "issue" in libzypp, as he uninstalled nvidia-uvm-gfxG03-kmp-desktop once already.
I tried the update now as well on an nvidia system, and Apper/PackageKit and YaST as well wanted to install nvidia-uvm-gfxG03-kmp-default and kernel-default on this kernel-desktop system. I had to manually de-select the -default flavor, then the correct one (-desktop) was selected. I checked, and the SoftLocks file was empty here, so this was not the cause for me. And I don't have any taboos in place either. Maybe it would be safer if the kmp package would recommend a uvm-kmp package of the same kernel flavor? Not sure if this is doable though.
Interesting to see that you can still use a gfx card on such a system with the latest driver. Second boot sounds like kernel modules get unlodaded and reloaded first.
I had the same issue here. On the first reboot after the installation, nvidia fails to load and fbdev is used. And I do have the correct packages installed. Also others have reported this issue, and that a simple reboot would fix it, and indeed a reboot fixed it here as well. So something apparently doesn't quite work as intended. Should we open a new bug report for this? I can't find anything suspicious in the log files though, the nvidia kernel module seems to be loaded correctly. I have saved a copy of the dmesg from the "failed" boot if it might help. The only difference I see to the successful boot immediately afterwards is that there's an additional: [ 21.929497] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem [ 21.929730] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 0 [ 21.929740] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.79 Sun May 18 03:55:59 PDT 2014 [ 21.952135] nvidia_uvm: Loaded the UVM driver, major device number 250 whereas the successful boot has this instead: [ 20.140360] nvidia 0000:01:00.0: irq 43 for MSI/MSI-X [ 20.757102] NVRM: Your system is not currently configured to drive a VGA console [ 20.757106] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver [ 20.757107] NVRM: requires the use of a text-mode VGA console. Use of other console [ 20.757109] NVRM: drivers including, but not limited to, vesafb, may result in [ 20.757110] NVRM: corruption and stability problems, and is not supported. But I have no idea why this would change from one boot to the next. -- 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.