Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

graphics/drm-kmod: just activates one screen on 12.0 instead of both screens as on 11.2 (see local kernel hacker) #116

Open
schorsch1976 opened this issue Dec 28, 2018 · 13 comments

Comments

@schorsch1976
Copy link

I got an AMD Radeon Pitcarain GPU. It runs smoothly on 11.2-RELEASE with dual monitor. As i upgraded to freebsd 12.0-RELEASE it shows just one monitor. As i read on the notes that there is amdgpu driver for newer cards HD7000+.
The suggested amdgpu for HD7000+ shows the attached screenshot.

The radeonkms driver on 12.0 just activates one screen instead of both screens as on 11.2-RELEASE.

I took this screenshot (as i dont have a local kernel hacker)

dsc_1079

@valpackett
Copy link
Contributor

Are you booting with UEFI? Try disabling the EFI framebuffer with hw.syscons.disable=1. (That disables the display until the GPU driver gets loaded, but you can always SSH into the machine).

ring 0 test failed is one of the symptoms of the efifb conflict. (Though hw_init of IP block failed wasn't part of these reports…)

@schorsch1976
Copy link
Author

Yes, i boot UEFI. What driver should i use with pitcairn? amdgpu or radeonkms?

@valpackett
Copy link
Contributor

Both amdgpu and radeonkms support Pitcairn, try amdgpu first.

@schorsch1976
Copy link
Author

With radeonkms and hw.syscons.disable=1 just one screen gets active.
With amdgpu both screens are active but x11 is not working and i get these messages:

dsc_1083

@iotamudelta
Copy link
Member

@schorsch1976 amdgpu is the way forward, if it's supported by your GPU, I'd recommend using that. The messages should not be harmful. Can you post your Xorg.log? You will probably want to install the xf86-video-amdgpu Xorg DDX.

@schorsch1976
Copy link
Author

With amdgpu (i forgot xf86-video-amdgpu) i could logon and start x11. sddm was ok but as plasma5 started the screen was flickering at the beginning and when i moved the mouse, the cursor followed but the background was set to the background image. No menu showd up, right click showd just a black rectangle. I guess maybe OpenGL was not working.

Here is my xorg log.

Xorg.0.log

@iotamudelta
Copy link
Member

Making progress! :-) Can you also confirm that the permissions on the /dev/drm devices have group video and your user is in that group?

@schorsch1976
Copy link
Author

Yes, my user is in group video and /dev/drm is group video too.

@valpackett
Copy link
Contributor

You will probably want to install the xf86-video-amdgpu Xorg DDX

Hm, it's odd that it didn't work without it. My RX 480 worked fine with modesetting. -amdgpu only reduced screen tearing.

flickering

Plasma is apparently infamous for flickering, you can try turning on full screen repaints..

also, are you on the latest version of Mesa?

@schorsch1976
Copy link
Author

As i used amdgpu nothing changed, i used "DRI" "3" and "TearFree" "true", nothinging changed, but as i switched to "Driver "modesetting" and i removed the old ".config" folder in my home, i can work now on Plasma5 and FreeBSD 12.

I also purged the xf86-video-ati package. I am on packages / latest. I guess, this works for me now . Also works for me the amdgpu driver. The key seems to have been the old ".config" folder.

@rozle
Copy link

rozle commented Dec 30, 2018

"Yes, my user is in group video and /dev/drm is group video too."

My user is in group video but when I boot computer without /boot/modules//kld_list="radeonkms.ko" (black screen) I do not have /dev/drm. Is it normanl, please?

@schorsch1976
Copy link
Author

@rozle I guess yes, see comment 2 (after my first post)

@rozle
Copy link

rozle commented Jan 4, 2019

Yes, I saw your comment 2 but it doesn't works for me and my ring tests pass.
But I have still problem and doesn't work for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants