Display black after update [SOLVED!]

Using Zynthian
1

I just updated a few minutes ago, and now the Zynthian display won’t start. Oddly, I can still get sound out from my most recent layer, but it looks like startx is just failing.

-- Logs begin at Thu 2019-02-14 10:11:58 GMT. --
Aug 17 06:38:34 zynthian startx[582]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 17 06:38:34 zynthian startx[582]: (==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 17 06:38:34 2020
Aug 17 06:38:34 zynthian startx[582]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Aug 17 06:38:34 zynthian startx[582]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Aug 17 06:38:36 zynthian startx[582]: ./zynthian.sh: line 55: /sys/class/backlight/*/bl_power: No such file or directory
Aug 17 06:38:39 zynthian startx[582]: libjackpeak registering as 'jackpeak'.
Aug 17 06:38:39 zynthian startx[582]: libjackpeak created input ports
Aug 17 06:38:40 zynthian startx[582]: ERROR:zynthian_engine_mixer.get_controllers_dict: Can't configure headphones volume control: Headphones volume control not found!
Aug 17 06:38:40 zynthian startx[582]: ERROR:zynthian_engine_mixer._send_controller_value: 'NoneType' object has no attribute 'items'
Aug 17 06:38:41 zynthian startx[582]: ERROR: PatternManager failed to open file for load /zynthian/zynthian-my-data/sequences/patterns.zynseq

Because of the headphones mention, I thought it might have something to do with the fact that I left the “Headphones” checkbox on in Admin before this recent reboot, so I went into zynthian_envars.sh and turned it back to 0, but after another reboot, I’m still getting no display, and seeing this:

-- Logs begin at Mon 2020-08-17 06:50:21 BST. --
Aug 17 06:50:24 zynthian startx[577]: (++) from command line, (!!) notice, (II) informational,
Aug 17 06:50:24 zynthian startx[577]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 17 06:50:24 zynthian startx[577]: (==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 17 06:50:24 2020
Aug 17 06:50:24 zynthian startx[577]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Aug 17 06:50:24 zynthian startx[577]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Aug 17 06:50:26 zynthian startx[577]: ./zynthian.sh: line 55: /sys/class/backlight/*/bl_power: No such file or directory
Aug 17 06:50:29 zynthian startx[577]: libjackpeak registering as 'jackpeak'.
Aug 17 06:50:29 zynthian startx[577]: libjackpeak created input ports
Aug 17 06:50:30 zynthian startx[577]: ERROR:zynthian_engine_mixer._send_controller_value: 'NoneType' object has no attribute 'items'
Aug 17 06:50:31 zynthian startx[577]: ERROR: PatternManager failed to open file for load /zynthian/zynthian-my-data/sequences/patterns.zynseq

Edit: Looking through things, it looks like maybe just the new buster doesn’t have the backlight power interface we’re looking for?

root@zynthian:~# find /sys/class -iname '*backlight*'

Edit 2: Here’s my fbtft-related modules loaded.

root@zynthian:~# grep -i fb /proc/modules 
fb_ili9486 16384 1 - Live 0xbf23d000 (C)
fbtft 36864 1 fb_ili9486, Live 0xbf22e000 (C)
syscopyarea 16384 1 fbtft, Live 0xbf21f000
sysfillrect 16384 1 fbtft, Live 0xbf1a8000
sysimgblt 16384 1 fbtft, Live 0xbf1a3000
fb_sys_fops 16384 1 fbtft, Live 0xbf126000
2

Fixed with rpi-update per Time for the Buster RC-3 SD image.

3

The question is … why your kernel was upgraded on the update?
Did you run an “apt-get upgrade” by hand?

Automatic upgrades should be disabled … i will check …

Regards,

4

I did. I thought that was all the webconf upgrade button did (since I had to do it already to restore my missing vcgencmd) so I did it manually bc i was already SSHed in. I discovered that wasn’t the case afterwards.

5

The zynthian update script:

/zynthian/zynthian-sys/scripts/update_zynthian.sh

can be called in 3 ways:

  • Directly from command line:

    update_zynthian.sh

  • From webconf:

    software->update

  • From UI’s Admin menu:

    Update Software

Currently, this script doesn’t call “apt-get upgrade”. In the past it did, but it was quite problematic and now it’s avoided.

Kind Regards!

1 Like