Can't get higher than 1024x768 in Linux, but I can in Windows
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
(II) NVIDIA(0): ___:ffff: Using hsync range of 30.00-60.00 kHz
(II) NVIDIA(0): ___:ffff: Using vrefresh range of 50.00-75.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 300.00 MHz
(II) NVIDIA(0): Not using default mode "1152x864" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using mode "1280x1024" (no mode of this name)
(II) NVIDIA(0): Not using default mode "1280x960" (width too large for virtual size)
(II) NVIDIA(0): Not using default mode "1152x768" (width too large for virtual size)
(WW) NVIDIA(0): Not using mode "576x384":
I know this card/monitor combination can do 1280x1024 (because it does in Windows ). I made sure the v & h refresh rates match my monitor (which seemed to be the main problem with other threads that I've searched with similar problmes), but what am I missing? Linux has always looked "bad" for me (mainly fonts and low resolution). I don't play any games before you insult my lowly video card.
Last edited by debuser123; 11-19-2006 at 11:20 PM.
Use gtf to help you make modelines and copy the output to the monitor section of /etc/X11/xorg.conf or /etc/X11/XF86Config-4. Also you may have to add Option "UseEDID" "false" to the same section where you specify nvidia as the driver. You can literally destroy your CRT monitor if you use the wrong setting, so be careful what settings you give it.
If you have nVidia GeForce 256, you will have to use the old nVidia software. The nVidia version 7182 is for GeForce2 Go and up.
Use gtf to help you make modelines and copy the output to the monitor section of /etc/X11/xorg.conf or /etc/X11/XF86Config-4. Also you may have to add Option "UseEDID" "false" to the same section where you specify nvidia as the driver. You can literally destroy your CRT monitor if you use the wrong setting, so be careful what settings you give it.
If you have nVidia GeForce 256, you will have to use the old nVidia software. The nVidia version 7182 is for GeForce2 Go and up.
Thank you for replying. I actually tried drivers 9629, 8776, which both failed saying there was no card found that it supported. 7182 did succeed (which ultimately resulted in me having to mess with building the kernel...which was good times back in the day) but 7182 worked. In the readme file it lists the GeForce 256 as a supported card (with a PCI ID of 0x0100)...lspci confirms that (10de:0100 as I think 0x10de is nVidia's vendor ID). What version drivers should I be looking for? I thought there was going to be "nvidia-legacy" type driver based on what nvidia's web site says but it isn't clear what exactly is the legacy nvidia driver.
I added that modeline and that option in, but it still didn't work.
This was the modeline I used:
...which you can see specifies a hsync of 80.17 kHz when the monitor only goes from 30 - 60.
(log file of course says not using mode 1280x1024_75.00 due to hsync out of range).
If I supplied gtf with a 56Hz refresh rate, this is the highest rate that gives an hsync <60 (59.25KHz). I'm not going to try it though cause I don't want to mess my monitor up. Or will it matter since this is an LCD and not a CRT?
Last edited by debuser123; 11-19-2006 at 10:03 PM.
It's unlikely that you will blow a modern monitor up. You will more than likely get an out-of-range message on the screen if the input signal would possibly damage the monitor.
Your monitor probably has an OSD where you might be able to find which frequencies it uses at 1280x1024 in windows. Check that if you want to feel more secure.
So I would give it a go with a vertical refresh of 56Hz or lower
#1) have to specify a fake hsync range (I just guessed something like 50-80)
#2) have to have a modeline in for 1280x1024 @ 75hz
#3) have that mode listed under the Screen/Display subsection
This is using the nvidia driver (7182)
and now linux actually looks "right"!
The funny thing is is that it doesn't use the mode I specify and then the log displays "default" 1280x1024 modes:
It seems the active mode is the 1280x1024 60hz refresh rate (the 3rd one listed, and which is also verified by my monitors OSD [thanks Wim]). If I do try and use 1280x1024@75Hz, the screen just looks messed up and sometimes goes all-black.
So I really don't know how to describe why it works but....it works.
Regarding #2...I tried a modeline of 60hz, which always resorted in a black non-responsive screen.
Last edited by debuser123; 11-19-2006 at 11:23 PM.
Debian provides old software. I suggest using latest version if possible from the desire Linux distribution.
For nVidia lagency software, you have to look in their archive servers.
If you do not care for 3D rendering, use nv or vesa driver.
Try using Knoppix or Powerstrip in Windows to create modelines.
Quote:
Originally Posted by Wim Sturkenboom
It's unlikely that you will blow a modern monitor up. You will more than likely get an out-of-range message on the screen if the input signal would possibly damage the monitor.
Your monitor probably has an OSD where you might be able to find which frequencies it uses at 1280x1024 in windows. Check that if you want to feel more secure.
So I would give it a go with a vertical refresh of 56Hz or lower
Why is everybody think that electronic devices that get damage, blows up. CRT monitors are the only piece of hardware that can be damaged by software. In Windows, it always states "Do you want to stay with these settings" after you change the resolution or refresh rate. Windows will not know the safest setting. It just reads either EDID, DDC, or guess. In Linux, only two things that is stopping X Window System the vertical and horizontal values. If these are not set, any modeline you add will work. There is no way of X Window System to stop what it is about to do. The latest XFree86 or Xorg, tries to access EDID, DDC, or guess the values, but usually it is half right. It is better to read the monitor's manual, use FCC or UL site to gather the information.
@debuser123
Your screen can NOT handle 1280x1024 @ 75 Hz . Specs are not (good) enough for that !! It's either lower resolution at higher refresh or higher resolution at lower refresh.
This applies to any monitor, not only yours.
@Electro
Talking to me? Maybe my phrasing was not properly choosen. I know that it will not always say 'boom' or that the screen will not explode when it gets damaged.
@debuser123
Your screen can NOT handle 1280x1024 @ 75 Hz . Specs are not (good) enough for that !! It's either lower resolution at higher refresh or higher resolution at lower refresh.
This applies to any monitor, not only yours.
Actually I looked at the OSD (which displays hsync & vrefresh) while in 1280x1024 in windows; 80Khz & 75hz respectively. This stuff is weird or I just don't get it.
With further inspection it seems all I need to do at minimum is:
1) change the hsync range to something "usable"
2) add "1280x1024" to the Screen/Display/Modes option
Even though the official specs say 30-60Khz hsync, the monitor can do up to 80Khz (as it does in Windows verified with the OSD).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.