[Bug 213666] New: YaST fails to detect presence of a SCSI scanner
https://bugzilla.novell.com/show_bug.cgi?id=213666 Summary: YaST fails to detect presence of a SCSI scanner Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bruce.butterfield@aeroflex.com QAContact: jsrain@novell.com Computer: AMD Athelon XP 1800, 512M RAM OS: SuSE 10.1, No updates (computer not on network) PCI SCSI card: Adaptec, identified (PCI) as ABP940U / ABP960U Scanner: UMAX Astra 1200S (uses SCSI interface) The scanner was OFF when SuSE was installed, and had not been used since installation. I turned ON the scanner, and then turned on power to the computer to boot. The Adaptec SCSI card found the scanner on slot 2 during hardware boot. I used Yast / Hardware / Scanner to set up the card. Yast did NOT find any scanners. Since it did not find the scanner automatically, I manually added a "scanner" and configured it from the list (and my scanner is on the list of known scanners). Yast reported that no scanners of that type were available. XSane indicated that no devices were available. Yast hardware information reported the presence of my PCI card, but identified it as a SCSI storage device, and not a controller. I found the card located both in the PCI and Storage sections. There was no SCSI section. The hardware information did NOT report the presence of the scanner. I rebooted to Win98. Win98 detected new hardware and properly configured the scanner. The scanner had previously worked with SuSE 8.2 and 9.0. I rebooted to Knoppix 4.0.2. It assigned advansys.o to work with the SCSI card at boot, and XSane detected the scanner, identified it correctly, and was able to both configure the scanner and take images from the scanner. I rebooted back to SuSE 10.1, and was unable to get SuSE to detect the presence of the scanner. I tried to run "rescan-scsi-bus.sh" (I did not use any options on the cmd line), and it did not detect any new SCSI devices. When I again used YAST to show me the hardware information, there was a new section for SCSI, and the SCSI controller card was present in that section (identified as indicated above), but it was identified as a storage device, and no scanner was present anywhere. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213666 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jsrain@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213666 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213666 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213666 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal Status|NEW |NEEDINFO Info Provider| |bruce.butterfield@aeroflex.com ------- Comment #2 from jsmeix@novell.com 2006-10-23 05:53 MST ------- Does the following command (run it as root) find the scanner? sane-find-scanner -q If not, does the following command list it: lsscsi -g -l -v Attach the output of the following commands: export SANE_DEBUG_SANEI_SCSI=255 ; sane-find-scanner -q FYI: YaST calls "sane-find-scanner -q" to detect scanners. A prerequisite is that the underlying SCSI stuff works correctly. The YaST scanner tool does not change or set up the SCSI system. The YaST scanner tool cab only set up a scanner which is recognized as generic SCSI device by the SCSI system. The bug is not critical because there is no "Crash, loss of data, corruption of data, severe memory leak", see https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213666 ------- Comment #3 from bruce.butterfield@aeroflex.com 2006-10-24 07:54 MST ------- I tried the first two commands, and had no response. From the errors in the third line, it appears that I am missing some standard SCSI files. I am attaching my terminal session below: Sargon:~ # sane-find-scanner -q Sargon:~ # Sargon:~ # lsscsi -g -l -v Sargon:~ # Sargon:~ # export SANE_DEBUG_SANEI_SCSI=255 ; sane-find-scanner -q [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=131072 bytes [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg0' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg1' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg2' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg3' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg4' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg5' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg6' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg7' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg8' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sg9' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sga' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgb' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgc' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgd' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sge' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgf' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgg' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgh' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgi' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgj' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgk' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgl' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgm' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgn' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgo' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgp' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgq' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgr' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgs' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgt' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgu' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgv' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgw' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgx' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgy' failed: No such file or directory [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: open of `/dev/sgz' failed: No such file or directory Sargon:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=213666 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|bruce.butterfield@aeroflex.c| |om | Resolution| |INVALID ------- Comment #4 from jsmeix@novell.com 2006-10-25 01:02 MST ------- As long as "lsscsi" doesn't show your SCSI scanner, the SCSI system doesn't know about it and then no scanner setup tool can set it up. I.e. the problem is in the SCSI system. In particular check that your SCSI host adapter is set up. The command lsscsi -H -l -v must show it. Perhaps there is no kernel-module loaded for your SCSI host adapter. If you know which module it is, load it with modproble kernel_module_name Regarding missing device node files: Nowadays almost all device nodes are no longer static but generated and removed on the fly via "udev" (see "man udev") during runtime (e.g. when matching kernel modules are loaded or un-loaded). I am no SCSI expert therefore I cannot help you any further. To get different issues well seperated, plase file a seperated new bug report regarding the SCSI problem. I close this bug as invalid because there is no bug in the scanner setup tool. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com