Re: BBB fbdev or lack there of
On Sun, May 11, 2014 at 1:44 PM, Nigel Sollars <nsollars@gmail.com> wrote:
> Hi all,
>
> ive switched back for a bit to the beaglebone after looking into SGX stuff
> on the Panda.
>
> Current OS is Wheezy running
>
> Linux arm 3.14.0-bone0 #1 SMP Wed Apr 2 14:55:38 UTC 2014 armv7l GNU/Linux
>
> I did this one up over netinstall and Robert Nelson's repo for the kernel.
> now with Xorg if I use Xorg -configure I get
>
> No devices to configure. Configuration failed.
>
> fbdev is in the list of drivers, I did look at dmesg to see what was found,
>
> [ 4.290629] tilcdc 4830e000.lcdc: found TDA19988
> [ 4.296075] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [ 4.303034] [drm] No driver support for vblank timestamp query.
> [ 4.309566] tilcdc 4830e000.lcdc: No connectors reported connected with
> modes
> [ 4.317051] [drm] Cannot find any crtc or sizes - going 1024x768
> [ 4.331875] Console: switching to colour frame buffer device 128x48
> [ 4.343381] tilcdc 4830e000.lcdc: fb0: frame buffer device
> [ 4.349272] tilcdc 4830e000.lcdc: registered panic notifier
> [ 4.355125] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0
>
> Could someone point me in the right direction as to what I am missing,
>
> PS. I did read forums about not using any of the omap fb's as apparently
> they are not for this SoC.
Auto-detection doesn't work on this soc, use this xorg.conf for now:
With either the "modesetting" or "fbdev" driver. Note while the
modesetting driver does work it does randomly hardlock the soc. (even
the jtag port hard locks)
Section Monitor
Identifier Builtin Default Monitor
EndSection
Section Device
Identifier Builtin Default fbdev Device 0
# Driver modesetting
# Driver fbdev
EndSection
Section Screen
Identifier Builtin Default fbdev Screen 0
Device Builtin Default fbdev Device 0
Monitor Builtin Default Monitor
DefaultDepth 16
EndSection
Section ServerLayout
Identifier Builtin Default Layout
Screen Builtin Default fbdev Screen 0
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Reply to: