Hans, Can you give me your current snapscan.conf and firmware file?
Thanks, Jaime On 5/30/07, Hans van Esdonk <[EMAIL PROTECTED]> wrote: > > Hi Jaime, > > Last week I tried the scanbuttond trick but it didn't work. > But believe it or not....at the moment the scanner works and I still > don't know why. > Different from some time ago is that I changed the line in snapscan.conf > like described below by Conrad. I remember something with USB when > installing version 6.10. It could be installed but sometimes the PC > stayed hanging during boot up of 6.10. I switched off the option "usb > legacy support" in the bios of my PC and since then it worked nice. > 7.04 runs nicely too with this option off. > Now xsane works both from the gui and terminal window, but I'm not sure > if this will be the case tomorrow. > > Hans > > > Jaime schreef: > > Hans, > > > > Exactly the same problem here. I think it is related with the > USB_SUSPEND > > issue. > > > > Please, can you test if now scanbuttond solves the problem? (in my case, > it > > remains the same ....) > > > > On 5/30/07, Hans van Esdonk <[EMAIL PROTECTED]> wrote: > > > >> I did the things mentioned below. > >> > >> u176v046.bin was the file from disk I had to use. > >> > >> It all looked promising. The scanner worked!! > >> > >> But strange things happened. It took a lot of time before the scan was > >> possible. After 19 seconds warmup the xsane window appeared. Pressing > the > >> prescan button first led to "scanner busy" but after some time it made > a > >> prescan and I could print it out. > >> So, I tried a few times and also from the terminal window. The messages > >> were clear: first line 19 seconds warm-up and then about 20 times the > same > >> line: 20 seonds warm-up, so in total about 7 minutes. > >> Once again a try and it worked. That was the last time. The > illumination > >> tube did not return to the beginning and the scanner wasn't found > anymore. > >> So it looks if xsane only detects the scanner in the startposition > >> (detector?) > >> This is crazy!!!While typing this the scannerlight moves to the start > >> position and a scan is possible....... > >> So, what can be going on??? > >> > >> Hans van Esdonk > >> > >> > >> > >> Conrad Knauer schreef: > >> > >>> Hans van Esdonk wrote: > >>> > >>> "With my BenQ 3300U (Acer) this doesn't work. The line tube doesn't go > >>> "home" after starting xsane. If it is at home position (after using > >>> windows program mirascan) it works every now and then and I don't know > >>> why." > >>> > >>> Your scanner likely requires proprietary firmware to be loaded when > >>> running it from Linux, as per > http://snapscan.sourceforge.net/#supported > >>> > >>> Can you check to see which USB ID your scanner is specifically? To do > >>> this, install the "sane-utils" package (from the universe repository) > >>> and run "sane-find-scanner" from Terminal. > >>> > >>> For me, in the middle of the output was: > >>> > >>> "found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], > >>> > >> chip=LM9832/3) at libusb:003:007" > >> > >>> (the USB ID is the vendor/product strings; 0x04a9, 0x220e) > >>> > >>> For you the output should have vendor=0x04a5 and product as 0x20b0 or > >>> 0x20de. > >>> > >>> If its the one ending in b0, you need the firmware file u176v046.bin > >>> If its the one ending in de, you need the firmware file u222v067.bin > >>> > >>> That should be located somewhere in the Windows driver (you'll need to > >>> extract it; alternately it should be somewhere installed in Windows). > >>> > >>> Put it somewhere on your Ubuntu partition and then run, partially as > per > >>> http://snapscan.sourceforge.net/#work > >>> > >>> gksudo gedit /etc/sane.d/snapscan.conf > >>> > >>> At the very top where it says: > >>> > >>> --- > >>> # Change to the fully qualified filename of your firmware file, if > >>> # firmware upload is needed by the scanner > >>> firmware /usr/share/sane/snapscan/your-firmwarefile.bin > >>> --- > >>> > >>> change the location in that last line to the location of your firmware > >>> file. > >>> > >>> Then restart xsane and hopefully it should work :) If not, then try > the > >>> scanbuttond fix previously mentioned in this bug and see if that fixes > >>> it; please report back here either way. > >>> > >>> > >>> > >> -- > >> some usb_devices fault if usb_suspend enabled > >> https://bugs.launchpad.net/bugs/85488 > >> You received this bug notification because you are a direct subscriber > >> of a duplicate bug. > >> > >> > > > > > > -- > > > > ****************************************** > > Ningún bit ha sido maltratado durante la creación y envío de este > mensaje. > > No bit has been injured in the creation and sending of this message. > > ****************************************** > > > > > > -- > some usb_devices fault if usb_suspend enabled > https://bugs.launchpad.net/bugs/85488 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- ****************************************** Ningún bit ha sido maltratado durante la creación y envío de este mensaje. No bit has been injured in the creation and sending of this message. ****************************************** -- some usb_devices fault if usb_suspend enabled https://bugs.launchpad.net/bugs/85488 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
