On a 1024x768-screen instead a 2560x1440 it’s even not easy to operate …
xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
I’ve just tried to use a new kernel from openSuse Kernel repository.
After updating the kernel - Kernel 4.11 - at boot time the display is looking better - I think in native 2560x1440 Pixel - but soon after the KDE starting screen:
KERNEL PANIC
I’ve taken the old version, but:
How should I proceed?!
After some hours, going back to the last ‘stützpunkt’ : my monitor is working! Great!
This version is the very first for me with working screen:
uname -a
Linux linux-ep76 4.11.0-rc4-1.g491b77c-default #1 SMP PREEMPT Mon Mar 27 12:50:15 UTC 2017 (491b77c) x86_64 x86_64 x86_64 GNU/Linux
O.k., that was to expect, and also a slow system for some time.
But a 1024x768-screen … My now nearly dead PC from 2005 had a screen with 1600x1200 … and web pages weren’t filled with SPAM.
My Ryzen is running slow, but stable in vanilla 42.2 - but on 1024x768 there’s no overview, and that I’m needing for a totally new environment.
A native screen - 2560x1440 - is only possible using the very unstable and restricted usable kernel 4.11.0-rc4, but only using a read-only rollback and waiting a long, long time for booting (e.g. 10 min delay because a lot of “unexpected IRQ trap at vector 07” messages).
The same kernel in other modes is ending nearly always in “kernel panic”, but at one time in an endless IRQ trap at vector 07 - loop.
(My first try to write an answer was ending in unknown state with black screen)
So, just for testing I’ve tried to install the vanilla kernel 4.11 - but I’m using a read only rollback, and unrolled it will end in kernel panic.
Using this rollback is - beside it’s unstability - easy because of a big screen - but all usable rollbacks aren’t of any use for updating.
That’s a big handicap for the rollback technique …
I rebooted my Ryzen with kernel 4.4 and installed the ‘same’ Beta-test kernel 4.11, but the vanilla kernel. In Yast I my only change was to select this vanilla kernel.
After Installation I made a new boot on the fly. The system started successfully - not with kernel panic.
Screen ist at 2560x1440, and the system is working up to now.
Up to now I haven’t tried a cold boot using this kernel 4.11.
There are 2 possiibilities:
that’s working - then the error is in the opensuse standard kernel patch
42.2 versuchsweise als zweites System neu auf den Ryzen eingespielt, auf andere Platte.
Installation vom selben Träger wie zuvor, auch fehlerfrei, aber wesentlicher Unterschied:
MAC-Adresse ist jetzt beim Router angemeldet, also Patches nicht erst nach ersten Booten eingespielt.
der Monitor wurde diesmal bei der Installation erkannt und konfiguriert, ohne Kernelupgrade!
uname -r
4.4.57-18.3-default
beim Booten keine Fehlermeldung
(neuer thread: Lautsprecher am Monitor (Display-Port) geben nach wie vor keinen Ton,
nur die alten externen. Weder mit noch ohne Kabelanschluß.
Am alten PC unter VGA+Audiokabel tönen sie)
Trotz unverändertem Swap (knapp 32 GB) und selber MS-Partition kommt das System nach Standby nicht wieder hoch
im Gegensatz zu vorher.
Kann man das mit ‘Bordmitteln’ abstellen?
After allowing internet contact by setting the MAC-address at the router I reinstalled the 42.2
Now after installation the screen is set to full size (1440x2560). That's done by boot option.
After an offline installation this change is not made automatically before kernel change.
My graphic card is a polaris (also ‘too new’), monitor on Display Port. As an internal workaround it’s seen as VGA:
HDMI audio boxes are deactivated
There’s no error message at boot time (at boot: 4.11 beta 4+5 kernels were giving some minutes error messages, looping endlessly, or ending in kernel panic, but a reboot may help
with standard kernel 4.4.57-18.3-default the system is slowing down after some time, perhaps after some idle time (some seconds for echo of a char).
Beside the same swap partition of ~32GB und the same MS-Partition than before there’s no awaking after standby in opposition to my first 42.2 installation.
It seems to be best to be patient, wait for a stable kernel 4.11, and hope.
Today I installed Tumbleweed on an USB3-Port disk (as I just wrote that, Leap 42.2 crashed - this time “CPU 13 bank 3 … machine check”).
After greater problems at the first boot - kernel panic, and the usual enerving boot error (not) logging messages - this system was creeping up slowly.
Sadly beside adding the kernel repository yast wasn’t able to work - yast was hanging infinitely when I tried to update tumbleweed, but also at the attempt to make an addition to the boot loader parameters.
I wanted to install kernel 4.11 RC7, but that was therefore impossible, and it was impossible to see, if HDMI audio is running on my machine under tumbleweed with kernel 4.10.11.
There’s some progress to see, but up to now Leap 42.2 with the default kernel is still the most stable of a series of instable versions for my Ryzen PC (I’ve not tried 42.2 with 4.11 RC7).
