12-23-2019, 03:07 PM
(12-23-2019, 02:48 PM)TheOldPresbyope Wrote: @weaverMany thanks Kent, will give it a go later.
Reading the last few entries in https://github.com/raspberrypi/linux/issues/3331, running "sudo SKIP_KERNEL=1 rpi-update" will NOT update the kernel but WILL update the start*.elf and fixup*.dat files. According to the poster popcornmix this is all you need, and poster BigMuscle85 confirmed it worked.
So, why not try it? At worst, you'll just have to burn a new image if things go wrong.
Here's the output on one of my moOde 6.4.0 players
Code:pi@moode3a:~ $ sudo SKIP_KERNEL=1 rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
#############################################################
WARNING: 'rpi-update' updates to pre-releases of the linux
kernel tree and Videocore firmware.
'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer.
DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)
*** Downloading specific firmware revision (this will take a few minutes)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 168 0 168 0 0 1282 0 --:--:-- --:--:-- --:--:-- 1282
100 115M 100 115M 0 0 3959k 0 0:00:29 0:00:29 --:--:-- 5681k
*** Updating firmware
*** As requested, not updating kernel
*** As requested, not updating kernel modules
*** Updating VideoCore libraries
*** Using HardFP libraries
*** Updating SDK
*** Running ldconfig
*** Storing current firmware revision
*** Deleting downloaded files
*** Syncing changes to disk
*** If no errors appeared, your firmware was successfully updated to 57d3b3ac6e893c8545b830a866091cdf8daf4961
*** A reboot is needed to activate the new firmware
and upon reboot, the kernel remains
Code:Kernel 4.19.83-v7+ #1277, Raspbian 10.2, moOde 6.4.0 2019-11-24
I don't have an local display to press into use ATM but I tried setting framebuffer_depth=32 in config.txt and rebooting. Result:
Code:pi@moode3a:~ $ vcgencmd get_config framebuffer_depth
framebuffer_depth=32
Looks good from here.
Regards,
Kent