Bug 22265 - GeForce3 Ti 500 - Unknown DCB 1.5 entry
Summary: GeForce3 Ti 500 - Unknown DCB 1.5 entry
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-12 21:15 UTC by Martin Mueller
Modified: 2011-02-08 09:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Zipfile containing Xorg.0.log and the output of lspci -vvnn (4.79 KB, application/octet-stream)
2009-06-12 21:15 UTC, Martin Mueller 		no flags Details
View All

Description Martin Mueller 2009-06-12 21:15:18 UTC 
Created attachment 26746 [details]
Zipfile containing Xorg.0.log and the output of lspci -vvnn

I've tried to use the Nouveau Driver on an Fedora 11 installation
Linux  2.6.29.4-167.fc11.i586 #1 SMP Wed May 27 17:14:37 EDT 2009 i686 athlon i386 GNU/Linux

Video Card is a GeForce3 Ti 500 

Using the nouveau driver in my xorg.conf I get a blank screen after booting the system. (Text Console works) 

Looking at Xorg.0.log the following lines are found

(II) NOUVEAU(0): BMP BIOS found
(II) NOUVEAU(0): BMP version 5.20
(II) NOUVEAU(0): Bios version 03.20.00.20
(II) NOUVEAU(0): Found Display Configuration Block version 1.5
(!!) NOUVEAU(0): Raw DCB entry 0: f0003f00 000088b8
(!!) NOUVEAU(0): Raw DCB entry 1: f2205002 ffffffff
(EE) NOUVEAU(0): Unknown DCB 1.5 entry, please report

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812d07b]
1: /usr/bin/Xorg(xf86SigHandler+0x9e) [0x80c061e]
2: [0xc1a400]
3: /usr/lib/xorg/modules/drivers//nouveau_drv.so(NvSetupOutputs+0x3b) [0x1f16ab]
4: /usr/lib/xorg/modules/drivers//nouveau_drv.so [0x1e8c4a]
5: /usr/bin/Xorg(InitOutput+0x4e9) [0x80a8e39]
6: /usr/bin/Xorg(main+0x1cb) [0x806b92b]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0xaa5a66]
8: /usr/bin/Xorg [0x806afa1]

Fatal server error:
Caught signal 11.  Server aborting

Is there a workaround (special configuration entry, kernel parameter etc.) available?
Comment 1 Marcin Slusarz 2010-10-13 11:46:05 UTC 
This is a bug in UMS, which was dropped 10 months ago. Current KMS code seems to handle this case.

Can you test current Nouveau and verify this?
Comment 2 Lucas Stach 2011-02-08 09:01:57 UTC 
No reaction from reporter for three months now, should work with recent versions. If not please open a new bug.

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.