Am Mit, 09 Mai 2001 schrieb Olaf Hering:
What kernel do you use? I recommend the 2.4.2 kernel, the used CMD646 controller is broken and works only with 2.2.16 and 2.4.2.
Gruss Olaf
Until now I tried 2.2.16, 2.2.18 and 2.4.2! I got a hint from Jochen Hoffmann. He told me they had similar problems with two IBM DTLA-305040 (same family as mine) on AMD K7 computers running SuSE 6.4. Kernel update from 2.2.18 to 2.2.19 solved his problem and as a work around he turned off dma support. So I installed 2.2.18 and 2.4.2 but the error messages still occurred. Then I turned off UDMA of the DTLA-307030 and for the first time these kernel messages disappeared (with kernel 2.2.16 or 2.4.2). It must be a data transfer problem. After shortening the UltraATA cable from 24" to 12" I turned on again UDMA Mode 2. It works well since five hours. I only get a nfsserver failure during bootup with kernel 2.4.2: Starting kernel based NFS serverlockdsvc: Invalid argument .....failed and a few new kernel messages: May 9 19:46:46 MacHu8 inetd[395]: swat/tcp (2): bind: Address already in use May 9 19:47:37 MacHu8 /usr/sbin/gpm[637]: Error in protocol I'm not sure why this cable shortening works. Why should a longer cable support one UDMA/33 drive and another on the same cable won't work? And what about my CMD646? In which way is it broken? Regards, Micha