On Tue 23 Jan 17:12, Jeff Garzik wrote: > However, I am unable to keep it from corrupting data. I primarily use > it on sil3114, just like your hardware, but I have the same problems > with other controllers. > > My gut feeling is that the i-RAM has very strict RAM model requirements, > and needs the latest firmware, but I have not yet tested these hypotheses. Hm, that's a pity! I have used an Apacer 512 MB PC2700 module in my i-Ram for testing, but I have ordered two Kingston KVR400X64C3A/1G sticks that are on Gigabytes list of recommended ram modules[1]. The Apacer module hasn't given my any trouble though. I ran some stress tests on it last night, bonnie++[2] and stress[3] for a few hours, and as far as I could tell this didn't screw up the file system in any way. Do you have any test applications that can reproduce the error on your i-Ram? I'd be more than happy to do some testing both using my old Apacer module and the new Kingston modules when they arrive. With regards to the i-Ram being picky about RAM, check this post: http://www.nerdnos.net/?newsarchives According to this guy, the i-Ram does not support high density ram modules. Could this be what's causing your data/file system corruption? [1]: http://www.gigabyte.com.tw/Support/Peripherals/FAQ_Model.aspx?FAQID=2152&ProductID=2076 [2]: http://www.coker.com.au/bonnie++/ [3]: http://weather.ou.edu/~apw/projects/stress/ -- Oddbjørn Kvalsund - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
