MX Linux Forum

Posted: **Tue Apr 04, 2023 10:01 pm**

When istalling a new kernel with the MX package installer I see this error.

Error! Bad return status for module build on kernel
bad exit status: 2

for multiple modules, is this a problem I can or should fix?

Posted: **Tue Apr 04, 2023 10:11 pm**

There are some dkms packages that get rebuilt for each kernel. Newer versions of these are in the AHS repository along with the new kernels. Any of these dkms packages that you actually use should be updated. Ones that you don't can be removed.
Posting your Quick System Info will show us your hardware so we can tell which, if any you need for basic operation.
Others (virtualbox-dkms for example) will depend on whether you actually use the program.

Posted: **Tue Apr 04, 2023 10:12 pm**

Please post your Quick System Info before we can diagnose any errors/issues.

*you beat me by 22 seconds @timkb4cq

Posted: **Tue Apr 04, 2023 11:31 pm**

Code: Select all

Snapshot created on: 20220924_1134
System:    Kernel: 5.10.0-18-amd64 [5.10.140-1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet persist_static 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_bare_systemd_only_x64 Wildflower Sep 25  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Apple product: MacBookPro9,2 v: 1.0 serial: <filter> Chassis: 
           type: 10 v: Mac-6F01561E16C75D06 serial: <filter> 
           Mobo: Apple model: Mac-6F01561E16C75D06 v: MacBookPro9,2 serial: <filter> UEFI: Apple 
           v: 229.0.0.0.0 date: 07/24/2019 
Battery:   ID-1: BAT0 charge: 51.4 Wh (96.8%) condition: 53.1/62.9 Wh (84.5%) volts: 12.3 
           min: 10.9 model: SMP bq20z451 type: Li-ion serial: N/A status: Full cycles: 952 
CPU:       Info: Dual Core model: Intel Core i7-3520M bits: 64 type: MT MCP arch: Ivy Bridge 
           family: 6 model-id: 3A (58) stepping: 9 microcode: 21 cache: L2: 4 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23148 
           Speed: 2504 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 2504 2: 3489 3: 3423 
           4: 3393 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           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: Retpolines, IBPB: conditional, IBRS_FW, STIBP: 
           conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Apple driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:0166 class-ID: 0300 
           Device-2: Apple FaceTime HD Camera type: USB driver: uvcvideo bus-ID: 1-1.1:3 
           chip-ID: 05ac:8509 class-ID: 0e02 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.3x8.3") 
           s-diag: 398mm (15.7") 
           Monitor-1: LVDS-1 res: 1280x800 hz: 60 dpi: 114 size: 286x179mm (11.3x7.0") 
           diag: 337mm (13.3") 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.3.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel 
           v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Broadcom NetXtreme BCM57765 Gigabit Ethernet PCIe driver: tg3 v: kernel 
           port: efa0 bus-ID: 01:00.0 chip-ID: 14e4:16b4 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Broadcom BCM4331 802.11a/b/g/n vendor: Apple AirPort Extreme driver: wl 
           v: kernel modules: bcma port: efa0 bus-ID: 02:00.0 chip-ID: 14e4:4331 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Apple Bluetooth USB Host Controller type: USB driver: btusb v: 0.8 
           bus-ID: 2-1.8.1.3:9 chip-ID: 05ac:821d class-ID: fe01 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 
           sub-v: 229a hci-v: 4.0 rev: 170f 
           Info: acl-mtu: 1021:6 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 247.34 GiB used: 10.27 GiB (4.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS543225A7A384 size: 232.89 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 
           serial: <filter> rev: A60W scheme: MBR 
           ID-2: /dev/sdc maj-min: 8:32 type: USB vendor: PNY model: USB 2.0 FD size: 14.46 GiB 
           block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP 
           scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 65.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 1845 lib: 916 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
Info:      Processes: 237 Uptime: 1h 22m wakeups: 2 Memory: 7.68 GiB used: 1.74 GiB (22.7%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

Posted: **Tue Apr 04, 2023 11:32 pm**

I do intend to use virtualbox and kvm/qemu.

Posted: **Wed Apr 05, 2023 12:37 am**

mxpi.log

Posted: **Wed Apr 05, 2023 2:37 am**

Moved to appropriate forum section.

Posted: **Wed Apr 05, 2023 5:33 am**

It seems like I no longer have wifi after activating the new kernel.

Posted: **Wed Apr 05, 2023 6:15 am**

https://forum.mxlinux.org/viewtopic.php?t=74744

Please don't spread the same issue across multiple threads.

Posted: **Wed Apr 05, 2023 7:33 am**

Okay, that topic was about firefox, and I only mentioned this issue there because system report is here.

I apologize...

Does someone know which modules I need to fix and how?

This seems like a similar issue:

https://forum.mxlinux.org/viewtopic.php ... el#p715833

Posted: **Wed Apr 05, 2023 8:01 am**

from the log you posted, it would be the realtek rtl88*-dkms packages that fail to build, plus the broadcom-sta-dkms package. likely virtualbox would as well.

you aren't using the realtek rtl88* drivers, but you are using the broadocom-sta driver (wl).

if you want to use the ahs 6.1 kernel, you might as well enable the ahs repo and update everything. you'll get the firmware that matches the kernel, plus updated mesa packages and the dkms driver packages that will build on that kernel.

otherwise stick to the supported 5.10 kernel. looking at your hardware, I'm not seeing a particularly compelling reason to go to 6.1 if the 5.10 is already working.

Posted: **Wed Apr 05, 2023 8:38 am**

@dolphin_oracle,

Thanks, I'll just try to use it as is then. I only really care about getting updates to patch security issues and to make a system that actually works.

If I did want to upgrade, is the solution just what you said? I would update to the ahs version of stuff by installing those packages and then reinstall the kernel?

Posted: **Wed Apr 05, 2023 9:17 am**

to use ahs, you enable ahs repo, do updates as usual, and then install the kernel if you wish.

the 5.10 kernel gets security patches, FWIW. and it auto-updates over time.

Posted: **Wed Apr 05, 2023 2:12 pm**

@dolphin_oracle ,

Thank you. Should I upgrade to 5.10 - 21 to get the security updates or is version 18 better?

Posted: **Wed Apr 05, 2023 2:32 pm**

je55eah wrote: Wed Apr 05, 2023 2:12 pm @dolphin_oracle ,

Thank you. Should I upgrade to 5.10 - 21 to get the security updates or is version 18 better?

if the linux-image-amd64 metapackage is installed, the latest 5.10 kernel should get installed automatically with updates. yes, I would run the latest 5.10 kernel.

Posted: **Wed Apr 05, 2023 3:20 pm**

It looks like many kernel wi-fi drivers involves the kernel module "wl", which unfortunately has the same name as the broadcom-sta driver, but the OP's QSI shows that they have a in-kernel "bcma" driver:

Code: Select all

           Device-2: Broadcom BCM4331 802.11a/b/g/n vendor: Apple AirPort Extreme driver: wl 
           v: kernel modules: bcma port: efa0 bus-ID: 02:00.0 chip-ID: 14e4:4331 class-ID: 0280 
           IF: wlan0 state: up mac: <filter>

Or that they have two drivers fighting over the device, in which case MX Network Assistant can help diagnose and fix the problem.

Posted: **Sat Apr 08, 2023 5:47 am**

Thanks for looking at it @Stevo

Posted: **Mon Apr 10, 2023 9:53 pm**

To enable the ahs repo, do I disable the bullseye main non-free and enable bullseye ahs on this screen?

Posted: **Mon Apr 10, 2023 9:59 pm**

just enable ahs. you want to keep the mx main repo enabled.

Posted: **Thu Apr 13, 2023 2:57 pm**

This seems to have worked perfectly. Thank you.

MX Linux Forum

Error! Bad return status for module build on kernel

Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel [Solved]

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel

Re: Error! Bad return status for module build on kernel