Nvidia driver installer problem [Solved]

[FlyBy]

Hi everyone,
I've clean installed 21.1 KDE as my usual dual-boot with win10, updates done then backed up the partition so no probs getting back to fresh install anytime. I then ran the Nvidia Driver Installer from MX Tools, chose option 2 (not Optimus) but on reboot my PC hangs unresponsive with a blank screen. I thought this is the choice I usually make but to be sure I restored the partition then ran the Nvidia Driver Installer again, this time choosing Optimus but this also hangs unresponsive with a blank screen after reboot.
I've been scratching my head over this for a couple of hours. If I've done something daft could some kind soul point me which way to proceed please?

Code: Select all

System:    Kernel: 5.18.0-4mx-amd64 [5.18.16-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.18.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.2_KDE_x64 Wildflower 27 August 2022 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: HP product: HP Pavilion Gaming Laptop 17-cd0xxx 
           v: Type1ProductConfigId serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: HP model: 85FF v: 43.47 serial: <filter> UEFI: Insyde v: F.55 date: 03/28/2022 
Battery:   ID-1: BAT1 charge: 37.5 Wh (100.0%) condition: 37.5/52.5 Wh (71.5%) volts: 12.7 
           min: 11.6 model: Hewlett-Packard PABAS0241231 type: Li-ion serial: <filter> 
           status: Full 
CPU:       Info: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake 
           note: check family: 6 model-id: 9E (158) stepping: A (10) microcode: F0 cache: 
           L2: 12 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399 
           Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable 
           Type: retbleed mitigation: IBRS 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Hewlett-Packard 
           driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300 
           Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Hewlett-Packard 
           driver: nvidia v: 470.141.03 bus-ID: 01:00.0 chip-ID: 10de:1f91 class-ID: 0300 
           Device-3: Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD Integrated Webcam 
           type: USB driver: uvcvideo bus-ID: 1-5:4 chip-ID: 05c8:03bc class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: 
           loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa alternate: nv display-ID: :0 
           screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 128 size: 382x215mm (15.0x8.5") 
           diag: 438mm (17.3") 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 
           chip-ID: 8086:a348 class-ID: 0403 
           Device-2: NVIDIA vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403 
           Sound Server-1: ALSA v: k5.18.0-4mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl 
           port: 5000 bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus-ID: 03:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8 
           bus-ID: 1-14:5 chip-ID: 8087:0aaa class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1 
           sub-v: 100 hci-v: 5.1 rev: 100 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 
           port: 5060 bus-ID: 00:17.0 chip-ID: 8086.282a rev: 10 class-ID: 0104 
Drives:    Local Storage: total: 1.36 TiB used: 13.71 GiB (1.0%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 2B4QFXO7 temp: 32.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM049-2GH172 size: 931.51 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: RPM2 scheme: GPT 
Partition: ID-1: / raw-size: 50 GiB size: 48.91 GiB (97.83%) used: 13.63 GiB (27.9%) fs: ext4 
           dev: /dev/nvme0n1p6 maj-min: 259:6 
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 85.9 MiB (33.5%) 
           fs: vfat dev: /dev/nvme0n1p5 maj-min: 259:5 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 43.0 C mobo: 29.8 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2412 note: see --pkg apt: 2405 lib: 1367 flatpak: 7 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
           2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye ahs
Info:      Processes: 267 Uptime: 14m wakeups: 2 Memory: 15.47 GiB used: 2.07 GiB (13.4%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

[Huckleberry Finn]

Code: Select all

sudo rm /etc/X11/xorg.conf

[Huckleberry Finn]

... after installing the driver...

... Or (when there's the blank screen) you can boot with "any Linux" media (no matter new/old release or CD/DVD/Usb etc.) and delete the /etc/X11/xorg.conf in the MX Partition simply with the file manager.

... You can choose the Optimus by the way :)

[dolphin_oracle]

the /var/log/ddm.log file should be provided in a post so we can see what happens during install.

while ddm shouldn't be creating an xorg file, it doesn't hurt to check.

[FlyBy]

@Huckleberry Finn I tried that but there is no /etc/X11/xorg.conf

@dolphin_oracle I have attached the ddm.log

[dolphin_oracle]

something is odd. if the user is on mx21, and installing the 510 nvidia drivers, it shouldn't require bumblebee. it shouldn't even offer. It should be telling you that you can run with the PRIMUS functions of the nvidia drivers. that said, there is nothing wrong with bumblebee, and it looks like the install was OK.

what does the output of "nvidia-detect" say?

are you dual-booting and if so does MX control your grub menu?

when you say black screen, is there a blinking cursor or no? do you see any text at all?

[FlyBy]

$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1)

Checking card: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
Your card is supported by the default drivers.
Your card is also supported by the Tesla 470 drivers series.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
Your card is also supported by the Tesla 418 drivers series.
It is recommended to install the nvidia-driver package.

I am dual-booting and MX controls my grub menu.

By black screen, I should have said I see either a static or blinking cursor, I have now done several fresh installs of the distro then ran the MX Tools Nvidia Driver Installer after which I end up with either a static or blinking cursor. However I don't see any text at all.

Out of curiosity I clean installed my previous MX version MX-19.4_kde_x64 patito feo March 31 2021. After running update etc I used the MX Tools Nvidia Driver Installer, choosing option 2 (not Optimus). The installation was a success, and no mention of bumblebee drivers.

[roundup976]

The black screen with a blinking cursor was the problem I had with NVidia dirver 510 version. My card was not compatible, and the Nvidia Driver Installer tool would not give me an option for anything else in the stable repos. I used the MX Package Installer to re-install version 470 of the drivers and the issue was resolve. When installing 470 in the package manager I only selected a few 470 options like the driver and the settings and checked the box to install dependencies and let it pick what else was needed. Reboot and everything was back to good.

@dolphin_oracle and @timkb4cq pointed me in the right direction. Maybe check out that post.

https://forum.mxlinux.org/viewtopic.php?t=71400

[FlyBy]

The black screen with a blinking cursor was the problem I had with NVidia dirver 510 version. My card was not compatible, and the Nvidia Driver Installer tool would not give me an option for anything else in the stable repos. I used the MX Package Installer to re-install version 470 of the drivers and the issue was resolve. When installing 470 in the package manager I only selected a few 470 options like the driver and the settings and checked the box to install dependencies and let it pick what else was needed. Reboot and everything was back to good.

@dolphin_oracle and @timkb4cq pointed me in the right direction. Maybe check out that post.

https://forum.mxlinux.org/viewtopic.php?t=71400

That's great that you were able to resolve the problem, and I appreciate you dropping me a line. I tried what I thought I understood from that post, but clearly screwed something up with messages about broken dependences etc. I put my hands up to being a noob! I've restored from a full backup just as it was before I even tried the nvidia installer so it's all good. I'll plod on and learn without nvidia working, it's no biggie. Cheers!

[roundup976]

The black screen with a blinking cursor was the problem I had with NVidia dirver 510 version. My card was not compatible, and the Nvidia Driver Installer tool would not give me an option for anything else in the stable repos. I used the MX Package Installer to re-install version 470 of the drivers and the issue was resolve. When installing 470 in the package manager I only selected a few 470 options like the driver and the settings and checked the box to install dependencies and let it pick what else was needed. Reboot and everything was back to good.

@dolphin_oracle and @timkb4cq pointed me in the right direction. Maybe check out that post.

https://forum.mxlinux.org/viewtopic.php?t=71400

That's great that you were able to resolve the problem, and I appreciate you dropping me a line. I tried what I thought I understood from that post, but clearly screwed something up with messages about broken dependences etc. I put my hands up to being a noob! I've restored from a full backup just as it was before I even tried the nvidia installer so it's all good. I'll plod on and learn without nvidia working, it's no biggie. Cheers!

If you would like, I can actually give you a much more detailed account of what I did. I sometimes feel bad about going into to much detail and giving people more than they may want to read. Step by step and the packages and how I installed them and/or uninstalled them.