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

Nubco · 2023-07-12 22:47:11

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

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

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

seth wrote:

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

I am not clear on what is being communicated here beyond the simple explanation of the #hashtag being used for comments.

What is the context in which I am to use to apply what you are trying to say? Also, I'm not clear what it is that you are saying.

Sorry. I have large holes in my understanding.

seth · 2023-07-13 04:43:57

I fucked up the edit and hit the quote button (it's hot and was late)
The aspect you're missing is that the relevant entries in your /etc/default/grub are all commented, so you're not disabling the framebuffer console.

Wrt. the ls output, are there no "edid" files in any of those card* directories?
Also, are you maybe using "fish" as interactive shell?

Nubco · 2023-07-13 16:27:54

seth wrote:

I fucked up the edit and hit the quote button (it's hot and was late)
The aspect you're missing is that the relevant entries in your /etc/default/grub are all commented, so you're not disabling the framebuffer console.
Wrt. the ls output, are there no "edid" files in any of those card* directories?
Also, are you maybe using "fish" as interactive shell?

Thank you for taking steps toward clarification!

Yes, I am using fish as interactive shell. Also, I'm not clear on the steps to disable the framebuffer console because I had it set the way I interpreted the wiki. I will work on both of those and post for confirmation.

Thanks again!

Nubco · 2023-07-13 17:56:58

Ok, I took fish out of interactive only and now have it as my default shell.

I ran your code in bash and got a bunch of output that I wish I would have saved for you.

I don't know if it is what you want, but I also changed my grub file to the following...

http://ix.io/4AvW

Here's the new output of...

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

I'm hoping this is progress!

.r--r--r-- 0 root 13 Jul 12:49 /sys/class/drm/card0-DP-1/edid
.r--r--r-- 0 root 13 Jul 12:49 /sys/class/drm/card0-DP-2/edid
.r--r--r-- 0 root 13 Jul 12:49 /sys/class/drm/card0-eDP-1/edid
.r--r--r-- 0 root 13 Jul 12:49 /sys/class/drm/card0-HDMI-A-1/edid

Last edited by Nubco (2023-07-13 17:57:36)

seth · 2023-07-13 18:00:42

Ok, I took fish out of interactive only and now have it as my default shell.

That's probably not helpful

I ran your code in bash and got a bunch of output

but that is

that I wish I would have saved for you.

(for name in /sys/class/drm/card0*; do basename $name; edid-decode < $name/edid; echo "===="; done) | curl -F 'file=@-' 0x0.st

Edit:

GRUB_GFXMODE=2880x1800x32,auto

comment that again, did you run "grub-mkconfig -o /boot/grub/grub.cfg" after edting /etc/default/grub ?

Last edited by seth (2023-07-13 18:02:55)

Nubco · 2023-07-13 18:14:21

Ok, got it!

Here's the output of edid code...

http://0x0.st/HjQa.txt

I commented out the line requested above and ran the grub config code and rebooted.

Here's the journal file...

http://0x0.st/HjQS.txt

Thanks again for all you help!

Last edited by Nubco (2023-07-13 18:14:56)

Nubco · 2023-07-13 18:24:36

Oops... that past post included a file (15-monitor.conf) that should have been deactivated first as requested early on.

Here's a fresh boot in the right context.

edid code results...

http://0x0.st/HjQa.txt

Fresh boot journal...

http://0x0.st/HjQ9.txt

Last edited by Nubco (2023-07-13 18:25:25)

seth · 2023-07-13 18:24:43

I commented out the line requested above and ran the grub config code and rebooted.

Any success?

You've the internal dispaly and a Samsung monitor (Tv?) attached via HDMI, do you see the same artifacts/behavior on both?
What if you detach the HDMI monitor?

Nubco · 2023-07-13 18:35:52

seth wrote:

Any success?

Not yet.

seth wrote:

You've the internal dispaly and a Samsung monitor (Tv?) attached via HDMI, do you see the same artifacts/behavior on both?

Yes, it is a big TV. The only display is on the MacBook in the upper 1 inch of the screen after a quick few lines from Grub in the middle of the screen. The TV is in "no signal" mode until X starts.

seth wrote:

What if you detach the HDMI monitor?

As stated in my earliest post, the only strange thing is that the MacBook is the "0" monitor in Nouveau and when the TV is unattached. But, when the TV is attached, it seemingly becomes the "0" monitor. That is one of the things that my "15-monitor.conf" file changes as you can likely see in the "pre-oops" post.

No TTYs either way, except in the pre-X state or if Nouveau is the driver.

Last edited by Nubco (2023-07-13 18:37:13)

seth · 2023-07-13 19:05:19

Revert the grub changes (we'll need the fbcon for this) and boot the multi-user.target w/ nouveau (so your console now hopefully looks fine, nvidia probably won't work w/o drm.modeset either)
There run

fbset -si

and post the output.
We'll then try to ask the kernel explicitly for this mode, https://www.kernel.org/doc/Documentation/fb/modedb.rst
https://wiki.archlinux.org/title/Kernel_parameters

Nubco · 2023-07-13 20:02:01

seth wrote:

Revert the grub changes (we'll need the fbcon for this) and boot the multi-user.target w/ nouveau (so your console now hopefully looks fine, nvidia probably won't work w/o drm.modeset either)
There run
fbset -si
and post the output.
We'll then try to ask the kernel explicitly for this mode, https://www.kernel.org/doc/Documentation/fb/modedb.rst
https://wiki.archlinux.org/title/Kernel_parameters

So, if I understand correctly, I am to get rid of Nvidea drivers temporarily and comment back out the aforementioned lines in the Grub file, unblacklist Nouveau, and boot into Arch with the multi-user.target kernel parameter.

Then, within the resultant boot into Arch, run the prescribed command and share with you the results.

I looked up "fbcon" and it appears to be a driver that I already have...

┬─ 14:59:28
│[I] ca@arch in ~
╰─>$ journalctl -b | grep fbcon
Jul 13 13:27:29 arch kernel: fbcon: Deferring console take-over
Jul 13 13:27:29 arch kernel: fbcon: Taking over console

Am I understanding correctly?

Last edited by Nubco (2023-07-13 20:02:50)

seth · 2023-07-13 20:05:34

Yes, but that's w/ a broken output, right?
We want to know what's used when it's working.

correctly

Correctly.

Nubco · 2023-07-13 23:09:27

seth wrote:

fbset -si
and post the output.

Sorry it took me so long to get here. I had to chroot a few times because I was trying to figure out how to deactivate the NVIDIA drivers without uninstalling them. I finally just uninstalled them. LOL (Remember, those special 199 drivers were another issue mentioned in my very first post.)

Yes, with the Nouveau driver I do have access to the TTYs as expected.

I installed fbset.

Now, this is my little hangup...

┬─ 18:01:32
│[I] ca@arch in ~
╰─>$ fbset -si | 0x0
Unknown video mode `-si'
451 Unavailable For Legal Reasons⏎

EDIT: Nevermind...

Separating them to -s -i worked.

http://0x0.st/Hjju.txt

I'll just hang out here on Nouveau for a bit till I hear back from you.

Thanks again!

Last edited by Nubco (2023-07-14 06:36:58)

seth · 2023-07-14 06:54:00

Separating them to -s -i worked.

Yup, sorry.

mode "2880x1800"
    geometry 2880 1800 3840 2160 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : nouveaudrmfb
    Address     : (nil)
    Size        : 33292288
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 15360
    Accelerator : No

Did you run this out of a GUI session?
(The timings are 0 and the virtual resolution > than the actual one, matching the samsung resolution)

On a liimb, just add

video=eDP-1:2280x1800R@60e

to the kernel parameters.

Nubco · 2023-07-14 15:19:04

seth wrote:

Did you run this out of a GUI session?
(The timings are 0 and the virtual resolution > than the actual one, matching the samsung resolution)

Assuming I understand your question correctly, yes, I am running everything on bare metal. No virtual machine involved at all.

seth wrote:

On a liimb, just add
video=eDP-1:2280x1800R@60e
to the kernel parameters.

In order to run that test and get a meaningful result, I assume "Nouveau" can be disregarded now and I need to reestablish the Nvidia driver setup?

I assume you mean...

video=eDP-1:2880x1800R@60e

rather than 2280.

Last edited by Nubco (2023-07-14 15:39:08)

seth · 2023-07-14 15:24:45

1. No, i meant sth. like gnome in contrast to the linux console
2. That test would only be relevant w/ the nvidia driver, but if the previous output wasn't obtained on the console, get the proper output first.

Nubco · 2023-07-14 15:43:14

seth wrote:

1. No, i meant sth. like gnome in contrast to the linux console

I think we are bumping up against another hole in my understanding.

I don't understand what you are asking for right now.

I got the result by rebooting, logging in, starting x, which starts Qtile, then opening Alacrity, and running the command.

Do I need to run the command in another way or from another place like Grub or something?

Last edited by Nubco (2023-07-14 15:47:03)

Scimmia · 2023-07-14 15:54:57

the 'starting x' part is the GUI (Graphical User Interface) session he was talking about.

Nubco · 2023-07-14 16:30:17

Scimmia wrote:

the 'starting x' part is the GUI (Graphical User Interface) session he was talking about.

Got it! Thank you so much! That makes perfect sense. I was used to people referring to the GUI vs terminal on a post-startx basis.

Ok, here is the correct output taken right after the console login... (no startx)

mode "2880x1800"
    geometry 2880 1800 3840 2160 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : nouveaudrmfb
    Address     : (nil)
    Size        : 33292288
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 15360
    Accelerator : No

Seems the output is actually still the same.

Last edited by Nubco (2023-07-14 16:33:11)

seth · 2023-07-14 18:42:10

Yes, unfortunately the timings are all still 0
Try that again w/o the Samsung TV attached during the boot.

Otherwise just try the suggested video mode.

Nubco · 2023-07-14 22:35:22

seth wrote:

Yes, unfortunately the timings are all still 0
Try that again w/o the Samsung TV attached during the boot.
Otherwise just try the suggested video mode.

Thanks for reaching out. I was literally about to reestablish Nvidia and run that, but now I can run the test you mentioned first without having to backtrack.

Nubco · 2023-07-14 22:41:57

Nubco wrote:

...but now I can run the test you mentioned first without having to backtrack.

Here's the results...

mode "2880x1800"
    geometry 2880 1800 2880 1800 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : nouveaudrmfb
    Address     : (nil)
    Size        : 20840448
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 11520
    Accelerator : No

Last edited by Nubco (2023-07-14 22:42:49)

Nubco · 2023-07-15 00:05:34

Ok, nvidia is back and I used the...

video=eDP-1:2880x1800R@60e

...parameter.

The hidden upper 1 inch ghostly blind login and boot were the same unfortunately.

Here's the journal results...

http://0x0.st/Hjpe.txt

Last edited by Nubco (2023-07-15 00:07:16)

Nubco · 2023-07-17 02:22:38

I plan to dig deeper into this persistent issue tomorrow.

I miss my TTY! LOL

Arch Linux

#26 2023-07-12 22:47:11

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

#27 2023-07-12 22:52:12

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

#28 2023-07-13 04:43:57

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

#29 2023-07-13 16:27:54

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

#30 2023-07-13 17:56:58

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

#31 2023-07-13 18:00:42

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

#32 2023-07-13 18:14:21

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

#33 2023-07-13 18:24:36

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

#34 2023-07-13 18:24:43

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

#35 2023-07-13 18:35:52

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

#36 2023-07-13 19:05:19

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

#37 2023-07-13 20:02:01

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

#38 2023-07-13 20:05:34

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

#39 2023-07-13 23:09:27

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

#40 2023-07-14 06:54:00

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

#41 2023-07-14 15:19:04

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

#42 2023-07-14 15:24:45

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

#43 2023-07-14 15:43:14

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

#44 2023-07-14 15:54:57

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

#45 2023-07-14 16:30:17

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

#46 2023-07-14 18:42:10

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

#47 2023-07-14 22:35:22

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

#48 2023-07-14 22:41:57

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

#49 2023-07-15 00:05:34

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

#50 2023-07-17 02:22:38

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

Board footer

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

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