Announcement

Collapse
No announcement yet.

[SOLVED] Installing linux-headers-6.8.0-47 fails with error 11

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] Installing linux-headers-6.8.0-47 fails with error 11

    Trying to install linux-headers-6.8.0-47-generic via system update constantly fails. The message:

    Code:
    Package failed to install:
    Error while installing package: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
    I had exactly the same problem with the version before and it had obviously to do with dkms. So I deleted dkms and had no WLAN anymore. After setting up a cable connection I could update to 6.8.0-45 as expected. So I reinstalled dkms, but the WLAN still didn’t work until I reinstalled bcmwl-kernel-source. Problem was solved, but I don’t exactly wish to repeat this process with every new kernel version. How could I solve the problem more substantially? (The machine is a 2013 MacBook Pro with Kubuntu 24.4.)

    This is what I get with ~$ sudo apt upgrade

    Code:
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    Calculating upgrade... Done
    The following packages were automatically installed and are no longer required:
    enblend enfuse hugin-data hugin-tools libaec0 libappstream4 libappstreamqt2 libgsl27 libgslcblas0 libhdf5-103-1t64 libhdf5-hl-100t64 libkf5plotting5
    libpano13-3t64 libpano13-bin libsz2 libvigraimpex11 linux-modules-6.8.0-44-generic linux-modules-extra-6.8.0-44-generic mailcap plasma-runners-addons
    Use 'sudo apt autoremove' to remove them.
    Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
    libcjson1 libavdevice60 ffmpeg libpostproc57 libavcodec60 libavutil58
    libswscale7 libswresample4 libavformat60 libavfilter9
    Learn more about Ubuntu Pro at https://ubuntu.com/pro
    The following upgrades have been deferred due to phasing:
    python3-distupgrade ubuntu-release-upgrader-core ubuntu-release-upgrader-qt
    0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
    4 not fully installed or removed.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue? [Y/n] Y
    Setting up linux-image-6.8.0-47-generic (6.8.0-47.47) ...
    Setting up linux-headers-6.8.0-47-generic (6.8.0-47.47) ...
    /etc/kernel/header_postinst.d/dkms:
    * dkms: running auto installation service for kernel 6.8.0-47-generic
    Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
    Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
    Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
    
    Building module:
    Cleaning build area...
    make -j8 KERNELRELEASE=6.8.0-47-generic...(bad exit status: 2)
    ERROR (dkms apport): binary package for applespi: 0.1 not found
    Error! Bad return status for module build on kernel: 6.8.0-47-generic (x86_64)
    Consult /var/lib/dkms/applespi/0.1/build/make.log for more information.
    dkms autoinstall on 6.8.0-47-generic/x86_64 succeeded for broadcom-sta evdi
    dkms autoinstall on 6.8.0-47-generic/x86_64 failed for applespi(10)
    Error! One or more modules failed to install during autoinstall.
    Refer to previous errors for more information.
    * dkms: autoinstall for kernel 6.8.0-47-generic
    ...fail!
    run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-headers-6.8.0-47-generic (--configure):
    installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
    dpkg: dependency problems prevent configuration of linux-headers-generic:
    linux-headers-generic depends on linux-headers-6.8.0-47-generic; however:
    Package linux-headers-6.8.0-47-generic is not configured yet.
    
    dpkg: error processing package linux-headers-generic (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of linux-generic:
    linux-generic depends on linux-headers-generic (= 6.8.0-47.47); however:
    Package linux-headers-generic is not configured yet.
    
    dpkg: error processing package linux-generic (--configure):
    dependency problems - leaving unconfigured
    No apport report written because the error message indicates its a followup error from a previous failure.
    No apport report written because the error message indicates its a followup error from a previous failure.
    Processing triggers for linux-image-6.8.0-47-generic (6.8.0-47.47) ...
    /etc/kernel/postinst.d/dkms:
    * dkms: running auto installation service for kernel 6.8.0-47-generic
    Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
    Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
    Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
    
    Building module:
    Cleaning build area...
    make -j8 KERNELRELEASE=6.8.0-47-generic...(bad exit status: 2)
    ERROR (dkms apport): binary package for applespi: 0.1 not found
    Error! Bad return status for module build on kernel: 6.8.0-47-generic (x86_64)
    Consult /var/lib/dkms/applespi/0.1/build/make.log for more information.
    dkms autoinstall on 6.8.0-47-generic/x86_64 succeeded for broadcom-sta evdi
    dkms autoinstall on 6.8.0-47-generic/x86_64 failed for applespi(10)
    Error! One or more modules failed to install during autoinstall.
    Refer to previous errors for more information.
    * dkms: autoinstall for kernel 6.8.0-47-generic
    ...fail!
    run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-image-6.8.0-47-generic (--configure):
    installed linux-image-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
    No apport report written because MaxReports is reached already
    Errors were encountered while processing:
    linux-headers-6.8.0-47-generic
    linux-headers-generic
    linux-generic
    linux-image-6.8.0-47-generic
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    And these are the current lines in /var/log/dpkg.log:

    Code:
    2024-10-24 21:18:45 startup packages configure
    2024-10-24 21:18:45 configure linux-image-6.8.0-47-generic:amd64 6.8.0-47.47 <none>
    2024-10-24 21:18:45 status half-configured linux-image-6.8.0-47-generic:amd64 6.8.0-47.47
    2024-10-24 21:18:47 status installed linux-image-6.8.0-47-generic:amd64 6.8.0-47.47
    2024-10-24 21:18:47 status triggers-pending linux-image-6.8.0-47-generic:amd64 6.8.0-47.47
    2024-10-24 21:18:47 configure linux-headers-6.8.0-47-generic:amd64 6.8.0-47.47 <none>
    2024-10-24 21:18:47 status half-configured linux-headers-6.8.0-47-generic:amd64 6.8.0-47.47
    2024-10-24 21:18:50 trigproc linux-image-6.8.0-47-generic:amd64 6.8.0-47.47 <none>
    2024-10-24 21:18:50 status half-configured linux-image-6.8.0-47-generic:amd64 6.8.0-47.47

    #2
    Have you tried:

    sudo apt full-upgrade

    DKMS should update automatically

    Please Read Me

    Comment


      #3
      oshunluvr Interesting idea, thanks. Unfortunately I receive a similar, if not identical result:

      Code:
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      Calculating upgrade... Done
      The following packages were automatically installed and are no longer required:
      enblend enfuse hugin-data hugin-tools libaec0 libappstream4 libappstreamqt2 libgsl27 libgslcblas0 libhdf5-103-1t64 libhdf5-hl-100t64 libkf5plotting5
      libpano13-3t64 libpano13-bin libsz2 libvigraimpex11 linux-modules-6.8.0-44-generic mailcap plasma-runners-addons
      Use 'sudo apt autoremove' to remove them.
      Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
      libcjson1 libavdevice60 ffmpeg libpostproc57 libavcodec60 libavutil58
      libswscale7 libswresample4 libavformat60 libavfilter9
      Learn more about Ubuntu Pro at https://ubuntu.com/pro
      The following upgrades have been deferred due to phasing:
      python3-distupgrade ubuntu-release-upgrader-core ubuntu-release-upgrader-qt
      0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
      4 not fully installed or removed.
      After this operation, 0 B of additional disk space will be used.
      Do you want to continue? [Y/n] Y
      Setting up linux-image-6.8.0-47-generic (6.8.0-47.47) ...
      Setting up linux-headers-6.8.0-47-generic (6.8.0-47.47) ...
      /etc/kernel/header_postinst.d/dkms:
      * dkms: running auto installation service for kernel 6.8.0-47-generic
      Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
      Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
      Sign command: /usr/bin/kmodsign
      Signing key: /var/lib/shim-signed/mok/MOK.priv
      Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
      Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
      
      Building module:
      Cleaning build area...
      make -j8 KERNELRELEASE=6.8.0-47-generic...(bad exit status: 2)
      ERROR (dkms apport): binary package for applespi: 0.1 not found
      Error! Bad return status for module build on kernel: 6.8.0-47-generic (x86_64)
      Consult /var/lib/dkms/applespi/0.1/build/make.log for more information.
      dkms autoinstall on 6.8.0-47-generic/x86_64 succeeded for broadcom-sta evdi
      dkms autoinstall on 6.8.0-47-generic/x86_64 failed for applespi(10)
      Error! One or more modules failed to install during autoinstall.
      Refer to previous errors for more information.
      * dkms: autoinstall for kernel 6.8.0-47-generic
      ...fail!
      run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
      dpkg: error processing package linux-headers-6.8.0-47-generic (--configure):
      installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
      dpkg: dependency problems prevent configuration of linux-headers-generic:
      linux-headers-generic depends on linux-headers-6.8.0-47-generic; however:
      Package linux-headers-6.8.0-47-generic is not configured yet.
      
      dpkg: error processing package linux-headers-generic (--configure):
      dependency problems - leaving unconfigured
      dpkg: dependency problems prevent configuration of linux-generic:
      linux-generic depends on linux-headers-generic (= 6.8.0-47.47); however:
      Package linux-headers-generic is not configured yet.
      
      dpkg: error processing package linux-generic (--configure):
      dependency problems - leaving unconfigured
      No apport report written because the error message indicates its a followup error from a previous failure.
      No apport report written because the error message indicates its a followup error from a previous failure.
      Processing triggers for linux-image-6.8.0-47-generic (6.8.0-47.47) ...
      /etc/kernel/postinst.d/dkms:
      * dkms: running auto installation service for kernel 6.8.0-47-generic
      Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
      Deprecated feature: REMAKE_INITRD (/etc/dkms/framework.conf)
      Sign command: /usr/bin/kmodsign
      Signing key: /var/lib/shim-signed/mok/MOK.priv
      Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
      Deprecated feature: REMAKE_INITRD (/var/lib/dkms/applespi/0.1/source/dkms.conf)
      
      Building module:
      Cleaning build area...
      make -j8 KERNELRELEASE=6.8.0-47-generic...(bad exit status: 2)
      ERROR (dkms apport): binary package for applespi: 0.1 not found
      Error! Bad return status for module build on kernel: 6.8.0-47-generic (x86_64)
      Consult /var/lib/dkms/applespi/0.1/build/make.log for more information.
      dkms autoinstall on 6.8.0-47-generic/x86_64 succeeded for broadcom-sta evdi
      dkms autoinstall on 6.8.0-47-generic/x86_64 failed for applespi(10)
      Error! One or more modules failed to install during autoinstall.
      Refer to previous errors for more information.
      * dkms: autoinstall for kernel 6.8.0-47-generic
      ...fail!
      run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
      dpkg: error processing package linux-image-6.8.0-47-generic (--configure):
      installed linux-image-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
      No apport report written because MaxReports is reached already
      Errors were encountered while processing:
      linux-headers-6.8.0-47-generic
      linux-headers-generic
      linux-generic
      linux-image-6.8.0-47-generic
      E: Sub-process /usr/bin/dpkg returned an error code (1)

      Comment


        #4
        This looks meaningful:

        ERROR (dkms apport): binary package for applespi: 0.1 not found

        Please Read Me

        Comment


          #5
          Honestly, unless there's a pressing need you don't have to update to the latest kernel every time one becomes available.

          Please Read Me

          Comment


            #6
            This looks meaningful: ERROR (dkms apport): binary package for applespi: 0.1 not found
            Yes, I recognized that as suspicious too. Just don't know what to do with the hint.

            Honestly, unless there's a pressing need you don't have to update to the latest kernel every time one becomes available.​
            That’s right, I’m living quite well with version 6.8.0-45 so far. But I fear to end up in a loop with no exit, so I would prefer to overcome the annoyance one day not too far away​. I was never good at tolerating weirdly acting systems. Maybe I should work on that, trying yoga or meditation or whatever.

            Comment


              #7
              Just another trial before I give up: How can I either get rid of applespi (which seems to exist at least partially in /var/lib/dkms/applespi/0.1/) or complete the maybe incomplete package or reinstall a working version? Is there any chance to get it fixed or should I just stay with kernel 6.8.0-45 forever? (After all, life is pretty easy with 6.8.0-45, so why worry about it?)
              Last edited by ralfheinz; Oct 28, 2024, 06:56 AM.

              Comment


                #8
                Ask chat gpt (or co-pilot ect...Chat GPT is current up to January, and if you are a subscriber you can add to the KB to get a response). Be sure to copy all the data presented here into the chat bot and see if they can give you some help. Then post results. This would be a last resort.

                Comment


                  #9
                  spiderman I did what you suggested. First I was impressed, later I got a bit frustrated by endless terminal noodlings without a result, but finally it worked, so all in all I’m clearly impressed. After copying all information above I got this as a first result:

                  ChatGPT:

                  The recurring issue with your kernel header updates appears to be tied to a problematic applespi module managed by dkms, which fails to build each time a new kernel version is installed. Here’s a structured approach to potentially resolve this:

                  1. Check the applespi Module Log: To gain more insight into the applespi build error, review the log by running:

                  Code:
                  cat /var/lib/dkms/applespi/0.1/build/make.log
                  This log will detail the specific build failure, which could provide clues for troubleshooting.

                  2. Temporarily Disable the applespi Module in DKMS: If applespi isn’t critical for your hardware functionality, you can try temporarily removing it from dkms to allow kernel headers to install cleanly:

                  Code:
                  sudo dkms remove applespi/0.1 --all
                  Then, proceed with:

                  Code:
                  sudo apt install -f sudo apt upgrade
                  This should install the latest kernel and headers without errors.

                  3. Reinstall DKMS and Related Modules: Since removing dkms previously affected your wireless functionality, it might be beneficial to reinstall dkms and related modules after the kernel update. Use:

                  Code:
                  sudo apt install --reinstall dkms bcmwl-kernel-source
                  This command reinstalls dkms along with the Broadcom Wi-Fi driver.

                  4. Blacklist the applespi Module (Optional): If applespi isn’t required, you can blacklist it to prevent it from loading in future kernel updates:

                  Code:
                  echo "blacklist applespi" | sudo tee /etc/modprobe.d/applespi.conf
                  Reboot the system afterward:

                  Code:
                  sudo reboot

                  5. Run Kernel Update Again: After blacklisting or removing applespi, rerun the kernel update:

                  Code:
                  sudo apt update sudo apt full-upgrade
                  This should help the system bypass the applespi build error and ensure smooth kernel updates without affecting your Wi-Fi. Let me know how this goes, and if you see specific errors in the make.log, feel free to share them for further insights.

                  ME:

                  Affter processing all steps as suggested, everything seemed to be fine except the old WLAN problem. Main difference: The WLAN was at least found this time, and I just couldn’t connect, but received:

                  Code:
                  Wireless Interface wlp2s0. The device could not be configured.
                  What followed was a long back and forth with ChatGPT, not completely uninteresting, but nothing seemed to solve the problem. Until a sudden breakthrough happened:

                  ChatGPT:

                  1. Check Wireless Interface

                  First, let's confirm the wireless interface is properly detected and managed by the system.

                  Code:
                  iwconfig
                  This should show you the status of your wireless interfaces. Ensure that wlp2s0 is listed.

                  2. Check for Blocked Interfaces

                  Sometimes, wireless interfaces can be blocked by software or hardware.

                  Code:
                  rfkill list
                  If you see that the wireless interface is soft or hard blocked, you can unblock it:

                  Code:
                  sudo rfkill unblock all
                  3. Reset Network Manager

                  Since you're using Ubuntu, it might be easier to let Network Manager handle your connections. Let's try restarting it.

                  Code:
                  sudo systemctl restart NetworkManager
                  4. Check Network Manager Configuration

                  Check your Network Manager settings to ensure that it's properly configured for the wireless network.

                  Open the Network Manager GUI by clicking on the network icon in the top-right corner.
                  Select "Settings" or "Edit Connections."
                  Ensure your Wi-Fi network is properly configured (SSID, security type, etc.).

                  5. Remove and Re-add Connection

                  Sometimes, the connection settings can get corrupted. Remove the existing connection and then try adding it again:

                  Remove the Connection:

                  Code:
                  nmcli connection delete <your-SSID>
                  Re-add the Connection:

                  Code:
                  nmcli device wifi connect <your-SSID> password <your-password>
                  ME:

                  Step 5 solved the problem, though it sounds like the most simple approach, it took quite a while til »we« got there. For the moment, all is looking good. The evil applespi seems to be blacklisted and in this respect not to be crucial. Of course I will have to wait til the next kernel version but for now I’m more than satisfied.

                  So thanks a lot for your suggestion that not only solved the problem but led to a (for me) completely new experience!







                  Last edited by ralfheinz; Oct 28, 2024, 07:45 AM.

                  Comment


                    #10
                    I'm so glad to hear of your success. I prefer human interaction vs BOTs, I am totally frustrated with customer service at 99% of companies these days due to their reliance on improperly coded computer programs. I find the current generation of coders lazy (building on and patching the mistakes of their programs) vs fixing the code. I.e. MS the public that they were going to a unix/linux based o/s. Has that happenned? I believe not. Instead they have Symantec writing 60% + of their opperating system and then selling the public a solution to the virus problem they refuse to correct. Anyhow, I am encouraged that things worked out for you. I have had only one success in marketing over the last 35 years and have failed to duplicate that in the past 20. I'm about to launch a Crypto project and am going to let ChatGPT design and help me impliment the marketing. Take care and keep in touch.

                    Comment


                      #11
                      Originally posted by spiderman View Post
                      I am going to let ChatGPT design and help me impliment the marketing. Take care and keep in touch.
                      I have always avoided ChatGPT due to concerns about humans becoming lazy and dependent upon that system. Becoming dependent on something is dangerous, however.... I must say that this solution was clear, precise, more direct than any human I have ever met. (although it was human knowledge to begin with, ChatGPT applied in a clean logical way) I would call this amazing. My concern, with this robot being able to answer questions this good, human interaction is in peril, and it is in a good position to become godlike. *I will save this solution, and I hope this cafe style response is not out of line. Thank you for this experience.

                      Comment


                        #12
                        LLMs and other tools that scrape the internet can be an awful idea when it comes to Linux desktop troubleshooting, considering the vast amount of content that is quickly outdated, the number of solutions users suggest for each problem, and the large percentage of those that are either incorrect or simply do not work. There is so much 'garbage' out there (specifically with Linux) that the results IMO are not trustworthy enough.

                        Comment


                          #13
                          That is interesting claydoh I will look at this more closely. I would like the convenience of that type of search engine, but deep down I have a feeling it should be destroyed. Are you saying that this correct solution was simple luck on the part of chatGPT?

                          Comment


                            #14
                            Luck or not, the way the models work, and where they get their info from includes a LOT of 'junk' content. Think of all the replies on a reddit thread, many that are useless solutions but may have a lot of likes, many that don't work, and a few that are correct.
                            Or all of the cookie-cutter copy-pasta Linus how-to sites that all provide the exact same stiff, but maybe a small error or oudtated info is accidentally left in, and propagated to all the dozens of other sites.

                            How does the language model (what these AI things are) decide which thing is best or appropriate? Bad data diluting the good. This is just mathematical analysis, no actual 'AI'

                            I am just saying don't trust blindly, just like you wouldn't blindly trust some rando bike riding kangaroo in a forum. At least some of these do provide sources for their content.

                            (I grade and rate this sort of thing as a job, and about half the Linux specific things I have seen - not many mind you - have been incorrect in some way.)

                            Comment


                              #15
                              If I had followed this thread past the initial post, about headers, I would have seen the networking issue, and most often the first or second thing I would have suggested is to create a new connection, tbh. Not way down at the bottom at step 5 or whatever.

                              Comment

                              Working...
                              X