The GPU chip on my motherboard died, and so I plugged in a cheap
video card, a maxsun AMD Radeon R5 220 2GB Graphics Card. As the
result my resolution is locked at 1024 x 768, which makes work
very difficult.

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024x768 76.00*

The graphics card supports my desired resolution of 1920x1080, but it
is not accessible.

The module is loaded:

$ lsmod
...
video 65536 2 amdgpu,radeon

I tried several things:

I put the statement xrandr --output HDMI-1 --mode 1920x1080
in my .Xresources file.

I have modified the line in /etc/default/grub to be
GRUB_CMDLINE_LINUX_DEFAULT="quiet i915.alpha_support=1"

I uncommented this line /etc/default/grub and changed it so
GRUB_FXMODE=1920x1080

I have several questions

Is there something in BIOS I need to change with the switch to
a graphics card. I didn't see it.

Was my choice of card unwise? Is buying a new and better card
a good idea?

What inexpensive Intel or Radeon card can someone recommend that
is known to work?

--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Haines Brown wrote:

The GPU chip on my motherboard died, and so I plugged in a cheap
video card, a maxsun AMD Radeon R5 220 2GB Graphics Card. As the
result my resolution is locked at 1024 x 768, which makes work
very difficult.

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
1024x768 76.00*

The graphics card supports my desired resolution of 1920x1080, but it
is not accessible.

The module is loaded:

$ lsmod
...
video 65536 2 amdgpu,radeon

Go look in your logs.

I have, in /var/log/Xorg.0.log:

[ 15.416] (II) AMDGPU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 15.416] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card0
[ 15.416] (--) AMDGPU(0): Chipset: "AMD Radeon RX 580 2048SP" (ChipID = 0x6fdf)

and so on.

I suspect your system is not actually loading the AMDGPU driver
into Xorg, and solving that will solve your problem.

-dsr-

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sun, Mar 15, 2026 at 07:23:31AM -0400, Dan Ritter wrote:

Haines Brown wrote:

The GPU chip on my motherboard died, and so I plugged in a cheap
video card, a maxsun AMD Radeon R5 220 2GB Graphics Card. As the
result my resolution is locked at 1024 x 768, which makes work
very difficult.

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm
1024x768 76.00*

The graphics card supports my desired resolution of 1920x1080, but it
is not accessible.

The module is loaded:

$ lsmod
...
video 65536 2 amdgpu,radeon

Go look in your logs.

There is no screen section. I find that the log file has no mention of AMDGPU. It does have

114.498] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
114.499] (==) No Layout section. Using the first Screen section.
114.499] (==) No screen section available. Using defaults.
114.499] (**) |-->Screen "Default Screen Section" (0)
114.499] (**) | |-->Monitor "<default monitor>"
114.499] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
...
114.667] (II) LoadModule: "radeon"
114.667] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so

114.670] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
ATI Radeon Mobility X600 (M24), ATI FireMV 2400,
ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL,
...

This starts a very long list of drivers. None have "220" in their name.

The log continues with

114.670] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
114.670] (II) FBDEV: driver for framebuffer: fbdev
114.670] (II) VESA: driver for VESA chipsets: vesa
114.670] (II) [KMS] drm report modesetting isn't supported.
114.670] (EE) open /dev/dri/card0: No such file or directory
114.670] (WW) Falling back to old probe method for modesetting
114.670] (EE) open /dev/dri/card0: No such file or directory
114.670] (II) Loading sub module "fbdevhw"
...
114.671] ABI class: X.Org Video Driver, version 25.2
114.671] (EE) Unable to find a valid framebuffer device
114.671] (WW) Falling back to old probe method for fbdev
...
114.671] (II) FBDEV(3): using default device
114.671] vesa: Refusing to run on UEFI
114.671] (EE) Screen 0 deleted because of no matching config section.
114.671] (II) UnloadModule: "radeon"
114.671] (EE) Screen 0 deleted because of no matching config section.
114.671] (II) UnloadModule: "modesetting"
114.671] (EE) Screen 0 deleted because of no matching config section.
114.671] (II) UnloadModule: "fbdev"
114.671] (II) UnloadSubModule: "fbdevhw"
114.671] (II) FBDEV(0): Creating default Display subsection in Screen secti>
"Default Screen Section" for depth/fbbpp 24/32
114.671] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32

I don't understand much of this, but no evidence that the AMDGPU drive
is being loaded. I find that /dev/ does not have a /dri subdirectory. On
a working machine it is present and holds card0 and other files. Scree
secion does not exist.

--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sun, 15 Mar 2026 at 13:40, Haines Brown <haines@histomat.net> wrote:

On Sun, Mar 15, 2026 at 07:23:31AM -0400, Dan Ritter wrote:

Haines Brown wrote:

The GPU chip on my motherboard died, and so I plugged in a cheap
video card, a maxsun AMD Radeon R5 220 2GB Graphics Card. As the
result my resolution is locked at 1024 x 768, which makes work
very difficult.

[...]

The graphics card supports my desired resolution of 1920x1080, but it
is not accessible.

[...]

Go look in your logs.

You are not looking in enough of the right places. See my comments below.

There is no screen section. I find that the log file has no mention of AMDGPU. It does have

114.498] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
114.499] (==) No Layout section. Using the first Screen section.
114.499] (==) No screen section available. Using defaults.
114.499] (**) |-->Screen "Default Screen Section" (0)
114.499] (**) | |-->Monitor "<default monitor>"
114.499] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
...
114.667] (II) LoadModule: "radeon"
114.667] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so

114.670] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
ATI Radeon Mobility X600 (M24), ATI FireMV 2400,
ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL,
...

This starts a very long list of drivers. None have "220" in their name.

The log continues with

114.670] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
114.670] (II) FBDEV: driver for framebuffer: fbdev
114.670] (II) VESA: driver for VESA chipsets: vesa
114.670] (II) [KMS] drm report modesetting isn't supported.
114.670] (EE) open /dev/dri/card0: No such file or directory
114.670] (WW) Falling back to old probe method for modesetting
114.670] (EE) open /dev/dri/card0: No such file or directory
114.670] (II) Loading sub module "fbdevhw"
...
114.671] ABI class: X.Org Video Driver, version 25.2
114.671] (EE) Unable to find a valid framebuffer device
114.671] (WW) Falling back to old probe method for fbdev
...
114.671] (II) FBDEV(3): using default device
114.671] vesa: Refusing to run on UEFI
114.671] (EE) Screen 0 deleted because of no matching config section.
114.671] (II) UnloadModule: "radeon"
114.671] (EE) Screen 0 deleted because of no matching config section.
114.671] (II) UnloadModule: "modesetting"
114.671] (EE) Screen 0 deleted because of no matching config section.
114.671] (II) UnloadModule: "fbdev"
114.671] (II) UnloadSubModule: "fbdevhw"
114.671] (II) FBDEV(0): Creating default Display subsection in Screen secti>
"Default Screen Section" for depth/fbbpp 24/32
114.671] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32

I don't understand much of this, but no evidence that the AMDGPU drive
is being loaded. I find that /dev/ does not have a /dri subdirectory. On
a working machine it is present and holds card0 and other files. Scree
secion does not exist.

Hi, I am not an expert in any of this, particularly the ridiculous rabbit
hole of AMD marketing.

However I did enough research to get a different ancient AMD graphics card
to work on Debian 12. Following a similar path for yours finds this:

[1] says about the "Radeon 200 series":
TeraScale 2 (VLIW5) (Northern Islands or Evergreen) is found on R5 235X
and below branded products.

It appears that your "R5 220" is one of these "below branded" products, according to the "Cards" list at [1].

[2] says about the "Terascale" products:
The "successor" of this technology is "Graphics Core Next 1" aka GCN1.

So it seems that your card is not newer than GCN 1.2, because it is
"succeeded" by (ie before) GCN1.

[3] says about Debian packages:
xserver-xorg-video-amdgpu package [...] will officially cover any cards
that are part of GCN 1.2 ("GCN 3rd generation") or newer.

This suggests that you do NOT need the xserver-xorg-video-amdgpu
package.

[3] says about Debian packages:
Support for GCN 1.1 and older chips is also provided by the
xserver-xorg-video-ati driver wrapper package, which depends on three
hardware-specific driver packages:
xserver-xorg-video-mach64
xserver-xorg-video-r128
xserver-xorg-video-radeon"

This suggests that you need the xserver-xorg-video-ati package installed.

Do you have that?

These commands give useful information:

$ apt list --installed 'xserver-xorg-video-*'

$ sudo dmesg | grep -iE 'amdgpu|drm|radeon'

$ inxi -GxxSM -y1

Links:
[1] https://en.wikipedia.org/wiki/Radeon_200_series
[2] https://en.wikipedia.org/wiki/TeraScale_(microarchitecture)#TeraScale_2
[3] https://wiki.debian.org/AtiHowTo#Drivers says:

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sun, Mar 15, 2026 at 09:12:52PM +0000, David wrote:

On Sun, 15 Mar 2026 at 13:40, Haines Brown <haines@histomat.net> wrote:

On Sun, Mar 15, 2026 at 07:23:31AM -0400, Dan Ritter wrote:

Haines Brown wrote:

The graphics card supports my desired resolution of 1920x1080, but it is not accessible.

Hi, I am not an expert in any of this, particularly the ridiculous rabbit hole of AMD marketing.

I had no idea this kind of information is available in Wikipedia.

So it seems that your card is not newer than GCN 1.2, because it is "succeeded" by (ie before) GCN1.

[3] says about Debian packages:
xserver-xorg-video-amdgpu package [...] will officially cover any cards
that are part of GCN 1.2 ("GCN 3rd generation") or newer.

This suggests that you do NOT need the xserver-xorg-video-amdgpu
package.

Are you saying that the needed driver is provided by the xserver-xorg-video-amdgpu package and do I do not need to install
it. Indeed, it was istalled automatically in my system.

[3] says about Debian packages:
Support for GCN 1.1 and older chips is also provided by the
xserver-xorg-video-ati driver wrapper package, which depends on three
hardware-specific driver packages:
xserver-xorg-video-mach64
xserver-xorg-video-r128
xserver-xorg-video-radeon"

This suggests that you need the xserver-xorg-video-ati package installed.

Do you have that?

I do have both the xserver-xorg-video-amdgpu and
xserver-xorg-video-ati packages installed.

These commands give useful information:

$ apt list --installed 'xserver-xorg-video-*
Yes both are installed]

$ sudo dmesg | grep -iE 'amdgpu|drm|radeon'
[ 52.384303] ACPI: bus type drm_connector registered
[ 52.592481] [drm] radeon kernel modesetting enabled.
[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesettin>
[ 53.380213] [drm] amdgpu kernel modesetting enabled.
[ 53.380256] amdgpu: CRAT table not found
[ 53.380257] amdgpu: Virtual CRAT table created for CPU
[ 53.380264] amdgpu: Topology: Add CPU node

Does this suggest that the radeon driver unable to the resolution
but it was set by the amdgpu?

$ inxi -GxxSM -y1
$ inxi -GxxSM -y1
System:
Host: Iskra
Kernel: 6.1.0-44-amd64
arch: x86_64
bits: 64
compiler: gcc
v: 12.2.0
Desktop: Fluxbox
v: 1.3.5
dm: startx
Distro: Devuan GNU/Linux 5 (daedalus)

Machine:
Type: Desktop
Mobo: Gigabyte
model: Z590 AORUS ELITE AX
v: x.x
serial: <superuser required>
UEFI: American Megatrends LLC.
v: F4
date: 03/16/2021

Graphics:
Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
vendor: Hightech Information System
driver: N/A
arch: TeraScale-2
pcie:
speed: 2.5 GT/s
lanes: 4
bus-ID: 06:00.0
chip-ID: 1002:68f9
Device-2: Sunplus Innovation USB Camera
type: USB
driver: snd-usb-audio,uvcvideo
bus-ID: 1-10.1.4.4:36
chip-ID: 1bcf:28c4
Display:
server: X.Org
v: 1.21.1.7
driver:
X:
loaded: vesa
unloaded: fbdev,modesetting,radeon
dri: swrast
gpu: N/A
display-ID: :0.0
screens: 1
Screen-1: 0
s-res: 1024x768
s-dpi: 96
Monitor-1: default
res: 1024x768
size: N/A
API: OpenGL
v: 4.5 Mesa 22.3.6
renderer: llvmpipe (LLVM 15.0.6 256 bits)
direct-render: Yes

Does this say that the radeon driver is unloaded because the
vesa driver already loaded?

I find that the he VESA driver supports most graphics cards
without acceleration and at display resolutions limited to a set
programmed in the Video BIOS by the manufacturer.

What is Video BIOS? Part of my BIOS? Does this mean resolutions
available are set in my BIOS?

Does the statement resolution:
2024x768 mean it is current or is the only available one?

--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, 16 Mar 2026 at 10:01, Haines Brown <haines@histomat.net> wrote:

[...]

Hi, thanks for providing the info requested, that's really helpful.

I'm not the best person to answer your questions because I have never
needed to take much interest in graphics card technology, so I expect that
I'm quite ignorant of it relative to many readers of this list.

So my contribution here is limited to trying to help you provide
information that might allow someone else to give you informed answers.

We have at least definitely indentified the card that you have. These lines from the 'inxi' output you provided:

Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
vendor: Hightech Information System
arch: TeraScale-2

plus that you wrote previously that you have a:

AMD Radeon R5 220 2GB Graphics Card

confirm that you have a:

Radeon R5 220 card released 21 December 2013 [1]

which uses:

Terascale 2 40nm GPU which dates from September 2009 [2]

which is why your card was a "low end" (ie budget) model when it was
released, because it was AMD's way of selling off stock of a GPU which was "old" at the time the card was released.

Are you saying that the needed driver is provided by the xserver-xorg-video-amdgpu package and do I do not need to install it.
Indeed, it was istalled automatically in my system.

All I can do is point you to the Debian wiki [3] that I mentioned
previously, which says that you don't need xserver-xorg-video-amdgpu, and
you do need xserver-xorg-video-ati, which you have shown that you have installed.

In the information that you showed, I would be very concerned about this:

[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesettin>

That error message has been truncated. What does the full message say?

Because I wonder if it says something like:
"radeon kernel modesetting ... requires firmware-amd-graphics"

So can you please show the output of:

$ apt list --installed 'firmware-amd-*'

And if firmware-amd-graphics package is not installed, can you try
installing it and see if that fixes your issue.

If it does not, then I am out of ideas and hopefully someone else will
be able to further assist you.

The firmware-amd-graphics package is provided by Debian in the non-free-firmware repository.

Also, in your 'inxi' output, these lines are bad:

loaded: vesa
unloaded: fbdev,modesetting,radeon

because you need the radeon driver to be loaded !!

Does the statement resolution:
2024x768 mean it is current or is the only available one?

You have 1024x768 as the current resolution because that is the maximum provided by the vesa driver, which is currently the only working driver,
and in use. To get the higher resolution that your card is capable of, you
need to get the radeon driver working.

Links:
[1] https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units
[2] https://en.wikipedia.org/wiki/TeraScale_(microarchitecture)#TeraScale_2_(VLIW5)
[3] https://wiki.debian.org/AtiHowTo#Drivers

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, Mar 16, 2026 at 11:15:46AM +0000, David wrote:

On Mon, 16 Mar 2026 at 10:01, Haines Brown <haines@histomat.net> wrote:

[...]

We have at least definitely indentified the card that you have. These lines from the 'inxi' output you provided:

Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
vendor: Hightech Information System
arch: TeraScale-2

plus that you wrote previously that you have a:

AMD Radeon R5 220 2GB Graphics Card

confirm that you have a:

Radeon R5 220 card released 21 December 2013 [1]

A little hard to do. With my low resolution can see only a portion
of the web page. I dig a little and find:

Radeon R5 220 (Caicos Pro) December 21, 2013 OEM

In the information that you showed, I would be very concerned about this:

[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesettin>

That error message has been truncated. What does the full message say?

Sorry about that. It is:

[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon
kernel modesetting for R600 or later requires firmware installed

Because I wonder if it says something like:
"radeon kernel modesetting ... requires firmware-amd-graphics"

So can you please show the output of:

$ apt list --installed 'firmware-amd-*'

This only returned: Listing... Done.

I find that firmware-amd-graphics package is not installed.

I installed it, but get:

...
Setting up firmware-amd-graphics (20230210-5) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-44-amd64
W: initramfs-tools configuration sets RESUME=UUID=cbdfa8a6-a127-4139-96dc-60ef57dd121a
W: but no matching swap device is available.

Does "swp device" refer to swap area? I definitively created it
when partitioning. However, the partition table ended up with two swap spaces. One is on an inactive drive witn the UUID mentioned above and
the other on my currently active drive, although the partitioner
gave it a different UUID than shows up when I run # blkid on
the partition.

However, I can't imagine how this would be relevant to my problem.

And if firmware-amd-graphics package is not installed, can you try
installing it and see if that fixes your issue.

I now install it.

If it does not, then I am out of ideas and hopefully someone else will
be able to further assist you.

The firmware-amd-graphics package is provided by Debian in the non-free-firmware repository.

My sources.list has: contrib non-free non-free-firmware and so it
should have been installed. But the description of the package
says it is not automatically installed.

Also, in your 'inxi' output, these lines are bad:

loaded: vesa
unloaded: fbdev,modesetting,radeon

because you need the radeon driver to be loaded !!

Does the statement resolution:
2024x768 mean it is current or is the only available one?

You have 1024x768 as the current resolution because that is the maximum provided by the vesa driver, which is currently the only working driver,
and in use. To get the higher resolution that your card is capable of, you need to get the radeon driver working.

Understood. As I suspected. I'll reboot as soon as I can take a
break from work to see if installing the firmware-amd-graphics
package made a difference.


--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, Mar 16, 2026 at 08:41:40AM -0400, Haines Brown wrote:

On Mon, Mar 16, 2026 at 11:15:46AM +0000, David wrote:

On Mon, 16 Mar 2026 at 10:01, Haines Brown <haines@histomat.net> wrote:

[...]

We have at least definitely indentified the card that you have. These lines from the 'inxi' output you provided:

Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
vendor: Hightech Information System
arch: TeraScale-2

plus that you wrote previously that you have a:

AMD Radeon R5 220 2GB Graphics Card

confirm that you have a:

Radeon R5 220 card released 21 December 2013 [1]

A little hard to do. With my low resolution can see only a portion
of the web page. I dig a little and find:

Radeon R5 220 (Caicos Pro) December 21, 2013 OEM

In the information that you showed, I would be very concerned about this:

[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesettin>

That error message has been truncated. What does the full message say?

Sorry about that. It is:

[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon
kernel modesetting for R600 or later requires firmware installed

Because I wonder if it says something like:
"radeon kernel modesetting ... requires firmware-amd-graphics"

So can you please show the output of:

$ apt list --installed 'firmware-amd-*'

This only returned: Listing... Done.

I find that firmware-amd-graphics package is not installed.

I installed it, but get:

...
Setting up firmware-amd-graphics (20230210-5) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-44-amd64
W: initramfs-tools configuration sets RESUME=UUID=cbdfa8a6-a127-4139-96dc-60ef57dd121a
W: but no matching swap device is available.

Does "swp device" refer to swap area? I definitively created it
when partitioning. However, the partition table ended up with two swap spaces.
One is on an inactive drive witn the UUID mentioned above and
the other on my currently active drive, although the partitioner
gave it a different UUID than shows up when I run # blkid on
the partition.

However, I can't imagine how this would be relevant to my problem.

And if firmware-amd-graphics package is not installed, can you try installing it and see if that fixes your issue.

I now install it.

It solved the proben thanks to your suggestion. When I reboot I come up
with the resolution I want.

As you indicate, the need for this driver is documented, but it helps
to know where to look. Thank you for your duidance.qq


--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, Mar 16, 2026 at 06:00:35AM -0400, Haines Brown wrote:

On Sun, Mar 15, 2026 at 09:12:52PM +0000, David wrote:

On Sun, 15 Mar 2026 at 13:40, Haines Brown <haines@histomat.net> wrote:

On Sun, Mar 15, 2026 at 07:23:31AM -0400, Dan Ritter wrote:

Haines Brown wrote:

The graphics card supports my desired resolution of 1920x1080, but it is not accessible.

This suggests that you need the xserver-xorg-video-ati package installed.

Do you have that?

I do have both the xserver-xorg-video-amdgpu and
xserver-xorg-video-ati packages installed.

These commands give useful information:

$ apt list --installed 'xserver-xorg-video-*
Yes both are installed]

$ sudo dmesg | grep -iE 'amdgpu|drm|radeon'
[ 52.384303] ACPI: bus type drm_connector registered
[ 52.592481] [drm] radeon kernel modesetting enabled.
[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesettin>
[ 53.380213] [drm] amdgpu kernel modesetting enabled.
[ 53.380256] amdgpu: CRAT table not found
[ 53.380257] amdgpu: Virtual CRAT table created for CPU
[ 53.380264] amdgpu: Topology: Add CPU node

Does this suggest that the radeon driver unable to the resolution
but it was set by the amdgpu?

$ inxi -GxxSM -y1
$ inxi -GxxSM -y1
System:
Host: Iskra
Kernel: 6.1.0-44-amd64
arch: x86_64
bits: 64
compiler: gcc
v: 12.2.0
Desktop: Fluxbox
v: 1.3.5
dm: startx
Distro: Devuan GNU/Linux 5 (daedalus)

Very glad that we were able to solve your problem. Unfortunately, Devuan
is off-topic for this list - see the monthly FAQ which explains that we
may be unable to support Debian derviatives because they do things
differently. Our support for anything other than Debian is necessarily
best efforts only and may be very wrong.

See https://www.devuan.org/os/contact for dedicated Devuan information.

I'd suggest the DNG mailing list for the future.

All the very best, as ever,

Andy Cater
(amacater@debian.org)

Does the statement resolution:
2024x768 mean it is current or is the only available one?

--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, 16 Mar 2026 at 17:30, Haines Brown <haines@histomat.net> wrote:

On Mon, Mar 16, 2026 at 08:41:40AM -0400, Haines Brown wrote:

On Mon, Mar 16, 2026 at 11:15:46AM +0000, David wrote:

[ 52.592548] [drm:radeon_pci_probe [radeon]] *ERROR* radeon
kernel modesetting for R600 or later requires firmware installed

Because I wonder if it says something like:
"radeon kernel modesetting ... requires firmware-amd-graphics"

So can you please show the output of:

$ apt list --installed 'firmware-amd-*'

This only returned: Listing... Done.

I find that firmware-amd-graphics package is not installed.

I installed it, but get:

Setting up firmware-amd-graphics (20230210-5) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-44-amd64
W: initramfs-tools configuration sets RESUME=UUID=cbdfa8a6-a127-4139-96dc-60ef57dd121a
W: but no matching swap device is available.

Not a big problem, W is just a warning. You could try to fix it by
editing /etc/initramfs-tools/conf.d/resume so that the line:
RESUME=UUID=cbdfa8a6-a127-4139-96dc-60ef57dd121a
becomes two lines:
# RESUME=UUID=cbdfa8a6-a127-4139-96dc-60ef57dd121a
RESUME=none
and then run:
$ sudo update-initramfs -uk all

[...]

And if firmware-amd-graphics package is not installed, can you try installing it and see if that fixes your issue.

I now install it.

It solved the proben thanks to your suggestion. When I reboot I come up
with the resolution I want.

Thanks for letting us know that your problem is solved.

By the way, because your graphics card is quite old you might experience
some applications that expect modern GPU features might not function correctly.

For example if you experience firefox crashing, you can check my advice at [1].

[1] https://lists.debian.org/debian-user/2025/10/msg00148.html
[1] message-id: CAMPXz=pxVzaw8_X_goZGB7vftUjO3ps8zDsVvtGjut4GqfNW3g@mail.gmail.com

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

In a new installatoin, when printing with lpr the output is
landscape when it should be portrait.

Both of the following commands print landscape.

$ lpr -o landscape <file>
$ lpr -o portrait <file>

The -o option works

$ lpr -o orientation-requested=1 <file> prints portrait
$ lpr -o orientation-requested=2 <file> prints landscape
$ lpr -o orientation-requested=3 <file> prints portrait
$ lpr -o orientation-requested=4 <file> prints landscape

When I print a file opened with emacs by means of Ctl-p, the
result is landscape when it should be portrait.

When CUPS prints its test page, it is normal (portrait)

The operating system is a fresh install and so drivers?are up to
date.

I do:

$ lpoptions -p HP_LaserJet_Pro_M428f_M429f_8264A8 -o orientation-requested=portrait

This has no effect on the operation of lpr

--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

In a new installation, when printing with lpr the output is
landscape when it should be portrait.

When CUPS prints its test page, it is normal (portrait)

The -o option works

$ lpr -o orientation-requested=3 <file> prints portrait
$ lpr -o orientation-requested=4 <file> prints landscape

When I print a file opened with emacs by means of Ctl-p, the
result is landscape when it should be portrait.

The operating system is a fresh install and so drivers?are up to
date.

I do:

$ lpoptions -p HP_LaserJet_Pro_M428f_M429f_8264A8 -o
orientation-requested=portrait

This has no effect on the operation of lpr


--

Haines Brown

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)