https://qa.mandrakesoft.com/show_bug.cgi?id=1220





------- Additional Comments From [EMAIL PROTECTED]  2003-02-20 11:59 -------
Still present in RC1. 



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
Scannerdrake tells me that my scanner is not found in database. The sane-config man 
entry 
is present, no executable.  
 
sane-find-scanner tentatively locates a scanner-- this is nice. 
 
Ok, edit epson.conf 
 
try again 
 
same 
 
RTFMing for 2 hours.... 
 
edit dll.conf to say 
 
#net 
epson 
 
(save file) 
 
[cook@pcp885780pcs cook]$ sane-find-scanner /dev/usb/scanner0 
 
  # No SCSI scanners found. If you expected something different, make sure that 
  # you have loaded a SCSI driver for your SCSI adapter. 
 
found USB scanner (vendor=0x04b8, product=0x0110) at /dev/usb/scanner0 
  # Your USB scanner was detected. It may or may not be supported by 
  # SANE. Try scanimage -L and read the backend's manpage. 
 
  # Scanners connected to the parallel port or other proprietary ports can't be 
  # detected by this program. 
 
  # You may want to run this program as root to find all devices. Once you 
  # found the scanner devices, be sure to adjust access permissions as 
  # necessary. 
[cook@pcp885780pcs cook]$ 
 
NOW, the thing works. Leaving dll.conf defaulted to net stinks, the sane-find-scanner 
thng is 
not changing, and sane-config which one normally uses to autoconfig is missing. 
 
Looks like the SANE DB entry for the Epson Perfection 1650/1650 Photo is missing an 
entry, 
or only has Epson Perfection 1650 instead of the dual entry. the driver is in the 
epson lib, 
and is teh GT-8200 module inside the libsane-epson lib and the scanner works. 
 
Problem is multitiered, given it was discovered tentatively at first as an Epson, the 
epson lib 
should have been set in as backend to use. I also had to edit modules.conf and tell it 
what 
scanner to use as an option, then do a scanner modprobe, but that alone was not 
enough. 
 
All the above had to be done also (note that the installer found the scanner and 
location on 
USB bus, and I had an icon that did nothing except gen error in title. this is also 
for others. 
Beta 2 had no scanner for my scanner, and did nada with it except an icon that did not 
run 
XSANE right. 9.0 can set up my scanner to same driver, the GT-8200, out of box. Please 
fix 
xref DB you use to match, or the DB that you are bundling with SANE for sane to know 
what 
modules to set in, adn make sure that when scanners are configed they are configged 
all the 
way or get /usr/bin/sane-config back into the RPM set. The SANE-Epson man page lists a 
Epson Perfection 1650 (this should be a Epson Perfection 1650/1650 Photo in DB, adn 
xref'd to the Epson GT-8200 submodule). 
 
Fix or document how to fix in simple linear way: 
 
run sane-find-scanner 
 
take vendor and product info, add a line like: 
options scanner vendor=<vendor#> product=<prod#> 
 
(so I stuck in:  
options scanner vendor=04b8 product=0110 
) 
take name of vendor, edit that vendor's conf file so only the line that applies is 
used: 
 
SCSI was defaulted, most Epson's are USB, so I had to comment the SCSI line and 
uncomment the /dev/usb/scanner0 line (which was already set up as a base layer device 
at 
install, the sane modules never got hooked and I think the scanner kernel module was 
not 
hooked *right* to begin with) 
 
rerun sane-find-scanner as in excerpt of console session above with device name: 
sane-find-scanner /dev/usb/scanner0 
(this functions as a test call, then SANE remembers its config well, and after that 
XSane 
loads fine and works) 
 
Till and MCC\Drakxtools teams, printing works GREAT, but scanning does not unless one 
totally manually installs. The printerdrake module needs to be focus-forced to paint 
in front 
of the MCC main window, only way I could invoke and see was from Konsole. Scannerdrake 
I coudl not get to run, from console, about 30 TODO: force-focus errors looped 
followed by 
a DB mismatch that was given as title of bug. 
 
John Danielson

Reply via email to