Brian Stevenson wrote:
So you're "hot plugging" the scanner and running that command in a term.?? Thanks for the info. I'll give the kernel a damn good thrashing later and let you know what happens.
Yeah, I usually have the scanner off when I boot anyhow, so I just switch the scanner power on, then scsiadd -scanbus, and everything works. I don't mess with the cables, only the power switch. It all works out OK for me, except the "annoyance" that I know there is a glitch in the boot process. That's why I havn't looked too hard for a fix. Actually it's kindof nice, since I know that I can use the scanner anytime, and don't have to have it on at boot. It's the way I would want it. Someone on the usenet hypothesized that the newer scsi interface for the 2.4 kernels may have some trouble dealing with timing differences between the fast internal cable and the slower external cable. Why only at boot? That's the million dollar question. :-)