Antix 19.3 Full – crash during boot – SELinux policy33 not such file or director

Forum Forums New users New Users and General Questions Antix 19.3 Full – crash during boot – SELinux policy33 not such file or director

  • This topic has 20 replies, 7 voices, and was last updated Feb 16-11:02 am by roland.
Viewing 15 posts - 1 through 15 (of 21 total)
  • Author
    Posts
  • #54214
    Member
    AvatarWallon

    Hello,

    I have more and more often the problem when I want to start Antix 19.3 Full installed on a USB stick. I have to shut down the computer. I took 2 pictures because I can’t get into Antix to give a copy of the dmesg file.
    What can I do to avoid this problem at startup?

    
    System:    Host: MSI Kernel: 5.8.16-antix.1-amd64-smp x86_64 bits: 64 compiler: N/A 
               parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.16-antix.1-amd64-smp 
               root=UUID=7da674d4-292a-42aa-b0a5-dd717bc90c00 ro quiet 
               Desktop: IceWM 2.1.1 dm: SLiM 1.3.6 
               Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020 
               base: Debian GNU/Linux 10 (buster) 
    Machine:   Type: Desktop Mobo: MSI model: H170M PRO-VDH (MS-7982) v: 1.0 serial: <filter> 
               UEFI [Legacy]: American Megatrends v: 2.A0 date: 07/27/2016 
    Memory:    RAM: total: 15.59 GiB used: 869.5 MiB (5.4%) 
               RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
    PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. 
    CPU:       Topology: Quad Core model: Intel Core i5-6400 bits: 64 type: MCP arch: Skylake-S 
               family: 6 model-id: 5E (94) stepping: 3 microcode: D6 L2 cache: 6144 KiB 
               bogomips: 21599 
               Speed: 3275 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 3279 2: 3249 3: 3290 
               4: 3256 
               Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon art avx avx2 
               bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl 
               dtes64 dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase fxsr 
               ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid invpcid_single 
               lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat 
               pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed 
               rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall 
               tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 
               xsave xsavec xsaveopt xsaves xtopology xtpr 
               Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
               Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
               Type: mds mitigation: Clear CPU buffers; SMT disabled 
               Type: meltdown mitigation: PTI 
               Type: spec_store_bypass 
               mitigation: Speculative Store Bypass disabled via prctl and seccomp 
               Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
               Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: 
               disabled, RSB filling 
               Type: srbds status: Vulnerable: No microcode 
               Type: tsx_async_abort status: Not affected 
    Graphics:  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Micro-Star MSI driver: nvidia 
               v: 460.39 bus ID: 01:00.0 chip ID: 10de:1401 
               Display: x11 server: X.Org 1.20.4 driver: nvidia 
               unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz 
               OpenGL: renderer: GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 direct render: Yes 
    Audio:     Device-1: Intel Sunrise Point-H HD Audio 
               vendor: Micro-Star MSI 100 Series/C230 Series Family driver: snd_hda_intel v: kernel 
               bus ID: 00:1f.3 chip ID: 8086:a170 
               Device-2: NVIDIA GM206 High Definition Audio vendor: Micro-Star MSI 
               driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fba 
               Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo 
               bus ID: 1-6:3 chip ID: 046d:082d serial: <filter> 
               Sound Server: ALSA v: k5.8.16-antix.1-amd64-smp 
    Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI 
               driver: r8169 v: kernel port: d000 bus ID: 02:00.0 chip ID: 10ec:8168 
               IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
               IP v4: <filter> scope: global broadcast: <filter> 
               IP v6: <filter> type: dynamic mngtmpaddr scope: global 
               IP v6: <filter> scope: link 
               WAN IP: <filter> 
    Drives:    Local Storage: total: 1.16 TiB used: 6.69 GiB (0.6%) 
               ID-1: /dev/sda vendor: Kingston model: SUV400S37240G size: 223.57 GiB block size: 
               physical: 4096 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: D6SD scheme: GPT 
               ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1SB102 size: 931.51 GiB block size: 
               physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
               rev: CC43 scheme: GPT 
               ID-3: /dev/sdc type: USB vendor: SanDisk model: Extreme size: 29.82 GiB block size: 
               physical: 512 B logical: 512 B serial: <filter> rev: 0001 scheme: MBR 
               Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH24NSD1 rev: LG00 
               dev-links: cdrom,cdrw,dvd,dvdrw 
               Features: speed: 12 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram 
               state: running 
    RAID:      Message: No RAID data was found. 
    Partition: ID-1: / raw size: 25.85 GiB size: 25.44 GiB (98.43%) used: 6.68 GiB (26.3%) fs: ext2 
               dev: /dev/sdc3 label: rootantiXb uuid: 7da674d4-292a-42aa-b0a5-dd717bc90c00 
               ID-2: /media/an/sdc2-usb-SanDisk_Extreme_ raw size: 1.97 GiB size: 1.97 GiB (99.80%) 
               used: 12.9 MiB (0.6%) fs: vfat dev: /dev/sdc2 label: N/A uuid: A026-227D 
               ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) 
               cache pressure: 50 (default 100) dev: /dev/sdc1 label: N/A 
               uuid: 7a9849a2-51d6-4ba3-b83c-b81827894a3d 
    Unmounted: ID-1: /dev/sda1 size: 450.0 MiB fs: ntfs label: N/A uuid: 767C9A4C7C9A0751 
               ID-2: /dev/sda2 size: 99.0 MiB fs: vfat label: N/A uuid: CA5D-855D 
               ID-3: /dev/sda3 size: 16.0 MiB fs: <root required> label: N/A uuid: N/A 
               ID-4: /dev/sda4 size: 222.51 GiB fs: ntfs label: N/A uuid: 460E63F10E63D907 
               ID-5: /dev/sda5 size: 521.0 MiB fs: ntfs label: N/A uuid: F2844E49844E1091 
               ID-6: /dev/sdb1 size: 128.0 MiB fs: <root required> label: N/A uuid: N/A 
               ID-7: /dev/sdb2 size: 931.39 GiB fs: ntfs label: HDD 1To uuid: 6640C99340C969FF 
    USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 16 rev: 2.0 speed: 480 Mb/s 
               chip ID: 1d6b:0002 
               Device-1: 1-5:7 info: MGE UPS Systems UPS type: HID driver: hid-generic,usbhid 
               interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 0463:ffff serial: <filter> 
               Device-2: 1-6:3 info: Logitech HD Pro Webcam C920 type: Video,Audio 
               driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s 
               chip ID: 046d:082d serial: <filter> 
               Device-3: 1-9:4 info: Logitech M105 Optical Mouse type: Mouse 
               driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s chip ID: 046d:c077 
               Device-4: 1-10:5 info: Microsoft Wired Keyboard 600 (model 1576) type: Keyboard,HID 
               driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s chip ID: 045e:07f8 
               Device-5: 1-12:6 info: Genesys Logic USB 2.0 Multislot Card Reader/Writer 
               type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s 
               chip ID: 05e3:0716 serial: <filter> 
               Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.0 speed: 5 Gb/s 
               chip ID: 1d6b:0003 
               Device-6: 2-1:2 info: SanDisk SDCZ80 Flash Drive type: Mass Storage driver: usb-storage 
               interfaces: 1 rev: 3.0 speed: 5 Gb/s chip ID: 0781:5580 serial: <filter> 
    Sensors:   System Temperatures: cpu: 39.0 C mobo: 29.8 C gpu: nvidia temp: 32 C 
               Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
    Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
               1: deb http: //mirror.tiguinet.net/mx/packages/antix/buster buster main nonfree nosystemd
               Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
               1: deb http: //deb.debian.org/debian buster-backports main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
               1: deb http: //ftp.be.debian.org/debian/ buster-updates main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/debian.list 
               1: deb http: //ftp.be.debian.org/debian/ buster main contrib non-free
               2: deb http: //security.debian.org/ buster/updates main contrib non-free
               Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
               1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main
               No active apt repos in: /etc/apt/sources.list.d/onion.list 
               No active apt repos in: /etc/apt/sources.list.d/various.list 
    Processes: CPU top: 5 
               1: cpu: 7.1% command: chromium pid: 4207 mem: 208.5 MiB (1.3%) 
               2: cpu: 4.8% command: chromium pid: 4046 mem: 275.8 MiB (1.7%) 
               3: cpu: 4.3% command: chromium pid: 4443 mem: 201.1 MiB (1.2%) 
               4: cpu: 4.1% command: app-select started by: python3 pid: 5232 mem: 44.9 MiB (0.2%) 
               5: cpu: 3.3% command: chromium pid: 4004 mem: 282.4 MiB (1.7%) 
               Memory top: 5 
               1: mem: 282.4 MiB (1.7%) command: chromium pid: 4004 cpu: 3.3% 
               2: mem: 275.8 MiB (1.7%) command: chromium pid: 4046 cpu: 4.8% 
               3: mem: 208.5 MiB (1.3%) command: chromium pid: 4207 cpu: 7.1% 
               4: mem: 201.1 MiB (1.2%) command: chromium pid: 4443 cpu: 4.3% 
               5: mem: 173.5 MiB (1.0%) command: chromium pid: 4099 cpu: 0.6% 
    Info:      Processes: 181 Uptime: 9m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: 
               gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36
    
    • This topic was modified 3 weeks, 2 days ago by Wallon.
    #54216
    Member
    AvatarWallon

    It’s not possible to attach my first picture.
    I have something like this on my screen;

    SELinux : Could not open policy file <= /etc/selinux/targeted/policy/policy.33: No such file or directory
    INIT: versioin 2.93 booting
    [info] Using makefile-style concurrent boot in runlevel S

    I try to attach my second picture…

    Attachments:
    #54219
    Member
    XecureXecure

    First Google result: https://access.redhat.com/solutions/91863
    Solution: disable Selinux.

    Also, why install in a USB instead of using antiX in Live USB mode, as it was designed?

    The Most Extensive Live-usb on the Planet!

    #54224
    Member
    AvatarWallon

    I prefer the installation on an external SSD or USB stick. It’s a choice, a habit. I did the persistence test and found it to be slower. There are more operations to maintain a Live USB. Aren’t we in a free world?

    #54232
    Member
    skidooskidoo

    > > > Kernel: 5.8.16-antix.1-amd64-smp x86_64

    How/why did the OP wind up with Selinux enabled?
    My understanding was that antiX kernels do support Selinux, but the Selinux feature is not activated unless specifically requested via a bootline parameter.
    Is this kernel configured differently, behaves differently from other kernels?

    .
    > > > I did the persistence test and found it to be slower.

    Perhaps comparatively “slower to reach desktop session from boot”, but…
    Your specs show 16GB RAM. If you restest, using root_perist + automatic (or semi-auto) mode… along with toram bootline option, you should expect a wonderful “speed” increase. I/O operations will benefit from the massively superior bandwidth, compared to USB2.

    .
    > > > There are more operations to maintain a Live USB.

    Based on my observation of wildly-differing usage patterns ~~ some of the kids install//download gobs of programs to test drive then delete all but desirable “keepers”, some continually install more more more and “collect” programs on their system ~~ occasional live-remaster operations may be required. Some kids never bother, never feel the need to remaster but when they do, the remastering amounts to “click, click, done”. Okay, I have seen extreme cases where a remaster operation may take 20minutes {finger-drumming idle time}… but I cannot find merit in your assertion “there are more operations to maintain”. If a given user “collects” to extremes, and their collection outgrows the space available within the rootfs… “click, click, resize” and they are “back in business” for another XX weeks, or months.

    ___________________________________________
    When requesting help, pasting the output from inxi -Fzr command will provide important relevant details:
    antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specs

    #54234
    Moderator
    AvatarModdIt

    wallon wrote: There are more operations to maintain a Live USB. Aren’t we in a free world?

    He might think about the fact that any support and help he gets to fix the results of his
    experiments is not free, it costs the person who answers a part of his life expectancy for his
    convenience.

    • This reply was modified 3 weeks, 2 days ago by ModdIt.
    #54242
    Member
    KooKoo

    I have had this in the past after installing nvidia drivers, but it never stop the computer from booting. Just did not like seeing the message.

    https://www.tecmint.com/disable-selinux-in-centos-rhel-fedora/

    • This reply was modified 3 weeks, 2 days ago by Koo.

    T430 i7-3632QM 16gb , antiX-19.2.1-runit_x64-base Hannie Schaft 29 March 2020 , 5.8.16-antix.1-amd64-smp
    Testing 21a on T430.

    #54246
    Member
    AvatarWallon

    I’m not the only one with this problem.Here, on the Antix forum, 2 users also have the same problem but with a “policy.31” message. In my case, it is the message “policy.33”.

    etc/selinux/targeted/policy/policy 31 [Solved sort of]

    I tried the solution to set the parameter [selinux=0] using kernel 5.8.16.
    This erases the message at boot time but the boot still crashes. The computer crashes at the moment when the sentence appears “waiting for /dev to be fully populated…”.
    Is it really related to Nvidia? Is it really related to SELinux?

    By returning to kernel 4.19.152, the computer boots normally for the moment and I don’t have a message with “SELinux”. I only have this message “udevd[188]: Error running install command for nvidia”.

    #54248
    Member
    XecureXecure

    There must be some problem with the nvidia dkms package that got installed with the nvidia drivers. Normally, when you install a new kernel, during installation (of the kernel) all drivers that are setup using a dkms package will compile for the new kernel (drivers need to be compiled for each kernel). If they don’t, you will see an error appear during the installation (“nvidia-blablala-dkms failed to complete” or something similar). The new kernel will properly be installed, but the driver will not work for that kernel (as it wasn’t compiled for it).

    This is the limitation of Linux. The kernel controls everything, so all drivers need to be already included in the (final) kernel folder before it is used at boot, or else the driver will not work. As installing the nvidia driver blacklists the opensource nouveau driver, your system isn’t able to boot to a graphical interface (no driver to manage the graphical interface).

    Try removing the 5.8 linux kernel, reboot, and try installing it again. This time, pay attention to what errors it spits out. It may give a clue to what may be missing.

    You are right that you can do whatever you want with your system. Sorry if my previous answer seemed a bit out of place. I have had such good experience using the live system I tend to favor it over installed. When I mess up (I do this often, as I experiment with packages and configurations), I can choose to not save the current persistent changed (on persist_root), remove the rootfs file and start anew or just restore the previous remaster linuxfs.

    For nvidia drivers, I have failed each time I tried, so I gave up (I have little patience, and I am OK with using the nouveau drivers for now). Fortunately, caprea is much better at this, and has been able to help out.

    #54250
    Member
    KooKoo

    etc/selinux/targeted/policy/ error message is right the folder is not their nor any policy’s installed anyway.

    Maybe have look at this in the repo.
    selinux-policy-default
    Strict and Targeted variants of the SELinux policy

    I run a gtx970 and had not trouble with the card or drivers. But always install with sgfxi.

    For nvidia drivers, I have failed each time I tried, so I gave up (I have little patience, and I am OK with using the nouveau drivers for now). Fortunately, caprea is much better at this, and has been able to help out.

    • This reply was modified 3 weeks, 1 day ago by Koo.

    T430 i7-3632QM 16gb , antiX-19.2.1-runit_x64-base Hannie Schaft 29 March 2020 , 5.8.16-antix.1-amd64-smp
    Testing 21a on T430.

    #54252
    Moderator
    capreacaprea

    What always worked for me is, booting into a working kernel(in your case 4.19.152)
    and reinstalling the new kernel, it is not necessary to uninstall the kernel beforehand
    Afterwards the nvidia-driver worked on both kernels.

    So there seems to be indeed a problem with the nvidia-kernel-dkms package

    There’s also the command
    sudo dpkg-reconfigure nvidia-kernel-dkms
    but that didnt work for me 100% sure either and I dont know why.

    #54294
    Member
    AvatarWallon

    Dear Xecure,

    You are right with the dkms.
    I uninstalled the 5.8.16 kernel and reinstalled it through “Software Installer”. Note, I made several copy / paste during the installation process. It’s a bit of a shame that the terminal disappears automatically before you can copy all the information. Is there a “log” file that records an installation when you go through “Software Installer”?
    Here is what I was able to recover, it mentions a problem concerning the dkms.

    
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    The following NEW packages will be installed:
      linux-headers-5.8.16-antix.1-amd64-smp linux-image-5.8.16-antix.1-amd64-smp
    0 upgraded, 2 newly installed, 2 reinstalled, 0 to remove and 3 not upgraded.
    Need to get 63.8 MB of archives.
    After this operation, 355 MB of additional disk space will be used.
    Get:1 http://ftp.be.debian.org/debian buster/main amd64 libc6-dev amd64 2.28-10 [2,691 kB]
    Get:2 http://mirror.tiguinet.net/mx/packages/antix/buster buster/main amd64 linux-headers-5.8.16-antix.1-amd64-smp amd64 5.8.16-antix.1-amd64-smp-1 [7,898 kB]
    Get:3 http://ftp.be.debian.org/debian buster/main amd64 libelf-dev amd64 0.176-1.1 [72.1 kB]
    Get:4 http://mirror.tiguinet.net/mx/packages/antix/buster buster/main amd64 linux-image-5.8.16-antix.1-amd64-smp amd64 5.8.16-antix.1-amd64-smp-1 [53.2 MB]
    Fetched 63.8 MB in 10s (6,205 kB/s)                                            
    Selecting previously unselected package linux-headers-5.8.16-antix.1-amd64-smp.
    (Reading database ... 176400 files and directories currently installed.)
    Preparing to unpack .../linux-headers-5.8.16-antix.1-amd64-smp_5.8.16-antix.1-amd64-smp-1_amd64.deb ...
    Unpacking linux-headers-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) ...
    Selecting previously unselected package linux-image-5.8.16-antix.1-amd64-smp.
    Preparing to unpack .../linux-image-5.8.16-antix.1-amd64-smp_5.8.16-antix.1-amd64-smp-1_amd64.deb ...
    Unpacking linux-image-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) ...
    Preparing to unpack .../libc6-dev_2.28-10_amd64.deb ...
    Unpacking libc6-dev:amd64 (2.28-10) over (2.28-10) ...
    Preparing to unpack .../libelf-dev_0.176-1.1_amd64.deb ...
    Unpacking libelf-dev:amd64 (0.176-1.1) over (0.176-1.1) ...
    Setting up linux-headers-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) ...
    Setting up libelf-dev:amd64 (0.176-1.1) ...
    Setting up libc6-dev:amd64 (2.28-10) ...
    Setting up linux-image-5.8.16-antix.1-amd64-smp (5.8.16-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: 5.8.16-antix.1-amd64-smp (x86_64)
    Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
    update-initramfs: Generating /boot/initrd.img-5.8.16-antix.1-amd64-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/sdc1
    I: (UUID=7a9849a2-51d6-4ba3-b83c-b81827894a3d)
    I: Set the RESUME variable to override this.
    ....
    

    Here are the details of the make.log file

    
    DKMS make.log for ndiswrapper-1.61 for kernel 5.8.16-antix.1-amd64-smp (x86_64)
    Fri 12 Feb 2021 10:27:36 PM CET
    make: Entering directory '/usr/src/linux-headers-5.8.16-antix.1-amd64-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
      MKSTUBS /var/lib/dkms/ndiswrapper/1.61/build/win2lin_stubs.h
      AR      /var/lib/dkms/ndiswrapper/1.61/build/built-in.a
      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
    In file included from /var/lib/dkms/ndiswrapper/1.61/build/crt.c:16:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h: In function ‘raise_irql’:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:110:40: error: ‘struct task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
     #define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
                                            ^~~~~~~~~~~~
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:672:36: note: in expansion of macro ‘tsk_cpus_allowed’
      cpumask_copy(&info->cpus_allowed, tsk_cpus_allowed(current));
                                        ^~~~~~~~~~~~~~~~
    In file included from /var/lib/dkms/ndiswrapper/1.61/build/hal.c:16:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h: In function ‘raise_irql’:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:110:40: error: ‘struct task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
     #define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
                                            ^~~~~~~~~~~~
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:672:36: note: in expansion of macro ‘tsk_cpus_allowed’
      cpumask_copy(&info->cpus_allowed, tsk_cpus_allowed(current));
                                        ^~~~~~~~~~~~~~~~
    make[1]: *** [scripts/Makefile.build:281: /var/lib/dkms/ndiswrapper/1.61/build/crt.o] Error 1
    make[1]: *** Waiting for unfinished jobs....
    make[1]: *** [scripts/Makefile.build:281: /var/lib/dkms/ndiswrapper/1.61/build/hal.o] Error 1
    In file included from /var/lib/dkms/ndiswrapper/1.61/build/ndis.h:19,
                     from /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.h:19,
                     from /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.c:28:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h: In function ‘raise_irql’:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:110:40: error: ‘struct task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
     #define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
                                            ^~~~~~~~~~~~
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:672:36: note: in expansion of macro ‘tsk_cpus_allowed’
      cpumask_copy(&info->cpus_allowed, tsk_cpus_allowed(current));
                                        ^~~~~~~~~~~~~~~~
    In file included from /var/lib/dkms/ndiswrapper/1.61/build/ndis.h:19,
                     from /var/lib/dkms/ndiswrapper/1.61/build/loader.c:16:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h: In function ‘raise_irql’:
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:110:40: error: ‘struct task_struct’ has no member named ‘cpus_allowed’; did you mean ‘nr_cpus_allowed’?
     #define tsk_cpus_allowed(tsk) (&(tsk)->cpus_allowed)
                                            ^~~~~~~~~~~~
    /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:672:36: note: in expansion of macro ‘tsk_cpus_allowed’
      cpumask_copy(&info->cpus_allowed, tsk_cpus_allowed(current));
                                        ^~~~~~~~~~~~~~~~
    /var/lib/dkms/ndiswrapper/1.61/build/loader.c: In function ‘load_sys_files’:
    /var/lib/dkms/ndiswrapper/1.61/build/loader.c:157:4: error: too many arguments to function ‘__vmalloc’
        __vmalloc(load_driver->sys_files.size,
        ^~~~~~~~~
    In file included from ./include/asm-generic/io.h:911,
                     from ./arch/x86/include/asm/io.h:375,
                     from ./include/linux/scatterlist.h:9,
                     from ./include/linux/dma-mapping.h:11,
                     from ./include/linux/skbuff.h:31,
                     from ./include/linux/if_ether.h:19,
                     from ./include/uapi/linux/ethtool.h:19,
                     from ./include/linux/ethtool.h:18,
                     from ./include/linux/netdevice.h:37,
                     from /var/lib/dkms/ndiswrapper/1.61/build/ntoskernel.h:25,
                     from /var/lib/dkms/ndiswrapper/1.61/build/ndis.h:19,
                     from /var/lib/dkms/ndiswrapper/1.61/build/loader.c:16:
    ./include/linux/vmalloc.h:111:14: note: declared here
     extern void *__vmalloc(unsigned long size, gfp_t gfp_mask);
                  ^~~~~~~~~
    /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.c: In function ‘set_ndis_auth_mode’:
    /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.c:702:25: warning: this statement may fall through [-Wimplicit-fallthrough=]
       wnd->iw_auth_key_mgmt = IW_AUTH_KEY_MGMT_PSK;
    /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.c:703:2: note: here
      case Ndis802_11AuthModeWPANone:
      ^~~~
    make[1]: *** [scripts/Makefile.build:281: /var/lib/dkms/ndiswrapper/1.61/build/loader.o] Error 1
    make[1]: *** [scripts/Makefile.build:281: /var/lib/dkms/ndiswrapper/1.61/build/iw_ndis.o] Error 1
    make: *** [Makefile:1765: /var/lib/dkms/ndiswrapper/1.61/build] Error 2
    make: Leaving directory '/usr/src/linux-headers-5.8.16-antix.1-amd64-smp'
    
    #54297
    Member
    AvatarWallon

    Now I reinstall the 5.8.16 kernel on the 5.8.16 kernel. So, without uninstalling it first. I still have the dkms problem.

    
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    0 upgraded, 0 newly installed, 4 reinstalled, 0 to remove and 3 not upgraded.
    Need to get 0 B/63.8 MB of archives.
    After this operation, 0 B of additional disk space will be used.
    (Reading database ... 197503 files and directories currently installed.)
    Preparing to unpack .../linux-headers-5.8.16-antix.1-amd64-smp_5.8.16-antix.1-amd64-smp-1_amd64.deb ...
    Unpacking linux-headers-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) over (5.8.16-antix.1-amd64-smp-1) ...
    Preparing to unpack .../linux-image-5.8.16-antix.1-amd64-smp_5.8.16-antix.1-amd64-smp-1_amd64.deb ...
    dkms: removing: broadcom-sta 6.30.223.271 (5.8.16-antix.1-amd64-smp) (x86_64)
    
    -------- Uninstall Beginning --------
    Module:  broadcom-sta
    Version: 6.30.223.271
    Kernel:  5.8.16-antix.1-amd64-smp (x86_64)
    -------------------------------------
    
    Status: Before uninstall, this module version was ACTIVE on this kernel.
    
    wl.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-smp/updates/dkms/
    rmdir: failed to remove 'updates/dkms': 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.
    
    depmod...
    
    update-initramfs...
    
    DKMS: uninstall completed.
    dkms: removing: nvidia-current 460.39 (5.8.16-antix.1-amd64-smp) (x86_64)
    
    -------- Uninstall Beginning --------
    Module:  nvidia-current
    Version: 460.39
    Kernel:  5.8.16-antix.1-amd64-smp (x86_64)
    -------------------------------------
    
    Status: Before uninstall, this module version was ACTIVE on this kernel.
    
    nvidia-current.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-smp/updates/dkms/
    rmdir: failed to remove 'updates/dkms': 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.
    
    nvidia-current-modeset.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-smp/updates/dkms/
    rmdir: failed to remove 'updates/dkms': 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.
    
    nvidia-current-drm.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-smp/updates/dkms/
    rmdir: failed to remove 'updates/dkms': 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.
    
    nvidia-current-uvm.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-smp/updates/dkms/
    rmdir: failed to remove directory '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.
    
    depmod...
    
    DKMS: uninstall completed.
    dkms: removing: virtualbox-guest 6.1.16 (5.8.16-antix.1-amd64-smp) (x86_64)
    
    -------- Uninstall Beginning --------
    Module:  virtualbox-guest
    Version: 6.1.16
    Kernel:  5.8.16-antix.1-amd64-smp (x86_64)
    -------------------------------------
    
    Status: Before uninstall, this module version was ACTIVE on this kernel.
    
    vboxguest.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-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.8.16-antix.1-amd64-smp/updates/
    
    vboxsf.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-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.8.16-antix.1-amd64-smp/updates/
    
    vboxvideo.ko:
     - Uninstallation
       - Deleting from: /lib/modules/5.8.16-antix.1-amd64-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.8.16-antix.1-amd64-smp/updates/
    depmod...
    
    Removing original_module from DKMS tree for kernel 5.8.16-antix.1-amd64-smp (x86_64)
    
    DKMS: uninstall completed.
    Unpacking linux-image-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) over (5.8.16-antix.1-amd64-smp-1) ...
    Preparing to unpack .../libc6-dev_2.28-10_amd64.deb ...
    Unpacking libc6-dev:amd64 (2.28-10) over (2.28-10) ...
    Preparing to unpack .../libelf-dev_0.176-1.1_amd64.deb ...
    Unpacking libelf-dev:amd64 (0.176-1.1) over (0.176-1.1) ...
    Setting up linux-headers-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) ...
    Setting up libelf-dev:amd64 (0.176-1.1) ...
    Setting up libc6-dev:amd64 (2.28-10) ...
    Setting up linux-image-5.8.16-antix.1-amd64-smp (5.8.16-antix.1-amd64-smp-1) ...
    Error! Bad return status for module build on kernel: 5.8.16-antix.1-amd64-smp (x86_64)
    Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
    update-initramfs: Generating /boot/initrd.img-5.8.16-antix.1-amd64-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/sdc1
    I: (UUID=7a9849a2-51d6-4ba3-b83c-b81827894a3d)
    I: Set the RESUME variable to override this.
    
    #54298
    Member
    skidooskidoo

    Is there a “log” file that records an installation when you go through “Software Installer”?

    Unsure which tool is associated with a label “Software Installer”

    /var/log/apt/history.log

    /var/log/apt/term.log
    provides a more detailed accounting, simiilar to what “scrolls on the screen” during commandline apt operations.

    /root/.synaptic/log/
    a timestamped logfile is added in this directory upon exiting synaptic, if any install/remove operations were performed

    ___________________________________________
    When requesting help, pasting the output from inxi -Fzr command will provide important relevant details:
    antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specs

    #54323
    Moderator
    capreacaprea

    I still have the dkms problem

    Error! Bad return status for module build on kernel: 5.8.16-antix.1-amd64-smp (x86_64)
    Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.

    There is no attempt at all here , during the installation, to build the nvidia driver against the kernel , the nvidia driver is not even mentioned here. There are only complaints for the ndiswrapper,which are normal because ndiswrapper is not yet buildable against the latest kernel.

    Please try it the way i described it above

    booting into a working kernel(in your case 4.19.152)
    and reinstalling the new kernel

    `

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