rawhide install report: failed - now working with xdriver=vesa

[Adam Williamson]

On Mon, 2009-08-17 at 17:37 -0400, G.Wolfe Woodbury wrote:
> On 08/17/2009 04:38 PM, Adam Williamson wrote:
> > On Mon, 2009-08-17 at 14:50 -0400, James Laska wrote:
> >> On Mon, 2009-08-17 at 11:44 -0700, Adam Williamson wrote:
> >>> On Sun, 2009-08-16 at 22:17 -0400, G.Wolfe Woodbury wrote:
> >>>> On 08/16/2009 09:36 PM, G.Wolfe Woodbury wrote:
> >>>>> Did the xdriver=vesa boot parameter and the install is proceeding
> >>>>> normally.  Now about 85% done, further than it's gotten before.
> >>>>>
> >>>> It succeeded. had to add radeon.modeset=0 to GRUB to get it to startup
> >>>> correctly.  No way to predict that.
> >>>
> >>> Usual procedure: file a bug on xorg-x11-drv-ati with the appropriate
> >>> information...
> >>>
> >>> https://fedoraproject.org/wiki/Xorg/Debugging
> >>>
> >>> does the installer boot OK if you use radeon.modeset=0 (but not
> >>> xdriver=vesa)?
> >>
> >> I suspect I'm seeing something similar.  With the latest rawhide
> >> (xorg-x11-drv-ati-6.12.2-21.fc12.i686 and
> >> kernel-2.6.31-0.125.4.2.rc5.git2.fc12.i686), I'm unable to login to
> >> startx without seeing the following segfault.
> >
> > G. Wolfe, can you please check your /var/log/Xorg.*.log after trying to
> > start up with KMS enabled on the affected system to see if your issue is
> > the same as jlaska's? it's quite important - if this is affecting
> > multiple cards it may have implications for the Alpha.
> >
> I don't show a segfault, but the QD 7200 fails to detect a screen and 
> errs out.  The network comes up and the system is running underneath a 
> dead head.  The error in Xorg.0.log is that it can see no monitors 
> definitely connected, then it says screens found but not useable.

Looks like a different bug, then. Can you file it, according to the
instructions I linked above? Thanks.

-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net