drm2 deprecation in base: problems with gpu-firmware-kmod port
Niclas Zeising
zeising+freebsd at daemonic.se
Wed Aug 29 11:55:55 UTC 2018
On 08/29/18 14:09, Alexey Dokuchaev wrote:
> Hi there,
>
> I've tried the kernel after drm2 bits were removed from the base to see
> how they would be served by the ports. This is on -CURRENT/i386 with
> Radeon HD 4350/4550 (RV710) gfx card. I've installed gpu-firmware-kmod
> and drm-legacy-kmod ports, and rebooted into new kernel. I don't use
> kld_list="..." and only load a few modules from /boot/loader.conf, like
> HDD controller and sound drivers, nothing gfx-related.
>
> First thing I do after console login is "kldload radeonkms", had always
> worked like a charm. Now it's broken:
>
> ...
> info: [drm] radeon: 512M of VRAM memory ready
> info: [drm] radeon: 512M of GTT memory ready.
> info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> info: [drm] Driver supports precise vblank timestamp query.
> info: [drm] MSI enabled 1 message(s)
> drmn0: info: radeon: using MSI.
> info: [drm] radeon: irq initialized.
> info: [drm] GART: num cpu pages 131072, num gpu pages 131072
> info: [drm] probing gen 2 caps for device 8086:2e31 = 1/0
> info: [drm] Loading RV710 Microcode
> radeonkmsfw_RV710_pfp: could not load firmware image, error 2
> error: [drm:pid16419:r600_init_microcode] *ERROR* r600_cp: Failed to load firmware "radeonkmsfw_RV710_pfp"
> error: [drm:pid16419:rv770_startup] *ERROR* Failed to load firmware!
> drmn0: error: disabling GPU acceleration
> drmn0: warning: 0x18b7d200 unpin not necessary
> drmn0: warning: 0x18b7d200 unpin not necessary
> error: [drm:pid16419:rv770_init] *ERROR* radeon: ucode required for R600+.
> drmn0: error: Fatal error during GPU init
>
> I have this file with the previous kernel (when it all was in the base):
>
> /boot/kernel.june/radeonkmsfw_RV710_pfp.ko (11908 bytes).
>
> With the drm2/firmware bits served from ports, the name is different:
>
> $ pkg info -l gpu-firmware-kmod | grep RV710_pfp
> /boot/modules/radeon_RV710_pfp_bin.ko
>
> File size is also different: 10428 bytes. How shall I proceed from this
> point to get things back in working order? Thanks,
The size difference is probably due to the firmware having been updated.
I have to check this though, to be sure.
What happens if you rename the new firmware (the one currently in
/boot/modules/) to the old name? Does everything load fine then?
Regards
--
Niclas
More information about the freebsd-x11
mailing list