Bug 1202950 - radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
radeon [Radeon 6450] Blank screen (Kernel driver regression on Leap 15.4)
Status: IN_PROGRESS
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel
Leap 15.4
x86-64 openSUSE Leap 15.3
: P3 - Medium : Normal (vote)
: ---
Assigned To: openSUSE Kernel Bugs
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-08-30 20:59 UTC by Jacobs
Modified: 2022-11-02 23:09 UTC (History)
5 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Video of boot process (394.12 KB, video/x-matroska)
2022-08-30 20:59 UTC, Jacobs
Details
Output hwinfo (3.11 MB, image/jpeg)
2022-09-14 19:02 UTC, Jacobs
Details
y2logs (615.35 KB, application/x-compressed)
2022-10-04 19:25 UTC, Jacobs
Details
dmesg log (1.74 KB, text/plain)
2022-11-02 22:23 UTC, Jacobs
Details
lsmod output (276 bytes, text/plain)
2022-11-02 22:23 UTC, Jacobs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jacobs 2022-08-30 20:59:14 UTC
Created attachment 861206 [details]
Video of boot process

Dear team,

first time for me reporting a bug here. I'm running openSUSE for years without serious problems on this system:

Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.76.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-150300.59.90-default
OS Type: 64-bit
Processors: 6 × AMD Phenom(tm) II X6 1075T Processor
Memory: 7,8 GiB
Graphic card: Radeon 6450
Mainboard: ASUS M5A88-V EVO

Installed openSUSE Leap 15.3. is working fine.

Now downloaded openSUSE Leap 15.4 Build 243.2 and trying to start offline upgrade from DVD or USB. Base system starts. Drivers are being installed (green process bar on the bottom of the display). Display switches to console mode. Different steps performed successful. Until removing repos. Last output "removed '/etc/zypp/repos.d/repo-sle-update.repo'". Then the display turns black, going to sleep mode, DVD drive continues to work a few seconds more and stops. See attached video for details. Only reboot possible.

As mentioned I tried to use DVD or USB, I downloaded image twice. I changed display settings at boot menu. I changed graphic card to mainboard internal. No change, display is going to sleep at the same stage of boot process.

Any idea? Thanks.
Comment 1 Stefan Hundhammer 2022-08-31 09:26:26 UTC
If you didn't already do that, checking the ISO checksum would be the obvious first step.

https://get.opensuse.org/leap/15.4/#download

In the "Download" combo box next to the image that you intend to use, also download the "Checksum" file (it's only a very small file) and use it to verify that your ISO is 100% correct:

  sha256 -c -c openSUSE-Leap-15.4*.sha256

Was that successful?
Comment 2 Stefan Hundhammer 2022-08-31 09:28:17 UTC
(In reply to Stefan Hundhammer from comment #1)
>   sha256 -c -c openSUSE-Leap-15.4*.sha256

Only one "-c", of course:

    sha256 -c openSUSE-Leap-15.4*.sha256
Comment 4 Jacobs 2022-09-01 20:05:36 UTC
(In reply to Stefan Hundhammer from comment #2)
> (In reply to Stefan Hundhammer from comment #1)
> >   sha256 -c -c openSUSE-Leap-15.4*.sha256
> 
> Only one "-c", of course:
> 
>     sha256 -c openSUSE-Leap-15.4*.sha256

Hi,

thanks for your feedback. I tried this but it doesn't work out of the box. When I download the x86_64-image it is saved as "openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso" but the checksum file looks for "openSUSE-Leap-15.4-DVD-x86_64-Media.iso". So I receive following output:

Data> sha256sum -c openSUSE-Leap-15.4*.sha256
sha256sum: openSUSE-Leap-15.4-DVD-x86_64-Media.iso: Datei oder Verzeichnis nicht gefunden
openSUSE-Leap-15.4-DVD-x86_64-Media.iso: FEHLSCHLAG öffnen oder lesen
sha256sum: WARNUNG: 1 aufgeführte Datei konnte nicht gelesen werden

I have renamed the iso-image matching to the checksum-file and received an OK.

I burned the image to a DVD using K3B. Reboot the computer, change language to German and chose upgrade. But process stops at the same point as before.
Comment 5 Michal Filka 2022-09-13 06:53:56 UTC
(In reply to Jacobs from comment #4)
> (In reply to Stefan Hundhammer from comment #2)
> > (In reply to Stefan Hundhammer from comment #1)
> > >   sha256 -c -c openSUSE-Leap-15.4*.sha256
> > 
> > Only one "-c", of course:
> > 
> >     sha256 -c openSUSE-Leap-15.4*.sha256
> 
> Hi,
> 
> thanks for your feedback. I tried this but it doesn't work out of the box.
> When I download the x86_64-image it is saved as
> "openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso" but the checksum file
> looks for "openSUSE-Leap-15.4-DVD-x86_64-Media.iso". So I receive following
> output:
> 
> Data> sha256sum -c openSUSE-Leap-15.4*.sha256
> sha256sum: openSUSE-Leap-15.4-DVD-x86_64-Media.iso: Datei oder Verzeichnis
> nicht gefunden
> openSUSE-Leap-15.4-DVD-x86_64-Media.iso: FEHLSCHLAG öffnen oder lesen
> sha256sum: WARNUNG: 1 aufgeführte Datei konnte nicht gelesen werden
> 
> I have renamed the iso-image matching to the checksum-file and received an
> OK.
> 
> I burned the image to a DVD using K3B. Reboot the computer, change language
> to German and chose upgrade. But process stops at the same point as before.

well, you still should be able to start the installer in text mode using textmode=1 as boot parameter when starting installation.

Can you than switch to another console and show us what "hwinfo --gfxcard" sees?
Comment 6 Jacobs 2022-09-14 19:02:12 UTC
Created attachment 861479 [details]
Output hwinfo
Comment 7 Jacobs 2022-09-14 19:03:33 UTC
(In reply to Michal Filka from comment #5)
> (In reply to Jacobs from comment #4)
> > (In reply to Stefan Hundhammer from comment #2)
> > > (In reply to Stefan Hundhammer from comment #1)
> > > >   sha256 -c -c openSUSE-Leap-15.4*.sha256
> > > 
> > > Only one "-c", of course:
> > > 
> > >     sha256 -c openSUSE-Leap-15.4*.sha256
> > 
> > Hi,
> > 
> > thanks for your feedback. I tried this but it doesn't work out of the box.
> > When I download the x86_64-image it is saved as
> > "openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso" but the checksum file
> > looks for "openSUSE-Leap-15.4-DVD-x86_64-Media.iso". So I receive following
> > output:
> > 
> > Data> sha256sum -c openSUSE-Leap-15.4*.sha256
> > sha256sum: openSUSE-Leap-15.4-DVD-x86_64-Media.iso: Datei oder Verzeichnis
> > nicht gefunden
> > openSUSE-Leap-15.4-DVD-x86_64-Media.iso: FEHLSCHLAG öffnen oder lesen
> > sha256sum: WARNUNG: 1 aufgeführte Datei konnte nicht gelesen werden
> > 
> > I have renamed the iso-image matching to the checksum-file and received an
> > OK.
> > 
> > I burned the image to a DVD using K3B. Reboot the computer, change language
> > to German and chose upgrade. But process stops at the same point as before.
> 
> well, you still should be able to start the installer in text mode using
> textmode=1 as boot parameter when starting installation.
> 
> Can you than switch to another console and show us what "hwinfo --gfxcard"
> sees?

Hello, I have attached a picture showing the output of 'hwinfo --gfxcard'. I hope this is o.k. in this way.
Comment 8 Jacobs 2022-10-02 18:41:43 UTC
Hy there, is there anything more I can/should test? Are there any further suggestions how to solve this problem?
Comment 9 Michal Filka 2022-10-03 07:03:06 UTC
(In reply to Jacobs from comment #8)
> Hy there, is there anything more I can/should test? Are there any further
> suggestions how to solve this problem?

You should be able to boot installation in text mode by attaching textmode=1 when starting installation (see e.g. https://en.opensuse.org/SDB:Installation_with_little_memory)
This issue could be related to https://bugzilla.suse.com/show_bug.cgi?id=1202930 Could you check suggestions / questions there and give us a feedback?
Could you also attach yast logs? You can use save_y2logs for that. See https://en.opensuse.org/openSUSE:Report_a_YaST_bug for more info.

Thanks
Comment 10 Jacobs 2022-10-04 19:25:28 UTC
Created attachment 861963 [details]
y2logs
Comment 11 Jacobs 2022-10-04 19:33:10 UTC
(In reply to Michal Filka from comment #9)
> (In reply to Jacobs from comment #8)
> > Hy there, is there anything more I can/should test? Are there any further
> > suggestions how to solve this problem?
> 
> You should be able to boot installation in text mode by attaching textmode=1
> when starting installation (see e.g.
> https://en.opensuse.org/SDB:Installation_with_little_memory)
> This issue could be related to
> https://bugzilla.suse.com/show_bug.cgi?id=1202930 Could you check
> suggestions / questions there and give us a feedback?
> Could you also attach yast logs? You can use save_y2logs for that. See
> https://en.opensuse.org/openSUSE:Report_a_YaST_bug for more info.
> 
> Thanks

Hello,

I started installation without any changes on video mode settings or something else. I only switched language to German and added boot parameter "textmode=1".

Running
  hwinfo --gfxcard | grep "Module Alias"
results
  Module Alias: "pci:v00001002d00006779sv0000174Bsd0000A007bc03sc00i00"

Running
  lspci -nnk | grep VGA
results
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779]

I have attached the y2logs.
Comment 12 Jacobs 2022-11-01 21:49:09 UTC
Hello, are there any suggestions how to solve my upgrade problem? Give the provided information any hints to the root cause of the problem?
Comment 13 Lukas Ocilka 2022-11-02 07:45:46 UTC
Logs show that the Installer has been started, and it has been started in text mode as requested.

Nothing really suspicious for the first sight, except "FAT-fs (sdf1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck." in 'messages' which IMO should not be causing this behavior.

There's one more thing you could do if you had more computers: try installing/updating the system using ssh: https://en.opensuse.org/SDB:Linuxrc#p_ssh (search for "ssh" option)

 # use ssh and set ssh password
 ssh=1 sshpassword=foobar123

when the installation system boots, it tells you the IP to connect to remotely and you just run `yast` to start it. In that case, the display is not used for YaST and it might work. You may also try to look around using another ssh connection.
Comment 14 Lukas Ocilka 2022-11-02 07:47:09 UTC
And BTW, my feeling is that this is probably not connected with YaST itself, but rather with the videocard driver, Kernel or something like that so maybe we are not the best team for debugging the problem.
Comment 15 Steffen Winterfeldt 2022-11-02 09:16:37 UTC
From the video it looks like some problem with Xorg. The screen goes into
standby when Xorg is started.

It is not clear why this happens. There is a log in /var/log/Xorg.0.log you
could check. There might be a driver missing.

You might try booting with the 'nomodeset' boot option.

You can also boot with startshell=1 which would not start the installer but
give you a bash prompt where you can run 'Xorg' manually and check what
happens.

In any case this looks not like an installer issue.

Reassigning to Xorg people.
Comment 16 Stefan Dirsch 2022-11-02 10:29:54 UTC
Yes, start the installation as you did in comment#6 for generating 'hwinfo' output. Then run 'Xorg -verbose 7 -logverbose 7-retro". You should see a Moiree pattern with a 'X' cursor on it. Check if the cursor can be moved with your mouse. Then after a few seconds press "Ctrl-Alt-Backspace" twice(rapidly!!!) to kill it. And then attach the generated /var/log/Xorg.0.log.
Comment 17 Stefan Dirsch 2022-11-02 10:31:37 UTC
The output of 'lsmod | grep radeon' and 'dmesg' would be also useful.
Comment 18 Jacobs 2022-11-02 22:23:12 UTC
Created attachment 862621 [details]
dmesg log
Comment 19 Jacobs 2022-11-02 22:23:36 UTC
Created attachment 862622 [details]
lsmod output
Comment 20 Jacobs 2022-11-02 22:24:48 UTC
Hello,

booting in textmode and running Xorg or 'Xorg -verbose 7 -logverbose 7 -retro' dosen't work. With Xorg the screen turns black immediatly and system is going to sleep and with the longer command the X-cursor can be seen shortly and then screen turns black. No interaction possible.

So /var/log/Xorg.0.log cannot be provided.

Output from dmesg and lsmod attached.

Booting with 'nomodeset' was successful. Then the graphical installl interface came up. 

Will this mean I can go on with 'nomodeset' to do the upgrade or do I risk to not be able to boot in graphic mode after upgrade?
Comment 21 Stefan Dirsch 2022-11-02 23:03:59 UTC
radeon driver is loaded. Apparently there is a regression in the driver on kernel 15.4. By updating with "nomodeset" you likely will be limited to "fbdev" Xdriver, i.e. lose any video hardware acceleration, multimonitor support and possibly needed specific monitor resolutions.
Comment 22 Stefan Dirsch 2022-11-02 23:06:17 UTC
Kernel issue. Reassigning.