![]() ![]() This time the Intel just mysteriously worked along with bbswitch. What confuses me is that it sounds as if all Wayland display servers are window. X11 runs with the Xorg server and a separate window manager for compositing, and Wayland uses display servers that also handle compositing. Interestingly, when I switched to Nvidia, suse-prime complained about not able to detect Nvidia and wanted to switch to Intel. I am researching differences between xorg and wayland and am being confused by one thing. PCI BusID of NVIDIA card could not be detected! Unloading bbswitch and switching nvidia ON. Forcing nvidia due to Intel card not found With a few changes, the Xorg server can be modified to use wayland input devices for input and forward either the root window or individual top-level windows as wayland surfaces. user_logout_waiter: X restart detected, preparing switch to intel Here is the part of the log: service restored by user Then it would attempt to switch to Nvidia instead and caused black screen with login, because it also couldn’t detect Nvidia. Update: I took a look at the prime-select.log and here is what I found (copied and pasted from the bug report page):Īccording to `prime-select.log’, it couldn’t detect Intel when I tried to switch to it. Here I’m wondering if missing driver-related packages are missing might be the cause of the issues mentioned above. For example, my Tumbleweed ships with packages like intel-media-driver intel-vaapi-driver xorg-x11-driver-video libvulkan_intel Mesa-vulkan-device-select, which MicroOS doesn’t. By default, MicroOS comes with less installed packages than Tumbleweed, nor does it have ‘recommended packages’ like Tumbleweed. Switching to Nvidia G05 driver doesn’t help either. I think these are MicroOS exclusive issues, as I never encountered them on Tumbleweed. However, my /usr/sbin/prime-select get-current said I’m using Intel with bbswitch on. If I select sudo prime-select Nvidia, I was able to log out and log in successfully.I skimmed our forum, the arch wiki and arch forum. sudo prime-select unset and sudo prime-select service restore won’t help. Goal: My mission was to enable wayland (or xwayland) on Nvidia, more specifically allow to choose between xorg and wayland on GDM at login, and make that settings wheel appear in the lower right corner at login. After rebooting the device, /usr/sbin/prime-select get-current still said no driver configured. When I put sudo prime-select intel, my laptop immediately turned into black screen with login.Next, in the left pane, scroll to the bottom and select Users. So, you first need to open Settings from the app launcher. Otherwise, the dedicated option will not appear on the lock screen. I installed the Nvidia G06 driver with suse-prime and bbswitch. Before you switch between Wayland or Xorg in Ubuntu, you first need to disable Automatic Login. But now that I get the bottom-right gear, I’ve re-enabled auto-login and it works (as in, I boot straight into the desktop, but when I log out I get the gear on the bottom-right while typing the password).A user of Micro OS Gnome here. The only different thing then was that I had auto-login enabled. Now, I still do not understand though why originally (before touching nf) I was not getting the gear to begin with. So I think my mistake was that I needed to reboot in order to see the effects of these changes. Weston/Wayland compositor Hardware Render. After restarting, I could see the gear again. You agree to grant Intel a non-exclusive, royalty-free license to any patent. ![]() After removing it I tried by logging out and back in, but still could not see the gear.Once I had WaylandEnabled=false or WaylandEnabled=true, the gear would never appear, GDM would just do one of the two without showing the gear.After resetting nf to the state above, I was still not getting the gear when typing the password. The most important reason people chose X. In the question What are the best Linux display servers X.Org is ranked 1st while Wayland is ranked 2nd. I am using Virtualbox with guest additions installed so I think the VESA driver above should be appropriate for it? When comparing Wayland vs X.Org, the Slant community recommends X.Org for most people. # Uncomment the line below to turn on debuggingįinally, I checked to make sure I have a video driver for my display and I have: ~]$ pacman -Qq | grep -i xf86-video # Uncomment the line below to force the login screen to use Xorg I also read I can force GDM via configuration: ~]$ cat /etc/gdm/nf While reading up on this, people suggested that I am already using Xorg, but the about page in Gnome settings says Wayland and also: ~]$ echo $XDG_SESSION_TYPE Based on what I’ve read, I should be able to see a gear icon at the login screen to switch between Xorg and Wayliand, but I do not have that on my log in screen. I’ve been reading up on this but can’t seem to get it to work. ![]()
0 Comments
Leave a Reply. |