Kingston Fury RGB RAM linux
ee1004 kernel driver messes with i2c access to the Kingston Fury RAM on current 6.x kernel
quick fix
echo 'blacklist ee1004' | sudo tee /etc/modprobe.d/kingston-fury-blacklist.conf
seen from United States
seen from Germany

seen from Saudi Arabia
seen from United States
seen from China
seen from United States
seen from United States
seen from United States

seen from Malaysia
seen from China
seen from United States
seen from Japan

seen from India
seen from United States
seen from Poland
seen from Greece
seen from Germany

seen from Malaysia
seen from China
seen from United States
Kingston Fury RGB RAM linux
ee1004 kernel driver messes with i2c access to the Kingston Fury RAM on current 6.x kernel
quick fix
echo 'blacklist ee1004' | sudo tee /etc/modprobe.d/kingston-fury-blacklist.conf
Debian wheezy kvm guest + virtio networking
I have a kvm vps with #frantech for storage, however I've noticed for some time that the vm's network connectivity hangs every once in a while.
- virtio + 3.2.x kernel -> random network hangs - virto + 2.6.x kernel -> great performance - e1k + 3.2.x kenel -> shitty performance
so I guess I'm going to stick with 2.6 for now..
well Delta enlightened me on their IRC chanel: 23:47 <~Delta> virtio networking is gimpy 23:47 <~Delta> it's fixed in ~3.13+