We’ve had a few days that also hit 40 C too - but most of those are usually in late January or early February (sometimes still get 40 C days here in March too) - a week of those is a killer… thankfully this is a mediterranean climate, i.e. dry, so no “web bulb” issues here…
1 Like
It looks attractive. Our place is similar… a rural block. We enjoy the lifestyle, been here since 1998.
Can you tell me what kernel Ubuntu 22.04 is running. ?
All I know is 6.0.11-×25 works and 5.10.0-19 doesnt work with amdgpu driver
22.04 desktop :
5.15 :
Linux titan 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
22.10 Thinkpad (also AMD GPU / but vega8 on CPU die):
5.19 :
Linux fenrix 5.19.0-26-generic #27-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 23 20:44:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Thank you,
So somewbere between 5.10.0 and 5.15.0 the kernel becones capable of handling amdgpu driver module.
It is likely Debian will achieve that in its next release
BTW… did you notice, @4dandl4 knows how to tell if the graphics card is using its driver
lshw -c video
lists the driver that is in use, blank if none.
Regards
Neville
Desktop machine 22.04 :
╭─x@titan ~/MPZ/WizardRifle
╰─➤ sudo lshw -c video
*-display
description: VGA compatible controller
product: Navi 23 [Radeon RX 6600/6600 XT/6600M]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:2f:00.0
logical name: /dev/fb0
version: c7
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=amdgpu latency=0 resolution=2560,1440
resources: irq:122 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:f000(size=256) memory:fca00000-fcafffff memory:fcb00000-fcb1ffff
Thinkpad E495 22.10 :
╭─x@fenrix ~/.config
╰─➤ sudo lshw -c video
*-display
description: VGA compatible controller
product: Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:05:00.0
logical name: /dev/fb0
version: c2
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi msix vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
resources: irq:42 memory:c0000000-cfffffff memory:d0000000-d01fffff ioport:1000(size=256) memory:d0500000-d057ffff memory:c0000-dffff
I’m just about to try HoloISO (live CD first) on the Thinkpad - i.e. Arch based distro that Valve ship on their SteamDeck… Not sure what kernel… Will report back results…
Right, so both your machines are definitely using the amdgpu driver for the graphics card.
1 Like
@Akito @berninghausen @4dandl4 @daniel.m.tripp
I have the other half of the solution
Just recapping
[quote="nevj, post:32, topic:10040"]
I have a partial solution.
I have discovered that if I use the displayport outout from the amd graphics card instead of the hdmi port, the " black=pink" problem in Void and Solus completely disappears. Everything is back to normal.
That leaves Debian and Devuan. They never had the pink problem, but they both have intermittant failure to boot… the screen goes blank and says “no hdmi signal”.
In Debian and Devuan I had to load the driver modules required for the amd graphics card (that is different, Void and Solus loaded them automatically).
So I made entries in /etc/modules. There was nothing to tell me which modules to load, I guessed by looking at what Void and Solus loaded.
[/quote]
The problem of Debian and Devuan hanging intermittently during boot can be solved by
- remove the amdgpu module from /etc/modules … it does not work with old kernels.
- set the kernel boot parameter
acpi=offbefore booting… this can be done by editing on the grub menu screen, or by editing the file /boot/grub/grub.cfg
What I get is a 1920 x 1080 display controlled by the Vesa system that is part of the bios. No driver shows in the lshw output.
lshw -c video
*-display UNCLAIMED
description: VGA compatible controller
product: Advanced Micro Devices, Inc. [AMD/ATI]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
version: c7
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list
configuration: latency=0
resources: memory:c0000000-cfffffff memory:d0000000-d01fffff ioport:e000(size=256) memory:fb600000-fb6fffff memory:c0000-dffff
That was Devuan, Debian is the same.
Devuan kernel is vmlinuz-5.10.0-9-amd64… older than Debian !!
As far as I can tell visually, the display is perfectly adequate displaying a few Xfce treminal windows or Firefox or Thunderbird. That is all I need. I can afford to wait for Debian and Devuan to catch up with their kernels.
So now I have operable versions of Debian/Gnome, Devuan/Xfce, Solus/Budgie, Void/Xfce, and Void/Lumina.
There is still some issue with Void/KDE. It boots down to starting sddm and fails every time.
Will get back to that later.
Summary:
So what was it like changing graphics cards in a multiboot system with 6 Linuxes.
Well it was 6 x the work, but there are advantages in diversity… at least some of those 6 Linuxes worked with the new card straight off, so I had something to work with . I can imagine only one system and getting a blank screen would not be very edifying.
Why did I do it? My old nvidia card was unsupported and driven by a kludge. I wanted to change to AMD to get LTS. The only cards I could buy new were the AMD RX series, so I chose the smallest and cheapest one of the range, the RX6400. Way too powerful for my needs. Perhaps I should have risked an older secondhand card.
What is the outcome. Well I have Void and Solus using the card in accelerated graphics mode, and Debian and Devuan using the card in Vesa mode. I may one day get Debian and Debvian to use the amdgpu driver, when their kernels catch up.
Thanks to all
Regards
Neville
2 Likes
3.5 acres …a fantastic area for amateur radio antennas
If you are a ham : Lucky you !
Frank (Wicklowham) EI7KS
2 Likes
@nevj
Vesa mode is only loading a generic vga driver with no support for your card. So you have one out of four distros using the correct driver for your card. Why are you using distros that have no support for your card, save your data and use something else, even my Gentoo is using kernel 5.15.80.
You have already spent a good sum of cash, for a up-to-date GPU, makes no sense to not utilize an OS that supports that GPU, but it is your time and your machine. Your friend Daniel.
Déjà vu
The Matrix has a loopback.
No, 2 out of 4. Solus and Void both use correct driver
Debian and Devuan are using Vesa.
It was an experiment. I wanted to find a path away from Debian, partly because of systemd, partly from wanting more uptodate rolling release.
I chose to look at Devuan, Solus, and Void.
It is a long term trial. This graphics card episode is part if it, obviously.
I will eventually choose probably 2 distros.
My current favourite is Void
Gentoo is not out of the equation.
One of the big considerations is that one needs to have a stable distro controlling grub and running important stuff like email. So I might end up with one stable distro and one bleeding edge… your version of that is to have one stable Win and one Linux to play with.
The Debian/Devuan situation with old kernels is temporary. They will catch up next release. The Vesa driver is fine temporarily. I mostly work in Void anyway.
Do you understand ACPI? Why is it having trouble with a driverless graphics card? That might be a bug in ACPI?
There is another kernel-boot-parameter
pci=noacpi
This disables ACPI for IRQ routing and PCI scanning.
So I may be able to disable only part of ACPI
I have had issues in the past but it has been long ago!!!
I think if that were my PC, I would let Solus boot first and start uninstalling distros until you have a working PC without errors. Distros can always be reinstalled. It states that Solus is based on Debian, if it is, it must be Debian Testing. Void is independent, if so, for how long. So either use Solus, or install Debian Testing.
You have this all wrong, I have XP installed on one machine that has Gentoo and Debian also installed.
XP is not their for stability, it is installed for some of my older software, ie games, I sometimes run. Gentoo is the first to boot, XP is chosen from grub. I do have my main machine that is running W10 and W7, the only Linux is a Linux Mint VM. This machine will be rebuilt soon for W11.
OK.
I mean Win is your fallback.
Debian is my fallback at moment… just because it has been there for over 10 years and never failed me.
Yes, long term is the issue with Void? Probably Solus too.
I might just do nothing for 6 months. I do have a working PC.
All this started because I could not buy a plain old fashioned graphics card unless I went secondhand. I dont actually want or need accelerated graphics but it was forced onto me.
1 Like
I still did not completely read through thte whole thread, so sorry if I’m repeating something.
You may try to install newer kernel from Debian Backports.
For this, you need to add the backports repo to the /etc/apt/sources.list.
Thank you.
I have never tried to install a newer kernel in Debian . I did not know where to start. Is it hazardous?
I need to determine how new it has to be, to support the amdgpu driver.
At moment I know 5.10.0 is too old , and 5.15.0 is OK.
Regards
Neville
I’m on Bullseye, and running on 5.10.0-20 - I don’t have the newer kernel.
But I have the following line in my sources.list:
deb http://deb.debian.org/debian bullseye-backports main contrib non-free
You can add this line too.
Then run sudo apt update!
apt search linux-image | grep backports
will list the kernels you could install from the backports repo.
I get the following list:
linux-headers-5.18.0-0.deb11.4-686/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-headers-5.18.0-0.deb11.4-686-pae/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-headers-5.18.0-0.deb11.4-amd64/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-headers-5.18.0-0.deb11.4-cloud-amd64/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-headers-5.18.0-0.deb11.4-rt-686-pae/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-headers-5.18.0-0.deb11.4-rt-amd64/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-headers-5.19.0-0.deb11.2-686/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-headers-5.19.0-0.deb11.2-686-pae/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-headers-5.19.0-0.deb11.2-amd64/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-headers-5.19.0-0.deb11.2-cloud-amd64/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-headers-5.19.0-0.deb11.2-rt-686-pae/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-headers-5.19.0-0.deb11.2-rt-amd64/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-headers-6.0.0-0.deb11.2-686/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-headers-6.0.0-0.deb11.2-686-pae/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-headers-6.0.0-0.deb11.2-amd64/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-headers-6.0.0-0.deb11.2-cloud-amd64/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-headers-6.0.0-0.deb11.2-rt-686-pae/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-headers-6.0.0-0.deb11.2-rt-amd64/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-headers-6.0.0-0.deb11.6-686/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-headers-6.0.0-0.deb11.6-686-pae/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-headers-6.0.0-0.deb11.6-amd64/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-headers-6.0.0-0.deb11.6-cloud-amd64/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-headers-6.0.0-0.deb11.6-rt-686-pae/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-headers-6.0.0-0.deb11.6-rt-amd64/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-686/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-686-dbg/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-686-pae/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-686-pae-dbg/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-686-pae-unsigned/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-686-unsigned/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-amd64-dbg/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-amd64-unsigned/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-cloud-amd64/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-cloud-amd64-dbg/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-cloud-amd64-unsigned/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-rt-686-pae/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-rt-686-pae-dbg/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-rt-686-pae-unsigned/bullseye-backports 5.18.16-1~bpo11+1 i386
linux-image-5.18.0-0.deb11.4-rt-amd64/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-rt-amd64-dbg/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.18.0-0.deb11.4-rt-amd64-unsigned/bullseye-backports 5.18.16-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-686/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-686-dbg/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-686-pae/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-686-pae-dbg/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-686-pae-unsigned/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-686-unsigned/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-amd64-dbg/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-amd64-unsigned/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-cloud-amd64/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-cloud-amd64-dbg/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-cloud-amd64-unsigned/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-rt-686-pae/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-rt-686-pae-dbg/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-rt-686-pae-unsigned/bullseye-backports 5.19.11-1~bpo11+1 i386
linux-image-5.19.0-0.deb11.2-rt-amd64/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-rt-amd64-dbg/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-5.19.0-0.deb11.2-rt-amd64-unsigned/bullseye-backports 5.19.11-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-686/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-686-dbg/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-686-pae/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-686-pae-dbg/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-686-pae-unsigned/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-686-unsigned/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-amd64/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-amd64-dbg/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-amd64-unsigned/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-cloud-amd64/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-cloud-amd64-dbg/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-cloud-amd64-unsigned/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-rt-686-pae/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-rt-686-pae-dbg/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-rt-686-pae-unsigned/bullseye-backports 6.0.3-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.2-rt-amd64/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-rt-amd64-dbg/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.2-rt-amd64-unsigned/bullseye-backports 6.0.3-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-686/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-686-dbg/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-686-pae/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-686-pae-dbg/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-686-pae-unsigned/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-686-unsigned/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-amd64/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-amd64-dbg/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-amd64-unsigned/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-cloud-amd64/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-cloud-amd64-dbg/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-cloud-amd64-unsigned/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-rt-686-pae/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-rt-686-pae-dbg/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-rt-686-pae-unsigned/bullseye-backports 6.0.12-1~bpo11+1 i386
linux-image-6.0.0-0.deb11.6-rt-amd64/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-rt-amd64-dbg/bullseye-backports 6.0.12-1~bpo11+1 amd64
linux-image-6.0.0-0.deb11.6-rt-amd64-unsigned/bullseye-backports 6.0.12-1~bpo11+1 amd64
The latest I could install is kernel 6.0.0-0:
sudo su
apt install linux-image-6.0.0-0.deb11.6-amd64 linux-headers-6.0.0-0.deb11.6-amd64
Probably I’d try the newer firmwares from the backports too:
apt install firmware-amd-graphics -t bullseye-backports
I’m not sure, if this is required…
That’s it.
Reboot after complete.
You can revert to older kernel when booting to it (selecting in GRUB), then remove packages of the newer kernels.
I think it’s safe, I used kernels from the backports without problems, when I was on Buster, and I needed a newer nvidia driver whith a CUDA version that works with the that time upgraded Davinci Resolve.
However, taking a systemback (or equivalent 
) snapshot before installing something makes it more safe.
Thank you. All new to me.
I will certainly do a backup first… maybe even image it to another partition then do the backport upgrade on the image.
Might be an idea not to get too new a kernel.
Regards
Neville
1 Like
You are most welcome 
That’s a wise decision. Imaging the whole system partitions, or just use systemback: doesn’t really matter, what matters is that you can easily undo system changes, if things go wrong.
You could easily choose 5.18 as well, just replace the package names accordingly.
I usually like to have a stable reliable system, which just works, so I don’t upgrade to newer stuff just because its newer. I like to upgrade, if it brings stuff I need…
So now I still have the older kernel, and have no plan to upgrade it at the moment.
You now have a hardware, which the older kernel doesn’t operate properly -as it seems- so you have a very good reason to upgrade it. 
1 Like
What @kovacslt is saying sounds good!!! I have Debian running 5.10, I would try the update and pass the results on, no big deal if I mess up Debian.
One more thing you could do, since you do not need much, as for as graphics, would be to find a cpu with onboard graphics, if your mobo is compatible.
1 Like