Benjamin Herrenschmidt <benh@au1.ibm.com> writes: The log is incomplete... looks like the bcm43xx driver is so verbose, it kicked useful things out. Thus I can't see the output from the video driver which is the interesting bit... Also, is it nvidiafb or rivafb ? For a week or so I'm following linux-2.6 trunk kernels (thank's Maximilian), but the problem I reported and opened

On Tue, Aug 07, 2007 at 03:47:39PM +0200, Antonio-M. Corbi Bellot wrote: Hi: I've narrowed a little bit the problem, let's see: I usually work with an external monitor attached to the powerbook (see my xorg.conf attached), well, the problems with the framebuffer I described in this bug seem to happen _only_ when I've attached the external monitor but _not_ when I use only

On Mon, Jul 30, 2007 at 03:39:24PM +0200, Antonio-M. Corbi Bellot wrote: Benjamin Herrenschmidt <benh@au1.ibm.com> writes: The log is incomplete... looks like the bcm43xx driver is so verbose, it kicked useful things out. Thus I can't see the output from the video driver which is the interesting bit... Also, is it nvidiafb or rivafb ? After sending the bug report

Benjamin Herrenschmidt <benh@au1.ibm.com> writes: The log is incomplete... looks like the bcm43xx driver is so verbose, it kicked useful things out. Thus I can't see the output from the video driver which is the interesting bit... Also, is it nvidiafb or rivafb ? After sending the bug report I compiled myself a vanilla 2.6.22.1 from kernel.org and the framebuffer is correctly detected