**Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

Nubco · 2023-07-10 00:50:38

This issue has existed for me for some months and I'm not sure when it started or why. Though other things don't work near as well if I shift to Nouveau, when I Ctl-Option-F2+ into one of the other available TTYs they work flawlessly via Nouveau. Additionally in both Arch Linux and the Arch Linux-LTS kernels, all TTYs work flawlessly prior to "StartX."

Once in X, in practice, the TTYs are still there but just visually blacked out. I know this because I can log-in blind and startx for my Qtile setup to take over the visuals. This is true in both the Arch Linux and Arch Linux-LTS kernels. I did experience the main kernel's recent issues with the Nvidia-470xx driver which was brilliantly solved via this thread... https://bbs.archlinux.org/viewtopic.php … 5#p2108685

I suspect this TTY issue is rooted in the improper system configuration of the display settings after X that should somehow apply specifically to a new TTY. I have tried lots of things so far from the Arch Wiki, but have yet to fall upon the right settings or the correct solution.

Summary: TTY works in Nouveau all the time and with Nvidia only prior to starting X. After X is started, fresh TTYs are blacked out, but seemingly functional in the blackness.

Please help if you can!

Xorg.0.log - http://ix.io/4acS
/etc/X11/xorg.conf.d/15-monitor.conf - http://ix.io/4AcU
journalctl -b - http://ix.io/4AcX
dmesg - http://ix.io/4AcY

Nvidia Drivers

nvidia-470xx-dkms 470.199.02-1
nvidia-470xx-utils 470.199.02-1
opencl-nvidia-470xx 470.199.02-1

Last edited by Nubco (2023-07-10 04:36:42)

V1del · 2023-07-10 14:54:48

You can generally do that by enabling modesetting but you have a typo in your attempt to do so. The kernel parameter is nvidia-drm.modeset=1 not nvidia-drm-modeset=1 (note the dot and not a second dash)

Nubco · 2023-07-10 17:33:58

V1del wrote:

You can generally do that by enabling modesetting but you have a typo in your attempt to do so. The kernel parameter is nvidia-drm.modeset=1 not nvidia-drm-modeset=1 (note the dot and not a second dash)

I don't know why yet, but when I substituted the

for the

the system would not boot and I had to arch-chroot in to get back here. For the time being, I simply removed that kernel parameter entirely.

Yes, the TTY issue still persists in the slightly modified system.

Newest Xorg.0.log - http://ix.io/4AhY

Looking into what may be going on now...

My current theory is that your correct kernel parameter may be triggering the error due to some other setting that is wrong and it must have been hidden because the pathway to it was obscured due to my earlier mistake.

Last edited by Nubco (2023-07-10 17:41:01)

V1del · 2023-07-10 17:45:33

I'd generally suggest you drop your xorg.conf and make sure that you removed the kms hook from mkinitcpio and regenerated your initramfs, as mentioned in bullet point 5 of: https://wiki.archlinux.org/title/NVIDIA#Installation

Nubco · 2023-07-10 19:07:04

V1del wrote:

I'd generally suggest you drop your xorg.conf and make sure that you removed the kms hook from mkinitcpio and regenerated your initramfs, as mentioned in bullet point 5 of: https://wiki.archlinux.org/title/NVIDIA#Installation

Yes, I had already done that. I also have Nouveau blacklisted among others.

My understanding is very limited at this stage. Thank you so much for your help!!!

I will post a variety of files that could be messed up.

Grub - http://ix.io/4Ai3
Blacklist.conf - http://ix.io/4Ai9
mkinitcpio.conf - http://ix.io/4Aid
I don't seem to have a xorg.conf, but rather the following files in xorg.conf.d... (I posted the contents of 15-monitor.conf earlier as well)
/etc/X11/xorg.conf.d/15-monitor.conf - http://ix.io/4AcU

.rw-r--r--  257 root  2 Jul 18:48 10-nvidia-drm-outputclass.conf
.rw-r--r--  120 root  3 Jul 23:10 12-nvidia.conf
.rw-r--r-- 1.7k root 29 Jun 18:18 15-monitor.conf
.rw-r--r--  153 root 11 Jun 14:49 30-touchpad.conf
.rw-r--r--  167 root 11 Jun 22:59 90-custom-kdb.conf-old

I will post the contents of 10 & 12 above right here below...

10...

Section "OutputClass"
    Identifier "nvidia"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "AllowEmptyInitialConfiguration"
    Option "PrimaryGPU" "yes"
    ModulePath "/usr/lib/nvidia/xorg"
    ModulePath "/usr/lib/xorg/modules"
EndSection

12...

Section "Device"
	Identifier	"Device0"
	Driver		"nvidia"
	VendorName	"NVIDIA Corporation"
	BusID "PCI:1:0:0"
EndSection

Side note: This link seems to be related but my knowledge-base is to small... https://forums.developer.nvidia.com/t/u … ing/204068

Last edited by Nubco (2023-07-10 19:11:05)

seth · 2023-07-10 19:33:11

/etc/X11/xorg.conf.d/15-monitor.conf is a full blown nvidia-settings generated static server config, remove that file.
12-nvidia.conf is pointless and 10-nvidia-drm-outputclass.conf proabably a copy of /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf - except there's a pointless "PrimaryGPU" added.
Delete those as well (make sure the file in /usr/share still exists!)

Kinda more interesting though is

GRUB_GFXMODE=2880x1800x24,1024x768x24,auto

Rather try https://wiki.archlinux.org/title/GRUB/T … ramebuffer

Finally, re-add nvidia-drm.modeset=1

Nubco · 2023-07-11 00:31:34

Thank you for your help!

seth wrote:

/etc/X11/xorg.conf.d/15-monitor.conf is a full blown nvidia-settings generated static server config, remove that file.
12-nvidia.conf is pointless and 10-nvidia-drm-outputclass.conf proabably a copy of /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf - except there's a pointless "PrimaryGPU" added.
Delete those as well (make sure the file in /usr/share still exists!)
Kinda more interesting though is
GRUB_GFXMODE=2880x1800x24,1024x768x24,auto
Rather try https://wiki.archlinux.org/title/GRUB/T … ramebuffer
Finally, re-add nvidia-drm.modeset=1

I did every single thing you recommended and configured Grub like linked below. But, the only way I could get my system to boot again after was to remove nvidia-drm.modeset=1 again (or replace the period with a dash) via chroot.

Current Grub file - http://ix.io/4Ajw

I also tried the GRUB_GFXPAYLOAD_LINUX=text option before commenting it out as shown.

Last edited by Nubco (2023-07-11 00:33:49)

seth · 2023-07-11 06:00:05

the only way I could get my system to boot again after was to remove nvidia-drm.modeset=1

Can you boot the multi-user.target w/ the parameter? (2nd link below)
Do you have a journal from such failing boot (don't reboot w/ the power button, frenetically press ctrl+alt+del multiple times or use https://wiki.archlinux.org/title/Keyboa … el_(SysRq) )

YOu btw. don't have to chroot or anything, you can edit the kernel commandline in grub (select the entry, press "e")

Nubco · 2023-07-11 20:12:42

seth wrote:

the only way I could get my system to boot again after was to remove nvidia-drm.modeset=1
Can you boot the multi-user.target w/ the parameter? (2nd link below)
Do you have a journal from such failing boot (don't reboot w/ the power button, frenetically press ctrl+alt+del multiple times or use https://wiki.archlinux.org/title/Keyboa … el_(SysRq) )
YOu btw. don't have to chroot or anything, you can edit the kernel commandline in grub (select the entry, press "e")

Thank you for the Grub tip! That will definitely save some time!

You mention a 2nd link below but I don't find one in your post, but I'm still trying to figure it out. On that note, I ctrl+alt+del doesn't work on my machine (older MacBookPro), but I have shift+power tap set to reboot. I don't know if that is the same thing yet. SysRq is new to me and I'm deciphering how to use it with my system. Last time in chroot I tried to get journalctl -b but it was a fail. W

BTW, when a failed boot (in this context) occurs, the normal full page scrolling display of actions is replaced by a set of ghostly displayed text restricted to the top inch of the laptop screen that then stops and the computer just hangs there indefinitely.

Last edited by Nubco (2023-07-11 20:16:27)

seth · 2023-07-11 20:15:56

They're in my signature.
http://wiki.archlinux.org/index.php/Sys … _boot_into

I tried to get journalctl -b but it was a fail

In which way? (You also want "-b -1" for the previous boot)

Nubco · 2023-07-11 20:21:56

seth wrote:

They're in my signature.
http://wiki.archlinux.org/index.php/Sys … _boot_into
I tried to get journalctl -b but it was a fail
In which way? (You also want "-b -1" for the previous boot)

Sorry. You were fast and I edited my above post-reply. When I say fail, I mean that it told me that no journal was present. I also couldn't access the xorg.0.log. I figured it must be because I was in chroot because they work fine in a normal boot.

I will try the -1 method once back in normal boot.

Last edited by Nubco (2023-07-11 20:22:59)

Zod · 2023-07-11 20:22:54

At risk of being wrong but trying to save you guys a little time...

nvidia_drm.modeset=1
https://wiki.archlinux.org/title/NVIDIA … de_setting

Nubco · 2023-07-11 20:27:10

Zod wrote:

At risk of being wrong but trying to save you guys a little time...
nvidia_drm.modeset=1
https://wiki.archlinux.org/title/NVIDIA … de_setting

Zod - What are you seeking to communicate there?

If it is the correct kernel parameter, yes, that is the change the results in a failed boot at this time and we don't know why. Hopefully, once resolved, that will also repair the TTY issue.

Zod · 2023-07-11 20:29:43

It's and underscore.

between nvidia and drm is an underscore...not a dash.

Nubco · 2023-07-11 21:10:44

seth wrote:

They're in my signature.
http://wiki.archlinux.org/index.php/Sys … _boot_into
I tried to get journalctl -b but it was a fail
In which way? (You also want "-b -1" for the previous boot)

Got it!

journalctl -b -1 - http://ix.io/4AnR
journalctl -b - http://ix.io/4AnT

Last edited by Nubco (2023-07-11 21:27:04)

seth · 2023-07-11 21:30:16

Jul 11 16:04:08 arch systemd[1]: Reached target Graphical Interface.
…
Jul 11 16:04:08 arch systemd-logind[557]: New session 1 of user ca.

The boot reached the graphical.target and you (auto?) login as "ca" - do you also autostart a display server (ie. eg. automatically run startx) and /that/ is when the problems start?
Ie. can you boot the multi-user.target w/ "nvidia-drm.modeset=1"?

@Zod, modprobe flattens those, dash or underscore are the same itr. and we know that there's a different behavior between "nvidia-drm.modeset=1" and some complete nonsense parameter (that'll just get ignored/passed to the userspace)

Nubco · 2023-07-12 02:35:15

seth wrote:

Jul 11 16:04:08 arch systemd[1]: Reached target Graphical Interface.
…
Jul 11 16:04:08 arch systemd-logind[557]: New session 1 of user ca.
The boot reached the graphical.target and you (auto?) login as "ca" - do you also autostart a display server (ie. eg. automatically run startx) and /that/ is when the problems start?
Ie. can you boot the multi-user.target w/ "nvidia-drm.modeset=1"?
@Zod, modprobe flattens those, dash or underscore are the same itr. and we know that there's a different behavior between "nvidia-drm.modeset=1" and some complete nonsense parameter (that'll just get ignored/passed to the userspace)

Yes, I had autologin setup, but for troubleshooting I had turned off the autostarting of X. This time though I turned off autologin also and rebooted and learned something interesting.

Turns out though it was all hidden from view, I was actually logged in, but X was not started. Since I now turned off autologin as well, I logged in blind, then started X blind and it booted in.

The TTYs still didn't work, but this is new information.

During a normal boot, I get the full-page stream of various green OKs, on the boot with the nvidia-drm.modeset=1 in play, the page only displays convoluted text crammed into that top inch or so of screen.

Here's a posted pic on the two screens for comparison...
https://imgur.com/a/h670jdR

Here's the log from the last test boot as well - http://ix.io/4AoA

Oh, and I haven't figured out how to try the "multi-user.target" thing yet, but would be happy to if I knew how or get it figured out.

Last edited by Nubco (2023-07-12 02:40:21)

Nubco · 2023-07-12 03:22:52

Nubco wrote:

Oh, and I haven't figured out how to try the "multi-user.target" thing yet, but would be happy to if I knew how or get it figured out.

https://wiki.archlinux.org/title/systemd#3.6

Yes, I have not tried the multi-user.target boot parameter and got the same results described above.

Strange boot behavior and still no TTY availability.

This must be a tough one!

Thanks for sticking with me, Seth!

Last edited by Nubco (2023-07-12 05:21:43)

seth · 2023-07-12 15:01:55

How does the LTS kernel perform if you keeo the framebuffer console disabled in grub?
(Skip nvidia-drm.modeset=1 for now, I assume it triggers the same problem as X11 wrt the console)

Nubco · 2023-07-12 16:33:18

seth wrote:

How does the LTS kernel perform if you keeo the framebuffer console disabled in grub?
(Skip nvidia-drm.modeset=1 for now, I assume it triggers the same problem as X11 wrt the console)

You will note that my system is on the latest Arch update now and I now have nvidia_drm.modeset=1 along with auto-login and auto-startx enabled due to the discoveries mentioned previously. It boots fine in terms of general result, other than no TTY and the boot process display is crammed into that top inch as displayed on the former photo link.

Here are the grub settings for these two tests...
http://ix.io/4Ar1

This log is from the newest Arch update...
http://ix.io/4AqZ

This log is from the LTS Kernel...
http://ix.io/4Ar0

Thanks again!

Last edited by Nubco (2023-07-12 19:43:58)

seth · 2023-07-12 20:04:00

You're not disabling the framebuffer console atm.
On a remote chance, move the nvidia modules into the initramfs, https://wiki.archlinux.org/title/NVIDIA#Early_loading

I missed that in your previous post, but "macbook" could be the cause here.

for name in /sys/class/drm/card0*; do basename $name; edid-decode < $name/edid; echo "===="; done

https://aur.archlinux.org/packages?O=0&K=edid-decode

Nubco · 2023-07-12 22:14:04

seth wrote:

You're not disabling the framebuffer console atm.

I must be doing it wrong then. I was following this instruction...

https://wiki.archlinux.org/title/GRUB/T … ramebuffer

...and I'm not sure what to do different. (I will double-check though and make sure I didn't make a simple error that you are referring to.)

EDIT: Yes, it seems to me that I followed those instruction to the best of my understanding. Am I missing something?

seth wrote:

On a remote chance, move the nvidia modules into the initramfs, https://wiki.archlinux.org/title/NVIDIA#Early_loading

I believe I've had that setup all along...
http://ix.io/4Aid

Are you referring to something different than the way I currently have it in my mkinitcpio.conf?

seth wrote:

I missed that in your previous post, but "macbook" could be the cause here.
for name in /sys/class/drm/card0*; do basename $name; edid-decode < $name/edid; echo "===="; done
https://aur.archlinux.org/packages?O=0&K=edid-decode

So are you saying that I should install the package you linked and then run the above code in the terminal?

I hope because I'm about to try that.

EDIT: Hmm... not sure if that worked or not. The terminal never returned with a new prompt or anything.

Last edited by Nubco (2023-07-12 22:33:08)

seth · 2023-07-12 22:35:33

The #hashtag indicates a comment in grub syntax (just like bash)

The terminal never returned with a new prompt or anything.

ls /sys/class/drm/card0*/edid

seth · 2023-07-12 22:36:03

Am I missing something?

seth wrote:

The #hashtag indicates a comment in grub syntax (just like bash)
The terminal never returned with a new prompt or anything.
ls /sys/class/drm/card0*/edid

Nubco · 2023-07-12 22:43:57

EDIT: I posted this before I saw your specific request but after you posted it.

I don't know if it helps but here's the ls output of that drm file...

http://ix.io/4Asn

This version may be better...

lrwxrwxrwx    0 root 12 Jul 17:33 card0 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
lrwxrwxrwx    0 root 12 Jul 17:33 card0-DP-1 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-DP-1
lrwxrwxrwx    0 root 12 Jul 17:33 card0-DP-2 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-DP-2
lrwxrwxrwx    0 root 12 Jul 17:33 card0-eDP-1 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-eDP-1
lrwxrwxrwx    0 root 12 Jul 17:33 card0-HDMI-A-1 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0/card0-HDMI-A-1
lrwxrwxrwx    0 root 12 Jul 17:33 renderD128 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/renderD128
.r--r--r-- 4.1k root 12 Jul 17:33 version

Last edited by Nubco (2023-07-12 22:48:19)

Arch Linux

#1 2023-07-10 00:50:38

**Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#2 2023-07-10 14:54:48

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#3 2023-07-10 17:33:58

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#4 2023-07-10 17:45:33

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#5 2023-07-10 19:07:04

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#6 2023-07-10 19:33:11

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#7 2023-07-11 00:31:34

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#8 2023-07-11 06:00:05

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#9 2023-07-11 20:12:42

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#10 2023-07-11 20:15:56

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#11 2023-07-11 20:21:56

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#12 2023-07-11 20:22:54

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#13 2023-07-11 20:27:10

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#14 2023-07-11 20:29:43

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#15 2023-07-11 21:10:44

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#16 2023-07-11 21:30:16

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#17 2023-07-12 02:35:15

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#18 2023-07-12 03:22:52

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#19 2023-07-12 15:01:55

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#20 2023-07-12 16:33:18

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#21 2023-07-12 20:04:00

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#22 2023-07-12 22:14:04

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#23 2023-07-12 22:35:33

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#24 2023-07-12 22:36:03

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

#25 2023-07-12 22:43:57

Re: **Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau**

Board footer

Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau

Re: Extra TTY's visually blacked out on Nvidia-470xx, but not Nouveau