* Carlos E. R. [11-14-21 15:36]:

On 14/11/2021 21.20, Patrick Shanahan wrote:

...

have been using nvidia cards (and others) forever and had few problems, but maybe getting old is now a problem.

have a new dell desktop i7-11700 with onboard intel RodketLake-S GT1 [UHD Graphicks 750] and nVidia GA104 [GeForce rTX 3060 Ti]

The last time I purchased a computer, I followed the recommendation to switch to AMD, specially for the video. And they were right, I had to do nothing. I can do things and get even better/faster video, but at it is I can even play 3D games.

and I am not interested in AMD, I have nVidia.

As you, I used Nvidia before.

...

I entered the bios and configured using the NVidia card rather than Auto.

Wait, double video, intel+nvidia? Is that "Optimus"? It is a big source of trouble. I did not know of desktops using it, though.

I don't believe so, but do not know. It is *not* a laptop.

https://en.wikipedia.org/wiki/Nvidia_Optimus

Search also for bumblebee at our wiki.

https://en.opensuse.org/SDB:NVIDIA_Bumblebee

If it is optimus hardware, the handling and installation of the drivers change completely. Sorry, I can't explain how. Daniel has that, I'm sure he can describe with colourful expletives his experience.

Maybe it is not optimus, being a desktop.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode What sort of day was it? A day like all days, filled with those events that alter and illuminate our times... all things are as they were then, but were you there?

* Felix Miata [11-14-21 16:02]:

Patrick Shanahan composed on 2021-11-14 15:20 (UTC-0500):

...

PLEASE help

cat /var/log/Xorg.0.log.old | susepaste cat /var/log/Xorg.0.log | susepaste

Do you know for a fact that you can disable KMS (nomodeset) and have NVidia proprietary drivers functional? That's not possible with FOSS display drivers. It commonly results in blinking cursor in upper left on black screen, because the DM can't start without working X.

no, I didn't know that, tks. https://paste.opensuse.org/58852214 https://paste.opensuse.org/82324516 tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode What sort of day was it? A day like all days, filled with those events that alter and illuminate our times... all things are as they were then, but were you there?

* Felix Miata [11-16-21 13:44]:

Patrick Shanahan composed on 2021-11-16 12:27 (UTC-0500):

...

* Felix Miata composed:

...

...

Patrick Shanahan composed on 2021-11-14 15:20 (UTC-0500):

...

...

...

PLEASE help

...

...

cat /var/log/Xorg.0.log.old | susepaste cat /var/log/Xorg.0.log | susepaste

...

...

Do you know for a fact that you can disable KMS (nomodeset) and have NVidia proprietary drivers functional? That's not possible with FOSS display drivers. It commonly results in blinking cursor in upper left on black screen, because the DM can't start without working X.

To be clear, the crude fallback drivers fbdev and vesa may or may not work if KMS is disabled. It's the optimal FOSS drivers that unconditionally depend on KMS.

...

no, I didn't know that, tks.

...

https://paste.opensuse.org/58852214 https://paste.opensuse.org/82324516

There's not a lot to report from them. The Intel Rocket Lake IGP's HDMI-2 port (supporting "Max Resolution (HDMI)‡ 4096x2160@60Hz"[1]) is connected to a Samsung 4k display, running the default modesetting DIX (display driver; same driver all my non-ancient Intel IGPs run), but only operating @1920x1080. There's no sign in them I recognize that an NVidia GPU is present.

[1] https://ark.intel.com/content/www/us/en/ark/products/212047/intel-core-i7117...

I will specify in bios that nvidia be used instead of "auto" which in this case is using the onboard intel display card, and provide the same information again. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode What sort of day was it? A day like all days, filled with those events that alter and illuminate our times... all things are as they were then, but were you there?

Patrick Shanahan composed on 2021-11-16 14:59 (UTC-0500):

...

I will specify in bios that nvidia be used instead of "auto" which in this case is using the onboard intel display card, and provide the same information again.

/var/log/Xorg.0.log.old https://paste.opensuse.org/90240294

/var/log/Xorg.0.log https://paste.opensuse.org/24052494

no video output from either card

From the latter: [159549.883] (II) modeset(0): Output DP-1 disconnected [159549.883] (II) modeset(0): Output HDMI-1 disconnected [159549.883] (II) modeset(0): Output HDMI-2 connected [159549.883] (II) modeset(0): Output DP-2 disconnected [159549.883] (II) modeset(0): Output HDMI-3 disconnected [159549.883] (II) modeset(0): Using exact sizes for initial modes [159549.883] (II) modeset(0): Output HDMI-2 using initial mode 1920x1080 +0+0 ... [159549.883] (II) UnloadModule: "nvidia" [159549.883] (II) Unloading nvidia This suggests X knows about the NVidia card, but that the only connected monitor is connected to a motherboard port, not to any NVidia card port, so only the Intel IGP has anything to do. Why no video output I can't explain from anything I see in the log. If you're trying to get both NVidia and Intel outputs to work at the same time in order to use only HDMI cables instead of DisplayPort, I'd be surprised if you can find any way to do it with a Dell BIOS. IME, with a Dell, it's one or the other only. IME with a Dell, the onboard never works as expected if a discrete graphics card is installed. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

Patrick Shanahan composed on 2021-11-16 14:44 (UTC-0500):

I will specify in bios that nvidia be used instead of "auto" which in this case is using the onboard intel display card, and provide the same information again.

Auto should work. What depends is where you connect your video cables. The Intel IGP should automatically play dead if you plug both cables into NVidia card ports. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

* Robert Munteanu [11-14-21 18:13]:

Hi,

On Sun, 2021-11-14 at 15:20 -0500, Patrick Shanahan wrote:

...

I have spent much tooo much time trying on my own to resolve this.  PLEASE help

Is the nvidia kenrel module available/loaded?

$ modinfo nvidia

https://paste.opensuse.org/65363374

$ lsmod | grep nvidia

blank currently

Why have you chosen to add 'nomodeset' to the kernel parameters? Anything in of interest via `journalctl -b`?

not that I saw, but ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode What sort of day was it? A day like all days, filled with those events that alter and illuminate our times... all things are as they were then, but were you there?

* Daniel Morris [11-15-21 07:40]:

On Sun, Nov 14, 2021 at 03:20:36PM -0500, Patrick Shanahan wrote:

...

have been using nvidia cards (and others) forever and had few problems, but maybe getting old is now a problem.

Which kernel are you using, which do you think you are using?

I tried the proprietary driver for the first time last week as the nouveau driver keeps locking up every n'th suspend. Initially I got 1024x768 on my 32"/80cm monitor. Then I tried to configure it and just got a black screen after causing an unhelpful xorg.conf file to be created.

This is a Leap 15.2 system (long overdue nuke & paving a fresh install), and a little while later I realised it was running the -prempt kernel. Deleting the xorg.conf and booting from grub to the default kernel had the display spring into life at 2560x1440 without any further intervention. I'll have to give it a few days to see if the lockup after multiple suspend/wake is fixed.

I also notice the X prompt to give the disk decrypt keys for home disks is missing, so I guess there's a dependency/sequencing glitch with the proprietary driver, but simple work-around is to drop to the the virtual console where the kernel's text-mode is waiting for the passphrase.

I think the -prempt kernel was installed due to a virtualbox packaging glitch last year. I stopped digging at that point.

I am definitely running kernel-default-5.14.14.2 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode What sort of day was it? A day like all days, filled with those events that alter and illuminate our times... all things are as they were then, but were you there?

On Tue, 2021-11-16 at 20:32 +0000, Scott Bradnick wrote:

On Tue, 2021-11-16 at 12:38 -0500, Patrick Shanahan wrote:

...

* Daniel Morris [11-15-21 07:40]:

...

On Sun, Nov 14, 2021 at 03:20:36PM -0500, Patrick Shanahan wrote:

...

have been using nvidia cards (and others) forever and had few problems, but maybe getting old is now a problem.

Which kernel are you using, which do you think you are using?

I tried the proprietary driver for the first time last week as the nouveau driver keeps locking up every n'th suspend. Initially I got 1024x768 on my 32"/80cm monitor. Then I tried to configure it and just got a black screen after causing an unhelpful xorg.conf file to be created.

This is a Leap 15.2 system (long overdue nuke & paving a fresh install), and a little while later I realised it was running the -prempt kernel. Deleting the xorg.conf and booting from grub to the default kernel had the display spring into life at 2560x1440 without any further intervention. I'll have to give it a few days to see if the lockup after multiple suspend/wake is fixed.

I also notice the X prompt to give the disk decrypt keys for home disks is missing, so I guess there's a dependency/sequencing glitch with the proprietary driver, but simple work-around is to drop to the the virtual console where the kernel's text-mode is waiting for the passphrase.

I think the -prempt kernel was installed due to a virtualbox packaging glitch last year. I stopped digging at that point.

I am definitely running kernel-default-5.14.14.2

NVIDIA stuff is "fun"; I'm hardly a pro with it, but I've had the most, consistent success (when keep TW up-to-date) using the ABSOLUTE latest .run from https://download.nvidia.com/XFree86/Linux-x86_64/ on a laptop that has both Intel & NVIDIA (controlled by "prime"):

#  prime-select get-current Driver configured: nvidia bbswitch not loaded. NVIDIA modules are loaded

I'm currently using 495.44 w/ 5.14.14-2-default (even have secure boot enabled and sign the drivers each time) [paying attention to the missing "sign-file" for each new kernel]. Big things to pay attn to are having nouveau disabled (which the driver installer will do) and ensuring the nvidia_drm kernel module _actually_ loads. There's a file in /etc/modprobe.d that's supposed to do that - but I've had better success just tacking .broken onto the end of it so it doesn't muddy any waters.

It seems concerning that no GPU is listed in your Xorg log(s):

#  grep -i gpu /var/log/Xorg.0.log [   330.319] (**) |   |-->GPUDevice "modesetting" [   330.319] (**) |   |-->GPUDevice "nvidia" [   330.319] (==) Automatically adding GPU devices [   330.339] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [   330.370] (**) NVIDIA(0): Option "AllowExternalGpus" [   330.378] (II) NVIDIA(0): NVIDIA GPU Quadro T1000 (TU117GL-A) at PCI:1:0:0 (GPU-0)

#  uname -a Linux a-dell-laptop 5.14.14-2-default #1 SMP Thu Oct 21 05:05:03 UTC 2021 (2b5383f) x86_64 x86_64 x86_64 GNU/Linux

# grep -i T100 /var/log/Xorg.0.log [   330.378] (II) NVIDIA(0): NVIDIA GPU Quadro T1000 (TU117GL-A) at PCI:1:0:0 (GPU-0)

# grep -i drm /var/log/Xorg.0.log [   330.320] (II) xfree86: Adding drm device (/dev/dri/card1) [   330.320] (II) xfree86: Adding drm device (/dev/dri/card0)

# lsmod | grep -i nvidia nvidia_uvm           1175552  0 nvidia_drm             73728  4 nvidia_modeset       1155072  2 nvidia_drm nvidia              36950016  106 nvidia_uvm,nvidia_modeset drm_kms_helper        299008  2 nvidia_drm,i915 drm                   626688  9 drm_kms_helper,nvidia,nvidia_drm,i915,ttm

Maybe I spoke too soon, I did a zypper dup a few minutes later and now I just get a black screen ; even redoing things w/ the .run also gives me a black screen. To me, there seems to be some issue w/ the xorg updates provided by 20211111 vs 20211110: 20211110: xorg-x11-server-1.20.13-1.2.x86_64 20211111: xorg-x11-server-21.1.1-1.1.x86_64 20211110: xorg-x11-server-extra-1.20.13-1.2.x86_64 20211111: xorg-x11-server-extra-21.1.1-1.1.x86_64 20211110: xorg-x11-server-Xvfb-1.20.13-1.2.x86_64 20211111: xorg-x11-server-Xvfb-21.1.1-1.1.x86_64 If I boot from the zypper snapshot just prior (I'd installed yast2-rdp and it's still there and working). Here's a paste of all that was updated by the 'dup' => https://paste.opensuse.org/65393126 I'll poke around https://bugzilla.opensuse.org and see if anyone else has reported this type of issue. I see these: https://bugzilla.opensuse.org/show_bug.cgi?id=1192751 https://bugzilla.opensuse.org/show_bug.cgi?id=1192678 And it seems to be my issue, I'm logging in to icewm with lightdm. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC

* Scott Bradnick [11-16-21 17:24]:

On Tue, 2021-11-16 at 22:01 +0000, Scott Bradnick wrote:

...

I'll poke around https://bugzilla.opensuse.org and see if anyone else has reported this type of issue.

I see these:

https://bugzilla.opensuse.org/show_bug.cgi?id=1192751 https://bugzilla.opensuse.org/show_bug.cgi?id=1192678

And it seems to be my issue, I'm logging in to icewm with lightdm.

That's certainly my issue, this makes lightdm pop-up as usual/expected when the laptop boots:

# cat /usr/etc/X11/xdm/xrandr-auto.sh #!/usr/bin/bash printf "THE SCRIPT WAS RUN ['%s'].\n" "$(date)" >> /tmp/xrandr-auto.txt /usr/bin/xrandr --auto

# grep display-setup-script /usr/share/lightdm/lightdm.conf.d/50-suse- defaults.conf display-setup-script=/usr/etc/X11/xdm/xrandr-auto.sh

So, NVIDIA 495.44 and 5.14.14-2-default are working fine together.

-- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64)

https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC

I have nVidia 470.86-49.2 installed and kernel-default 5.14.14-10 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode What sort of day was it? A day like all days, filled with those events that alter and illuminate our times... all things are as they were then, but were you there?

Maybe I spoke too soon, I did a zypper dup a few minutes later and now I just get a black screen ; even redoing things w/ the .run also gives me a black screen.

JFTR, I had to boot into nvidia-driver (as I need to use the external screen) and ended up in a black screen as well (TW, 20211111 on ThinkPad X1 Extreme, ): Will subscribe to https://bugzilla.opensuse.org/show_bug.cgi?id=1192678 https://bugzilla.opensuse.org/show_bug.cgi?id=1192751 Cheers Axel