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 Tue 18 Sep 2018, 21:55
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Compiling
Kernel Compiling - Kernel-kit
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 3 [40 Posts]   Goto page: Previous 1, 2, 3
Author Message
moeppyfan


Joined: 11 Feb 2016
Posts: 48

PostPosted: Sat 19 Mar 2016, 07:56    Post subject:  

peebee wrote:
all-firmware arises from .pets included in the woof-ce build and resides in the puppy_*.sfs not in the zdrv.....

Thanks peebee. That's good to know. Also found some excellent tips to get ndiswrapper working again! Very Happy
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3464
Location: Worcestershire, UK

PostPosted: Sat 19 Mar 2016, 08:14    Post subject:  

moeppyfan wrote:
peebee wrote:
all-firmware arises from .pets included in the woof-ce build and resides in the puppy_*.sfs not in the zdrv.....

Thanks peebee. That's good to know. Also found some excellent tips to get ndiswrapper working again! Very Happy

Yes - any "non-kernel" drivers have to be recompiled for a new kernel - includes ndiswrapper, broadcom wl, nvidia and other proprietary video drivers....etc.

Encourage you to upload your new kernel somewhere and put a link on:
http://www.murga-linux.com/puppy/viewtopic.php?t=106084

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
slavvo67

Joined: 12 Oct 2012
Posts: 1570
Location: The other Mr. 305

PostPosted: Sat 27 Aug 2016, 14:50    Post subject:  

Is this still being supported, tested? Just wondering before I jump in and spend a bunch of time, here.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 3464
Location: Worcestershire, UK

PostPosted: Sat 27 Aug 2016, 15:59    Post subject:  

slavvo67 wrote:
Is this still being supported, tested? Just wondering before I jump in and spend a bunch of time, here.

Short answer - yes

Longer answer - kernel kit is now a part of woof-ce and is therefore held on github from where you can download woof-ce including kernel-kit

https://github.com/puppylinux-woof-CE/woof-CE/tree/testing/kernel-kit

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
oldyeller


Joined: 15 Nov 2011
Posts: 888
Location: Alaska

PostPosted: Fri 18 Nov 2016, 21:40    Post subject:  

Hello,

I have finally complied a kernel Laughing Laughing after all the puppies i did. Out of all the folders I have now which ones do I make the pet from?

Any help would be great Thanks
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1540

PostPosted: Wed 24 Jan 2018, 10:23    Post subject:  

Just out of curiosity, is there any way to upgrade a kernel using this? Say I make 4.4.112 with kernel-kit, then I want to make 4.4.113, and all the files compiled in the linux-4.4.112 folder are still there. My strategy so far is just to restart clean every time the 3.18, 4.1, 4.4, etc. branches have a new point update, which I've done probably at least 30 times now, which takes around 3-4 hours to compile on my laptop each time, so I usually start it up, go out for the day, then when I come back when it's usually done. I didn't see anything in the readme about this, so guessing it might be a complex thing to add, and might end up being buggy, though when I edit a few files in an IDE then recompile it seems to magically know which files it need to recompile, which is infinitely faster than doing Build All for each small change and probably healthier on the CPU and hard drive. Something like "if selected 4.4.113 and 4.4.x is already there, don't delete the compiled files, just replace the new files over the old ones". Does this sound like a practical feature to add, or just a daunting PITA? Laughing My impression is that cp -u only copies files that are newer, so maybe I could just add a line to stop kernel-kit at this point and try it manually to see if it only compiles the new files after...

edit: hmmm yes, I guess I can move the linux-4.4.112 directory somewhere else before starting build.sh again, then when it stops before "Compiling the Kernel" I can copy all the o files from the linux-4.4.112 directory into the linux-4.4.113 directory...
Back to top
View user's profile Send private message 
Hesse James


Joined: 08 Feb 2010
Posts: 78

PostPosted: Thu 25 Jan 2018, 16:38    Post subject: Kernel 4.9.77 with RETPOLINE active for Xenial64  

Hello
I expect that you have heard about the recent vulnerabilities of most of the actual CPU's. These vulnerabilities are known as Meltdown and Spectre. I think this picture about these vulverabilities exaggerates a bit
but the threat should not be underestimated (picture stems from an article in ct about Spectre/Meltdown).



A mitigation (RETPOLINE) was shipped with the actual kernel 4.9.77. As a negative effect it might reduce the CPU-perfomance for about 5 %.
To evaluate the effect I compiled this kernel for Xenial64. These are the additional kernel parameters that are part of the base settings of 4.9.77 compared to 4.9.58:

# Linux/x86 4.9.77 Kernel Configuration
CONFIG_RETPOLINE=y
CONFIG_GENERIC_CPU_VULNERABILITIES=y
CONFIG_KEYS_COMPAT=y
CONFIG_PAGE_TABLE_ISOLATION=y

After changing the kernel I used HARDINFO to determine the CPU performance with the Xenial64 7.5 Standard-Kernel 4.9.58, the 4.9.77 without and with RETPOLINE activated.
According to the literature RETPOLINE should reduce the performance significantly.

______________________________________________Kernel 4.9.58________Kernel 4.9.77 no retpoline___Kernel 4.9.77 with retpoline

CPU Blowfish (lower is better)______This Machine___3581 MHz__2.025____ 3300 MHz__1.986_________3300 MHz__1.997
CPU CryptoHash (higher is better)__This Machine___3581 MHz__717.230___3300 MHz__781.685_______3300 MHz__755.834
CPU Fibonacci (lower is better)_____This Machine___3581 MHz__0.289_____3300 MHz__0.291_________3300 MHz__0.294
CPU N-Queens (lower is better)____This Machine___3581 MHz__7.153_____3300 MHz__6.935_________3300 MHz__7.236

According to these results I see only a performance reduction for N-QUEENS and CryptoHash. For some reasons the K4.9.58 doesn't determine the CPU frequency correctly.
If you are interested in testing and protecting your machine against the vulverability you can download here my compiled kernel with all necessary files including the used .config file.

Update !
http://www.mediafire.com/file/h1ys05ddq2i30d5/kernel-4.9.124_Xenial64.tar.gz

Christian

P.S. These are the configuration differences between the standard kernel .config 4.9.58 and 4.9.124:
CONFIG_RETPOLINE=y
CONFIG_GENERIC_CPU_VULNERABILITIES=y
CONFIG_PAGE_TABLE_ISOLATION=y
CONFIG_HOTPLUG_SMT=y
Back to top
View user's profile Send private message 
rockedge


Joined: 11 Apr 2012
Posts: 797
Location: Connecticut, United States

PostPosted: Thu 06 Sep 2018, 08:24    Post subject:  

I am attempting to compile a 4.14.63 RT kernel using the aufs=4.14.56+ and the RT-patches-4.14.63....but have a compiling failure about half way through the compile itself.

Code:
UPupBB 18.05 [i686]
gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0
git version 2.17.1
mksquashfs version 4.3 (2014/05/12)


Jobs for make: 2
kernel_version=4.14.63
kernel_version_info=
Linux: 4.14.63
aufs=4.14.56+
the build.log ends with
Code:
CC [M]  net/wireless/ap.o
  CC [M]  net/wireless/trace.o
  CC [M]  net/wireless/ocb.o
  CC [M]  net/wireless/debugfs.o
  CC [M]  net/wireless/wext-compat.o
  CC [M]  net/wireless/wext-sme.o
  CC [M]  net/wireless/lib80211.o
  CC [M]  net/wireless/lib80211_crypt_wep.o
  CC [M]  net/wireless/lib80211_crypt_ccmp.o
  CC [M]  net/wireless/lib80211_crypt_tkip.o
  AR      net/wireless/built-in.o
  LD [M]  net/wireless/cfg80211.o
  AR      net/built-in.o
Error: failed to compile the kernel sources
.

I have tried 7 different variations but I am missing something that is causing the failure...anyone have any ideas to throw into the mix?

copy of the complete log...it is a compressed zip file
build.log.zip
Description 
zip

 Download 
Filename  build.log.zip 
Filesize  46.02 KB 
Downloaded  10 Time(s) 
Back to top
View user's profile Send private message Visit poster's website 
peebee


Joined: 21 Sep 2008
Posts: 3464
Location: Worcestershire, UK

PostPosted: Thu 06 Sep 2018, 13:06    Post subject:  

the error is at line 6231 in the log:

CC [M] drivers/hv/vmbus_drv.o
drivers/hv/vmbus_drv.c: In function ‘vmbus_isr’:
drivers/hv/vmbus_drv.c:969:25: error: implicit declaration of function ‘get_irq_regs’; did you mean ‘get_mm_rss’? [-Werror=implicit-function-declaration]
struct pt_regs *regs = get_irq_regs();
^~~~~~~~~~~~
get_mm_rss
drivers/hv/vmbus_drv.c:969:25: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
scripts/Makefile.build:328: recipe for target 'drivers/hv/vmbus_drv.o' failed
make[2]: *** [drivers/hv/vmbus_drv.o] Error 1
scripts/Makefile.build:587: recipe for target 'drivers/hv' failed
make[1]: *** [drivers/hv] Error 2
Makefile:1035: recipe for target 'drivers' failed
make: *** [drivers] Error 2

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
rockedge


Joined: 11 Apr 2012
Posts: 797
Location: Connecticut, United States

PostPosted: Fri 07 Sep 2018, 09:13    Post subject:  

Thank you peebee!!!! I looked closer at that error and found a fix.
here : https://www.spinics.net/lists/linux-rt-users/msg19382.html

this involved fixing drivers/hv/vmbus_drv.c by adding the line
Code:
#include <asm/irq_regs.h>


this resulted in a Successful compile of a real time kernel! 4.14.63-rt37 PAE 32bit
I am about to use woof -CE to build a Tahr with this kernel.

log output :
Code:
------------------
Output files:
- output/huge-4.14.63-upupbb.tar.bz2
  (kernel tarball: vmlinuz, modules.sfs - used in the woof process)
  you can use this to replace vmlinuz and zdrv.sfs from the current wce puppy install..

- output/kernel_sources-4.14.63-upupbb.sfs
  (you can use this to compile new kernel modules - load or install first..)
------------------

Included here is a DOT config file for anyone who would like to compile a similar kernel. Remove the .gz extension.

Here is the download link for the kernel 4.14.63-rt37
http://rockedge.org/kernels

again thank you peebee for the insight!
DOTconfig-4.14.63-x86-060918.gz
Description 
gz

 Download 
Filename  DOTconfig-4.14.63-x86-060918.gz 
Filesize  170.37 KB 
Downloaded  2 Time(s) 
build.log.zip
Description 
zip

 Download 
Filename  build.log.zip 
Filesize  126.22 KB 
Downloaded  2 Time(s) 
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 3 of 3 [40 Posts]   Goto page: Previous 1, 2, 3
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Compiling
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.0604s ][ Queries: 14 (0.0135s) ][ GZIP on ]