“spectre” and “meltdown” – security kernel upgrades

Forum Forums News Announcements “spectre” and “meltdown” – security kernel upgrades

This topic contains 62 replies, has 16 voices, and was last updated by Fonsis Apr 16-8:00 am.

Viewing 15 posts - 1 through 15 (of 63 total)
  • Author
    Posts
  • #4964
    Forum Admin
    anticapitalista
    anticapitalista

    Please read this post.

    spectre-and-meltdown-security-kernel-upgrades/

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

    #4979
    Forum Admin
    rokytnji
    rokytnji

    Done on shop emachine 3507 desktop

    $ inxi -Fxz
    System:    Host: biker Kernel: 4.14.12-antix.1-amd64-smp x86_64 bits: 64 gcc: 6.3.0
               Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: MX-17_x64 Horizon December 15, 2017
    Machine:   Device: desktop System: GATEWAY product: W3507 v: 500 serial: N/A
               Mobo: Intel model: D102GGC2 v: AAD70214-201 serial: N/A
               BIOS: Intel v: GC11020M.15A.2010.2006.0817.0956 date: 08/17/2006
    CPU:       Single core Intel Celeron D (-UP-) arch: Netburst Prescott rev.4 cache: 512 KB
               flags: (lm nx sse sse2 sse3) bmips: 6400 speed: 3200 MHz (max)
    Graphics:  Card: Advanced Micro Devices [AMD/ATI] RC410 [Radeon Xpress 200/1100] bus-ID: 01:05.0
               Display Server: x11 (X.Org 1.19.2 )
               drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
               Resolution: 1024x768@85.00hz
               OpenGL: renderer: Gallium 0.4 on ATI RC410 version: 2.1 Mesa 13.0.6 Direct Render: Yes
    Audio:     Card Advanced Micro Devices [AMD/ATI] IXP SB4x0 High Def. Audio Controller
               driver: snd_hda_intel bus-ID: 00:14.2
               Sound: Advanced Linux Sound Architecture v: k4.14.12-antix.1-amd64-smp
    Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
               driver: 8139too v: 0.9.28 port: 1000 bus-ID: 02:02.0
               IF: eth0 state: down mac: <filter>
               Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u usb-ID: 001-004
               IF: wlan0 state: N/A mac: N/A
    Drives:    HDD Total Size: 444.0GB (1.7% used)
               ID-1: /dev/sda model: ST3120213A size: 120.0GB
               ID-2: /dev/sdb model: Maxtor_5A320J0 size: 323.9GB
    Partition: ID-1: / size: 9.1G used: 5.1G (59%) fs: ext4 dev: /dev/sda1
               ID-2: /home size: 31G used: 211M (1%) fs: ext4 dev: /dev/sda3
               ID-3: swap-1 size: 2.17GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
    Sensors:   System Temperatures: cpu: 51.2C mobo: 49.9C
               Fan Speeds (in rpm): cpu: 2277 fan-2: 1130 fan-4: 0
    Info:      Processes: 171 Uptime: 3 min Memory: 322.5/1869.1MB
               Init: SysVinit runlevel: 5 Gcc sys: 6.3.0 Client: Shell (bash 4.4.121) inxi: 2.3.53 
    

    Just install info below. Rebooted OK so far.

    ..Setting up linux-headers-4.14.12-antix.1-amd64-smp (4.14.12-antix.1-amd64-smp-1) ...
    Setting up linux-image-4.14.12-antix.1-amd64-smp (4.14.12-antix.1-amd64-smp-1) 
    Warning: Unable to find an initial ram disk that I know how to handle.
    Will not try to make an initrd.
    update-initramfs: Generating /boot/initrd.img-4.14.12-antix.1-amd64-smp
    I: The initramfs will attempt to resume from /dev/sda2
    I: (UUID=a55f5477-b77d-4e07-b34a-d0260ad85959)
    I: Set the RESUME variable to override this.
    Generating grub configuration file ...
    using custom appearance settings
    Found background image: /usr/share/backgrounds/MXLinux/grub/mxreflection_by_ant_ony.png
    Found linux image: /boot/vmlinuz-4.14.12-antix.1-amd64-smp
    Found initrd image: /boot/initrd.img-4.14.12-antix.1-amd64-smp
    Found linux image: /boot/vmlinuz-4.13.0-1-amd64
    Found initrd image: /boot/initrd.img-4.13.0-1-amd64
    Found memtest86+ image: /boot/memtest86+.bin
    Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
    done
    
    

    Later is laptop upgrades.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #4980

    Anonymous

    I just done the computer in my signature and it all went without issues.

    Thanks.

    @Dell-Optiplex-360:~
    $ inxi -Fxz
    System:    Host: Dell-Optiplex-360 Kernel: 4.14.12-antix.1-amd64-smp x86_64 bits: 64 gcc: 6.3.0
               Desktop: IceWM 1.4.2 Distro: antiX-17_x64-base Heather Heyer 24 October 2017
    Machine:   Device: desktop System: Dell product: OptiPlex 360 serial: N/A
               Mobo: Dell model: 0T656F v: A01 serial: N/A BIOS: Dell v: A01 date: 11/28/2008
    CPU:       Dual core Intel Core2 6300 (-MCP-) arch: Conroe rev.6 cache: 2048 KB
               flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7446
               clock speeds: max: 1867 MHz 1: 1600 MHz 2: 1867 MHz
    Graphics:  Card: NVIDIA G72 [GeForce 7300 LE] bus-ID: 01:00.0
               Display Server: X.Org 1.19.2 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
               Resolution: 1024x768@60.00hz
               OpenGL: renderer: Gallium 0.4 on NV46 version: 2.1 Mesa 13.0.6 Direct Render: Yes
    Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
               Sound: Advanced Linux Sound Architecture v: k4.14.12-antix.1-amd64-smp
    Network:   Card: Broadcom Limited NetLink BCM5784M Gigabit Ethernet PCIe driver: tg3 v: 3.137 bus-ID: 02:00.0
               IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
    Drives:    HDD Total Size: 80.0GB (8.2% used)
               ID-1: /dev/sda model: SAMSUNG_HD080HJ/ size: 80.0GB
    Partition: ID-1: / size: 71G used: 4.3G (7%) fs: ext4 dev: /dev/sda1
               ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
    Sensors:   System Temperatures: cpu: 55.0C mobo: N/A gpu: 48.0
               Fan Speeds (in rpm): cpu: N/A
    Info:      Processes: 112 Uptime: 0 min Memory: 136.4/3002.7MB Init: SysVinit runlevel: 5 Gcc sys: 6.3.0
               Client: Shell (bash 4.4.121) inxi: 2.3.53 
    #4983
    Member
    wasp
    wasp

    The recommended choice for a stable system which one is? I personally installed the 4.9.75.antix2 kernel without any reboot problems, but I wanted to know if in the future to upgrade the kernel just an apt-get dist-upgrade or install the kernel as now?
    PS thanks to the developers, a quick and stable distro without systemd! 🙂

    #4984
    Forum Admin
    rokytnji
    rokytnji

    Install the kernel as now is what I gather from this thread.

    Dell e4310 laptop

    $ inxi -Fxz
    System:    Host: biker Kernel: 4.14.12-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: laptop System: Dell product: Latitude E4310 v: 0001 serial: N/A
               Mobo: Dell model: 0T6M8G v: A01 serial: N/A
               BIOS: Dell v: A03 date: 07/08/2010
    Battery    BAT0: charge: 48.8 Wh 127.0% condition: 38.5/48.8 Wh (79%)
               model: Samsung SDI DELL RM6618A status: Full
    CPU:       Dual core Intel Core i5 M 520 (-MT-MCP-) arch: Nehalem rev.5 cache: 3072 KB
               flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9575
               clock speeds: max: 2400 MHz 1: 1199 MHz 2: 1999 MHz 3: 1599 MHz 4: 1733 MHz
    Graphics:  Card: Intel Core Processor Integrated Graphics Controller bus-ID: 00:02.0
               Display Server: X.Org 1.19.2 driver: intel Resolution: 1366x768@60.00hz
               OpenGL: renderer: Mesa DRI Intel Ironlake Mobile
               version: 2.1 Mesa 13.0.6 Direct Render: Yes
    Audio:     Card Intel 5 Series/3400 Series High Def. Audio
               driver: snd_hda_intel bus-ID: 00:1b.0
               Sound: Advanced Linux Sound Architecture v: k4.14.12-antix.1-amd64-smp
    Network:   Card-1: Intel 82577LM Gigabit Network Connection
               driver: e1000e v: 3.2.6-k port: 6040 bus-ID: 00:19.0
               IF: eth0 state: down mac: <filter>
               Card-2: Intel Centrino Advanced-N 6200 driver: iwlwifi bus-ID: 02:00.0
               IF: wlan0 state: up mac: <filter>
    Drives:    HDD Total Size: 60.0GB (40.7% used)
               ID-1: /dev/sda model: KINGSTON_SV300S3 size: 60.0GB
    Partition: ID-1: / size: 7.7G used: 3.7G (52%) fs: ext4 dev: /dev/sda2
               ID-2: /home size: 48G used: 20G (43%) fs: ext4 dev: /dev/sda1
    Sensors:   System Temperatures: cpu: 55.0C mobo: N/A
               Fan Speeds (in rpm): cpu: N/A
    Info:      Processes: 163 Uptime: 2 min Memory: 196.8/7906.3MB
               Init: SysVinit runlevel: 5 Gcc sys: 6.3.0
               Client: Shell (bash 4.4.121) inxi: 2.3.53 
    

    Install info. Rebooted OK.

    Setting up linux-headers-4.14.12-antix.1-amd64-smp (4.14.12-antix.1-amd64-smp-1) ...
    Setting up linux-image-4.14.12-antix.1-amd64-smp (4.14.12-antix.1-amd64-smp-1) ...
    Warning: Unable to find an initial ram disk that I know how to handle.
    Will not try to make an initrd.
    Error! Bad return status for module build on kernel: 4.14.12-antix.1-amd64-smp (x86_64)
    Consult /var/lib/dkms/virtualbox-guest/5.1.30/build/make.log for more information.
    update-initramfs: Generating /boot/initrd.img-4.14.12-antix.1-amd64-smp
    Generating grub configuration file ...
    Found background: /usr/share/wallpaper/back.jpg
    Found background image: /usr/share/wallpaper/back.jpg
    Found linux image: /boot/vmlinuz-4.14.12-antix.1-amd64-smp
    Found initrd image: /boot/initrd.img-4.14.12-antix.1-amd64-smp
    Found linux image: /boot/vmlinuz-4.10.5-antix.3-amd64-smp
    Found initrd image: /boot/initrd.img-4.10.5-antix.3-amd64-smp
    Found memtest86+ image: /boot/memtest86+.bin
    done
    

    Just more info

    harry@biker:~
    $ cat /var/lib/dkms/virtualbox-guest/5.1.30/build/make.log
    DKMS make.log for virtualbox-guest-5.1.30 for kernel 4.14.12-antix.1-amd64-smp (x86_64)
    Wed Jan 10 17:04:08 CST 2018
    make: Entering directory '/usr/src/linux-headers-4.14.12-antix.1-amd64-smp'
    Makefile:942: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
      AR      /var/lib/dkms/virtualbox-guest/5.1.30/build/built-in.o
      AR      /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/built-in.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/VBoxGuest-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/VBoxGuest.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/HGCMInternal.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/GenericRequest.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/Init.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/PhysHeap.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/SysHlp.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/VMMDev.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/alloc-r0drv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/initterm-r0drv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/memobj-r0drv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/mpnotification-r0drv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/powernotification-r0drv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/assert-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/mp-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/mpnotification-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/process-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/semevent-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/semeventmulti-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/semfastmutex-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/semmutex-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/spinlock-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/thread-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/thread2-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/time-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/timer-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/linux/RTLogWriteDebugger-r0drv-linux.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/r0drv/generic/semspinmutex-r0drv-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/alloc/alloc.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/err/RTErrConvertFromErrno.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/err/RTErrConvertToErrno.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/log/log.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/log/logellipsis.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/log/logrel.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/log/logrelellipsis.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/log/logcom.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/log/logformat.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg1Weak.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg2.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg2Add.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg2AddWeak.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg2AddWeakV.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg2Weak.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/RTAssertMsg2WeakV.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/assert.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/misc/thread.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/RTStrCopy.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/RTStrCopyEx.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/RTStrCopyP.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/strformat.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/strformatrt.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/strformattype.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/strprintf.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/string/strtonum.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/table/avlpv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/time/time.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTAssertShouldPanic-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTLogWriteStdErr-stub-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTLogWriteStdOut-stub-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTMpGetCoreCount-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTSemEventWait-2-ex-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTSemEventWaitNoResume-2-ex-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTSemEventMultiWait-2-ex-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/RTSemEventMultiWaitNoResume-2-ex-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/rtStrFormatKernelAddress-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/errvars-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/generic/mppresent-generic.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/VBox/log-vbox.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/VBox/logbackdoor.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/common/alloc/heapsimple.o
      LD [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxguest/vboxguest.o
      AR      /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/built-in.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/vfsmod.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/dirops.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/lnkops.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/regops.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/utils.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/GenericRequest.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/SysHlp.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/PhysHeap.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/Init.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/VMMDev.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/HGCM.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/VBoxGuestR0LibSharedFolders.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/VbglR0CanUsePhysPageList.o
      LD [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxsf/vboxsf.o
      AR      /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/built-in.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/HGSMIBase.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/HGSMICommon.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/HGSMIMemAlloc.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/heapoffset.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/Modesetting.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_irq.o
      CC [M]  /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_main.o
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.c:285:5: error: unknown field ‘set_busid’ specified in initializer
         .set_busid = drm_pci_set_busid,
         ^
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.c:285:18: error: ‘drm_pci_set_busid’ undeclared here (not in a function)
         .set_busid = drm_pci_set_busid,
                      ^~~~~~~~~~~~~~~~~
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.c: In function ‘vbox_init’:
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.c:329:12: error: implicit declaration of function ‘drm_pci_init’ [-Werror=implicit-function-declaration]
         return drm_pci_init(&driver, &vbox_pci_driver);
                ^~~~~~~~~~~~
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.c: In function ‘vbox_exit’:
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.c:333:5: error: implicit declaration of function ‘drm_pci_exit’ [-Werror=implicit-function-declaration]
         drm_pci_exit(&driver, &vbox_pci_driver);
         ^~~~~~~~~~~~
    cc1: some warnings being treated as errors
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.c:399:5: error: unknown field ‘gamma_set’ specified in initializer
         .gamma_set = vbox_fb_gamma_set,
         ^
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.c:399:18: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
         .gamma_set = vbox_fb_gamma_set,
                      ^~~~~~~~~~~~~~~~~
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.c:399:18: note: (near initialization for ‘vbox_fb_helper_funcs.fb_probe’)
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.c:400:5: error: unknown field ‘gamma_get’ specified in initializer
         .gamma_get = vbox_fb_gamma_get,
         ^
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.c:400:18: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
         .gamma_get = vbox_fb_gamma_get,
                      ^~~~~~~~~~~~~~~~~
    /var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.c:400:18: note: (near initialization for ‘vbox_fb_helper_funcs.initial_config’)
    scripts/Makefile.build:314: recipe for target '/var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.o' failed
    make[2]: *** [/var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_drv.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    cc1: some warnings being treated as errors
    scripts/Makefile.build:314: recipe for target '/var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.o' failed
    make[2]: *** [/var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo/vbox_fb.o] Error 1
    scripts/Makefile.build:573: recipe for target '/var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo' failed
    make[1]: *** [/var/lib/dkms/virtualbox-guest/5.1.30/build/vboxvideo] Error 2
    Makefile:1518: recipe for target '_module_/var/lib/dkms/virtualbox-guest/5.1.30/build' failed
    make: *** [_module_/var/lib/dkms/virtualbox-guest/5.1.30/build] Error 2
    make: Leaving directory '/usr/src/linux-headers-4.14.12-antix.1-amd64-smp'
    

    I aint sweating virtual box or dkms as I never use it.

      Sheepish 2nd edit

    : If you wanna avoid my dkms/virtual box errors. Do a dist-upgrade before the kernel install.
    I just dist-upgraded and guess what? Virtual box and dkms was in the dist-upgrade.

    • This reply was modified 1 year ago by rokytnji.
    • This reply was modified 1 year ago by rokytnji.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #4988
    Member

    skidoo

    just an apt-get dist-upgrade or install the kernel as now?

    In another recent topic, someone asked “Does a dist-upgrade operation automatically install the latest kernel?”
    Based on my (infrequent dist-upgrade) experience, I replied “No”… and nobody followed up to dispute that answer.

    Today, wondering whether “apt dist-upgrade” vs “apt-get dist-upgrade” might produce a different result…
    First, I checked the docs. Per the docs, would need to use the commandstring “apt upgrade full”
    ~~ IOW, per the docs, “apt dist-upgrade” does not exist, should not be recognized.
    Second, I tested, and confirmed that “apt dist-upgrade” is, in fact, recognized on my untweaked antiX17 system.
    It produces the same result as “apt-get dist-upgrade” (it does not attempt to automatically install newer available kernel)

    #4989
    Member
    caprea
    caprea

    The default freedom of choice which kernel you use in antix, when and if downgrading to an older or updating to a recent new one,
    and not being suddenly unpleasantly surprised with a kernel after a dist-upgrade, like in many other distros,
    is something I really dont want to miss in antix.

    • This reply was modified 1 year ago by caprea.
    #4991
    Member

    skidoo

    caprea, I agree and am entirely content with the status quo.
    I checked all the /etc/apt conf+preferences files and, except for autoremove rules, didn’t find anything mentioning kernel package handling.
    The “like in many other distros” behavior… I don’t know what mechanism those other distros employ to achieve “auto” kernel upgrade.

    edit:
    sudo apt-conf dump
    shows all the settings key:values but I still didn’t find anything mentioning linux* (or *kernel*) package hold-vs-autoupgrade

    • This reply was modified 1 year ago by skidoo.
    #4993
    Forum Admin
    anticapitalista
    anticapitalista

    Other distros do it by keeping the exact same deb file name.

    If we were upgrading the existing 4.10.5 kernel to a bugfix 4.10.5, it would make sense to have this auto-install with a dist-upgrade.
    However, the kernels now offered are different and it is up to the user to decide.

    Next point release of antiX-17.1 will ship with 4.9.xx

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

    #4998
    Member
    cyrilus31
    cyrilus31

    Anyway, anti, thanks for the clarification.

    #4999
    Member
    wasp
    wasp

    Other distros do it by keeping the exact same deb file name.

    If we were upgrading the existing 4.10.5 kernel to a bugfix 4.10.5, it would make sense to have this auto-install with a dist-upgrade.
    However, the kernels now offered are different and it is up to the user to decide.

    Next point release of antiX-17.1 will ship with 4.9.xx

    Thanks!
    Maybe then it is better to install the default kernel (now 4.9.75) in order to automatically have automatic patches in the future …

    #5004
    Member
    Fonsis
    Fonsis

    Hi guys,
    regarding to this statement “Unfortunately, I have not been able to patch the 4.10-5 kernel (antiX-17 default) or the 4.4 version (antiX-16 series). “, I would much appreciate a “how to” document listed here on antix website on how to upgrade the kernel manually for antix 17 default and antix 16.

    Thank you and best regards,
    Fonsis
    🙂

    Best regards,
    Fonsis
    🙂

    #5005
    Forum Admin
    anticapitalista
    anticapitalista

    On antiX-17, use cli-aptiX and choose from the list of antiX or Debian kernels

    Or apt-get install linux-headers-4.9.75-antix.2-amd64-smp linux-image-4.9.75-antix.2-amd64-smp

    For antiX-16, you will have to wait or instead the Debian 3.16 kernel

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

    #5006
    Member
    Fonsis
    Fonsis

    apt-get install linux-headers-4.9.75-antix.2-amd64-smp linux-image-4.9.75-antix.2-amd64-smp

    -> done!

    How do I make 4.9.75 my default kernel at boot?
    I don’t see any menu.lst and control center lists a lot of options but where to add the new kernel for boot?

    I CAN choose 4.9.75 at boot manually – and it works.
    This is the good news.
    But I would like to have 4.9.75 as default kernel. 🙂

    Best regards,
    Fonsis
    🙂

    Best regards,
    Fonsis
    🙂

    #5008
    Forum Admin
    rokytnji
    rokytnji

    apt-get install linux-headers-4.9.75-antix.2-amd64-smp linux-image-4.9.75-antix.2-amd64-smp

    -> done!

    How do I make 4.9.75 my default kernel at boot?
    I don’t see any menu.lst and control center lists a lot of options but where to add the new kernel for boot?

    I CAN choose 4.9.75 at boot manually – and it works.
    This is the good news.
    But I would like to have 4.9.75 as default kernel. 🙂

    Best regards,
    Fonsis
    🙂

    Right now. I am plodding along on my IBM T23. Finally got 17 installed. Posting this post on my better Dell Laptop. Because of non sse2 cpu on my T23 and I can’t seem to log in yet on this forum with it with Dillo or Netsurf yet. Firefox and SeaMonkey are useless on it. Keeps crashing at 100% cpu. Anyhows.

    When done with my Kernel install on the T23. I will reboot and boot into 4.9.75 and open synaptic and un-install kernel 4.10. Let it update grub. Done. Now 4.9 is at the top of the list. I see no reason to keep a 4.10 kernel and header I won’t boot into.

    Working with this IBM T23 laptop in todays world is like watching paint dry. Here is hoping qupzilla bails me out on that laptop and logging into this forum. WordPress uses java and cookies. I have cookies enabled in Dillo. But WordPress don’t seem to care . Oh well. Back to the grind stone.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

Viewing 15 posts - 1 through 15 (of 63 total)

You must be logged in to reply to this topic.