Results 1 to 9 of 9

Thread: No GUI on boot

  1. #1

    Default No GUI on boot

    Hi. I'm using Tumbleweed and everything worked fine until I tried installing NVIDIA drivers shown here:
    https://opensuse.github.io/openSUSE-...l_proprietary/

    I tried the nvidia-glG05 first then uninstalled then my issues started. I then tried installing nvidia-glG04 and uninstalled with no changes to my issue. I have a NVIDIA RTX 2080 SUPER.

    These are the steps I followed.

    Setup the driver⚓︎
    With Yast⚓︎

    1. Go to YAsT2.
    2. Then Software Management.
    3. On the menu, click Configuration > Repositories... (or do Ctrl + R).
    4. Click Add > Community Repositories.
    5. Select nVidia Graphics Drivers > Accept > Trust.
    6. On the Configured Software Repositories > Click Ok
    7. Back to Software Management Windows" > View > Repositories > Select nVidia Graphics Drivers.
    8. Select x11-video-nvidiaG05 > Accept (Some graphic cards need G04, see the first section above)
    9. Reboot.
    After uninstall now when I boot up it comes up to CLI. I have to run "startx" to get the KDE desktop to load. I also followed this guide here.
    16.3.3 No Graphical Login

    If the machine comes up, but does not boot into the graphical login manager, anticipate problems either with the choice of the default systemd target or the configuration of the X Window System. To check the current systemd default target run the command sudo systemctl get-default. If the value returned is not graphical.target, run the command sudo systemctl isolate graphical.target. If the graphical login screen starts, log in and start YaST › System › Services Manager and set the Default System Target to Graphical Interface. From now on the system should boot into the graphical login screen.
    If the graphical login screen does not start even if having booted or switched to the graphical target, your desktop or X Window software is probably misconfigured or corrupted. Examine the log files at /var/log/Xorg.*.log for detailed messages from the X server as it attempted to start. If the desktop fails during start, it may log error messages to the system journal that can be queried with the command journalctl (see Book “Reference”, Chapter 11 “journalctl: Query the systemd Journal” for more information). If these error messages hint at a configuration problem in the X server, try to fix these issues. If the graphical system still does not come up, consider reinstalling the graphical desktop.
    I ran "sudo systemctl get-default" and it returns "graphical.target". The GUI still does not load. I ran "journalctl" and get this.

    Code:
    -- Journal begins at Sat 2021-10-09 16:01:03 AKDT, ends at Sat 2021-10-16 17:51:05 AKDT. -- 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Queued start job for default target Main User Target. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Created slice User Application Slice. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Started Daily Cleanup of User's Temporary Directories. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Reached target Paths. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Reached target Timers. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Starting D-Bus User Message Bus Socket... 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Listening on Multimedia System. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Listening on Sound System. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Starting Create User's Volatile Files and Directories... 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Finished Create User's Volatile Files and Directories. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Listening on D-Bus User Message Bus Socket. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Reached target Sockets. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Reached target Basic System. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Reached target Main User Target. 
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Startup finished in 78ms. 
    Oct 09 16:01:03 localhost.localdomain sddm-helper[2045]: Adding cookie to "/run/user/1000/xauth_uNpEFu"
    Oct 09 16:01:03 localhost.localdomain systemd[2036]: Started D-Bus User Message Bus. 
    Oct 09 16:01:03 localhost.localdomain dbus-daemon[2057]: [session uid=1000 pid=2057] Activating service name='org.kde.KSplash' requested by ':1.2' (uid=1000 pid=>
    Oct 09 16:01:03 localhost.localdomain dbus-daemon[2057]: [session uid=1000 pid=2057] Successfully activated service 'org.kde.KSplash' 
    Oct 09 16:01:03 localhost.localdomain klauncher[2165]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    Oct 09 16:01:04 localhost.localdomain kcminit_startup[2169]: Initializing  "kcm_mouse" :  "kcminit_mouse"
    Oct 09 16:01:04 localhost.localdomain kcminit_startup[2169]: Initializing  "kcm_style" :  "kcminit_style"
    Oct 09 16:01:04 localhost.localdomain kcminit_startup[2169]: QDBusConnection: error: could not send signal to service "" path "//home/moz/.kde4/share/config/kdeg>
    Oct 09 16:01:04 localhost.localdomain plasma_session[2123]: org.kde.plasma.session: process job  "kcminit_startup" finished with exit code  0 
    Oct 09 16:01:04 localhost.localdomain dbus-daemon[2057]: [session uid=1000 pid=2057] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' r>
    Oct 09 16:01:04 localhost.localdomain systemd[2036]: Starting User preferences database... 
    Oct 09 16:01:04 localhost.localdomain dbus-daemon[2057]: [session uid=1000 pid=2057] Successfully activated service 'ca.desrt.dconf' 
    Oct 09 16:01:04 localhost.localdomain systemd[2036]: Started User preferences database. 
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: The name org.wicd.daemon was not provided >
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon 
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: print-manager.kded: unable to register service to dbus
    Oct 09 16:01:04 localhost.localdomain dbus-daemon[2057]: [session uid=1000 pid=2057] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kgl>
    Oct 09 16:01:04 localhost.localdomain systemd[2036]: Created slice User Background Tasks Slice. 
    Oct 09 16:01:04 localhost.localdomain systemd[2036]: Starting KDE Global Shortcuts Server... 
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5091:48: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5093:48: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:47: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5099:46: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:48: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5111:46: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5113:46: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5117:45: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain kwin_x11[2181]: kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5120:46: this compose sequence is a duplicat>
    Oct 09 16:01:04 localhost.localdomain dbus-daemon[2057]: [session uid=1000 pid=2057] Successfully activated service 'org.kde.kglobalaccel' 
    Oct 09 16:01:04 localhost.localdomain systemd[2036]: Started KDE Global Shortcuts Server. 
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: org.kde.wacomtablet.common: d->name.isEmpty? true
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: org.kde.wacomtablet.common: d->name.isEmpty? true
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: bluedevil: Created
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: Installing the delayed initialization callback.
    Oct 09 16:01:04 localhost.localdomain ksmserver[2242]: Qt: Session management error: networkIdsList argument is NULL
    Oct 09 16:01:04 localhost.localdomain kded5[2177]: System timezone has been changed, new timezone is "America/Anchorage"
    Oct 09 16:01:04 localhost.localdomain plasma_session[2123]: org.kde.plasma.session: Starting autostart service  "/etc/xdg/autostart/kaccess.desktop" ("/usr/bin/k>
    I know at one point at the login screen at the bottom I had an option to pick the session and I change it from whatever the default was to Wayland. Someone told me there is a conflict with nvidia drivers and that was the reason but I don't see it there to change anymore. I looked at changing my display manager thinking that might help shown here.
    https://en.opensuse.org/SDB:Change_Display_Manager

    moz@localhost:~> update-alternatives --list default-displaymanager
    Absolute path to 'update-alternatives' is '/usr/sbin/update-alternatives', so running it may require superuser privileges (eg. root).
    moz@localhost:~> sudo update-alternatives --list default-displaymanager
    [sudo] password for root:
    /usr/lib/X11/displaymanagers/console
    /usr/lib/X11/displaymanagers/sddm
    /usr/lib/X11/displaymanagers/xdm
    moz@localhost:~> update-alternatives --config default-displaymanager
    Absolute path to 'update-alternatives' is '/usr/sbin/update-alternatives', so running it may require superuser privileges (eg. root).
    moz@localhost:~> sudo update-alternatives --config default-displaymanager
    There are 3 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).

    Selection Path Priority Status
    ------------------------------------------------------------
    * 0 /usr/lib/X11/displaymanagers/sddm 25 auto mode
    1 /usr/lib/X11/displaymanagers/console 5 manual mode
    2 /usr/lib/X11/displaymanagers/sddm 25 manual mode
    3 /usr/lib/X11/displaymanagers/xdm 10 manual mode

    Press <enter> to keep the current choice[*], or type selection number:


    I hope this is enough information. I don't know too much about OpenSUSE but I'm trying to learn. Thank you.

  2. #2
    Join Date
    Dec 2010
    Location
    Mechelen, Belgium
    Posts
    79

    Default Re: No GUI on boot

    In tumbleweed, it is better to install the nvidia drivers (and make updates/upgrades) from the CLI (virtual terminal or console), not in graphical mode.
    I ma not a specialist of these problems but you could have a look at the blacklisted modules. By installing nvidia, nouveau was very probably blacklisted and it may have happened that it staid so after uninstalling the nvidia drivers.
    To help the readers, you could also show which gpu's are on your computer.
    You can show the result of:
    • sudo lspci -nnk | grep -iA2 vga
    • inxi -aFz
    • lsmod | grep 'nvidia' (and 'nouveau', 'intel', 'i915',...)


    An extreme solution is to reinstall your OS.

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,101
    Blog Entries
    15

    Default Re: No GUI on boot

    Hi
    You 2080 GPU is only supported via G05 or newer.... I would suggest booting to multi-user target and installing the G05 series or the 495.29.05 driver the hard way?

    Code:
    inxi -Gxxz
    
    Graphics:  Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel bus-ID: 02:00.0 
               chip-ID: 1002:699f 
               Device-2: NVIDIA GP108 [GeForce GT 1030] vendor: eVga.com. driver: nvidia v: 495.29.05 bus-ID: 03:00.0 
               chip-ID: 10de:1d01 
               Display: x11 server: X.Org 1.20.13 compositor: gnome-shell driver: loaded: amdgpu,nvidia 
               unloaded: fbdev,modesetting,vesa alternate: ati,nouveau,nv resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz 
               3: 1920x1080~60Hz s-dpi: 96 
               OpenGL: renderer: Radeon RX550/550 Series (POLARIS12 DRM 3.42.0 5.14.9-1-default LLVM 13.0.0) v: 4.6 Mesa 21.2.3 
               direct render: Yes
    https://en.opensuse.org/SDB:NVIDIA

    https://en.opensuse.org/SDB:NVIDIA_the_hard_way
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4

    Default Re: No GUI on boot

    KDE is not ready yet for Wayland.
    Nvidia drivers are not ready yet for Wayland. Possibly new 495 series Nvidia drivers will help with that.

  5. #5

    Default Re: No GUI on boot

    Hello! Thank you everyone for your input. I actually got it fixed by using a (older/previous) read only snapshot and ran "sudo snapper rollback", rebooted and continued testing everything. Btrfs and snapshots are a life saver. I just didn't know about or understand them exactly until I read about them more. My desktop session is back to Plasma (X11) and using the nouveau driver for my RTX 2080. I do have video tearing now when moving open windows around, like Firefox, Dolphin, ect. I assume that's from the nouveau driver.

  6. #6

    Default Re: No GUI on boot

    Sorry to double post my previous post was too long so I have to break it up.

    Code:
    moz@localhost:~> sudo lspci -nnk | grep -iA2 vga 
    [sudo] password for root:  
    09:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] [10de:1e81] (rev a1) 
            Subsystem: Gigabyte Technology Co., Ltd Device [1458:3ff9] 
            Kernel driver in use: nouveau 
    moz@localhost:~> inxi -aFz 
    System:    Kernel: 5.14.9-1-default x86_64 bits: 64 compiler: gcc v: 11.2.1  
               parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.9-1-default root=UUID=a5cad08e-26d1-41f0-9cd1-e10acbc77e6a splash=silent  
               mitigations=auto quiet  
               Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Tumbleweed 20211012  
    Machine:   Type: Desktop System: Gigabyte product: X570 AORUS ELITE WIFI v: -CF serial: <filter>  
               Mobo: Gigabyte model: X570 AORUS ELITE WIFI v: x.x serial: <filter> UEFI: American Megatrends v: F11  
               date: 12/06/2019  
    CPU:       Info: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 family: 17 (23) model-id: 71 (113)  
               stepping: N/A microcode: 8701013 cache:L2: 6 MiB  
               flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 182059  
               Speed: 2053 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz):1: 2053 2: 3592 3: 2194 4: 2200 5: 2193  
               6: 2195 7: 2185 8: 2191 9: 2193 10: 2193 11: 2195 12: 2197 13: 2187 14: 2196 15: 2194 16: 2196 17: 2193 18: 2196  
               19: 2195 20: 2196 21: 2325 22: 2194 23: 2192 24: 2196  
               Vulnerabilities:Type: itlb_multihit status: Not affected  
               Type: l1tf status: Not affected  
               Type: mds status: Not affected  
               Type: meltdown status: Not affected  
               Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp  
               Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
               Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling  
               Type: srbds status: Not affected  
               Type: tsx_async_abort status: Not affected  
    Graphics:  Device-1: NVIDIA TU104 [GeForce RTX 2080 SUPER] vendor: Gigabyte driver: nouveau v: kernel bus-ID: 09:00.0  
               chip-ID: 10de:1e81 class-ID: 0300  
               Display: x11 server: X.org 1.20.3 compositor: kwin_x11 driver:loaded: modesetting,nouveau unloaded: fbdev,vesa  
               alternate: nv,nvidia resolution: <missing: xdpyinfo>  
               OpenGL:renderer: llvmpipe (LLVM 13.0.0 256 bits) v: 4.5 Mesa 21.2.3 compat-v: 3.1 direct render: Yes  
    Audio:     Device-1: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 09:00.1 chip-ID: 10de:10f8  
               class-ID: 0403  
               Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel  
               bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403  
               Sound Server-1: ALSA v: k5.14.9-1-default running: yes  
               Sound Server-2: PulseAudio v: 15.0 running: yes  
               Sound Server-3: PipeWire v: 0.3.38 running: no  
    Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus-ID: 04:00.0  
               chip-ID: 8086:24fb class-ID: 0280  
               IF: wlp4s0 state: up mac: <filter>  
               Device-2: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel port: f000 bus-ID: 05:00.0  
               chip-ID: 8086:1539 class-ID: 0200  
               IF: enp5s0 state: down mac: <filter>  
    Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-5:2 chip-ID: 8087:0aa7  
               class-ID: e001  
               Report: This feature requires one of these tools: hciconfig/bt-adapter  
    Drives:    Local Storage:total: 931.51 GiB used: 11.04 GiB (1.2%)  
               SMART Message: Unable to run smartctl. Root privileges required.  
               ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WDS100T3X0C-00SJG0 size: 931.51 GiB block-size:
               physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 111110WD scheme: GPT  
    

  7. #7

    Default Re: No GUI on boot

    Code:
    Partition: ID-1: / raw-size: 70.27 GiB size: 70.27 GiB (100.00%) used: 11 GiB (15.7%) fs: btrfs dev: /dev/nvme0n1p5  
               maj-min: 259:5  
               ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 33.4 MiB (34.8%) fs: vfat dev: /dev/nvme0n1p1  
               maj-min: 259:1  
               ID-3: /home raw-size: 70.27 GiB size: 70.27 GiB (100.00%) used: 11 GiB (15.7%) fs: btrfs dev: /dev/nvme0n1p5  
               maj-min: 259:5  
               ID-4: /opt raw-size: 70.27 GiB size: 70.27 GiB (100.00%) used: 11 GiB (15.7%) fs: btrfs dev: /dev/nvme0n1p5  
               maj-min: 259:5  
               ID-5: /var raw-size: 70.27 GiB size: 70.27 GiB (100.00%) used: 11 GiB (15.7%) fs: btrfs dev: /dev/nvme0n1p5  
               maj-min: 259:5  
    Swap:      Kernel:swappiness: 60 (default) cache-pressure: 100 (default)  
               ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:6  
    Sensors:   System Temperatures:cpu: 41.8 C mobo: 16.8 C gpu: nouveau temp: 40.0 C  
               Fan Speeds (RPM): N/A gpu: nouveau fan: 824  
    Info:      Processes: 386 Uptime: N/A wakeups: 0 Memory: 15.55 GiB used: 3.12 GiB (20.1%) Init: systemd v: 249 runlevel: 5  
               target: graphical.target tool: systemctl Compilers:gcc: N/A Packages:rpm: 2173 lib: 1019 flatpak: 0 Shell: Bash  
               v: 5.1.8 running-in: konsole inxi: 3.3.03
    
     
     moz@localhost:~> lsmod | grep 'nvidia' 
    i2c_nvidia_gpu         16384  0 
    moz@localhost:~> lsmod | grep 'nouveau' 
    nouveau              2416640  2 
    video                  57344  1 nouveau
    drm_ttm_helper         16384  1 nouveau
    ttm                    86016  2 drm_ttm_helper,nouveau
    i2c_algo_bit           16384  2 igb,nouveau
    mxm_wmi                16384  1 nouveau
    drm_kms_helper        299008  1 nouveau
    drm                   626688  6 drm_kms_helper,drm_ttm_helper,ttm,nouveau
    wmi                    32768  4 gigabyte_wmi,wmi_bmof,mxm_wmi,nouveau
    button                 24576  1 nouveau
    moz@localhost:~> lsmod | grep 'intel' 
    intel_rapl_msr         20480  0 
    intel_rapl_common      28672  1 intel_rapl_msr 
    snd_hda_intel          57344  4 
    snd_intel_dspcfg       28672  1 snd_hda_intel
    snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg 
    snd_hda_codec         172032  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek 
    snd_hda_core          110592  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek 
    snd_pcm               167936  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core 
    btintel                32768  1 btusb 
    bluetooth             720896  43 btrtl,btintel,btbcm,bnep,btusb,rfcomm 
    snd                   114688  16 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm 
    ghash_clmulni_intel    16384  0 
    aesni_intel           380928  6 
    crypto_simd            16384  1 aesni_intel
    cryptd                 28672  3 crypto_simd,ghash_clmulni_intel
    crc32c_intel           24576  2 
    moz@localhost:~> lsmod | grep 'i915' 
    moz@localhost:~> 

  8. #8

    Default Re: No GUI on boot

    Mobo: Gigabyte model: X570 AORUS ELITE WIFI v: x.x serial: <filter> UEFI: American Megatrends v: F11
    date: 12/06/2019
    Too old BIOS.

  9. #9
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    3,270
    Blog Entries
    1

    Default Re: No GUI on boot

    student penguin
    Quote Originally Posted by thibdb13 View Post
    • sudo lspci -nnk | grep -iA2 vga
    • inxi -aFz
    Everything you asked for from lspci, and is relevant to likely graphical failure issues, is included in the inxi output you asked for. The "kitchen sink" inxi you asked for is loaded with irrelevancies (audio, bluetooth, cpu, disks, machine, network, partitions, sensors, swap, etc) that a more concise inxi -GSaz would exclude. man inxi

    • lsmod | grep 'nvidia' (and 'nouveau', 'intel', 'i915',...)
    Instead:
    Code:
    lsmod | egrep 'nouveau|nvidia|i915|intel'
    (functionally same as grep -e). man grep/egrep
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, TW, 15.3 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.2 on i965P w/ Radeon
    Tertiary: Mageia, Fedora, Debian, more on Kaby Lake & older Intel, AMD, NVidia &&&&&

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •