Error installing 5.2 kernel

Forum Forums General Software Error installing 5.2 kernel

  • This topic has 1 reply, 2 voices, and was last updated Dec 24-4:04 am by anticapitalista.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #31097
    Member
    umuluto

      Here’s the log:

      Reading package lists…
      Building dependency tree…
      Reading state information…
      0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 3 not upgraded.
      Need to get 0 B/41.2 MB of archives.
      After this operation, 0 B of additional disk space will be used.
      (Reading database …
      (Reading database … 5%
      (Reading database … 10%
      (Reading database … 15%
      (Reading database … 20%
      (Reading database … 25%
      (Reading database … 30%
      (Reading database … 35%
      (Reading database … 40%
      (Reading database … 45%
      (Reading database … 50%
      (Reading database … 55%
      (Reading database … 60%
      (Reading database … 65%
      (Reading database … 70%
      (Reading database … 75%
      (Reading database … 80%
      (Reading database … 85%
      (Reading database … 90%
      (Reading database … 95%
      (Reading database … 100%
      (Reading database … 255570 files and directories currently installed.)
      Preparing to unpack …/linux-image-5.2.21-antix.2-486-smp_5.2.21-antix.2-486-smp-1_i386.deb …
      dkms: removing: virtualbox-guest 6.0.12 (5.2.21-antix.2-486-smp) (i686)

      ——– Uninstall Beginning ——–
      Module: virtualbox-guest
      Version: 6.0.12
      Kernel: 5.2.21-antix.2-486-smp (i686)
      ————————————-

      Status: Before uninstall, this module version was ACTIVE on this kernel.

      vboxguest.ko:
      – Uninstallation
      – Deleting from: /lib/modules/5.2.21-antix.2-486-smp/updates/
      rmdir: failed to remove ‘updates’: Directory not empty
      – Original module
      – Archived original module found in the DKMS tree
      – Moving it to: /lib/modules/5.2.21-antix.2-486-smp/updates/

      vboxsf.ko:
      – Uninstallation
      – Deleting from: /lib/modules/5.2.21-antix.2-486-smp/updates/
      rmdir: failed to remove ‘updates’: Directory not empty
      – Original module
      – No original module was found for this module on this kernel.
      – Use the dkms install command to reinstall any previous module version.

      vboxvideo.ko:
      – Uninstallation
      – Deleting from: /lib/modules/5.2.21-antix.2-486-smp/updates/
      rmdir: failed to remove ‘updates’: Directory not empty
      – Original module
      – Archived original module found in the DKMS tree
      – Moving it to: /lib/modules/5.2.21-antix.2-486-smp/updates/
      depmod….

      Removing original_module from DKMS tree for kernel 5.2.21-antix.2-486-smp (i686)

      DKMS: uninstall completed.
      Unpacking linux-image-5.2.21-antix.2-486-smp (5.2.21-antix.2-486-smp-1) over (5.2.21-antix.2-486-smp-1) …
      Setting up linux-image-5.2.21-antix.2-486-smp (5.2.21-antix.2-486-smp-1) …
      Error! Bad return status for module build on kernel: 5.2.21-antix.2-486-smp (i686)
      Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
      Error! Bad return status for module build on kernel: 5.2.21-antix.2-486-smp (i686)
      Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
      update-initramfs: Generating /boot/initrd.img-5.2.21-antix.2-486-smp
      cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
      nor crypto modules. If that’s on purpose, you may want to uninstall the
      ‘cryptsetup-initramfs’ package in order to disable the cryptsetup initramfs
      integration and avoid this warning.
      I: The initramfs will attempt to resume from /dev/sda5
      I: (UUID=fdcc672b-9030-40bc-83b1-62e1b602c02f)
      I: Set the RESUME variable to override this.
      Generating grub configuration file …
      Found background: /usr/share/wallpaper/grub/back.png
      Found background image: /usr/share/wallpaper/grub/back.png
      Found linux image: /boot/vmlinuz-5.2.21-antix.2-686-smp-pae
      Found initrd image: /boot/initrd.img-5.2.21-antix.2-686-smp-pae
      Found linux image: /boot/vmlinuz-5.2.21-antix.2-486-smp
      Found initrd image: /boot/initrd.img-5.2.21-antix.2-486-smp
      Found linux image: /boot/vmlinuz-4.9.193-antix.1-486-smp
      Found initrd image: /boot/initrd.img-4.9.193-antix.1-486-smp
      Found memtest86+ image: /boot/memtest86+.bin
      Found Windows 10 on /dev/sda1
      done

      DKMS make.log for broadcom-sta-6.30.223.271 for kernel 5.2.21-antix.2-486-smp (i686)
      Tue 24 Dec 2019 03:31:43 AM +07
      /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/5.2.21-antix.2-486-smp/build M=pwd
      make[1]: warning: jobserver unavailable: using -j1. Add ‘+’ to parent make rule.
      make[1]: Entering directory ‘/usr/src/linux-headers-5.2.21-antix.2-486-smp’
      CFG80211 API is prefered for this kernel version
      Using CFG80211 API
      Kernel architecture is X86_32
      CC [M] /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/shared/linux_osl.o
      CC [M] /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.o
      /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’:
      /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:780:2: warning: this ‘if’ clause does not guard… [-Wmisleading-indentation]
      if ((val & 0x0000ff00) != 0)
      ^~
      /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:782:3: note: …this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
      bar1_size = pci_resource_len(pdev, 2);
      ^~~~~~~~~
      CC [M] /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_iw.o
      CC [M] /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.o
      /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’:
      /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:460:9: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration]
      set_fs(get_ds());
      ^~~~~~
      get_fs
      /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:460:9: error: incompatible type for argument 1 of ‘set_fs’
      set_fs(get_ds());
      ^~~~~~~~
      In file included from ./include/linux/uaccess.h:11,
      from ./arch/x86/include/asm/fpu/xstate.h:5,
      from ./arch/x86/include/asm/pgtable.h:26,
      from ./include/linux/mm.h:99,
      from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/include/linuxver.h:65,
      from /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:26:
      ./arch/x86/include/asm/uaccess.h:29:40: note: expected ‘mm_segment_t’ {aka ‘struct <anonymous>’} but argument is of type ‘int’
      static inline void set_fs(mm_segment_t fs)
      ~~~~~~~~~~~~~^~
      cc1: some warnings being treated as errors
      make[2]: *** [scripts/Makefile.build:279: /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.o] Error 1
      make[1]: *** [Makefile:1610: _module_/var/lib/dkms/broadcom-sta/6.30.223.271/build] Error 2
      make[1]: Leaving directory ‘/usr/src/linux-headers-5.2.21-antix.2-486-smp’
      make: *** [Makefile:177: all] Error 2

      DKMS make.log for ndiswrapper-1.61 for kernel 5.2.21-antix.2-486-smp (i686)
      Tue 24 Dec 2019 03:31:48 AM +07
      make: Entering directory ‘/usr/src/linux-headers-5.2.21-antix.2-486-smp’
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/crt_exports.h
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/hal_exports.h
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/ndis_exports.h
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel_exports.h
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel_io_exports.h
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/rtl_exports.h
      MKEXPORT /var/lib/dkms/ndiswrapper/1.61/build/usb_exports.h
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/crt.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/hal.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/loader.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/ndis.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel_io.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/pe_linker.o
      /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.c: In function ‘ntoskernel_init’:
      /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.c:2521:2: error: implicit declaration of function ‘do_gettimeofday’; did you mean ‘do_settimeofday64’? [-Werror=implicit-function-declaration]
      do_gettimeofday(&now);
      ^~~~~~~~~~~~~~~
      do_settimeofday64
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/pnp.o
      CC [M] /var/lib/dkms/ndiswrapper/1.61/build/proc.o
      cc1: some warnings being treated as errors
      make[1]: *** [scripts/Makefile.build:279: /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.o] Error 1
      make[1]: *** Waiting for unfinished jobs….
      make: *** [Makefile:1610: _module_/var/lib/dkms/ndiswrapper/1.61/build] Error 2
      make: Leaving directory ‘/usr/src/linux-headers-5.2.21-antix.2-486-smp’

      • This topic was modified 3 years, 4 months ago by umuluto.
      #31101
      Forum Admin
      anticapitalista
        Helpful
        Up
        0
        ::

        Which version of antiX are you using? Are you using default repos (ie not sid nor testing)?

        If you don’t need them you could remove broadcom-sta and ndiswrapper packages and reinstall the headers

        apt-get install --reinstall linux-headers-5.2.21-antix.2-486-smp

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

        antiX with runit - leaner and meaner.

      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.