https://bugzilla.novell.com/show_bug.cgi?id=470959 User wolfgang@rosenauer.org added comment https://bugzilla.novell.com/show_bug.cgi?id=470959#c2 --- Comment #2 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2009-01-30 07:08:35 MST --- (In reply to comment #1)
I assume it does not only happen with xscanimage but alos with xsane and scanimage so that it is a general device I/O issue.
Yes, true. It's for sure no xscanimage thing but probably an hplip one.
In the past any "error during device I/O" has always been a lower-level USB issue where I cannot help at all so that I close it as "wontfix" which actually means "cantfix". (Or I could close it with "worksforme" because for me it works - but I don't have your model.)
I don't get any error messages about low level usb issues with dmesg or in /var/log/messages. The communication with the device works as I can successfully print using the hp backend. I guess it's something to report for hplip upstream?
Setting the SANE_DEBUG_HPAIO environment variable will display the following messages to stderr. SANE_DEBUG_HPAIO=2 (error messages) SANE_DEBUG_HPAIO=6 (error messages + device info) SANE_DEBUG_HPAIO=8 (error messages + device info + sane api calls)
[sanei_debug] Setting debug level of hpaio to 8. [hpaio] sane_hpaio_init(): scan/sane/hpaio.c 1581 [hpaio] sane_hpaio_get_devices(local=0): scan/sane/hpaio.c 1600 [hpaio] sane_hpaio_open(/usb/Officejet_6300_series?serial=CN69DCH2GW04M4): scan/sane/hpaio.c 1635 [hpaio] device ID string=<MFG:HP;MDL:Officejet 6300 series;CMD:MLC,PCL,PML,DW-PCL,DESKJET,DYN;1284.4DL:4d,4e,1;CLS:PRINTER;DES:Q8066B;SN:CN69DCH2GW04M4;S:038000C484001021002c1800018c2880049;J: ;Z:0102,0503fac9015cc9,0600;BT:000000000000,4F66666963656A6574203633303020736572696573,0000008F,60;>: scan/sane/hpaio.c 1684 [hpaio] Model = Officejet_6300_series: scan/sane/hpaio.c 1692 [hpaio] Scanner type=SCL: scan/sane/hpaio.c 1774 [hpaio] failed to open pml channel: scan/sane/hpaio.c 674 [hpaio] sane_hpaio_exit(): scan/sane/hpaio.c 1594
Often it helps to connet the scanner directly with a short USB cable to the computer. Additionally it may help to use explicitely the slower USB 1 (and not USB 2 which might be too fast for your hardware) via unloading/loading appropriate kernel module(s).
It's already connected using a short USB cable directly to the internal USB hub and the other "devices" (printer, cardreader) work correctly. I'll report that for hplip but wanted to add that information here as well. -- 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.