Tiny Core Base > piCore Test Releases

piCore 6.0 Beta200

<< < (3/7) > >>

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

bmarkus:

--- Quote from: lykkedk on December 20, 2014, 01:04:29 AM ---
Soo, how do you guys jump between theese version numbers, when the only download is e.g 3.14.y


--- End quote ---

I keep a copy of downloaded versions for later use. Regarding final version of piCore it will be uploaded to the repo.

lykkedk:

--- Quote ---I keep a copy of downloaded versions for later use. Regarding final version of piCore it will be uploaded to the repo.

--- End quote ---

Okay, i use same method, will continue to do so, further on  :)

RG; Jesper

sbp:
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

meo:
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

Navigation

[0] Message Index

[#] Next page

[*] Previous page