Bug 8778 - X.org 7.1 doesn't find my Mobility X700
Summary: X.org 7.1 doesn't find my Mobility X700
Status: RESOLVED DUPLICATE of bug 6796
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.1 (2006.05)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-26 08:32 UTC by speedator
Modified: 2006-11-18 09:00 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (21.25 KB, text/plain)
2006-10-26 08:33 UTC, speedator
no flags Details

Description speedator 2006-10-26 08:32:27 UTC
X.org 7.1 doesn't find my graphics card.

If I boot with Live-CD(Ubuntu Edgy) there is first:

PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMConfig

And this, which appears also with Dapper(and other distributions like fedora),
but doesn't result in problems:
PCI: Cannot allocate resource region 7 of bridge 0000:00:1c0

Then:
Faild to start the x-server
(EE)No device detected
Fatal server error: no screen found

ATI Mobility Radeon X700 on Fujitsu-Siemens Amilo M1437G
Comment 1 speedator 2006-10-26 08:33:49 UTC
Created attachment 7534 [details]
Xorg.0.log
Comment 2 speedator 2006-10-27 03:48:01 UTC
Tested with Mandriva 2007 and Fedora 6 and have the same problem.
So this seems a general X.org 7.1 problem.
I pretty hope this works again for 7.2.
Comment 3 Timo Jyrinki 2006-11-01 12:55:38 UTC
Again Mach64 detection routine haunting the X300-X800 cards, marking duplicate
of 6796. And no, unfortunately it is not working in X.org 7.2 either. (if you
manually edit the xorg.conf and change the string "ati" to "radeon", it should
work though, but out-of-the-box experience is basically the blue screen of X or
something similar).

*** This bug has been marked as a duplicate of 6796 ***
Comment 4 speedator 2006-11-18 09:00:25 UTC
Doesn't work. Neither with "ati" nor with "radeon".


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.