[sane-devel] Canon CanoScan LiDE 35
On 10/27/05, Regin LARSEN re...@opia.dk wrote: Cameron Harris skribis/wrote: Today, I checked out a CVS copy of the sane-backends, and compiled it all with genesys support. Unfortunately it hangs when i try scanimage you've to use the genesys-sources from the experimental directory regin Well... I checked out experimental, copied the experimental/genesys/* over to the backend/ directory, then make clean/make/make install... Gets slightly further in the scanning this time. # SANE_DEBUG_GENESYS=255 scanimage -d genesys outputs lots of stuff and my scanner's head moves a little bit, flashes a few different colours.. but then it gets to... [genesys] sanei_genesys_read_data_from_scanner (size = 156 bytes) [genesys] genesys_read_valid_words [genesys] sanei_genesys_read_register (0x44, 0x00) completed [genesys] sanei_genesys_read_register (0x43, 0x00) completed [genesys] sanei_genesys_read_register (0x42, 0x00) completed [genesys] genesys_read_valid_words: 0 words [genesys] genesys_read_valid_words [genesys] sanei_genesys_read_register (0x44, 0x84) completed [genesys] sanei_genesys_read_register (0x43, 0x2b) completed [genesys] sanei_genesys_read_register (0x42, 0x00) completed [genesys] genesys_read_valid_words: 11140 words Where it stops for about 30 seconds, then... [genesys] sanei_genesys_read_data_from_scanner: reading bulk data failed: Error during device I/O [genesys] genesys_black_white_shading_calibration: Failed to read data: Error during device I/O [genesys] genesys_flatbed_calibration: failed to do dark+white shading calibration: Error during device I/O [genesys] genesys_start_scan: failed to do flatbed calibration: Error during device I/O scanimage: sane_start: Error during device I/O [genesys] sane_cancel: start Any ideas? Thanks :) -- Cameron Harris
[sane-devel] Canon CanoScan LiDE 35
On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Cameron Harris schrieb: Well... I checked out experimental, copied the experimental/genesys/* over to the backend/ directory, then make clean/make/make install... Gets slightly further in the scanning this time. # SANE_DEBUG_GENESYS=255 scanimage -d genesys outputs lots of stuff and my scanner's head moves a little bit, flashes a few different colours.. but then it gets to... [genesys] sanei_genesys_read_data_from_scanner (size = 156 bytes) [genesys] genesys_read_valid_words [genesys] sanei_genesys_read_register (0x44, 0x00) completed [genesys] sanei_genesys_read_register (0x43, 0x00) completed [genesys] sanei_genesys_read_register (0x42, 0x00) completed [genesys] genesys_read_valid_words: 0 words [genesys] genesys_read_valid_words [genesys] sanei_genesys_read_register (0x44, 0x84) completed [genesys] sanei_genesys_read_register (0x43, 0x2b) completed [genesys] sanei_genesys_read_register (0x42, 0x00) completed [genesys] genesys_read_valid_words: 11140 words Where it stops for about 30 seconds, then... [genesys] sanei_genesys_read_data_from_scanner: reading bulk data failed: Error during device I/O [genesys] genesys_black_white_shading_calibration: Failed to read data: Error during device I/O [genesys] genesys_flatbed_calibration: failed to do dark+white shading calibration: Error during device I/O [genesys] genesys_start_scan: failed to do flatbed calibration: Error during device I/O scanimage: sane_start: Error during device I/O [genesys] sane_cancel: start Any ideas? Thanks :) Does it always stop there? It looks like the usb connection somehow broke while transfering data. Does the scanner re-register with your system at the moment the transmission stops? There will be some kernel messages about a new usb device in that case. Yeah it always stops there, nothing in dmesg about it. -- Cameron Harris
[sane-devel] Canon CanoScan LiDE 35
Cameron Harris schrieb: On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Does it always stop there? It looks like the usb connection somehow broke while transfering data. Does the scanner re-register with your system at the moment the transmission stops? There will be some kernel messages about a new usb device in that case. Yeah it always stops there, nothing in dmesg about it. Then i would like to have a full log, with SANE_DEBUG_GENESYS=255, SANE_DEBUG_GENESYS_GL841=255, SANE_DEBUG_SANEI_USB=255. That log will get large. Please compress it and send it to me(The list won't accept messages larger than 50k). If the compressed log is larger than 4MB we need to find a different transport channel. Regards, Pierre
[sane-devel] Canon CanoScan LiDE 35
Cameron Harris schrieb: Right.. got a full compressed log, attached it to this message. Thanks :) Thanks for the log. Please try the attached patch. I don't know if it helps. The backend is trying to read 156 bytes from the scanner, but libusb does not provide that much. We need to find out where the data is lost. The patch addresses one possible cause. Regards, Pierre -- next part -- A non-text attachment was scrubbed... Name: bulkin.diff Type: text/x-patch Size: 514 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051030/cd1d1128/bulkin.bin From fba...@gmx.net Sun Oct 30 17:26:46 2005 From: fba...@gmx.net (Franz Bakan) Date: Sun Oct 30 18:27:18 2005 Subject: [sane-devel] Build system changes -- please test! In-Reply-To: 20051029201432.ga1...@meier-geinitz.de Message-ID: mailman.86.1130696838.11105.sane-de...@lists.alioth.debian.org On Sat, 29 Oct 2005 22:14:32 +0200, Henning Meier-Geinitz wrote: I have just committed some changes regarding the Makefiles to the sane-backends CVS. Please test if sane-backends can still be built and installed on your system (especially OpenBSD and MacOS X). still builds on OS/2 :-) Franz
[sane-devel] Canon CanoScan LiDE 35
On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Cameron Harris schrieb: Right.. got a full compressed log, attached it to this message. Thanks :) Thanks for the log. Please try the attached patch. I don't know if it helps. The backend is trying to read 156 bytes from the scanner, but libusb does not provide that much. We need to find out where the data is lost. The patch addresses one possible cause. Regards, Pierre U.. well... good and bad news. The patch made it get past where it was stopping before, and now loads of rubbish appears on the terminal when I do scanimage. I ran xsane to see if it was scanning anything, hit acquire preview. The scanner made a few noises, then went bp until the scan was done. While it was beeping, the scanner head was lit green. The image produced was just grey lines on a black-ish background. One good thing is that if I open the scanner lid mid-scan, it seems to have an effect on the image appearing on screen. Sane Screenshot: http://htsc01.b3ta.org/scan.png Where it gets lighter is where I opened the lid, and darker again when I closed it. I'll try getting it onto a Windows system and actually making sure the scanner works properly :|, maybe I could get a USB snoop while I'm at it, just in case. Thanks again :) . -- Cameron Harris
[sane-devel] Canon CanoScan LiDE 35
Cameron Harris schrieb: On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Thanks for the log. Please try the attached patch. I don't know if it helps. The backend is trying to read 156 bytes from the scanner, but libusb does not provide that much. We need to find out where the data is lost. The patch addresses one possible cause. Regards, Pierre U.. well... good and bad news. The patch made it get past where it was stopping before, and now loads of rubbish appears on the terminal when I do scanimage. I ran xsane to see if it was scanning anything, hit acquire preview. The loads of rubbish actually are the requested image. scanimage outputs on stdout per default. The scanner made a few noises, then went bp until the scan was done. While it was beeping, the scanner head was lit green. Did the head move? xsanes default is to scan in grey mode, which is translated into a monochrome green scan. The image produced was just grey lines on a black-ish background. One good thing is that if I open the scanner lid mid-scan, it seems to have an effect on the image appearing on screen. Sane Screenshot: http://htsc01.b3ta.org/scan.png Where it gets lighter is where I opened the lid, and darker again when I closed it. I guess the calibration step failed. Each scan should look like this: - (optionally)move head home - blink lamp - move head away from home - blink lamp - move head home - (maybe) blink lamp - move head away from home - blink lamp - move head home - do a short scan - move head home - do the real scan If the head moved in the short scan part, please compress and send me black_white_shading.pnm. That image should be generated while using scanimage with SANE_DEBUG_GENESYS=255. I'll try getting it onto a Windows system and actually making sure the scanner works properly :|, maybe I could get a USB snoop while I'm at it, just in case. Regards, Pierre
[sane-devel] Canon CanoScan LiDE 35
On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Cameron Harris schrieb: On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote: Thanks for the log. Please try the attached patch. I don't know if it helps. The backend is trying to read 156 bytes from the scanner, but libusb does not provide that much. We need to find out where the data is lost. The patch addresses one possible cause. Regards, Pierre U.. well... good and bad news. The patch made it get past where it was stopping before, and now loads of rubbish appears on the terminal when I do scanimage. I ran xsane to see if it was scanning anything, hit acquire preview. The loads of rubbish actually are the requested image. scanimage outputs on stdout per default. The scanner made a few noises, then went bp until the scan was done. While it was beeping, the scanner head was lit green. Did the head move? xsanes default is to scan in grey mode, which is translated into a monochrome green scan. The image produced was just grey lines on a black-ish background. One good thing is that if I open the scanner lid mid-scan, it seems to have an effect on the image appearing on screen. Sane Screenshot: http://htsc01.b3ta.org/scan.png Where it gets lighter is where I opened the lid, and darker again when I closed it. I guess the calibration step failed. Each scan should look like this: - (optionally)move head home - blink lamp - move head away from home - blink lamp - move head home - (maybe) blink lamp - move head away from home - blink lamp - move head home - do a short scan - move head home - do the real scan If the head moved in the short scan part, please compress and send me black_white_shading.pnm. That image should be generated while using scanimage with SANE_DEBUG_GENESYS=255. I'll try getting it onto a Windows system and actually making sure the scanner works properly :|, maybe I could get a USB snoop while I'm at it, just in case. Regards, Pierre Fantastic! I just messed around with the lock button on the bottom of the scanner, locking and unlocking a few times, then tilting it to the side a bit.. and it works now! All I can guess is that someone picked up the scanner when it was unlocked and I wasn't looking and it made the scanner head lock in a funny position... but now it works, so that's cool. :D It was the bulkin patch that seemed to actually make it scan. Thanks for your help :) -- Cameron Harris
[sane-devel] Canon CanoScan LiDE 35
Cameron Harris schrieb: Fantastic! I just messed around with the lock button on the bottom of the scanner, locking and unlocking a few times, then tilting it to the side a bit.. and it works now! All I can guess is that someone picked up the scanner when it was unlocked and I wasn't looking and it made the scanner head lock in a funny position... but now it works, so that's cool. :D It was the bulkin patch that seemed to actually make it scan. Thanks for your help :) Thanks for your valuable input. I commited the change. Regards, Pierre
[sane-devel] Canon CanoScan LiDE 35
Hi, On Thu, Oct 27, 2005 at 11:23:13PM +0100, Cameron Harris wrote: Today, I checked out a CVS copy of the sane-backends, and compiled it all with genesys support. Unfortunately it hangs when i try scanimage (debug output:) Are you sure that you use the experimental CVS? I'm asking because ... The problem seems to be occuring in genesys_gl841.c, ~4390: /* Write initial registers */ RIE (sanei_genesys_bulk_write_register (dev, dev-reg, GENESYS_GL841_MAX_REGS * 2)); ... this code is in line 4922 in experimental CVS. Any ideas? I think read previously in the mailing list that gl841 support is nearing completion... In experimental CVS. Not yet in the normal CVS. Bye, Henning
[sane-devel] Canon CanoScan LiDE 35
Today, I checked out a CVS copy of the sane-backends, and compiled it all with genesys support. Unfortunately it hangs when i try scanimage (debug output:) [genesys] sanei_genesys_create_slope_table: 8 steps, step_type = 0, exposure_time = 250, same_speed =0 [genesys] sanei_genesys_create_slope_table: yres = 600.00 [genesys] sanei_genesys_create_slope_table: returns sum_time=371, completed [genesys] sanei_genesys_create_slope_table: 255 steps, step_type = 1, exposure_time = 250, same_speed =0 [genesys] sanei_genesys_create_slope_table: yres = 600.00 [genesys] sanei_genesys_create_slope_table: returns sum_time=9767, completed [genesys] sanei_genesys_write_register (0x0e, 0x00) completed [genesys] sanei_genesys_bulk_write_register (size = 162) *hang* [genesys] sanei_genesys_bulk_write_register: failed while writing bulk data: Error during device I/O scanimage: open of device genesys:libusb:004:006 failed: Error during device I/O The problem seems to be occuring in genesys_gl841.c, ~4390: /* Write initial registers */ RIE (sanei_genesys_bulk_write_register (dev, dev-reg, GENESYS_GL841_MAX_REGS * 2)); Any ideas? I think read previously in the mailing list that gl841 support is nearing completion... Thanks in advance :) -- Cameron Harris
