Package Details: exfat-dkms-git 205.c0915bb-1

Git Clone URL: https://aur.archlinux.org/exfat-dkms-git.git (read-only)
Package Base: exfat-dkms-git
Description: Native (nofuse) kernel module for EXtendedFAT support - use with DKMS
Upstream URL: https://github.com/barrybingo/exfat-nofuse
Licenses: GPL2
Conflicts: exfat, exfat-git
Submitter: PyroDevil
Maintainer: freswa
Last Packager: freswa
Votes: 55
Popularity: 1.383769
First Submitted: 2013-07-24 13:59
Last Updated: 2019-01-14 22:34

Pinned Comments

freswa commented on 2017-01-14 00:36

This requires exfat-utils-nofuse because exfat-utils uses the fuse driver by default (instead of this kernel module).

Latest Comments

1 2 3 4 Next › Last »

jpegxguy commented on 2019-09-02 11:33

The staging driver is indeed from Samsung, just with one unified header file. It has the same functions but seems like some vfat stuff is removed. Maybe the author of the linux patch already shaped the driver a bit.

Anyhow it's good that the community can now work on the exFAT driver in linux git. I do agree this package should be kept. After all, there is no actual exfat driver in current arch kernels.

freswa commented on 2019-09-02 11:13

IIRC upstream of this package uses some first leaked and then reimplemented Samsung code. I don't know where the kernel code comes from - maybe Microsoft? I'd like to keep this package until the driver in the kernel leaves staging.

jpegxguy commented on 2019-09-02 10:22

What's the difference between the now staged exfat driver:

https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/exfat?h=staging-next

and this git tree? I do see the one used here has more lines of code. Maybe the community should pump knowledge into the driver in the linux git tree.

Or should we keep this git tree because that driver in linux git is going to be massively reworked?

barrybingo commented on 2019-01-14 09:51

Hiya. I maintain fork https://github.com/barrybingo/exfat-nofuse and am willing to maintain that fork for future kernels. You can switch to my fork. See https://github.com/dorimanx/exfat-nofuse/pull/137#issuecomment-453948618

artafinde commented on 2019-01-05 10:02

Consider changing the upstream repo to https://github.com/barrybingo/exfat-nofuse instead of the one from dorimanx as it seems more active.

artafinde commented on 2019-01-04 08:52

Patch for 4.20+ https://gist.github.com/inglor/a2d4c7e63d2522b7d48cf553e54469d9

dini commented on 2019-01-04 08:10

Please go to "barrybingo" repository or add a patch for 4.20

tjc commented on 2018-10-19 10:52

I am still having problems with this package. Currently I have to manually use this "barrybingo" fork: https://github.com/barrybingo/exfat-nofuse and install it manually. However the upstream that this package builds from, https://github.com/dorimanx/exfat-nofuse, still hasn't been updated since April. This package should be considered broken currently and I don't know what moonman is talking about as the upstream hasn't changed.

moonman commented on 2018-09-10 03:54

Maintainer doesn't seem to be available [EDIT] Package has been updated

dreieck commented on 2018-09-07 10:14

A bit more elaborate patch to build with kernel 4.18 is there:

https://github.com/dorimanx/exfat-nofuse/issues/136#issuecomment-419014014

@freswa: Can you incorporate such a fix in a prepare()-function until upstream fixes the issue?