Radeon HD driver does not support UltraWide displays

[roiredxsoto]

Good day,

Box Specs: AMD A8-5600K, 16GB Ram, Radeon RX560, Dell U3415W ultrawide

~> uname -a
Haiku Cygnvs 1 hrev52379 Oct  1 2018 14:59:14 x86_64 x86_64 Haiku

Expected behaviour:

• turn on box, boot to desktop without issues

Observed behaviour:

• turn on box, modules load, black screen, screen goes to sleep mode, no desktop

Reproduce:

• Anytime that VESA safe mode driver is commented out in /boot/home/config/settings/kernel/drivers/kernel

VESA driver works "fine", RadeonHD driver always results in black screen and display going to sleep mode after all system modules loaded, thus desktop is not loaded, but box is still on. Have to manually force hardware shutdown, as press power button once does not shut down the box as with the USB issues.

[roiredxsoto]

listdev file

[roiredxsoto]

list of drivers "listimage | grep drivers/"

[roiredxsoto]

syslog with VESA driver loaded, set as default in /boot/home/config/settings/kernel/drivers/kernel

[roiredxsoto]

presumed syslog of using RadeonHD driver on boot

[roiredxsoto]

Good day,

VESA mode is no longer available, only 'framebuffer' is there for the Radeon RX570 and the Radeon RX560 (on hrev54477). Not sure if that makes any difference.

Regards,
RR

[kallisti5]

weird.. All of the attached logs seem to just show using VESA mode.

Any log lines related to the radeon_hd driver will show "radeon_hd" These logs only show the driver loading for the card, but the accelerant is never called.

So, it appears you haven't captured the radeon_hd driver being used in the attached syslogs.

Generally if radeon_hd doesn't work for some reason, it will say so.

Maybe next time you try, look at syslog_old as well as syslog? There should be 30+ lines matching "radeon_hd" in the relevant logs.

I double checked, and your card is definitely supported in the driver:

{0x67ff, 12, 1, RADEON_POLARIS11, CHIP_STD, "Radeon RX 560"},

We need to more clearly state that the vesa/framebuffer driver is being used in our logging. :-|

[roiredxsoto]

20200803-Syslog

[roiredxsoto]

Good day @kallisti5,

I attached today's syslog from the Haikbox with the RX560 (1680x1050), and there are actually some lines with the radeon_hd text in there. This syslog is using the SafeVideo mode, as I never got Haiku to boot without safevideo, unless something has changed lately. :)

I will try to boot again without the SafeVideo and see if can get to desktop here with the RX560 and at home with the RX570, and update the info accordingly.

Thanks and regards,
RR

PD.: This happens with the Ultrawide (3440x1440) and a normal 16:9 (1680x1050) display

[kallisti5]

Thanks, the new logs still don't show anything useful...

KERN: radeon_hd: init_hardware
KERN: radeon_hd: init_driver
KERN: radeon_hd: init_driver: GPU(0) Radeon RX 560, revision = 0xcf
KERN: radeon_hd: publish_devices
KERN: radeon_hd: find_device
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/radeon_hd

There will be 30+ lines of log data when radeon_hd is used. This shows the radeon_hd driver was loaded, and found a card... but these are the logs from VESA.

Please check syslog *and* syslog_old.

The general process when this happens goes:

1) Boot Haiku normally. Black or corrupt screen? 2) wait 2 minutes with the black / corrupt screen. 3) Hold ctl+alt+del until the machine reboots. 4) Boot Haiku again. This tap space space just before haiku boot screen appears. 5) Select fail safe video

Step 3 is important because the potential for the logs to no be written to disk yet exists if you just hard reset via the physical button or power off.

[roiredxsoto]

Good day @kallisti5,

I did the steps you pointed out and got the syslog files that are attached today. Nonetheless, this I did with the home haikbox, with the RX570. Didn't have time at work to turn on the haikbox and do the test with the RX560. Will do there when I get free time. In the meantime, let me know if the attached Syslogs are of any help or if you need I do more testing.

Regards,
RR

[roiredxsoto]

Syslog file after crash.

[roiredxsoto]

Syslog with default failsafe settings on RX570

[roiredxsoto]

Syslog.old file after crash, presumed to be same as Syslog1

[roiredxsoto]

Good day @kallisti5,

Today I had some time to check the syslog and syslog.old files and certified what you said, the loaded driver is the VESA, though Screen prefs still shows I'm using Framebuffer.

Tested just now with:

~> uname -a
Haiku hawku 1 hrev54953 Feb 10 2021 07:02:19 x86_64 x86_64 Haiku
~>

But no 30+ lines with the radeon_hd, nor in syslog, nor in syslog.old. I'll go with the process you pointed out again and check the outcome to see if there is something new there.

Thanks.
Regards,
RR

[roiredxsoto]

new syslog after booting again in failsafe

[roiredxsoto]

old syslog

[roiredxsoto]

Syslog after blacklisting again the video driver, using safe mode video

[roiredxsoto]

Presumed syslog of boot process that ended up in app_server crash

[roiredxsoto]

Good day,

~> uname -a
Haiku hawku 1 hrev55009 Mar 22 2021 06:58:52 x86_64 x86_64 Haiku

Today I carried the test again (but on the integrated Radeon Vega):

1- add the comment to the fail-safe mode in kernel settings
2- boot Haiku
3- (new) the white screen came out with all the debug jitter scrolling through the screen until it stalled
4- after stalle, waited for more than 2 minutes with the screen like that
5- pressed Ctrl+alt+del for nearly 4 minutes, nothing happened
6- hard reboot

Attached are the new Syslog and Syslog.old, as well as some pics. And now that I have time to review the Syslogs, there is nothing about those 30 lines of "radeon" anywhere. Strange :?

Hope this helps
Regards,
RR

[roiredxsoto]

20210322 Syslog

[roiredxsoto]

20210322 Syslog.old

[roiredxsoto]

White screen with debug info starting

[roiredxsoto]

20210322 White screen after the debug lines stalled. Nothing happened afterwards for more than 2 minutes, stayed like this until reboot

[modeenf]

Strange I have the same Card (Rx 560) with the same problem in hrev56193. My radeon_hd shows..

Perhaps my log can give som clue? sorry for "Hijacking" your ticket..