Thanks for the input, Peter. Seeing your post made me want to cheer...not because of your misfortune, but just to know I wasn't imagining things :)"Donald Spoon" <[EMAIL PROTECTED]> writes:
couldn't get much out of them. Here is one that has identical results with the 2.4.17 kernel, and apparently works OK with the 2.2.19 kernel from what I can devine. http://www.sslug.dk/emailarkiv/alpha/2002_01/msg00003.html .
That's me.
I wrote the kernel list too without any answers: http://www.uwsg.iu.edu/hypermail/linux/kernel/0201.3/2187.html
Searched google. Tried to diff the two drivers to find any difference
explaining the fail. Asked around. No luck anywhere.
I tried sending an E-Mail to the author, but it bounced on me.
SSLUG adds '.sslug.dk' as spamprotection in the webarchive of our mailling lists. That is why you couldn't reach me that way.
During my Google search, I found some tantalizing "hints" from other users of this SCSI card, but in different machines and as a secondary controller for scanners, etc. There were a couple of reports that the driver would produce similar errors when compiled into the kernel, but would work OK if loaded as a module. I gathered that once the kernel is up & running this driver works as advertised.
All things so far seem to imply something going wrong in the kernel for our machines. Harm reports he got a 2.4.3 Red Hat kernel to boot, and Alastair Watts says he has it going on his XLT with a 2.4.7 kernel. Maybe we can back-track on kernel versions to the point where it starts working, look at the change logs, and "maybe" get a clue as to what is going on... dunno.
Cheers, -Don Spoon-
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]