Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Debian 11 system get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupdown"

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
belchior
Posts: 6
Joined: 2023-03-08 01:16

[SOLVED] Debian 11 system get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupdown"

#1 Post by belchior »

Hi, this is my first time using Debian. I'm a new linux user that enjoy a lot Debian philosophy, but has only basic knowledge.
I ask you kindly to give me detailed orientations if possible.

My problem: Sometimes, my notebook get stuck and won't boot. Last time i waited 10 minutes and had to reboot. It doesn't happen all the time. I would say 3 out of 10 boots.
I don't know how to provide proper information, but i tried to take a pic of my screen [https://imgur.com/a/wl8hUYZ] during the problem and added some commands outputs here...


lspci

Code: Select all

joao@debian:~$ lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Processor Host Bridge/DRAM Registers [Coffee Lake H] (rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1d.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #14 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 (rev f0)
00:1e.0 Communication controller: Intel Corporation Cannon Lake PCH Serial IO UART Host Controller (rev 10)
00:1f.0 ISA bridge: Intel Corporation HM470 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
06:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5763 (rev 01)
07:00.0 Non-Volatile memory controller: ADATA Technology Co., Ltd. Device 33f8 (rev 03)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 25)
09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
And i also tried a
journalctl -b -1 -p3
to list the last boot problem and it is always related to this :

Code: Select all

root@debian:~# journalctl -b -1 -p3
-- Journal begins at Wed 2023-02-22 04:17:17 -03, ends at Tue 2023-03-07 20:00:51 -03. --
mar 07 19:32:56 debian kernel: integrity: Problem loading X.509 certificate -65
mar 07 19:32:56 debian kernel: integrity: Problem loading X.509 certificate -65
mar 07 19:32:56 debian kernel: 
mar 07 19:32:56 debian kernel: iwlwifi 0000:09:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
mar 07 19:32:56 debian kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
mar 07 19:32:59 debian bluetoothd[828]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
mar 07 19:32:59 debian bluetoothd[828]: sap-server: Operation not permitted (1)
mar 07 19:32:59 debian bluetoothd[828]: Failed to set mode: Blocked through rfkill (0x12)
mar 07 19:34:56 debian systemd[1]: Failed to start Helper to synchronize boot up for ifupdown.
mar 07 19:35:57 debian systemd-udevd[359]: wlan0: Worker [383] processing SEQNUM=3676 killed
mar 07 19:36:53 debian kernel: INFO: task kworker/u16:2:53 blocked for more than 120 seconds.
mar 07 19:36:53 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:36:53 debian kernel: INFO: task kworker/3:2:192 blocked for more than 120 seconds.
mar 07 19:36:53 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:36:53 debian kernel: INFO: task systemd-udevd:383 blocked for more than 120 seconds.
mar 07 19:36:53 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:36:53 debian kernel: INFO: task NetworkManager:706 blocked for more than 120 seconds.
mar 07 19:36:53 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:36:53 debian kernel: INFO: task modprobe:766 blocked for more than 120 seconds.
mar 07 19:36:53 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:36:53 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:38:54 debian kernel: INFO: task kworker/u16:2:53 blocked for more than 241 seconds.
mar 07 19:38:54 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:38:54 debian kernel: INFO: task kworker/3:1:78 blocked for more than 120 seconds.
mar 07 19:38:54 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:38:54 debian kernel: INFO: task kworker/3:2:192 blocked for more than 241 seconds.
mar 07 19:38:54 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:38:54 debian kernel: INFO: task systemd-udevd:383 blocked for more than 241 seconds.
mar 07 19:38:54 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:38:54 debian kernel: INFO: task NetworkManager:706 blocked for more than 241 seconds.
mar 07 19:38:54 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 07 19:38:54 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 07 19:43:18 debian kernel: watchdog: watchdog0: watchdog did not stop!
Last edited by belchior on 2023-04-29 01:28, edited 1 time in total.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#2 Post by sunrat »

You probably need firmware, at least intel-microcode and firmware-iwlwifi for starters.
The easy way (when it works) is to install isenkram and run

Code: Select all

isenkram-autoinstall-firmware
It sometimes doesn't detect all required firmware so let us know how it goes.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

belchior
Posts: 6
Joined: 2023-03-08 01:16

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#3 Post by belchior »

sunrat wrote: 2023-03-08 04:58 You probably need firmware, at least intel-microcode and firmware-iwlwifi for starters.
I have installed Debian non-free iso, maybe the reason i already have these two packages installed.
The easy way (when it works) is to install isenkram and run

Code: Select all

isenkram-autoinstall-firmware
It sometimes doesn't detect all required firmware so let us know how it goes.

This is the output:

Code: Select all

joao@debian:~$ sudo isenkram-autoinstall-firmware
info: looking for firmware file iwl-debug-yoyo.bin requested by kernel
info: some kernel driver requested extra firmware files: iwlwifi-ma-a0-gf-a0-59.ucode iwlwifi-ma-a0-mr-a0-59.ucode iwlwifi-QuQnj-b0-hr-b0-59.ucode iwlwifi-QuQnj-b0-jf-b0-59.ucode iwlwifi-so-a0-gf-a0-59.ucode iwlwifi-so-a0-hr-b0-59.ucode iwlwifi-so-a0-jf-b0-59.ucode iwlwifi-SoSnj-a0-gf4-a0-59.ucode iwlwifi-SoSnj-a0-gf-a0-59.ucode iwlwifi-SoSnj-a0-hr-b0-59.ucode iwlwifi-SoSnj-a0-mr-a0-59.ucode rtl_bt/rtl8723b_config.bin rtl_bt/rtl8723bs_config.bin rtl_bt/rtl8723ds_config.bin rtl_bt/rtl8723ds_fw.bin rtl_bt/rtl8761a_config.bin rtl_bt/rtl8821a_config.bin iwl-debug-yoyo.bin
info: locating packages with the requested firmware files
info: determining whether enabling other components is required
info: No new firmware package with requested firmware detected.

belchior
Posts: 6
Joined: 2023-03-08 01:16

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#4 Post by belchior »

Can i try these fixes?
Bug#959985: ifupdown-pre.service: Failed to start Helper to synchronize boot up for ifupdown
https://linux.debian.bugs.dist.narkive. ... r-ifupdown
[EDITED] firmware: failed to load iwl-debug-yoyo.bin (-2)
viewtopic.php?t=149817
Startup Debian 9 error: `Failed to start Raise network interfaces`
https://unix.stackexchange.com/question ... interfaces

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#5 Post by Aki »

Hello,

I suppose the workaround is suggested in [1]:
In my case, the failing `ifupdown-pre.service` results in the interface `br0`
not being brought up at all, leading to no network after boot.

The best workaround I found was to mask `ifupdown-pre.service`:

Code: Select all

# systemctl mask ifupdown-pre.service
Afterwards, the system boots up without delay and interface `br0` is brought up
at boot.
It would be interesting to understand why ifupdown-pre.service sometime fails.

It could be caused by the wlan0 kernel module that misses some firmware and/or is unstable for certain WiFi connection standards/protocols. Therefore the latter could be related to missing firmware and this could be related/caused by [2].

Hope that helps

---
[1] https://bugs.debian.org/cgi-bin/bugrepo ... bug=959985
[2] viewtopic.php?t=149817
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

belchior
Posts: 6
Joined: 2023-03-08 01:16

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#6 Post by belchior »

Aki wrote: 2023-03-10 14:37 Hello,

I suppose the workaround is suggested in [1]:
In my case, the failing `ifupdown-pre.service` results in the interface `br0`
not being brought up at all, leading to no network after boot.

The best workaround I found was to mask `ifupdown-pre.service`:

Code: Select all

# systemctl mask ifupdown-pre.service
Afterwards, the system boots up without delay and interface `br0` is brought up
at boot.
It would be interesting to understand why ifupdown-pre.service sometime fails.

It could be caused by the wlan0 kernel module that misses some firmware and/or is unstable for certain WiFi connection standards/protocols. Therefore the latter could be related to missing firmware and this could be related/caused by [2].

Hope that helps

---
[1] https://bugs.debian.org/cgi-bin/bugrepo ... bug=959985
[2] viewtopic.php?t=149817
Hi! I did it and those errors are gone...however now i have a new one and it seems worse because i can't even reboot using "Ctrl + Alt + Del" when i get stuck.

Code: Select all

joao@debian:~$ sudo journalctl -b -1 -p3 
-- Journal begins at Wed 2023-02-22 04:17:17 -03, ends at Mon 2023-03-13 14:34:45 -03. --
mar 13 14:18:44 debian kernel: integrity: Problem loading X.509 certificate -65
mar 13 14:18:44 debian kernel: integrity: Problem loading X.509 certificate -65
mar 13 14:18:44 debian kernel: 
mar 13 14:18:47 debian bluetoothd[874]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
mar 13 14:18:47 debian bluetoothd[874]: sap-server: Operation not permitted (1)
mar 13 14:18:47 debian bluetoothd[874]: Failed to set mode: Blocked through rfkill (0x12)
mar 13 14:20:14 debian systemd[1]: Failed to start Hostname Service.
mar 13 14:21:45 debian systemd-udevd[359]: wlan0: Worker [399] processing SEQNUM=3593 killed
mar 13 14:22:41 debian kernel: INFO: task kworker/0:1:14 blocked for more than 120 seconds.
mar 13 14:22:41 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:22:41 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:22:41 debian kernel: INFO: task kworker/u16:2:53 blocked for more than 120 seconds.
mar 13 14:22:41 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:22:41 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:22:41 debian kernel: INFO: task systemd-udevd:399 blocked for more than 120 seconds.
mar 13 14:22:41 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:22:41 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:22:41 debian kernel: INFO: task modprobe:656 blocked for more than 120 seconds.
mar 13 14:22:41 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:22:41 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:22:41 debian kernel: INFO: task NetworkManager:697 blocked for more than 120 seconds.
mar 13 14:22:41 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:22:41 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:24:42 debian kernel: INFO: task kworker/0:1:14 blocked for more than 241 seconds.
mar 13 14:24:42 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:24:42 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:24:42 debian kernel: INFO: task kworker/u16:2:53 blocked for more than 241 seconds.
mar 13 14:24:42 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:24:42 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:24:42 debian kernel: INFO: task kworker/7:1:93 blocked for more than 120 seconds.
mar 13 14:24:42 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:24:42 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:24:42 debian kernel: INFO: task systemd-udevd:399 blocked for more than 241 seconds.
mar 13 14:24:42 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:24:42 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:24:42 debian kernel: INFO: task modprobe:656 blocked for more than 241 seconds.
mar 13 14:24:42 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:24:42 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
mar 13 14:30:35 debian systemd[1]: Assertion 'hashmap_isempty(m->jobs)' failed at src/core/manager.c:1342, function manager_clear_jobs_and_>
mar 13 14:30:35 debian systemd[1]: Caught <ABRT>, dumped core as pid 972.
lines 1-41
I took a pic from my boot as well:
https://imgur.com/a/wNSOHm4
and from the command suggested in the picture:
systemctl status systemd-hostnamed.service
i got:

Code: Select all

● systemd-hostnamed.service - Hostname Service
     Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static)
     Active: inactive (dead)
       Docs: man:systemd-hostnamed.service(8)
             man:hostname(5)
             man:machine-info(5)
             man:org.freedesktop.resolve1(5)
P.S But this output
the command suggested in the picture:
systemctl status systemd-hostnamed.service
i got:
correspond to the next boot attempt, when the notebook in fact succeed to boot. I had to hard reset the notebook. So I don't know if it was supposed to show something different if i had the chance to check the former attempt to boot.

The "no limit" in the picture, when the system gets stuck and dont boot...is there a way to stablish a limit?

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#7 Post by sunrat »

belchior wrote: 2023-03-13 18:03i can't even reboot using "Ctrl + Alt + Del" when i get stuck.
Can you reboot with Magic Sysrq keys?
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

belchior
Posts: 6
Joined: 2023-03-08 01:16

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#8 Post by belchior »

sunrat wrote: 2023-03-13 21:49
belchior wrote: 2023-03-13 18:03i can't even reboot using "Ctrl + Alt + Del" when i get stuck.
Can you reboot with Magic Sysrq keys?
I didn't test this option...
I decided to check and noticed that my Bluetooth has never worked :(
it pairs, but does not connect

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#9 Post by Aki »

Hello,
belchior wrote: 2023-03-13 18:03 [..] now i have a new one and it seems worse because i can't even reboot using "Ctrl + Alt + Del" when i get stuck.

Code: Select all

joao@debian:~$ sudo journalctl -b -1 -p3 
-- Journal begins at Wed 2023-02-22 04:17:17 -03, ends at Mon 2023-03-13 14:34:45 -03. --
mar 13 14:18:44 debian kernel: integrity: Problem loading X.509 certificate -65
mar 13 14:18:44 debian kernel: integrity: Problem loading X.509 certificate -65
mar 13 14:18:44 debian kernel: 
mar 13 14:18:47 debian bluetoothd[874]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
mar 13 14:18:47 debian bluetoothd[874]: sap-server: Operation not permitted (1)
mar 13 14:18:47 debian bluetoothd[874]: Failed to set mode: Blocked through rfkill (0x12)
mar 13 14:20:14 debian systemd[1]: Failed to start Hostname Service.
mar 13 14:21:45 debian systemd-udevd[359]: wlan0: Worker [399] processing SEQNUM=3593 killed
mar 13 14:22:41 debian kernel: INFO: task kworker/0:1:14 blocked for more than 120 seconds.
mar 13 14:22:41 debian kernel:       Tainted: P           OE     5.10.0-21-amd64 #1 Debian 5.10.162-1
mar 13 14:22:41 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[..]
mar 13 14:30:35 debian systemd[1]: Assertion 'hashmap_isempty(m->jobs)' failed at src/core/manager.c:1342, function manager_clear_jobs_and_>
mar 13 14:30:35 debian systemd[1]: Caught <ABRT>, dumped core as pid 972.
lines 1-41
It seems the kernel module (driver) for the wifi network card (iwlwifi ?) gets stuck and systemd gets stuck in return.
belchior wrote: 2023-03-13 18:03 The "no limit" in the picture, when the system gets stuck and dont boot...is there a way to stablish a limit?
This configuration should be in the systemd-hostnamed.service file, but it could be better to boot temporary disabling the kernel module for the wifi
wifi network card. At boot, you can interactively add in grub a kernel parameter to disable the wifi network card, for example the following kernel parameter (if I remember correctly, you are using iwlwifi kernel module):

Code: Select all

modprobe.blacklist=iwlwifi
Otherwise, you can boot grub in recovery mode (single user) and blacklist the iwlwifi kernel module using /etc/modprobe.d/blacklist
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#10 Post by Aki »

@belchior : Have you made any progress ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

belchior
Posts: 6
Joined: 2023-03-08 01:16

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#11 Post by belchior »

Aki wrote: 2023-03-31 15:55 @belchior : Have you made any progress ?
Hi, i apologize for the long time without answering, i had went through some personal problems and kinda spend a whole month without turn on the laptop...

For a while reinstalling the firmware solved the problem, until lately when i decided to get back to work on my photos and it didin't boot again. Same problem apparently.

What actually worked out for me was to upgrade to Debian 12 and install the non-free firmware following these instructions from the debian wiki
https://www.debian.org/releases/jessie/ ... 04.html.en
I downloaded and installed manually and it worked. All errors are gone. Problem solved.

Maybe i could've done the same with Debian 11 idk, but i bumped into this only after decided to try debian bookworm. I wasn't sure about it because i don't care about the latest and greatest, and the important part to me is stability, but even debian testing (at least in its actual stage) is a whole different experience from what i had with manjaro or even ubuntu when i was to scary of linux to consider myself able to try debian. Those were just not my cup of tea as i eventually had issues updating things. Specially Manjaro.

Debian is indeed a special experience that made me finally comfortable in linux and i've been learning a lot with it. Thanks a million to all the community and the devs.

Should i mark this as solved? [How do i do it btw?]

arzgi
Posts: 1185
Joined: 2008-02-21 17:03
Location: Finland
Been thanked: 31 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#12 Post by arzgi »

belchior wrote: 2023-04-28 15:31 Should i mark this as solved? [How do i do it btw?]

Edit your first posts header in the thread, and prepend it with [SOLVED]

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: [Debian 11 Bullseye] System get stuck at boot screen after: "Failed to start Helper to synchronize boot up for ifupd

#13 Post by Aki »

Hello,
belchior wrote: 2023-04-28 15:31
Aki wrote: 2023-03-31 15:55 @belchior : Have you made any progress ?
Hi, i apologize for the long time without answering, i had went through some personal problems and kinda spend a whole month without turn on the laptop...
Don't worry, nice to read you again.
belchior wrote: 2023-04-28 15:31 What actually worked out for me was to upgrade to Debian 12 and install the non-free firmware following these instructions from the debian wiki
https://www.debian.org/releases/jessie/ ... 04.html.en
I downloaded and installed manually and it worked. All errors are gone. Problem solved.
Happy you sort it out, too.
belchior wrote: 2023-04-28 15:31 Debian is indeed a special experience that made me finally comfortable in linux and i've been learning a lot with it. Thanks a million to all the community and the devs.
Happy to hear from you. This is the best result for all of us, much more important than the "technicalities".
belchior wrote: 2023-04-28 15:31 Should i mark this as solved? [How do i do it btw?]
Yes, as @arzgi already pointed out, it would be useful to mark the thread as "Solved" for the benefit of other viewers that are experimenting your same issue.

Happy Debian & happy hacking! :-)
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Post Reply