Skip to content
Snippets Groups Projects
New look: Off

HTC Vision / Desire Z / G2: blank screen after PM boot logo

    • Closed Imported Issue created by Administrator @root

    I can connect via SSH. The display works when booting, PMOS logo is displayed. Then the screen is blank. No combination of touch and keys seems to wake it up.

    Now the interesting part: when I'm executing /etc/init.d/lightdm restart, I can see the login screen for about 2 seconds. That's on Hildon. On Matchbox, the screen briefly flashes when I kill the x server.

    The log doesn't look very useful.

    Mar 10 11:59:40 htc-vision user.notice gdr:x11: X.Org X Server 1.20.4
Mar 10 11:59:40 htc-vision user.notice gdr:x11: X Protocol Version 11, Revision 0
Mar 10 11:59:40 htc-vision user.notice gdr:x11: Build Operating System: Linux 4.14.78-1-vanilla armv8l Alpine Linux
Mar 10 11:59:40 htc-vision user.notice gdr:x11: Current Operating System: Linux htc-vision 3.0.101-cyanogenmod #2-postmarketOS PREEMPT Thu Feb 28 09:27:15 UTC 2019 armv7l
Mar 10 11:59:40 htc-vision user.notice gdr:x11: Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true  androidboot.baseband=26.03.02.2
Mar 10 11:59:40 htc-vision user.notice gdr:x11: Build Date: 07 March 2019  09:48:38PM
Mar 10 11:59:40 htc-vision user.notice gdr:x11:  
Mar 10 11:59:40 htc-vision user.notice gdr:x11: Current version of pixman: 0.38.4
Mar 10 11:59:40 htc-vision user.notice gdr:x11:         Before reporting problems, check http://wiki.x.org
Mar 10 11:59:40 htc-vision user.notice gdr:x11:         to make sure that you have the latest version.
Mar 10 11:59:40 htc-vision user.notice gdr:x11: Markers: (--) probed, (**) from config file, (==) default setting,
Mar 10 11:59:40 htc-vision user.notice gdr:x11:         (++) from command line, (!!) notice, (II) informational,
Mar 10 11:59:40 htc-vision user.notice gdr:x11:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Mar 10 11:59:40 htc-vision user.notice gdr:x11: (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 10 11:59:40 2019
Mar 10 11:59:40 htc-vision user.notice gdr:x11: (==) Using config directory: "/etc/X11/xorg.conf.d"
Mar 10 11:59:40 htc-vision user.notice gdr:x11: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Mar 10 11:59:41 htc-vision user.notice gdr:x11: The XKEYBOARD keymap compiler (xkbcomp) reports:
Mar 10 11:59:41 htc-vision user.notice gdr:x11: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Mar 10 11:59:41 htc-vision user.notice gdr:x11: >                   X11 cannot support keycodes above 255.
Mar 10 11:59:41 htc-vision user.notice gdr:x11: >                   This warning only shows for the first high keycode.
Mar 10 11:59:41 htc-vision user.notice gdr:x11: > Internal error:   Could not resolve keysym XF86MonBrightnessCycle
Mar 10 11:59:41 htc-vision user.notice gdr:x11: Errors from xkbcomp are not fatal to the X server
Mar 10 11:59:42 htc-vision user.notice gdr:x11: initializing gtk
Mar 10 11:59:42 htc-vision user.notice gdr:x11: 
Mar 10 11:59:42 htc-vision user.notice gdr:x11: (matchbox-desktop:2444): GLib-GObject-CRITICAL **: 11:59:42.835: g_type_class_add_private: assertion 'private_size > 0' failed
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Administrator
      Administrator @root · Imported
      Author Owner

      cat /dev/urandom >/dev/fb0 does nothing to the screen.

      htc-vision:/home/gdr# echo 1 > /sys/class/graphics/fb0/blank
htc-vision:/home/gdr# echo 0 > /sys/class/graphics/fb0/blank
ash: write error: Invalid argument

      WTF, can't disable blanking but can enable? The echo 0 command above triggers some seemingly related kernel messages:

      [ 2750.410827] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 2750.410888] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 2750.418090] lcdc_on: Can't set MDP LCDC pixel clock to rate 25000000

      By GDR! on 2019-05-01T14:48:21

    • Administrator
      Administrator @root · Imported
      Author Owner

      Log from the short time when startx makes the screen go on:

      [ 4274.612823] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 4274.612854] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 4274.665618] panel_power: Panel power ON=0
[ 4274.665679] sonywvga_panel_unblank
[ 4274.665710] lcdc_config_gpios: power goes to 1
[ 4274.711791] panel_power: Panel power ON=0
[ 4274.740875] wl_iw_iscan_set_scan: Scan from SIOCGIWSCAN not supported
[ 4274.948242] sonywvga_panel_unblank: will send unblank
[ 4274.948608] sonywvga_panel_unblank: good!
[ 4275.078155] sonywvga_panel_blank
[ 4275.128906] lcdc_config_gpios: power goes to 0
[ 4275.274536] panel_power: Panel power OFF=0
[ 4275.423583] panel_power: Panel power OFF=0
[ 4275.425689] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 4275.425720] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 4275.431732] lcdc_on: Can't set MDP LCDC pixel clock to rate 25000000
[ 4275.748321] wl_iw_iscan_set_scan: Scan from SIOCGIWSCAN not supported
[ 4276.047821] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 4276.047821] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 4276.052276] lcdc_on: Can't set MDP LCDC pixel clock to rate 25000000
[ 4276.756072] wl_iw_iscan_set_scan: Scan from SIOCGIWSCAN not supported
[ 4277.763946] wl_iw_iscan_set_scan: Scan from SIOCGIWSCAN not supported
[ 4277.790557] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 4277.790588] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 4277.839233] panel_power: Panel power ON=0
[ 4277.839263] sonywvga_panel_unblank
[ 4277.839263] lcdc_config_gpios: power goes to 1
[ 4277.885711] panel_power: Panel power ON=0
[ 4278.118255] sonywvga_panel_unblank: will send unblank
[ 4278.118621] sonywvga_panel_unblank: good!
[ 4278.208282] sonywvga_panel_blank
[ 4278.258239] lcdc_config_gpios: power goes to 0
[ 4278.403869] panel_power: Panel power OFF=0
[ 4278.552734] panel_power: Panel power OFF=0
[ 4278.554870] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 4278.554901] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 4278.561004] lcdc_on: Can't set MDP LCDC pixel clock to rate 25000000
[ 4278.771087] wl_iw_iscan_set_scan: Scan from SIOCGIWSCAN not supported
[ 4279.778747] wl_iw_iscan_set_scan: Scan from SIOCGIWSCAN not supported

      The 400ms between "unblank" and "blank" again looks kind of similar to what I saw with my eyes. About half a second flash.

      By GDR! on 2019-05-01T15:16:16

      Edited by Administrator
    • Administrator
      Administrator @root · Imported
      Author Owner 
      htc-vision:/sys/devices/virtual/graphics/fb0/power# /etc/init.d/msm-fb-refresher restart
 * WARNING: you are stopping a boot service
 * Stopping msm-fb-refresher ...
 * start-stop-daemon: no matching processes found                                                                       [ ok ]
 * Starting msm-fb-refresher ...
 * start-stop-daemon: /usr/sbin/msm-fb-refresher is already running                                                     [ !! ]
 * ERROR: msm-fb-refresher failed to start

      (after killing msm-fb-refresher, trying to run it one-shot)

      htc-vision:/sys/devices/virtual/graphics/fb0/power# ps aux | grep msm-fb
 2672 root      0:00 grep msm-fb
htc-vision:/sys/devices/virtual/graphics/fb0/power# /usr/sbin/msm-fb-refresher 
Failed FBIOPAN_DISPLAY: Operation not permitted

      By GDR! on 2019-05-01T15:51:34

    • Administrator
      Administrator @root · Imported
      Author Owner 
      htc-vision:/sys/devices/virtual/graphics/fb0/power# fbdebug -d /dev/fb0 -m 0
Unable to set fb mode: Invalid argument
htc-vision:/sys/devices/virtual/graphics/fb0/power# fbdebug -d /dev/fb0 -p
Unable to pan the display: Operation not permitted

      and in log

      [ 1182.232727] mdp4_csc_config: Block type 10 isn't supported by CSC.
[ 1182.232788] mdp4_csc_config: Block type 8 isn't supported by CSC.
[ 1182.239044] lcdc_on: Can't set MDP LCDC pixel clock to rate 25000000

      okay, this is way over my head, i tried reading kernel sources but didn't get anything from it.

      By GDR! on 2019-05-01T15:59:51

    • Administrator
      Administrator @root · Imported
      Author Owner

      Just an update: Weston works, it's certainly something with X that's causing the issue. Too bad that Weston isn't usable.

      By GDR! on 2019-05-02T13:19:11

    • Administrator
      Administrator @root · Imported
      Author Owner

      To continue this series of blog posts, I've built fbterm for musl libc, apart from the super flaky keyboard input it works. Patches here https://github.com/gjedeer/fbterm

      Help on making X run still welcome.

      By GDR! on 2019-05-02T16:53:19

    • Administrator
      Administrator @root · Imported
      Author Owner

      @gjedeer About all the Operation not permitted errors with msm-fb-refresher and fbdebug, have you tried also with sudo?

      I also had a device some time ago with weston working but not X, what I remember is that when X starts it seems to do blank and unblank, and this causes the framebuffer to break.

      The problem is not related to the X server but to the framebuffer driver in the kernel. And if I remember correctly my first attempt to verify that, was patching the driver to do nothing when blank ioctl is called. Maybe you can try it too.

      PS: Congrats with fbterm ;)

      By Daniele Debernardi on 2019-05-02T17:28:32

      Edited by Administrator
    • Administrator
      Administrator @root · Imported
      Author Owner

      @drebrez thank you for the answer. Yes, I've done everything as root.

      I guess you don't happen to remember which ioctl that was? I had a hard time finding it in strace.

      By GDR! on 2019-05-02T21:14:27

    • Administrator
      Administrator @root · Imported
      Author Owner

      https://gitlab.postmarketos.org/postmarketos/pmaports/blob/master/main/fbdebug/fbdebug.c#L277

      But in the framebuffer driver I don't remember where it is exactly, and it's probably different in every downstream framebuffer driver...

      By Daniele Debernardi on 2019-05-03T00:03:03

    • Administrator
      Administrator @root · Imported
      Author Owner

      @drebrez sorry if it's a silly question but I don't know how to build anything custom and run it in PMOS. Say i want to build a kernel like you did - when I enter android_kernel_htc_vision and do make, it says that a config is missing.

      I guess I could go through make menuconfig, but this doesn't feel like the right way. What would be the PMOS-friendly way to do change a line or two and rebuild the kernel?

      By GDR! on 2019-05-06T17:58:53

    • Administrator
      Administrator @root · Imported
      Author Owner

      ...okay, on yet another search I've found https://wiki.postmarketos.org/wiki/Porting_to_a_new_device#Kernel_package

      By GDR! on 2019-05-06T18:15:43

    • Administrator
      Administrator @root · Imported
      Author Owner

      If you know what you want to change, you can create a patch like this and add it to the pmaport:

      https://wiki.postmarketos.org/wiki/Patching#Legacy_Guide

      For kernels specifically, there is:

      https://wiki.postmarketos.org/wiki/Compiling_kernels_with_envkernel.sh

      And we also have pmbootstrap build --src=/path/to/different/kernel/source linux-htc-vision (also mentioned in the first wiki link)

      If you get stuck with building packages, a good place to ask is the IRC/matrix chat, good luck!

      By Oliver Smith on 2019-05-06T22:22:36

    • Administrator moved from pmbootstrap#1770 (closed) · Imported

      moved from pmbootstrap#1770 (closed)

      By Daniele Debernardi on 2020-01-05T02:03:26

    • Administrator closed · Imported

      closed

    Please register or sign in to reply