Comments on: Dear Lazyweb — how to get native screen resolution in F7? http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/ Just another GNOME Blogs weblog Fri, 22 Apr 2011 19:06:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Davyd http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-121 Davyd Mon, 13 Aug 2007 10:33:53 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-121 Turns out we sent ours back as defective. Got new ones that worked. Someone suggested that there might be a bad batch kicking around out there. Turns out we sent ours back as defective. Got new ones that worked. Someone suggested that there might be a bad batch kicking around out there.

]]> By: Marc http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-120 Marc Sun, 12 Aug 2007 22:15:06 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-120 VGA isn't so bad compared to DVI...I have a monitor with both VGA and DVI inputs and I'm constantly switching between both. Both inputs are running at 1920x1200, and honestly I couldn't tell you which was VGA if you put a gun to my head. VGA isn’t so bad compared to DVI…I have a monitor with both VGA and DVI inputs and I’m constantly switching between both. Both inputs are running at 1920×1200, and honestly I couldn’t tell you which was VGA if you put a gun to my head.

]]> By: marsbiker http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-119 marsbiker Sun, 12 Aug 2007 20:07:55 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-119 i think the point of the question was (at least for me) how to get the Open Source nv-driver working. Not the Closed Source nvidia-driver. i think the point of the question was (at least for me) how to get the Open Source nv-driver working. Not the Closed Source nvidia-driver.

]]> By: ajax http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-118 ajax Sun, 12 Aug 2007 15:46:01 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-118 See nona's comment above. This is a limitation in the nv driver. We're using a panel setup frontend that's limited by whatever the BIOS configured at boot time, and nv BIOSes have a habit of defaulting to 1280x1024. The usual workaround is to drive the panel over VGA instead, but we are planning to fix this properly someday. See nona’s comment above. This is a limitation in the nv driver. We’re using a panel setup frontend that’s limited by whatever the BIOS configured at boot time, and nv BIOSes have a habit of defaulting to 1280×1024.

The usual workaround is to drive the panel over VGA instead, but we are planning to fix this properly someday.

]]> By: Matthias http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-117 Matthias Sun, 12 Aug 2007 14:48:11 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-117 Hi, I happen to run a Samsung 226BW in its native resolution of 1680x1050 with an nVidia (7600 GS) gfx-card and Fedora 7 just fine. Connecting the monitor by dvi is definitately the preferred method though as the analog connection never got the display size right (though resolution was correct). Maybe you should over to livna.org and grab "livna-config-display"- and the nvidia-driver-packages (they do work with kernels up to 2.16.22.2). No modeline hacks are neccessary in xorg.conf, or what so ever. For me, autodetection just worked right out of the box. If this does not solve the issue, your videocard may be the culprit here - as was mentioned before. Have you tried "the other OS" and checked that its possible there to select and run desired resolution ? I am bit lazy in math things like that, but to me it appears 128 MB RAM is not quite enough to run 1600x1200 in 32bit mode. cheers, Hi,

I happen to run a Samsung 226BW in its native resolution of 1680×1050 with an nVidia (7600 GS) gfx-card and Fedora 7 just fine. Connecting the monitor by dvi is definitately the preferred method though as the analog connection never got the display size right (though resolution was correct).

Maybe you should over to livna.org and grab “livna-config-display”- and the nvidia-driver-packages (they do work with kernels up to 2.16.22.2). No modeline hacks are neccessary in xorg.conf, or what so ever. For me, autodetection just worked right out of the box.

If this does not solve the issue, your videocard may be the culprit here – as was mentioned before. Have you tried “the other OS” and checked that its possible there to select and run desired resolution ? I am bit lazy in math things like that, but to me it appears 128 MB RAM is not quite enough to run 1600×1200 in 32bit mode.

cheers,

]]> By: jeff http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-116 jeff Sun, 12 Aug 2007 12:03:55 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-116 I have a Samsung 204B on debian sid. running from an onboard GeForce 6100 GPU (256MB reserved in BIOS). It was detected and ran at 1600x1200 with no preconfigured xorg.conf file (nv driver) but the display was offset 1.5 cm to the right. I tried proprietory Nvidia drivers but these did not work with the linux 2.6.21 kernel. I now run following patched version at 1600x1200 which can be found with google : NVIDIA-Linux-x86-100.14.11-pkg1-patched.run - the install creates an xorg.conf file. Pls email me for further info. I have a Samsung 204B on debian sid. running from an onboard GeForce 6100 GPU (256MB reserved in BIOS). It was detected and ran at 1600×1200 with no preconfigured xorg.conf file (nv driver) but the display was offset 1.5 cm to the right. I tried proprietory Nvidia drivers but these did not work with the linux 2.6.21 kernel. I now run following patched version at 1600×1200 which can be found with google : NVIDIA-Linux-x86-100.14.11-pkg1-patched.run – the install creates an xorg.conf file. Pls email me for further info.

]]> By: Teo http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-115 Teo Sun, 12 Aug 2007 10:36:31 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-115 Same problem with a Toshiba notebook, resolved with a bit of EDID hacking. Look at http://www.nvnews.net/vbulletin/showthread.php?t=81635&highlight=EDID Same problem with a Toshiba notebook, resolved with a bit of EDID hacking.
Look at http://www.nvnews.net/vbulletin/showthread.php?t=81635&highlight=EDID

]]> By: marsbiker http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-114 marsbiker Sun, 12 Aug 2007 09:50:07 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-114 Hm, i have the same problem with a FSC P20-2 - but only with the nv-driver. nvidia works fine. I would really be interested in a solution - i haven't found one myself and been wondering why nobody else has this problem. Hm, i have the same problem with a FSC P20-2 – but only with the nv-driver. nvidia works fine. I would really be interested in a solution – i haven’t found one myself and been wondering why nobody else has this problem.

]]> By: nona http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-113 nona Sun, 12 Aug 2007 04:07:53 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-113 See: https://bugs.freedesktop.org/show_bug.cgi?id=3654 https://bugs.freedesktop.org/show_bug.cgi?id=4314 If it is what I think it is, it's because your video card's BIOS doesn't have the correct display timings, and the "nv" driver relies on the BIOS for mode setup. The closed source "nvidia" driver doesn't have this problem. See:
https://bugs.freedesktop.org/show_bug.cgi?id=3654
https://bugs.freedesktop.org/show_bug.cgi?id=4314

If it is what I think it is, it’s because your video card’s BIOS doesn’t have the correct display timings, and the “nv” driver relies on the BIOS for mode setup. The closed source “nvidia” driver doesn’t have this problem.

]]> By: Paul http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/comment-page-1/#comment-112 Paul Sun, 12 Aug 2007 04:03:02 +0000 http://blogs.gnome.org/newren/2007/08/11/dear-lazyweb-how-to-get-native-screen-resolution-in-f7/#comment-112 I seem to recall one of the nVidia drivers (proprietary or open) stopped correctly getting the refresh rates from the monitor at some point. I fixed it by using the other driver, noting down the refresh rates it detected and then defining them specifically in my X config file for the other driver. I seem to recall one of the nVidia drivers (proprietary or open) stopped correctly getting the refresh rates from the monitor at some point. I fixed it by using the other driver, noting down the refresh rates it detected and then defining them specifically in my X config file for the other driver.

]]>