Tiny Core Base > piCore Test Releases

piCore-9.0beta3 released

(1/11) > >>

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

PDP-8:
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!!

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

PDP-8:
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.

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

Navigation

[0] Message Index

[#] Next page