Custom kernel (linuxNN-vd)

I’m in the process of migrating my custom kernel to Arch/EOS, currently, this is 5.8-rc.
As Manjaro uses a custom mkinitcpio, some changes to the PKGBUILD were necessary.

However, I left Manjaro’s extramodules handling in place.

From what I can tell, EOS doesn’t use extramodules, and relies on dkms for out-of-tree modules, is that correct?

If you want to have a look at it, and maybe even compile and install it, here you go:

(Note: it still says “for Manjaro”, haven’t updated that part yet)
(Note 2: virtualbox host modules do not work yet with 5.8)

Any sort of feedback is welcome!

6 Likes

Apart from any modules included in the Arch repos, yes.

2 Likes

I really think you should reconsider the name for your kernel. :wink:

3 Likes

linuxNN-tp ?

graysky’s CPU optimisations

What are those btw, can you expand a little? :slight_smile:

I think it’s these:

2 Likes

Just tested this with acpi_call module.

Both dkms and extramodule work correctly.
However dkms does not work if the kernel is compiled with Clang, but this is a known problem: CC=clang has to be passed to make in dkms.conf.

So it seems that both ways are possible, which is good news :slight_smile:


@jonathon: correct.


Why? :slight_smile:

2 Likes

Uhh…because in many English speaking countries, vd has this meaning. :thinking:

5 Likes

That is probably the last thing that comes to my mind when I think of ‘vd’…
Actually never heard of that term, despite having watched all of House MD :slight_smile:

(Hint: it stands for ‘Victor Development’, quite cheesy isn’t it?)

3 Likes

:rofl:

Also it can potentially be spread and adopted as fast as vd, which should be good! :laughing:

P.S. @dalto Haven’t seen this one coming too

3 Likes

vd is rather an old term, the new term is STD So don’t use that one either.

This is starting to sound like a class I took in high school. :hear_no_evil:
Just for historic reference, I graduated from high school in 1968. Yah, hippies, Vietnam War, Timothy Leary, and a lot of other weird stuff.


Pudge

3 Likes

What does the Z stand for in ZSTD? :exploding_head:

2 Likes

Zuckerberg ? :laughing:

3 Likes

Now that’s funny!

Seriously, knowing it’s facebook standard…you just can’t make that up! :laughing:

I think i need to check up on doctor, just as you guys, i have about 1000 zstd packages on my system now, not looking good :rofl:

Of course they unpack and transmit on your system very fast, but i’m not sure i’m fan of Zuckerberg’s std :rofl:

1 Like

Given that this kernel supports ZSTD kernel and initram compression, I’d be very careful… :sweat_smile:

1 Like
std::cout << "That explains a lot." << std::endl;

Compiled and packaged 5.8.0-3 on my GL702ZC, when I install I hit:

(4/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux58-vd.preset: 'default'
  -> -k /boot/vmlinuz-linux58-vd -c /etc/mkinitcpio.conf -g /boot/initramfs-linux58-vd.img -z zstd
==> Starting build: 5.8.0-vd-3
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [sd-vconsole]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux58-vd.img
Incorrect parameters 
Usage : 
      zstd [args] [FILE(s)] [-o file] 

FILE    : a filename 
          with no FILE, or when FILE is - , read standard input
Arguments : 
 -#     : # compression level (1-19, default: 3) 
 -d     : decompression 
 -D DICT: use DICT as Dictionary for compression or decompression 
 -o file: result stored into `file` (only 1 output file) 
 -f     : overwrite output without prompting, also (de)compress links 
--rm    : remove source file(s) after successful de/compression 
 -k     : preserve source file(s) (default) 
 -h/-H  : display help/long help and exit 
bsdtar: Write error
bsdtar: Write error
==> ERROR: Image generation FAILED: bsdtar (step 1) reported an error

Used the generic x86_64.config and skipped nconfig.

I have this in my mkinitcpio.conf:

MODULES=(xxhash crc32c amdgpu lz4 lz4_compress)
...
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
COMPRESSION_OPTIONS=(-12 --favor-decSpeed)

see this

may be missing patches zstd and also update mkinitcpio.conf
if you want use zstd

$ pacman -Qs zstd
local/lib32-zstd 1.4.5-1
    Zstandard - Fast real-time compression algorithm (32-bit)
local/zstd 1.4.5-1
    Zstandard - Fast real-time compression algorithm

?