I think the no 3d controller thing might just be how it is on amd/nvidia systems? it could also be a wayland thing I suppose. This is mine:
01:00.0 VGA compatible controller: NVIDIA Corporation GA104 [Geforce RTX 3070 Ti Laptop GPU] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 1b9c
Kernel driver in use: nvidia
--
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev c7)
Subsystem: ASUSTeK Computer Inc. Device 1b9c
Kernel driver in use: amdgpu
which is working. Also notably, on laptops with nvidia dgpus, by default the nvidia gpu is always used for vulkan applications on arch. The only way to fix this is to manually define the default vulkan driver in .profile or something like that like this command for amdgpu.
export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json #Run Vulkan on AMD
then edit prime-run to use the nvidia-icd files when it’s called.
At least that’s how it was for both my current system (amd/nvidia) and last system (intel/nvidia).
yup, thats how it was out of the box for me. there is no discernable way to turn off the nvidia gpu besides supergfxctl (asus thing).
I don’t remember if my last laptop was the same or not; but I do remember the nvidia gpu was always ‘on’ and always connected to the driver (reason I remember this was i was messing with vga passthrough, u need to disconnect the card from the nvidia gpu driver and connect it to the vfio one instead, the only way to do it was between reboots, there were other ways but they lead to system freezes and kernel panics). The exact command i used was the lspci one earlier in this thread.
It’s interesting to me that so many Hybrid laptops work so differently. I’m sure you also don’t have an issue with Firefox on full screen playing videos where it goes white?
No, I can’t get far enough to even login even under fallback with the gpu option set to auto select so I just reinstalled the distro from the start now. It seems to be okay for now. I know it’s extreme for some folks that I do that but I don’t have much of anything on the laptop in terms of data so wiping is just quicker for me than trying to tease out configurations. In my opinion, sometimes it’s best to clean the slate to make sure I didn’t miss something.
Well that approach didn’t work well. When I came back today after locking the laptop for about a day it, the login screen would turn white and kde-win would crash. It’s quite frustrating, so I turned it back to auto-select for now. My guess is there’s something dodgy with these Acer Nitro laptops with their bios at this point since I had similar issues with Pop_OS on my first one (Microcenter service offered to just replace my laptop since my guess is they didn’t bother trying to service it since it was three weeks out from purchase) where the screen in this case would flash white until it became completely white for the entire environment and not just youtube.
Honestly, this really makes me sour towards Nvidia GPUs if they behave this way even on their own proprietary drivers. It’s quite annoying.
I think I might have to try the prime tool since isn’t that meant to handle these hybrid iGPU/dGPU setups?
Edit: here’s what pacman -Q | grep -A 2 -E “(nvidia|amd|nouv|mesa|intel)” produced.
Does it happen on any wayland environment or only the one you’re using? (did you try sway?) Are we sure the nvidia gpu actually has anything to do with this? And are you sure it doesn’t happen on X? Also is
Yeah I think the introduction of the nouveau driver possibly caused issues? I’m a programmer but not one that does OS so I have no clue how the kernel modules are handled in terms of overlapping functionality. Last night, I used the nvidia-inst tool and it didn’t do much, the current 550 drivers were left in and it didn’t install nvidia_drm so I have no clue if that’s okay or jor. What I do know is that it seems kde-win isn’t crashing and Firefox for now is playing nice. I might need to dig into the logs to figure this issue out I swear.
If you installed the nvidia drivers and it’s working properly i wouldn’t waste my time trying to understand why it didn’t work before. It could be because of nouveau opensource drivers which i would never use on newer nvidia hardware such as the 4060 series.
If you want to know how that can be fixed, it’ll lead you down the right path at least.
But since GL is defaulting to the AMD gpu, it would stand to reason that firefox and also kwin are probably being run on your AMD gpu, try using prime-run to launch firefox and see if it behaves any differently. If it doesn’t, check your hardware acceleration settings in firefox, see if turning it off/on has an effect.