"Input Signal Out of Range" Message

English Install/Boot/Login
1

Greetings to all

I consider myself to be a complete newbie to Linux, although I have once used Linux Mint for about four weeks a year ago.

When I first tried installing Tumbleweed, the monitor – a Mecer TW999 – had displayed the “Input Signal Out of Range” message; and so I put the new HDD into which I wished to install Tumbleweed in another older PC and installed Tumbleweed; I did this so I could connect the display cable to the older PC’s display port. I could not do this on the main PC because it does not have such a port, the only available port there is that of a graphics card, which is an Nvidia GT 520.

I managed to install Tumbleweed into the HDD using the older PC without the monitor displaying the “out of range” message. But as soon as I put the HDD back into the main PC, and connected the display cable to the graphics card, the monitor displayed the message again. I put the HDD back into the older PC, and also connected the graphics card into the older PC, and connected the display cable to the older PC itself, and the display was fine. When I disconnected the display cable from the older PC and connected it to the graphics card, which is now in the older PC, the monitor displayed the message again. This made me suspect the problem is linked with the graphics card.

The menu with such options as “OpenSUSE Tumbleweed,” “Advanced options for OpenSUSE Tumbleweed,” etc., are displayed correctly, but the monitor will display the “out of range” message whenever it goes forward from here, regardless of the option I choose.

I have searched for solutions online, but I have so far found none that are either helpful in my case, or that can be executed by following the listed steps.

May anyone please help me to find a solution to this problem.

2

I have put the HDD back into the older PC, booted into Tumbleweed, installed Nvidia display drivers, turned off the older PC, plugged in the graphics card, connected the display cable onto the graphics card, turned on the older PC, and I got this: paste.opensuse.org/94885063

I don’t know how to get to the normal, graphical desktop environment.

3

I don’t understand how in one scenario you can’t connect the monitor to your “main PC” because it doesn’t have the needed video port (VGA probably) … then in the next scenario you do.

4

the Mercer Monitor appears to be 1440x900…

Maybe the Monitor and machine are not handshaking and the default resolution is being over driven ???

Do you get a boot screen???

At boot screen press e find line starting linux or linuxefi go end of line and enter space and nomodeset. then F10 to continue boot.

Does that work???

5

When that happens, login and do cat /var/log/Xorg.0.log | susepaste and provide the resulting URL.

NVidia’s proprietary drivers install for a particular GPU. If not using that GPU, as in moving the HDD to some other PC, the configuration cannot be expected to work. You could try removing that configuration, simple if it is the single file /etc/X11/xorg.conf, not so simple otherwise. Rename that file after logging in at that text prompt, then try rebooting.

If it doesn’t help, provide better information about your hardware, specifically, what cable type is used in each configuration, and whether both PCs normally use GT 520s, and if they don’t, what it is the other does have. inxi -Gay output pasted here within code tags is good for providing this information if run from within an X session, not quite as good if not. It’s even less helpful if it was necessary to use nomodeset at boot in order to get any X session to start, but better than nothing.

Appending video=1440x900@60 to the linu line after striking E at the grub menu might be more helpful than nomodeset, but don’t try both at once.

6

Thank you for your response. It did not help, unfortunately.

7

I tried renaming the file, which was listed as xorg.conf.d; unfortunately, it did not work. I have since put the older PC back to rest, connected the HDD and graphics card back to the main PC, connected the cable to the graphics card, and reinstalled Tumbleweed. From the beginning, I set the output to be 1024x760 (if I remember well) for the duration of the installation, and it installed without incident; but it again displayed the “out of range message” as soon as it was done installing.

I have tried both no modset and video=somevalue@60, but both didn’t work, even for other values of “somevalue.”

The old PC is not used, but is put to rest. Before this, however, it used the GT 520 without a problem. The hard drives in that PC is have both Windows 7 and Windiws XP installed in them.

The main PC has never used anything else besides the graphics card, and has never had a problem with it. It ran on Windows 10 on an aged hard drive before I decided to install OpenSUSE on this new HDD.

I am unsure how I may obtain the cable information, but it has this text written on it, “E55218 AWM 2919 VW-1 80°C 30V LONGWELL-P LOW VOLTAGE COMPUTER CABLE.”

The PC itself is an i7 with 8GB of RAM installed.

8

VGA missed pin? Count pins on VGA cable.
Or what you are using?

9

I’m using a VGA cable, and all fifteen pins are present.

10

/etc/X11/xorg.conf is a file. /etc/X11/xorg.conf.d is a directory. If /etc/X11/xorg.conf didn’t exist, then it could play no part in the observed problem. There could be files in /etc/X11/xorg.conf.d/ that might have been relevant, but by renaming the directory, your test was actually meaningful, showing that /etc/X11/xorg.con* are a non-issue.

I have tried both no modset and video=somevalue@60, but both didn’t work, even for other values of “somevalue.”
e.g. video=1024x768@60???

I am unsure how I may obtain the cable information, but it has this text written on it, “E55218 AWM 2919 VW-1 80°C 30V LONGWELL-P LOW VOLTAGE COMPUTER CABLE.”
By “cable” here is meant cable connectors. Possibilities for a GT 520 are probably DVI, HDMI & VGA.

How old is this “main PC”? Does it have a UEFI BIOS? If yes, are you booting in UEFI mode? IME, certain GPU/Cable type/Display combinations can be quite cantankerous on PCs with UEFI. Is it possible for you to use a DisplayPort, HDMI or DVI cable instead with the “main PC”?

Something else to try is at the Grub menu strike the E key and append plymouth=0 to the end of the linu line (which probably is wrapped, possibly twice), then proceed with boot.

Booted to a command prompt, you may try

sudo update-alternatives --config default-displaymanager

to switch from whatever login manager is in use to some other. Some possibilities are SDDM, LightDM, GDM, XDM.

11

ILL kernel 5.14 is not compatible with Nvidia yet.
Try to use AMD/ATI/Intel.

12

Yes. I had also tried 800x600@60, but to no avail.

I’m not well-versed in these things. (/.). The cable type is VGA. The graphics card accepts all the types you have listed, but the monitor only accepts VGA and DVI. I had previously stated, mistakenly, that the main PC does not have a display port. It does, but it only takes DVI. I visited local stores today and looked for a DVI cable, or a VGA-to-DVI converter, but I found none.

The main PC is seven-years old. Yes, it does have a UEFI BIOS, and I am booting in UEFI mode. I tried hitting with UEFI mode disabled, but that unfortunately didn’t make any difference.

Thank you very much! =D. I was able to boot into a graphical desktop environment after switching to XDM, if my memory serves me correctly. The resolution is currently set to 1024x768@60 by the system. What I have noticed so far is that the system seems to fail to recognise the graphics card, and the graphics testify to the fact. It also fails to identify the monitor being used. Reddit videos fail to play in both Firefox and Chromium, but YouTube videos play just fine. The PC frequently freezes after some time of being moderately used, but I am unsure if this is an OS issue, or a PC issue.

13

That’s unfortunate. :/. I saw several Reddit users repeating the fact.

I unfortunately don’t have any other graphics card besides this Nvidia one.

14

The above comment is inconsistent with the following statement:

What I have noticed so far is that the system seems to fail to recognise the graphics card, and the graphics testify to the fact. It also fails to identify the monitor being used.

You should boot to a graphical desktop, open a terminal, then do

inxi -Gay

and paste the output here wrapped in code tags so that we get a sense of what’s really going on.

The PC frequently freezes after some time of being moderately used, but I am unsure if this is an OS issue, or a PC issue.
Is this fairly consistent, or more like random? Is the inside of the PC clean and its fans all working? If the problem is more random, it could be a power supply weakness. Some don’t last as long as they should, and develop inconsistent voltages that components sometimes cannot tolerate.

15

I seem to have naively jumped to conclusions. What I meant to say is, when looking in System Settings > Display Configuration, the monitor name is not displayed, but the word “VGA-0” is displayed instead; and that the graphics do not appear polished.

Here’s the output:


**Graphics:**
  **Device-1:** NVIDIA GF119 [GeForce GT 520] **vendor:** Point of View BV  
  **driver:** nvidia **v:** 390.144 **alternate:** nouveau,nvidia_drm **bus-ID:** 01:00.0  
  **chip-ID:** 10de:1040 **class-ID:** 0300  
  **Display:** x11 **server:** X.org 1.20.13 **compositor:** kwin_x11 **driver:**
  **loaded:** modesetting,nvidia **unloaded:** fbdev,vesa **alternate:** nouveau,nv  
  **resolution:** <missing: xdpyinfo>  
  **OpenGL:****renderer:** llvmpipe (LLVM 12.0.1 128 bits) **v:** 4.5 Mesa 21.2.2  
  **compat-v:** 3.1 **direct render:** Yes

The problem seems to have disappeared, although Reddit videos aren’t playing still. It always came specifically about 15-minutes into using a browser. The inside of the PC is clean, and all its fans are working.

16

You still haven’t provided Xorg.0.log as requested in post #5. xdpyinfo should be installed so that inxi info can be complete.

17

I’m sorry. (/.)

Here’s the Xorg.0.log output: https://susepaste.org/75094729

Here’s inixi info after xdpyinfo has been installed:

**

Graphics:** 
  **Device-1:** NVIDIA GF119 [GeForce GT 520] **vendor:** Point of View BV  
  **driver:** nvidia **v:** 390.144 **alternate:** nouveau,nvidia_drm **bus-ID:** 01:00.0  
  **chip-ID:** 10de:1040 **class-ID:** 0300  
  **Display:** x11 **server:** X.Org 1.20.13 **compositor:** kwin_x11 **driver:**  
  **loaded:** modesetting,nvidia **unloaded:** fbdev,vesa **alternate:** nouveau,nv  
  **display-ID:** :0 **screens:** 1  
  **Screen-1:** 0 **s-res:** 1024x768 **s-dpi:** 75 **s-size:** 347x260mm (13.7x10.2")  
  **s-diag:** 434mm (17.1")  
  **Monitor-1:** VGA-0 **res:** 1024x768 **hz:** 60  
  **OpenGL:** **renderer:** llvmpipe (LLVM 12.0.1 128 bits) **v:** 4.5 Mesa 21.2.2  
  **compat-v:** 3.1 **direct render:** Yes
18

As you have installed NVidia’s proprietary drivers, which I never do, I’m out of ideas what is going on. That log is very different from logs which I’ve previously seen. It does show errors, but some I’ve never seen before, while some information I expect to see is absent. Unless someone else here chimes in with NVidia driver experience to help further, I can only suggest to either post your problem in NVidia’s own help forums, or uninstall the NVidia driver package to see if standard FOSS drivers can work as they do for me.

19

loaded: modesetting,nvidia

You need only one of them.
Possibly kernel is too new for Nvidia drivers.

Device-1: NVIDIA GF119 [GeForce GT 520]

Maybe Nvidia driver is not supported for this new kernel.

**OpenGL:**renderer: llvmpipe

Kernel is not using Nvidia drivers.

alternate: nouveau,nv

Use Nvidia or nouveau drivers, not both.
It is better to uninstall one of them.

20

Inxi is showing success loading those two modules reported in Xorg.0.log. It will do this whether they were installed or not, unless a driver was explicitly specified in /etc/X11/Xorg.con*.

alternate: nouveau,nv

Use Nvidia or nouveau drivers, not both.
It is better to uninstall one of them.
Inxi is showing Xorg was unable to load those two modules as reported in Xorg.0.log. It will do this whether they were installed or not, unless a driver was explicitly specified in /etc/X11/Xorg.con*.