You are not logged in.

#1 2019-06-14 04:01:37

Jekuma
Member
Registered: 2019-02-24
Posts: 7

[SOLVED] Getty is Unseeable after Installing Nvidia Drivers

Okay, I have installed Arch on a computer with a Nvidia Geforce 1050 GPU. Initially, when I used the nouveau drivers everything worked normally. However once I installed the proprietary Nvidia driver, getty stopped being visible. Getty still does work and whatnot -- I just have to enter my login credentials and from there type 'startx' to get back to i3.

I ran journalctl -xe and nothing appeared to be off:

[jerry@jerry ~]$ journalctl -x
-- Logs begin at Thu 2019-06-13 20:09:59 EDT, end at Thu 2019-06-13 23:44:25 EDT. --
Jun 13 20:09:59 jerry kernel: Linux version 5.1.9-arch1-1-ARCH (builduser@heftig-25959) (gcc version 8.3.0 (GCC)) #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC>
Jun 13 20:09:59 jerry kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=5661c17a-9cbd-4da9-a85b-eb18d925de9a rw quiet
Jun 13 20:09:59 jerry kernel: KERNEL supported cpus:
Jun 13 20:09:59 jerry kernel:   Intel GenuineIntel
Jun 13 20:09:59 jerry kernel:   AMD AuthenticAMD
Jun 13 20:09:59 jerry kernel:   Hygon HygonGenuine
Jun 13 20:09:59 jerry kernel:   Centaur CentaurHauls
Jun 13 20:09:59 jerry kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 13 20:09:59 jerry kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 13 20:09:59 jerry kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 13 20:09:59 jerry kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Jun 13 20:09:59 jerry kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Jun 13 20:09:59 jerry kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 13 20:09:59 jerry kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Jun 13 20:09:59 jerry kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Jun 13 20:09:59 jerry kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Jun 13 20:09:59 jerry kernel: BIOS-provided physical RAM map:
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000a307afff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000a307b000-0x00000000a30b1fff] ACPI data
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000a30b2000-0x00000000a4a91fff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000a4a92000-0x00000000a4a92fff] ACPI NVS
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000a4a93000-0x00000000a4a93fff] reserved
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000a4a94000-0x00000000b1527fff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b1528000-0x00000000b23a6fff] reserved
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b23a7000-0x00000000b23cffff] ACPI data
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b23d0000-0x00000000b24cbfff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b24cc000-0x00000000b27f3fff] ACPI NVS
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b27f4000-0x00000000b332bfff] reserved
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b332c000-0x00000000b33a1fff] type 20
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b33a2000-0x00000000b33fffff] usable
Jun 13 20:09:59 jerry kernel: BIOS-e820: [mem 0x00000000b3400000-0x00000000b7ffffff] reserved
[jerry@jerry ~]$ journalctl -xe
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Subject: A start job for unit session-1.scope has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit session-1.scope has finished successfully.
-- 
-- The job identifier is 1141.
Jun 13 23:44:13 jerry systemd[560]: Started D-Bus User Message Bus.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 16.
Jun 13 23:44:15 jerry systemd[1]: systemd-hostnamed.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-hostnamed.service has successfully entered the 'dead' state.
Jun 13 23:44:15 jerry audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd>
Jun 13 23:44:15 jerry kernel: audit: type=1131 audit(1560483855.840:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="sy>
Jun 13 23:44:23 jerry systemd[560]: Starting Sound Service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 31.
Jun 13 23:44:23 jerry dbus-daemon[466]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' request>
Jun 13 23:44:23 jerry systemd[1]: Starting RealtimeKit Scheduling Policy Service...
-- Subject: A start job for unit rtkit-daemon.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit rtkit-daemon.service has begun execution.
-- 
-- The job identifier is 1229.
Jun 13 23:44:23 jerry dbus-daemon[466]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Jun 13 23:44:23 jerry systemd[1]: Started RealtimeKit Scheduling Policy Service.
-- Subject: A start job for unit rtkit-daemon.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit rtkit-daemon.service has finished successfully.
-- 
-- The job identifier is 1229.
Jun 13 23:44:23 jerry audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/sys>
Jun 13 23:44:23 jerry rtkit-daemon[734]: Successfully called chroot.
Jun 13 23:44:23 jerry kernel: audit: type=1130 audit(1560483863.750:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd>
Jun 13 23:44:23 jerry rtkit-daemon[734]: Successfully dropped privileges.
Jun 13 23:44:23 jerry rtkit-daemon[734]: Successfully limited resources.
Jun 13 23:44:23 jerry rtkit-daemon[734]: Running.
Jun 13 23:44:23 jerry rtkit-daemon[734]: Watchdog thread running.
Jun 13 23:44:23 jerry rtkit-daemon[734]: Canary thread running.
Jun 13 23:44:23 jerry rtkit-daemon[734]: Successfully made thread 733 of process 733 owned by '1000' high priority at nice level -11.
Jun 13 23:44:23 jerry rtkit-daemon[734]: Supervising 1 threads of 1 processes of 1 users.
Jun 13 23:44:24 jerry rtkit-daemon[734]: Supervising 1 threads of 1 processes of 1 users.
Jun 13 23:44:24 jerry rtkit-daemon[734]: Successfully made thread 746 of process 733 owned by '1000' RT at priority 5.
Jun 13 23:44:24 jerry rtkit-daemon[734]: Supervising 2 threads of 1 processes of 1 users.
Jun 13 23:44:25 jerry rtkit-daemon[734]: Supervising 2 threads of 1 processes of 1 users.
Jun 13 23:44:25 jerry rtkit-daemon[734]: Successfully made thread 747 of process 733 owned by '1000' RT at priority 5.
Jun 13 23:44:25 jerry rtkit-daemon[734]: Supervising 3 threads of 1 processes of 1 users.
Jun 13 23:44:25 jerry rtkit-daemon[734]: Supervising 3 threads of 1 processes of 1 users.
Jun 13 23:44:25 jerry rtkit-daemon[734]: Successfully made thread 748 of process 733 owned by '1000' RT at priority 5.
Jun 13 23:44:25 jerry rtkit-daemon[734]: Supervising 4 threads of 1 processes of 1 users.
Jun 13 23:44:25 jerry systemd[560]: Started Sound Service.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 31.
Jun 13 23:44:25 jerry bluetoothd[468]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource
Jun 13 23:44:25 jerry bluetoothd[468]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink
Jun 13 23:44:25 jerry pulseaudio[733]: E: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.E>
Jun 13 23:44:25 jerry kernel: Bluetooth: RFCOMM TTY layer initialized
Jun 13 23:44:25 jerry kernel: Bluetooth: RFCOMM socket layer initialized
Jun 13 23:44:25 jerry kernel: Bluetooth: RFCOMM ver 1.11
lines 1984-2019/2019 (END)

I definitely know that this isn't the best way to check the nvidia driver's status. So can somebody push me in the right direction into not only fixing this, but to self diagnose these types of issues in the future?

Last edited by Jekuma (2019-06-15 01:31:21)

Offline

#2 2019-06-14 05:24:01

seth
Member
Registered: 2012-09-03
Posts: 51,056

Offline

#3 2019-06-14 06:40:04

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,672

Re: [SOLVED] Getty is Unseeable after Installing Nvidia Drivers

Alternatively, or if you aren't using GRUB, enable KMS by adding nvidia-drm.modeset=1 to your kernel parameters or an appropriate line in /etc/modprobe.d

Offline

#4 2019-06-14 16:53:06

Jekuma
Member
Registered: 2019-02-24
Posts: 7

Re: [SOLVED] Getty is Unseeable after Installing Nvidia Drivers

Nope, tried both methods. Neither method worked.

Offline

#5 2019-06-14 21:09:07

seth
Member
Registered: 2012-09-03
Posts: 51,056

Re: [SOLVED] Getty is Unseeable after Installing Nvidia Drivers

Offline

#6 2019-06-14 23:39:30

Jekuma
Member
Registered: 2019-02-24
Posts: 7

Re: [SOLVED] Getty is Unseeable after Installing Nvidia Drivers

seth wrote:

I'm not sure, this is a desktop system that has both the iGPU (Intel HD Graphics) and the dedicated GPU (GeForce 1050) enabled.

EDIT: turns out that kernel was not loading in the nvidia driver during start. Simply adding

nvidia

along with

nvidia-drm.modeset=1

into kernel parameters fixes this.

Last edited by Jekuma (2019-06-15 01:51:45)

Offline

Board footer

Powered by FluxBB