Solved ASUS laptop AMD Radeon R7

Hello forum,

today i decided to finally install FreeBSD on my Windows 10 ASUS laptop. I am using my sons computer to type this message because i cannot get xorg working. Is someone able to offer advice? I cannot get xorg to load. First it complains about the Framebuffer mode, then after a Device is specified, then it cannot find a screen.

To my knowledge, i am supposed to install drm-kmod. I have done that. I have seen it suggested to install xf86-video-xxx as well, so i chose xf86-video-ati to install for radeon. I cannot manually load radeonkms because FreeBSD complains about a type mismatch. So i currently have no graphics support. Is drm-kmod correct for this system?

pciconf -lv | grep -B3 display
vgapci0 pci0:0:1:0
device 'Wani [Radeon R5/R6/R7 Graphic]'
class 'display'

I have no experience with this process because the VirtualBox driver and additions just work and xorg loads without a need to create a xorg.conf.d entry. I'd like to get my graphics working.

Is this system and gpu not supported?
 
whenever i run fwget, the response is that i have the latest versions. The gpu-firmware-kmod-corrizo was automatically installed by FreeBSD during installation.

after i install drm-kmod, i try to load the driver but i get drm and dmabuf errors.
i uninstalled drm-kmod and decided to try drm-515-kmod.
I do not get errors whenever i try kldload radeonkms.
instead i see that the driver is already loaded.
so does this imply that i have the right driver?

i follow the instructions in the Handbook for AMD graphics.
after i kld_list="radeonkms" in the rc.conf and install drm-515-kmod, the xorg framebuffer mode disappears.
So Framebuffermode is associated with a graphics driver.
Then i am left with no screens found.

The Handbook mentions to create a 10-monitor.conf file in xorg.conf.d
the conf file should contain Section "Screen" Identifier "Screen0"
But this is where the error occurs. So it isn't finding a screen.
What command can i type to find info about the monitor attached to the laptop? maybe it isn't Screen0 but something else that needs to be entered.

I have tried to install FreeBSD on two different AMD systems. It seems to me that AMD is not well supported. I am fine with it if that is the case. I am posting to see if there is something different that i can do outside of that which is mentioned in the Handbook. I can always install Mint on my system and use FreeBSD in VirtualBox, where the Oraclke drivers work. I have no interest in using generic drivers since that it is equivalent to a VirtualBox machine.

If noone has a resolution, then i will just proceed to install Mint. I hope that AMD drivers get better in the future.

Thanks for reading.
 
okay, i'm rolling up my sleeves. I'm getting mad. I want FreeBSD on my system. I've studied this system for over a month now.

I'm going to try to make a few changes and reboot.

I'll be back...
 
pciconf -lv | grep -B3 display
vgapci0 pci0:0:1:0
device 'Wani [Radeon R5/R6/R7 Graphic]'
class 'display'
This seems to be missing something as I get:
Rich (BB code):
# pciconf -lv | grep -B3 display
vgapci0@pci0:0:2:0:     class=0x030000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x9bc8 subvendor=0x1028 subdevice=0x09a4
    vendor     = 'Intel Corporation'
    device     = 'CometLake-S GT2 [UHD Graphics 630]'
    class      = display
To my knowledge, i am supposed to install drm-kmod. I have done that. I have seen it suggested to install xf86-video-xxx as well, so i chose xf86-video-ati to install for radeon
This (edit: that is the xf86-video-ati) looks like the wrong choice; what CPU and graphics card does this laptop have?
This may help.
This, as a 'log' of my 14.2-RELEASE -> 14.3-RELEASE upgrade may help too, although with intel graphics.

You normally only need a BusID when you have multiple 'display' devices, that could be the case with your laptop.
 
The Beast is working with graphics!

I uninstalled drm-kmod and removed my xorg.conf.d files.

I installed drm-515-kmod and set kld_list="amdgpu"


xorg has started! :) now i am happy. I love this system. Goodbye Windows!

No more VirtualBox FreeBSD, no more Windows and no Linux. Today is a great day <3

ps i covered some of the screen dust with a solid color in my attached photo of my new ASUS FreeBSD system.
 

Attachments

  • TheBeast.png
    TheBeast.png
    726.8 KB · Views: 197
The Beast is working with graphics!

I uninstalled drm-kmod and removed my xorg.conf.d files.

I installed drm-515-kmod and set kld_list="amdgpu"


xorg has started! :) now i am happy. I love this system. Goodbye Windows!

No more VirtualBox FreeBSD, no more Windows and no Linux. Today is a great day <3

ps i covered some of the screen dust with a solid color in my attached photo of my new ASUS FreeBSD system.
Beautiful.
 
i want to add a note for others having this problem. I posted earlier about an older laptop that had the same problem but i remember that the radeonkms driver actually loaded using kldload radonkms (the screen changed to black then the graphics driver loaded). Xorg did not boot (no screens found).

today i had the same problem on a different system (the one in this post and the laptop that i am using to type this message from FreeBSD.)

What works for me will also work on my old laptop:
install drm-kmod or drm-515-kmod. use kldload amdgpu or radeonkms. The graphics driver is working when the screen changes to black, then returns to the shell and the text is smaller and clearer. You can simply add kld_list="amdgpu" or kld_list="radeonkms" to the rc.conf file. Adding this info in an xorg.conf.d file seems to prevent xorg from loading. I suspect that the BusID is incorrect or xorg needs more info. Either way, xorg will autodetect the driver.

Maybe this works for others having the same problems with AMD graphics.

As a side note: once i had xorg loaded, i decided to install xfce4. I loaded xfce4 and it was working. I logged out, added some packages, then reloaded xfce4. However, the screen was black in xfce4. I couldn't get xfce4 loaded again. I decided to rename the .config/xfce4 folder to xfce4. I reloaded xfce4 and it worked again. So keep this mind if you also have trouble with xfce4.

I'm going to log off now and enjoy my new FreeBSD system before bed. Goodnight :)
 
Back
Top