Kernel 4.15.0-antix.1

[Moderator caprea]

Tried today the 4.15.0-antix.1-kernel to build against the nvidia-driver 384.111 from backports(installed with ddm-mx), broadcam-sta, ndiswrapper, virtualbox-guest

All four of them missed libelf-dev on antix17

DKMS make.log for nvidia-current-384.111 for kernel 4.15.0-antix.1-amd64-smp (x86_64)
Sa 10. Feb 11:05:12 CET 2018
make  KBUILD_VERBOSE=1 -C /lib/modules/4.15.0-antix.1-amd64-smp/build M=/var/lib/dkms/nvidia-current/384.111/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.15.0-antix.1-amd64-smp/build NV_KERNEL_OUTPUT=/lib/modules/4.15.0-antix.1-amd64-smp/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video Q= modules
make[1]: Verzeichnis „/usr/src/linux-headers-4.15.0-antix.1-amd64-smp“ wird betreten
Makefile:932: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Schluss.
make[1]: Verzeichnis „/usr/src/linux-headers-4.15.0-antix.1-amd64-smp“ wird verlassen
Makefile:81: die Regel für Ziel „modules“ scheiterte
make: *** [modules] Fehler 2

DKMS make.log for broadcom-sta-6.30.223.271 for kernel 4.15.0-antix.1-amd64-smp (x86_64)
Sa 10. Feb 11:05:08 CET 2018
/bin/sh: 1: [: Illegal number: 
/bin/sh: 1: [: Illegal number: 
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
KBUILD_NOPEDANTIC=1 make -C /lib/modules/4.15.0-antix.1-amd64-smp/build M=<code>pwd</code>
make[1]: Warnung: Kein Jobserver verfügbar: -j1 wird gesetzt. Fügen Sie der Ursprungsregel
„+“ hinzu.
make[1]: Verzeichnis „/usr/src/linux-headers-4.15.0-antix.1-amd64-smp“ wird betreten
Makefile:932: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Schluss.
make[1]: Verzeichnis „/usr/src/linux-headers-4.15.0-antix.1-amd64-smp“ wird verlassen
Makefile:177: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2

and so on

So I installed libelf-dev

For the nvidia-driver this was enough, afterwards it built perfectly.

For virtualbox-guest I had to install the 5.26 from the MX 17 test repo, this also builds perfectly.

broadcam-sta and ndiswrapper didn’t build.

$ dkms status
broadcom-sta, 6.30.223.271, 4.10.5-antix.3-amd64-smp, x86_64: installed
broadcom-sta, 6.30.223.271, 4.14.14-antix.1-amd64-smp, x86_64: installed
ndiswrapper, 1.61, 4.10.5-antix.3-amd64-smp, x86_64: installed
ndiswrapper, 1.61, 4.14.14-antix.1-amd64-smp, x86_64: installed
nvidia-current, 384.111, 4.14.14-antix.1-amd64-smp, x86_64: installed
nvidia-current, 384.111, 4.15.0-antix.1-amd64-smp, x86_64: installed
virtualbox-guest, 5.2.6, 4.14.14-antix.1-amd64-smp, x86_64: installed
virtualbox-guest, 5.2.6, 4.15.0-antix.1-amd64-smp, x86_64: installed (original_module exists)
helga@antix1:~

$ inxi -Fxz
System:    Host: antix1 Kernel: 4.15.0-antix.1-amd64-smp x86_64 bits: 64 gcc: 6.3.0
           Desktop: IceWM 1.4.2 Distro: antiX-17_x64-full Heather Heyer 24 October 2017
Machine:   Device: desktop Mobo: Gigabyte model: B85M-HD3 v: x.x serial: N/A
           BIOS: American Megatrends v: F12 date: 08/13/2015
CPU:       Quad core Intel Core i5-4430 (-MCP-) arch: Haswell rev.3 cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 23945
           clock speeds: max: 3200 MHz 1: 1306 MHz 2: 1109 MHz 3: 1241 MHz 4: 1296 MHz
Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           bus-ID: 00:02.0
           Card-2: NVIDIA GM206 [GeForce GTX 960] bus-ID: 01:00.0
           Display Server: X.Org 1.19.2 driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GTX 960/PCIe/SSE2
           version: 4.5.0 NVIDIA 384.111 Direct Render: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Def. Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Card-3 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.15.0-antix.1-amd64-smp
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 03:00.0
           IF: eth0 state: down mac: <filter>
           Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter
           driver: ath9k bus-ID: 06:00.0
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 1256.3GB (0.4% used)
           ID-1: /dev/sda model: TS256GSSD370 size: 256.1GB
           ID-2: /dev/sdb model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 29G used: 4.7G (18%) fs: ext4 dev: /dev/sda4
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:31C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 158 Uptime: 27 min Memory: 537.6/7864.4MB
           Init: SysVinit runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121) inxi: 2.3.54 
helga@antix1:~

Well, I dont need ndiswrapper or broadcam-sta.

Without libelf-dev neither the nvidia-driver nor the virtualbox-guest could have been builded against 4.15-kernel.Until now running fine, thanks.

• This topic was modified 5 years, 2 months ago by caprea.
• This topic was modified 5 years, 2 months ago by caprea.

[Anonymous]

Helpful

Up

0

::

😉 and, that’s the security status this kernel of today.

[Member entropyfoe]

Helpful

Up

0

::

Wow, great work getting that all sorted out.

As for the security, I thought 4.15 had all the spectre patches baked in.
Was there some other required fix,, like using gcc 7.3.3 or some such number?

Linus delayed an extra week for this kernel because of meltdown/spectre.
I have amd, so the meltdwon is little concern.

Asus Prime 370X-Pro
AMD Ryzen 1600X (6 cores @ 3.6 GHz)
16 Gig DDR4 3200 (G Skill)
Nvidia -MSI GeForce GT 710 fanless
Samsung 960 NVMe SSD nvme0n1 P1,P2, and P3=MX-18, P4=antiX-19 beta
2TB WD sda1= data
on-board ethernet &and sound

[Moderator caprea]

Helpful

Up

0

::

Its just learning by doing, using what is offered in a practicable manner
and listening(reading), trying to understand, what the really smart people here and on mx-forum are telling, how the things are depending and working together( anti,dave,skidoo,stevo…….)

I really enjoy giving my little,little piece to get the new kernel a real option,even if you have special hardware.
This is linux I think, a lot of fun doing something together.

[Forum Admin anticapitalista]

Helpful

Up

0

::

caprea wrote:

…
I really enjoy giving my little,little piece to get the new kernel a real option,even if you have special hardware.
This is linux I think, a lot of fun doing something together.

Totally agree!

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator caprea]

Helpful

Up

0

::

After gcc-7 was updated today to 7.3.0-3 on testing-repo

Attachments:

1. 

   ANTIXscreenshot.v01.jpg
   

[Forum Admin anticapitalista]

Helpful

Up

0

::

A new 4.15.3 set of kernels are waiting to appear in the repos.
The ones in testing and sid have been built with gcc7.3 and should offer more protection for spectre

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator caprea]

Helpful

Up

0

::

On my antix-installation running testing-repo. Kernel 4.15.3-antix.1-amd64-smp
I dont have any stability problems and everything is running well.
Can’t test the problem with android-phone used as wifi-spot, bc no smartphone in the house.(It’s solved on mx-forum with 4.15.3 )

• This reply was modified 5 years, 2 months ago by caprea.

Attachments:

1. 

   SPECTRE.jpg
   

[Anonymous]

Helpful

Up

0

::

Hi everyone,
Just installed the 4.15-3 this morning and mine still shows the PTI/meltdown v3
vulnerability. I did a reload-update-apply in synaptic then installed the kernel
image. Did I miss something? I’m running 32 bit on sid repos.

[Moderator caprea]

Helpful

Up

0

::

The developers lag behind a little bit for 32bit I think.

[Anonymous]

Helpful

Up

0

::

Well that makes sense because there are more people and developers running on 64-bit
hardware…I might set my intel aside and run my Amd on for now, at least until meltdown
is patched. It looks like Amd didn’t follow intel design and is immune.

[Author]

Posts