Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load
Package: firmware-linux-nonfree
Version: 20151018-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Whenever I boot my computer I get error messages regarding the video card's firmware.
My video card is an ASUS HD 7850 DirectCU II. I would expect from the package contents
list that the correct firmware is the Pitcairn that does appear to load properly.
Just not sure why it it is attempting to load Tahiti after loading Pitcairn.
This is the relevent section from dmesg:
[ 3.969038] radeon 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[ 3.969041] radeon 0000:01:00.0: GTT: 2048M 0x0000000080000000 - 0x00000000FFFFFFFF
[ 3.969043] [drm] Detected VRAM RAM=2048M, BAR=256M
[ 3.969045] [drm] RAM width 256bits DDR
[ 3.969132] [TTM] Zone kernel: Available graphics memory: 8231736 kiB
[ 3.969133] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 3.969135] [TTM] Initializing pool allocator
[ 3.969157] [TTM] Initializing DMA pool allocator
[ 3.969177] [drm] radeon: 2048M of VRAM memory ready
[ 3.969179] [drm] radeon: 2048M of GTT memory ready.
[ 3.969191] [drm] Loading pitcairn Microcode
[ 3.971268] systemd[1]: Started Journal Service.
[ 3.971836] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/pitcairn_pfp.bin
[ 3.973613] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/pitcairn_me.bin
[ 3.974234] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/pitcairn_ce.bin
[ 3.974896] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/pitcairn_rlc.bin
[ 3.977269] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/pitcairn_mc.bin
[ 3.978266] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/pitcairn_smc.bin
[ 3.978272] [drm] Internal thermal controller with fan control
[ 3.978339] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[ 3.987303] [drm] radeon: dpm initialized
[ 3.988553] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/TAHITI_uvd.bin
[ 3.988592] radeon 0000:01:00.0: firmware: failed to load radeon/TAHITI_vce.bin (-2)
[ 3.988638] radeon 0000:01:00.0: Direct firmware load for radeon/TAHITI_vce.bin failed with error -2
[ 3.988641] radeon 0000:01:00.0: radeon_vce: Can't load firmware "radeon/TAHITI_vce.bin"
[ 3.988687] [drm] GART: num cpu pages 524288, num gpu pages 524288
[ 3.990648] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0
[ 3.990652] [drm] PCIE gen 2 link speeds already enabled
[ 4.004520] [drm] PCIE GART of 2048M enabled (table at 0x0000000000277000).
[ 4.004677] radeon 0000:01:00.0: WB enabled
[ 4.004684] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8804296e7c00
[ 4.004689] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8804296e7c04
[ 4.004694] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8804296e7c08
[ 4.004698] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8804296e7c0c
[ 4.004701] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8804296e7c10
[ 4.005679] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90002035a18
[ 4.005682] radeon 0000:01:00.0: VCE init error (-22).
[ 4.005731] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.005733] [drm] Driver supports precise vblank timestamp query.
[ 4.005735] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[ 4.005774] radeon 0000:01:00.0: radeon: using MSI.
[ 4.005812] [drm] radeon: irq initialized.
[ 4.192571] [drm] ring test on 0 succeeded in 3 usecs
[ 4.192581] [drm] ring test on 1 succeeded in 1 usecs
[ 4.192586] [drm] ring test on 2 succeeded in 1 usecs
[ 4.192604] [drm] ring test on 3 succeeded in 8 usecs
[ 4.192613] [drm] ring test on 4 succeeded in 5 usecs
[ 4.368444] [drm] ring test on 5 succeeded in 2 usecs
[ 4.368453] [drm] UVD initialized successfully.
[ 4.368696] [drm] ib test on ring 0 succeeded in 0 usecs
[ 4.368762] [drm] ib test on ring 1 succeeded in 0 usecs
[ 4.368825] [drm] ib test on ring 2 succeeded in 0 usecs
[ 4.368873] [drm] ib test on ring 3 succeeded in 0 usecs
[ 4.368906] [drm] ib test on ring 4 succeeded in 0 usecs
* What exactly did you do (or not do) that was effective (or ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firmware-linux-nonfree depends on:
ii firmware-amd-graphics 20151018-2
ii firmware-misc-nonfree 20151018-2
Versions of packages firmware-linux-nonfree recommends:
ii amd64-microcode 2.20141028.1
ii intel-microcode 3.20150121.1
firmware-linux-nonfree suggests no packages.
-- no debconf information
Reply to: