Black Screen after USB boot, but sound works

Louhy · May 8, 2019

Attempting to install on a new MSI laptop (includes an NVidia 1080).

Followed the install guide using dd to create an install USB with the latest (4.0) iso.
Disabled "secure boot" in BIOS. Fast Boot disabled. Boot mode is UEFI with CSM (this worked well for booting into other distros including Manjaro/Budgie and Ubuntu/Budgie).
I've also been trying Legacy and regular UEFI boot in an effort to get things working (to confuse things further..)

I get to a boot loader screen where I can choose from Solus 4.0 (Budgie) and Reboot Into Firmware Interface.

After booting to Solus, at the very end of log output I did notice that Nouveau complains about these: "secboot:error during falcon reset: -110" "gr: init failed, -110" for a split second before the screen goes dark (i'm only able to read that because sometimes when I restart, it shows again). That error is a little more interesting given that it's just video that isn't working... (Does this call for an obligatory Linux middle finger gif for NVidia?)
I DO hear a 3 tone login chime on startup, even when I only get a black screen.

... while gathering info to post this (rebooting a few times) I seem to have gotten things to work a few times, but not consistently! All I've been changing is the boot mode and secure boot stuff in BIOS. After I boot successfully into a working Solus, if I try a simple "Restart" to verify that I can repeat it... black screen.

I'm still not sure whether this is going to be a problem if I install to disk, but since I can "sometimes" get the boot to work off of USB, I think I'm going to take a leap of faith here and overwrite a Manjaro partition, and hope that this never happens booting from disk. Still I'd be interested in thoughts anyone has about what might be going on here, even if this isn't an issue after install. At the very least maybe this post will help someone else.

Edit - I am able to get a command line terminal up with ctrl-alt-F2, but it prompts for a login.

Louhy · May 10, 2019

Okay, update time. I managed to get installed to disk, but I do still have this startup issue. I've found that I'm able to recover from a "stalled" boot with:
ctrl+alt+F2
(log in)
sudo lightdm

Now, my question is - obviously I'd like to fix/avoid this, but is there any problem (security or otherwise) with doing this for now? I initially tried running lightdm as the regular user, but it said you need sudo (or something to that effect).

And of course, why would this fail the first time but succeed when I run it later?

(I figured I'd try this after looking at the log below, where lightdm fails to start.)

Here's the end of a boot log when it "stalls". I haven't tried it yet but I wouldn't doubt that the live boot is doing the same or similar:

May 10 02:05:00 gt75 NetworkManager[737]: <info>  [1557468300.7822] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
May 10 02:05:00 gt75 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
May 10 02:05:00 gt75 kernel: [drm] Driver supports precise vblank timestamp query.
May 10 02:05:00 gt75 kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
May 10 02:05:00 gt75 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 10 02:05:00 gt75 systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 10 02:05:00 gt75 kernel: ------------[ cut here ]------------
May 10 02:05:00 gt75 kernel: nouveau 0000:01:00.0: timeout
May 10 02:05:00 gt75 kernel: WARNING: CPU: 2 PID: 642 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x188/0x240 [nouveau]
May 10 02:05:00 gt75 kernel: Modules linked in: arc4 cmac bnep snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core ledtrig_audio snd_compress ac97_bus intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp iwlmvm snd_hda_codec btusb iTCO_wdt iTCO_vendor_support btrtl snd_hda_core kvm_intel btbcm mac80211 snd_hwdep btintel kvm iwlwifi snd_pcm irqbypass bluetooth atlantic nouveau(+) snd_timer psmouse efivars msi_wmi wmi_bmof snd intel_wmi_thunderbolt sparse_keymap cfg80211 mxm_wmi i2c_algo_bit soundcore mei_me rfkill mei i2c_i801 thermal fan ac battery evdev tpm_tis tpm_tis_core tpm rng_core acpi_pad button vboxvideo(C) ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm vboxsf(O) binfmt_misc vboxguest hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid sd_mod sdhci_pci xhci_pci cqhci sdhci xhci_hcd serio_raw mmc_core ahci usbcore
May 10 02:05:00 gt75 kernel:  libahci usb_common wmi video
May 10 02:05:00 gt75 kernel: CPU: 2 PID: 642 Comm: systemd-udevd Tainted: G         C O      5.0.7-114.current #1
May 10 02:05:00 gt75 kernel: Hardware name: Micro-Star International Co., Ltd. GT75 Titan 8RG/MS-17A3, BIOS E17A3IMS.108 03/08/2018
May 10 02:05:00 gt75 kernel: RIP: 0010:acr_ls_sec2_post_run+0x188/0x240 [nouveau]
May 10 02:05:00 gt75 kernel: Code: 04 24 48 8b 40 10 48 8b 78 10 4c 8b 77 50 4d 85 f6 74 1e e8 ba 71 22 e1 4c 89 f2 48 c7 c7 ed 2a 68 a0 48 89 c6 e8 c2 a6 bc e0 <0f> 0b e9 26 ff ff ff 4c 8b 77 10 eb dc 8b 43 20 48 c7 c6 10 9c 67
May 10 02:05:00 gt75 kernel: RSP: 0018:ffffc90002aaf678 EFLAGS: 00010286
May 10 02:05:00 gt75 kernel: RAX: 0000000000000000 RBX: ffff8884a6b15b80 RCX: 0000000000000000
May 10 02:05:00 gt75 kernel: RDX: 0000000000000007 RSI: ffffffff820860f2 RDI: 00000000ffffffff
May 10 02:05:00 gt75 kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 000000000000039c
May 10 02:05:00 gt75 kernel: R10: 0000000000000003 R11: 0000000000000000 R12: ffff8884a91b2e00
May 10 02:05:00 gt75 kernel: R13: 0000000000000040 R14: ffff8884aaf38050 R15: 0000000000000005
May 10 02:05:00 gt75 kernel: FS:  00007f6dc8123040(0000) GS:ffff8884ad880000(0000) knlGS:0000000000000000
May 10 02:05:00 gt75 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 10 02:05:00 gt75 kernel: CR2: 00005590cf8b98e0 CR3: 00000004a1de2004 CR4: 00000000003606e0
May 10 02:05:00 gt75 kernel: Call Trace:
May 10 02:05:00 gt75 kernel:  acr_r352_bootstrap+0x19b/0x290 [nouveau]
May 10 02:05:00 gt75 kernel:  acr_r352_reset+0x35/0x220 [nouveau]
May 10 02:05:00 gt75 kernel:  gf100_gr_init_ctxctl_ext+0x6e/0x7d0 [nouveau]
May 10 02:05:00 gt75 kernel:  gf100_gr_init_ctxctl+0x2e/0x2b0 [nouveau]
May 10 02:05:00 gt75 kernel:  ? gf100_gr_init+0x53c/0x580 [nouveau]
May 10 02:05:00 gt75 kernel:  nvkm_engine_init+0xaa/0x1e0 [nouveau]
May 10 02:05:00 gt75 kernel:  nvkm_subdev_init+0xb2/0x200 [nouveau]
May 10 02:05:00 gt75 kernel:  nvkm_engine_ref.part.0+0x43/0x60 [nouveau]
May 10 02:05:00 gt75 kernel:  nvkm_ioctl_new+0x125/0x200 [nouveau]
May 10 02:05:00 gt75 kernel:  ? nvkm_fifo_chan_child_del+0x90/0x90 [nouveau]
May 10 02:05:00 gt75 kernel:  ? gf100_gr_dtor+0xd0/0xd0 [nouveau]
May 10 02:05:00 gt75 kernel:  nvkm_ioctl+0xd8/0x170 [nouveau]
May 10 02:05:00 gt75 kernel:  nvif_object_init+0xbf/0x110 [nouveau]
May 10 02:05:00 gt75 kernel:  nvc0_fbcon_accel_init+0x59/0x910 [nouveau]
May 10 02:05:00 gt75 kernel:  nouveau_fbcon_create+0x545/0x550 [nouveau]
May 10 02:05:00 gt75 kernel:  ? preempt_count_add+0x79/0xb0
May 10 02:05:00 gt75 kernel:  __drm_fb_helper_initial_config_and_unlock+0x1cf/0x430 [drm_kms_helper]
May 10 02:05:00 gt75 kernel:  nouveau_fbcon_init+0x179/0x1d0 [nouveau]
May 10 02:05:00 gt75 kernel:  nouveau_drm_device_init+0x462/0x810 [nouveau]
May 10 02:05:00 gt75 kernel:  ? pci_bus_read_config_word+0x49/0x70
May 10 02:05:00 gt75 kernel:  nouveau_drm_probe+0x265/0x2d0 [nouveau]
May 10 02:05:00 gt75 kernel:  ? _raw_spin_unlock_irqrestore+0x18/0x30
May 10 02:05:00 gt75 kernel:  local_pci_probe+0x41/0x90
May 10 02:05:00 gt75 kernel:  pci_device_probe+0x115/0x190
May 10 02:05:00 gt75 kernel:  really_probe+0xf3/0x2b0
May 10 02:05:00 gt75 kernel:  driver_probe_device+0x4f/0xc0
May 10 02:05:00 gt75 kernel:  __driver_attach+0xb4/0xd0
May 10 02:05:00 gt75 kernel:  ? driver_probe_device+0xc0/0xc0
May 10 02:05:00 gt75 kernel:  bus_for_each_dev+0x77/0xc0
May 10 02:05:00 gt75 kernel:  bus_add_driver+0x19c/0x1e0
May 10 02:05:00 gt75 kernel:  ? 0xffffffffa06e6000
May 10 02:05:00 gt75 kernel:  driver_register+0x6b/0xb0
May 10 02:05:00 gt75 kernel:  ? 0xffffffffa06e6000
May 10 02:05:00 gt75 kernel:  do_one_initcall+0x46/0x1ea
May 10 02:05:00 gt75 kernel:  ? free_unref_page_commit.isra.20+0x64/0xd0
May 10 02:05:00 gt75 kernel:  ? kmem_cache_alloc_trace+0x160/0x1b0
May 10 02:05:00 gt75 kernel:  ? do_init_module+0x22/0x210
May 10 02:05:00 gt75 kernel:  do_init_module+0x5a/0x210
May 10 02:05:00 gt75 kernel:  load_module+0x123f/0x1300
May 10 02:05:00 gt75 kernel:  __se_sys_finit_module+0xb1/0xd0
May 10 02:05:00 gt75 kernel:  do_syscall_64+0x5f/0x170
May 10 02:05:00 gt75 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 10 02:05:00 gt75 kernel: RIP: 0033:0x7f6dc8300749
May 10 02:05:00 gt75 kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 07 07 0d 00 f7 d8 64 89 01 48
May 10 02:05:00 gt75 kernel: RSP: 002b:00007ffe196fadd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
May 10 02:05:00 gt75 kernel: RAX: ffffffffffffffda RBX: 0000564cb5d7a520 RCX: 00007f6dc8300749
May 10 02:05:00 gt75 kernel: RDX: 0000000000000000 RSI: 00007f6dc81e7aa7 RDI: 0000000000000010
May 10 02:05:00 gt75 kernel: RBP: 0000564cb5d7a520 R08: 0000000000000000 R09: 0000564c00020000
May 10 02:05:00 gt75 kernel: R10: 0000000000000010 R11: 0000000000000246 R12: 0000564cb5d7a520
May 10 02:05:00 gt75 kernel: R13: 00007f6dc81e7aa7 R14: 0000000000000000 R15: 0000564cb5d7c890
May 10 02:05:00 gt75 kernel: ---[ end trace df621dca5e98bcaf ]---
May 10 02:05:01 gt75 kernel: psmouse serio1: synaptics: queried max coordinates: x [..5656], y [..4728]
May 10 02:05:01 gt75 kernel: psmouse serio1: synaptics: queried min coordinates: x [1284..], y [1128..]
May 10 02:05:01 gt75 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN1509 SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
May 10 02:05:01 gt75 systemd[1]: Stopped Display Manager.
May 10 02:05:01 gt75 systemd[1]: Starting Display Manager...
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.0693] keyfile: add connection /var/run/NetworkManager/system-connections/Wired connection 1.nmconnection (265c35a7-cdfb-3e29-8fdf-0cd2d88f43c6,"Wired connection 1")
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.0697] settings: (enp2s0): created default wired connection 'Wired connection 1'
May 10 02:05:01 gt75 NetworkManager[737]: <warn>  [1557468301.0700] device (enp2s0): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
May 10 02:05:01 gt75 systemd[1]: Started Display Manager.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 10 02:05:01 gt75 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00323/0x840300/0x26800/0x0, board id: 3163, fw id: 2286728
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1096] sup-iface[0x19f0910,wlp3s0]: supports 5 scan SSIDs
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1101] device (wlp3s0): supplicant interface state: starting -> ready
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1101] Wi-Fi P2P device controlled by interface wlp3s0 created
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1103] manager: (p2p-dev-wlp3s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1106] device (p2p-dev-wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
May 10 02:05:01 gt75 NetworkManager[737]: <warn>  [1557468301.1110] sup-iface: failed to cancel p2p connect: P2P cancel failed
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1111] device (p2p-dev-wlp3s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
May 10 02:05:01 gt75 NetworkManager[737]: <info>  [1557468301.1112] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
May 10 02:05:01 gt75 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
May 10 02:05:01 gt75 systemd[1]: Stopped Display Manager.
May 10 02:05:01 gt75 systemd[1]: Starting Display Manager...
May 10 02:05:01 gt75 systemd[1]: Started Display Manager.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
May 10 02:05:01 gt75 systemd[1]: Stopped Display Manager.
May 10 02:05:01 gt75 systemd[1]: Starting Display Manager...
May 10 02:05:01 gt75 systemd[1]: Started Display Manager.
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 10 02:05:01 gt75 systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
May 10 02:05:02 gt75 systemd[1]: Stopped Display Manager.
May 10 02:05:02 gt75 systemd[1]: Starting Display Manager...
May 10 02:05:02 gt75 systemd[1]: Started Display Manager.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
May 10 02:05:02 gt75 systemd[1]: Stopped Display Manager.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Start request repeated too quickly.
May 10 02:05:02 gt75 systemd[1]: lightdm.service: Failed with result 'exit-code'.
May 10 02:05:02 gt75 systemd[1]: Failed to start Display Manager.
May 10 02:05:02 gt75 kernel: nouveau 0000:01:00.0: secboot: error during falcon reset: -110
May 10 02:05:02 gt75 kernel: nouveau 0000:01:00.0: gr: init failed, -110
May 10 02:05:02 gt75 kernel: nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x200000, bo 000000005fb6d82a
May 10 02:05:02 gt75 kernel: fbcon: nouveaufb (fb0) is primary device
May 10 02:05:03 gt75 kernel: nouveau 0000:01:00.0: disp: 0x000063b6[0]: INIT_GENERIC_CONDITON: unknown 0x07
May 10 02:05:03 gt75 kernel: nouveau 0000:01:00.0: disp: 0x00005f47[2]: INIT_GENERIC_CONDITON: unknown 0x07
May 10 02:05:03 gt75 kernel: Console: switching to colour frame buffer device 240x67
May 10 02:05:03 gt75 kernel: nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
May 10 02:05:03 gt75 kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
May 10 02:05:03 gt75 systemd[1]: Created slice system-systemd\x2dbacklight.slice.
May 10 02:05:03 gt75 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:nv_backlight...
May 10 02:05:03 gt75 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
May 10 02:05:03 gt75 systemd-backlight[837]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
May 10 02:05:03 gt75 systemd[1]: systemd-backlight@backlight:acpi_video0.service: Main process exited, code=exited, status=1/FAILURE
May 10 02:05:03 gt75 systemd[1]: systemd-backlight@backlight:acpi_video0.service: Failed with result 'exit-code'.
May 10 02:05:03 gt75 systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
May 10 02:05:03 gt75 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:nv_backlight.
May 10 02:05:05 gt75 kernel: atlantic: link change old 0 new 1000
May 10 02:05:05 gt75 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6249] device (enp2s0): carrier: link connected
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6260] device (enp2s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6278] policy: auto-activating connection 'Wired connection 1' (265c35a7-cdfb-3e29-8fdf-0cd2d88f43c6)
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6292] device (enp2s0): Activation: starting connection 'Wired connection 1' (265c35a7-cdfb-3e29-8fdf-0cd2d88f43c6)
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6292] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6294] manager: NetworkManager state is now CONNECTING
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6295] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6299] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6304] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6318] dhcp4 (enp2s0): dhclient started with pid 839
May 10 02:05:05 gt75 avahi-daemon[738]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::a909:f08b:b641:f84b.
May 10 02:05:05 gt75 avahi-daemon[738]: New relevant interface enp2s0.IPv6 for mDNS.
May 10 02:05:05 gt75 avahi-daemon[738]: Registering new address record for fe80::a909:f08b:b641:f84b on enp2s0.*.
May 10 02:05:05 gt75 dhclient[839]: DHCPREQUEST for 192.168.0.3 on enp2s0 to 255.255.255.255 port 67
May 10 02:05:05 gt75 dhclient[839]: DHCPACK of 192.168.0.3 from 192.168.0.1
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6781] dhcp4 (enp2s0):   address 192.168.0.3
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6782] dhcp4 (enp2s0):   plen 24 (255.255.255.0)
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6782] dhcp4 (enp2s0):   gateway 192.168.0.1
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6783] dhcp4 (enp2s0):   lease time 604800
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6783] dhcp4 (enp2s0):   hostname 'gt75'
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6783] dhcp4 (enp2s0):   nameserver '68.105.28.11'
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6783] dhcp4 (enp2s0):   nameserver '68.105.29.11'
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6784] dhcp4 (enp2s0):   nameserver '68.105.28.12'
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6784] dhcp4 (enp2s0): state changed unknown -> bound
May 10 02:05:05 gt75 avahi-daemon[738]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.0.3.
May 10 02:05:05 gt75 avahi-daemon[738]: New relevant interface enp2s0.IPv4 for mDNS.
May 10 02:05:05 gt75 avahi-daemon[738]: Registering new address record for 192.168.0.3 on enp2s0.IPv4.
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6804] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6819] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6824] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May 10 02:05:05 gt75 dhclient[839]: bound to 192.168.0.3 -- renewal in 240458 seconds.
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6834] manager: NetworkManager state is now CONNECTED_LOCAL
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6875] manager: NetworkManager state is now CONNECTED_SITE
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6878] policy: set 'Wired connection 1' (enp2s0) as default for IPv4 routing and DNS
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6920] device (enp2s0): Activation: successful, device activated.
May 10 02:05:05 gt75 NetworkManager[737]: <info>  [1557468305.6938] manager: startup complete
May 10 02:05:05 gt75 nm-dispatcher[771]: req:3 'up' [enp2s0]: new request (1 scripts)
May 10 02:05:05 gt75 nm-dispatcher[771]: req:3 'up' [enp2s0]: start running ordered scripts...
May 10 02:05:05 gt75 systemd-resolved[626]: Using degraded feature set (UDP+EDNS0) for DNS server 68.105.28.11.
May 10 02:05:05 gt75 systemd-resolved[626]: DNSSEC validation failed for question getsol.us IN DS: failed-auxiliary
May 10 02:05:05 gt75 systemd-resolved[626]: DNSSEC validation failed for question us IN SOA: failed-auxiliary
May 10 02:05:05 gt75 systemd-resolved[626]: Server 68.105.28.11 does not support DNSSEC, downgrading to non-DNSSEC mode.
May 10 02:05:05 gt75 systemd-resolved[626]: DNSSEC validation failed for question getsol.us IN AAAA: failed-auxiliary
May 10 02:05:06 gt75 NetworkManager[737]: <info>  [1557468306.0065] manager: NetworkManager state is now CONNECTED_GLOBAL
May 10 02:05:06 gt75 nm-dispatcher[771]: req:4 'connectivity-change': new request (1 scripts)
May 10 02:05:06 gt75 nm-dispatcher[771]: req:4 'connectivity-change': start running ordered scripts...
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.0967] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.0995] dhcp6 (enp2s0): dhclient started with pid 856
May 10 02:05:07 gt75 avahi-daemon[738]: Leaving mDNS multicast group on interface enp2s0.IPv6 with address fe80::a909:f08b:b641:f84b.
May 10 02:05:07 gt75 avahi-daemon[738]: Joining mDNS multicast group on interface enp2s0.IPv6 with address 2600:8806:3000:3e:a362:db0f:4d60:48c7.
May 10 02:05:07 gt75 avahi-daemon[738]: Registering new address record for 2600:8806:3000:3e:a362:db0f:4d60:48c7 on enp2s0.*.
May 10 02:05:07 gt75 avahi-daemon[738]: Withdrawing address record for fe80::a909:f08b:b641:f84b on enp2s0.
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.1021] policy: set 'Wired connection 1' (enp2s0) as default for IPv6 routing and DNS
May 10 02:05:07 gt75 dhclient[856]: XMT: Confirm on enp2s0, interval 1040ms.
May 10 02:05:07 gt75 dhclient[856]: RCV: Reply message on enp2s0 from fe80::461c:12ff:fe04:e93d.
May 10 02:05:07 gt75 dhclient[856]: message status code Success: "Your addresses are correct for this link! Yay!"
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   valid_lft 604800
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   preferred_lft 604800
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   address 2600:8806:3000:3e::bcb2
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   nameserver '2001:578:3f::30'
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   nameserver '2001:578:3f:1::30'
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   nameserver '2001:578:3f::30'
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0):   nameserver '2001:578:3f:1::30'
May 10 02:05:07 gt75 NetworkManager[737]: <info>  [1557468307.5465] dhcp6 (enp2s0): state changed unknown -> bound, event ID="23:8f:90:a1|1557386125"
May 10 02:05:07 gt75 avahi-daemon[738]: Registering new address record for 2600:8806:3000:3e::bcb2 on enp2s0.*.
May 10 02:05:07 gt75 nm-dispatcher[771]: req:5 'dhcp6-change' [enp2s0]: new request (1 scripts)
May 10 02:05:07 gt75 nm-dispatcher[771]: req:5 'dhcp6-change' [enp2s0]: start running ordered scripts...
May 09 22:05:28 gt75 systemd-timesyncd[623]: Synchronized to time server [2001:4860:4806:8::]:123 (time3.google.com).
May 09 22:07:20 gt75 login[760]: gkr-pam: unable to locate daemon control file
May 09 22:07:20 gt75 login[760]: pam_unix(login:session): session opened for user lou by LOGIN(uid=0)
May 09 22:07:20 gt75 login[760]: gkr-pam: unable to locate daemon control file
May 09 22:07:20 gt75 systemd[1]: Created slice User Slice of UID 1000.
May 09 22:07:20 gt75 systemd[1]: Created slice system-user\x2druntime\x2ddir.slice.
May 09 22:07:20 gt75 systemd[1]: Started /run/user/1000 mount wrapper.
May 09 22:07:20 gt75 systemd[1]: Starting User Manager for UID 1000...
May 09 22:07:20 gt75 systemd-logind[733]: New session 1 of user lou.
May 09 22:07:20 gt75 systemd[893]: pam_unix(systemd-user:session): session opened for user lou by (uid=0)
May 09 22:07:20 gt75 systemd[1]: Started Session 1 of user lou.
May 09 22:07:21 gt75 systemd[893]: Starting D-Bus User Message Bus Socket.
May 09 22:07:21 gt75 systemd[893]: Reached target Timers.
May 09 22:07:21 gt75 systemd[893]: Reached target Paths.
May 09 22:07:21 gt75 systemd[893]: Listening on D-Bus User Message Bus Socket.
May 09 22:07:21 gt75 systemd[893]: Reached target Sockets.
May 09 22:07:21 gt75 systemd[893]: Reached target Basic System.
May 09 22:07:21 gt75 systemd[1]: Started User Manager for UID 1000.
May 09 22:07:21 gt75 systemd[893]: Starting Initialise XDG User Directories...
May 09 22:07:21 gt75 systemd[893]: Started Initialise XDG User Directories.
May 09 22:07:21 gt75 systemd[893]: Reached target Default.
May 09 22:07:21 gt75 systemd[893]: Startup finished in 43ms.
May 09 22:07:43 gt75 sudo[909]:      lou : TTY=tty1 ; PWD=/home/lou ; USER=root ; COMMAND=/usr/bin/journalctl -b
May 09 22:07:43 gt75 sudo[909]: pam_unix(sudo:session): session opened for user root by lou(uid=0)
May 09 22:15:03 gt75 systemd-resolved[626]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 68.105.28.11.
May 09 22:15:03 gt75 systemd-resolved[626]: Using degraded feature set (UDP+EDNS0) for DNS server 68.105.28.11.
May 09 22:15:03 gt75 systemd-resolved[626]: DNSSEC validation failed for question getsol.us IN DS: failed-auxiliary
May 09 22:15:03 gt75 systemd-resolved[626]: DNSSEC validation failed for question getsol.us IN SOA: failed-auxiliary
May 09 22:15:03 gt75 systemd-resolved[626]: DNSSEC validation failed for question getsol.us IN A: failed-auxiliary
May 09 22:15:45 gt75 sudo[909]: pam_unix(sudo:session): session closed for user root
May 09 22:16:14 gt75 sudo[929]: pam_unix(sudo:auth): authentication failure; logname=lou uid=1000 euid=0 tty=/dev/tty1 ruser=lou rhost=  user=lou
May 09 22:16:18 gt75 sudo[929]:      lou : TTY=tty1 ; PWD=/home/lou ; USER=root ; COMMAND=/usr/bin/journalctl -b
May 09 22:16:18 gt75 sudo[929]: pam_unix(sudo:session): session opened for user root by lou(uid=0)
May 09 22:16:18 gt75 sudo[929]: pam_unix(sudo:session): session closed for user root
May 09 22:16:27 gt75 sudo[933]:      lou : TTY=tty1 ; PWD=/home/lou ; USER=root ; COMMAND=/usr/bin/journalctl -b
May 09 22:16:27 gt75 sudo[933]: pam_unix(sudo:session): session opened for user root by lou(uid=0)

So far when I do the "sudo lightdm" I've noticed that it requires a password to reboot or shut down, so that has me concerned that this isn't really such a good temporary fix.

Louhy · May 10, 2019

Ugh. Well it seems like installing proprietary drivers via DoFlicky in "Hardware Drivers" may have fixed it, will revisit if that turns out to be false. Unfortunately that doesn't make a live USB boot work any better.

kyrios · May 10, 2019

Which drivers were installed the Nvidia ones?
Then you have to append nomodeset or eventually nouveau.modeset=0 to the kernel parameters of the live ISO.
just spam the space bar when the computer starts to show the boot menu then press e to add the extra parameters.

Louhy · May 11, 2019

The log has nouveau all over it. I installed NVidia's driver to get things working more reliably.

Didn't know about the space bar - will have to try that out.

Edit: Ok, turns out all I need to use nomodeset with the USB I have is to press e when it prompts for Solus or "firmware". Didn't look like Grub to me, I'm used to the old upper-left raw text Grub menu!

[deleted] · May 11, 2019

kyrios Yeah my Solus installation on my desktop with Nvidia GPU suddenly booted into completely black screen, not even a cursor in output. Made my Solus useless

kyrios · May 11, 2019

[deleted] When you hit continuously the spacebar during the normal boot (not the usb live iso), it doesn't show the boot menu (from which you can select the previous version of the kernel) ?

If not, you can do a boot rescue and either append the nomodeset to the kernel parameters or revert the last updates (I guess this occurred after some updates or so) ?

Note to everybody: There is a doc link on the top navigation bar, use it, it's not there just as a decoration item !

Louhy · May 11, 2019

kyrios There is a doc link on the top navigation bar, use it, it's not there just as a decoration item !

It's great, very helpful, definitely a factor in spurring my interest in Solus.

Looks like a kernel update went out 6 days ago, maybe that's what's causing these black screen reports? I thought newer kernels were supposed to resolve these things. Maybe I'll try a switch back to nouveau on the spare laptop later so I can see if the older kernel works more reliably.

Found a few references to driver changes in change logs here but nothing stands out to me..

[deleted] · May 11, 2019

kyrios Yes, this occurred after recent updates.