kernel compiling in woof-ce
sukk-0.9
one bug fix and some small changes.
one bug fix and some small changes.
- Attachments
-
- sukk-0.9.tar.gz
- (114.72 KiB) Downloaded 249 times
stemsee wrote:sukk-0.9
one bug fix and some small changes.
Code: Select all
...Extracting the Aufs sources
Extracting the kernel sources
Adding Aufs to the kernel sources
Resetting the minor version number
Reducing the verbosity level
Applying ../patches/*
./ubuild.sh: line 312: ../patches/*: No such file or directory
Error: failed to apply ../patches/* on the kernel sources.
<root> /initrd/mnt/dev_save/Downloads/sukk-0.9/sukk-0.9
bash-4.2#
DOTconfig
I
think I'm starting to get the hang of your build system. I merged the
/proc/config.gz from fathouse-retro and JL64 under 3.18.5 for a new
DOTconfig-64, edited build64 and version patch to suit and dropped into
Dist/sources the k3.18,8 package & aufs with Sukk.8. Everything went
well, and the new kernel, modules and sources popped out in about 56
minutes.
Still won't run chromium-sandbox. I thought it might be in the memory
allocation, but not (chrome puts everything you've been doing into the
swap drive and proceeds to fill your memory till it's used to the point
of snapping). Still searching through 6,000 lines to find the
difference (why it works right out of the box with fathouse k3.16.2, but
not any of the newer kernels I've compiled with your builds.
I'd stay with k3.16.2 but there's a lot it won't do or gets wrong, and
that won't do.
Thanks,
df
ps., it's not that I want the fancy browser, but a lot of folks do, and
I'm not going to be the one who tells them they can't! Hell, I've
already done three impossible things this morning.
And in case anyone's interested, here is the customized config for k3.18.8:
think I'm starting to get the hang of your build system. I merged the
/proc/config.gz from fathouse-retro and JL64 under 3.18.5 for a new
DOTconfig-64, edited build64 and version patch to suit and dropped into
Dist/sources the k3.18,8 package & aufs with Sukk.8. Everything went
well, and the new kernel, modules and sources popped out in about 56
minutes.
Still won't run chromium-sandbox. I thought it might be in the memory
allocation, but not (chrome puts everything you've been doing into the
swap drive and proceeds to fill your memory till it's used to the point
of snapping). Still searching through 6,000 lines to find the
difference (why it works right out of the box with fathouse k3.16.2, but
not any of the newer kernels I've compiled with your builds.
I'd stay with k3.16.2 but there's a lot it won't do or gets wrong, and
that won't do.
Thanks,
df
ps., it's not that I want the fancy browser, but a lot of folks do, and
I'm not going to be the one who tells them they can't! Hell, I've
already done three impossible things this morning.
And in case anyone's interested, here is the customized config for k3.18.8:
- Attachments
-
- config.gz
- (34.59 KiB) Downloaded 213 times
fixed?
I think I've fixed it, starting with line 209:
[/code]
Code: Select all
CONFIG_BPF_SYSCALL=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
- Attachments
-
- DOTconfig.gz
- (34.96 KiB) Downloaded 263 times
Excellent stuff! So now chrome works properly, right? I have been trying to incorporate popcorn into my own distro, and even trying to upgrade the kernel in Chromecastpup-v3 but chrome always has problems and popcorn depends on chrome (apparently).
So I will change that for all configs and release sukk-1.0 after testing.
So I will change that for all configs and release sukk-1.0 after testing.
sukk-1.0 with DryFalls config edits, small bug fix for aufs download file.
- Attachments
-
- sukk-1.0.tar.gz
- (115.21 KiB) Downloaded 269 times
Thanks Stemsee. This link Diseased Newt might explain why syscall/bpf is the key. syscall has to be enabled. Peebee directed me (thanks, Peebe) to the kernel/modules for the fatdog700 final (k3.18.7) which he used in the upgrade of LxPup64 from 14 to 15. Well, it runs lighthouse tolerably well even though I've yet to get fd700 to boot on this machine since the change from k3.16.2 (although virtual machine will boot it!). That is how I extracted the file to compare to my config from JL64-3.18.8. Unfortunately, their config file won't recompile in your kit because of a check built in to detect changes (as near as I can tell) and terminate the compile if found. Seems kind of proprietary to me, but that's just me. Anyway, while the new compile works well in lighthouse, I couldn't guarantee it will work with other distros. For example, I couldn't get LxPup64-14 to boot with it, so please be for-warned. It may not generalize. I'm going to try it in fatdog and see if it will finally boot to a desktop, but at the moment it's not a big priority.
df
df
Well, your discovery has solved my chrome and popcorn problems. I have updated Chromecastpup-v3 to 3.19.2-64bit kernel.
NOTE BENE: I had to install the modules with headers to the savefile in order for them to load on boot!! They would not load as an zdrv_*_.sfs !!
So now I will remaster with modules 'in' after deleting old modules.
NOTE BENE: I had to install the modules with headers to the savefile in order for them to load on boot!! They would not load as an zdrv_*_.sfs !!
So now I will remaster with modules 'in' after deleting old modules.
Hi stemsee
Encryption keys are needed to download......
Thanks
PeeBee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Hi Peebee
3.19.2-64
https://mega.co.nz/#F!9IBCiA6C!w8Q0-dcgw7J-B9iVfvS4gA
3.19.2-pae
https://mega.co.nz/#F!9IBCiA6C!w8Q0-dcgw7J-B9iVfvS4gA
3.19.2-64
https://mega.co.nz/#F!9IBCiA6C!w8Q0-dcgw7J-B9iVfvS4gA
3.19.2-pae
https://mega.co.nz/#F!9IBCiA6C!w8Q0-dcgw7J-B9iVfvS4gA
Flummoxed but pleasantly surprised
Hi stemseestemsee wrote:Hi Peebee
3.19.2-64
https://mega.co.nz/#F!9IBCiA6C!w8Q0-dcgw7J-B9iVfvS4gA
3.19.2-pae
https://mega.co.nz/#F!9IBCiA6C!w8Q0-dcgw7J-B9iVfvS4gA
Thanks - but those links are the same - and lead to the 64 bit kernel
I downloaded it (thinking it was the pae version) and put it into a 32-bit LxPup15.03-pae install. It was only when I did some pup-sysinfo checks that I realised that I had a 64-bit kernel.
It all worked successfully which is great but now I'm really confused as I ended up with a 64-bit kernel and a 32-bit system which logic tells me shouldn't have worked. Can a 64-bit kernel run 32-bit programs???
Everything I tried worked - including adding a 32-bit sfs of Chromium.
Is there any need for the pae version if the 64-bit runs 32-bit with no problems?????
My laptop only has 4GB of ram - would a mixed 64/32 system support >4GB?
Looking forward to some enlightenment!
Cheers
peebee
p.s. any chance of kernel sources so that I can try compiling drivers?
p.p.s then tried the 64-bit kernel with LxPup64-15.03 and of course that worked OK as well.
- Attachments
-
- Screenshot.png
- (94.14 KiB) Downloaded 421 times
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
pae
https://mega.co.nz/#!oFhBjQRK!ULW5BbK6M ... 6oA5iqba3Q
fingers crossed
64bit with ia32 enabled in config runs all 64 and 32 bit programs when libraries are available. Aslo qemu will let you run 64 bit iso on 32bit system with 64bit kernel.
64bit kernel will recognize and use ram upto 64gb (i think) pae will use ram differently ... jamesbond says it is better to use a 64bit kernel over a pae kernel.
If compiling for 32 bit using 64bit kernel then you must specify arch as 32bit in configure.
https://mega.co.nz/#!oFhBjQRK!ULW5BbK6M ... 6oA5iqba3Q
fingers crossed
64bit with ia32 enabled in config runs all 64 and 32 bit programs when libraries are available. Aslo qemu will let you run 64 bit iso on 32bit system with 64bit kernel.
64bit kernel will recognize and use ram upto 64gb (i think) pae will use ram differently ... jamesbond says it is better to use a 64bit kernel over a pae kernel.
If compiling for 32 bit using 64bit kernel then you must specify arch as 32bit in configure.
SUKK-1.0
I think it's done, and I'm keeping it! Sukk1.0 jut flew through its thing and produced a really nice kernel package. 3.19.2 runs things really well, and from the looks of things, deals better with f2fs (although personally, I'm sticking with EXT4).
All I did to interfere was rebuild the kernel modules to include kernel headers. Even so, Edit-SFS (parallel mksquash using 4 processors) compressed the new file down from 44 to 39M. Kernel sources compressed from 106 to 91M.
Great job. I'm going to write a batch file to start up Sukk1.0 and include it in JL64, if that's alright.
df
All I did to interfere was rebuild the kernel modules to include kernel headers. Even so, Edit-SFS (parallel mksquash using 4 processors) compressed the new file down from 44 to 39M. Kernel sources compressed from 106 to 91M.
Great job. I'm going to write a batch file to start up Sukk1.0 and include it in JL64, if that's alright.
df
Sukk-1.0 is good for single kernel builds at-a-time but not auto consecutive builds. So here is sukk-1.1 and if you haven't got time to waste don't download it yet.
I realised that variable '$arch' was being reused ... Oops! (frickin amateur!)
Also solved consecutive building. And added menu item '888' reconfigure DOTconfigs then build 64 bit kernel. And tidied up a bit.
As usual , I release it first and test it later! Because I am not properly trained!! Not because I want to sabotage your own efforts. I'm just eager to get it out there.
But I will set it to build 3.19.3, 64, pae and nonpae kernels tonight. Should take about 3 hours.
To do :-
1 Add 4.0-rc* handling
2 Add remove non-system specific modules.
I realised that variable '$arch' was being reused ... Oops! (frickin amateur!)
Also solved consecutive building. And added menu item '888' reconfigure DOTconfigs then build 64 bit kernel. And tidied up a bit.
As usual , I release it first and test it later! Because I am not properly trained!! Not because I want to sabotage your own efforts. I'm just eager to get it out there.
But I will set it to build 3.19.3, 64, pae and nonpae kernels tonight. Should take about 3 hours.
To do :-
1 Add 4.0-rc* handling
2 Add remove non-system specific modules.
- Attachments
-
- sukk-1.1.tar.gz
- (114.87 KiB) Downloaded 220 times