What | Removed | Added |
---|---|---|
Component | Kernel | X11 3rd Party Driver |
Assignee | kernel-maintainers@forge.provo.novell.com | xorg-maintainer-bugs@forge.provo.novell.com |
QA Contact | qa-bugs@suse.de | sndirsch@suse.com |
(In reply to Ulrich Windl from comment #2) > I tried booting the previous kernel (via GRUB menu), but that didn't change > a thing. So this is no kernel regression, as it seems. > Next thing I tried was to remove the Nvidia "G03" packages via Yast software > management, and surprisingly those modules were not removed, but replaced > with Nvidia "G04" modules: > nvidia-uvm-gfxG04-kmp-default-352.79_k4.1.12_1-19.1.x86_64 Mon Feb 1 > 13:12:37 2016 > x11-video-nvidiaG04-352.79-19.1.x86_64 Mon Feb 1 13:09:20 2016 > nvidia-computeG04-352.79-19.1.x86_64 Mon Feb 1 13:09:15 2016 > nvidia-glG04-352.79-19.1.x86_64 Mon Feb 1 13:09:01 2016 > nvidia-gfxG04-kmp-default-352.79_k4.1.12_1-19.1.x86_64 Mon Feb 1 13:08:06 > 2016 It's because of the dependency, I suppose. > These modules cauise a complete failure to star tthe X server (it seems). > I had to switch to the text console. There I removed those "G04" packets > (which worked). Then I could start an X session with the usual resolution > again. So, this looks more like an issue of Nvidia stuff. Changed the component.