Re: drm2 again

Niclas Zeising <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]>
On 10/31/18 10:11 PM, Johannes Lundberg wrote:
> 
> 
> On Wed, Oct 31, 2018 at 8:13 PM Steve Kargl 
> <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>     On Wed, Oct 31, 2018 at 07:56:36PM +0000, Johannes Lundberg wrote:
>      >
>      > Whenever this happens your kernel is out of sync. The best when using
>      > CURRENT is, like Niclas said, to build from source, either ports
>     or the
>      > github repo.
>      >
> 
>     It was a 6-day old kernel.  However, after rebuilding
>     and installing a new kernel; and rebuilding and installing
>     a graphics/drm-legacy-kmod, again.
> 
>     % dmesg | grep drm
>     info: [drm] Initialized drm 1.1.0 20060810
>     drmn0: <Caicos [Radeon HD 6450]> on vgapci0
>     info: [drm] RADEON_IS_PCIE
>     info: [drm] initializing kernel modesetting (CAICOS 0x1002:0x6779
>     0x1092:0x6450).
>     info: [drm] register mmio base: 0xFEA20000
>     info: [drm] register mmio size: 131072
>     info: [drm] radeon_atrm_get_bios: ===> Try ATRM...
>     info: [drm] radeon_atrm_get_bios: pci_find_class() found: 0:1:0:0,
>     vendor=1002, device=6779
>     info: [drm] radeon_atrm_get_bios: Get ACPI device handle
>     info: [drm] radeon_acpi_vfct_bios: ===> Try VFCT...
>     info: [drm] radeon_acpi_vfct_bios: Get "VFCT" ACPI table
>     info: [drm] radeon_acpi_vfct_bios: Failed to get "VFCT" table:
>     AE_NOT_FOUND
>     info: [drm] igp_read_bios_from_vram: ===> Try IGP's VRAM...
>     info: [drm] igp_read_bios_from_vram: VRAM base address: 0xc0000000
>     info: [drm] igp_read_bios_from_vram: Map address: 0xfffff800c0000000
>     (262144 bytes)
>     info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature: 0x2F07
>     info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM...
>     info: [drm] radeon_read_bios: Map address: 0xfffff800000c0000
>     (131072 bytes)
>     info: [drm] ATOM BIOS: C26401
>     drmn0: info: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
>     (1024M used)
>     drmn0: info: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF
>     info: [drm] Detected VRAM RAM=1024M, BAR=256M
>     info: [drm] RAM width 64bits DDR
>     info: [drm] radeon: 1024M 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 1002:5a16 = 2/0
>     info: [drm] enabling PCIE gen 2 link speeds, disable with
>     radeon.pcie_gen2=0
>     info: [drm] Loading CAICOS Microcode
>     error: [drm:pid109:ni_init_microcode] *ERROR* ni_cp: Failed to load
>     firmware "radeon/CAICOS_pfp.bin"
>     error: [drm:pid109:evergreen_startup] *ERROR* Failed to load firmware!
>     drmn0: error: disabling GPU acceleration
>     drmn0: warning: 0xfffff800061f8c00 unpin not necessary
>     drmn0: warning: 0xfffff800061f8c00 unpin not necessary
>     error: [drm:pid109:evergreen_init] *ERROR* radeon: MC ucode required
>     for NI+.
>     drmn0: error: Fatal error during GPU init
>     info: [drm] radeon: finishing device.
>     info: [drm] radeon: ttm finalized
>     device_attach: drmn0 attach returned 22
> 
> 
> I found some more firmware calls that were unpatched.
> Committed to: https://github.com/FreeBSDDesktop/drm-legacy
> 
> Port will be updated this evening.
> 
> Thanks for your patients.  Fingers crossed this time...
> 
> 

Port is updated with the latest change.  Make sure you have FreeBSD 
Ports r483619 or later.
Regards
-- 
Niclas
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
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.