Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 162011 - 'Mode "1600x1200" is larger than BIOS programmed panel size' improper
Summary: 'Mode "1600x1200" is larger than BIOS programmed panel size' improper
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 4
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-29 02:51 UTC by P Wolf
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-09-14 08:48:02 UTC

Attachments (Terms of Use)
Xorg.0.log (deleted)
2005-06-29 02:56 UTC, P Wolf
no flags Details
xorg.conf (deleted)
2005-06-29 02:57 UTC, P Wolf
no flags Details

System ID Priority Status Summary Last Updated 4314 None None None Never

Description P Wolf 2005-06-29 02:51:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
Xorg.0.log shows the message, 'Mode "1600x1200" is larger than BIOS programmed panel size of 1280 x 1024.  Removing.'  System-config-display offers 1600x1200 anyway, but when I select it and relogin, something strange happens (see Actual Results).

The monitor is a 1600x1200 Dell 2001FP (Digital).  The video card is an NVidia GeForce 6800.  Win XP manages them at 1600x1200 so I know the hardware is ok.

The computer itself is a Dell Dimension 8400.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Use system-config-display to set up for a Dell 2001FP (Digital) and NVidia GeForce 6800.
2.Relogin. It defaults to 800x600. Use system-config-display to adjust the resolution. Notice it offers resolutions 1600x1200 and even higher. Choose 1600x1200.
3.Relogin. Notice how the menus at top and bottom of the FC4 desktop are only visible if you chase them with the mouse.
4.Use system-config-display to step down to 1280x1024.  Relogin.  Now it is fine (except that the display is fuzzy, faking 1280x1024 on a 1600x1200 LCD!).

Actual Results:  When I select a resolution above 1280x1024 and relogin, here is the strange thing that happens.  The screen continues to use 1280x1024 resolution and offer a 1280x1024 desktop, but it reserves black bands at top and bottom and I can pan around the desktop using the mouse.  In short, it is not as good as the real 1280x1024.

Expected Results:  Win XP can use this monitor/NVidia combination at 1600x1200, and Xorg.0.log shows log notes indicating that it sensed a "supported" mode at 1600x1200.  I expected to be able to use 1600x1200 resolution in Linux as I do in Windows.

Additional info:

Comment 1 P Wolf 2005-06-29 02:56:25 UTC
Created attachment 116106 [details]

Comment 2 P Wolf 2005-06-29 02:57:52 UTC
Created attachment 116107 [details]

Comment 3 Mike A. Harris 2005-08-30 11:40:52 UTC
From what you've provided above, this appears to either be a video BIOS
bug, a misconfiguration, or a bug in the 'nv' driver.

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Dell 2001FP (Digital)"
	DisplaySize  410	310
	HorizSync    31.0 - 80.0
	VertRefresh  56.0 - 76.0
	Option	    "dpms"

The H/V ranges here seem a bit suspect to me. Please refer to the display
manufacturer's official documentation and confirm wether these ranges are
correct or not.  If they are incorrect, please attach the manufacturer's
*.INF file for this display, which should have come on a CDROM with the
display, or alternatively from your manufacturer's website.

If the problem turns out to be due to improper H/V ranges, and you attach
the requested .INF file, please reassign the bug to the "hwdata" component
and we'll update our hardware database with the correct settings.

If the H/V ranges are correct however, or if the problem is not resolved
by changing them, then the problem may be a video BIOS issue, or a bug
in the "nv" driver.  In this case, you will need to file a bug report in
the upstream X.Org bug tracker located at in
the "xorg" component against the "nv" driver, so that the driver
maintainers can investigate the problem and try to find a fix or some
kind of workaround.

Setting status to "NEEDINFO_REPORTER", awaiting status update including
Horiz/vert refresh testing results, and/or upstream bug URL for tracking.

Comment 4 P Wolf 2005-08-30 23:59:35 UTC
(In reply to comment #3)

The H/V ranges match the user's manual.  I put in bug #4314.

Comment 5 Olivier Baudron 2005-09-05 07:53:17 UTC
Can you try with the latest xorg-x11 (6.8.2-37.FC4.45) ? Thanks in advance.

Comment 6 P Wolf 2005-09-05 12:30:02 UTC
The problem still occurs with xorg-x11-6.8.2-37.FC4.45

Comment 7 Mike A. Harris 2005-09-14 08:48:02 UTC
Thanks for the upstream bug URL.  Setting status to "UPSTREAM" for tracking
in X.Org bugzilla.

Comment 8 Dax Kelson 2006-03-02 08:13:37 UTC
I'm suffering with this problem with FC5 test releases and rawhide.

Note You need to log in before you can comment on or make changes to this bug.