I’m on exactly this right now, I am on Wayland. If you have confirmed you’re on 3.03, which means you did update it yourself from this thread, then there is no reason a fully updated Ubuntu 22.04.3 install on 6.1.0-1024-oem should be on Wayland.
I’d log out, select the little gear, avoid choosing X, try again.
This would be correct. When on Battery, I highly recommend selecting Power Saver. On power, you can choose whatever you like, Performance for example.
You may not on the right BIOS if you’re not seeing a clock screen when lifting your lid to resume. In s2idle, which is what we use for this laptop, the behavior on 3.03 on Ubuntu 22.04.3 is close lid, suspends. Lift lid, wakes to a clock screen.
Please recheck your BIOS as there are multiple points that make this feel like 3.02 behavior. Then make absolutely sure you’ve updated it.
If you run this:
sudo lsmod | grep amdgpu
and see this:
amdgpu 13041664 28
iommu_v2 24576 1 amdgpu
gpu_sched 49152 1 amdgpu
drm_buddy 20480 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
ttm 98304 2 amdgpu,drm_ttm_helper
drm_display_helper 188416 1 amdgpu
drm_kms_helper 208896 4 drm_display_helper,amdgpu
i2c_algo_bit 16384 1 amdgpu
drm 598016 17 gpu_sched,drm_kms_helper,drm_display_helper,drm_buddy,amdgpu,drm_ttm_helper,ttm
video 65536 1 amdgpu
Same with:
sudo lshw -C video | grep amdgpu
Seeing this:
configuration: depth=32 driver=amdgpu latency=0 resolution=2256,1504
And this may be where all of the other stuff with Wayland/X, Suspend and related are falling down. You should not, whatsoever, need to have done this and it may have made things…complicated.
To be clear, you do not install anything outside of what appeared in the guide. Doing so, adds something that I am not going to be able to replicate.
The OEM C install is all that is needed, you do not need to compile anything and doing so means you would be best off starting off fresh with a new install in my opinion.
Again, with the LTS, we do not want to be installing stuff outside of the exist repos, it will created added layers of complexity making support difficult
You would have followed this guide, the second section in red, and followed the link to here.
Follow these steps exactly, try a couple times if needed be - reboot. Again, due to all the other stuff done, I’d fresh install and start over, though.
Hopefully this provides some actionable guidelines.
Short version, our guides are setup end to end, but it’s critical not to start compiling random things as it will goof things up. 