[Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

LinuxLover471 · 2025-03-27 06:35:20

Hi, I hope that you are doing well.

I had 2 attempts to try/fix this.

This issue was appearing for me whenever I tried to use the nouveau driver, or any arch-based distro's bootable drive. I had tried booting into endeavour, and vanilla arch, and both did not boot because of the driver issue and my display always turned off. Therefore I have to use nomodeset in the kernel parameters to boot into the installation medium OR if I want to boot into arch. When I tried using proprietary drivers, (nvidia-470xx-dkms and it's other packages) it booted into the system perfectly.

I had also tried installing nouveau after installing the nvidia driver (and removing the nvidia driver) but my monitor would not get any signal again. I simply removed the nvidia driver and installed the mesa and lib32-mesa package, I set up KMS hook in mkinitcpio.conf and also removed nvidia modules and added the nouveau modules and regenerated with "sudo mkinitcpio -P". I then tried to create a xorg.conf by using "sudo Xorg -configure" and "sudo X -configure" but it always said there are no screens found and exited error 2, but in the second attempt it only exited with an error 2. I also noticed trying to boot with nomodeset in the default initramfs still resulted in blank screen/no signal. But trying the same thing with fallback initramfs did in fact showed the display but the system didn't bother booting into the GUI/KDE Plasma. It did start the graphical environment but didn't bother booting into it. I then opened a tty and tried lsmod | grep "nvidia" to see if nvidia drivers are interfering and to no one's surprise, they were not there. I also tried lsmod | grep "nouveau" and it gave an output showing it did infact load.

Also I tried booting into the normal initramfs and tried rebooting from there by entering a tty environment, i.e., I blindly tried to check if the system is even working or not. I entered sudo reboot and it did respond to the command. Which means only the display output is messed up.

I also checked the logs with "journalctl -xe -p 3 --no-pager and found out some errors in sddm-

Could not read display number from pipe. ( this was repeated three times).
Could not start display server on vt 1

Super short summary of issues-
No xorg.conf in /etc/xorg.conf?
Xorg doesn't detect any screens when using "sudo X -config" or "sudo startx" and says "Server terminated with error 2."
Sddm could not read display number from pipe and could not start display server on vt 1. (it was vt 2 on the first attempt).

Things I tried-
Trying to create a xorg .conf with "sudo Xorg -configure" it resulted in either no screens found or the configuration didn't fix the issue nor help at all.
I tried switching the display manager from sddm to lightdm, didn't fix anything. But rather made the situation worse because it didn't even start. (Maybe I forgot to enable it? I probably didn't)

What is the cause?-
I think it's probably something with Xorg or with the initramfs configuration.

Logs-
Nouveau log-

Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: NVIDIA GK107 (0e7080a2)
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: bios: version 80.07.df.00.01
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: vgaarb: deactivate vga console
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: fb: 4096 MiB DDR3
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: VRAM: 4096 MiB
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: GART: 1048576 MiB
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: TMDS table version 2.0
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: MM: using COPY for buffer copies
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: [drm] Registered 4 planes with drm panic
Mar 26 20:15:13 archlinux kernel: [drm] Initialized nouveau 1.4.0 for 0000:01:00.0 on minor 0
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Mar 26 20:15:13 archlinux systemd-modules-load[106]: Inserted module 'nouveau'
Mar 26 20:15:16 G31M-ES2L kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
Mar 26 20:15:18 G31M-ES2L kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1
Mar 26 20:15:18 G31M-ES2L kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1

(Probably a log of the boot when the issue happened, I can't remember.)-
https://pastebin.com/iVASiM38

I know I should just stick to the nvidia drivers, but I wanted to find out what was causing the nouveau issue, so I thought that the bright minds of the arch linux forums must have some solution.

Edit- Also this was not an issue in debian and mint, if that helps. Although I was not able to use all 100hz of my monitor it was limited to 75 hz.
I had also read the arch wiki and did try the MSI kernel parameters and other things but it still gave no signal to the monitor.
output of inxi -Fxxxz-

System:
  Kernel: 6.13.8-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: G31M-ES2L serial: <superuser required>
    uuid: <superuser required> BIOS: Award v: FI date: 08/09/2010
CPU:
  Info: quad core model: Intel Core2 Quad Q9550 bits: 64 type: MCP
    smt: <unsupported> arch: Penryn rev: A cache: L1: 256 KiB L2: 12 MiB
  Speed (MHz): avg: 2829 min/max: 2000/2834 cores: 1: 2829 2: 2829 3: 2829
    4: 2829 bogomips: 22664
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK107 [GeForce GT 740] driver: nvidia v: 470.256.02
    arch: Kepler-2 pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0fc8
    class-ID: 0300
  Display: x11 server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-size: <missing: xdpyinfo>
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: LG (GoldStar) FHD
    serial: <filter> res: mode: 1920x1080 hz: 100 scale: 100% (1) dpi: 102
    size: 480x260mm (18.9x10.24") diag: 546mm (21.5") modes: max: 1920x1080
    min: 640x480
  API: Vulkan v: 1.4.309 layers: 1 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: N/A device-ID: 10de:0fc8
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  Info: Tools: api: vulkaninfo de: kscreen-doctor
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio
    vendor: Gigabyte GA-D525TUD driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:27d8 class-ID: 0403
  Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b class-ID: 0403
  API: ALSA v: k6.13.8-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pw-jack type: plugin
Network:
  Message: No PCI device data found.
  Device-1: Ralink 802.11 n WLAN driver: rt2800usb type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 2-8:5 chip-ID: 148f:5370 class-ID: 0000
    serial: <filter>
  IF: wlp0s29f7u8 state: up mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 22.59 GiB (1.6%)
  ID-1: /dev/sda vendor: A-Data model: SU800 size: 476.94 GiB
    speed: <unknown> tech: SSD serial: <filter> fw-rev: 8B scheme: MBR
  ID-2: /dev/sdb vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
    speed: <unknown> tech: HDD rpm: 7200 serial: <filter> fw-rev: A7C0
    scheme: MBR
Partition:
  ID-1: / size: 68.35 GiB used: 16.49 GiB (24.1%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 29.36 GiB used: 6.1 GiB (20.8%) fs: ext4 dev: /dev/sda6
Swap:
  ID-1: swap-1 type: partition size: 7.91 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 57.0 C mobo: N/A gpu: nvidia temp: 47 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 30%
Info:
  Memory: total: 4 GiB available: 3.82 GiB used: 1.68 GiB (43.9%)
  Processes: 196 Power: uptime: 3m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 257 default: graphical
  Packages: pm: pacman pkgs: 843 Compilers: gcc: 14.2.1 Shell: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.37

Thanks for reading this large post and your time,
LL

Last edited by LinuxLover471 (2025-03-30 06:21:02)

seth · 2025-03-27 08:05:46

No xorg.conf in /etc/xorg.conf?

Do not attempt to create one.

Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1
Mar 26 20:15:13 archlinux kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes

Dump the edid from a boot w/ the nvidia driver and try to inject that, https://wiki.archlinux.org/title/Kernel … s_and_EDID
You'll have to add

nvidia_drm.modeset=1

to the https://wiki.archlinux.org/title/Kernel_parameters to get it exposed to the drm subsystem - you can also leave that parameter when using nouveau.
Though the simpledrm device doesn't show up in your journal?

LinuxLover471 · 2025-03-27 15:23:38

seth wrote:

Dump the edid from a boot w/ the nvidia driver and try to inject that, https://wiki.archlinux.org/title/Kernel … s_and_EDID
You'll have to add
nvidia_drm.modeset=1
to the https://wiki.archlinux.org/title/Kernel_parameters to get it exposed to the drm subsystem - you can also leave that parameter when using nouveau.
Though the simpledrm device doesn't show up in your journal?

Hey, I extracted the edid from get-edid and confirmed it with parse-edid command, then I copied it to /usr/lib/firmware/edid/edid.bin and also added an entry in mkinitcpio's Files section, then I tried rebooting with all the kms and nouveau options in the mkinitcpio and also removed the nvidia drivers but when I rebooted it was still not able to show the display, I will extract the logs tomorrow and post them here. Also I kept the nvidia_drm.modeset=1 option.

Also I noticed I can now boot into the system with the default/normal initramfs with the nomodeset options, whereas I was not able to do that normally. This is an improvement.

I forgot to extract the logs because my system was unstable with the nomodeset option and it was crashing too much so I used timeshift-gui to revert back. Thus, I am able to post this post.

Edit-
I think I was able to extract the logs with journalctl -b -2
https://pastebin.com/2GRiEHBe
I hope they are the right logs.
Thanks for your time,
LL

Last edited by LinuxLover471 (2025-03-27 15:27:49)

seth · 2025-03-27 16:02:21

That journal uses the nvidia driver? (And seems to be the boot where you copied the edid)

LinuxLover471 · 2025-03-28 03:13:24

seth wrote:

That journal uses the nvidia driver? (And seems to be the boot where you copied the edid)

I think the logs got reset because of the timeshift, my bad, I would extract them today, thanks for your time.

LinuxLover471 · 2025-03-29 03:54:57

I finally extracted the logs, sorry for being extremely late, it took me more than 24 hours because I forgot. Also this time I am not able to boot with the normal initramfs and nomodeset, the same goes for the fallback initramfs, it's just stuck on reached Graphical environment.

Here is the nomodeset version-
https://pastebin.com/wSpQe2XL

Here is the one with some added options (The ones mentioned in the arch wiki nouveau page, like the MSI option) -
https://pastebin.com/92pmWJLP

Probably the most important version without the nomodeset option-
https://pastebin.com/1YjQzGVf

Thanks,
LL

Last edited by LinuxLover471 (2025-03-29 03:59:29)

seth · 2025-03-29 07:27:30

… drm.edid_firmware=edid/edid.bin …
…
Mar 29 08:49:00 G31M-ES2L kernel: nouveau 0000:01:00.0: drm: DDC responded, but no EDID for DVI-I-1
…

You've nouveau in the initramfs, did you add the edid there as well?

drm.edid_firmware=DVI-I-1:edid/edid.bin

LinuxLover471 · 2025-03-29 09:10:56

seth wrote:

You've nouveau in the initramfs, did you add the edid there as well?
drm.edid_firmware=DVI-I-1:edid/edid.bin

I did add the edid. I just typed in /usr/lib/firmware/edid/edid.bin in the Files section of the initramfs and updated it.

Is it necessary to add DVI-I-1 option? I only use the HDMI port of my monitor and GPU.

Thanks,
LL

Last edited by LinuxLover471 (2025-03-29 09:12:56)

seth · 2025-03-29 09:13:23

Is it necessary to add DVI-I-1 option?

Technically not, but it will stress where to apply that.
Does the edid show up in /sys/class/drm/* ?
Can you sh into the system and add it there at runtime (and then start a display server)?

LinuxLover471 · 2025-03-29 09:17:33

seth wrote:

Does the edid show up in /sys/class/drm/* ?

I will check and then report.

seth wrote:

Can you sh into the system and add it there at runtime

I will try that right now, thanks!

Also here is my ls of /sys/class/drm/* with the nvidia driver to compare it with the nouveau one.-

/sys/class/drm/version

/sys/class/drm/card0:
card0-DVI-I-1  card0-HDMI-A-1  card0-VGA-1  dev  device  power  subsystem  uevent

/sys/class/drm/card0-DVI-I-1:
connector_id  device  dpms  edid  enabled  modes  power  status  subsystem  uevent

/sys/class/drm/card0-HDMI-A-1:
connector_id  device  dpms  edid  enabled  modes  power  status  subsystem  uevent

/sys/class/drm/card0-VGA-1:
connector_id  device  dpms  edid  enabled  modes  power  status  subsystem  uevent

/sys/class/drm/renderD128:
dev  device  power  subsystem  uevent

Last edited by LinuxLover471 (2025-03-29 09:23:46)

LinuxLover471 · 2025-03-29 09:48:24

This is what I got in /sys/class/drm/*

/sys/class/drm/version

/sys/class/drm/card0:
card0-DVI-I-1
card0-HDMI-A-1
card0-VGA-1
dev
device
power
subsystem
uevent

/sys/class/drm/card0-DVI-I-1:
connector_id
device
dpms
edid
enabled
modes
power
status
subsystem
uevent

/sys/class/drm/card0-HDMI-A-1:
connector_id
device
dpms
edid
enabled
modes
power
status
subsystem
uevent

/sys/class/drm/card0-VGA-1:
connector_id
device
dpms
edid
enabled
modes
power
status
subsystem
uevent

/sys/class/drm/renderD128:
dev
device
power
subsystem
uevent

Wait I forgot to add it at runtime, sorry, let me try again.

Edit-
Some logs-
https://pastebin.com/Wn77F20Q

Last edited by LinuxLover471 (2025-03-29 09:54:27)

seth · 2025-03-29 09:50:00

edid-decode /sys/class/drm/card0-DVI-I-1/edid

LinuxLover471 · 2025-03-29 10:36:30

seth wrote:

edid-decode /sys/class/drm/card0-DVI-I-1/edid

Sadly I got no output, I tried using > edid.txt but there was no output, I had to rely on this to be able to read it because the display was off. And I still wasn't able to reach the Display Manager. Also the command is decode-edid, I dont't know why though.
I tried to load the edid but it didn't work.

Thanks,
LL

seth · 2025-03-29 10:38:39

https://github.com/timvideos/edid-decode/

cat /sys/class/drm/card0-DVI-I-1/edid | curl -F 'file=@-' 0x0.st

LinuxLover471 · 2025-03-29 10:57:01

seth wrote:

cat /sys/class/drm/card0-DVI-I-1/edid | curl -F 'file=@-' 0x0.st

I was just added > logs.txt and read that with nomodeset option, it said that-

451 Unavailable For Legal Reasons

seth · 2025-03-29 11:07:15

You can also just copy that file somewhere and upload it to termbin or a google drive, but this will under no circumstances work when "nomodeset" is in place.

LinuxLover471 · 2025-03-29 11:30:09

seth wrote:

You can also just copy that file somewhere and upload it to termbin or a google drive, but this will under no circumstances work when "nomodeset" is in place.

I know it would not work with the nomodeset option, that's why I blindly tried to extract the link with it. I logged in without nomodeset, and after the command used nomodeset to actually be able to read the contents and post it at here.

I will try this.

Thanks,
LL

LinuxLover471 · 2025-03-29 11:43:39

I tried copying the file as logs.txt, again, but the file does not have any content it has a space occupation of 0.

I also explicitly stated in the kernel parameters to add this parameter to the DVI port.

Wait, i don't have any DVI port on the monitor, so what would it do of the edid? I do have 1 in the GPU, but it shouldn't be related to that, right? Also my monitor only has VGA and HDMI.

Thanks,
LL

seth · 2025-03-29 17:09:47

cp /sys/class/drm/card0-HDMI-A-1/edid hdmi.edid
cp /sys/class/drm/card0-VGA-1/edid vga.edid

See whether either of thos is not empty, maybe the DVI error indicates nouveau being dead-set on the wrong output, see https://www.kernel.org/doc/Documentation/fb/modedb.rst to specifically enable one.
Maybe it's all just a wild goose chase

LinuxLover471 · 2025-03-30 06:10:48

Hey, Adding the video=HDMI-A-1=1920x1080@100e option and video=VGA-1:d video=DVI-I-1:d options fixed the issue!

The driver is loaded, but when I tried to use wayland, the display is kind of blurry, especially the DE options, like the wifi applet, and the system settings app, which is annoying, I like sharp looks. I hope that you can tell me how to fix it, also there are a few graphical issues in the games ( I tried running doom3 vanilla which is based on opengl through wine). There is lag when scrolling through web pages. X11 looks sharp but I wanted to use wayland (It was the whole point of installing nouveau). Also occasionally the mouse becomes super large and then becomes normal again. When I load arch linux from the bootloader, the screen gets transferred to the upper right side of the monitor taking approximately 1:4 of the screen. And get's fixed as soon as the display manager loads. Also the minimize and maximize options are gone from my zen browser.

Edit=
It seems my display was scaled to 105%, changing it to 100 fixed the blur issue.
It seems the mouse was not an issue and actually a feature, I am so dumb lol.
The zen browser minimize and maximize options are back.
The graphical issue in doom3 are still there.

All in all, thank you very much! (You received eternal gratitude).

Thanks,
LL

Last edited by LinuxLover471 (2025-03-30 06:30:14)

seth · 2025-03-30 10:48:29

You should probably open a new thread for the superturboturkeypuncher³ glitches (and elaborate which engine implementation you run and link a screenshot)

Arch Linux

#1 2025-03-27 06:35:20

[Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#2 2025-03-27 08:05:46

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#3 2025-03-27 15:23:38

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#4 2025-03-27 16:02:21

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#5 2025-03-28 03:13:24

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#6 2025-03-29 03:54:57

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#7 2025-03-29 07:27:30

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#8 2025-03-29 09:10:56

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#9 2025-03-29 09:13:23

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#10 2025-03-29 09:17:33

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#11 2025-03-29 09:48:24

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#12 2025-03-29 09:50:00

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#13 2025-03-29 10:36:30

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#14 2025-03-29 10:38:39

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#15 2025-03-29 10:57:01

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#16 2025-03-29 11:07:15

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#17 2025-03-29 11:30:09

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#18 2025-03-29 11:43:39

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#19 2025-03-29 17:09:47

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#20 2025-03-30 06:10:48

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

#21 2025-03-30 10:48:29

Re: [Solved]Nouveau driver=blank screen, GT740. Monitor gets no signal.

Board footer