Display resolution messed up when switching to console

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Display resolution messed up when switching to console

981 Views
hiromiyokoo
Contributor II

Hello,

I'm using a board with an iMX6DL with a yocto poky qt-in-use-image distro.

I'm not launching the default application, instead I'm using a qt example this way:

export DISPLAY=:0

cd ~/declarative/animation/basics/color-animation

Xorg &

./color-animation

It works like a charm, but when I try to switch to a console with <ctrl><alt><f1> and then go back to X with <ctrl><alt><f2> (or <f3> sometimes), the image on the LVDS display is all messed up. It's composed of black and white lines (no colour signals). The application is still responding (I can see in some way the image, messed up) and I can move the mouse pointer.

The same issue happens when I try to suspend with:

echo mem > /sys/power/state

or

echo standby > /sys/power/state

and then resume with the power button. The image becomes a mess.

If I kill Xorg and the qt example, and launch them again, I get a perfect image again.

In the log /var/volatile/log/Xorg.0.log the weird outputs are:

[2673309.221] (**) Option "config_info" "udev:/sys/devices/soc0/soc.1/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/input/input2/event2"

[2673309.221] (II) XINPUT: Adding extended input device "Lite-On Technology Corp. HP Basic USB Keyboard" (type: KEYBOARD, id 8)

[2673309.221] (**) Option "xkb_rules" "evdev"

[2673309.221] (**) Option "xkb_model" "pc104"

[2673309.221] (**) Option "xkb_layout" "us"

[2673392.361] setversion 1.4 failed

[2673744.380] (II) evdev: Lite-On Technology Corp. HP Basic USB Keyboard: Close

[2673744.380] (II) UnloadModule: "evdev"

[2673744.381] (II) evdev: USB Optical Mouse: Close

[2673744.381] (II) UnloadModule: "evdev"

[2673744.381] (II) evdev: 20b8000.kpp: Close

and:

[2673308.891] drmOpenDevice: node name is /dev/dri/card0

[2673308.891] drmOpenDevice: open result is 13, (OK)

[2673308.891] drmOpenByBusid: drmOpenMinor returns 13

[2673308.891] drmOpenByBusid: Interface 1.4 failed, trying 1.1

[2673308.891] drmOpenByBusid: drmGetBusid reports platform:Vivante GCCore:00

[2673308.894] (EE) AIGLX error: vivante exports no extensions (/usr/lib/dri/vivante_dri.so: undefined symbol: __driDriverExtensions)

[2673308.894] (EE) AIGLX: reverting to software rendering

[2673308.917] (II) AIGLX: Loaded and initialized swrast

[2673308.918] (II) GLX: Initialized DRISWRAST GL provider for screen 0

[2673308.921] (II) VIVANTE(0): Setting screen physical size to 211 x 127

[2673309.082] (II) config/udev: Adding drm device (/dev/dri/card0)

[2673309.084] (II) config/udev: Adding input device 20b8000.kpp (/dev/input/event0)

[2673309.084] (**) 20b8000.kpp: Applying InputClass "evdev keyboard catchall"

[2673309.084] (II) LoadModule: "evdev"

[2673309.084] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so

Labels (3)
0 Kudos
Reply
3 Replies

766 Views
b36401
NXP Employee
NXP Employee

Please try to send SIGUSR1 to X server for it to re-init the display.

Have a great day,

Victor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

766 Views
hiromiyokoo
Contributor II

Thank you for your help, I tried to put my application into the startx script and now it works perfectly.

0 Kudos
Reply

766 Views
hiromiyokoo
Contributor II

Is there anybody out there who knows what I should do to fix this behaviour?

0 Kudos
Reply