> > I agree that if it has known problems which destroy data it should be
> > unavailable in the stable kernel. It certainly sounds as if that's the
> > case, and the driver could be held out until 2.4.20 or so when it can be
> > fixed, or if it can't be fixed it can just go away.
>
> Then I suggest you give up computing, because PC hardware doesnt make
> your grade. BTW the general open promise bugs *dont* include data
> corruption so I suspect it may be your h/w thats hosed.
Mine, and the original poster? And the "me too?" I understood the author
to say that the new board needed a driver change, and if that's the case
why not hold off the driver until he gets to it? Nobody if faulting him
for lack of time, but it seems not to work.
Guess it must be my hardware, two boards, two systems, corruption only on
the drives on the new... hell with it, obviously if you don't have the
problem the original poster and I must be clueless whiners.
I'll drop this discussion and scrap the board, restores cost more than
controllers :-(
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/