[SOLVED] ModemManager stuck on “starting in system bus” 06 May 2021, 19:22:41 I updated my system today with sudo pacman -Syyu and rebooted it and modemmanager said it was starting in the system bus. How do I fix this? Last Edit: 08 May 2021, 01:38:09 by alium
Re: ModemManager stuck on “starting in system bus” Reply #1 – 06 May 2021, 20:29:31 Did system booting correctly?
Re: ModemManager stuck on “starting in system bus” Reply #2 – 06 May 2021, 21:15:18 Yes. It bootd properly but modemmanager couldn’t detect some files from 5.11.6 so it hung
Re: ModemManager stuck on “starting in system bus” Reply #3 – 06 May 2021, 21:20:26 https://youtu.be/87XWP4Zw1bo this is the outcome
Re: ModemManager stuck on “starting in system bus” Reply #4 – 07 May 2021, 01:22:26 Are you able to switch ttys from that and still actually log in though? I suppose the irq messages are from modem manager? The virtualbox modules failing probably has something to do with you using the fallback kernel I guess. I don't think either of these things failing should block any other service though.Edit: I just realized that we don't actually have modemmanager scripts. Not sure how you are starting it (rc.local)? Last Edit: 07 May 2021, 01:35:25 by Dudemanguy
Re: ModemManager stuck on “starting in system bus” Reply #5 – 07 May 2021, 09:06:41 I can switch ttys but once I do they instantly stop. I have a separate windows partition if that’ll help with anythingedit: does 26 have rc.local?
Re: ModemManager stuck on “starting in system bus” Reply #6 – 07 May 2021, 10:00:53 I would boot in Live ISO, a chroot to installed Artix and simply disabled the service, or modemanager temporarily uninstalled before I fix the problem that causes it.Chroot is always the best way to fix it when it is not booted. 1 Likes
Re: ModemManager stuck on “starting in system bus” Reply #7 – 07 May 2021, 14:52:06 I don't how you are starting ModemManager on bootup, but I suppose it's somehow blocking parts of the boot process. This is one of the reason why service managers exist. I'll add a ModemManager service script later today.
Re: ModemManager stuck on “starting in system bus” Reply #8 – 07 May 2021, 15:37:23 Quote from: Dudemanguy – on 07 May 2021, 14:52:06I don't how you are starting ModemManager on bootup, but I suppose it's somehow blocking parts of the boot process. This is one of the reason why service managers exist. I'll add a ModemManager service script later today.I would prefer it staying off. Not many people need modem these days. It belongs to history.
Re: ModemManager stuck on “starting in system bus” Reply #9 – 07 May 2021, 15:46:05 Quote from: calvinh – on 07 May 2021, 15:37:23I would prefer it staying off. Not many people need modem these days. It belongs to history.It's just a *-s6 script package. You don't have to install it. 1 Likes
Re: ModemManager stuck on “starting in system bus” Reply #10 – 07 May 2021, 16:31:46 It just occurred to me that NetworkManager might actually start ModemManager on its own. Are you using the NetworkManager service 1? Regardless, NetworkManager failing, being stuck, etc. shouldn't block anything. There's exactly one s6-rc call on bootup that starts everything up in parallel (with some dependency handling).Anyways, there's a ModemManager-s6 package now if you find that useful. Last Edit: 07 May 2021, 16:39:07 by Dudemanguy
Re: ModemManager stuck on “starting in system bus” Reply #11 – 07 May 2021, 18:23:33 Quote from: Dudemanguy – on 07 May 2021, 16:31:46It just occurred to me that NetworkManager might actually start ModemManager on its own. Are you using the NetworkManager service 1? Regardless, NetworkManager failing, being stuck, etc. shouldn't block anything. There's exactly one s6-rc call on bootup that starts everything up in parallel (with some dependency handling).Anyways, there's a ModemManager-s6 package now if you find that useful. I don’t have a modem plasma just had it installed for some reason (it was needed by plasma-nm) either way I untinstalled it and now another problem awaits. modules from the old kernel are still needed by s6-rc for some reason. So it also look for those, fails, then the entire machine fails. here is what happened Last Edit: 07 May 2021, 18:28:43 by 1
Re: ModemManager stuck on “starting in system bus” Reply #12 – 07 May 2021, 18:43:17 looks similar like this problems https://bbs.archlinux.org/viewtopic.php?id=235222 https://bugs.archlinux.org/task/55880you can try reinstalling your kernel, maybe it might help ...or try Code: [Select]mkinitcpio -p linuxmaybe it's not related to s6 ...
Re: ModemManager stuck on “starting in system bus” Reply #13 – 07 May 2021, 18:43:29 Quote from: 1 – on 07 May 2021, 18:23:33 I don’t have a modem plasma just had it installed for some reason (it was needed by plasma-nm) either way I untinstalled it and now another problem awaits. modules from the old kernel are still needed by s6-rc for some reason. So it also look for those, fails, then the entire machine fails. here is what happenedThe modules failing to load is a red herring. I just confirmed this on my own machine by putting a fake module in a conf and rebooting. The s6-rc command returns 123, as desired, because the module doesn't exist and a user should know that he has messed up his conf. It does not affect any other part of the boot process however and logging into tty and so on was fine.A couple of observations:1. The crypto_user module not being found is definitely very wrong. It should be in all artix kernels. Something is bad here.2. I have no idea what is printing those "No irq handler" messages, but that looks suspicious. I do not know if that is something important however.My first suggestion would be to fix your kernel at any rate (upgrade since we are on 5.12 now). You should definitely have crypto_user.Edit: A search says that "no irq handler" is kernel related, so I think your kernel is just messed up. Last Edit: 07 May 2021, 18:48:52 by Dudemanguy
Re: ModemManager stuck on “starting in system bus” Reply #14 – 07 May 2021, 19:04:07 Quoteno irq handlerthis is not a issue, i have it too.... me just missing some gpio driver in kernel or what