Tiny Core Base > piCore Final Releases
piCore 15.0 Release
Synerworks:
Will do. I only used the 'temp.tcz' dependency to illustrate a use case, so if the 'rpi-vc.tcz' extension is obsoleted, the repo dependency should switch over to 'raspi-utils.tcz' instead. Nonetheless, the issue manifests itself when attempting to use the VC tools and the incorrect repo is loaded or both and then throws the exception. Also, the superseded objects could be copied from the working 'raspi-utils.tcz' repo into the obsoleted extension to avoid this inconsistency when using the required component but picking the wrong 'provides.sh' result. Just attempting to avoid caveats as they come up.
rhbvkleef:
Are there any plans for updating node.tcz in the future? By now I really have to jump through hoops to get JS and TS applications to work.
Juanito:
In armhf or aarch64?
The node.js extensions (as opposed to the node extensions) seem quite recent?
DrRob:
--- Quote from: Paul_123 on October 29, 2024, 01:42:24 PM ---Known Issues:
- Internal Wifi on some Raspi chipsets, there is a driver problem with wpa_supplicant 2.11 (Add brcmfmac.feature_disable=0x82000 to cmdline.txt on the boot drive)
--- End quote ---
Which Raspi chipsets please? Or better still, which Pi models? By trial and error it seems to include the Pi Zero?
Paul_123:
I don’t have every combination to test. It may just be the zero based product. They all use the same driver. Just different firmware.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version