piCore-11

[Twist]

Great stuff. With a few modifications (config.txt, cmdline.txt and remastered to change /etc/inttab) I got 11alpha1a up and running on a headless zero-w with just a serial console.
Next steps obvs to see if wireless can be made functional. I then noticed that the tcz's currently available do not cover those normally covered by compiletc. Missing at the moment are: bison, findutils, m4, make, patch, pkg-config, libffi_base-dev, libmount-dev. Not sure all of those are needed all the time, but certainly make is.

Can you give an indicative timeline of when these will be available so that any other missing tcz's can be compiled and build under picore11 itself?

[bmarkus]

Check repo, many of the claimed tcz packages were aded to repos today.

[Twist]

Ah, nice.
Not sure if you're aware, but mpfr.tcz is not yet available (gcc > mpc > mpfr).
This may not be the right place to ask, but can I compile 11.x extensions on a 9.x, or 10.x picore system? Or should I just wait a little until the basics for compiling tcz's on 11.x is available?

[bmarkus]

can I compile 11.x extensions on a 9.x, or 10.x picore system? Or should I just wait a little until the basics for compiling tcz's on 11.x is available?

Yes, they are expected to work.

[uli]

Hi,

installed it on a 3B+ and it works out of the box. Great work. Thanks.

I dared to mess a bit with the boot files to allow for a (somewhat simplistic) dual boot with Rasbian, plus, went for httplist to get rid of the root partition and load extensions from the web instead.
However, that way I found that I couldn't reliably connect to the networks. Turned out that eth0 is not available in this case.

Seems that a waitusb as a kernel parameter solved it for now. Generally at least, no statistics on rare failures yet.

So, I am happy I could solve it. Assuming now that issue is an inherent one of the current build, and not due to my messing around. Unless you tell me otherwise...

Though, I am wondering whether the boot sequence should perhaps make sure that we are waiting for eth0 becoming available first, then going for a dhcp request and onwards.

Since I would guess there are very few people these days who wish to run their 3B+ without networks, I would think trying to harden the startup procedure for everyone might perhaps be beneficial. I know by far too little about the Raspi world (yet) to dig into these things myself, but perhaps someone might have a good idea, or tell me that I caused that issue myself by messing around with boot files...

Uli

[Paul_123]

PiCore is a very basic shell of Linux.   Everyone does something different with it.  Network purposely connects in the background.

 If you need to wait for network,  add some code in /opt/bootlocal.sh to wait for network to be up and connected with a valid address.

[onelife]

Hi all,

I don't want to ask a silly question in this thread BUT perhaps a simple yes, or no, if it's worth a try

I'm far from a guru with TC and try make it work for how we use this - I am currently on 8.1.5 and thinking of making the big jump to 11. Do you think this is a feasible upgrade / rebuild of our portable system? The current tcz's I have on 8.1.5 are :

Code: [Select]

mc.tcz
mpg123.tcz
rsync.tcz
bash.tcz
coreutils.tcz
vtun.tcz
lzo.tcz
visudo.tcz
cpulimit.tcz
libmagic.tcz
dermixd.tcz
java.tcz
libsndfile.tcz
studio.tcz
ntp.tcz
libvorbis.tcz
flac.tcz
firmware-ralinkwifi.tcz
libusb.tcz
usbutils.tcz
wifi.tcz
usb-modeswitch-data.tcz
usb-modswitch.tcz
firmware-brcmfmac43430.tcz
wireless-4.4.13-piCore+.tcz
rtc-4.4.13-piCore+.tcz
usb-serial-4.4.13-piCore+.tcz
alsa.tcz
alsa-plugins.tcz
alsa-utils.tcz
wireless-4.4.13-piCore_v7+.tcz
rtc-4.4.13-piCore_v7+.tcz
usb-serial-4.4.13-piCore_v7+.tcz
libacl.tcz
openssh.tcz
alsa-modules-4.4.19-piCore_v7+.tcz
alsa-modules-4.4.19-piCore+.tcz
alsa-modules-4.4.39-piCore_v7+.tcz
usb-serial-4.4.39-piCore_v7+.tcz
wireless-4.4.39-piCore_v7+.tcz
firmware.tcz
alsa-modules-4.4.39-piCore+.tcz
libevdev.tcz
libevent.tcz
libopus.tcz
beamer.tcz
As you might see - some of these are my own tcz's and those I believe I should be able to make work - But I'm worried some of the more common tcz's are missing such as :

Code: [Select]

usb-serial-4.4.39-piCore_v7+.tcz
usb-modeswitch-data.tcz
usb-modswitch.tcz
mpg123.tcz
rsync.tcz
firmware-brcmfmac43430.tcz
vtun.tcz
ntp.tcz
libvorbis.tcz
libasound.tcz
I wonder if these tcz's can perhaps be taken from TC 8?

Thanks and let's see anyones thoughts.

    [EDIT]: Added code tags.  Rich

[Juanito]

At the moment piCore 9.x is the most recent release and piCore-11.x is in beta testing.

You can see which extensions are available by looking at the following in a browser:

repo.tinycorelinux.net/9.x/armv7/tcz
repo.tinycorelinux.net/11.x/armv7/tcz

[Pengo]

@onelife:

I am happy to say that piCore 9.03 is extremely stable (I've multiple Pi's with an uptime > 1 year!)

Could have been even more if we didn't have a power outage.

So if version 11 will have the same stability, I'll be moving towards it  ;-)

[onelife]

Thank you for this - Indeed then I will only try go to version 9.

However, I'm not sure if this will fix my issue. I'm trying to get a new modem to work that requires the latest usb-modeswitch from what I am told.

I started a ticket on this topic here http://forum.tinycorelinux.net/index.php/topic,23609.0.html but I'm not sure if 9. will then be the solution as I don't see any usb-modeswitch in that repo? Perhaps the modemmanager.tcz is the new version that has this function built in?

I guess I can download the 9 iso and start poking around - But seems many tcz's I will need could be missing.

Do most from 8 actually work straight over with 9? Example, rsync or vtun?

Thank you for confirming not to go to 11 yet - That I'm sure would have been a deep hole for someone that's not experienced.

Regards,

[Juanito]

Some extensions from piCore 8.x will work in 9.x, but others (that depend on older libraries) will not.

You will have to try and see - any extension identified as working can be copied over to the 9.x. repo.

[Rich]

Hi onelife

... But I'm worried some of the more common tcz's are missing such as :

Code: [Select]

usb-serial-4.4.39-piCore_v7+.tcz
usb-modeswitch-data.tcz
usb-modswitch.tcz
mpg123.tcz
rsync.tcz
firmware-brcmfmac43430.tcz
vtun.tcz
ntp.tcz
libvorbis.tcz
libasound.tcz
I wonder if these tcz's can perhaps be taken from TC 8? ...

usb-serial-4.4.39-piCore_v7+.tcz  can not be taken from TC 8 because it's a different kernel version (4.4.39-piCore_v7+).
You would need to use  usb-serial-4.9.22-piCore-v7.tcz  instead.