[Bug 350688] New: SCSI hardware configuration scanner os: opensuse 10.3

newer
[Bug 377981] New: f-spot crash on...

older
[Bug 372726] New: kopete crashes...

bugzilla_noreply＠novell.com

26 Dec 2007 26 Dec '07

10:53

https://bugzilla.novell.com/show_bug.cgi?id=350688 User cees@ieee.org added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c31 Summary: SCSI hardware configuration scanner os: opensuse 10.3 Product: openSUSE 10.3 Version: Final Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: cees@ieee.org QAContact: jsrain@novell.com Found By: Other I switched on my scsi hp scanjet 4c scanner. It is regonized by Yast but i can't configure it. It works fine under windows and it worked fine under suse 10.2 55: SCSI 602.0: 10c04 Scanner [Created at scsi.1561] UDI: /org/freedesktop/Hal/devices/pci_1000_1_scsi_host_scsi_device_lun0_scsi_generic Unique ID: i6Hy.MAy8A2PsRY8 Parent ID: B35A.sgyNtPQ5NJE SysFS ID: /class/scsi_generic/sg4 SysFS BusID: 6:0:2:0 Hardware Class: scanner Model: "HP C2520A" Vendor: "HP" Device: "C2520A" Revision: "3503" Driver: "sym53c8xx" Driver Modules: "sym53c8xx" Device File: /dev/sg4 Device Number: char 21:4 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #31 (SCSI storage controller) In the yast config screen: Not Configured Hewlett-PackardSCSI processor 'JP C2520A 3503' at /dev/sg4 But i can't configure it. If i high light the line and edit is with the edit buton, it will put the config on the next line. So.... some thing awkward happening her. -- 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.

Show replies by date

bugzilla_noreply＠novell.com

3 Jan 3 Jan

17:35

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c1 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |cees@ieee.org --- Comment #1 from Cyril Hrubis 2008-01-03 10:35:32 MST --- Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks! -- 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.

bugzilla_noreply＠novell.com

26 Jan 26 Jan

14:53

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User cees@ieee.org added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c2 Cees Keyer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|cees@ieee.org | --- Comment #2 from Cees Keyer 2008-01-26 07:53:28 MST --- Created an attachment (id=191920) --> (https://bugzilla.novell.com/attachment.cgi?id=191920) Yast2 log file wilst detecting the scanner and trying to config it. -- 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.

bugzilla_noreply＠novell.com

14:54

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User cees@ieee.org added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c3 --- Comment #3 from Cees Keyer 2008-01-26 07:54:42 MST --- Created an attachment (id=191921) --> (https://bugzilla.novell.com/attachment.cgi?id=191921) yast screen dumps configuring scanner -- 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.

bugzilla_noreply＠novell.com

14:57

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User cees@ieee.org added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c4 --- Comment #4 from Cees Keyer 2008-01-26 07:57:51 MST --- Created an attachment (id=191922) --> (https://bugzilla.novell.com/attachment.cgi?id=191922) HWinfo output for scanner with problems. -- 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.

bugzilla_noreply＠novell.com

28 Jan 28 Jan

13:13

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jsmeix@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.

bugzilla_noreply＠novell.com

29 Jan 29 Jan

11:43

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c5 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #5 from Johannes Meixner 2008-01-29 04:43:24 MST --- According to "man sane-hp" the "hp" driver is the right one for a "C2520A 3503" (according to the man page is its actually a "ScanJet 3C" but this doesn't matter - it is the right driver for both models). YaST activates the right driver but then the driver fails to communicate with the device. Therefore it is no YaST issue but a lower-level issue. The most often problem which is reported by users regarding scanner setup is when a driver was set up but then no scanner was recognized by this driver. If the driver is the right one for the scanner, then in very most cases the reason is a low-level (kernel related) device communication problem (i.e. a low-level USB problem or a low-level SCSI problem). Those problems cannot be fixed from within the YaST scanner setup module

...

From the YaST help text:

SCSI scanners are normally detected. If difficulties arise proceeding with [Add], check whether your scanner is shown by the command 'lsscsi'. If not, the SCSI system cannot communicate with the scanner. Verify that an appropriate kernel module for the SCSI host adapter has been loaded. .. If a driver is set up but no scanner is recognized by the driver, possible reasons are: The scanner is not connected or switched off, the driver is not the right one for the particular model (even small differences in model names or internal differences in the same model series may require different drivers), there are low-level (kernel related) device communication problems (e.g. a low-level USB problem or a low-level SCSI problem). ------------------------------------------------------------ Have a look at " Trouble-Shooting (Debugging)" at http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 Perhaps it helps to find the actual reason why the "hp" driver cannot talk to your scanner. In your particular case you could set export SANE_DEBUG_DLL=4 export SANE_DEBUG_HP=128 export SANE_DEBUG_SANEI_SCSI=128 or even export SANE_DEBUG_SANEI_SCSI=255 See "man sane-hp" and "man "sane-scsi". -- 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.

bugzilla_noreply＠novell.com

30 Jan 30 Jan

06:38

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User cees@ieee.org added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c6 --- Comment #6 from Cees Keyer 2008-01-29 23:38:58 MST --- Created an attachment (id=192260) --> (https://bugzilla.novell.com/attachment.cgi?id=192260) output from lsscsi and The scanner is detected by the scsi (sub)system. I can't configure it though.. run trough all the SDB notes on scanner problems. It worked fine under 10.2 it works on windows too :( -- 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.

bugzilla_noreply＠novell.com

08:36

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c7 --- Comment #7 from Johannes Meixner 2008-01-30 01:36:14 MST --- I marked this report about the YaST scanner setup as "invalid" because it is invalid regarding the YaST scanner setup. But this does not mean that there is no issue regarding your SCSI system (or whatever else the actual reason is). Of course your scanner is detected by the SCSI system because otherwise it would not be shown at all in YaST but the crucial point is that the scanner driver "hp" fails to communicate with it. See comment #5 what might help to find the actual reason why the "hp" driver cannot talk to your scanner. Is it a completely new clean installation of openSUSE 10.3 or an update from a previous version or did you update whatever packages in your 10.3 system or did you change the "hp" driver config file /etc/sane.d/hp.conf? Is the "hp" driver config file /etc/sane.d/hp.conf the original from our sane-backends RPM? Check if the following command reports that is is changed: rpm -V sane-backends | grep 'hp.conf' The original "hp" driver config file has the first line scsi HP This lets the "hp" driver search the SCSI bus for a "HP" device to find a HP SCSI scanner, see "man sane-scsi". If your /etc/sane.d/hp.conf is not the original from our sane-backends RPM, use the original or adapt your config file accordingly (see "man sane-hp" and "man sane-scsi"). Check the trouble-shooting/debugging messages according to what I described in comment #5 if the hp driver actually searches your SCSI bus for your scanner. By the way: My HP SCSI scanner ScanJet 6200C works well with the hp driver on a AMD 64-bit system. -- 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.

bugzilla_noreply＠novell.com

31 Jan 31 Jan

07:56

New subject: [Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3

https://bugzilla.novell.com/show_bug.cgi?id=350688 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350688#c8 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #8 from Johannes Meixner 2008-01-31 00:56:18 MST --- I got this via personal mail (shortened): ================================================================= From: Cees Keyer .. I made a symbolic link from /dev/sg4 to /dev/scanner. dit a chmod 666 to /dev/sg4 and xsane works just fine. Output from de debug levels are attached to the e-mail. /dev/scanner might be the cause it doesn't exists in /dev .. [hp] sane_init called [hp] hp_init: global.is_up = 1 [hp] sane_init will finish with Success [dll] init: backend `hp' is version 1.0.8 [hp] sane_get_devices called [hp] hp_read_config: hp backend v1.06/$Revision: 1.21 $ starts reading config file [hp] hp_read_config: processing line <scsi HP> .. [hp] hp_read_config: processing line [hp] hp_attach_matching_devices: attach matching scsi HP [hp] hp_attach: "/dev/sg2" [hp] hp_get_dev: New device /dev/sg2, connect-scsi, scsi-request=1 [hp] sanei_hp_device_new: /dev/sg2 [hp] hp_GetOpenDevice: device /dev/sg2 not open [hp] scsi_new: open failed (Invalid argument) [hp] /dev/sg2: Can't open scsi device .. [hp] hp_read_config: attach /dev/scanner [hp] hp_attach_matching_devices: attach matching /dev/scanner [hp] hp_attach: "/dev/scanner" [hp] hp_get_dev: New device /dev/scanner, connect-scsi, scsi-request=1 [hp] sanei_hp_device_new: /dev/scanner [hp] hp_GetOpenDevice: device /dev/scanner not open [hp] scsi_new: open failed (Invalid argument) [hp] /dev/scanner: Can't open scsi device [hp] hp_read_config: reset to default config [hp] sane_get_devices will finish with Success [dll] sane_get_devices: found 0 devices [dll] sane_exit: exiting [dll] sane_exit: calling backend `hp's exit function [hp] sane_exit called [hp] hp_destroy: global.is_up = 0 [hp] sane_exit will finish [dll] sane_exit: finished ================================================================= The hp driver recognizes the line "scsi HP" but because of whatever reason it doesn't find the scanner. It seems to find only a "HP" SCSI device at /dev/sg2 which is not the scanner and then it seems it doesn't further scan the SCSI bus to find the scanner at /dev/sg4. After this it checks /dev/scanner which of course fails too because there is no /dev/scanner file at all. The problem is not that there is no /dev/scanner file. The problem is that it doesn't find it by scanning the SCSI bus. Nowadays there cannot be a fixed SCSI device file because nowadays the device files are created anew by udev during system boot. Therefore you scanner could be once at /dev/sg4 and another time at /dev/sg3 or /dev/sg6 or whatever arbitrary number it may get depending on what the udev magic does. Therefore a scanner setup tool cannot configure a fixed scanner device file. It might work for your system as long as nothing changes regarding /dev/sg* devices. Nowadays a lot of non-SCSI devices get internally a generic SCSI device assigned, see "lsscsi -g" e.g on my workstation: --------------------------------------------------------------- .. disk ATA ST3120022A 3.04 /dev/sda /dev/sg0 .. cd/dvd PIONEER DVD-RW DVR-106D 1.10 /dev/sr0 /dev/sg1 .. cd/dvd PIONEER DVD-ROM DVD-121R 1.00 /dev/sr1 /dev/sg2 .. scanner ScanMaker X12USL 1.30 - /dev/sg3 .. disk Sony UMH-U HS-MS 2.12 /dev/sdb /dev/sg4 .. disk Sony UMH-U HS-CF 2.12 /dev/sdc /dev/sg5 .. disk Sony UMH-U HS-SM 2.12 /dev/sdd /dev/sg6 --------------------------------------------------------------- The onyl real SCSI device is the scanner - the rest are usual IDE disk/cd/dvd devices (perhaps even USB mass storage devices). Perhaps in your case you habe a "HP" disk at /dev/sg2 and the hp driver gets confused by it. Perhaps it helps in your case to help te hp driver to find your scanner when you have a more specific "scsi HP" line in /etc/sane.d/hp.conf e.g. something like one of the following lines scsi HP C2520A scsi HP * C2520A scsi HP "HP C2520A" C2520A scsi HP "HP C2520A" see the GENERAL INFO in "man sane-scsi" for details. -- 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.