On Monday, 02-12-2024 at 14:56 Timothy M Butterworth wrote:
On Sun, Dec 1, 2024 at 9:42 PM George at Clug wrote:
On Monday, 02-12-2024 at 03:20 Timothy M Butterworth wrote:
On Sun, Dec 1, 2024 at 10:12 AM George at Clug
wrote:
On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:
All,
You may want to avoid upgrading KDE Plasma to 6.2 in sid. I
upgraded
it
earlier and after a reboot I only get a black screen when
logging in.
Whenever someone says, KDE Plasma and black screen together, I
think
"nvidia drivers".
I doubt that is your issue. But do you have an Nvidia GPU
in the
computer?
George.
No, I do not have Nvidia. I have Sid in a VM. The black screen
is strange
because I have a visible mouse pointer. I also get crash
reporter popups.
"A black screen with only a visible mouse pointer" is one of the
issues I
have seen on computers with an Nvidia GPU, hence to me it was
likely you
had an Nvidia GPU, since you do not, then I suspect that the issue
is
related to the Graphics type that you have selected for your VM,
maybe
changing this to virtio and enabling OpenGL?
FYI: My Debian Testing VM with KDE Plasma Wayland is working well
after
updates.
What GPU does your computer have?, and what Graphics system is
your VM
using? (Which graphics driver and Display protocol do you use ?)
I have AMD with OpenAMD GPU Driver.
I am not familiar with the OpenAMD GPU Driver so I cannot comment on
them.
I am using the proprietary, non-free-firmware firmware-amd-graphics
packaged drivers on the Debian Bookworm computer that I was testing a
VM of KDE Testing.
$ inxi -G
Graphics:
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver:
amdgpu
https://wiki.debian.org/AtiHowTo
Proprietary, binary-only firmware (also known as microcode) is not
allowed in the main Debian repository as per the Debian Free Software Guidelines. The firmware can be obtained by installing the firmware-amd-graphics package, as long as the non-free-firmware
component is enabled in your SourcesList file.
Being curious about Wayland, KDE, and graphic drivers, I did further
testing.
On a PC with an Nvidia RTX 2070 and Nvidia proprietary drivers,
running KDE in X11 (because at this stage Wayland will not load), in Virt-Manager, I created a VM of Debian Testing, installing KDE
Plasma, using Virtio video drivers (no OpenGL support). I was able to
log in with session of Wayland. I changed the virtual video drive to
QXL and was still able to log in.
So both QXL and Virtio drivers work when using Nvidia or AMD
proprietary drivers (at least for the GPU versions I was testing
with).
I could test with older models of Nvidia or AMD graphics cards but for
now, I have done enough testing.
George.
Were you using a Wayland session or an X11 session?
Wayland
Do you get to see the SDDM login screen or is that black with a
mouse
pointer, too?
SDDM works fine
I use a Radeon RX 6600 GPU. In Virt-Manager, my Display is Spice
server,
Address, Hypervisor default, Port set to Auto. OpenGL is not
selected.
On my Debian Bookworm i7 Intel computer, I had a Debian Testing VM
with
Cinnamon, so I cloned this VM, ran updates and then installed
kde-full.
During the installation I selected "sddm" for the default display
manager.
When I rebooted I could see the SDDM login screen, and for the
"Session",
I selected Plasma (Wayland), then logged in normally. Everything
was
working as expected.
If I selected the QXL video type, then when I booted up, the VM
hung
during loading and no mouse pointer.
I need to correct my above statement, after discovering that QXL
drivers worked in a VM running on a PC with an Nvidia card, I retested
and discovered that on a PC with a Radeon RX 6600 GPU, and using AMD
firmware drivers, VM of Debian Testing using Wayland worked well with
QXL drivers and/or with Virtio drivers.
On Radeon GPU PC, running a VM which is using QXL drivers:
# lspci -k | grep -A 2 -E '(3D|VGA)'
00:01.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual
graphic card (rev 05)
Subsystem: Red Hat, Inc. QEMU Virtual Machine
Kernel driver in use: qxl
# env | grep -E -i 'vga|x11|xorg|wayland|plasma'
DESKTOP_SESSION=plasmawayland MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/
user@1000.service/session.slice/plasma-plasmashell.service/memory.pressure
WAYLAND_DISPLAY=wayland-0
PLASMA_USE_QT_SCALING=1
QT_WAYLAND_FORCE_DPI=96
When I changed back to the virtio
driver, all worked well and I was able log in and watch youtube
videos.
Please let me know if I can help.
I just use the VM to do testing of the installer and updates. I am
just
going to waite a week or so then do a clean install.
Here are my VM settings for the display
*
> function="0x0"/>
----------------------------------
When using Cinnamon I usually enable "OpenGL" too, so I tried this
too.
> function="0x0"/>
*
===========================================================================
# apt update && apt update && apt full-upgrade --autoremove -y &&
apt
autoremove -y && apt clean
Hit:1 http://security.debian.org/debian-security testing-security
InRelease
Hit:2 http://deb.debian.org/debian testing InRelease
Hit:3 http://deb.debian.org/debian testing-updates InRelease
Hit:4 http://deb.debian.org/debian testing-backports InRelease
All packages are up to date.
Hit:1 http://security.debian.org/debian-security testing-security
InRelease
Hit:2 http://deb.debian.org/debian testing InRelease
Hit:3 http://deb.debian.org/debian testing-updates InRelease
Hit:4 http://deb.debian.org/debian testing-backports InRelease
All packages are up to date.
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux trixie/sid
Release: n/a
Codename: trixie
# uname -r
6.11.10-amd64
# env | grep -E -i 'x11|xorg|wayland|plasma'
DESKTOP_SESSION=plasmawayland
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1004.slice/
user@1004.service
/session.slice/plasma-plasmashell.service/memory.pressure WAYLAND_DISPLAY=wayland-0
PLASMA_USE_QT_SCALING=1
QT_WAYLAND_FORCE_DPI=96
# lspci -k | grep -A 2 -E '(3D|VGA)'
00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU
(rev 01)
Subsystem: Red Hat, Inc. Device 1100
Kernel driver in use: virtio-pci
===========================================================================
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀
<html>
<head>
<style type="text/css">
body,p,td,div,span{
font-size:13px; font-family:Arial, Helvetica, sans-serif;
};
body p{
margin:0px;
}
</style>
</head>
<body>
On Monday, 02-12-2024 at 14:56 Timothy M Butterworth wrote:<br>
> On Sun, Dec 1, 2024 at 9:42 PM George at Clug <
Clug@goproject.info> wrote:<br>
> <br>
> > On Monday, 02-12-2024 at 03:20 Timothy M Butterworth wrote:<br>
> > > On Sun, Dec 1, 2024 at 10:12 AM George at Clug <
Clug@goproject.info><br>
> > wrote:<br>
> > ><br>
> > > ><br>
> > > ><br>
> > > > On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:<br>
> > > > > All,<br>
> > > > ><br>
> > > > > You may want to avoid upgrading KDE Plasma to 6.2 in sid. I upgraded<br>
> > it<br>
> > > > > earlier and after a reboot I only get a black screen when logging in.<br>
> > > ><br>
> > > > Whenever someone says, KDE Plasma and black screen together, I think<br>
> > > > "nvidia drivers".<br>
> > > ><br>
> > > > I doubt that is your issue. But do you have an Nvidia GPU in the<br>
> > computer?<br>
> > > ><br>
> > > > George.<br>
> > > ><br>
> > ><br>
> > > No, I do not have Nvidia. I have Sid in a VM. The black screen is strange<br>
> > > because I have a visible mouse pointer. I also get crash reporter popups.<br>
> > ><br>
> ><br>
> > "A black screen with only a visible mouse pointer" is one of the issues I<br>
> > have seen on computers with an Nvidia GPU, hence to me it was likely you<br>
> > had an Nvidia GPU, since you do not, then I suspect that the issue is<br>
> > related to the Graphics type that you have selected for your VM, maybe<br>
> > changing this to virtio and enabling OpenGL?<br>
> ><br>
> > FYI: My Debian Testing VM with KDE Plasma Wayland is working well after<br>
> > updates.<br>
> ><br>
> > What GPU does your computer have?, and what Graphics system is your VM<br>
> > using? (Which graphics driver and Display protocol do you use ?)<br> > ><br>
> <br>
> I have AMD with OpenAMD GPU Driver.<br>
I am not familiar with the OpenAMD GPU Driver so I cannot comment on them.<br>
I am using the proprietary, non-free-firmware firmware-amd-graphics packaged drivers on the Debian Bookworm computer that I was testing a VM of KDE Testing.<br>
$ inxi -G<br>
Graphics:<br>
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu<br>
<a target="_blank" class="blue" href="
https://wiki.debian.org/AtiHowTo">https://wiki.debian.org/AtiHowTo</a><br>
Proprietary, binary-only firmware (also known as microcode) is not allowed in the main Debian repository as per the Debian Free Software Guidelines. The firmware can be obtained by installing the firmware-amd-graphics package, as long as the
non-free-firmware component is enabled in your SourcesList file. <br> <br><div>Being curious about Wayland, KDE, and graphic drivers, I did further testing.</div><div><br></div><div>On a PC with an Nvidia RTX 2070 and Nvidia proprietary drivers, running KDE in X11 (because at this stage Wayland will not load), in Virt-
Manager, I created a VM of Debian Testing, installing KDE Plasma, using Virtio video drivers (no OpenGL support). I was able to log in with session of Wayland. I changed the virtual video drive to QXL and was still able to log in. </div><div><
</div><div>So both QXL and Virtio drivers work when using Nvidia or AMD proprietary drivers (at least for the GPU versions I was testing with). </div><div><br></div><div>I could test with older models of Nvidia or AMD graphics cards but for now,
I have done enough testing.<br></div><div><br>
</div><div>George.</div>
> <br>
> <br>
> ><br>
> > Were you using a Wayland session or an X11 session?<br>
> ><br>
> <br>
> Wayland<br>
> <br>
> <br>
> ><br>
> > Do you get to see the SDDM login screen or is that black with a mouse<br>
> > pointer, too?<br>
> ><br>
> <br>
> SDDM works fine<br>
> <br>
> <br>
> ><br>
> > I use a Radeon RX 6600 GPU. In Virt-Manager, my Display is Spice server,<br>
> > Address, Hypervisor default, Port set to Auto. OpenGL is not selected.<br>
> ><br>
> > On my Debian Bookworm i7 Intel computer, I had a Debian Testing VM with<br>
> > Cinnamon, so I cloned this VM, ran updates and then installed kde-full.<br>
> > During the installation I selected "sddm" for the default display manager.<br>
> ><br>
> > When I rebooted I could see the SDDM login screen, and for the "Session",<br>
> > I selected Plasma (Wayland), then logged in normally. Everything was<br>
> > working as expected.<br>
> ><br>
> > If I selected the QXL video type, then when I booted up, the VM hung<br><div>
> > during loading and no mouse pointer. <br></div><div><br></div><div>I need to correct my above statement, after discovering that QXL drivers worked in a VM running on a PC with an Nvidia card, I retested and discovered that on a PC with a
Radeon RX 6600 GPU, and using AMD firmware drivers, VM of Debian Testing using Wayland worked well with QXL drivers and/or with Virtio drivers. <br></div><div><br></div><div>On Radeon GPU PC, running a VM which is using QXL drivers:<br><br># lspci -k |
grep -A 2 -E '(3D|VGA)'<br>00:01.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 05)<br> Subsystem: Red Hat, Inc. QEMU Virtual Machine<br>
Kernel driver in use: qxl<br><br># env | grep -E -i 'vga|x11|xorg|wayland|plasma'<br>DESKTOP_SESSION=plasmawayland<br>MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/
user@1000.service/session.slice/plasma-plasmashell.service/memory.
pressure<br>WAYLAND_DISPLAY=wayland-0<br>PLASMA_USE_QT_SCALING=1<br>QT_WAYLAND_FORCE_DPI=96</div><div><br></div><div><br></div><div>> > When I changed back to the virtio</div>
> > driver, all worked well and I was able log in and watch youtube videos.<br>
> ><br>
> > Please let me know if I can help.<br>
> ><br>
> <br>
> I just use the VM to do testing of the installer and updates. I am just<br>
> going to waite a week or so then do a clean install.<br>
> <br>
> <br>
> ><br>
> > Here are my VM settings for the display<br>
> ><br>
> > <graphics type="spice" port="5900" autoport="yes" listen="127.0.0.1"><br>
> > <listen type="address" address="127.0.0.1"/><br> > > <image compression="off"/><br>
> > </graphics><br>
> ><br>
> > <video><br>
> > <model type="virtio" heads="1" primary="yes"/><br> > > <alias name="video0"/><br>
> > <address type="pci" domain="0x0000" bus="0x00" slot="0x01"<br>
> > function="0x0"/><br>
> > </video><br>
> ><br>
> > ----------------------------------<br>
> ><br>
> > When using Cinnamon I usually enable "OpenGL" too, so I tried this too.<br>
> ><br>
> > <video><br>
> > <model type="virtio" heads="1" primary="yes"><br> > > <acceleration accel3d="yes"/><br>
> > </model><br>
> > <address type="pci" domain="0x0000" bus="0x00" slot="0x01"<br>
> > function="0x0"/><br>
> > </video><br>
> ><br>
> > <graphics type="spice"><br>
> > <listen type="none"/><br>
> > <image compression="off"/><br>
> > <gl enable="yes" rendernode="/dev/dri/by-path/pci-0000:03:00.0-render"/><br>
> > </graphics><br>
> ><br>
> > ===========================================================================<br>
> ><br>
> > # apt update && apt update && apt full-upgrade --autoremove -y && apt<br>
> > autoremove -y && apt clean<br>
> > Hit:1 <a target="_blank" class="blue" href="
http://security.debian.org/debian-security">http://security.debian.org/debian-security</a> testing-security<br>
> > InRelease<br>
> > Hit:2 <a target="_blank" class="blue" href="
http://deb.debian.org/debian">http://deb.debian.org/debian</a> testing InRelease<br>
> > Hit:3 <a target="_blank" class="blue" href="
http://deb.debian.org/debian">http://deb.debian.org/debian</a> testing-updates InRelease<br>
> > Hit:4 <a target="_blank" class="blue" href="
http://deb.debian.org/debian">http://deb.debian.org/debian</a> testing-backports InRelease<br>
> > All packages are up to date.<br>
> > Hit:1 <a target="_blank" class="blue" href="
http://security.debian.org/debian-security">http://security.debian.org/debian-security</a> testing-security<br>
> > InRelease<br>
> > Hit:2 <a target="_blank" class="blue" href="
http://deb.debian.org/debian">http://deb.debian.org/debian</a> testing InRelease<br>
> > Hit:3 <a target="_blank" class="blue" href="
http://deb.debian.org/debian">http://deb.debian.org/debian</a> testing-updates InRelease<br>
> > Hit:4 <a target="_blank" class="blue" href="
http://deb.debian.org/debian">http://deb.debian.org/debian</a> testing-backports InRelease<br>
> > All packages are up to date.<br>
> > Summary:<br>
> > Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0<br>
> > Summary:<br>
> > Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0<br>
> ><br>
> > # lsb_release -a<br>
> > No LSB modules are available.<br>
> > Distributor ID: Debian<br>
> > Description: Debian GNU/Linux trixie/sid<br> > > Release: n/a<br>
> > Codename: trixie<br>
> ><br>
> > # uname -r<br>
> > 6.11.10-amd64<br>
> ><br>
> > # env | grep -E -i 'x11|xorg|wayland|plasma'<br>
> > DESKTOP_SESSION=plasmawayland<br>
> ><br>
> > MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1004.slice/
user@1004.service<br>
> > /session.slice/plasma-plasmashell.service/memory.pressure<br>
> > WAYLAND_DISPLAY=wayland-0<br>
> > PLASMA_USE_QT_SCALING=1<br>
> > QT_WAYLAND_FORCE_DPI=96<br>
> ><br>
> > # lspci -k | grep -A 2 -E '(3D|VGA)'<br>
> > 00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU (rev 01)<br>
> > Subsystem: Red Hat, Inc. Device 1100<br>
> > Kernel driver in use: virtio-pci<br>
> ><br>
> ><br>
> > ===========================================================================<br>
> ><br>
> ><br>
> ><br>
> ><br>
> <br>
> -- <br>
> ⢀⣴⠾⠻⢶⣦⠀<br>
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system<br>
> ⢿⡄⠘⠷⠚⠋⠀ <a target="_blank" class="blue" href="
https://www.debian.org">https://www.debian.org</a>/<br>
> ⠈⠳⣄⠀⠀<br>
>
</body></html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)