---------- Forwarded Message ----------
Subject: Re: [newbie] Acerfirm installed OK Date: Thursday 15 July 2004 06:11 am From: Frank <[EMAIL PROTECTED]> To: et <[EMAIL PROTECTED]> Updating the real cause for those that follow: The problem was with confusing 'acerfirm' and 'u96v121.bin'. In the past I used the Acerfirm file wereas here the *.bin file was required. Once I pointed things to the correct file, I was able to go the GUI way and use MCC to configure the scanner for me. Do use the GUI menu for starting either XSane or Kooka for your scanning because I get unreliable results starting xsane from the command line. My next mission is to get Gimp2 to see the scanner, but I have Gimp1.2 to see me through for now. Regards Frank Big or small, a challenge requires the same commitment to resolve. Registered Linux User # 324213 et wrote: >On Saturday 26 June 2004 12:25 am, Frank wrote: >>Thanks for that et, but no go as yet I'm afraid. >> >>The firmware entry is toward the top of my /etc/sane.d/snapscan.conf >>file and I have amended it to: >> >>firmware /home/frank/u96v121.bin = [ I have added this line.] >>#firmware /home/frank/acerfirm = [ this line did read = >>"/usr/share/sane/firmware/acerfirm" and I do have the acerfirm file >>within both directories.] I take it I can only have one firmware pointer >>at a time? > >only one firmware can be uploaded to the scanner, and it _must_ be the > correct one. it may be that u96v121.bin is not in your /home/frank > directory, or that for your scanner u96v121.bin is not the correct *.bin > file. >when you start xsane from the command ine, what copy and paste here the > error message you get. >also copy and paste what 'sane-find-scanner', then, 'scanimage -L' tells you >(without the quotes). > >>I'm still trying using 2.6.3-7 kernel mind, and elsewhere here I have >>been advised to use the 2.4 kernel [ which I have installed and ready to >>go.] It's just a pain to have to reboot into the alternative system to >>just do a scan. I may as well boot back into WinMe, get the scan done >>and go from there. >> >>Any more ideas? >> >>Frank >> >>et wrote: >>>>On Friday 25 June 2004 04:50 am, Frank wrote: >>>>>>Having a devels own time of getting my scanner up and running. >>>>>> >>>>>>I have a Prisa Acer 640u which is recognised, albeit with an acerfim >>>>>>file, by sane .92 [ ex Mandrake 9.1 days ], but under Mandrake 10 >>>>>>Official and using MCC, no go! >>>>> >>>>>I can Identify with the problems, I have the cheaper little brother to >>>>>your 640u, the 340U,,, same headaches, but when it works, it is well >>>>>worth the 32 dollars I paid for it 4 years ago. >>>>> >>>>>some other impootant facts needed in geting it running would be what >>>>>kernel you are using, and what desktop (kde? Gnome? xfce?). for me, >>>>>using 2.6.3-4mdksmp, kde, it does not even require anything setup in >>>>>mcc, I just start xsane, however I have had to edit the file >>>>>/etc/sane.d/snapscan.conf to tell it where to find my 'firmware' (a .bin >>>>>file that was on the windows install disks, and depends on what scanner >>>>>you use, this is the property binarary file your scanner needs to run to >>>>>set itself up. >>>> >>>>2.6.3-7mdk && KDE >>>>[ When using MDK9.1 I used to see a Desktop Icon reference showing me >>>>that the scanner was ready to go. Not since I went to MDK10 though?] >>>> >>>>My "/etc/sane.d/snapscan.conf" entries....... >>>><snip> >>>>firmware /usr/share/sane/firmware/acerfirm ( And I re-copied the >>>>original here to be sure.) >>> >>>look for a line that starts with the word "firmware". >>>that is the arguement you need to change from the same words as the error >>>quote '/path/to/your/firmware' you need to change that path to be the >>>absolute path of what ever is the *.bin file. >>>I have copied my *.bin file, to my home directory, so on mine that line >>>reads firmware /home/et/u34v110.bin >>>the numbers change a little based on what scanner you have, my guess for >>>your scanner, if you have your windows parttiton mounted as '/mnt/win_c' >>>you should remove the "#" at the begining of the line, and have the line >>>say; "firmware /mnt/win_c/mira/Mira341U/bin/u64v119.bin" (without the >>>quotes) or where ever that file is o your computer. >>> >>>>[ Note: not recognised by our scanners as 'firmware' but rather >>>>'acerfirm' .. but then I guess you have been there?] >>>><snip again> >>>># Benq/Acer/Vuego 640U >>>>usb 0x04a5 0x2060 >>>><end snip> >>>> >>>>>>Oh, MCC goes through all the recognition stuff OK and informs me that >>>>>>the scanner is now ready to use under Xsane or/and Kooka. Yeah, right. >>>>>> >>>>>>Fire up xsane and ........... nothing............ seen or even hinted >>>>>>at. >>>>>> >>>>>>Did I miss doing something else with MCC? >>>>> >>>>>did you try and start xsane from the command line? sometimes that gives >>>>>many more error messages than when you click on a gui >>>> >>>>Either way all I get is ................ Invalid Argument >>>>This is what makes me think I have missed something. >>>> >>>>> Doing #lsusb sees the scanner OK. >>>>> >>>>> Bus 001 Device 002: ID 04a5:2060 Acer Peripherals Inc. (now BenQ Corp.) >>>>> Prisa 620U+/640U ------------------------------------------------------- -- linux counter #167806
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
