The xorg log will tell, but I'm pretty sure it runs on the VESA driver.
You could try to avoid a framebuffer console instead of nomodeset, https://wiki.archlinux.org/index.php/GR … ramebuffer
Xorg.0.log @ https://pastebin.com/euqbx6i4
]]>'nomodeset' instructs the kernel to defer modesetting for the X to do it, the legacy method, the only difference, so far, is to deny fancy screen stuff until X starts running.
nomodeset disables kernel mode setting for that boot. The vesa X11 display driver works without KMS not sure on the nvidia one.
]]>It prevents https://wiki.archlinux.org/index.php/Ke … de_setting - you won't be able to run a graphical display server (except on the VESA driver)
Aug 02 13:11:01 KISE-005 kernel: You have booted with nomodeset. This means your GPU drivers are DISABLED Aug 02 13:11:01 KISE-005 kernel: Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly Aug 02 13:11:01 KISE-005 kernel: Unless you actually understand what nomodeset does, you should reboot without enabling it
The kernel module loads nevertheless and there're no errors.
However windows still seems to hibernate:
Aug 02 13:11:02 KISE-005 mount[436]: Windows is hibernated, refused to mount. Aug 02 13:11:02 KISE-005 mount[436]: Falling back to read-only mount because the NTFS partition is in an Aug 02 13:11:02 KISE-005 mount[436]: unsafe state. Please resume and shutdown Windows fully (no hibernation Aug 02 13:11:02 KISE-005 mount[436]: or fast restarting.)
And my money remains on this being the cause.
Well in any case your suggestion about 'nomodeset' solved the problem, adding it to the kernel resolved the issue regards properly booting with nvidia. Thanks a bunch. Turns out this was occasionally happening in other distributions particularly Ubuntu. 'nomodeset' instructs the kernel to defer modesetting for the X to do it, the legacy method, the only difference, so far, is to deny fancy screen stuff until X starts running.
With regards to hibernation in Windows, I had turned off hibernation in the Windows GUI but this did not delete the 'hiberfil.sys' in Windows system root directory. To do this requires using CMD or powershell ~ which I have now done.
journal for success @ https://pastebin.com/BJtre06N
]]>Aug 02 13:11:01 KISE-005 kernel: You have booted with nomodeset. This means your GPU drivers are DISABLED
Aug 02 13:11:01 KISE-005 kernel: Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly
Aug 02 13:11:01 KISE-005 kernel: Unless you actually understand what nomodeset does, you should reboot without enabling it
The kernel module loads nevertheless and there're no errors.
However windows still seems to hibernate:
Aug 02 13:11:02 KISE-005 mount[436]: Windows is hibernated, refused to mount.
Aug 02 13:11:02 KISE-005 mount[436]: Falling back to read-only mount because the NTFS partition is in an
Aug 02 13:11:02 KISE-005 mount[436]: unsafe state. Please resume and shutdown Windows fully (no hibernation
Aug 02 13:11:02 KISE-005 mount[436]: or fast restarting.)
And my money remains on this being the cause.
]]>Try to boot "nomodeset" and whether that allows you to
a) boot w/ the nvidia driver
b) inspect dmesg/the journal
Boot successful with nvidia
Journal @ https://pastebin.com/LhXe2p17
Dmesg @ https://pastebin.com/drrYnx9f
Terrific!
In a nutshell, what does nomodeset do or not do... .. ?
]]>Try to boot "nomodeset" and whether that allows you to
a) boot w/ the nvidia driver
b) inspect dmesg/the journalSo I made a hardware change, added a GTX560Ti to my GTX1070Ti system, and it borked my archlinux installation, crashing during boot.
After returning to original hardware configuration, arch still crashes during boot.Would actually suggest a HW issue (ie. missing dedicated power supply, wrong PCI slot, …)
Otherwise, since you mentioned windows, see the 3rd link in my signature (if windows is hibernating, this can cause all sorts of weird issues)
So the Windows 10 hibernate turns on a (dim) light-bulb. So I booted both Win10 (SSD&HDD-backup) and I killed all sleep, hibernate and hybrid sleep options and turned off fast startup, plus moved all virtual memory to the respective system partitions (SSD&HDD), Best practice I think to isolate as much as possible.
Next I opened the system using nouveau and reinstalled nvidia, then reboot with nouveau blacklisted, The system again crashed during boot.
The journal for this attempt is @ https://pastebin.com/PbQtVYMM
Going throughthe journal I picked up these:
-- Logs begin at Wed 2020-03-18 17:52:50 PDT, end at Sun 2020-08-02 11:41:22 PDT. --
Aug 02 11:34:56 KISE-005 kernel: microcode: microcode updated early to revision 0x2f, date = 2019-02-17
Aug 02 11:34:57 KISE-005 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 02 11:34:57 KISE-005 mount[447]: Windows is hibernated, refused to mount.
Aug 02 11:34:57 KISE-005 mount[447]: Falling back to read-only mount because the NTFS partition is in an
Aug 02 11:34:57 KISE-005 mount[447]: unsafe state. Please resume and shutdown Windows fully (no hibernation
Aug 02 11:34:57 KISE-005 mount[447]: or fast restarting.)
Aug 02 11:34:58 KISE-005 kernel: nvidia: loading out-of-tree module taints kernel.
Aug 02 11:34:58 KISE-005 kernel: nvidia: module license 'NVIDIA' taints kernel.
Aug 02 11:34:58 KISE-005 kernel: Disabling lock debugging due to kernel taint
Aug 02 11:34:58 KISE-005 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 450.57 Sun Jul 5 14:42:25 UTC 2020
Aug 02 11:34:58 KISE-005 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Aug 02 11:34:58 KISE-005 kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
Aug 02 11:34:58 KISE-005 systemd[1]: Started Getty on tty1.
Aug 02 11:35:03 KISE-005 login[532]: LOGIN ON tty1 BY ljohnson
Aug 02 11:35:03 KISE-005 systemd[1]: Reached target Multi-User System.
Aug 02 11:35:03 KISE-005 systemd[1]: Reached target Graphical Interface.
Aug 02 11:35:49 KISE-005 systemd[1]: Received SIGINT.
Aug 02 11:35:49 KISE-005 systemd[1]: Stopping Session 1 of user ljohnson.
Aug 02 11:35:49 KISE-005 audit[532]: CRED_DISP pid=532 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="ljohnson" exe="/usr/bin/login" hostname=KISE-005 addr=? terminal=tty1 res=success'
Aug 02 11:35:49 KISE-005 login[532]: pam_unix(login:session): session closed for user ljohnson
⇝Aug 02 11:34:57 "Windows is hibernated, refused to mount." ~ so I suspect there is a hanging hibernation out there
Then ⇝
Aug 02 11:34:58 KISE-005 kernel: nvidia: loading out-of-tree module taints kernel.
Aug 02 11:34:58 KISE-005 kernel: nvidia: module license 'NVIDIA' taints kernel.
Aug 02 11:34:58 KISE-005 kernel: Disabling lock debugging due to kernel taint
and then ⇝
Aug 02 11:34:58 KISE-005 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 450.57 Sun Jul 5 14:42:25 UTC 2020
But if you check a successful nvidia boot from 7/15 { https://pastebin.com/fRJLpEWK } all these are there
Next step is to try nomodeset boot and see what can be done about the hanging hibernation.
]]>So I made a hardware change, added a GTX560Ti to my GTX1070Ti system, and it borked my archlinux installation, crashing during boot.
After returning to original hardware configuration, arch still crashes during boot.
Would actually suggest a HW issue (ie. missing dedicated power supply, wrong PCI slot, …)
Otherwise, since you mentioned windows, see the 3rd link in my signature (if windows is hibernating, this can cause all sorts of weird issues)
]]>Do you still get the same error? (The "NVRM: No NVIDIA devices probed." one)
https://wiki.archlinux.org/index.php/NV … de_setting
Try adding nvidia-drm.modeset=1
It's a conundrum, if the nvidia module gets loaded, the system ceases during boot to a blank screen, and I have no access to getty, journal, dmesg, remote login or journalctl. If the nouveau module gets loaded to multi-user.target, then the nvidia module gets stopped, but I have access to the system.
The "NVRM: No NVIDIA devices probed." comes from dmesg after a nouveau boot, per you 1st message.
So I added the kernel parameter and also to mkinitcpio.conf 'MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)' per https://wiki.archlinux.org/index.php/NV … de_setting
Again failed to boot to multiuser. This time i accessed /var/log by way of another Linux on the hardware looking to see if an Xorg.0.log had been created, and no luck there.
----
Possible to find out something at rescue.target?
]]>https://wiki.archlinux.org/index.php/NV … de_setting
Try adding nvidia-drm.modeset=1
The problem is more likely that nouveau is in the initramfs and loaded, because the blacklist wasn't picked up (present) w/ the last initramfs generation.
.............and rebuild the initramfs (mkinitcpio or dracut)
You're not trying to run 440xx on the GTX 560 again, though. Are you?
Thanks for the suggestion, Seth
So still trying to get the system to boot to multi-user.target using nvidia (440xx,GTX1070Ti) I rebuilt the initramfs using dracut which is new to me
[--ljohnson{09:50:27}~]$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] (rev a1)
[root@KISE-005 ~]# dracut /boot/initramfs-linux.img
dracut: Executing: /usr/bin/dracut /boot/initramfs-linux.img
dracut: Will not override existing initramfs (/boot/initramfs-linux.img) without --force
[root@KISE-005 ~]# dracut --force /boot/initramfs-linux.img
dracut: Executing: /usr/bin/dracut --force /boot/initramfs-linux.img
dracut: dracut module 'bootchart' will not be installed, because command '/sbin/bootchartd' could not be found!
dracut: dracut module 'dash' will not be installed, because command '/bin/dash' could not be found!
dracut: dracut module 'mksh' will not be installed, because command '/bin/mksh' could not be found!
dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
dracut: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fcoemon' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fcoeadm' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!
dracut: dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found!
dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!
dracut: *** Including module: bash ***
dracut: *** Including module: systemd ***
Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist.
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: modsign ***
dracut: *** Including module: i18n ***
dracut: *** Including module: network-legacy ***
dracut: *** Including module: network ***
dracut: *** Including module: btrfs ***
dracut: *** Including module: crypt ***
dracut: *** Including module: dm ***
dracut: Skipping udev rule: 64-device-mapper.rules
dracut: Skipping udev rule: 60-persistent-storage-dm.rules
dracut: Skipping udev rule: 55-dm.rules
dracut: *** Including module: dmraid ***
dracut: *** Including module: kernel-modules ***
dracut: *** Including module: kernel-modules-extra ***
dracut: *** Including module: kernel-network-modules ***
dracut: *** Including module: lvm ***
dracut: Skipping udev rule: 64-device-mapper.rules
dracut: Skipping udev rule: 56-lvm.rules
dracut: Skipping udev rule: 60-persistent-storage-lvm.rules
dracut: *** Including module: mdraid ***
dracut: Skipping udev rule: 64-md-raid.rules
dracut: *** Including module: multipath ***
dracut: Skipping udev rule: 40-multipath.rules
dracut: *** Including module: qemu ***
dracut: *** Including module: qemu-net ***
dracut: *** Including module: cifs ***
dracut: *** Including module: lunmask ***
dracut: *** Including module: nfs ***
dracut: *** Including module: resume ***
dracut: *** Including module: rootfs-block ***
dracut: *** Including module: terminfo ***
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
dracut: Skipping udev rule: 50-firmware.rules
dracut: Skipping udev rule: 50-udev.rules
dracut: Skipping udev rule: 91-permissions.rules
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: dracut-systemd ***
dracut: *** Including module: usrmount ***
dracut: *** Including module: base ***
dracut: *** Including module: fs-lib ***
dracut: *** Including module: shutdown ***
dracut: *** Including modules done ***
dracut: *** Installing kernel module dependencies ***
dracut: *** Installing kernel module dependencies done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done ***
dracut: *** Hardlinking files ***
Mode: real
Files: 2469
Linked: 10 files
Compared: 0 xattrs
Compared: 739 files
Saved: 1.34 MiB
Duration: 0.02 seconds
dracut: *** Hardlinking files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing AuthenticAMD.bin ***
dracut: *** Using microcode found in '/boot/intel-ucode.img' ***
dracut: *** Store current command line parameters ***
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Creating image file '/boot/initramfs-linux.img' ***
dracut: *** Creating initramfs image file '/boot/initramfs-linux.img' done ***
and no love, boot still hangs with blank screen
so I rebuilt the initramfs after adding 'nvidia' to "MODULES=()' in '/etc/mkinitcpio.conf' using mkinitcpio
[root@KISE-005 ~]# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.7.11-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [autodetect]
findmnt: /etc/fstab: parse error at line 28 -- ignored
-> Running build hook: [modconf]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.7.11-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [modconf]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
and no love again, boot still hangs with blank screen.
Now the only way I can access the system is by blacklisting nvidia and not blacklisting nouveau, basically back where all this started.
I can access the system also by booting from thumb drive and arch-chroot into it. But I am still without nvidia and have to deal with nouveau's short comings when dealing with 2D images.
note: error in fstab was an extraneous character which stopped the mounting of a data only ntfs partition
]]>The problem is more likely that nouveau is in the initramfs and loaded, because the blacklist wasn't picked up (present) w/ the last initramfs generation.
lsmod
lsinitcpio /boot/initramfs-linux.img | grep nouveau
and rebuild the initramfs (mkinitcpio or dracut)
You're not trying to run 440xx on the GTX 560 again, though. Are you?
]]>Failed to boot with nvidia but dmesg now show this:
[ 4.793324] nvidia: loading out-of-tree module taints kernel.
[ 4.793331] nvidia: module license 'NVIDIA' taints kernel.
[ 4.793331] Disabling lock debugging due to kernel taint
[ 4.799200] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 4.807373] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
[ 4.807752] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[ 4.807754] NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[ 4.807754] NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
[ 4.807755] NVRM: No NVIDIA devices probed.
??? nvidia: module verification failed: signature and/or required key missing - tainting kernel ???
]]>Were any packages updated during the addition and subsequent removal of the GTX560Ti?
If yes try rolling back to the date before that update. If not try the 390xx packages instead of 450xx.
If that fails I am out of ideas.
It would not have been possible as the system would not boot and run.
So I installed the 390xx and ran the nvidia system. It failed to boot.
journal-390xx-fail @ https://pastebin.com/rHkvUDi0
I think I will swap out the GTX1070Ti and swap in the GTX560Ti and try that, tomorrow
Thanks for all your effort loqs
]]>