Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: bmarkus on October 30, 2021, 07:21:16 AM
-
I ordered a Raspberry Pi Zero 2 W, it will arrive next week. Let's see what to do with it :)
-
Still waiting for my board too. For $15, a nice little piece of hardware.
For the config.txt, it follows the [PI02] directive. But for all intents and purposes, a pi3 to the kernel. The wifi needs different firmware BRCM43436 .....which I'll update shortly. The interesting thing with that, the new firmware was added to the rpi packaging 13 months ago. At some point in the future, the board will get a different wifi chip that will use BRCM43436s.
According to RPi, the latest RPiOS images work with this board, those images are 5.10.17 kernels. So things might be promising the current piCore release.
-
Latest piCore 13.0.x ccomes with 5.10.16 kernel. It is 8 months old, I will release 13.1.0 with an up to date kernel.
-
Could you have a look at this:
$ dmesg | grep cert
[ 3.498402] Loading compiled-in X.509 certificates
[ 403.494066] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 403.558074] [<805e3eb0>] (x509_check_for_self_signed) from [<805e32b4>] (x509_cert_parse+0x16c/0x1c8)
[ 403.558090] [<805e3148>] (x509_cert_parse) from [<805e3bf0>] (x509_key_preparse+0x20/0x1a0)
[ 403.559333] cfg80211: Problem loading in-kernel X.509 certificate (-22)
..something connected with compiling natively and missing a cert/crypto module?
-
Zero 2 W arrived, will check it in the next days.
-
Yes bmarkus,
........the community's are reporting slightly better performance from the "Pi zero 2 W" with overclock.........than a "pi 3+".......
https://www.youtube.com/watch?v=5RB29g18m-I
Also people may not know about the free "Debian build" of a tool called "Puffin browser." which will run in Rasbian and other Linux's builds (likely even picore) for these boards.
Puffin works perfect on these boards..........it gives excellent web performance with as many as 8 HEAVY web tabs open in a single browser session.
Such tabs as Facebook, Ebay etc......... and also fluid 1080p video from "youtube" in the web browser......... on a 1.4ghz overclock board.
(it leaves Chromium standing......even when Chromium is ran on some regular Laptop)
People need to also remember that many applications can be run in a web browser
from the cloud. Making these small computers extremely useful. "Audiotool"
There are tons of free advanced web apps that run in the browser.... ready to go.........
........these tiny computers have very good software ecosystems
out there.
https://mxlinux.org/blog/mx-fluxbox-raspberry-pi-ragout-now-final/
There are full custom Android 10's for the Pi's .......ready to go
https://konstakang.com/devices/rpi3/
Then such things as "Cameyo" free droid app can give you limitless ways to run any Msoft apps you choose.... from your Pi. (in the cloud)
.....And you can also run the free "AURORA" droid app...... a "play store clone"....... for thousands of free droid apps to your Pi......
There are many free custom 64 bit Linux builds for these boards. @https://mxlinux.org/blog/mx-fluxbox-raspberry-pi-ragout-now-final/
The portability and replacement costs means the board could be a desirable PC platform .........sporting almost zero power consumption, and negligible buying cost..... for a desktop PC.
........i am finding some commercial high end music apps that are built for "Pi's"
such as "Reaper" and "Waveform FREE" .......giving excellent performance on an overclocked board.
https://www.tracktion.com/products/waveform-free
These DAW's can also easily take many free ARM vst's .....that's "VST & VSTi plug ins" compiled for ARM...... as chains.........
( there are many free ARM plug ins already existing [VST's]......... (compiled for Arm).....)
(professional level)
A "pro production suite" can be achieved on a shoe string with this board
Training academy's could be built etc......
......there are also commercial graphics tools compiled for "Pi's"....
i mean as a general purpose all round computer it works.......... it can work real good via "browser web apps" from your DSL........
it can also be used as a professional platform for productivity. ( Titles exist for it)
There are also free custom "Blue Ray player media centers" for it.........so it doubles up it's usage as a home media centers
https://osmc.tv
........it saves people the need to buy home satellite boxes and expensive smart TV's
why bother with all the above. I think it's the "replace-ability" of these tiny computers and convenience.......(almost throw away in nature......yet useful)
i mean many forum members use the boards for embedded projects, but it's many other things too.......(just flicking in & out microSD cards)
V
-
Hi bmarkus,
Got mine too a few days ago and (as you will soon find out) confirm that current 13.0.3 won't boot (stuck at rainbow screen).
Waiting for the update....
Thanks !
-
Did Somebody when Raspberry Pi Zero 2 W can work with Tiny Core Linux?
-
Did Somebody when Raspberry Pi Zero 2 W can work with Tiny Core Linux?
Yes, piCore 13.1.0 works fine
-
Will boot past the rainbow screen on my RPi02W, but wifi.sh -a reports "No wifi devices found!"
-
Will boot past the rainbow screen on my RPi02W, but wifi.sh -a reports "No wifi devices found!"
The same SD in a Pi Zero W will start wifi. I am running the 13.1 core with firmware-rpi-wifi.tcz and wireless-5.10.77-piCore.tcz. In onboot.lst, I have openssh, firmware-rpi-wifi, wifi, then compiletc, nano, and bash-dev. Saw a recommendation about firmware-brcmwifi.tcz in another post, but that was a rabbit hole. I am trying to use the onboard WiFi.
This is how I pulled wifi related files from tinycorelinux.net :
for pkg in ca-certificates libiw libnl ncurses openssl readline wifi wireless-5.10.77-piCore wireless_tools wpa_supplicant firmware-rpi-wifi; do for f in $pkg.tcz{,.dep,.info,.list,.md5.txt,.tree,.zsync}; do wget http://ftp.nluug.nl/os/Linux/distr/tinycorelinux/13.x/armv6/tcz/$f; done; doneI loaded those files to /mnt/mmcblk0p2/tce/optional and the packages seem to be loading, but still wifi.sh reports no devices. I don't see any cfg80211 related messages in dmesg, but I'm not sure what I should be looking for there in terms of failures to find hardware, but this seems to indicate that there is a different device ID between the two different WiFi chips so maybe it's a clue : https://github.com/raspberrypi/linux/commit/c52581ffa49b9c0e5de3349436c283fe20128073#diff-ffce630590e253b5f402e964a1085c5709e56a2ba5e060579fe68cfd87988fe7
-
I’ve seen some posts saying rpi was going To use different WiFi chips on these boards. Needed different firmware. Can you post the output of dmesg…. Just the last part where the WiFi stuff is loading.
-
Can you post the output of dmesg…. Just the last part where the WiFi stuff is loading.
I loosely compared the output of dmesg with the RPiZW to the output with the same SD on the RPiZ2W and it seems like the main differences are after the line random: crng init done
The RPiZW has this :
[ 32.039699] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 32.472500] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 32.472778] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 32.472802] cfg80211: failed to load regulatory.db
[ 32.636609] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 32.673373] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 32.678598] usbcore: registered new interface driver brcmfmac
[ 32.999646] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 32.999839] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 32.999974] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 33.001139] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[ 33.610445] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
where the RPiZ2W has nothing. Is the wireless hardware presented as a USB device? Maybe I need to install usbutils and do a lsusb?
-
Wait - I stripped the timestamps to do a dmesg compare side by side, and I didn't even realize the RPIZ2W has an ARMV7 processor where the RPIZW has an ARMv6 - do I need to be using the packages from armv7?
-
Yes. The Zero 2 W is a quad core armv7 processor.
-
Thanks for clearing this up. Finally got it to work by using the armv7 packages and specifically the wireless-5.10.77-piCore-v7.tcz package.
I used this to pull the WiFi packages instead of what I had above :
for pkg in ca-certificates libiw libnl ncurses openssl readline wifi wireless-5.10.77-piCore-v7 wireless_tools wpa_supplicant firmware-rpi-wifi; do for f in $pkg.tcz{,.dep,.info,.list,.md5.txt,.tree,.zsync}; do wget http://ftp.nluug.nl/os/Linux/distr/tinycorelinux/13.x/armv7/tcz/$f; done; done
Then, in /mnt/mmcblk0p2/tce/onboot.lst, add the line
wireless-5.10.77-piCore-v7.tcz
just before the line that was there for firmware-rpi-wifi.tcz
-
the firmware should be first in onboot.lst........before the kernel drivers extension.
-
This is what I have in onboot.lst and it is auto connecting on boot and I'm able to SSH into it with wifi.sh -a in /opt/bootlocal.sh :
openssh.tcz
wireless-5.10.77-piCore-v7.tcz
firmware-rpi-wifi.tcz
wifi.tcz
compiletc.tcz
nano.tcz
bash-dev.tcz
-
Generally speaking, is there a way to include packages for the RPiZW and the RPiZ2W in the filesystem and take two different paths to installing them depending on the processor it's running on?
-
Hi vandiwa
Please listen to Paul_123, he knows what he's talking about. Place firmware-rpi-wifi.tcz at the beginning of onboot.lst.
Your current list creates a potential race condition where the firmware may not be detected and loaded in time.
-
Generally speaking, is there a way to include packages for the RPiZW and the RPiZ2W in the filesystem and take two different paths to installing them depending on the processor it's running on?
Been discussed many times. The default images are kept very small on purpose. We provide toolkits to build a highly customizable small footprint system.
-
Hi vandiwa
Generally speaking, is there a way to ...
Generally speaking, all non kernel related extensions are compiled to be backwards compatible with ARMv6, though
there may be a few exceptions. So the nano.tcz you find in the ARMv7 repo is identical to the one in the ARMv6 repo.
For kernel related extensions, they have unique names, wireless-5.10.77-piCore-v7.tcz vs wireless-5.10.77-piCore.tcz.
You can have both in your tce/optional/ directory. If you list it like this in your onboot.lst:
wireless-KERNEL.tczthen the correct version will be loaded depending on the processor that is being booted.
-
Thanks Rich, and I can confirm that the same image I have booting and starting WiFi on the ARMv7 now will also boot and start WiFi on the ARMv6, and that was a pleasant surprise.
-
As you build your system, keep in mind, tce-ab will only download from the repository the correct kernel version of a (kernel dependant) extension.
-
Wait - I stripped the timestamps to do a dmesg compare side by side, and I didn't even realize the RPIZ2W has an ARMV7 processor where the RPIZW has an ARMv6 - do I need to be using the packages from armv7?
32-bit TCZ packages, except kernel modules are built for arm v6 architecture, you can use them on v7 and v7l.
-
Is there a way to install wireguard?
I installed many packages but I cant even do make!!
-
Load the compiletc extension