Bug 62293
Summary: | Device couldn't be opened for scanning | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Joachim Kunze <joachim> |
Component: | sane-backends | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | skipjack-beta1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-06-18 19:01:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Kunze
2002-03-29 09:00:46 UTC
Previous versions? Do you mean in 7.2, or just before applying skipjack updates? It worked pretty well until 7.2 and with the 2.4.9-versions of Skipjack. From the 2.4.18-based versions on scanning don't work. Unfortunately with the change to the 2.4.18 kernels also the sane-versions changed, but with a try with 2.4.9-31 I had the same problem :-( 2.4.9-version of skipjack?? Please confirm the versions of both the kernel and sane-backends when it last worked. Also, are you trying this as root or as a non-root user? What model of scanner is this? Do you have a symlink /dev/scanner? (If not you'll need to make one.) Sorry I was not precise enough - I meant the 2.4.9-x kernel-based Skipjack versions. The symlink to the right device exists Last time it worked with the following versions: kernel: 2.4.9-31 sane-backends: 1.0.7-4 or previous (here I'm not sure) The scanner is a Mustek 12000SP (SCSI) and it worked from 7.0-7.2 without any problems The SCSI-controller is an Adaptec 2940 UW. It neither works as root nor as a user. Can you try backing off to a kernel/sane-backends combination that you can test works, so that we can find out if it's a kernel problem or a SANE one? Thanks. (You can use the --oldpackage rpm flag to 'upgrade' to older versions.) I've tested a lot the last week wtiht the following results: - when I use the sane-backends-1.0.5-4 or sane-backends-1.0.5-4.1 it works pretty well with all kernel versions from 2.4.9-31 till 2.4.18-0.21 - when I switch to a version of sane >= 1.0.7-4, xsane can't detect the device Hope that helps. Unfortunately I'm on holiday from tomorrow on. Please show me the output of 'cat /proc/scsi/scsi'. Et voil` ------------------------------------------------------------------------- Attached devices: Host: scsi0 Channel: 00 Id: 05 Lun: 00 Vendor: SCANNER Model: Rev: 2.02 Type: Scanner ANSI SCSI revision: 01 CCS Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: ARCHIVE Model: Python 04106-XXX Rev: 727A Type: Sequential-Access ANSI SCSI revision: 02 I'm pretty sure that this is fixed in 1.0.8. You might be able to work around it by changing 'scsi SCANNER' in /etc/sane.d/mustek.conf to 'scsi * * Scanner'. Sorry - I tried the recommended changements in /etc/sane.d/mustek.conf, but the scanner is still not recognized by xsane. On another machine with a completely different configuration (only the Adaptec 2940 UW is the same type) I received the same result wit a microtek scanner. Using the old 7.2 packages resolved the problem. Are you able to try rebuilding 1.0.8 from source? There is a .src.rpm in rawhide (ftp.redhat.com/pub/redhat/linux/rawhide/).. Hi Tim, no problem - already compiled, installed and it works on both machines pretty fine now. Thank you very much - can we in Germany expect a german version soon? What about ocr support? Regards, Joachim |