Package Details: enhanceio-dkms-git 108.01-2

Git Clone URL: (read-only, click to copy)
Package Base: enhanceio-dkms-git
Description: dkms module for EnhanceIO block device caching
Upstream URL:
Keywords: cache EnhanceIO SSD
Licenses: GPL
Submitter: thermionix
Maintainer: None
Last Packager: Frontier
Votes: 10
Popularity: 0.000000
First Submitted: 2013-12-09 01:45
Last Updated: 2015-06-09 06:18

Dependencies (3)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6

mmmm_cake commented on 2014-04-13 21:13

I successfully installed the modified version that was added in response to the issue you linked to. Considering that this project is probably dead (it hasn't been updated in months and has been sold to a corporation), the fix will probably never be merged into the master branch. Is it possible to change the package to use the modified files at ?

thermionix commented on 2014-04-11 00:09

there's an issue on github regarding 3.14 build errors;

mmmm_cake commented on 2014-04-10 15:12

Just noticed that in my previous comment I copies the errors from the files I downloaded manually. The errors I get when installing from AUR via Packer are the same thing, just that the location is different (/tmp/packerbuild-0...).

mmmm_cake commented on 2014-04-10 15:05

I just upgraded to Linux 3.14.0 and suddenly I'm not able to install the EnhanceIO drivers anymore. I had been installing them manually after every upgrade using the same files that I downloaded from GitHub every time, but now I'm getting errors. I also get the same errors when I try installing from the AUR. Anyone know what's going on?
The errors look something like this:
/home/arie/Downloads/EnhanceIO-master/Driver/enhanceio/eio_main.c: In function ‘bc_put’:
/home/arie/Downloads/EnhanceIO-master/Driver/enhanceio/eio_main.c:96:13: error: ‘struct bio’ has no member named ‘bi_size’
bc->bc_bio->bi_size = 0;
But there are a lot more of them.

salsadoom commented on 2014-04-08 02:23

Revising my previous post. Yeah, be very careful using this. Using write-back is horrendously unsafe for sure, testing for the last few hours with write-through seems ok. If it does barf again, I'll post here so others know.

thermionix commented on 2014-04-07 23:05

yep I've also disabled it on the three machines I was testing it on, following corruption on all of them

salsadoom commented on 2014-04-07 22:16

Followed the arch wiki documentation. Caused all sorts of filesystem errors and a kernel panic for me. I would exercise extreme caution with this right now.