Bug 14491 - enabling randr-1.2 support causes LVDS unknown config bits error when starting the X server
Summary: enabling randr-1.2 support causes LVDS unknown config bits error when startin...
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14405
  Show dependency treegraph
 
Reported: 2008-02-13 17:04 UTC by Travis M.
Modified: 2008-04-26 17:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (58.57 KB, text/x-log)
2008-02-13 17:04 UTC, Travis M.
no flags Details
the hacked EDID file to make my LCD work properly under the propriatory nvidia driver (it works fine with nv and nouveau out-of-the-box) (128 bytes, application/octet-stream)
2008-02-13 17:07 UTC, Travis M.
no flags Details
X log with randr 1.2 enabled (55.82 KB, application/octet-stream)
2008-02-14 07:42 UTC, Henrik Sørensen
no flags Details
Patch to work around DCB v2.0 LVDS config bits issue (850 bytes, patch)
2008-02-18 11:48 UTC, Stuart Bennett
no flags Details | Splinter Review
X.org with patch applied (56.85 KB, application/octet-stream)
2008-02-19 08:18 UTC, Henrik Sørensen
no flags Details

Description Travis M. 2008-02-13 17:04:14 UTC
Created attachment 14298 [details]
Xorg.0.log

I am running Nouveau on a Dell Latitude C840 with an NVIDIA GeForce 4 440 Go which has 64MB of VRAM and AGP 4x. I am the unlucky owner of a C840 with a Samsung LCD that needs a hacked EDID to work properly with the nvidia driver (attached). My Linux kernel version is 2.6.24.1 and I am running Debian Testing (Lenny).

Nouveau was compiled on 02/13/08 (today), and I removed the nvidia driver before installing it.

I get this after enabling randr-1.2 support in the output of startx when it starts the X server:

Raw DCB entry 0: 03000223 00000004
(EE) NOUVEAU(0): Unknown LVDS configuration bits, please report

The X server fails to start because there are no valid video modes to pick from, so all the screens have a invalid configuration. Attached is a detailed Xorg log file that details the register dumps.

lspci | grep -i vga:

01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go] (rev a3)
Comment 1 Travis M. 2008-02-13 17:07:47 UTC
Created attachment 14299 [details]
the hacked EDID file to make my LCD work properly under the propriatory nvidia driver (it works fine with nv and nouveau out-of-the-box)
Comment 2 Henrik Sørensen 2008-02-14 07:40:51 UTC
I have the same issue on my very similiar Dell Insprion 8100 (The pentium 3-m version of the C840 with inspiron stamped on it). The machine also has a NV17
card (gf 4 go 440) with an unknown SXGA+ LCD (1400x1050), it does not require an edid hack or modeline for the nvidia blob, just an override to tell it to use the LCD instead of the vga output it defaults to.

It fails with the same message when randr12 is enabled (works with it disabled):

Raw DCB entry 0: 03000223 00000004
(EE) NOUVEAU(0): Unknown LVDS configuration bits, please report
Comment 3 Henrik Sørensen 2008-02-14 07:42:03 UTC
Created attachment 14311 [details]
X log with randr 1.2 enabled
Comment 4 Stuart Bennett 2008-02-18 11:48:48 UTC
Created attachment 14394 [details] [review]
Patch to work around DCB v2.0 LVDS config bits issue

See what happens with this patch applied
Comment 5 Henrik Sørensen 2008-02-19 08:18:29 UTC
Created attachment 14415 [details]
X.org with patch applied
Comment 6 Danny 2008-03-05 01:22:30 UTC
Do you have any ModeLine, PreferredMode, HorizSync or VertRefresh lines in your Monitor section? 
I am guessing Option "ModeDebug" "yes" may help to find why it fails.

d.
Comment 7 Stuart Bennett 2008-03-08 07:45:23 UTC
Hi, can you confirm that the unknown LVDS config bits issue is now fixed?
Comment 8 Stuart Bennett 2008-04-26 17:09:14 UTC
The LVDS config bits issue in question is fixed. Open a new bug if your laptop still doesn't work.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.