Bug 12234 - X not starting with latest git using Radeon X700
Summary: X not starting with latest git using Radeon X700
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-31 08:41 UTC by Daniel Qarras
Modified: 2007-08-31 12:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
lspci -vvv output (12.47 KB, text/plain)
2007-08-31 08:42 UTC, Daniel Qarras
no flags Details
Failing X startup log (29.43 KB, text/plain)
2007-08-31 08:51 UTC, Daniel Qarras
no flags Details
xorg.conf (1.06 KB, text/plain)
2007-08-31 08:52 UTC, Daniel Qarras
no flags Details
Log when X starting ok (55.47 KB, text/plain)
2007-08-31 09:45 UTC, Daniel Qarras
no flags Details

Description Daniel Qarras 2007-08-31 08:41:33 UTC
After upgrading my ati radeon drivers to 2007-08-31 git X won't start any more, not matter what config is used. I'll attach output of lspci, xorg.conf and X log.
Comment 1 Daniel Qarras 2007-08-31 08:42:29 UTC
Created attachment 11354 [details]
lspci -vvv output
Comment 2 Daniel Qarras 2007-08-31 08:51:54 UTC
Created attachment 11355 [details]
Failing X startup log
Comment 3 Daniel Qarras 2007-08-31 08:52:22 UTC
Created attachment 11356 [details]
xorg.conf
Comment 4 Daniel Qarras 2007-08-31 08:53:52 UTC
It must be noted that startup won't work even if I comment out modes/dpms/monitor lines or some combination of them.

When testing, there has been no tv-out cable connected.
Comment 5 Alex Deucher 2007-08-31 09:09:05 UTC
The driver is not able to detect any monitors attached.  I disabled load detection on the tv dac since was causing false detections for some people.  What monitors do you have attached to what ports and can you attach a log from when it last worked?
Comment 6 Daniel Qarras 2007-08-31 09:45:54 UTC
Created attachment 11357 [details]
Log when X starting ok
Comment 7 Daniel Qarras 2007-08-31 09:47:11 UTC
My system is an Acer Aspire 1690 laptop with a 1200x800 display. Currently I am using xorg-x11-drv-ati-6.7.192-1.fc8 Fedora RPM which changelog says:

* Tue Aug 28 2007 Adam Jackson <ajax@redhat.com> 6.7.192-1
- xf86-video-ati 6.7.192

* Tue Aug 28 2007 Dave Airlie <airlied@redhat.com> 6.7.191-2
- radeon-6.7.191-git-master.patch - upgrade to git head
  f36720377737210c985b196d9a988efdd767f1c7
Comment 8 Alex Deucher 2007-08-31 11:20:47 UTC
(In reply to comment #7)
> My system is an Acer Aspire 1690 laptop with a 1200x800 display. Currently I am
> using xorg-x11-drv-ati-6.7.192-1.fc8 Fedora RPM which changelog says:
> 
> * Tue Aug 28 2007 Adam Jackson <ajax@redhat.com> 6.7.192-1
> - xf86-video-ati 6.7.192
> 
> * Tue Aug 28 2007 Dave Airlie <airlied@redhat.com> 6.7.191-2
> - radeon-6.7.191-git-master.patch - upgrade to git head
>   f36720377737210c985b196d9a988efdd767f1c7
> 

It should be pretty much the same code then.  When you say you are using the code from git do you mean the randr-1.2 branch or the master branch?  I suspect you are using the randr-1.2 branch which is old.  That branch got merged into master a while back and can be considered dead at this point.  The redhat version is pretty much tracking the master branch so you should be fine.
Comment 9 Daniel Qarras 2007-08-31 11:42:49 UTC
I got the sources with:

git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
Comment 10 Alex Deucher 2007-08-31 11:55:25 UTC
(In reply to comment #9)
> I got the sources with:
> 
> git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
> 

yes, both branches live in the same tree.  the question is, did you check out the randr-1.2 branch (git checkout randr-1.2 or similar) or stay on master.
Comment 11 Daniel Qarras 2007-08-31 12:41:24 UTC
Yep, now it works. Sorry about the noise.


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.