Recent Posts

1

dCore Imported Extensions / Re: e17 howto

« Last post by Jason W on Today at 06:00:16 PM »

Ok, done.

Does this fix the missing deb mentioned in the other thread?  I was about to look into that.

I have made a performance improvement to the importsce routine, I will upload it tomorrow.  Maybe we should test that missing dep after the changes.

2

dCore Imported Extensions / e17 howto

« Last post by jls_legalize on Today at 04:16:21 PM »

Hi
I've attached an updated readme for e17 and also the data for e17.
the e17-stable in PKGEXTRAREPODEP can be removed as well as bullet and harfbuzz since those packages are available in the repos listed in the readme.
thanks Jason

3

dCore Imported Extensions / Re: ub-dCore: X does not start

« Last post by Jason W on Today at 09:32:10 AM »

In reference to my machine where the mouse and keyboard freeze on starting X, it was caused by backing up files in /usr/share/X11/xorg.conf.d.  Removing them from my backup fixed the issue.

4

Raspberry Pi / Re: Building landing wheels while in flight

« Last post by mcdudeabides on Today at 08:46:29 AM »

Hello again Bela.  Please forgive me if I'm being obtuse, but I am challenged in understanding how to apply the extensions concept.  If I were to put myself in Steen's shoes, then I would see piCorePlayer as the sum of the following parts:
1) the base TC kernel image (retrieved by direct download and burn)
2) the base support libraries (most likely the things found in a "full" Linux deploy, loaded by tcz- things like alsa, flac, ffmepeg, etc.)
3) support utilities (most likely things to extend Linux functionality, loaded by tcz- things like wireless, i2c tools, firmwares, etc.)
4) support applications (loaded by tcz, things like dropbear, perl, etc.)
5) third party applications (ready for ARM, not tcz packaged, requires custom integration - things like OliWeb, squeezelite)
5) end user support (the scripts, web pages, config stores that "are" piCorePlayer - custom created, integrated)

If I were the builder of the next flavor of the piCorePlayer image (assuming no kernel update), I could see the convenience of performing a tce-update (I guess this would have to be base norestore??) to refresh all the extensions.   The third party applications currently installed would be untouched.  Most likely I would then be making changes to the end user support environment (e.g. - troubleshooting new DAC shows new module and modprobe needed, base script modified).  I'm assuming at this point that all the changes for end user support would be packaged and become their own unique tcz? Is this package something that should be submitted to TC or is it in the "custom repo"?

Assuming the above, if I now try to think from the perspective of the end user.  I have a running instance of PiCorePlayer.  There is a button on the web page to "update" (assume no kernel update at this time).  Can I then call the tce-update and have it download and install the changes?  Is there a way in a running instance to drop all of the current extensions to allow a reload (could brute force all the LOOP devices)? I guess after this a reboot will be required.

I can see the application in going through minor iterations (e.g. 1.14a to 1.14b to 1.14c etc.) using tce-update.  I don't see it applying to kernel updates, or is that also something could work?

Forgive the ramblings, I had a quick window of time to ask the questions and wanted to get them out there.

5

Raspberry Pi / [Solved]Re: Key Generation at boot PiCore-SSH

« Last post by jodel on Today at 08:07:41 AM »

Thanks for pointing me in the right direction.  I have just started on PiCore an it is taking me a while to come to grips with the differences between it and other linux that I have used.  The Corebook.pdf is useful.

6

Raspberry Pi / Re: Key Generation at boot PiCore-SSH

« Last post by bmarkus on Today at 06:02:36 AM »

Add key files to your backup. Please read the extension's info.

7

Raspberry Pi / [Solved]Key Generation at boot PiCore-SSH

« Last post by jodel on Today at 05:49:59 AM »

Hi, Just installed  piCore-5.2.1-SSH.zip.  Every time it boots it generates 3 different Keys.  Is this necessary and if not, how do I stop it?  Jodel

8

piCore Final Releases / piCore 5.2.2 released

« Last post by bmarkus on Today at 05:07:28 AM »

Team Tiny Core is pleased to announce the availability of piCore 5.2.2, the Raspberry Pi port of Tiny Core Linux. It is an independent system architected by Robert Shingledecker and now developed by a small team of developers with strong community support.

Tiny Core Linux is not a traditional distribution but a toolkit to create your own customized system. It offers not only flexibility, small footprint but a very recent kernel and set of applications making it ideal for custom systems, appliances as well as to learn Linux, matching Raspberry Pi perfectly. It is running entirely in RAM. There is no installation in conventional terms; extensions mounted read only, after reboot the same clean system is available. Base raw SD card image with CLI version is only 21.5 Mbyte including RPi boot loader, firmware and support files.

Changes from 5.2.1:

* Raspberry Pi firmware updated to April 14, 2014 version
* official BusyBox patches applied
* curaga's wget3 BusyBox patch applied, setting default timeout to 10s
* tce-load: Don't show an error when extension contains multiple modules
* tce-load: Use sudo when unmounting meta-extensions

Images with preinstalled SSH for headless operation and with GUI also available at

http://tinycorelinux.net/5.x/armv6/release/

For support visit http://forum.tinycorelinux.net/index.php/board,57.0.html

Béla Márkus
piCore Release Manager

9

TCE Q&A Forum / Re: Problem Saving ALSA Settings

« Last post by Juanito on Today at 03:33:34 AM »

I cant seem to find the src for libao in the repo so hard to tell how it was compiled....

see http://repo.tinycorelinux.net/5.x/x86_64/tcz/src/libao/compile_libao for the corepure64 extension, but it looks to be like the x86 extension was compiled without alsa support...

10

TCE Q&A Forum / Re: Problem Saving ALSA Settings

« Last post by ananix on Today at 02:52:42 AM »

Working on same project and have same problem, I have made two keys now one with working OSS and one with ALSA, both also having libao installed.

experimenting with command -r sound:local:oss, -r sound:local:alsa and sound:remote ...... leads me to the arguments is working but when local it always crashes with

ao_oss ERROR: Unrecognized channel name "#"¤%¤GARBAGE CHARACTERS!"#"!" in channel matrix "#!"#GARBAGE CHARACTERS¤#"%"
ao_oss WARNING: Input channel matrix invalid; ignoring.
rdesktop segfaults.....

I found others with same problem but with other programs, one placed it was fixed with removing a kernel module and i also have this

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591396

Can we use that to figure out if rdesktop have same problem or to get closer for the root cause of unrecognized channel name?

I cant seem to find the src for libao in the repo so hard to tell how it was compiled....

Did anyone try to compile rdesktop from newest source?

I think thats my next step....

Hope we can help each other figure this out

  -- Regards Andreas