Bug#413424:

[Rick Thomas <rbthomas55@pobox.com>]

Brice Goglin wrote:

> Rick Thomas wrote:
>
> > Is there anything else in the way of log files or traces I can  
> > provide?
>
> Please send the whole output (as root) of
>     /usr/share/bug/xserver-xorg/script 3>&1
> to your bug report (413424@bugs.debian.org) so that other people on  
> the
> list can look at them and we can point upstream devs at them as well.
>
> thanks,
> Brice



OK here it is... (attachment "x-errors")
Other texts are transcripts of other emails apparently sent to the  
wrong bug-report.


I'll be happy to follow-up on any suggestions as to what to test now...

Rick

Attachment: x-errors
Description: Binary data

========================================================================

> On Mon, Mar 24, 2008 at 07:50:18PM +0100, Brice Goglin wrote:
>
> > Hello,
> >
> > All of you guys reported a failure of the Xserver on your machine
> > because of PCI resource conflicts between the graphic and the network
> > boards. The upstream developers suspect that this is fixed nowadays
> > thanks to the PCI rework in the upcoming Xserver 1.5.
>
> Xserver 1.5-rc5 (xserver-xorg-core 2:1.4.99.905-1) and
> ati/radeon (1:6.9.0-2) r128/mach64 (6.8.0-2) are now available
> in experimental for powerpc. Please give it a try.
>
> Brice




> On Jul 23, 2008, at 3:45 PM, Brice Goglin wrote:
>
>
> > Rick Thomas wrote:
> >
> > > On Jul 23, 2008, at 3:16 AM, Brice Goglin wrote:
> > >
> > >
> > > > On Mon, Mar 24, 2008 at 07:50:18PM +0100, Brice Goglin wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > All of you guys reported a failure of the Xserver on your machine
> > > > > because of PCI resource conflicts between the graphic and the  
> > > > > network
> > > > > boards. The upstream developers suspect that this is fixed  
> > > > > nowadays
> > > > > thanks to the PCI rework in the upcoming Xserver 1.5.
> > > >
> > > > Xserver 1.5-rc5 (xserver-xorg-core 2:1.4.99.905-1) and
> > > > ati/radeon (1:6.9.0-2) r128/mach64 (6.8.0-2) are now available
> > > > in experimental for powerpc. Please give it a try.
> > > >
> > > > Brice
> > Just add an "experimental" line to your sources.list and use aptitude
> > install -t experimental x11-common xserver- 
> > xorg<alltheoneyouhaveinstalled>
> >
> > Brice
>
> OK, I did that and now X won't start.  FWIW, it chose to remove a  
> bunch of packages, including xserver-xorg-input-mouse and xserver- 
> xorg-input-kbd.  I reinstalled them since the most obvious  
> complaints in the X error messages seemed to indicate that it  
> needed them.
>
> What exactly I have done is:
>
> aptitude -t experimental install xserver-xorg-core x11-common  
> xserver-xorg-video-ati xserver-xorg-video-r128
> aptitude -t experimental install xserver-xorg-input-mouse
> aptitude -t experimental install xserver-xorg-input-kbd
> aptitude -t experimental install x11proto-xf86dri-dev
> aptitude -t experimental install x11proto-dri2-dev




> On Jul 25, 2008, at 7:00 PM, Brice Goglin wrote:
>
>
> > Rick Thomas wrote:
> >
> > > aptitude -t experimental install xserver-xorg-core x11-common
> > > xserver-xorg-video-ati xserver-xorg-video-r128
> >
> > Note that you don't need vidoe-ati since your Device section uses  
> > Driver
> > r128. ati is only needed if you use Driver ati (which will load r128
> > automatically).
> >
> >
> > > aptitude -t experimental install x11proto-xf86dri-dev
> > > aptitude -t experimental install x11proto-dri2-dev
> >
> > These ones only matter when building stuff, not for using X.
>
> OK.  I assume that this means they aren't doing any harm, either.
>
>
>
> > > What did I do wrong?
> >
> > I am not sure. Does it help if you remove "usefbdev" from the device
> > section of xorg.conf ?
>
> I tried that.  Both commenting it out, and setting it to "false"
> Neither helped.
>
>
> > Brice
>
>
>
> Is there anything else in the way of log files or traces I can  
> provide?
>
> Rick