Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 24 Nov 2017, 07:10
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
kernel compiling in woof-ce
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 31 of 32 [467 Posts]   Goto page: Previous 1, 2, 3, ..., 29, 30, 31, 32 Next
Author Message
musher0


Joined: 04 Jan 2009
Posts: 11174
Location: Gatineau (Qc), Canada

PostPosted: Sat 22 Apr 2017, 01:01    Post subject:  

Hello all.

I agree with pelo on this one.

We developers can do research about a new kernel, but middle-of-the-road
users will appreciate finding a brief explanation of the features of any new
kernel and why it is better than the one published before it.

BFN.

_________________
musher0
~~~~~~~~~~
"Logical entities must not be multiplied beyond necessity." | |
« Il ne faut pas multiplier les entités logiques sans nécessité. » (Ockham)
Back to top
View user's profile Send private message 
0xdawg


Joined: 18 Sep 2015
Posts: 33
Location: .de/

PostPosted: Sat 22 Apr 2017, 03:41    Post subject:  

musher0 wrote:
.... a brief explanation ....

there are brief explanations all over the web.

feel free to educate yourself for in-depth informations Rolling Eyes

_________________
Current Puppy: Carolina 1.3@Wyse X90LE
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Sat 22 Apr 2017, 03:43    Post subject:  

I ususally look here at the changelog

https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.10.11

http://news.softpedia.com/news/linux-kernels-4-10-11-4-9-23-lts-4-4-62-lts-improve-mips-intel-i915-support-514952.shtml
Back to top
View user's profile Send private message MSN Messenger 
musher0


Joined: 04 Jan 2009
Posts: 11174
Location: Gatineau (Qc), Canada

PostPosted: Sat 22 Apr 2017, 11:40    Post subject:  

That's quite technical.
Isn't there an explanation in "layman's terms" somewhere?

_________________
musher0
~~~~~~~~~~
"Logical entities must not be multiplied beyond necessity." | |
« Il ne faut pas multiplier les entités logiques sans nécessité. » (Ockham)
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1291

PostPosted: Sat 22 Apr 2017, 12:05    Post subject:  

musher0 wrote:
That's quite technical.
Isn't there an explanation in "layman's terms" somewhere?

The problem is that everything in the kernel is technical (and greek to the layman) I think. Laughing
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Thu 27 Apr 2017, 06:44    Post subject:  

So I have recently re-arranged ubuild.sh and forked it to nubuild.sh

The script is much shorter with only one build function which builds x86_64 32-pae and 32-nopae kernels and modules, switching each build arch according to arc variable.

The directory structure is different now with sources and vanilla and patches all in the parent directory. The only remaining sub directories are in dist where the packages are finalised. This makes it easier to navigate and view, and also for locating files etc.

There are no more build.conf files! Also only 3 DOTconfig files for x64 pae nopae, which can be reconfigure internally with 'nubuild.sh' '888' option.

I have not yet added recent improvements from woof-ce>kernel-kit , because sukk-2 seems fine without them for the moment.

Still testing.

EDIT: built 4.10.12 and 4.10.13 successfully.
SUKK-2_April-2017.tar.gz
Description  SUKK-2
gz

 Download 
Filename  SUKK-2_April-2017.tar.gz 
Filesize  119.34 KB 
Downloaded  65 Time(s) 
Back to top
View user's profile Send private message MSN Messenger 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Thu 27 Apr 2017, 21:31    Post subject:  

Oops! Nubuild couldn't build a 3.x kernel. Now it can.
nubuild.sh.gz
Description 
gz

 Download 
Filename  nubuild.sh.gz 
Filesize  23.67 KB 
Downloaded  50 Time(s) 
Back to top
View user's profile Send private message MSN Messenger 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Sun 30 Apr 2017, 06:24    Post subject:  

I was just re-configureing the DOTconfig for x64 and I noticed the option to specify path to files or dirs for the kernel compile to build (in?) the cpio (initrd) with the kernel build.

Code:
CONFIG_INITRAMFS_SOURCE="/initrd/mnt/dev_save/FatHouse/initrd-tree"
Back to top
View user's profile Send private message MSN Messenger 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Sun 30 Apr 2017, 07:55    Post subject:  

I just built a x64 4.10.13 kernel with initrd built in @ 40mb. Works fine.

In my initrd tree there were modules from previous 4.10.13 build which had not been configured fully for my hardware.

I also booted same kernel with external initrd with modules.sfs inside and everything worked fine too.

So it is possible to build the kernel with kernel modules inside the initrd, inside the kernel. As it is possible to specify several directories and/or files for the cpio archive at kernel compile time, it seems possible to also build in the main sfs, probably just need to code initrd init to look for it.

So now we are realistically and easily able to compile a puppy linux distribution as one vmlinuz file.

grub cfg/menu/lst
Code:
kernel vmlinuz
Back to top
View user's profile Send private message MSN Messenger 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Sun 30 Apr 2017, 10:57    Post subject:  

Re-compiled with full compliment of modules and kernel-modules.sfs put in initrd tree; removed initrd from grub.cfg boot entry. Installed new kernel (56MB) and re-booted flawlessly to desktop.
The kernel booted more verbosely.

eth0 is now sit0.


I did tried compiling the main sfs in, but @ 2GB compilation stopped at cpio phase and failed.
should work with a smaller main sfs.
Back to top
View user's profile Send private message MSN Messenger 
LateAdopter

Joined: 27 May 2011
Posts: 275
Location: Reading UK

PostPosted: Sun 30 Apr 2017, 12:43    Post subject:  

stemsee wrote:
The kernel booted more verbosely.

With kernel 4.10 the loglevel is set in DOTconfig and it defaults to 7 when you first save a 4.10 DOTconfig. Previously the kernel kit patched it to 3. This may be the cause of the extra rhubarb when booting.
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Sun 30 Apr 2017, 14:18    Post subject:  

Ahh! Could be Smile

Thanks LatAdopter!
Back to top
View user's profile Send private message MSN Messenger 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Tue 02 May 2017, 07:24    Post subject:  

After some research seems cpio archive is limited to 2GB size, in general.

re-compiled 4.7.1 with fatdog initrd tree, including modules and main sfs, builds successfully but at boot kernel panic!
Any ideas?
Back to top
View user's profile Send private message MSN Messenger 
Dry Falls

Joined: 16 Dec 2014
Posts: 508
Location: Upper Columbia

PostPosted: Sun 11 Jun 2017, 03:24    Post subject:  

stemsee wrote:
After some research seems cpio archive is limited to 2GB size, in general.

re-compiled 4.7.1 with fatdog initrd tree, including modules and main sfs, builds successfully but at boot kernel panic!
Any ideas?


Not many comers to this question. Aside from the verbosity issue, the 64k dotconfig in the new suuk does not support xz compression. Aside from that, I've been playing with a humungous initrd in JL64 and it requires
Code:
rootfstype=ramfs
as in fatdog or
Code:
rootwait rw
as in quirky. A number of smallish sfs files can be in the initrd, but large ones may present a problem. In lighthouse, even if the base file is inside the initrd, a pre-existing base anywhere in the system (top of partition) will be mounted, so pmedia and pdev1 boot parameters are also needed.

Without the rootfs parameter, memory allocation error and kernel panic everytime. >400M initrd and I get "init too big" error or "no working init". Go figure!

df

update: Further testing with humongous initrd in JL64 -- no need for above boot parameters. rootfs in pupstate is automatic (initrd=377M) so I assume that is taken care of by Tazoc's init script. adding only 10M to that gives a "no suitable memory target" error. I think this is a new kernel issue. I notice the fatdog initrd is 344M.
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2000
Location: In The Way

PostPosted: Wed 20 Sep 2017, 06:40    Post subject:  

Kernel-4.12.12 x64 kernel and modules

https://drive.google.com/file/d/0B1gMz4e6lUx3UEYxeFVfRlhSbmc
Back to top
View user's profile Send private message MSN Messenger 
Display posts from previous:   Sort by:   
Page 31 of 32 [467 Posts]   Goto page: Previous 1, 2, 3, ..., 29, 30, 31, 32 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0552s ][ Queries: 15 (0.0091s) ][ GZIP on ]