Manjaro install of Nvidia driver Boot hangs

File Case # #191011-000632

I installed Manjaro 11,10 on my computer with a GTX960 Nvidia card. I had a video driver but it was the free opensource. The proprietory software was from nvidia and I used: both the Manjaro Settings (second one on the list?) on the Menu (I am using Linux mint when I am doing this so it is from memory) which took a long time and I hoped would work but it didn’t and :
sudo mhwd -a pci nonfree 0300 .
After a reboot both ways left me with the booting stuck at "started TLP System startup/shutdown. Using CTRL F2 I got a tty signin and ended up with a tty connection that I could not get the graphics to load from. I know that this problem is associated with the graphics driver from reading on the Internet and my experience. I also know that the problem is intimately associated with my hardware ( see inxi…). I installed Manjaro on another computer with no problem with the graphics driver. I installed the manjaro 18.10 on this computer on a 1Tb Toshiba USB drive. On the Nvidia website they said to use the 430 driver but the results of the installations use the 435. I tried to get information that I saw asked for on the Internet. I really don’t understand what I am doing but if you have something to start with it may help. Tell me what I have to give you.

The journalctl -xe -p3 -b > ManLog.txt came after an attempted boot and I got to the tty to sign in and put in the command. It stopped at the next thing which was started light display manager.

I saw in my grub /etc/defaults/grub that it did not have nouveau.modeset=0 but I was not able to do a update-grub. I got an error message that I forgot but I will get it to you if I need to. I had to use the live CD and chroot to do it but I never got anywhere. This is a recurring problem I saw on the Internet. I could not find a clear answer and I think there is a real problem between the driver and my hardware. I hope you can help me. Manjaro worke well for what I saw of it.

I sent files like the printout of my hardware, a journalctl printout, a xorg.o.log, system.journal, a user-1000journal but there is no place for attachments. I am not a professional just a user with a card that the driver has problems under Manjaro.

xorg.0.log
[ 24.666]
X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
[ 24.666] Build Operating System: Linux Arch Linux
[ 24.666] Current Operating System: Linux edwardM 5.2.11-1-MANJARO #1 SMP PREEMPT Thu Aug 29 07:41:24 UTC 2019 x86_64
[ 24.666] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.2-x86_64 root=UUID=1e6b9bac-58b4-4b3c-ac82-7fe6db78b537 rw quiet apparmor=1 security=apparmor resume=UUID=f3cfa22c-be47-459a-bf7d-e2eb5015973c udev.log_priority=3
[ 24.666] Build Date: 14 August 2019 10:50:56PM
[ 24.666]
[ 24.666] Current version of pixman: 0.38.4
[ 24.666] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 24.666] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 24.667] (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Oct 11 17:16:37 2019
[ 24.667] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 24.667] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 24.667] (==) ServerLayout “layout”
[ 24.667] (
) |–>Screen “Screen0” (0)
[ 24.667] () | |–>Monitor “Monitor0”
[ 24.667] (
) | |–>Device “Device0”
[ 24.667] (==) Automatically adding devices
[ 24.667] (==) Automatically enabling devices
[ 24.667] (==) Automatically adding GPU devices
[ 24.667] (==) Automatically binding GPU devices
[ 24.667] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 24.667] (WW) The directory “/usr/share/fonts/OTF” does not exist.
[ 24.667] Entry deleted from font path.
[ 24.667] (WW) The directory “/usr/share/fonts/Type1” does not exist.
[ 24.667] Entry deleted from font path.
[ 24.667] (WW) fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi". [ 24.667] Entry deleted from font path. [ 24.667] (Run 'mkfontdir' on "/usr/share/fonts/100dpi"). [ 24.667] (WW) fonts.dir’ not found (or not valid) in “/usr/share/fonts/75dpi”.
[ 24.667] Entry deleted from font path.
[ 24.667] (Run ‘mkfontdir’ on “/usr/share/fonts/75dpi”).
[ 24.667] (==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/TTF
[ 24.667] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 24.667] (**) Extension “COMPOSITE” is enabled
[ 24.667] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 24.667] (II) Module ABI versions:
[ 24.667] X.Org ANSI C Emulation: 0.4
[ 24.667] X.Org Video Driver: 24.0
[ 24.667] X.Org XInput driver : 24.1
[ 24.667] X.Org Server Extension : 10.0
[ 24.668] (++) using VT number 7

[ 24.668] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 24.669] (–) PCI:*(1@0:0:0) 10de:1401:103c:2b4d rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x???/131072
[ 24.669] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 24.669] (II) LoadModule: “glx”
[ 24.669] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 24.670] (II) Module glx: vendor=“X.Org Foundation”
[ 24.670] compiled for 1.20.5, module version = 1.0.0
[ 24.670] ABI class: X.Org Server Extension, version 10.0
[ 24.670] (II) LoadModule: “nvidia”
[ 24.670] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 24.670] (II) Module nvidia: vendor=“NVIDIA Corporation”
[ 24.670] compiled for 1.6.99.901, module version = 1.0.0
[ 24.670] Module class: X.Org Video Driver
[ 24.670] (II) NVIDIA dlloader X Driver 435.21 Sun Aug 25 08:17:08 CDT 2019
[ 24.670] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 24.670] (II) Loading sub module “fb”
[ 24.670] (II) LoadModule: “fb”
[ 24.670] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 24.670] (II) Module fb: vendor=“X.Org Foundation”
[ 24.670] compiled for 1.20.5, module version = 1.0.0
[ 24.670] ABI class: X.Org ANSI C Emulation, version 0.4
[ 24.670] (II) Loading sub module “wfb”
[ 24.670] (II) LoadModule: “wfb”
[ 24.670] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 24.670] (II) Module wfb: vendor=“X.Org Foundation”
[ 24.670] compiled for 1.20.5, module version = 1.0.0
[ 24.670] ABI class: X.Org ANSI C Emulation, version 0.4
[ 24.670] (II) Loading sub module “ramdac”
[ 24.670] (II) LoadModule: “ramdac”
[ 24.670] (II) Module “ramdac” already built-in
[ 24.805] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 24.805] (EE) NVIDIA: system’s kernel log for additional error messages and
[ 24.805] (EE) NVIDIA: consult the NVIDIA README for details.
[ 24.805] (EE) No devices detected.
[ 24.805] (EE)
Fatal server error:
[ 24.805] (EE) no screens found(EE)
[ 24.805] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 24.805] (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
[ 24.805] (EE)
[ 24.830] (EE) Server terminated with error (1). Closing log file.

journalctl -xe -p3 -b > ManLog.txt

– Logs begin at Fri 2019-10-11 16:02:16 KST, end at Sat 2019-10-12 06:24:15 KST. –
Oct 12 06:22:30 edwardM kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Oct 12 06:22:30 edwardM kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Oct 12 06:22:30 edwardM kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method _SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method _SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method _SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method _SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: ACPI Error: Aborting method _SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: kvm: disabled by bios
Oct 12 06:22:30 edwardM kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
Oct 12 06:22:26 edwardM systemd-modules-load[323]: Failed to insert module ‘nvidia’: Invalid argument
Oct 12 06:22:27 edwardM systemd-modules-load[323]: Failed to insert module ‘nvidia_drm’: Invalid argument
Oct 12 06:22:27 edwardM systemd[1]: Failed to start Load Kernel Modules.
– Subject: A start job for unit systemd-modules-load.service has failed
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance

– A start job for unit systemd-modules-load.service has finished with a failure.

– The job identifier is 48 and the job result is failed.
Oct 12 06:22:29 edwardM systemd-modules-load[580]: Failed to insert module ‘nvidia’: Invalid argument
Oct 12 06:22:29 edwardM systemd-modules-load[580]: Failed to insert module ‘nvidia_drm’: Invalid argument
Oct 12 06:22:29 edwardM systemd[1]: Failed to start Load Kernel Modules.
– Subject: A start job for unit systemd-modules-load.service has failed
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance

– A start job for unit systemd-modules-load.service has finished with a failure.

– The job identifier is 176 and the job result is failed.
Oct 12 06:22:30 edwardM systemd-modules-load[590]: Failed to insert module ‘nvidia’: Invalid argument
Oct 12 06:22:30 edwardM systemd-modules-load[590]: Failed to insert module ‘nvidia_drm’: Invalid argument
Oct 12 06:22:30 edwardM systemd[1]: Failed to start Load Kernel Modules.
– Subject: A start job for unit systemd-modules-load.service has failed
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance

– A start job for unit systemd-modules-load.service has finished with a failure.

– The job identifier is 397 and the job result is failed.
Oct 12 06:22:40 edwardM systemd[1]: Failed to start Light Display Manager.
– Subject: A start job for unit lightdm.service has failed
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance

– A start job for unit lightdm.service has finished with a failure.

– The job identifier is 1207 and the job result is failed.
Oct 12 06:24:14 edwardM kernel: scsi 6:0:0:0: rejecting I/O to dead device

inxi -MGCN (hardware Other computer no problem with different Nvidia card)

NOTE I was running Linux mint when I ran this. Same Computer different OS

edward@edward4:~$ inxi -MGCNA
Machine:
Type: Desktop Mobo: HP model: 2B4B v: 1.04 serial:
UEFI [Legacy]: AMI v: A0.14 date: 06/06/2016
CPU:
Topology: Quad Core model: Intel Core i7-6700 bits: 64 type: MT MCP
L2 cache: 8192 KiB
Speed: 3700 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 3700 2: 3700
3: 3700 4: 3700 5: 3700 6: 3700 7: 3700 8: 3700
Graphics:
Device-1: NVIDIA GM206 [GeForce GTX 960] driver: nvidia v: 430.26
Display: x11 server: X.Org 1.19.6 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 430.26
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio
driver: snd_hda_intel
Device-2: NVIDIA driver: snd_hda_intel
Device-3: Logitech G430 Surround Sound Gaming Headset type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound Server: ALSA v: k4.15.0-20-generic
Network:
Device-1: Intel Wireless 3165 driver: iwlwifi
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169

The computer was going blank and I could not continue. After the installation of the driver were some instructions as to configurations that had to be changed but I couldn’t read them and then act on them because the computer was non accessible when it would not boot. I do not know where the instructions are put in the computer to retrieve after a live boot. That may help since things changed enough that the computer could not be accessed. The first time I didn’t have that problem after the upgrade on another computer. There were no instructions or it was not bad enough to stop it from working…

Please make sure secure boot is diabled in bios.
Please run nvidia-bug-report.sh as root and attach the resulting .gz file to your post. Hovering the mouse over an existing post of yours will reveal a paperclip icon.
https://devtalk.nvidia.com/default/topic/1043347/announcements/attaching-files-to-forum-topics-posts/

Since I re-installed Manjaro again (twice) I have no installation with the driver which would have been not bootable. Installing the driver caused my system to be non usable. Part of the reason analyzing the past few days was that the installation would give me a black screen and only the power button shut off could get out of it. The last Nvidia graphic driver happened as I was reading all the things “I” was supposed to do after the installation. Not having enough time to read or do anything it meant reinstall again. Now I need some way of getting the driver in.

  1. I just thought of the fact that the live-DVD boot was pretty stable. Could I boot that and chroot to my Manjaro root partition in order to do the Nvidia graphics driver installation? Then if I install the driver I may be able to be able to do the things that I am supposed to do after the installation .

  2. If that is not possible I have Linux Mint on the same computer. I can read and modify the files on the Manjaro root drive (like configuration files). If I can find out what the graphic files are and how to modify them which I was supposed to do after the installation. Also I need a copy of the things I am supposed to modify. I also need to know where the graphic files are and which ones are being pointed to in the configurations. I can do this with the Live-DVD booted also probably. My graphics driver was installed and there was a lot of stuff I was instructed to do afterward but the system crashed and was not bootable. I have a lot of time installing Manjaro. I even have a new Kernel that seems to be more stable but it too is not totally stable and froze on me. I need professional guidance but I need to do the requested actions to the best of my ability once I know what the actions are. It is scary installing the driver and not being able to do it right because of instability of the OS.

I have installed a lot of packages on Linux Mint and I never had one that left me with something that needed to have configuration files changed “by me” after the installation for something that the package changed. Normally the upgrade would include those things in the package. I don’t know programming but if the package installed files in a different place then it should also change the associated configuration file where it was that it installed it. My other Manjaro installation using this package never gave me those messages about changing a config file that I can recall and the boot was working at the end of the installation. The person who set up the package should have taken care of things like letting the computer know where the files (config) are so they can be used.

First of all I had installed the new Kernel this time on Manjaro. This made the computer much more stable as far as the screen turning a dark grey and becoming non-responsive to the keyboard and mouse very often before. It did it afterwards but NOT when I was putting in the driver. I then went to the Manjaro settings manager on Settings in the Menu. I went down to devices. I chose the 430 driver from the list. I right clicked on it and attempted to install. Bottom line it installed with NO comments about updating anything or changing anything at the completion. That being said I proceeded to removed the open source driver. All this was with right clicking the mouse which I wasn’t aware of.

From my reading the 435 driver did not work for some graphics cards. When I watched the installation, I may have clicked on video-nvidia-435xx but it installed the video-nvidia-430xx. This time I just installed the 430 which is NOT the Best choice according to mhwd. Some how the conversion from 435 to install 430 put things in the wrong. I really did not understand the text on the printed files I sent you. What I did eventually understand is that the computer did not know where every file was located and wanted me to give the directions to in the files as to where to find the files.

My card is a GTX960. I included it in the information I gave because I did not have any problems with a different card on another computer with Manjaro. The big problem was that the authorities suggested a driver that messed up my installation. The literature pushes you toward the suggested installation. It took a long time to find out something simple like how to put in not the top suggested drive with mhwd which I could only use with the suggested driver.