drm-next-kmod and 11.2-RELEASE

This isn't very clear. You have downloaded /usr/src, so in src you have various directories and files.
You have downloaded ports so you have a /usr/ports/tree.
You then tried to install drm-next-kmod. As far as you can see, did it install successfully? You are using 11.2, correct?
You followed the pkg-msg, making yourself a member of the video group.
Code: 
 pw groupmod video -m scottro
Obviously, use your own user name rather than scottro. :)

In /etc/rc.conf you added the line
Code: 
 kld_list="/boot/modules/radeonkms.ko"
Did you then restart and the system failed to boot? Or startx failed to start?

Were there error messges? Anything towards the end of /var/log/Xorg.0

I have no experience with Radeon in FreeBSD since 4.x I think, so can't be that much help.
 
Yes, but I didn't add that line in /etc/rc.conf(I knew if loading amdgpu fail, i couldn't boot OS at all).
I am loading amdgpu module just from root shell
No, i didn't launch Xorg.
It fails right away after kldload amdgpu
I managed to get dmesg after I loaded amdgpu module:
Logs(In Pastebin)
 
error 2 is normal situation, firmware is getting loaded eventually.
Is it UEFI system ? I believe, syscons should be disabled with hw.syscons.disable=1 in /boot/loader.conf (You won't get screen output before driver loads)
 
Maccraft123 said:
No, it isn't UEFI
Click to expand...

Don't mix different versions/sources.
I have gotten the exact same GPU you use to work just fine in 12.x (will work fine on 11.2 too I suspect), granted it was on a Westmere/Haswell/SkyLake/KabyLake/SkyLake-X box.
First and foremost the x11-drivers/xf86-video-(blah) are not to be used with the new generation DRM kernel modules/hardware.
The graphics/drm-next-kmod (or the now-ignored graphics/drm-stable-kmod) supersede the graphics card offerings from x11-drivers xf86-video-* drivers
You will probably want something close to bleeding-edge for best results with this card.
So SVN will pretty much be required.

# svn co https://svn.freebsd.org/base/head /usr/src && # svn co https://svn.freebsd.org/ports/head /usr/ports

(in case you are using 11.2, you will want to use svn co https://svn.freebsd.org/base/release/11.2.0 /usr/src and so forth)

Next you will be doing a # make buildworld etc, followed by some beer, a dinner date with your gf, a movie and perhaps some bedroom acrobatics. Unless you are more wise and simply keep a pet cat for entertainment. Either way it will take a while to build the whole mess. This is your guide: https://www.freebsd.org/doc/handbook/makeworld.html
Rebuild the DRM modules, /usr/ports/graphics/drm-next-kmod/ # make clean install

If you square all that away, and successfully build/install/boot, you'll need to KLD load some modules for basic operation.
Adjust /etc/rc.conf to suit your needs. The kld_list="....." is the *only* way you want to do this. Leave /boot/loader.conf the hell alone! kld_list="linux linux64 amdgpu" for basic functionality. Adjust for /boot/modules/i915kms.ko (for Intel GPU) or radeonkms (for something you mistakenly stole, believing it to be a valuable trinket, from an archeology museum) as needed.

Getting AMD GPUs to work, as the plethora of guides indicate, will *only* work in BIOS mode, *not* in UEFI mode; I've had no success --ever-- with UEFI and varying AMD GPUs. The system console will need to be either SC or VT, depending on what hardware you got.
 
shkhln said:
Kernel drivers can't supersede Xorg drivers, you need both types of drivers to function. Unless you using Wayland, of course, then you don't need Xorg-anything.
Click to expand...

Nope. I'm typing from a laptop right now that only contains xorg-minimal, drm-next-kmod a few xf86-input odds & ends and *NO* xf86-video-* of any sort.
 
Interesting... Can you post your Xorg log? That might actually be the generic modesetting driver, in which case at least 3d acceleration wouldn't work.
 
shkhln said:
Interesting... Can you post your Xorg log? That might actually be the generic modesetting driver, in which case at least 3d acceleration wouldn't work.
Click to expand...
shkhln said:
Ok, I take that back. This is supposed to work as well.
Click to expand...

Behold! This is on a SkyLake Xeon E3-1275v5 workstation:

https://pastebin.com/v2wwGkwN

Note how I do not even keep vesa or scfb around. There is *no* custom xorg.conf on this machine...anywhere. Everything auto-probed & added. Unix desktop window manager-porn provided by compton (or the mummified xcompmgr).
 
Maccraft123 said:
I don't have a gf. Too lazy for for compiling everything. Worked once with graphics/drm-NEXT-kmod, then 5 days worked with it, update and BOOM don't work. I will have my computer back at 29th
Click to expand...

Of course you killed it....this is expected when you mix up versions/releases/binary pkgs/source; also why I provided the procedure in my previous message(s).
If you do *not* do a buildworld & installworld you will end up with mismatched versions of everything. If you svn only /usr/src and not /usr/ports or vice versa, you end up with mismatched fixes, patches, bugs & crashes.
I'm relatively lazy on select things as well, but doing an # svn up /usr/src & # svn up /usr/ports amounts to barely lifting fingers. Doing a buildworld & kernel takes about ~45-60 minutes on a Core i5 or i7 platform and doesn't require supervision; easily done while you have a beauty-rest. The installworld & mergemaster procedures take ~5 mins total. Followed by portmaster'ing graphics/drm-next-kmod takes another ~5mins. Boom-de-yada boom-de-yada the world is all good again!
 
I mix ports and packages all the time, and it works. Use portmaster, then get the list of ports it installs, and cancel the installation. Then install a few of those as packages, depending on if you know those packages don't interfere with the options you need.

For this, I install the package x11-servers/xorg-server, and ports under the lang category provided the latest version is available as packages, then go with portmaster the rest of the way. You can do it, if you keep track, know the pkg options don't interfere with the port options you need, and you may have to be ready to install everything if it changes, which is no different than using ports all the way.

Also, from what I realized, drm-*-kmod is for everything, and is enough for the console (when the driver is loaded through rc.conf). The driver under the xorg driver category is not used for the console, as it works on top of the kernel module and is basically for xorg.
 
sidetone said:
I mix ports and packages all the time, and it works. Use portmaster, then get the list of ports it installs, and cancel the installation. Then install a few of those as packages, depending on if you know those packages don't interfere with the options you need.

For this, I install the package x11-servers/xorg-server, and ports under the lang category provided the latest version is available as packages, then go with portmaster the rest of the way. You can do it, if you keep track, know the pkg options don't interfere with the port options you need, and you may have to be ready to install everything if it changes, which is no different than using ports all the way.

Also, from what I realized, drm-*-kmod is for everything, and is enough for the console (when the driver is loaded through rc.conf). The driver under the xorg driver category is not used for the console, as it works on top of the kernel module and is basically for xorg.
Click to expand...

Oh indeed you can mix ports/pkgs all you like...but don't expect the miracle of a binary pkg to suddenly work when kernel source is explicitly required, especially when the versions are out of sync. More of a rule-a-thumb thing to follow.
I don't even bother with any xf86-video-<name> drivers anymore these days, drm-next-kmod (in both 11.2 & 12) is sufficiently hardened for my purposes.
 
puretone said:
Oh indeed you can mix ports/pkgs all you like...but don't expect the miracle of a binary pkg to suddenly work when kernel source is explicitly required, especially when the versions are out of sync.
Click to expand...

Mixing ports and packages works to a point but you're limited to doing that with "leaf" ports that are not required by anything else. The recent change in the xproto ports is a good example where you just can't do it because those ports are required by just about any port that uses X11 graphics and if you try to mix up to date ports built by yourself with packages from the point in time before the change all hell is guaranteed to break loose.

Mixing ports and packages when there are different or conflicting options involved is a whole another level of problems.
 
puretone said:
(in case you are using 11.2, you will want to use svn co https://svn.freebsd.org/base/release/11.2.0 /usr/src and so forth)

Next you will be doing a # make buildworld etc, followed by some beer, a dinner date with your gf, a movie and perhaps some bedroom acrobatics. Unless you are more wise and simply keep a pet cat for entertainment. Either way it will take a while to build the whole mess. This is your guide: https://www.freebsd.org/doc/handbook/makeworld.html
Rebuild the DRM modules, /usr/ports/graphics/drm-next-kmod/ # make clean install

If you square all that away, and successfully build/install/boot, you'll need to KLD load some modules for basic operation.
Adjust /etc/rc.conf to suit your needs. The kld_list="....." is the *only* way you want to do this. Leave /boot/loader.conf the hell alone! kld_list="linux linux64 amdgpu" for basic functionality. Adjust for /boot/modules/i915kms.ko (for Intel GPU) or radeonkms (for something you mistakenly stole, believing it to be a valuable trinket, from an archeology museum) as needed.

Getting AMD GPUs to work, as the plethora of guides indicate, will *only* work in BIOS mode, *not* in UEFI mode; I've had no success --ever-- with UEFI and varying AMD GPUs. The system console will need to be either SC or VT, depending on what hardware you got.
Click to expand...
bmachine.jpg
SIR! I am DOING this! I have a GF & Cat. I soo want my KABINI AMD APU to start working finally!
I will serve you beer if this works! Because I make these... (See attached) only BSD. And I cant exactly fit hardware you see... The cherry wood
 
nik0tine said:
View attachment 5401
SIR! I am DOING this! I have a GF & Cat. I soo want my KABINI AMD APU to start working finally!
I will serve you beer if this works! Because I make these... (See attached) only BSD. And I cant exactly fit hardware you see... The cherry wood
Click to expand...

Some people are better multi-taskers then others when it comes to juggling gf/cat/life ;)

Good work. Kabini *should* be supported by graphics/drm-next-kmod I believe.

Side-note: your speakers reminded me of a video I saw on YouTube a while back, check it out:
 
puretone said:
(in case you are using 11.2, you will want to use svn co https://svn.freebsd.org/base/release/11.2.0 /usr/src and so forth)
Click to expand...

This is wrong, to get the release engineering branch of 11.2 with all the errata and security fixes you have to use:

svn co https://svn.freebsd.org/base/releng/11.2 /usr/src

The release/11.2.0 branch is just a snapshot (also called a tag but SVN doesn't have tags, only branches) from the time of the release is never again updated.
 
puretone said:
I don't even bother with any xf86-video-<name> drivers anymore these days, drm-next-kmod (in both 11.2 & 12) is sufficiently hardened for my purposes.
Click to expand...
I have only one box with 11-STABLE, now rebuilding. I shall try my luck without xf86-video-* and then build WM & minimal ports except firefox & palemoon. I don't understand the diference of portsnap and svn'ing.
 
You must log in or register to reply here.
Back
Top