[Bug 268962] graphics/drm-510-kmod: amdgpu.ko doesn't load properly from loader.conf

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268962

            Bug ID: 268962
           Summary: graphics/drm-510-kmod: amdgpu.ko doesn't load properly
                    from loader.conf
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

When I include:

amdgpu_load="YES"
amdgpu_name="/boot/modules/amdgpu.ko

in my /boot/loader.conf, it loads amdgpu.ko, and also loads drm.ko,
linuxkpi_gplv2.ko, dmabuf.ko, and ttm.ko (which I hypothesize happens because
the top Makefile specifies:

DEFAULT_KMODS=  dmabuf          \
                linuxkpi        \
                ttm             \
                drm             \
                amd             \
                radeon

But in order to work, we also need firmware for my graphics card to load, which
means amdgpu_raven_{gpu_info,sdma,asd,ta,pfp,me,ce,rlc,mec,mec2,vcn}_bin.ko
also have to be loaded in my case.  And they are, if I kldload amdgpu.ko by
hand in single-user mode or include amdgpu.ko in kld_list in my /etc/rc.conf. 
(And in that case, X windows comes up nicely using the "amdgpu" driver, whereas
otherwise it comes up in VESA mode.)

In conjunction with bug #267028, it would be nice if I could load amdgpu.ko at
/boot/loader.conf time, since loading it later on increases the chance of a
kernel crash in ZFS code.  Don't ask me why.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.