In the end of November 2022 (1 year ago), I switched from MacOs to Linux (Debian with KDE Plasma) on my MacBook.

No regret! Was a very good decision.

I think, I’ll never go back.

Experience:

  • I did not know about KDE Plasma until 1 year ago. The picture in my head about Linux was pretty much GNOME. I’m a huge fan of KDE Plasma now. KDE Plasma 6 in 2024 will probably be awesome.
  • The GitHub repository “Awesome-Linux-Software” was awesome during the first weeks. It made me realize that most of the stuff I was already using, is also available for Linux. Only software I had to leave behind: Affinity Designer (IMO far more intuitive to use than GIMP, sorry FOSS community) and Visual Studio for Mac (which is dead anyway)
  • The only advanced thing I had to do in the beginning: My WIFI connection is always gone when I close my MacBook, but there is not automatic reconnect when I reopen it. None of the usual stuff recommended when using Debian on a MacBook helped. So, I had to write a service that checks for this (something with rmmod, modprobe, brcmfmac, …). Probably too much for a casual user and hopefully not necessary for them…

TODO in the next year:

  • Trying out gaming on Linux, maybe buying a Steam Deck
  • Migrating to KDE Plasma 6 (and switching to Wayland)
  • Recommending our religion Linux to others
  • MonkderZweite@feddit.ch
    2·
    11 months ago

    Guess that was udev and not modprobe, where changes made are picked up immediately? My bad.

    What i do have though, is a bunch of scripts in /etc/modprobe.d, with a comment:

    # 'modinfo -p your-module' to list possible values
# 'systool -m your-module -av' to list active modules
# modinfo -p your-module |sort |awk -F':' '{print "\n# "$2"\n#options your-module "$1"="}' for a preset

    Maybe there is a module-functionality active that causes trouble? Btw, dmesg -H says nothing? Looks like brcmfmac is troublesome generally (of course broadcum, huh).

    Bttw: if you can’t /etc/modprobe for some reason, you can load module settings as kernel parameters (via Grub or whatever) like module.option=value.

    About the wakeup script, i have this in mine:

    #!/bin/sh
case $1/$2 in
  pre/*)
    # Put here any commands expected to be run when suspending or hibernating.

    # so bluetooth doesn't prevent sleep
    /usr/bin/bluetoothctl power off ;;
  post/*)
    # Put here any commands expected to be run when resuming from suspension or thawing from hibernation.

    # bluetooth on after resume
    /usr/bin/bluetoothctl power on ;;
esac

    Sorry, this is about as far as i can help without access to your computer.