Here are logs from 3 separate type of boots (actually I had to reboot at
least 20 times, because I had a lot of crashes/hangs):
1) USB safemode boot (since the normal USB boot didn't work ~ 5 times)
2) USB normal boot (it worked, don't know why, but I'm not complaining)
3) normal installed boot (c
With the live USB stick, there are also Xorg issues. Even got a nice
crash rapport.
** Attachment added: "_usr_lib_xorg_Xorg.127.crash"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5593009/+files/_usr_lib_xorg_Xorg.127.crash
--
You received this bug notification be
Here's the vulkaninfo. I got lucky, since the entire GUI hung shortly
after (don't think it's related to running this specific command
though).
Reverted the Wayland (GDM) change, so it's stock behaviour. And yes, I
switched back to stock config and kernel.
Will try to USB live version shortly.
*
Sorry for the late reply.
tonight I installed the full ubuntu-desktop package (with a "clean" test
user) and experienced crashes/hangs and other weird behaviour with the
stock setup. When I disabled Wayland in GDM3, it got a little better,
until that had issues as well.
Note: I went from an 7+ ye
am currently using AwesomeWM ( https://awesomewm.org/ ) with LightDM.
- when I ran the vulkaninfo this time, I temporarily switched back to 'stock'
config (which is radeon, not amdgpu). So that might be correct. Should I switch
to amdgpu and run it again?
- between first post and now, I also swi
Noticed something quite weird when using the default kernel module
(radeon).
- when running glxgears, it starts running normally, but stalls quickly. If I
active movement (hightling a part of my terminal and moving the mouse around
simultaneously), it seems to skyrocket and run normally. Until I
** Attachment added: "vulkaninfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592574/+files/vulkaninfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "lsmod.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592575/+files/lsmod.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1975566
** Attachment added: "glxinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592573/+files/glxinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1975
Already tried out some different things:
- Tried the latest linux kernel
- Fiddled with amdgpu & radeon kernel module options
- Tried running the amdgpu kernel module instead of radeon
Had to SSH into the machine to do anything (usually the system locks
up).
Some error messages from the fiddling:
Public bug reported:
Recently I upgraded my machine and moved my GPU over from the old (Intel
something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I
did a fresh Ubuntu install (server) and added packages to get my GUI
rolling (lightdm + awesomewm), just like before.
The graphics c
Public bug reported:
Upgraded to 21.04 (hirsute) and now the network card is unavailable
after suspend to RAM (sleep state S3). It worked flawlessly up until
20.10. My workaround for now is unloading and reloading the kernel
module, but that won't work for normal users, hence this report.
NIC in
12 matches
Mail list logo
