Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: bmarkus on December 17, 2014, 02:25:30 AM
-
After having issues with latest 3.17.y/3.18.y kernels I moved back to a more stable longterm 3.14.y Please try, specially WiFi and audio and report your findings.
http://repo.tinycorelinux.net/6.x/armv6/release_candidates/
This is a beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.
Since this is an beta cut, although the team has worked through several preview cuts, we ask that only experienced users test. This cut is not for production use. The features in any beta may change before a public release candidate is available.
Note that the fltk library has been updated to 1.3.3 to enable unicode. fltk-1.1 and 1.3 can be installed at the same time, and old apps using 1.1 will continue to work.
We appreciate testing and feedback.
Changelog for 6.0 Beta200:
* kernel updated to 3.14.23
Changelog for 6.0 Beta100:
* kernel updated to 3.18.0
Changelog for 6.0 Beta2:
* kernel updated to 3.17.4
* RPi firmware updated to December 3 release
* serial terminal now started by default
* preinstalled components updated
Changelog for 6.0 Beta1:
* kernel updated to 3.17.3
* glibc updated to 2.20
* gcc updated to 4.9.2
* e2fsprogs base libs/apps updated to 1.42.12
* util-linux base libs/apps updated to 2.25.2
-
Hi bmarkus!
Tried this new beta and downloaded wifi. Switched to a wifi adaptor (netgear) and it worked out just fine. It took just a few moments to download compile-essentials.tcz. Good work!
Kind greetings,
meo
-
i2cdetect not working, get the message
Error: could not open file '/dev/i2c-1 .....
got i2c-tools.tcz loaded etc
had no problem with beta2
-
Checked Beta200, had issues even mounting in Linux to add/resize partitions.
Same problem Beta100.
Gone back to Beta2
-
Load the i2c /dev driver:
sudo modpobe i2c-dev
This will create the two i2c entries in /dev.
-
Checked Beta200, had issues even mounting in Linux to add/resize partitions.
Same problem Beta100.
Please provide details of the mounting issue. What do you mean 'even'?
-
I use Windows 7 + Diskimager to put img on SDcard.
Then use my Linux Mint 17 box and Gparted to increase 2nd partition to make room for i2c-tools and busybox-httpd plus run scripts.
Add 3rd partition sized to rest of SDcard for logs.
Try to do this with Beta100/200 and the two partitions don't mount automatically in Linux.
-
Try to do this with Beta100/200 and the two partitions don't mount automatically in Linux.
Which two out of three? Are you saying, that only mmcblk0p1 mounted?
Anyhow, only one partition automounted, where /tce found, never ever two in the base system. Can you mount them manually and do you see /tce?
-
Both beta/100/200 SSH img partitions don't mount automatically in Linux.
Some orange? icon next to them, not sure what that means yet.
Normally when img written by diskimager, I just pop it in the Linux box, resize 2nd partition and add the 3rd.
Then I stick it in the Raspberry Pi then filezilla/MC my scripts and changes, this bit I think I can automate once I learn more Linux.
Probably can automate the whole SD imaging process, guess it's time to learn dd.
-
There are too many components used in the process. If you are using Linux (MINT?) to resize, why WINDOWS7 used to create image when it can be done on Linux with dd?
If you are using WINDOWS to create why another LINUX (MINT?) used instead of piCore itself to resize and create partitions? It has all necessary tools.
Please check what orange icon means.
Also check them on the Linux box with fsck before doing anything with them.
Published images created on TC 6.0 x86 ASUS notebook with buit-in card reader and tested on a Raspberry Pi box.
-
Hi.
I just want to say, that i like the use of a long term kernel (Aug. 2016 for 3.14.y)
Right now i use a 3.16.3 with some homerolled .tcz.
I have something, on my mind asking for some time now, regarding the kernel version e.g 3.14.y
When i download the e.g 3.14.y version, it has to be at the moment, where it has the right version number (.y), otherwise the kernel could be 3.14.33, 3.14.23 or whatever.
Soo, how do you guys jump between theese version numbers, when the only download is e.g 3.14.y
I have my "own" copy of the kernel 3.16.3, that i use, if i need to build some special package of kernel modules. (Example i have a module.tcz witch contains modules only for the linux ir / lirc)... This i have made only for bringing the overall image/size speed of booting so low as possible in my system. I allways have to use this specific kernel version, when i have to do that, otherwise the modules come out with wrong numbers.
I hope, that i made my self clear enough in my quistion?, and now that i finally got some day's off, i am looking forward to play with this new betacut....
Besides all that, i wish all reading this a good christmas.
Regards;
Jesper.
-
Soo, how do you guys jump between theese version numbers, when the only download is e.g 3.14.y
I keep a copy of downloaded versions for later use. Regarding final version of piCore it will be uploaded to the repo.
-
I keep a copy of downloaded versions for later use. Regarding final version of piCore it will be uploaded to the repo.
Okay, i use same method, will continue to do so, further on :)
RG; Jesper
-
Hi Belá
I have tested both my wifi adaptors (Edimax (realtek) and radlink) and both are working fine with your new beta (3.14.23 kernel).
The only thing which is bothering me with this kernel is:
It seems not to be maintained by the raspberry developers. The last update in the 3.14.y kernel was 8 months ago whereas the current stable kernel (3.12.y) was updated 23 hours ago.
The 3.14.y kernel is somehow not used anymore at the raspberry github, where focus for the moment is on 3.12.y (stable) or on the two development branches 3.17.y (25 days ago) or 3.18.y (2 days ago).
So if we are not going to use a development branch then why not choose a stable kernel that is maintained at the moment (3.12.y)?
Steen
-
Hi bmarkus!
Thanks for your incredible work on piCore! Since there has been a lot of laboring with different kernels lately, I did a checkup myself and I think "sbp" is right on this one. First a stable kernel that is and has been used for quite some time and then the rest of the software needed for the piCore.
Keep up the good work bmarkus,
meo
-
Hi Steen and Meo
situation is not so bad with 3.14.y as you say. Branch was created 8 month ago, but there are updated which are one month old only.
You are right, kernel development effort is focusing on Raspbian stable 3.12.y kernel and it is the most advenced in terms of Raspberry, while 3.17.y and 3.18.y are experimentals for example used to develop device tree or other features, but much behind on audio SoC support for example or has issues with wifi device support. Now as I see 3.17.y/3.18.y can't be used as a stable kernel in near future for us. We can make a decision to be conservative and use the mainstream Raspberry kernel, 3.12.y. I will make a 3.12.35 kernel and see how it goes.
Béla
-
Hi Béla!
Sounds good! Will try when posted.
Kind regards,
meo
-
Hi Béla,
I've installed this image and followed my tutorial (http://www.gerrelt.nl/RaspberryPi/wordpress/tutorial-unpluggable-squeezelite-player-on-tinycore)for setting up squeezelite.
But it isn't working.
There are no sound devices available:
tc@4-Gooseberry-PortableStereo:~$ sudo aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
tc@4-Gooseberry-PortableStereo:~$
But the USB soundcard is seen by lsusb.
Any tips?
Greetings,
Gerrelt.
-
Gerrelt@
Thanks, will check.
-
Hi Béla,
Never mind, I forgot to install "alsa-config"
After running this:
tce-load -wi alsa-config.tc
I got my sound devices back!
Greetings,
Gerrelt.
-
Béla,
I'm testing the X version now. Wifi seems to be working well.
I've found that the tce applications manager is still working too slow. Same as for Beta 1, 2 and 100. Same when loaded from GUI, or command line terminal.
Another issue is with the libs, or directories when installed the cmus media player.
libncurses.so.5: cannot open shared object file: No such file or directory. But ncurses.tcz is installed well.
-
Jan
thanks for testing and feedback.
I've found that the tce applications manager is still working too slow. Same as for Beta 1, 2 and 100. Same when loaded from GUI, or command line terminal.
Which function is slow? Please provide details.
Another issue is with the libs, or directories when installed the cmus media player.
libncurses.so.5: cannot open shared object file: No such file or directory. But ncurses.tcz is installed well.
Thanks for reporting. cmus must be rebuilt against the new version of ncurses.
-
cmus updated in repo. Please note new dependencies.
-
Hi Béla,
Which function is slow? Please provide details.
Overall respond speed is slow. Seems that the communication is somehow delayed. When I enter, or click the command, there is no response for several seconds. After another command enter the delay is again and again. The delay is even for more than 10 seconds. Means to install something which takes 1 minute in 5.3.1 distro, in 6.0 takes more than 5 minutes.
-
Even the mirror picker takes roughly 30 seconds instead of five.
-
cmus is working well now.
Good job. :)
-
Hi Béla,
Which function is slow? Please provide details.
Overall respond speed is slow. Seems that the communication is somehow delayed. When I enter, or click the command, there is no response for several seconds. After another command enter the delay is again and again. The delay is even for more than 10 seconds. Means to install something which takes 1 minute in 5.3.1 distro, in 6.0 takes more than 5 minutes.
I can't reproduce this, on my system it works fast as expected. Can you check is it a generic network issue or reletad just to apps?
Are you using wired or wireless connection?
Which repo is used? Default repo.tinycorelinux.net must be ok from your location.
What is the ping time to your router and other sites?
Is your system date and time correct?
-
Using RPi B+ with piCore 6.0 Beta 200-X. I can't load mirror.tcz. Every time I format the sd card and put piCore back on it it says the mirror.tcs file is invalid to load. I had tried to manually load it as well and same result.
I just checked the contents of /opt/tcemirror and it only has the repo.tinycorelinux.net url. I even created the directory /opt/localmirrors as the ApBrowser said to do that but it didn't help.
I can ping multiple internet sites and my own network computers but am unable to access the internet via anything but the terminal. The ApBrowser can't access the internet and it's probably because it can't load the mirror tcz.
I'm frustarted as it looks like piCore would be an excellent OS for my Pi but even with the older non-release candidates (the stable version) I had this problem. Hence the reason I tried this one.
I had to reformat my sd cards via my dad's Windows 7 PC as I think my Macbook Pro is corrupting them even when using a very old USB SD Card reader with an adapter. But I re-downloaded this OS on my dad's Win7 laptop and installed it to the card using Win32DiskImager that was recommended via raspberrypi.org. So I'm not sure how to help here other than let you know that for whatever reason the mirror.tcz file is either corrupt in the OS image itself or something is odd about my setup that is causing this issue. Please let me know if you know what the problem is and if I can fix it. Thank you.
-
Using RPi B+ with piCore 6.0 Beta 200-X. I can't load mirror.tcz. Every time I format the sd card and put piCore back on it it says the mirror.tcs file is invalid to load. I had tried to manually load it as well and same result.
Did you expand the file system as it is written in README file?
-
Using RPi B+ with piCore 6.0 Beta 200-X. I can't load mirror.tcz. Every time I format the sd card and put piCore back on it it says the mirror.tcs file is invalid to load. I had tried to manually load it as well and same result.
Did you expand the file system as it is written in README file?
Nope. I didn't read that section because the fist part of that section states: "Base system, piCore-5.x has only the first partitions;"
I'll try expanding it when I get back to working on my Pi. It's not easy for me to be able to read what is on my TV since the text is so small compared to the size of the TV, so it's inconvenient to have to work with it that way. I have no other way to view X other than trying to figure out how some people use their current laptop or android tablet screens as the monitor. And I'm annoyed with running X in VNC on my laptop but I can't even do that with piCore yet. If ever. I haven't even tried to see if SSH is working yet.
I really like piCore so far, except the part that I can't install anything. It's super fast but I would want to install it permanently to an SD card so that my RAM is free for regular RAM-based tasks. It's only got 512MB ram. Thanks.
-
Using RPi B+ with piCore 6.0 Beta 200-X. I can't load mirror.tcz. Every time I format the sd card and put piCore back on it it says the mirror.tcs file is invalid to load. I had tried to manually load it as well and same result.
Did you expand the file system as it is written in README file?
Nope. I didn't read that section because the fist part of that section states: "Base system, piCore-5.x has only the first partitions;"
You are not using the base system but the -X version with preinstalled apps on the second partition which must be sized to fit your SD card and the way using piCore. By default it has room only for preinstalled apps.
-
You are not using the base system but the -X version with preinstalled apps on the second partition which must be sized to fit your SD card and the way using piCore. By default it has room only for preinstalled apps.
Ah okay. Thank you, bmarkus.
-
Hi Béla,
The issue with the app manager was recognized as a pure server issue.
Seems that the main repo.tinycorelinux.net is overloaded, especially during evening time, and is very, very slow.
Even the second distro.ibiblio.org is quite slow. The best working are ftp.nluug.nl and ftp.vim.org.