[vega] No outputs definitely connected, trying again...

[oleyska]

Tried that kernel... same negative result.
(there is no 4.12.13+ version, so i tried 4.13.6+).


Also, I just found that I forgot to say one thing: my graphic card is not Vega Frontier Edition.
It is Sapphire vega. So maybe I need different firmware?

Also, another strange message in X log:




And another question:
How can I build the dc kernel myself? (I can try to debug the driver ).

As far as I understand,

• I need a stock 4/15 kernel from kernel.org (which right now is called 4.14-rc5),
• Also I need ubuntu kernel patches (where can I get them)
• and some amd patches

Am I right?

I think installed the firmware from m-bab, for you I tested the 4.13.6+ too and it's working for me too.
I got a Sapphire Radeon RX Vega 64 Black edition so shouldn't be a problem.
Does your fan ramp down upon boot?

Also:

glxinfo | grep render

Output= ?

[tourette]

Does your fan ramp down upon boot?

Sorry, I did not understood. What does "ramp down" mean? If you are asking about fan speed then no, speed does not changes.

glxinfo | grep render

Output= ?

Can't get it, because my screen is black after boot, so I cannot login into X session.

[oleyska]

Sorry, I did not understood. What does "ramp down" mean? If you are asking about fan speed then no, speed does not changes.



Can't get it, because my screen is black after boot, so I cannot login into X session.

Sorry for late answer.

Sudo dpkg -i firmware-radeon-ucode_1.60_all.deb
sudo dpkg -i linux-Image-4.13.10+_17.10.29.AMDGPU.UBUNTU_amd64.deb
sudo dpkg -i linux-headers-4.13.10+_17.10.29.AMDGPU.UBUNTU_amd64.deb

Check \boot\grub\grub.cfg that nomodeset is not checked or during boot as a one time event.
Worked for me on ubuntu 17.10 no additional mesa repo.

[tourette]

> Sorry for late answer.
Same pls for my late reply. Was A bit away from my PC.

> Sudo dpkg -i firmware-radeon-ucode_1.60_all.deb
> sudo dpkg -i linux-Image-4.13.10+_17.10.29.AMDGPU.UBUNTU_amd64.deb
> sudo dpkg -i linux-headers-4.13.10+_17.10.29.AMDGPU.UBUNTU_amd64.deb

Not working for me
Same black screen and

> AMDGPU(0): Output HDMI-A-1 has no monitor section
> AMDGPU(0): Output HDMI-A-1 disconnected
in the log

[tourette]

Ok, after a while I decided to give a try to new driver versions with new kernels on ubuntu 17.10.
I used mbab's packages for 4.15-rc3 from https://github.com/M-Bab/linux-kernel-amdgpu-binaries/ :

firmware-radeon-ucode_1.70_all.deb
linux-headers-4.15.0-rc3+_17.12.11.AMDGPU.UBUNTU_amd64.deb
linux-image-4.15.0-rc3+_17.12.11.AMDGPU.UBUNTU_amd64.deb

Aaaand... there is some progress

1. Now I can see normal login screen with high resolution
2. But when I log in, I see only graphic trash on my screen/
3. In syslog:
> Output DisplayPort-0 connected
(I also changed cable from dvi<->hdmi to dvi<->displayport)

There are a bunch of strange gnome errors and then lots of similar amdgpu errors:

Window manager warning: "XF86RFKill" is not a valid accelerator
(WW) AMDGPU(0): flip queue failed: Device or resource busy
(WW) AMDGPU(0): Page flip failed: Device or resource busy
(EE) AMDGPU(0): present flip failed
(WW) AMDGPU(0): flip queue failed: Device or resource busy
(WW) AMDGPU(0): Page flip failed: Device or resource busy
(EE) AMDGPU(0): present flip failed
(WW) AMDGPU(0): flip queue failed: Device or resource busy
(WW) AMDGPU(0): Page flip failed: Device or resource busy
(EE) AMDGPU(0): present flip failed

So now I am totally confused.
The driver seem to work at least in some circumstances.
But sometimes something get wrong. Ormaybe it is not the driver but X?

Does anybody has an idea what should I check now?



P.S.
And could you guys explain me, where is the high-level open-source driver exactly is?
In the kernel tree? Or there is only amdgpu and I should install something (mesa?) manually?

[tourette]

Then make bug reports to the kernel or mesa bug reporting system. Developers are more interested when you test with the latest code.

I am asking here because there are some people who got the driver working.
I thought maybe I did something wriong and they can help me.
And, as far as I can understand, some of the driver devs sometimes look on this forum.

kernel or mesa bug reporting system

Do you mean https://bugzilla.kernel.org?
Why I should report bugs there if it is kernel bugzilla, not the driver's one?
Because for now the driver is a part of the kernel?

[tourette]

And a question aside from the main topic.
It seems strange that the screen works fine on login screen, but become broken when I log in.
Maybe there is a difference in X settings for that modes? How can I find out?

[tourette]

Why you care

Because.

you seem to been win virus hoover user

And you seem to be a jew.

2 months and you can not make hardware work with Linux although we help you

People tried to help me, yes, but problem was not solved. No cause of the problem was found. No additional debugging from devs.

but will not try with lightdm and Xfce

And I also not tried lxqt, kde3 and even dancing with a tambourine. I wanted to get an advise what excactly I did wrong (if i did something wrong) or some advices from devs how to debug the problem.
Unfortunately, I got nothing of that.

[puleglot]

Also, another strange message in X log:

[ 20.797] (--) AMDGPU(0): Chipset: "Unknown AMD Radeon GPU" (ChipID = [B]0x687f[/B])

You probably have an old ddx driver which lacks VEGA PCI ids.