Re: X won't start: radeon

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

On Thu, 16 Jul 2009 20:48:22 -0400
Michael <macallan%NetBSD.org@localhost> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> On Jul 16, 2009, at 5:54 PM, Steven Bellovin wrote:
> 
> >
> > On Jul 16, 2009, at 5:34 PM, Michael wrote:
> >
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Hello,
> >>
> >> On Jul 16, 2009, at 5:07 PM, Steven Bellovin wrote:
> >>
> >>>
> >>> On Jul 16, 2009, at 5:01 PM, Matthias Scheler wrote:
> >>>
> >>>>
> >>>> On 16 Jul 2009, at 21:49, Steven Bellovin wrote:
> >>>>> I saw another thread that described the need for
> >>>>>
> >>>>>         PCI_ALLOW_MMAP
> >>>>>
> >>>>> in the kernel, albeit to fix different symptoms.  Is that what
> >>>>> I should try?
> >>>>
> >>>>
> >>>> No, that option no longer exists:
> >>>>
> >>>> http://mail-index.netbsd.org/source-changes/2009/07/14/msg223103.html
> >>>
> >>> Got it -- but any guesses on what I should try?
> >>
> >> You could show us your Xorg.0.log for starters.
> >> ( it still works on my U60 with a radeon as 2nd head )
> >>
> > Sorry -- I should have said there appeared to be nothing of
> > interest in it.  Anyway -- the log from trying to use -configure is
> > in http://www.machshav.com/~smb/Xorg.0.log .  If I fire up X after
> > removing the xorg.conf file, it doesn't get that error, but it
> > never displays anything and eventually exits. That log is at
> > http://www.machshav.com/~smb/noconfig-Xorg.0.log . I'm running a
> > GENERIC kernel.
> 
> Looks like it's one of those radeons that appear as two devices.
> Also, Xorg -configure doesn't seem to know about PCI domain numbers
> ( notice the @1 in the PCI identifier in the 2nd log? )
> I don't really know why exactly this one fails but what you can try
> is:
> - - use your old config
> - - replace the PCI bus identifier in the Device section with "PCI: 
> 01@01:00:0"
> - - cross fingers

Didn't work: "No screens found."  Do you want the whole log again?
> 
> There was talk on the xorg-devel list recently about removing Xorg - 
> configure completely because it doesn't always generate usable
> config files, the general consensus seemed to be to fix it though, so
> it would generate the same config as what Xorg would use without a
> config file.

Well, it didn't work for me without a config file, either...

> As a short term fix I'll look at the code and see if I can teach it
> to output PCI identifiers with domain numbers. We'll need that anyway.
> 

We need *something* to make it easy to configure X.  It used to be very
hard, was blessedly easy for a few years, and now seems to be
reverting...
>

                --Steve Bellovin, http://www.cs.columbia.edu/~smb