Vega 56 with displayport output yields black screen and flashing C/N/S keys on keyboard.

[mpxlbs]

I have an Gigabyte Vega 56 Gaming 8GB PCI-E card.

If I select to fall back to vesa drivers, it boots and works. Not doing that causes my screen to say that no inputs are found and the screen goes to sleep while the C/N/S keys flash once on my keyboard. I suspect that might be a kernel panic?

It's on a Asus Prime x370 Pro motherboard.

I'll attach listdev and syslog.

I'm in doubt if I should select the radeon or radeon_hd (definately not ATI) bug description, as it's a Vega card.

[mpxlbs]

Listdev output.

[mpxlbs]

Syslog output.

[mpxlbs]

Here is some info from Linux

       description: VGA compatible controller
       product: Vega 10 XL/XT [Radeon RX Vega 56/64]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:0d:00.0
       version: c3
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=amdgpu latency=0
       resources: irq:43 memory:e0000000-efffffff memory:f0000000-f01fffff ioport:e000(size=256) memory:fe600000-fe67ffff memory:c0000-dffff

(Thanks WikiFormatting!)

0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3) (prog-if 00 [VGA controller])
        Subsystem: Gigabyte Technology Co., Ltd Vega 10 XL/XT [Radeon RX Vega 56/64]
        Flags: bus master, fast devsel, latency 0, IRQ 43
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f0000000 (64-bit, prefetchable) [size=2M]
        I/O ports at e000 [size=256]
        Memory at fe600000 (32-bit, non-prefetchable) [size=512K]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [64] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [150] Advanced Error Reporting
        Capabilities: [200] Resizable BAR <?>
        Capabilities: [270] Secondary PCI Express <?>
        Capabilities: [2a0] Access Control Services
        Capabilities: [2b0] Address Translation Service (ATS)
        Capabilities: [2c0] Page Request Interface (PRI)
        Capabilities: [2d0] Process Address Space ID (PASID)
        Capabilities: [320] Latency Tolerance Reporting
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c3)

Here is the card itself

​https://www.gigabyte.com/Graphics-Card/GV-RXVEGA56GAMING-OC-8GD#kf

[mpxlbs]

KDL 1

[mpxlbs]

KDL 2

[mpxlbs]

Good news is that it gets me into KDL now(white screen) using hrev52809 .

I've added two images which shows the KDL errors.

Using fail safe video driver gets me into desktop. Before, using the native driver it would only result in signal lost on monitor and computer had frozen.

The first image fails to show what happens when I press enter, and that is that app server crashed (80)

[waddlesplash]

The app_server crash is known; that just means the radeon_hd driver failed to initialize and didn't bail out properly. So it seems there is something we don't expect about your hardware.

[mpxlbs]

At least I get some output, so something good has changed. What more info can I provide?

[mpxlbs]

Using hrev52860 , there are no changes.

[kallisti5]

Replying to waddlesplash:

The app_server crash is known; that just means the radeon_hd driver failed to initialize and didn't bail out properly. So it seems there is something we don't expect about your hardware.

Fun fact: Any graphics driver that attempts to bail out results in the app_server crashing :-)

You can try to type continue in the accelerant crash to see if you can get a bit further.

I don't have any Vega cards to test... donations welcome! :P

[mpxlbs]

Replying to kallisti5:

Replying to waddlesplash:

The app_server crash is known; that just means the radeon_hd driver failed to initialize and didn't bail out properly. So it seems there is something we don't expect about your hardware.

Fun fact: Any graphics driver that attempts to bail out results in the app_server crashing :-)

You can try to type continue in the accelerant crash to see if you can get a bit further.

I don't have any Vega cards to test... donations welcome! :P

The second image I've attached originally happens after I type continue.

Is there any more information I can give you kallisti5 ?

I don't know how driver development works, but I know that ever since I managed to get an output after a certain hrev (white kdl screen instead of black screen with no output on monitor), it sets it at the default 2560x1440 resolution, so it seems like it is able at least to get information out to the display. I don't know if you need to add the model number, or if I can provide you with any more hardware info then I already have provided.

I'm sorry also, but this is my primary card, and if I had a second I'd be more than willing to donate.

[mpxlbs]

Haiku R1 Beta 2.

No changes.

[mpxlbs]

hrev54408 which included ​https://git.haiku-os.org/haiku/commit/?id=3853f36288165ebacc3eb3004063b91cdf69d969 .

No change.