Artix Linux Forum

Artix Linux => System => Topic started by: 1 on 06 May 2021, 19:22:41

Title: [SOLVED] ModemManager stuck on “starting in system bus”
Post by: 1 on 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?(https://i.imgur.com/0uzsZeN.jpg)
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Arch_user on 06 May 2021, 20:29:31
Did system booting correctly?
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 06 May 2021, 21:15:18
Yes. It bootd properly but modemmanager couldn’t detect some files from 5.11.6 so it hung
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 06 May 2021, 21:20:26
https://youtu.be/87XWP4Zw1bo (https://youtu.be/87XWP4Zw1bo) this is the outcome
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 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)?
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 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 anything
edit: does 26 have rc.local?
Title: Re: ModemManager stuck on “starting in system bus”
Post by: alium on 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.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 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.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: calvinh on 07 May 2021, 15:37:23
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.

I would prefer it staying off. Not many people need modem these days. It belongs to history.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 07 May 2021, 15:46:05
I 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.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 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.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 07 May 2021, 18:23:33
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.
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 (https://youtu.be/4xgQJ6a6jzA)
Title: Re: ModemManager stuck on “starting in system bus”
Post by: alium on 07 May 2021, 18:43:17
looks similar like this problems https://bbs.archlinux.org/viewtopic.php?id=235222 https://bugs.archlinux.org/task/55880

you can try reinstalling your kernel, maybe it might help ...

or try
Code: [Select]
mkinitcpio -p linux

maybe it's not related to s6 ...
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 07 May 2021, 18:43:29
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 (https://youtu.be/4xgQJ6a6jzA)

The 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.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: alium on 07 May 2021, 19:04:07
Quote
no irq handler
this is not a issue, i have it too.... me just missing some gpio driver in kernel or what
Title: [SOLVED] Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 07 May 2021, 19:18:00
"(upgrade since we are on 5.12 now)."
This entire problem came from upgrading
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 07 May 2021, 19:30:43
Partial upgrades aren't supported in Arch or here.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 07 May 2021, 19:38:54
how do i fix the partially upgraded kernel??
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 07 May 2021, 19:44:14
Well we don't know what went wrong here. If you don't want to do a full upgrade yet (-Syu), you can also attempt alium's earlier suggestion.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 07 May 2021, 20:00:27
i did pacman -Syyu and i didnt see anything that caught my eye either.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 07 May 2021, 20:24:37
I think what’s happening is s6 thinks my kernel is still 5.11.16 when I upgraded to 5.12.1 in some .conf so how do I change it?
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 07 May 2021, 21:22:26
yeah s6 on its own is behind the kernel by 3 days
Title: Re: ModemManager stuck on “starting in system bus”
Post by: Dudemanguy on 07 May 2021, 22:10:11
s6? Don't you mean grub? s6 doesn't care about your kernel version.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: strajder on 07 May 2021, 23:57:07
Wait, is this the same live USB system (https://forum.artixlinux.org/index.php/topic,2534.msg16719.html)? If so, try actually installing it.
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 08 May 2021, 00:10:07
Nope, installed system. Also how do I edit grub to fix this?
Title: Re: ModemManager stuck on “starting in system bus”
Post by: 1 on 08 May 2021, 01:24:46
Once I had mounted /dev/sda1 to boot, reinstall Linux, and grub-mkconfig everything is fine now thanks for contributing :)