Superseded. If you still want to try it, is in Kernel Archive: https://archive.org/download/Puppy_Linux_Huge-Kernels
6.6.8 64bit Knl - superseded
Moderator: Forum moderators
Re: 6.6.8 64bit NON-USRMERGE Kernel Aufs/Overlayfs
Happy New Year @ozsouth
I thought I would get round to updating my kernel as I wanted to compile/build WireGuard VPN.
I did check beforehand and my understanding is that this has been included in the kernel.
When I attempt to compile the application I did receive an error message
Contained within the source directory there are kernel-tree-scripts (contents shown).
I am unsure as if these needed to be included in the building of the kernel or can be run retrospectively?
Any ideas/suggestions would be welcome
EDIT
There is an additional component of the application which does compile
-
- Posts: 1571
- Joined: Sun Jul 12, 2020 2:38 am
- Location: S.E. Australia
- Has thanked: 242 times
- Been thanked: 706 times
Re: 6.6.8 64bit NON-USRMERGE Kernel Aufs/Overlayfs
@Jasper - HNY 2U2.
My kernel 6.6.8 has the 5 essential items already, but not wireguard_debug (non-essential).
You can check what is compiled in via the /boot/config-6.6.8 ... file. All 4 'Kernel Requirements' (below) are builtin.
However, I compiled wireguard as a loadable module, not as builtin. So you need to run (in a terminal): modprobe wireguard
You could put that in a /root/Startup script. Hence recompiling is unnecessary.
From Wireguard site, for info only:
Kernel Requirements
WireGuard requires Linux ≥3.10, with the following configuration options, which are likely already configured in your kernel, especially if you're installing via distribution packages.
CONFIG_NET for basic networking support
CONFIG_INET for basic IP support
CONFIG_NET_UDP_TUNNEL for sending and receiving UDP packets
CONFIG_CRYPTO_ALGAPI for crypto_xor
Some, but not all, of these options directly correspond to menuconfig entries. The ones that do not correspond directly correspond to options that imply them. For enabling the above options, select these items in menuconfig:
[] Networking support (NET) -->
Networking options -->
[*] TCP/IP networking (INET)
[] IP: Foo (IP protocols) over UDP (NET_FOU)
[*] Cryptographic API (CRYPTO) -->
[*] Cryptographic algorithm manager (CRYPTO_MANAGER)
Then you will be able to configure these options directly:
CONFIG_WIREGUARD controls whether WireGuard is built as a module, as built-in, or not at all
CONFIG_WIREGUARD_DEBUG turns on verbose debug messages
These are selectable easily via menuconfig, if CONFIG_NET and CONFIG_INET are also selected:
[] Networking support -->
Networking options -->
[*] TCP/IP networking
[*] IP: WireGuard secure network tunnel
[ ] Debugging checks and verbose messages
Re: 6.6.8 64bit NON-USRMERGE Kernel Aufs/Overlayfs
@ozsouth
I have generated my private/pubic keys and set my IP address to be used.
The only missing step is creating a config file. Cannot seem to see where this is located atm. Will have to read the documentation and not charge in like the infantry.
It looks promising though
- mikewalsh
- Moderator
- Posts: 6167
- Joined: Tue Dec 03, 2019 1:40 pm
- Location: King's Lynn, UK
- Has thanked: 798 times
- Been thanked: 1987 times
Re: 6.6.8 64bit NON-USRMERGE Kernel Aufs/Overlayfs
@ozsouth :-
Thought I'd give this an outing, mate. I don't have as many Puppies running the official Nvidia drivers now - more running on just nouveau - which gives me somewhat more freedom to try out newer kernels. Working Nvidia drivers mean that I tend to leave that system alone, because even with shinobar's excellent utility I couldn't be arsed to keep repeating the process, IF I was to update kernels regularly!
I'm trialling this in my re-built Xenialpup64 ATM (was using k5.4.53 till this afternoon), also using Busterpup's glibc 2.28 (up from the original 2.23). Been here since around 3 pm - 8 hours ago - and, touch wood, all is serene and running like clockwork. Also using the supplied fdrv, and haven't found owt "missing" yet. Partly, I'm curious to see if the recently open-sourced code Nvidia has been drip-feeding into the kernel this last few months is making any real difference. It does seem smoother, if I'm honest.
Nice work!
(I'll run it for a couple more days; if I'm still happy, I'll perform a transplant on jrb's 'lite' spin of BK's old Quirky64 'April' 701. This has also been running Fossa's k5.4.53 for several months, and has been perfectly content with the jump from 3- to 5-series. I suspect it'll be happy with this one, too.)
Mike.