Has anyone had a problem with the latest snapshot? I did a ‘zyyper dup’ and my p/c now boots to a blank screen.
I re-booted using the previous kernel and that booted fine. Using KDE Plasma & Nvidia driver.
Thanks
Has anyone had a problem with the latest snapshot? I did a ‘zyyper dup’ and my p/c now boots to a blank screen.
I re-booted using the previous kernel and that booted fine. Using KDE Plasma & Nvidia driver.
Thanks
Hi
Yes I have the same issue… I also temporarily solved it by using the previous kernel.
Thanks for posting tk2 - always good to know it is not just me!
Hi
I’m assuming you’re both using the repository rpms, Not published for the 15.6.8 kernel yet… http://http.download.nvidia.com/opensuse/tumbleweed/x86_64/
I was under the impression that it should rebuild automagically on your system after a kernel update?
Or switch to the run file, AKA Hard Way? The 510.47.03 is running fine here manually rebuilt.
Thanks for posting Malcolm.
Yes - using the nvidia repo here. Yes - did automatically rebuild (as part of the ‘zypper dup’ process) but I am guessing that something is not quite right somewhere.
I’m using the exact same scenario as dth2: KDE Plasma & Nvidia driver from the repository rpms.
The automatic rebuild did run and I didn’t see any errors. However, I didn’t really check the whole log for errors before rebooting as it is just a minor kernel update.
Same issue, I am with amd graphics card. When booting I loose also the keyboard.
Hi
Have both here, primary graphics is AMD RX550, no issues here, Quadro T400 for the nvidia side (offload).
Nvidia GTX 1060 470.103.01 Update from Kernel 5.16.2 to 5.16.8:
NVIDIA RTX 3080 Ti 470.103 Update from Kernel 5.16.5 to 5.16.8:
GTX 550 Ti with 390er driver not affected. Boots fine with Kernel 5.16.8
Also the actual snapshot iso does not work on this two mentioned machines with newer cards.
openSUSE-Tumbleweed-DVD-x86_64-Snapshot20220212-Media.iso
If i try to install/update from the USB-Stick with these image, the last message seen is “init ramdisk”. After that the screen goes black and all USB-ports are lost.
Have old hardware, radeon hd 5570 with kernel firmware driver for radeon
hi,
similar problem here,
boots ok with Kernel: 5.16.5-1-default x86_64
with Kernel: 5.16.8-1-default x86_64 boot stops with a black screen
failure similar on another PC
doing a manual boot via grub, Kernel: 5.16.8-1-default x86_64 boots ok
something simple missing?
any suggestions anyone?
hw on this machine:-
Machine: Type: Desktop System: BIOSTAR product: A880G+ v: N/A serial: <filter>
Mobo: BIOSTAR model: A880G+ serial: <filter> BIOS: American Megatrends v: 080016 date: 01/25/2011
CPU: Info: Quad Core model: AMD Phenom II X4 965 bits: 64 type: MCP cache: L2: 2 MiB
Speed: 800 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RS880 [Radeon HD 4250] driver: radeon v: kernel
Display: x11 server: X.Org 1.21.1.3 driver: loaded: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RS880 (DRM 2.50.0 / 5.16.5-1-default LLVM 13.0.1) v: 3.3 Mesa 21.3.5
ps. Kernel: 5.16.8-1-default x86_64 boots ok on HP laptop
I boot ok, but on KDE Plasma, brightness on X11 and Wayland does not work.
When on X11, I cannot change screen brightness.
When on Wayland, it does not boot to desktop, but stuck in terminal login.
Operating System: openSUSE Tumbleweed 20220212
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.8-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics
Memory: 7.1 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2
Nvidia driver version: 510.47.03
On ancient DirectX11 AMD C2D setup & Plymouth never shows up, earlier kernel boots & pre snapper rolls back.
Workaround:
[Comment 7](https://bugzilla.opensuse.org/show_bug.cgi?id=1195887#c7) Stefan Dirsch 2022-02-14 15:22:23 UTC
Could you try with kernel option
initcall_blacklist=simpledrm_platform_driver_init
to disable simpledrm?
I plan to give Stefan’s fix a try. In the meantime, though: I’ll add myself to the list of affected users, with the nvidia .run installed “the hard way.” I locked the kernel at 5.16.5, haven’t yet done any additional troubleshooting.
Adding initcall_blacklist=simpledrm_platform_driver_init to kernek commandline “fixes” the problem on my machines with Nvidia cards.
Same here - adding:
initcall_blacklist=simpledrm_platform_driver_init
to the kernel commandline “fixes” the problem on my machine
I have the same problem.
Could you please describe the procedure to add this to the command line.
Thank you.