Bug#974581: np longer able to set native resolution of Dell U3014
On Sat, Jun 19 2021 at 16:56 +01, Simon Iremonger (debian) wrote: > Dear Janusz > > linux-image-amd64 linux-headers-amd64 have now come out in version > 5.10.0-0.bpo.7 in buster-backports. > > Please confirm the issue is solved for you (or not) by using that > kernel as above, so the bug report can be prgressed or closed. Unfortunately there is no improvement. Only the console output is displayed on the external monitor. Actually I stopped using the laptop, during a quick test there was no flickering, but it appeared usually after some time. The monitor is OK because Windows uses it with no problem at the native resolution. Please note the problem seems specific to a particular model of laptop, during a quick test with a desktop the problem doesn't occur even with the default kernel. Best regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#970574: xserver-xorg-video-amdgpu: ABI changed (24.0 to 24.1) but not the dependencies
Hi, deb...@iremonger.me.uk (2021-06-19 at 1704.32 +0100): > In short, I think this bug report should now be closed unless there > is an apparent issue specifically in buster or bullseye now [??] ? Currently I have xserver-xorg-video-amdgpu 19.1.0-2 with xserver-xorg-core 2:1.20.11-1 and it keeps working (updating Sid every now and then). The issue existed for a brief time, but probably does not matter in releases if they have debs in sync. Even if they do not explicitly request a given version, the avaliable versions implicitly avoid the problem (sorry, no machines to test them, but by numbers, Buster has an older video-amdgpu package, 18.1.99+git20190207-1, and Bullseye is like Sid now). Thus I agree it can be closed. For the record, in the rare case someone hits the issue, old log also had: ---8<--- [ 144.270] (II) Module ABI versions: [ 144.270]X.Org ANSI C Emulation: 0.4 [ 144.270]X.Org Video Driver: 24.0 [ 144.270]X.Org XInput driver : 24.1 [ 144.270]X.Org Server Extension : 10.0 --->8--- Notice the 24.0. Last ones have lines like: ---8<--- [24.338] (II) Module ABI versions: [24.338]X.Org ANSI C Emulation: 0.4 [24.339]X.Org Video Driver: 24.1 [24.339]X.Org XInput driver : 24.1 [24.339]X.Org Server Extension : 10.0 ... [24.374] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so [24.380] (II) Module amdgpu: vendor="X.Org Foundation" [24.380]compiled for 1.20.9, module version = 19.1.0 [24.380]Module class: X.Org Video Driver [24.380]ABI class: X.Org Video Driver, version 24.1 --->8--- Notice the two 24.1 for video drivers. xserver-xorg-video-amdgpu's "Depends" line still lists xorg-video-abi-24, without .1. Cheers, GSR
Bug#892982: system freeze after lock screen/switched off monitors/spontaneously
I can confirm the buster-backports now offers kernel 5.10.0-0.bpo.7-amd64 .. Please test this following notes on previous bug pointer. Can the bug now be closed, if that works, or doesn't -- I don't think there is an X.org bug here. --Simon
Bug#989545: libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy
Control: reassign -1 src:llvm-toolchain-11 1:11.0.1-2 Control: affects -1 libgl1-mesa-dri Control: tags -1 patch On 2021-06-07 09:42:44 +0200, Rubin Simons wrote: > Package: libgl1-mesa-dri > Version: 20.3.4-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > I'm using a Radeon Vega Frontier Edition with a Talos Blackbird Power9 system > (ppc64le). I'm constantly running into the issue mentioned here: > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4107 > > The above issue documents an issue in mesa caused by a bug in LLVM. Yes, so let's reassign it there. llvm maintainers, please cherry pick https://github.com/llvm/llvm-project/commit/c5a1eb9b0a76 if possible. Cheers > > The issue manifests itself when using Firefox, or in Gnome, when clicking on > the top-bar, which crashes gnome-shell. Any crash always logs the following: > > EE ../src/gallium/drivers/radeonsi/si_texture.c:1727 si_texture_transfer_map > - failed to create temporary texture to hold untiled copy > LLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* > instruction violates constant bus restriction > renamable $vgpr4 = V_CNDMASK_B32_e32 32768, killed $vgpr4, implicit killed > $vcc, implicit $exec > LLVM failed to compile shader > radeonsi: can't compile a main shader part > > It would be great if the resolution mentioned in the linked mesa issue #4107 > could be applied (I think this would require recompilation with an LLVM that > has said fix and/or a more general update of the LLVM runtime?). What I > understand from the upstream report is that the issue is not isolated to > non-x86 platforms, so I would imagine any Debian Bullseye user with a Vega > based Radeon would be impacted. > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > - Install Debian Bullseye + gnome-core on a Radeon Vega based system. >* What exactly did you do (or not do) that was effective (or > ineffective)? > - Click on Gnome top-bar after login. Watch X crash. Maximize any > window. Watch X crash. >* What was the outcome of this action? > - Frequent X crashes, graphics drawing corruption in Firefox. Above log > message appears frequently in logs. >* What outcome did you expect instead? > - A working system! > > *** End of the template - remove these template lines *** > > > VGA-compatible devices on PCI bus: > -- > :03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > [AMD/ATI] Vega 10 XTX [Radeon Vega Frontier Edition] [1002:6863] > 0005:02:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED > Graphics Family [1a03:2000] (rev 41) > > Contents of /etc/X11/xorg.conf.d: > - > total 4 > -rw-r--r-- 1 root root 639 Jun 3 14:56 00-devices.conf > > /etc/modprobe.d contains no KMS configuration files. > > Kernel version (/proc/version): > --- > Linux version 5.10.0-7-powerpc64le (debian-ker...@lists.debian.org) (gcc-10 > (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) > #1 SMP Debian 5.10.40-1 (2021-05-28) > > No Xorg X server log files found. > > udev information: > - > P: > /devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10 > L: 0 > E: > DEVPATH=/devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10 > E: SUBSYSTEM=input > E: PRODUCT=0/0/0/0 > E: NAME="HDA ATI HDMI HDMI/DP,pcm=11" > E: PHYS="ALSA" > E: PROP=0 > E: EV=21 > E: SW=140 > E: MODALIAS=input:bvpe-e0,5,kramlsfw6,8, > E: USEC_INITIALIZED=5707489 > E: ID_INPUT=1 > E: ID_INPUT_SWITCH=1 > E: ID_PATH=pci-:03:00.1 > E: ID_PATH_TAG=pci-_03_00_1 > E: ID_FOR_SEAT=input-pci-_03_00_1 > E: TAGS=:seat: > E: CURRENT_TAGS=:seat: > > P: > /devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10/event10 > N: input/event10 > L: 0 > E: > DEVPATH=/devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input10/event10 > E: SUBSYSTEM=input > E: DEVNAME=/dev/input/event10 > E: MAJOR=13 > E: MINOR=74 > E: USEC_INITIALIZED=5864423 > E: ID_INPUT=1 > E: ID_INPUT_SWITCH=1 > E: ID_PATH=pci-:03:00.1 > E: ID_PATH_TAG=pci-_03_00_1 > E: LIBINPUT_DEVICE_GROUP=0/0/0:ALSA > E: TAGS=:power-switch: > E: CURRENT_TAGS=:power-switch: > > P: > /devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input5 > L: 0 > E: > DEVPATH=/devices/pci:00/:00:00.0/:01:00.0/:02:00.0/:03:00.1/sound/card0/input5 > E: SUBSYSTEM=input > E: PRODUCT=0/0/0/0 > E: NAME="HDA ATI HDMI HDMI/DP,pcm=3" > E: PHYS="ALSA" > E: PROP=0 > E: EV=21 > E: SW=140 > E: MODALIAS=input:bvpe-e0,5,kramlsfw6,8, > E: USEC_INITIALIZED=5707853 > E: ID_INPUT=1 > E: ID
Processed: Re: Bug#989545: libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy
Processing control commands: > reassign -1 src:llvm-toolchain-11 1:11.0.1-2 Bug #989545 [libgl1-mesa-dri] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Bug reassigned from package 'libgl1-mesa-dri' to 'src:llvm-toolchain-11'. No longer marked as found in versions mesa/20.3.4-1. Ignoring request to alter fixed versions of bug #989545 to the same values previously set Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Marked as found in versions llvm-toolchain-11/1:11.0.1-2. > affects -1 libgl1-mesa-dri Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Added indication that 989545 affects libgl1-mesa-dri > tags -1 patch Bug #989545 [src:llvm-toolchain-11] libgl1-mesa-dri: si_texture.c:1727 si_texture_transfer_map - failed to create temporary texture to hold untiled copy Added tag(s) patch. -- 989545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887958: marked as done (xserver-xorg-video-amdgpu: Can't start second X session)
Your message dated Sat, 19 Jun 2021 18:49:57 +0100 with message-id and subject line Re: xserver-xorg-video-amdgpu: Can't start second X session has caused the Debian Bug report #887958, regarding xserver-xorg-video-amdgpu: Can't start second X session to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 887958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-amdgpu Version: 1.4.0-1 Severity: important Dear Maintainer, I am using KDE/sddm on a shard laptop with each user working in a different X session. I start new sessions via the "Switch User" menu option, which launches a new X session on a different virtual terminal. Since the last couple of upgrades to debain/unstable (sorry can't tell you exactly how many but over several months now) I have found that instead of starting a new X session, all that happens is that my current X session crashes. The most pertinent information I can find in the log files looks like this: [ 160.555] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied [ 160.556] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Sorry if this is the wrong place to be reporting this bug, but I can't turn up any other reports that seems to match it so want to start the ball rolling. Many thanks, -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 8 -rw-r--r-- 1 root root 1505 Oct 2 04:58 70-synaptics.conf -rw-r--r-- 1 root root 131 Oct 2 04:58 90-monitor.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14) Xorg X server log files on system: -- -rw-r--r-- 1 jschultz jschultz 52041 Aug 29 2016 /home/jschultz/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 6490 Jan 22 10:37 /var/log/Xorg.1.log -rw-r--r-- 1 root root 33725 Jan 22 10:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 163.696] (--) Log file renamed from "/var/log/Xorg.pid-2881.log" to "/var/log/Xorg.0.log" [ 163.697] X.Org X Server 1.19.5 Release Date: 2017-10-12 [ 163.697] X Protocol Version 11, Revision 0 [ 163.697] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian [ 163.697] Current Operating System: Linux thinkpad 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64 [ 163.697] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-3-amd64 root=UUID=fee128e7-2efb-403d-9a62-48341dfaab91 ro [ 163.697] Build Date: 16 October 2017 12:28:38PM [ 163.697] xorg-server 2:1.19.5-1 (https://www.debian.org/support) [ 163.697] Current version of pixman: 0.34.0 [ 163.697]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 163.697] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 163.697] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 22 10:37:45 2018 [ 163.697] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 163.697] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 163.697] (==) No Layout section. Using the first Screen section. [ 163.697] (==) No screen section available. Using defaults. [ 163.697] (**) |-->Screen "Default Screen Section" (0) [ 163.697] (**) | |-->Monitor "" [ 163.698] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 163.698] (==) Automatically adding devices [ 163.698] (==) Automatically enabling devices [ 163.698] (==) Automatically adding GPU devices [ 163.698] (==) Max clients allowed: 256, resource mask: 0x1f [ 163.698] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 163.698]Entry deleted from font path. [ 163.698] (==) FontPath set to:
Bug#987388: marked as done (Crash of amdgpu on Debian 11 Bullseye)
Your message dated Sat, 19 Jun 2021 18:43:59 +0100 with message-id <726398e3-85dc-6286-d4a6-337295ab9...@iremonger.me.uk> and subject line Re: Crash of amdgpu on Debian 11 Bullseye has caused the Debian Bug report #987388, regarding Crash of amdgpu on Debian 11 Bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 987388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-amdgpu Version: 19.1.0-2 Severity: critical Hi. Today I reinstalled a machine on Debian 11 Bullseye from testing (it was on Debian 10 Buster) and I had a crash of the AMD R9 380. I could no longer change tty and Xorg was frozen, I could only move the mouse, the keyboard shortcut to reboot the kernel was not working. After manual shutdown (electrical) I found undred lines of this in syslog: Apr 22 22:36:18 maxime-pc kernel: [18427.590382] amdgpu :01:00.0: amdgpu: 3fb1172e pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.590464] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.605898] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.606010] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.609057] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.609139] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.610566] amdgpu :01:00.0: amdgpu: 03ab56e3 pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.610644] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Apr 22 22:36:18 maxime-pc kernel: [18427.644577] amdgpu :01:00.0: amdgpu: 3fb1172e pin failed Apr 22 22:36:18 maxime-pc kernel: [18427.644659] [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 [...] Apr 22 22:37:15 maxime-pc kernel: [18484.803085] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) Apr 22 22:37:15 maxime-pc kernel: [18484.803096] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) Apr 22 22:37:18 maxime-pc kernel: [18487.595072] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) Apr 22 22:37:18 maxime-pc kernel: [18487.875072] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usa ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) show-blocked-tasks(w) dump-ftrace-buffer(z) (here I was typing on the emergency kernel reboot shortcut on keyboard) I don't know what could be the reason for this. But the problem has never occurred on Debian 10 Buster. Thanks. Max. --- End Message --- --- Begin Message --- Closing bug as per Maxime's previous message, reopen if problems recur. --Simon--- End Message ---
Bug#942318: xserver-xorg-video-amdgpu: VGA output is not detected in Radeon R7 (Carrizo) only the HDMI works. Motherboard MSI A68HM-E33 v2
Julian and bug 942318, buster-backports now provides kernel 5.10.0-0.bpo.7 via the buster-backports linux-image-amd64 linux-headers-amd64 packages. Please confirm if this solves the issue for you, and close the bug. --Simon
Bug#900087: marked as done (xserver-xorg-video-amdgpu: AMD RX 550 often locks up)
Your message dated Sat, 19 Jun 2021 18:19:56 +0100 with message-id <5a534fb2-054a-f255-c820-fb7db2648...@iremonger.me.uk> and subject line Re: xserver-xorg-video-amdgpu: AMD RX 550 often locks up has caused the Debian Bug report #900087, regarding xserver-xorg-video-amdgpu: AMD RX 550 often locks up to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 900087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xorg-video-amdgpu Version: 18.0.1-1 Severity: important Dear Maintainer, The lock ups for the AMD RX 550 graphics card I have been experiencing occur on time scales of a few hours after a boot to up to a maximum of two days after a reboot. The frequency of those backups is the reason I rated the severity of this issue as "important", but, of course, feel free to classify the severity any other way you like. Those lock ups have now become so frequent (3 of them yesterday) that I am now testing my new computer by using it normally but remotely using the display of another computer. In this mode the only use of the RX 550 is to display the login prompt to a Linux console. And that non-X use is so light, I am hoping the system stays up a long time without lock ups to confirm what I have found so far that the actual lock ups only occur when X is running directly on this computer. These lock ups when X is running on this computer all freeze the X display but come in several different varieties: * I can login from another computer via ssh and execute "shutdown -r now". However, the display remains black on the subsequent POST phase unless I hit the reset button. * I cannot login from another computer with ssh, but networking is up with this computer (i.e., ping works), and I had to hit the reset button. * Not even ping works, and I had to hit the reset button. On one occasion (I have forgotten which of the 3 varieties of lock ups this was) when I hit the reset button the card still gave a black screen during the POST phase so I was concerned it had been turned into a brick. However, as a last-ditch effort to get this display working again, I tried depressing the power button for 3 seconds so the computer powered off. Then several minutes later I powered on, and the card properly displayed the POST phase again after that. Between lock-up events, the card does display with extremely high quality, e.g., The Weather Network videos of the recent Hawaii eruption. Also, the non-graphical component of this new box seems to be reliable. For example, I recently copied 0.5TB of files from my old computer to this new computer using rsync, and then checked every one of those 4 trillion bits that had been transferred by a subsequent invocation of rsync --checksum. I am pretty sure this rsync --checksum test means the Ryzen 7 1700 CPU's, its 64GB of memory, the (external) source drive, and the (internal) destination drive are all reliable. I also ran "dpkg --verify" and "dpkg --audit" on xserver-xorg-video-amdgpu and firmware-amd-graphics (this firmware package is required for the RX 550) to verify those packages had not somehow become corrupted. I also noticed the following polaris-related (the RX 550 uses the POLARIS12 chipset) messages that are retrieved by dmesg WATCHOUT! root@merlin> dmesg |grep -B3 -A3 -i polaris [ 31.637861] ata10: DUMMY [ 31.637863] ata11: SATA max UDMA/133 abar m4096@0xfe708000 port 0xfe708200 irq 69 [ 31.637865] ata12: SATA max UDMA/133 abar m4096@0xfe708000 port 0xfe708280 irq 70 [ 31.639015] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x699F 0x1043:0x0513 0xC7). [ 31.639026] [drm] register mmio base: 0xFE80 [ 31.639026] [drm] register mmio size: 262144 [ 31.639036] [drm] probing gen 2 caps for device 1022:1453 = 737903/e -- [ 31.639302] amdgpu :0a:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x [ 31.639322] ATOM BIOS: 115-C994PI0-102 [ 31.639616] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 31.639825] amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/polaris12_mc.bin [ 31.639834] amdgpu :0a:00.0: VRAM: 4096M 0x00F4 - 0x00F4 (4096M used) [ 31.639836] amdgpu :0a:00.0: GTT: 256M 0x - 0x0FFF [ 31.639840] [drm] Detected VRAM RAM=4096M, BAR=256M -- [ 31.640488] [drm] DDC: 0x4878 0x4878 0x4879 0x4879 0x487a 0x487a 0x487b 0x487b [ 31.640488] [drm] Encoders: [ 31.640489] [drm] DFP3: INTERNAL_UNIPHY [
Bug#970574: xserver-xorg-video-amdgpu: ABI changed (24.0 to 24.1) but not the dependencies
GSR, Buster now has xserver-xorg-core version 2:1.20.4-1+deb10u3 [in-between the versions you quoted] and bullseye now has a newer newer 2:1.20.11-1 version. Given the date of your bug-report, it looks like you had the old 2018 version of the xorg-xserver package even though the buster package tas been updated twice since then to 2019 and 2020 versions. See Changelog:- https://metadata.ftp-master.debian.org/changelogs//main/x/xorg-server/xorg-server_1.20.4-1+deb10u3_changelog In short, I think this bug report should now be closed unless there is an apparent issue specifically in buster or bullseye now [??] ? --Simon
Bug#974581: np longer able to set native resolution of Dell U3014
Dear Janusz linux-image-amd64 linux-headers-amd64 have now come out in version 5.10.0-0.bpo.7 in buster-backports. Please confirm the issue is solved for you (or not) by using that kernel as above, so the bug report can be prgressed or closed. --Simon
