Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: bmarkus on April 16, 2017, 02:18:59 PM
-
Team Tiny Core is proud to announce immediate availability of the third beta release of the piCore-9.0 edition. Core components updated to latest upstream:
9.0beta3
- kernel 4.9.22
- BusyBox applets reviewed, added lsusb, mkfs.vfat, dropped rpm, etc.
- BusyBox mount replaced with util-linux to speed-up boot
- util-linux 2.29.2
- e2fsprogs 1.43.4
- MicroPython updated to 1.8.7-628
- RPi boot updated to 2017/04/15
Please note, waitusb=1 added to command line for armv6 to get /dev/mmcblk0p2 recognized. Depending on your SD card it may be unnecessary.
9.0beta2
Not released for public
9.0beta1
- kernel 4.9.10
- glibc 2.25
- BusyBox 1.26.2
- util-linux 2.29.1
- e2fsprogs 1.43.3
- GCC 6.3.0
piCore-8.x repo is compatible to 9.x except kernel dependent modules and header file.
Only one SD card image available, it works on all RPi boards. Download location:
http://tinycorelinux.net/9.x/armv7/test_releases/RPi/
Please try it and share your experience, bugs found, etc.
-
The first boot after writing the image with win32diskimager, I got the 4 raspberry's, and then a kernel panic page of errors like these for each of the 4 cpus in my RPI2:
CPU:2 PID:0 Comm: Swapper/2 Tainted G D 4.9.22-picore-v7#1
and so forth for each cpu.
At the very end:
End Kernel Panic - not syncing: Attempted to kill the idle task.
Fortunately, I just power-cycled the RPI again, and boot was a total success with no errors.
Loaded up with my usual assortment of programs, including the fifth browser, and loving it so far!!
-
Hi: Thank you for the new image.
I tested the new beta3 today. Here are the problems I encountered:
1.) VNC server extension. Call from command line brought the error below.
tc@box:~$ x11vnc
x11vnc: error while loading shared libraries: libXtst.so.6: cannot open shared object file: No such file or directory
2)
After installint the blueman extension, I was not able to locate the:
/usr/local/etc/init.d/bluez
bluez is not in this folder.
3)Can not start or restart or test status of pulseaudio server
tc@box:~$ pulseaudio -D
pulseaudio: error while loading shared libraries: libpulsecore-9.0.so: cannot open shared object file: No such file or directory
4) pavucontol can not be started either.
tc@box:~$ pavucontrol
pavucontrol: error while loading shared libraries: libgtkmm-3.0.so.1: cannot open shared object file: No such file or directory
5. Installed wifi.tcz - did not see any wlan sources. window disapperas after a few seconds. No wlan0 in ifconfig.
Everything else (ristretto,dillo,lefpad,pcmanfm) worked,
I miss the VLC player. Can it be brought over from previous repos?
Is it on your to do list bmarkus?
-
Just a note to beerstein's #5 issue..
My Netgear WG111 V2/V3 dongles have direct kernel support without needing firmware, and fire up ok in this alpha.
On a lark, tried getting the cute little "official" raspberry pi broadcom dongle working, but didn't put much time into it yet - despite the raspberry etching in the case, no joy! I gotta' get my blob on for that. :)
Thanks for putting lsusb into the main - it will help me track down the issue.
-
Which WiFi driver to use for the Zero W?
Are they working or is there some hoops to jump through?
Zero W locked up on boot, but A+ and Zero 1.3 worked fine.
Unloaded drivers and Zero W booted.
Still have to work my way through and find out which driver it was.
-
After installint the blueman extension, I was not able to locate the:
/usr/local/etc/init.d/bluez
bluez is not in this folder.
3)Can not start or restart or test status of pulseaudio server
tc@box:~$ pulseaudio -D
pulseaudio: error while loading shared libraries: libpulsecore-9.0.so: cannot open shared object file: No such file or directory
4) pavucontol can not be started either.
tc@box:~$ pavucontrol
pavucontrol: error while loading shared libraries: libgtkmm-3.0.so.1: cannot open shared object file: No such file or directory
It looks like you are missing the extension dep files or that, somehow, the "ldconfig" command has not been run by "tce-load"?
-
Notes on my Beta testing:
I am NOT overclocking the RPI2, just using the default arm_freq to cut down on any weird variables.
I load the TC.tcz graphical environment, and am loading and running that way. My wireless is called up with the graphical icon. Perhaps this is different from what beerstein is doing.
Got a TP-Link Nano usb model TL-WN725N up and running with the rtlwifi.tcz extension - it used the r8188eu ko firmare. Fired up from the gui, have not tested install and operation from the cli..
lovin' it!
-
Thanks all testing the beta. Goal is to have the base stable and work correctly with common CLI tools and common hw, like sound, WiFi, RTC, ... GUI applications and less frequently used packages are out of the scope now, they will be revised later when base system is finished. However, you can try 8.x packages, they are expected to work, as no new library introduced which may break applications.
Feedbacks are welcome :)
-
On a lark, tried getting the cute little "official" raspberry pi broadcom dongle working, but didn't put much time into it yet - despite the raspberry etching in the case, no joy! I gotta' get my blob on for that. :)
hi PDP-8,
I think this USB wifi adaptor has been working with piCore for years.
Find firmware-brcmwifi.tcz. I am not sure where it originally came from?
regards
Greg
-
Zero W locked up on boot, but A+ and Zero 1.3 worked fine.
Unloaded drivers and Zero W booted.
Hi Gavin,
does your Zero W works as expected with the stock 9.0beta3 image without installing additional packages?
Unfortunately I do not have Zero / Zero W and I can't test myself on real hw.
Béla
-
Screen off with xset working?
I noticed my screen never truly shuts off (hdmi - hdmi connection). I checked with xset q and also can fake it with xset dpms commands, but it never truly shuts off when left longer than 600 seconds. (as seen with xset q)
Do I need a vbe extension too possibly?
I'm not near my 8.1.5 version, so I haven't really tested screen shutdown / standby (other than just minimal screen blanking). I don't remember if it worked in that version..
Not a showstopper, but yes, it does help when running both the pi and 12v monitor from a solar charged battery...
-
Hi Bela, Zero W works fine without any WiFi stuff.
Will try the Pi3 WiFi first, get familiar with that.
I suspect it's just messing about with settings.
Now that we have a decent browser in Fifth, a piCore desktop is looking usable.
Oh, camera worked on Zero W, had not tried for ages.
WiFi Zero W camera 8)
Zero W mini Sumo bots with live action camera feeds and BT Smartphone control.
Rockcandy PS3 joysticks work in Linux.
PiCore just about robot ready ;D
-
PDP-8,
after loading the rpi-vc.tcz extension, you can turn off the display with
tvservice -o
and it should turn on again with
tvservice -p
(but mine currently doesn't O.o)
You probably want to automate this somehow because writing commands blindly is obviously a sdupit idea.
EDIT: I had to switch VTs back and forth to get my display back on. Maybe because I have a HDMI to VGA adapter attached.
-
Thanks misalf!! That works in this beta for sure.
So good in fact, that to turn it back on, I had to type in the blind sudo to a virtual terminal. :)
Might have to set up something like a sleep, followed by a filetool.sh -b, and then the screen off in case I have to come back hard with a power cycle. Ugh. :)
If I find something more elegant, I'll let you know.
-
Hi: (I am using RASPI 3)
So far I was able to fix the vnc server:
I downloaded and installed:libXi.tcz. Then I also needed to install libXtst.tcz.
Can somebody please try to verify this.?
x11vnc server is now running.
I still have problems with pulseaudio. I did an apps maintenance using the app browser and the system
recognized missing dependencies. Looks like it fixed some of it, but pulseaudio stll is not working: Now it misses a file named: libspeexdsp.so.1
Can somebody help here, or is pulseaudio not that important at the moment.
bluetooth and wifi still not working.
-
after install and setup of 9.beta3 on my RASPI 3 the
$ speaker-test
utility also did not work. After I installed libasound.tcz it worked. I still have no idea whether this problems are only in my installed system or if there is something missing in the .dep files or whether I am accessing a wrong reopo.
-
Tried piCore booting from USB stick.
It booted but no ethernet, no ipaddress.
Maybe the slower booting affected the Lan stuff as the Ethernet chip is also on USB.
Strange as the Lanchip is the USB hub????
-
I think when you try to boot from USB (on RASPI3) you need to put that "wait USB" command into
the cmdline.txt. Please refer to README file under Boot codes.
plse check bootcodes in FAQ
-
pulseaudio needs a fix.
pulseaudio: error while loading shared libraries: libspeexdsp.so.1: cannot open shared object file: No such file or directory.
libspeexdsp is not in the dependency file.
where can we find that extension?
-
Hi beerstein
You might try checking speexdsp.tcz or speex.tcz.
-
Thanks beerstein.
I did think it was something like that. tried usbwait=10.
But it was getting late and could not remember the syntax.
waitusb=10 added to cmdline.txt worked.
Now have piCore busy doing installing x11 - tce-load -wi TC.tcz
Yep X11 up and running
Boot is much slower, getting toward normal PC times, but not as long as Windows :P
Might have to get a M2 SSD and caddy, turn piCore into a real desktop.
Hey do USB CDROMs work on Pi?
-
pulseaudio needs a fix.
pulseaudio: error while loading shared libraries: libspeexdsp.so.1: cannot open shared object file: No such file or directory.
libspeexdsp is not in the dependency file.
where can we find that extension?
You might want to check your dep files - speex is a dep of libpulseaudio, which is in turn a dep of pulseaudio.
-
Hey do USB CDROMs work on Pi?
I have never tried and never heard someone tried yet, but it must work. You need the necessary kernel modules for the filesystem, the cdrom module and for the USB, but I'm sure everything is available. I do not have such hardware. If you can try, let us know the result ;)
-
May need a powered hub? I recall the pi had a bit weak USB output, and optical drives need some power.
-
My security cam Pi's use a WD purple in a USB3 externally powered caddy no problem.
Might get another $5 caddy and try a sata DVD drive :-*
Make myself a Pi Juke box? Got hundred of CD I have not heard since the last player bit the dust.
hmm robot arm with cdrom vacuum pickup, add to list ::)
-
Tried piCore booting from USB stick.
Are there any downsides in altering the OTP memory in order to enable USB booting?
Like warranty voided, maybe slower boot due to searching for boot files on USB, etc.
The only warning I found so far was that it can't be undone, which in itself doesn't necessarily sound like a big deal.
Also, is the firmware currently provided with piCore 9.0 able to set the USB boot bit, or is the 'next' branch / beta firmware from git required? The firmware and boot files that come with 8.x didn't seem to have recognized the setting in config.txt.
-
Might have to get a M2 SSD and caddy, turn piCore into a real desktop.
I believe the USB2.0 bandwith is the limit. ::)
I don't think installing a SSD for raspberry pi would do much help.
-
thanx for the help. I installed speexdsp.tcz and speex.tcz as well as libpulseaudio.
Now the error message can not find "libjson-c.so:
-
Hi beerstein
Try json-c.tcz
-
thanx for the help. I installed speexdsp.tcz and speex.tcz as well as libpulseaudio.
Now the error message can not find "libjson-c.so:
Please check that the files libpulseaudio.tcz.dep and pulseaudio.tcz.dep are present on your system and paste the contents here.
-
Also, is the firmware currently provided with piCore 9.0 able to set the USB boot bit, or is the 'next' branch / beta firmware from git required? The firmware and boot files that come with 8.x didn't seem to have recognized the setting in config.txt.
Yep, unless it has changed you do need the next version.
Option is to boot from SD and redirect to USB, which requires special bootloader for the other Pi's.
Don't think the flashing the OTP has caused any issues at the moment, except maybe boot speed.
I don't think installing a SSD for raspberry pi would do much help.
USB2 is the restriction, but M2 SSD will be lots of space for???? Media Server?
It should be the lowest power MSD/MB
Will 32GB be enough for a pICore development desktop?
-
Will 32GB be enough for a pICore development desktop?
a 32gb sd card works fine for me
-
Setup up WiFi on a SD card in a Pi3, as per my post a year ago.
Glad I put that down in the posts, forgotten I had documented it, very sad the memory these days.
Seems to work, I get an ip address for wlan0.
Stick same card in a Zero W and a few seconds after booted I get the message
"No wifi devices found!"
Good news is camera is working :P
Off to Pi forums for clues.
Bela, put notes in the boot partition readme for setting up WiFi/BT/camera when we figure it out.
-
the rpi3 internal bt works...
-
thanks juanito: Indeed the dep files for pulseaudio, libpulseaudio, wifi,blueman are all missing in my
/optional folder. I have no idea how this could happen.
How can I check for these files at the repo?
How can I download them and reinstall?
-
as an example:
$ wget http://tinycorelinux.net/9.x/armv7/tcz/pulseaudio.tcz.dep
-
I discovered that even the wget command is not working because of missing dependencies. I think the problem is either a bad uSD card or a defective RASPI_3 or my power supply is too week. I need to check this first and will then post back.Thankx for the help.
-
I discovered that even the wget command is not working because of missing dependencies.
IIRC, install openssl.tcz
I think I've seen a post about that.
-
Are there any downsides in altering the OTP memory in order to enable USB booting?
Like warranty voided, maybe slower boot due to searching for boot files on USB, etc.
The only warning I found so far was that it can't be undone, which in itself doesn't necessarily sound like a big deal.
Also, is the firmware currently provided with piCore 9.0 able to set the USB boot bit, or is the 'next' branch / beta firmware from git required? The firmware and boot files that come with 8.x didn't seem to have recognized the setting in config.txt.
The 9.0 firmware should do it. It's posted on the rpi website how to do it, so I doubt there are any warranty issues. New boards from the factory are set this way.
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/net.md
The system will always look for a bootcode.bin on the SDcard first, so there should be no downside.
-
I was able to fix the wget problem. Wget needs:
wget: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory
The extension libunistring.tcz is not listed in wget.tcz.dep
I do not know who is going to fix this. After I installed libunistring.tcz, wget command worked.
pulseaudio and pavucontrol seem to work now, but I had to install several dependency extensions
manually.
the blueman bluetooth extension is broken:
tc@box:~$ tce-load -w -i blueman.tcz
blueman.tcz.dep OK
dbus-python.tcz.dep OK
python.tcz.dep OK
gtk3-gir.tcz.dep OK
gdk-pixbuf-gir.tcz.dep OK
gobject-introspection.tcz.dep OK
at-spi2-core-gir.tcz.dep OK
atk-gir.tcz.dep OK
pango-gir.tcz.dep OK
pygobject3.tcz.dep OK
py2cairo.tcz.dep OK
libnotify-gir.tcz.dep OK
libnotify.tcz.dep OK
Downloading: libbluetooth.tcz
Connecting to repo.tinycorelinux.net (89.22.99.37:80)
wget: server returned error: HTTP/1.1 404 Not Found
md5sum: libbluetooth.tcz.md5.txt: No such file or directory
Error on libbluetooth.tcz
tc@box:~$
I do not know how to fix this.
-
The bluetooth kernel modules are not yet in the piCore 9.x repo, so the libbluetooth extension was not copied over from the 8.x repo.
-
bluetooth-KERNEL, bluez and libbluetooth added to the 9.x armv7 repo
-
great, thanx. I will try bluetooth today.
BTW: I have now WIFI, pulseaudio and pavucontrol working. I needed to copy a lot of extensions over manually.
Should I list all of them here or have these problems been fixed?
-
As far as I could see, only bluetooth-KERNEL, bluez and libbluetooth were missing?
-
I installed bluez and blueman again. I can now start the bluetooth daemon bluez from the command prompt.
After startx I can also start bluemen from GUI but errors show up and the BT manager disappears after a few seconds on the screen..
It probably might have something to do with permissions?
How to start blueman manager from command line? Would that help?
-
Blueman uses blueman-manager and blueman-applet - use "ps aux | grep blue" to check if either of them are running and kill any instances if they are.
Next start blueman-manager in one terminal window and blueman-applet in another terminal window and check for any error messages.
-
both commands generated long lists - too long to post here. I just post the end part of both commands:
1. from blueman-applet:
UpdatePowerState (/usr/local/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py:159)
off True
foff False
on True
current state False
new state False
_________
RequestPowerState (/usr/local/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py:131)
Requesting 1
_________
on_power_state_change_requested (/usr/local/lib/python2.7/site-packages/blueman/plugins/applet/KillSwitch.py:119)
1
_________
UpdatePowerState (/usr/local/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py:159)
off True
foff False
on True
current state False
new state False
_________
timeout (/usr/local/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py:126)
Timeout reached while setting power state
_________
UpdatePowerState (/usr/local/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py:159)
off True
foff False
on True
current state False
new state False
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
(blueman-applet:5797): Gtk-WARNING **: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/check-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
2. from blueman manager
pa_context_event (/usr/local/lib/python2.7/site-packages/blueman/main/PulseAudioUtils.py:341)
4
_________
on_pa_ready (/usr/local/lib/python2.7/site-packages/blueman/plugins/manager/PulseAudioProfile.py:27)
connected
_________
<lambda> (/usr/local/lib/python2.7/site-packages/blueman/main/PulseAudioUtils.py:353)
1
_________
get_interface_version (/usr/local/lib/python2.7/site-packages/blueman/bluez/BlueZInterface.py:13)
Detected BlueZ 5
_________
SetAdapter (/usr/local/lib/python2.7/site-packages/blueman/gui/DeviceList.py:269)
_________
SetAdapter (/usr/local/lib/python2.7/site-packages/blueman/gui/DeviceList.py:269)
No such adapter
_________
on_adapter_changed (/usr/local/lib/python2.7/site-packages/blueman/gui/manager/ManagerToolbar.py:80)
toolbar adapter None
(blueman-manager:5812): Gtk-WARNING **: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/check-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/blueman/gui/manager/ManagerMenu.py", line 92, in <lambda>
item.connect('activate', lambda *args: self.blueman.Applet.open_plugin_dialog())
File "/usr/local/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
**keywords)
File "/usr/local/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBu.ception: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
blueman-services version 2.0 starting
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
eth0
(blueman-services:5889): Gtk-WARNING **: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
tc@box:~$
/usr/local/lib/python2.7/site-packages/blueman/gui/GenericList.py:6: PyGIWarning
It looks kike it can not find the default controller
-
Did you comment out the disable bt overlay in the config?
(Also, please use code tags)
-
thanx -which config file do you mean? Just one or are there more than one?
-
see:
http://forum.tinycorelinux.net/index.php/topic,20854.0.html
-
thank you Juanito. Now bluetooth works from command line. Connected a keyboard and a mouse, but had problems with an external bluetooth speaker. To hook this speaker up is probably another animal.
Pulseaudio comes into play here. Hmm?
Blueman does not work out of the box yet.
After the bluetooth daemon was running and I had the bluetooth command line:
[bluetooth]# connect 7C:1E:52:67:41:FA
Attempting to connect to 7C:1E:52:67:41:FA
I was able to start blueman from its icon in wbar and the management gui window was stable and working.
BTW: piCore with this configuration will be very useful with the newly introduced PI ZERO W, which has built in WIFI and Bluetooth - and is available too. Using Raspian with the ZERO ---> too slow IMO.
-
yes, you will need pulseaudio to connect a bluetooth speaker