Why is amdgpu blacklisted in loader.conf

It was this commit:

lualoader: Create a module blacklist, add DRM modules to it

This is a step in the process of easing migration into the new world order
of DRM drivers. Strongly encourage users towards loading DRM modules via
rc.conf(5) instead of loader.conf(5) by failing the load from loader(8).
Users so inclined may wipe out the blacklist via module_blacklist="" in
loader.conf(5), and it is expected that these modules will eventually be
removed from the blacklist. They may still be loaded as dependencies of
other modules or explicitly via the loader prompt, but this should not be a
major problem.
 
Maccraft123 said:
Why? I want full resolution before loading it from rc.conf
Click to expand...
It's not, what exactly do you mean with "blacklisted" anyway?

I tried looking for amdgpu and only found x11-drivers/xf86-video-amdgpu which is obviously not a kernel module and therefor not directly related. I also found /usr/local/include/libdrm/amdgpu.h, installed by graphics/libdrm, but that also doesn't trace back to a kernel module.

Then I found this thread, which hints at graphics/drm-kmod. But once again nothing directly related to FreeBSD.

So yeah, I can't help wonder if you're not mixing up OS's considering that blacklisting is a practice done in modprobe.conf which has nothing to do with FreeBSD at all.

(edit)

FreeBSD does know about ram_blacklist but that isn't enabled by default (see /boot/defaults/loader.conf) nor does FreeBSD provide a list on its own.
 
Maccraft123 said:
It is blacklisted in /boot/defaults/loader.conf. cat /boot/defaults/loader.conf | grep amdgpu
Click to expand...
Code: 
peter@zefiris:/home/peter $ grep amdgpu /boot/defaults/loader.conf 
peter@zefiris:/home/peter $ freebsd-version -ur
11.2-RELEASE
11.2-RELEASE
I'll just be unwatching this thread now.
 
And I installed it with pkg
[root@maciek /usr/home/maccraft123]# pkg search drm-devel-kmod
drm-devel-kmod-4.16.g20181027 DRM modules for the linuxkpi-based KMS components (development version)
 
Code: 
[maccraft123@maciek ~]$ grep amdgpu /boot/defaults/loader.conf
module_blacklist="drm drm2 radeonkms i915kms amdgpu"    # Loader module blacklist
[maccraft123@maciek ~]$ freebsd-version -ur
12.0-BETA3
12.0-BETA3
 
I overrided it, doesn't work.
I want to know why.
In Linux i have early KMS from initramfs.
Since these drivers are ported from Linux it should also work on FreeBSD
 
1. If override didn't work, show how exactly you are doing it.
2. If override worked, but the driver doesn't do what you expect it to do, it's totally different problem (being ported from Linux doesn't necessarily mean it will work exactly the same).
 
It has been disabled in 12.0 because of graphics/drm-next-kmod. The port provides a newer and improved version which will conflict with the one from the base. That's why the base one has been blacklisted.
 
amdgpu is a fork of the radeon/R600, etc Linux DRM drivers which supports some newer GPUs.

Maccraft123 said:
In Linux i have early KMS from initramfs.
Since these drivers are ported from Linux it should also work on FreeBSD
Click to expand...
initframfs is a "Linuxism" and an entirely separate entity to the ported Linux DRM/KMS driver code. You're conflating two separate issues.
 
I think they all blacklisted because of the stability problems with EFI during the earlier boot. Actually package and port have the related message

Code: 
amdgpu, i915, and radeon DRM modules for the linuxkpi-based KMS components.
Currently corresponding to Linux 4.11 DRM. Experimental state. amdgpu and
radeonkms are known to fail with EFI boot.
 
Maccraft123 said:
If amdgpu would be fork of radeon, it would support GCN 1.x GPUs as well as radeon driver
Click to expand...
There are plenty of forked drivers which drop support for older hardware, that's often the whole point of the fork.

amdgpu definitely seems to be a fork, lots of files with same copyright notices and dates as the equivalents within the ati/radeon source. The same developers are involved also.

(and I believe xf86-video-amdgpu was forked from xf86-video-ati as well.)

/edit: But to remove all doubt - "amdgpu is based on current upstream open source AMD Radeon kernel driver"

https://www.x.org/wiki/Events/XDC2015/Program/deucher_zhou_amdgpu.pdf
 
Junkie said:
I think they all blacklisted because of the stability problems with EFI during the earlier boot. Actually package and port have the related message
Click to expand...

I pasted the actual commit message saying *why* those were blacklisted in the first reply to this thread, there's no need to guess :)
 
Maccraft123 said:
The amdgpu driver does not exist in base
This is only graphics/drm-[devel,next]-kmod
Click to expand...

Sir Dice gave you the correct answer:
  • These modules exist both as parts of FreeBSD base (quite old versions) and in several ports, drm-stable-kmod, drm-next-kmod and drm-devel-mod, for example
  • To avoid conflicts, installing the port/package adds the blacklisting to loader.conf - otherwise, an active graphics driver would exist when the port-based modules attempt to load, which would cause them to fail
So please come back when:
  • You have learned to communicate in a more civilized fashion on the forum
  • You understand the difference between base, ports and packages
  • You learn to take the advice from acknowledged experts on the forum, like Sir Dice
 
recluce said:
To avoid conflicts, installing the port/package adds the blacklisting to loader.conf - otherwise, an active graphics driver would exist when the port-based modules attempt to load, which would cause them to fail
Click to expand...
Actually, no. According to the commit message (link) and the UPDATING entry, the DRM drivers are blacklisted in loader.conf so people are encouraged to load them from rc.conf instead. Loading them from loader.conf is deprecated because it causes problems with EFI booting.
 
You must log in or register to reply here.
Back
Top