
I would highly recommend keeping an OSX partition for these reasons. I love Arch as a whole, but it's very frustrating to have these issues with the MBA in particular. I'm going to try booting into a black screen and then SSHing into the machine to see if any errors come up when starting, but as of right now it's a work in progress and I haven't been able to find much help about it. I get no errors for loading the backlight module during the boot if it doesn't bug out completely. In the case that the backlight is working, I no longer can adjust it the way I did before, so it's stuck on one brightness. Right now the way I deal with this is just restarting my computer over and over until the backlight is working.
ARCH LINUX MACBOOK AIR 2017 INSTALL UPDATE
After a recent kernel update (4.x something, I forget the exact one), my computer will often boot and the backlight will be completely off and I can't change it. However, recently my issues have been getting worse. Occasionally, the permissions for writing to those files would reset and I would just have to change them again to get them working. I just bound those scripts to my brightness keys and had everything working as intended. I avoided the problem by never suspending my computer and changing the lid close behavior.Īdditionally, in order to change the brightness, I had to write my own scripts to write to the brightness file. There was a kernel module "fix" that was designed for the previous MBAs that did not work for me. If I suspended it, upon waking it back up, the backlight had only two settings 0% or 100%. When I first installed Arch on my MBA about a year ago, I couldn't suspend my computer (still can't).

=> ERROR: A failure occurred in prepare().The problem has changed over time. Mv: cannot stat 'System/Library/Extensions/AppleCameraInterface.kext/Contents/MacOS/AppleCameraInterface': No such file or directory
ARCH LINUX MACBOOK AIR 2017 INSTALL DRIVER
> Creating working copy of facetimehd-firmware git repo.Ĭhecking dependencies for driver download. > Cloning facetimehd-firmware git repo.Ĭloning into bare repository '/var/tmp/pamac-build-andrey/facetimehd-firmware/facetimehd-firmware'. Make: Leaving directory '/usr/lib/modules/5.4.2-arch1-1/build' var/lib/dkms/bcwc-pcie/r255.af589aba0afd/build/fthd_drv.c:25:10: fatal error: linux/pci-aspm.h: No such file or directory Make: Entering directory '/usr/lib/modules/5.4.2-arch1-1/build'ĪR /var/lib/dkms/bcwc-pcie/r255.af589aba0afd/build/built-in.aĬC /var/lib/dkms/bcwc-pcie/r255.af589aba0afd/build/fthd_hw.oĬC /var/lib/dkms/bcwc-pcie/r255.af589aba0afd/build/fthd_drv.oĬC /var/lib/dkms/bcwc-pcie/r255.af589aba0afd/build/fthd_ringbuf.oĬC /var/lib/dkms/bcwc-pcie/r255.af589aba0afd/build/fthd_isp.o I updated to linux-5.4.2.arch1-1 and am getting errors when rebuilding the module: DKMS make.log for bcwc-pcie-r255.af589aba0afd for kernel 5.4.2-arch1-1 (x86_64) Warning: bcwc-pcie-git-r242.ea832ac-1 is up to date - reinstalling => bcwc-pcie-git-r242.ea832ac-1 already made - skipping build => Updated version: bcwc-pcie-git r242.ea832ac-1 A tooling behavior issue to check) % yay -Syuġ aur/bcwc-pcie-git r242.ea832ac-1 -> 0.0.0-4

Although rebuilding is stopped, I need to stop the auto-reinstall if there's no package rebuild.

unable to know whether I need to update, since the AUR helper can't tell due to version difference as it overwrites the PKGBUILD with the latest pkgver=0.0.0 to be mismatched from the current installed r242.ea832ac-1. I will probably need to find a way for myself to configure the AUR helper or augment my usage behavior for:ġ.

The AUR helper usually (with the majority of the small number of git AUR packages I use) will not be flagged for update via yay -Syu. However, it is a matter of my tooling usage and the dissonance compared to my usual experience up to now. Indeed there's no rebuild from the output below. Thank you for maintaining the package and I can understand the current setup offloads the maintainer from needing to update the pkgver for every git upstream update. As mentioned on Broadcom wirelessInstallation, the BCM4331 chipset used. In that case, check what kernel module is being used, by running lspci -v and look for the Network controller called BCM4331. Thanks for the explanation of intended behavior. Note: For 8,2 (potentially for 8,1 and 8,3 as well) be aware that you might find that ip link does not show the wireless network card.
