Package Details: mba6x_bl-dkms 0.0-1

Git Clone URL: https://aur.archlinux.org/mba6x_bl-dkms.git (read-only, click to copy)
Package Base: mba6x_bl-dkms
Description: Backlight for mba6x to fix post suspend/resume brightness.
Upstream URL: https://github.com/patjak/mba6x_bl
Keywords: brighness driver macbook
Licenses: GPL2
Submitter: frank604
Maintainer: None
Last Packager: whynothugo
Votes: 9
Popularity: 0.000000
First Submitted: 2014-02-03 12:32 (UTC)
Last Updated: 2016-06-29 09:39 (UTC)

Dependencies (1)

  • mba6x_bl-dkms-git

Required by (0)

Sources (0)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

whynothugo commented on 2016-03-17 01:51 (UTC)

Kernel >= 4.4 support seem broken. There's an upstream issue for that. You can edit the PKGBUILD if you want to try it anyway, but it MAY break your system.

ericgroom commented on 2016-03-17 00:06 (UTC)

I am on 4.4.5-1-ARCH and upon attempting to install I get the error, "error: target not found: linux<4.4"

vennahlot commented on 2016-03-13 21:33 (UTC)

After the latest kernel update, it works fine again on my laptop(early 2015 11" MBA). $uname -r 4.4.5-1-ARCH

whynothugo commented on 2016-02-16 14:16 (UTC)

I used LUKS and LVM, and thought mounting /boot failed, mounting / worked, and in the rescue mode, reinstalling linux "worked" (mkinitcpio failed, and pacman exited with an error). The system worked after that. > Anyways, thanks for this advice anyways, hopefully it can help someone else if they find themselves in a similar situation. Hopefully, yes.

bandali commented on 2016-02-16 13:42 (UTC) (edited on 2016-02-16 13:42 (UTC) by bandali)

> I faced a similar issue, and reinstalled `linux` to get around it, IIRC. Sorry to have this advice too late IIRC, I did think about reinstalling `linux` at one point, but since I use LUKS, I didn't manage to open and mount it to be able install `linux`. I guess I could've just used a live USB and chrooted and installed `linux` that way, but I don't know why I didn't think about it at that moment. Anyways, thanks for this advice anyways, hopefully it can help someone else if they find themselves in a similar situation.

whynothugo commented on 2016-02-16 06:35 (UTC)

> my laptop wouldn't boot up (was complaining about vfat being unknown when trying to mount /boot). I faced a similar issue, and reinstalled `linux` to get around it, IIRC. Sorry to have this advice too late

bandali commented on 2016-02-16 05:55 (UTC) (edited on 2016-02-16 05:56 (UTC) by bandali)

Thanks for updating the PKGBUILD for now. I upgraded to 4.4 and faced the same situation as you had in the issue you reported on the GitHub repo (#43). Then, IIRC, I tried downgrading the kernel and something didn't go as expected with dkms (I don't exactly remember what), so I renamed the 4.4 directory in /usr/lib/modules to some arbitrary name in hopes that dkms would generate the necessary files again upon upgrading (and I copied the rest of the missing files from the original directory). But I shouldn't have done that; because when I upgraded back to 4.4 and rebooted, my laptop wouldn't boot up (was complaining about vfat being unknown when trying to mount /boot). I even tried installing dosfstools but to no avail. So, I basically gave up and made a mental note to not mess with /usr/lib/modules ever again :)

whynothugo commented on 2016-02-15 23:50 (UTC)

@aminb: How did it screw up so had? I'll update this PKGBUILD to require linux < 4.4

bandali commented on 2016-02-15 23:34 (UTC)

Same thing, not working on 4.4.1, and dkms messed up my system beyond repair. I had to reinstall arch from scratch, and I've been staying on 4.3.

whynothugo commented on 2016-02-06 17:58 (UTC)

This failed for me on 4.4.1. Let me know if your experience varies.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »