Tiny Core Base > Raspberry Pi

Raspberry Pi Zero 2 W

<< < (4/6) > >>

vandiwa:
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 :

--- Code: ---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

--- End code ---
Then, in /mnt/mmcblk0p2/tce/onboot.lst, add the line

--- Code: ---wireless-5.10.77-piCore-v7.tcz

--- End code ---
just before the line that was there for firmware-rpi-wifi.tcz

Paul_123:
the firmware should be first in onboot.lst........before the kernel drivers extension.

vandiwa:
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 :

--- Code: ---openssh.tcz
wireless-5.10.77-piCore-v7.tcz
firmware-rpi-wifi.tcz
wifi.tcz
compiletc.tcz
nano.tcz
bash-dev.tcz

--- End code ---

vandiwa:
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?

Rich:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page