Scanner stops SuSE booting (7.3)
Hi People I have an Iwill (Initio) 2935UW SCSI controller in my PC with 2 cdroms connected internally and a Umax 1220s scanner hung off the rear "D" connector. The stock SuSE kernel will hang on boot after resetting the SCSI bus and finding the 3 devices; this even happens when trying to run setup from the CDs, but once I disconnect the scanner and cold boot everything goes without a hitch. Can anyone tell me what setting I need to reconfigure in the SuSE kernel to get the box booting with my scanner connected? TIA Brian
Hmmm, maybe it's an issue with plugging a 3rd connection to you scsi bus.
Some cards say not to use the external bus *and* the internal ones at the same time.
Not familiar with you card/model though.
Checking termination would the first palce, then cables.
/Dee
"Brian Stevenson"
Hi People
I have an Iwill (Initio) 2935UW SCSI controller in my PC with 2 cdroms connected internally and a Umax 1220s scanner hung off the rear "D" connector. The stock SuSE kernel will hang on boot after resetting the SCSI bus and finding the 3 devices; this even happens when trying to run setup from the CDs, but once I disconnect the scanner and cold boot everything goes without a hitch.
Can anyone tell me what setting I need to reconfigure in the SuSE kernel to get the box booting with my scanner connected?
TIA Brian
If any SCSI card I bought would not let me use the internal and external connectors, I would write to the magazines and have them prod the manufacturer. That's ridiculous! (And I would take it back to the dealer and make him give me something that worked!) --doug, wa2say At 14:42 12/20/2001 -0900, W.D.McKinney wrote:
Hmmm, maybe it's an issue with plugging a 3rd connection to you scsi bus. Some cards say not to use the external bus *and* the internal ones at the same time. Not familiar with you card/model though.
Checking termination would the first palce, then cables.
/Dee
"Brian Stevenson"
wrote: Hi People
I have an Iwill (Initio) 2935UW SCSI controller in my PC with 2 cdroms connected internally and a Umax 1220s scanner hung off the rear "D" connector. The stock SuSE kernel will hang on boot after resetting the SCSI bus and finding the 3 devices; this even happens when trying to run setup from the CDs, but once I disconnect the scanner and cold boot everything goes without a hitch.
Can anyone tell me what setting I need to reconfigure in the SuSE kernel to get the box booting with my scanner connected?
TIA Brian
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Brian Stevenson wrote:
I have an Iwill (Initio) 2935UW SCSI controller in my PC with 2 cdroms connected internally and a Umax 1220s scanner hung off the rear "D" connector. The stock SuSE kernel will hang on boot after resetting the SCSI bus and finding the 3 devices; this even happens when trying to run setup from the CDs, but once I disconnect the scanner and cold boot everything goes without a hitch.
Can anyone tell me what setting I need to reconfigure in the SuSE kernel to get the box booting with my scanner connected?
Hi, I have similar setup. An initio scsi card, internal cdr, and external umax scsi scanner. Up to Suse 6.4, it booted fine. With Suse 7.2, it hangs, if I have both units attached. I can turn off my internal cdr, so I can test the boot, with either the scanner on or the cdr on. It will boot fine as long as only one is connected, so it isn't an "external connector" problem. Someone on this list said to disable "verbose scsi error messages" in the kernel. Next time I roll my kernel I will try it. The suse kernel disables this I guess. I have got around this by executing "scsiadd -scanbus" when I need to use the scsi device. Any scsi scan utility will do it. It will find all the scsi devices just fine, after the booting has finished.
Hi, I have similar setup. An initio scsi card, internal cdr, and external umax scsi scanner. Up to Suse 6.4, it booted fine. With Suse 7.2, it hangs, if I have both units attached. I can turn off my internal cdr, so I can test the boot, with either the scanner on or the cdr on. It will boot fine as long as only one is connected, so it isn't an "external connector" problem.
Someone on this list said to disable "verbose scsi error messages" in the kernel. Next time I roll my kernel I will try it. The suse kernel disables this I guess.
I have got around this by executing "scsiadd -scanbus" when I need to use the scsi device. Any scsi scan utility will do it.
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. BTW guys the controller & termination are both fine; on this tripple booting machine. Thanks again Brian
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. :-)
participants (4)
-
Brian Stevenson
-
Doug McGarrett
-
W.D.McKinney
-
zentara