Jeff,
I swapped cables and tried 3 different RAM chips, so yep, did that :) Question on that - does the RAM 'matter' as the driver doesn't use it? I.e. is it used by the onboard control logic as cache?
Also tried moving the card to different PCI slots, still no luck :(
Now that server is my home server running off PATA drives, the SX4 card is sitting gathering dust (as I said) until I get my old PC operational again and can put the card in to re-test.
A few people seem to have this problem, so it is definitely worthwhile having a look at, I'd love to have a go just out of my own curiousity. Closest I've been to this kinda programming is interfacing with telephone switches for softphone and ACD functionality, I'm hoping that'll help me get a grasp in the interrupt driven space of hardware! :)
All I need is a bit of time ;)
:)J
Jeff Garzik wrote:
On Fri, Feb 18, 2005 at 10:44:57AM +1000, Johny Ågotnes wrote:
Just a quick note on the SX4 Card - I have seen data corruption on hard-drives too in the simplest possible setup, so I'd stay clear of that card until further notice.
Mine is sitting in a cupboard right now, awaiting 'someone' (me, if I get some time to learn low-level kernel drivers) debugging the issue.
Basically, accessing two drives via this card causes corruption, I had it working ok when I only accessed 1 drive, which is kinda pointless...
I've not need about to reproduce this in the lab.
Have you tried switching out RAM and cables?
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
