Mailinglist Archive: opensuse-bugs (7117 mails)
| < Previous | Next > |
[Bug 350688] SCSI hardware configuration scanner os: opensuse 10.3
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 29 Jan 2008 04:43:24 -0700 (MST)
- Message-id: <20080129114324.AA23124538D@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=350688
User jsmeix@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=350688#c5
Johannes Meixner <jsmeix@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #5 from Johannes Meixner <jsmeix@xxxxxxxxxx> 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
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.
User jsmeix@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=350688#c5
Johannes Meixner <jsmeix@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #5 from Johannes Meixner <jsmeix@xxxxxxxxxx> 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.
| < Previous | Next > |