And also check if you lcd is loaded and enabled. # adb shell cat /sys/devices/omapdss/display0/enabled
connect ddms or screen cast and check if you have any compositions happening in the frame buffer. - Preetam On Thu, Feb 9, 2012 at 11:01 PM, Zoltan Kuscsik <[email protected]> wrote: > Check the framebuffer resolution in: > > # adb shell cat /sys/class/graphics/fb0/virtual_size > > Is your LCD display able to work with this resolution, did you tried > to swap the HDMI-/DVI connector? > > Here you can check if the display is set to the right resolution/timing: > > # adb shell cat /sys/devices/omapdss/display0/timings > > > Zoli > > On Thu, Feb 9, 2012 at 1:03 PM, carchangel <[email protected]>wrote: > >> hello everyone >> >> I am using the Blaze board to run Android 4.0 system which have >> the >> Linux kernel 3.0.8. >> >> the u-boot ,x-loader and kernel is downloaded and built by the >> [L27.IS.2.P2 OMAP4 Icecream Sandwich Release Notes] which is recorded >> in >> http://omappedia.org/wiki/L27.IS.2.P2_OMAP4_Icecream_Sandwich_Release_Notes >> . >> >> Now the kernel can start normally ,but the LCD scree only flashed once >> at kernel starting. after starting ,the kernel always black.the strange >> log is >> >> 6.706115] cannot apply mgr(lcd) on inactive device >> [ 6.711791] omapfb omapfb: failed to apply dispc config >> [ 6.720703] cannot apply mgr(tv) on inactive device >> [ 6.726257] omapfb omapfb: failed to apply dispc config >> [ 6.735015] cannot apply mgr(lcd2) on inactive device >> [ 6.740692] omapfb omapfb: failed to apply dispc config >> anybody can give me some advise? >> thanks >> zhong yifeng >> >> -- >> unsubscribe: [email protected] >> website: http://groups.google.com/group/android-kernel > > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel > -- "The great pleasure in life is doing what people say you cannot do" -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
