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 6 posts - 16 through 21 (of 21 total)
  • Author
  • #54334

    Dear caprea,

    Each time, for my post #54294 and for my post #54297, I booted the PC with kernel 4.19.152. I could not do otherwise.

    Best regards,


    Maybe I got it wrong, but I think caprea means you install al kernels you want to use, and you reinstall nvidia drivers (please wait for caprea to confirm). This should build the drivers for each kernel.

    Alternatively, with all kernels installed, you can try to use the dkms tool to recompile the nvidia driver for all kernels. First check to see if the nvidia-kernel-dkms package is installed
    apt policy nvidia-kernel-dkms
    (you should be able to see something in “Installed:”. If it says “Installed: none”, then there is no dkms package installed for nvidia to recompile)
    If there is an installed version, run the dkms autoinstall command
    sudo dkms autoinstall
    If there is none, maybe you need to install it (better ask for caprea’s input)


    Everything looks good.

    $ uname -a
    Linux MSI 4.19.152-antix.1-amd64-smp #1 SMP PREEMPT Sun Oct 18 12:37:14 EEST 2020 x86_64 GNU/Linux
    $ apt policy nvidia-kernel-dkms
      Installed: 460.39-1~bpo10+1
      Candidate: 460.39-1~bpo10+1
      Version table:
     *** 460.39-1~bpo10+1 100
            100 buster-backports/non-free amd64 Packages
            100 /var/lib/dpkg/status
         418.181.07-1 500
            500 buster/non-free amd64 Packages
    $ sudo dkms autoinstall

    I have no clue why it doesn’t work for you. One difference I see is, I reinstalled kernel and headers with synaptic, not package-installer.
    Edit: Is it possible the nvidia-driver is installed on the kernel 5.8.16 and that is not your problem at all ?
    Please dkms status

    • This reply was modified 2 weeks, 6 days ago by caprea.
    $ dkms status
    broadcom-sta,, 4.19.152-antix.1-amd64-smp, x86_64: installed
    broadcom-sta,, 4.9.235-antix.1-amd64-smp, x86_64: installed
    ndiswrapper, 1.61, 4.19.152-antix.1-amd64-smp, x86_64: installed
    ndiswrapper, 1.61, 4.9.235-antix.1-amd64-smp, x86_64: installed
    nvidia-current, 460.39, 4.19.152-antix.1-amd64-smp, x86_64: installed
    virtualbox-guest, 6.1.16, 4.19.152-antix.1-amd64-smp, x86_64: installed (original_module exists)
    virtualbox-guest, 6.1.16, 4.9.235-antix.1-amd64-smp, x86_64: installed

    I also have the missing policy.33 report while initialising the boot on my installed 19.3 PC with kernel 5.8.16, but it causes no problems that I am aware of and proceeds to boot and stay booted. I am merely curious as to why this has begun to appear while I have not seen it on previous releases. But this is a new build so it has only ever run 19.3. and I am not in a position to tinker with kernel versions or graphics drivers for other reasons.

    It has an Nvidia graphics card properly installed, is this warning indeed related to the presence of this card or is this irrelevant?

    I am building another dual-cpu PC and will need to source a graphics card. Can anyone recommend an economical chipset to go for or a specific card that is not Nvidia? I have no quarrel with Nvidia but it seems sensible to ask the advice of others who may have travelled this route and perhaps found something more suitable. My use of graphics is very limited and any old cheapo card will in fact be suitable.

    Thanks in advance for all responses.

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