Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load

2021-03-23 Thread maximilian attems
tags 802937 moreinfo
stop

> Several months ago I got a new case that allowed me to reinstall the 
> graphics card. The old case wasn't big enough to accommodate the card + 
> the disk drives so I used an older, shorter card.

Can you reproduce with uptodate Debian bullseye?


sorry for the late reply and thank you for your report.



Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load

2019-10-29 Thread Giuseppe V
Package: firmware-amd-graphics
Followup-For: Bug #802937

Dear Maintainer,

I installed this package and when I reboot the machine, I got a blue tinted
screen. After trying everything, I tested the gamma and when  I reset it, the
screen retourned at normal colors. However, many icons and images are still in
low quality than before.

My GPU is a Sapphire Vapor-X R9 280X

Apparently, logs shows no errors:

DMESG:

[1.124900] [drm] radeon kernel modesetting enabled.
[1.124932] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 0:
0xe000 -> 0xefff
[1.124933] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 2:
0xf000 -> 0xf003
[1.124934] radeon :01:00.0: vgaarb: deactivate vga console
[1.126929] radeon :01:00.0: VRAM: 3072M 0x -
0xBFFF (3072M used)
[1.126929] radeon :01:00.0: GTT: 2048M 0xC000 -
0x00013FFF
[1.126979] [drm] radeon: 3072M of VRAM memory ready
[1.126979] [drm] radeon: 2048M of GTT memory ready.
[1.127008] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_pfp.bin
[1.127016] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_me.bin
[1.127024] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_ce.bin
[1.127032] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_rlc.bin
[1.127044] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_mc.bin
[1.127058] radeon :01:00.0: firmware: direct-loading firmware
radeon/tahiti_smc.bin
[1.131828] [drm] radeon: dpm initialized
[1.131866] radeon :01:00.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin
[1.131887] radeon :01:00.0: firmware: direct-loading firmware
radeon/TAHITI_vce.bin
[1.141253] radeon :01:00.0: WB enabled
[1.141255] radeon :01:00.0: fence driver on ring 0 use gpu addr
0xcc00 and cpu addr 0xc77d13af
[1.141255] radeon :01:00.0: fence driver on ring 1 use gpu addr
0xcc04 and cpu addr 0x4d8e6bbe
[1.141256] radeon :01:00.0: fence driver on ring 2 use gpu addr
0xcc08 and cpu addr 0x22eaff4f
[1.141257] radeon :01:00.0: fence driver on ring 3 use gpu addr
0xcc0c and cpu addr 0x2f3acd6b
[1.141257] radeon :01:00.0: fence driver on ring 4 use gpu addr
0xcc10 and cpu addr 0x963f94c9
[1.141449] radeon :01:00.0: fence driver on ring 5 use gpu addr
0x00075a18 and cpu addr 0x568a4f9f
[1.161386] radeon :01:00.0: fence driver on ring 6 use gpu addr
0xcc18 and cpu addr 0xa913cb9c
[1.161386] radeon :01:00.0: fence driver on ring 7 use gpu addr
0xcc1c and cpu addr 0xf32f8e7d
[1.161389] radeon :01:00.0: radeon: MSI limited to 32-bit
[1.161419] radeon :01:00.0: radeon: using MSI.
[1.161433] [drm] radeon: irq initialized.
[3.412783] fbcon: radeondrmfb (fb0) is primary device
[3.455999] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[3.471042] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on
minor 0
[   22.538983] radeon_dp_aux_transfer_native: 158 callbacks suppressed

Thank you for the help




-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.135


Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load

2015-10-25 Thread Gary Dale
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 :01:00.0: VRAM: 2048M 0x - 
0x7FFF (2048M used)
[3.969041] radeon :01:00.0: GTT: 2048M 0x8000 - 
0x
[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 :01:00.0: firmware: direct-loading firmware 
radeon/pitcairn_pfp.bin
[3.973613] radeon :01:00.0: firmware: direct-loading firmware 
radeon/pitcairn_me.bin
[3.974234] radeon :01:00.0: firmware: direct-loading firmware 
radeon/pitcairn_ce.bin
[3.974896] radeon :01:00.0: firmware: direct-loading firmware 
radeon/pitcairn_rlc.bin
[3.977269] radeon :01:00.0: firmware: direct-loading firmware 
radeon/pitcairn_mc.bin
[3.978266] radeon :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 :01:00.0: firmware: direct-loading firmware 
radeon/TAHITI_uvd.bin
[3.988592] radeon :01:00.0: firmware: failed to load 
radeon/TAHITI_vce.bin (-2)
[3.988638] radeon :01:00.0: Direct firmware load for 
radeon/TAHITI_vce.bin failed with error -2
[3.988641] radeon :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 0x00277000).
[4.004677] radeon :01:00.0: WB enabled
[4.004684] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8804296e7c00
[4.004689] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0x8804296e7c04
[4.004694] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x8804296e7c08
[4.004698] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x8804296e7c0c
[4.004701] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0x8804296e7c10
[4.005679] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0xc90002035a18
[4.005682] radeon :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 :01:00.0: radeon: MSI limited to 32-bit
[4.005774] radeon :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 

Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load

2015-10-25 Thread Gary Dale

On 25/10/15 04:43 PM, Ben Hutchings wrote:

Control: reassign -1 firmware-amd-graphics 20151018-2

On Sun, 2015-10-25 at 07:36 -0400, Gary Dale wrote:

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.

The 'Tahiti' and 'Pitcairn' chips are both in the 'Southern Islands'
family and have some modules in common, so they use the same firmware
for those modules.

[...]

[3.988553] radeon :01:00.0: firmware: direct-loading firmware 
radeon/TAHITI_uvd.bin
[3.988592] radeon :01:00.0: firmware: failed to load 
radeon/TAHITI_vce.bin (-2)
[3.988638] radeon :01:00.0: Direct firmware load for 
radeon/TAHITI_vce.bin failed with error -2
[3.988641] radeon :01:00.0: radeon_vce: Can't load firmware 
"radeon/TAHITI_vce.bin"

[...]

This file certainly is included in the package, though.

Can you check the package is installed properly:
 dpkg --verify firmware-amd-graphics

When did this problem first appear?  Did you upgrade the kernel or
firmware packages?

Ben.

The dpkg --verify runs but produces no output. Same results when I try 
--audit instead. I don't know if that is expected or not.


Several months ago I got a new case that allowed me to reinstall the 
graphics card. The old case wasn't big enough to accommodate the card + 
the disk drives so I used an older, shorter card.


I'm not sure when the error started appearing. Probably when I upgraded 
to Stretch.




Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load

2015-10-25 Thread Ben Hutchings
Control: reassign -1 firmware-amd-graphics 20151018-2

On Sun, 2015-10-25 at 07:36 -0400, Gary Dale wrote:
> 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.

The 'Tahiti' and 'Pitcairn' chips are both in the 'Southern Islands'
family and have some modules in common, so they use the same firmware
for those modules.

[...]
> [3.988553] radeon :01:00.0: firmware: direct-loading firmware 
> radeon/TAHITI_uvd.bin
> [3.988592] radeon :01:00.0: firmware: failed to load 
> radeon/TAHITI_vce.bin (-2)
> [3.988638] radeon :01:00.0: Direct firmware load for 
> radeon/TAHITI_vce.bin failed with error -2
> [3.988641] radeon :01:00.0: radeon_vce: Can't load firmware 
> "radeon/TAHITI_vce.bin"
[...]

This file certainly is included in the package, though.

Can you check the package is installed properly:
    dpkg --verify firmware-amd-graphics

When did this problem first appear?  Did you upgrade the kernel or
firmware packages?

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.

signature.asc
Description: This is a digitally signed message part