Kernel build script

Under development: PCMCIA, wireless, etc.
Message
Author
User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#31 Post by Iguleder »

Just compiled linux_kernel-2.6.32-41-lts. Uploading to my repo.

Haven't tested it yet; this one was built on a Debian Wheezy chroot with GCC 4.5.3 and has BFS 404 and a Puppy boot logo for framebuffer consoles.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

User avatar
dejan555
Posts: 2798
Joined: Sun 30 Nov 2008, 11:57
Location: Montenegro
Contact:

#32 Post by dejan555 »

Sounds good Iguleder, I will try to build lts for dpup485, so I see script also downloads kernel and does everything auto.
How much space is required, after devx is loaded, to download and compile/package the kernel?
I get about 700+ MB free RAM when I load devx so I'd compile it in ram if possible
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]

User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#33 Post by Iguleder »

Quite a lot ... I suggest you to have at least 1 GB. The kernel sources are several hundreds of MBs.

I used to do that in RAM on the PC with 2 GB of RAM, but now I do it on the netbook and it has just 1 GB, so I run it on a partition.

By the way - once the upload is over, I'll upload the build scripts. My wireless connection keeps disconnecting so I can't upload the cool stuff in parallel :lol:

btw: the only thing the script doesn't do is the actual package creation. It doesn't run dir2pet and mksquashfs; it just creates the packages in their extracted form.

btw II: you can use a chroot environment to run the script. This one (the .41) was built in a Debian Wheezy chroot environment with GCC 4.5.3, with Debian's goodness atop - the result is a 2 MB smaller package, compared to the .40 I built under 5.2.5. However, this kernel has been around for a long time, so you should use either 4.4.x or 4.5.x with it ... 4.6.0 has regressions and there is a possibility the kernel won't build with it.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

User avatar
dejan555
Posts: 2798
Joined: Sun 30 Nov 2008, 11:57
Location: Montenegro
Contact:

#34 Post by dejan555 »

Haven't used chroot enviroments yet. Could it be compiled with dpup's devx?
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]

User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#35 Post by Iguleder »

Yep, of course. Doing it the chroot just makes it ... more geeky :p

Btw - I uploaded the build script with all patches, etc' - here.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

User avatar
dejan555
Posts: 2798
Joined: Sun 30 Nov 2008, 11:57
Location: Montenegro
Contact:

#36 Post by dejan555 »

Ok, cool I tried your latest script and built kernel - works like a charm.
Booted in ram and loaded devx, then ran build.sh from partition.

Afterwards I replaced vmlinuz, unpack/resquashed initrd.gz and sfs with new modules and it booted OK.
I had to manually modprobe PS/2 mouse to work though :?
What could be the problem there, I tried adding input drivers including psmouse.ko to initrd.gz but it wouldn't work on boot anyway.
Net, sound and video modules work ok as well as usb mouse, just PS/2 mouse remains frozen.
I can add modprobe psmouse line to some of rc scripts maybe?
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]

User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#37 Post by Iguleder »

I think I saw some line which says that Barry made that module built-in since some kernel.

Do a diff between your rc.sysint or the initramfs' init to see the difference. I'm almost certain you need that line for kernel older than some kernel, I think it was the 4.3.1 one.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#38 Post by Iguleder »

Just built linux_kernel-2.6.32-42-lts; uploading it right now. I haven't tested it yet but it should work ... like the previous ones :D

The directory contains the sources (plus patches, Aufs, etc'), the kernel package, the kernel headers package, the kernel sources SFS and the build script. Have fun :)

There's also a build log, for the skeptic :lol:
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#39 Post by sc0ttman »

Could your kernel build scripts be added to your Pur-tools thing?
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#40 Post by Iguleder »

Theoretically, yes - but it's a very bad idea, for two reasons:
1) You can't install a kernel in Puppy, you'll have to remaster or rebuild your Puppy for that.
2) The kernel is a very sensitive component - it deserves its own build system.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#41 Post by sc0ttman »

Iguleder wrote:Theoretically, yes - but it's a very bad idea, for two reasons:
1) You can't install a kernel in Puppy, you'll have to remaster or rebuild your Puppy for that.
2) The kernel is a very sensitive component - it deserves its own build system.
I thought it would be wrong to put it in there, as its not installable in the same way as the pther packages, just wondered.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
Lothar
Posts: 15
Joined: Thu 02 Jun 2011, 09:01

#42 Post by Lothar »

Hey Iguleder and Pemasu,

I emailed J R Okajima (the man behind Aufs) in regard to the aufs-allow-sfs patch, and he wanted me to ask:

"Would you try aufs without the aufs-allow-sfs patch? I think it should work since July last year."

User avatar
Iguleder
Posts: 2026
Joined: Tue 11 Aug 2009, 09:36
Location: Israel, somewhere in the beautiful desert
Contact:

#43 Post by Iguleder »

If it works, don't touch it :lol:

All Puppy's kernels are built with this patch and work just fine, and I don't want to do all the testing that follows its removal. It causes zero issues, so I see no problem with using it.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]

Post Reply