Decided to play today; rpi 4b (4gb)
Downloaded and burned the image, powered the pi on and opened the m2p
web gui. Ignored the update available and went straight to install
Squeezebox server.
When the install completed I opened a Terminal:
This was the result of uname -a
Code:
--------------------
Linux max2play 4.19.50-v7l+ #895 SMP Thu Jun 20 16:03:42 BST 2019 armv7l
GNU/Linux
--------------------
I then ran sudo apt update
Code:
--------------------
218 packages can be upgraded. Run 'apt list --upgradable' to see them.
--------------------
and then sudo apt full-upgrade -y
after the update I rebooted from the web gui.
The pi did not come back up, I pulled the power and restarted , no
result.
I swapped sd card with a fresh image and this time applied the m2p
update before installing Squeezebox server
Code:
--------------------
Changelog V.2.51 17.10.2019
Jivelite Fullscreen toggle Bugfix
Raspberry Settings Plugin now with 64Bit Kernel switch (from 32 Bit Kernel)
in Max2Play Buster (newest Image)
Fix for Shairtunes2 Plugin in LMS to install SSL Libraries
Added apt update in Update Script for Max2Play-Buster Image to get latest
package resources. Buster moved from testing to stable. This resulted in
missing packages in some installers like Bluetooth.
Fixed Ampache Installer: choose correct PHP libraries and MySQL (now MariaDB)
in Max2Play Buster
Added WiFi Driver installer on WiFi/LAN page of web interface that
automatically installs the missing driver for your WiFi stick (based on script
from fars-robotics.net)
more small Bugfixes and Installer updates (SpotifyConnect, Bluetooth)
--------------------
Uname -a was unchanged
Code:
--------------------
Linux max2play 4.19.50-v7l+ #895 SMP Thu Jun 20 16:03:42 BST 2019 armv7l
GNU/Linux
--------------------
So the 64 bit kernel must only be installed when a a dac is added to the
pi ?
This ia my Rasbian OS
Code:
--------------------
pi@rpi4b:~ $ uname -a
Linux rpi4b 4.19.75-v8+ #1270 SMP PREEMPT Tue Sep 24 18:59:17 BST 2019
aarch64 GNU/Linux
--------------------
I ran update again and the number of packages was again 218.
Rebooted from the web gui and the pi did not boot (green led bwas
blinking 4 times in a regular pattern).
Checked over at the pi forum and found this
https://www.raspberrypi.org/forums/viewtopic.php?p=437084#p437084
> Unlike previous Raspberry PI's the RPI4B boots with the use of code from
> a built in EEPROM, that means it can use more complex boot code with
> more flexibility, and the ability to add new features.
>
> consequently when the new bootcode doesn't detect a valid start.elf file
> on the SD-card it will blink the activity LED, four times with an
> interval between the four blinks, (bootcode.bin is no longer used, and
> is ignored when it exists on the SD-card).
>
> Its very-very unlikely the EEPROM content is corrupted, but to check if
> this the case, unplug everything from the Raspberry Pi 4, including the
> SD card, and then turn the power back on.
> If the green LED blinks with a repeating four blink pattern then the
> bootloader is running correctly, and indicating that start.elf has not
> been found.
>
I popped the faulty card into a pi Raspbian and could not see start.elf
28853
so I would not bother running update for a while yet. It might run
differently though, from the Raspberry Settings tab.:confused::rolleyes:
ronnie
+-------------------------------------------------------------------+
|Filename: slarti m2p2.jpg |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=28853|
+-------------------------------------------------------------------+
------------------------------------------------------------------------
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View this thread: http://forums.slimdevices.com/showthread.php?t=101856
_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
