[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: powerpc daily sid_d-i CD builds working again



On Tue, May 16, 2006 at 09:53:53AM +0200, Yves-Alexis Perez wrote:
> On Tue, 2006-05-16 at 08:23 +0200, Sven Luther wrote:
> > On Tue, May 16, 2006 at 12:17:10AM +0200, Yves-Alexis Perez wrote:
> > > 0 OFfb ATY,264LTP
> > > 1 OFfb ATY,264LTP
> > 
> > Ok, this is atyfb, and you probably have a rage something chip in there. I
> > wonder about the two fbdevs, but i suppose this is one for the external port,
> > and one for the LCD panel. Do you per chance have an external monitor
> > connected ?
> 
> No, but I can connect one if needed.
> > 
> 
> > > dmesg says nothing about framebuffer. The .config is the one used when
> > > generating powerpc gtk installer, don't know where to find it.
> > 
> > Ok.
> 
> But syslog does. See http://heracles.corsac.net/~corsac/hydra/syslog
> 
> Jan  1 00:02:32 kernel: atyfb: using auxiliary register aperture
> Jan  1 00:02:32 kernel: atyfb: 3D RAGE LT PRO (Mach64 LI, PCI) [0x4c49 rev 0xdc]
> Jan  1 00:02:32 kernel: atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MHz PLL, 100 Mhz MCLK, 100 MHz XCLK
> Jan  1 00:02:32 kernel: atyfb: monitor sense=62b, mode 6
> Jan  1 00:02:32 kernel: Console: switching to colour frame buffer device 128x48
> Jan  1 00:02:32 kernel: atyfb: fb0: ATY Mach64 frame buffer device on PCI

Ok. 

My diagnostic here, is that g-i makes some assumptions that are wrong on
powerpc. Most probably it tries to load the vesafb module, but since the above
is builtin in the powerpc kernel, that test fails, obviously. Furthermore,
vesafb is a x86-only thingy.

Friendly,

Sven Luther



Reply to: