Delete the kernel and try broadcom-wl from Packman.
You need these 3 rpms:
Thanks! I tried installing those 3 RPMs using Zypper. I then rebooted the computer and enabled Wi-Fi. Right after I enabled Wi-Fi, the system froze.
On a subsequent boot, I did manage to browse the Web for a little while, but then the system froze again.
Was there any additional setup I was supposed to do after installing the 3 RPMs?
If not, then I guess broadcom-wl from Packman doesn’t solve the problem. Thanks for the suggestion, though.
So far, the only thing that has solved the problem for me is using kernel version 5.14.21. But this may not be a good long-term solution for security reasons (right?).
You have not shown any logs, see
Is your Bios/UEFI up to date?
Aha - it turns out that this problem also occurs in the live USB image of Fedora 40, with kernel version 6.8.5-301.fc40.x86_64. So the problem is not specific to openSUSE!
(Side note: The keyboard-backlight freezing issue I mentioned earlier does not seem to occur in Fedora 40, but the Wi-Fi freezing does.)
Now, as for the logs:
I tried running sudo dmesg -W on openSUSE Leap and then enabling Wi-Fi. When the system froze, only one log message was displayed:
sandeep@MacBookAirSandeep:~> sudo dmesg -W
[sudo] password for root:
[ 247.190726] NET: Registered PF_PACKET protocol family
When I rebooted the system after the freeze, sudo journalctl -r -b -1 produced the following output, which does not seem to be very useful:
sandeep@MacBookAirSandeep:~> sudo journalctl -r -b -1 | cat
[sudo] password for root:
Aug 11 12:32:42 MacBookAirSandeep sudo[3530]: pam_unix(sudo:session): session opened for user root by (uid=1000)
Aug 11 12:32:42 MacBookAirSandeep sudo[3530]: sandeep : TTY=pts/0 ; PWD=/home/sandeep ; USER=root ; COMMAND=/usr/bin/dmesg -W
Aug 11 12:32:37 MacBookAirSandeep systemd[2173]: Started VTE child process 3500 launched by gnome-terminal-server process 3481.
Aug 11 12:32:37 MacBookAirSandeep systemd[2173]: Started GNOME Terminal Server.
Aug 11 12:32:37 MacBookAirSandeep dbus-daemon[2243]: [session uid=1000 pid=2243] Successfully activated service 'org.gnome.Terminal'
Aug 11 12:32:36 MacBookAirSandeep systemd[2173]: Starting GNOME Terminal Server...
Aug 11 12:32:36 MacBookAirSandeep dbus-daemon[2243]: [session uid=1000 pid=2243] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.85' (uid=1000 pid=3472 comm="/usr/bin/gnome-terminal ")
Aug 11 12:32:36 MacBookAirSandeep systemd[2173]: Started Application launched by gnome-shell.
Aug 11 12:32:35 MacBookAirSandeep systemd[1]: Finished Check if mainboard battery is Ok.
Aug 11 12:32:35 MacBookAirSandeep systemd[1]: check-battery.service: Deactivated successfully.
Aug 11 12:32:35 MacBookAirSandeep systemd[1]: Starting Check if mainboard battery is Ok...
Aug 11 12:32:35 MacBookAirSandeep systemd[2173]: gnome-terminal-server.service: Consumed 1.368s CPU time.
Aug 11 12:32:02 MacBookAirSandeep systemd[2173]: Started VTE child process 3408 launched by gnome-terminal-server process 3389.
Aug 11 12:32:02 MacBookAirSandeep systemd[2173]: Started GNOME Terminal Server.
Aug 11 12:32:02 MacBookAirSandeep dbus-daemon[2243]: [session uid=1000 pid=2243] Successfully activated service 'org.gnome.Terminal'
Aug 11 12:32:01 MacBookAirSandeep systemd[2173]: Starting GNOME Terminal Server...
Aug 11 12:32:01 MacBookAirSandeep dbus-daemon[2243]: [session uid=1000 pid=2243] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.81' (uid=1000 pid=3380 comm="/usr/bin/gnome-terminal ")
Aug 11 12:32:01 MacBookAirSandeep systemd[2173]: Started Application launched by gnome-shell.
Aug 11 12:32:00 MacBookAirSandeep systemd[2173]: gnome-terminal-server.service: Consumed 7.303s CPU time.
Aug 11 12:31:05 MacBookAirSandeep sudo[3365]: pam_unix(sudo:session): session closed for user root
Aug 11 12:31:05 MacBookAirSandeep sudo[3365]: pam_unix(sudo:session): session opened for user root by (uid=1000)
Aug 11 12:31:05 MacBookAirSandeep sudo[3365]: sandeep : TTY=pts/1 ; PWD=/home/sandeep ; USER=root ; COMMAND=/usr/bin/dmesg
Aug 11 12:31:00 MacBookAirSandeep systemd[2173]: Started VTE child process 3339 launched by gnome-terminal-server process 3232.
Aug 11 12:30:57 MacBookAirSandeep gnome-shell[2331]: See https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html for details
Aug 11 12:30:57 MacBookAirSandeep gnome-shell[2331]: libinput error: event13 - bcm5974: kernel bug: Touch jump detected and discarded.
[...]
When I press Control+Alt+F2 while the system is frozen, nothing happens.
As for whether the EFI is up to date:
I booted into macOS High Sierra on the same computer (it is a dual-boot setup) and checked the system information from there. It shows that the computer is a MacBookAir4,1 with boot ROM version 135.0.0.0.0. That agrees with this website, so hopefully that means it is up to date: Which EFI firmware should your Mac be using? (version 3) – The Eclectic Light Company
I just noticed that Control+Alt+F2 does nothing even when the system is responding. Did you mean Control+Alt+F3? This switches to text mode when the system is responding, at which point I can press Control+Alt+F2 to go back to graphical mode.
But once the system freezes, pressing Control+Alt+F3 does not do anything.
I just found this page on Ask Ubuntu which looks relevant:
1 Like
Update: I have mostly given up on this for now. I have switched back to kernel 5.14.21, and the MacBook Air is usable again.
Hopefully this will get patched in an upcoming Linux kernel version. If not, I will probably just keep the old kernel for now and accept the security risk. At least it isn’t my primary computer.
Thank you, everyone, for the help and suggestions you provided! If anyone has any further insight, I would still be interested.
Have you reported your problem anywhere?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.