Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 May 2015 09:02:59 -0500
From:      "Zane C. B-H." <v.velox@vvelox.net>
To:        Trevor Roydhouse <trev@sentry.org>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Raspberry Pi 2 - Xorg issues
Message-ID:  <20150526090259.30c74175@vixen42.vulpes.vvelox.net>
In-Reply-To: <555E80F4.7030300@sentry.org>
References:  <555E80F4.7030300@sentry.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 22 May 2015 11:05:56 +1000
Trevor Roydhouse <trev@sentry.org> wrote:

> uname:
> 
> FreeBSD 11.0-CURRENT #0 r282694: Sun May 10 04:33:02 UTC 2015
> 
> dmesg:
> 
> fb0: <BCM2835 VT framebuffer driver> on ofwbus0
> fbd0 on fb0
> VT: initialize with new VT driver "fb".
> fb0: 1824x984(1824x984@0,0) 24bpp
> fb0: fbswap: 1, pitch 5472, base 0x3d359000, screen_size 5428224
> 
> Xorg.conf:
> 
> Section "Screen"
>      Identifier  "Screen"
>      Device      "Generic FB"
>      Monitor     "Monitor"
>      DefaultDepth 16
> 
>      SubSection "Display"
>        Depth      16
>      EndSubsection
> EndSection
> 
> Produces Xorg.0.log:
> 
> [  1051.191] (II) scfb: driver for wsdisplay framebuffer: scfb
> [  1051.272] (--) Using syscons driver with X support (version 2.0)
> [  1051.272] (--) using VT number 5
> [  1051.272] (WW) Falling back to old probe method for scfb
> [  1051.272] scfb trace: probe start
> [  1051.272] (II) scfb(0): using default device
> [  1051.273] scfb trace: probe done
> [  1051.273] (WW) VGA arbiter: cannot open kernel arbiter, no
> multi-card support
> [  1051.273] scfb: PreInit 0
> [  1051.273] (II) scfb(0): Using: depth (24),   width (1824),
> height (984)
> [  1051.273] (EE) scfb(0): specified depth (16) or bpp (16) doesn't 
> match framebuffer depth (24)
> [  1051.273] (II) UnloadModule: "scfb"
> [  1051.273] (EE) Screen(s) found, but none have a usable
> configuration.
> 
> 
> Xorg.conf:
> 
> Section "Screen"
>      Identifier  "Screen"
>      Device      "Generic FB"
>      Monitor     "Monitor"
>      DefaultDepth 24
> 
>      SubSection "Display"
>        Depth      24
>      EndSubsection
> EndSection
> 
> Produces Xorg.0.log:
> 
> [  1286.519] (II) scfb: driver for wsdisplay framebuffer: scfb
> [  1286.640] (--) Using syscons driver with X support (version 2.0)
> [  1286.640] (--) using VT number 5
> [  1286.640] (WW) Falling back to old probe method for scfb
> [  1286.641] scfb trace: probe start
> [  1286.641] (II) scfb(0): using default device
> [  1286.641] scfb trace: probe done
> [  1286.641] (WW) VGA arbiter: cannot open kernel arbiter, no
> multi-card support
> [  1286.641] scfb: PreInit 0
> [  1286.641] (II) scfb(0): Using: depth (24),   width (1824),
> height (984)
> [  1286.641] (EE) scfb(0): specified depth (24) or bpp (32) doesn't 
> match framebuffer depth (24)
> [  1286.641] (II) UnloadModule: "scfb"
> [  1286.642] (EE) Screen(s) found, but none have a usable
> configuration.
> 
> Solution to get X up:
> 
> Leave out DefaultDepth nn in the Screen section, but this yields
> very slow motion screen draws and long cursor tails. However, if I
> run a find / in an xterm, screen draws return to normal until find
> finishes... weird.
> 
> Any other solutions?

I am seeing the exact same thing using a image I built using a fresh
source tree on the 23rd.

It appears to be load related in some manner. For example I can also
get it to behave nicely. If I start compiling something like firefox
or the like.

Make any headway with this on your end?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150526090259.30c74175>