Yeah... the sg driver has changed significantly since then.
> Leonard N. Zubikoff, creator of the BusLogic driver, has remained
> unresponsive to my pleas for help.
I'll have to give it a try.
> Well, this is greatly hindering (i.e. making it impossible) my ability
> to scan *AT ALL*!
Me too... though I have little scanning to do except for SANE related
development.
> It's reached the point where I can reliably make the machine Oops during
> a scan.
Any scan? Can you make it not oops? I have only see random machine or sg
lockups that happen after one or more scans.
> If anybody has some good hints on how to trap all that output that flies
> across the screen so I can submit it to developers that know how to deal
> with it, I'm all ears.
I'm sure there is a way to add debug to the buslogic driver.
> And, like you, I'm getting myself a new SCSI adapter *JUST BECAUSE OF
> THIS*.
> I shouldn't have to, but if the developer seems uninterested and I'm
> uncapable...
Out of curiousity...
- Do you have any other SCSI controller in the system?
- Are you using IDE?
- Is the BusLogic adaptor the only device on it's IRQ?
- Is your system SMP?
- What motherboard are you using?
I ask as I had perfectly stable scanning with a UP SuperMicro P6SBA
motherboard with IDE drives and the BusLogic card being the only SCSI
card and on it's own IRQ.
Brian Macy
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com