WiFi disabled after disconnected power

Support Network
1

Hey everyone :slight_smile:

I am one of those energy saving freaks, that uses a switchable power socket which turns off all connected devices (monitor, TV, amplifier) over night, to prevent them from running in standby.

I have recently setup a new PC and with this one, a strange behaviour occurs: Every first boot after the power has been disconnected, the WiFi device is disabled. Once restarted, it reappears and works fine. While restarting, system-d halts for a couple of minutes showing the following error:

systemd-shutdown[1]: Waiting for process: 312 (systemd-udevd), 341 ((udev-worker))
mt7921e 0000:0d:00.0: not ready 65535ms after FLR, giving up
mt7921e 0000:0d:00.0: Direct firmware load for mediatek/WIFI_RAM_CODE_MT7922_1.bin failed
mt7921e 0000:0d:00.0: Direct firmware load for mediatek/WIFI_MT7922_patch_mcu_1_1_hdr failed
mt7921e 0000:0d:00.0: hardware init failed

Any ideas what might be the root of this problem?
Any help or hint is much appreciated, no matter how unseemingly related.

All the best!

2

This may not be easily answered without context; system details, and logs. The following links will help you find and post other information that will likely help:

Please try to post full logs, and other information rather than just what you think might be relevent. Cheers.

1 Like
3

Thank you!
What do you think would be helpful specifically?

Here is an $ inxi -mFxxxzzz for a start.

System:
  Kernel: 6.6.2-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11
    info: latte-dock wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
    base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: B650 GAMING X AX v: N/A serial: N/A
  Mobo: Gigabyte model: B650 GAMING X AX v: x.x serial: N/A UEFI: American
    Megatrends LLC. v: F9d date: 09/14/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 32 GiB available: 31.09 GiB used: 7.53 GiB (24.2%)
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM 0 type: no module installed
  Device-2: DIMM 1 type: DDR5 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 4800 MT/s volts: 1.1 width (bits): data: 64 total: 64
    manufacturer: N/A part-no: 6000 C36 Series serial: <filter>
  Device-3: DIMM 0 type: no module installed
  Device-4: DIMM 1 type: DDR5 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 4800 MT/s volts: 1.1 width (bits): data: 64 total: 64
    manufacturer: N/A part-no: 6000 C36 Series serial: <filter>
CPU:
  Info: 6-core model: AMD Ryzen 5 7500F bits: 64 type: MT MCP smt: enabled
    arch: Zen 4 rev: 2 cache: L1: 384 KiB L2: 6 MiB L3: 32 MiB
  Speed (MHz): avg: 1761 high: 4144 min/max: 400/5074 volts: 1.3 V
    ext-clock: 100 MHz cores: 1: 400 2: 4139 3: 400 4: 400 5: 3308 6: 400 7: 400
    8: 4144 9: 400 10: 3301 11: 400 12: 3450 bogomips: 88668
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA AD104 [GeForce RTX 4070] vendor: Palit Microsystems
    driver: nvidia v: 535.129.03 arch: Lovelace pcie: speed: 16 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:2786 class-ID: 0300
  Display: server: X.Org v: 21.1.9 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1600 s-dpi: 109 s-size: 894x372mm (35.20x14.65")
    s-diag: 968mm (38.12") monitors: <missing: xrandr>
  Monitor-1: Unknown-1 size-res: N/A modes: 1024x768
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 535.129.03
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070/PCIe/SSE2
  API: Vulkan v: 1.3.269 layers: 1 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2786
Audio:
  Device-1: NVIDIA vendor: Palit Microsystems driver: snd_hda_intel v: kernel
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22bc
    class-ID: 0403
  Device-2: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 0b:00.0 chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.6.2-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 0.3.85 status: n/a (root, process)
    with: pipewire-media-session status: active
  Server-3: PulseAudio v: 16.1 status: active (root, process)
    with: pulseaudio-alsa type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 0c:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: enp12s0 state: down mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 0d:00.0
    chip-ID: 14c3:0616 class-ID: 0280
  IF: wlp13s0 state: up mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 bus-ID: 1-9:7 chip-ID: 0e8d:0616 class-ID: e001
    serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 2.96 TiB used: 612.18 GiB (20.2%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB
    size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 44.9 C scheme: GPT
  ID-2: /dev/nvme1n1 vendor: Seagate model: FireCuda 530 ZP2000GM30013
    size: 1.82 TiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: SU6SM005 temp: 37.9 C scheme: GPT
  ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
    size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 47.9 C scheme: GPT
Partition:
  ID-1: / size: 227.64 GiB used: 38.22 GiB (16.8%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 548.9 MiB used: 296 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 45.4 C mobo: 42.0 C gpu: nvidia temp: 43 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
  Processes: 347 Uptime: 4h 36m wakeups: 0 Init: systemd v: 254
  default: graphical Compilers: gcc: 13.2.1 clang: 16.0.6 Packages: 1356
  pm: pacman pkgs: 1320 pm: flatpak pkgs: 36 Shell: Sudo (sudo) v: 1.9.15p2
  default: Bash v: 5.2.15 running-in: konsole inxi: 3.3.31

Regarding error logs, I already tried to find in the kernel and journald log via KSystemlog, to no avail. And I can’t seem to find the error in $ dmesg. Might it be hidden somewhere in the systemd logs?
Sorry, I am pretty noobish about this…

4

are you dual booting with windows?

5

Yes, but I always perform a complete shutdown before starting one or the other. This problem occurs when using Linux, shutting down, disconnecting power and then booting Linux again.

6

Try this:

journalctl --boot=-1 --priority=3 --catalog --no-pager

This switchable power socket you describe: Is your Internet router/modem also connected to that? It may be that WiFi simply isn’t ready at first boot, but at the next boot, it is.

This procedure should allow you to reboot from Windows to Linux with a lesser degree of complication; In Windows, disable Microsoft’s Fast Startup (a hibernation variant) using this command from a Cmd Prompt (with elevated privileges):

powercfg /h off

… and reboot; once into Windows; and then any OS you choose. When enabled, Fast Startup frequently plays havoc in a multiboot environment.

Additionally, disable Fast Boot in your BIOS, as indicated by Megavolt; I typically do this regardless of the OS being used. :point_down:

7

Fastboot in the UEFI Settings enabled? Linux doesn’t like skipping initialization steps, since it doesn’t save the state (like Windows), but pull it every time.

8

so check if fast startup is disabled in windows, and fast boot disabled in your bios/uefi - you may not have this option…

9

@soundofthunder and @megavolt and @brahma
Thank you all for your kind input.

1.) Fastboot in UEFI is disabled, I hate the conondrums with Fastboot skipping hardware inits. It’s never worth it.
2.) Windows Fast Startup / Hibernation is both disabled, of course
3.) Here is the $ journalctl --boot=-1 --priority=3 --catalog --no-pager
The error does not show up here though. Is there a way to see the log from shutdown?

Dez 02 12:45:02 BLASI kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP7._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 02 12:45:02 BLASI kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 02 12:45:02 BLASI kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 02 12:45:02 BLASI kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 02 12:45:02 BLASI kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 02 12:45:02 BLASI kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 02 12:45:02 BLASI kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Dez 02 12:45:02 BLASI kernel: 
Dez 02 12:45:02 BLASI kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 0
Dez 02 12:45:03 BLASI nmbd[589]: [2023/12/02 12:45:03.688394,  0] ../../source3/nmbd/nmbd.c:901(main)
Dez 02 12:45:03 BLASI nmbd[589]:   main: nmbd version 4.19.2 started.
Dez 02 12:45:03 BLASI nmbd[589]:   Copyright Andrew Tridgell and the Samba Team 1992-2023
Dez 02 12:45:03 BLASI nmbd[589]: [2023/12/02 12:45:03.692075,  0] ../../lib/util/become_daemon.c:150(daemon_status)
Dez 02 12:45:03 BLASI nmbd[589]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
Dez 02 12:45:03 BLASI nmbd[589]: [2023/12/02 12:45:03.692269,  0] ../../source3/nmbd/nmbd_subnetdb.c:252(create_subnets)
Dez 02 12:45:03 BLASI nmbd[589]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Dez 02 12:45:06 BLASI systemd[690]: /run/user/1000/systemd/generator.late/app-Rainlendar@autostart.service:18: WorkingDirectory= path is not absolute, ignoring: 
Dez 02 12:45:06 BLASI pulseaudio[731]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dez 02 12:45:06 BLASI pulseaudio[731]: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA developers.
Dez 02 12:45:06 BLASI pulseaudio[731]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Dez 02 12:45:07 BLASI libddcutil[851]: i2c_check_businfo_connector() failed for bus 3
Dez 02 12:45:07 BLASI libddcutil[851]: i2c_check_businfo_connector() failed for bus 4
Dez 02 12:45:07 BLASI libddcutil[851]: busno=3, sleep-multiplier =  1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Dez 02 12:45:24 BLASI bluetoothd[652]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
Dez 02 12:45:24 BLASI bluetoothd[652]: bap: Operation not supported (95)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to clear UUIDs: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to set mode: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:24 BLASI bluetoothd[652]: Failed to add UUID: Failed (0x03)
Dez 02 12:45:25 BLASI bluetoothd[652]: Failed to set mode: Failed (0x03)
Dez 02 12:45:28 BLASI pulseaudio[731]: org.bluez.BatteryProviderManager1.UnregisterBatteryProvider() Failed: org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying
Dez 02 12:45:29 BLASI pulseaudio[731]: Error opening PCM device front:1: No such file or directory
Dez 02 12:45:30 BLASI kernel: watchdog: watchdog0: watchdog did not stop!

I would like to lead the focus away from Dual-Boot as culprit: Windows is not involved. The error occurs when booting from Linux to Linux, with a power disconnection in between. The error does NOT occur, when switching between OS or booting from Linux to Linux - as long as the power has not been disconnected between boot cycles.

Thank you all for your suggestions so far!

10

does it happen with different kernels?
maybe some setting in bios/uefi?

11

This time there is no problem with mt7921e?

Anyhow… I saw also weird bugs where you need to add the PXE/Network Boot to be placed first in the boot priority, so that the integrated wifi module gets initialized properly. That might be the case here? Or maybe it just takes longer to “warm up” after a cold boot.

12

This command should generate logs that may or may not be useful; please post the output.

13

@brahma Yes, happens with Kernels from 5+ to 6 current.
@megavolt Thanks for the idea about PXE boot priority bug. I will try
@soundofthunder This is

journalctl --boot=-1 --priority=3 --catalog --no-pager

Dez 02 15:13:55 BLASI kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP7._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 02 15:13:55 BLASI kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 02 15:13:55 BLASI kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 02 15:13:55 BLASI kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 02 15:13:55 BLASI kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20230628/dswload2-326)
Dez 02 15:13:55 BLASI kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Dez 02 15:13:55 BLASI kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Dez 02 15:13:55 BLASI kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 1
Dez 02 15:13:55 BLASI kernel: 
Dez 02 15:13:57 BLASI bluetoothd[698]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
Dez 02 15:13:57 BLASI bluetoothd[698]: bap: Operation not supported (95)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to clear UUIDs: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to set mode: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:57 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:59 BLASI systemd[785]: /run/user/1000/systemd/generator.late/app-Rainlendar@autostart.service:18: WorkingDirectory= path is not absolute, ignoring: 
Dez 02 15:13:59 BLASI pulseaudio[827]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dez 02 15:13:59 BLASI pulseaudio[827]: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA developers.
Dez 02 15:13:59 BLASI pulseaudio[827]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Dez 02 15:13:59 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:59 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:59 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:13:59 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI bluetoothd[698]: Failed to add UUID: Failed (0x03)
Dez 02 15:14:00 BLASI libddcutil[950]: i2c_check_businfo_connector() failed for bus 3
Dez 02 15:14:00 BLASI libddcutil[950]: i2c_check_businfo_connector() failed for bus 4
Dez 02 15:14:01 BLASI libddcutil[950]: busno=3, sleep-multiplier =  1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Dez 02 15:14:01 BLASI bluetoothd[698]: Failed to set mode: Failed (0x03)
Dez 02 15:14:03 BLASI wpa_supplicant[786]: bgscan simple: Failed to enable signal strength monitoring
Dez 02 15:14:03 BLASI nmbd[1270]: [2023/12/02 15:14:03.539062,  0] ../../source3/nmbd/nmbd.c:901(main)
Dez 02 15:14:03 BLASI nmbd[1270]:   main: nmbd version 4.19.2 started.
Dez 02 15:14:03 BLASI nmbd[1270]:   Copyright Andrew Tridgell and the Samba Team 1992-2023
Dez 02 15:14:03 BLASI smbd[1280]: [2023/12/02 15:14:03.562506,  0] ../../source3/smbd/server.c:1746(main)
Dez 02 15:14:03 BLASI smbd[1280]:   smbd version 4.19.2 started.
Dez 02 15:14:03 BLASI smbd[1280]:   Copyright Andrew Tridgell and the Samba Team 1992-2023
Dez 02 23:06:32 BLASI pulseaudio[827]: org.bluez.BatteryProviderManager1.UnregisterBatteryProvider() Failed: org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying

@megavolt Was on the right track: Impatient as I was, I never waited. I just started my computer this morning, went down and made a coffee - voila, the wifi device was available.

So, the strange behaviour can now be reduced to this: The WiFi-Device takes a couple of minutes before it is available at first boot IF the power has been disconnected before. The strange thing about it is, that when the power has not been disconnected, it is always ready immediately after login, no matter how long the PC has been shut down before.

Nevertheless, I consider this problem solved. Obviously, it takes just a tiny bit longer for the hardware to be initialized after a power disconnecting - for whatever reason.

Thank you all for your insightful recommendations!

1 Like
14

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.