Jack477 / CommanderPi

Easy RaspberryPi4 GUI system managment
MIT License
188 stars 33 forks source link

Latest version on berryboot causing error #27

Closed markybill closed 3 years ago

markybill commented 3 years ago

Upgraded to the latest version now get the following trace back running from terminal Traceback (most recent call last): File "/home/pi/CommanderPi/src/main.py", line 9, in import gui as g File "/home/pi/CommanderPi/src/gui.py", line 5, in import bootloader as btl File "/home/pi/CommanderPi/src/bootloader.py", line 21, in ad = get_actual_version() File "/home/pi/CommanderPi/src/bootloader.py", line 12, in get_actual_version month = MONTHS[x_version_split[0]] KeyError: 'unknown'

It would appear that vcgencmd bootloader_version is returning unknown, changed to vcgencmd version and all works ok.

I am using latest raspberry os but booting from berryboot.

Jack477 commented 3 years ago

What do you see after type vcgencmd bootloader_version in terminal?

markybill commented 3 years ago

This is what I get for the two commands

pi@raspberrypi:~ $ vcgencmd bootloader_version unknown pi@raspberrypi:~ $ vcgencmd version Aug 19 2020 17:41:31 Copyright (c) 2012 Broadcom version e90cba19a98a0d1f2ef086b9cafcbca00778f094 (clean) (release) (start_x) pi@raspberrypi:~ $

Hope that helps

Jack477 commented 3 years ago

Hmm it's strange, I depends all on official doc https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md
vcgencmd version "Displays the build date and version of the firmware on the VideoCore." so it's not bootloader version? (source https://www.raspberrypi.org/documentation/raspbian/applications/vcgencmd.md)

I think you should try update eeprom
sudo apt update
sudo apt full-upgrade
sudo reboot

markybill commented 3 years ago

I read the documentation for the booteeprom and realized I forgot to mention that I am running the Commander on a Pi 3 model B+ and not a Pi 4, I guess this could be the issue. It works fine otherwise on the Pi3 and I find the info displayed useful.

Jack477 commented 3 years ago

Yes it could be issue. After 1.0 release I will do some work for compatibility with PI 3. Now all is designed for PI 4.