Bug 14060 - Server fails to start with randr 1.2 and a NV20
Summary: Server fails to start with randr 1.2 and a NV20
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.3 (2007.09)
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-13 10:13 UTC by Mathieu Bérard
Modified: 2008-01-19 02:54 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log with randr 1.2 enabled (42.08 KB, text/x-log)
2008-01-13 10:13 UTC, Mathieu Bérard 		no flags Details
Xorg.0.log with randr 1.2 disabled (75.55 KB, text/x-log)
2008-01-13 10:14 UTC, Mathieu Bérard 		no flags Details
xorg.conf (1.15 KB, application/octet-stream)
2008-01-13 10:16 UTC, Mathieu Bérard 		no flags Details
View All

Description Mathieu Bérard 2008-01-13 10:13:08 UTC 
Created attachment 13699 [details]
Xorg.0.log with randr 1.2 enabled

Xorg fails to start with the following error:

(EE) NOUVEAU(0): 1484: No valid modes.
(EE) Screen(s) found, but none have a usable configuration.

if randr 1.2 is enabled

Logs also report unknown DCB 1.4 / 1.5 entry.
Comment 1 Mathieu Bérard 2008-01-13 10:14:53 UTC 
Created attachment 13700 [details]
Xorg.0.log with randr 1.2 disabled
Comment 2 Mathieu Bérard 2008-01-13 10:16:00 UTC 
Created attachment 13701 [details]
xorg.conf
Comment 3 Mathieu Bérard 2008-01-13 10:18:13 UTC 
The card has 1 VGA, 1 DVI and 1 S-Video outputs.

lspci -vvv info:

01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 500] (rev a3) (prog-if 00 [VGA])
	Subsystem: Micro-Star International Co., Ltd. Unknown device 5301
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d8000000 (32-bit, prefetchable) [size=64M]
	Region 2: Memory at ddb80000 (32-bit, prefetchable) [size=512K]
	Expansion ROM at dfdf0000 [disabled] [size=64K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [44] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
		Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4
Comment 4 Maarten Maathuis 2008-01-17 06:06:36 UTC 
Have you asked malc0 in the irc channel?
Comment 5 Mathieu Bérard 2008-01-17 08:26:12 UTC 
Yes,
IIRC, the code force an error when unknown DCB entries are found to make sure
they get reported. I was told to comment the corresponding block of code in nv_bios.c and the server is now up and running with randr 1.2 . I saw a commit on that particular piece of code (4744e5410c27d8bd3c2f92bee4554801639dba29) just after I made the bug report. But xserver still refuse to launch out of the box, I still have to comment the block around ' ErrorF("Unknown DCB 1.4 / 1.5 entry, please report\n");' .
If failing on unknown DCB entries is indeed an intended 'feature', maybe this bug can be closed....

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.