On Sat, Jun 28, 2014 at 07:22:36PM +0200, Rainer Dorsch wrote: > you updated https://wiki.debian.org/ArmHardFloatPort/CuBox-i with > > "The 3.15.1-1~exp1+ kernel in experimental also includes support for > framebuffer video over HDMI." ... > and get console output on HDMI. It is not entirely aligned, i.e. at least on > the left and bottom part of the screen a few colums and rows are missing. It's highly dependent on your HDMI display. Some TVs force overscanning, some allow you to change it, and in some the UI to change it is inscrutible. I'd hope actual HDMI monitors work fine in general, but haven't actually tried any. > X does not start though: ... > [ 7.886] (**) |-->Screen "Default Screen Section" (0) > [ 7.886] (**) | |-->Monitor "<default monitor>" > [ 7.887] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. ... > [ 7.916] (II) LoadModule: "modesetting" > [ 7.919] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so > [ 7.923] (II) Module modesetting: vendor="X.Org Foundation" > [ 7.924] compiled for 1.15.1, module version = 0.9.0 > [ 7.924] Module class: X.Org Video Driver > [ 7.924] ABI class: X.Org Video Driver, version 15.0 > [ 7.924] (II) LoadModule: "fbdev" > [ 7.948] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so > [ 7.950] (II) Module fbdev: vendor="X.Org Foundation" > [ 7.950] compiled for 1.15.0, module version = 0.4.4 > [ 7.950] Module class: X.Org Video Driver > [ 7.950] ABI class: X.Org Video Driver, version 15.0 > [ 7.950] (II) modesetting: Driver for Modesetting Kernel Drivers: kms > [ 7.951] (II) FBDEV: driver for framebuffer: fbdev > [ 7.951] (++) using VT number 7 > > [ 7.965] (II) modesetting(G0): using drv /dev/dri/card0 > [ 7.965] (WW) Falling back to old probe method for modesetting > [ 7.965] (WW) Falling back to old probe method for fbdev > [ 7.966] (II) Loading sub module "fbdevhw" > [ 7.966] (II) LoadModule: "fbdevhw" > [ 7.966] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so > [ 7.968] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 7.968] compiled for 1.15.1, module version = 0.0.2 > [ 7.968] ABI class: X.Org Video Driver, version 15.0 > [ 7.968] (EE) No devices detected. > [ 7.968] (EE) > Fatal server error: > [ 7.968] (EE) no screens found(EE) > [ 7.969] (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > [ 7.969] (EE) Please also check the log file at "/var/log/Xorg.0.log" for > additional information. > [ 7.969] (EE) > rd@bokocube:/var/log$ > > Is that the same for you or do you have X.org running? Using the default settings works with the one TV I've tested. I could explore testing another. Though, it only gets 1024x768@16, which some people might not even consider useable. The default monitor configuration may not work with the monitor you're using, the framebuffer settings, or a number of other factors. > rd@bokocube:/var/log$ dmesg |grep hdmi > [ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rootfstype=ext4 ro > rootwait console=ttymxc0,115200 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 > cma=64 console=tty1 ahci_imx.hotplug=1 I used a much simpler commandline: [ 0.000000] Kernel command line: root=/dev/mmcblk0p1 console=ttymxc0,115200 So rather than focing a resolution, color depth, etc. I left it to autodetect them. In general, I wouldn't recommend forcing settings unless the defaults don't work for you. live well, vagrant
Attachment:
signature.asc
Description: Digital signature