Help with Printer

Ill make it short and simple hehe.
I had always used until now Opensuse 32 bits. Now i needed 64 bits to be able to fun Folding@Home. Problem is, my Canon Mp160 printer doesent work, ive tried EVERYTHING and no results (this includes german sites etc :stuck_out_tongue: )

From this website which is the closest hardware store from where i live, which printer is supported by OpenSuse 64 bits?

PC FACTORY : Tu centro tecnológico

Thanks

If you had it working on openSuse-32 it should also work on 64 bit version.
Look at OpenPrinting database - Printer: Canon mp160 for some instructions.

> Now i needed 64 bits to be able to fun Folding@Home.

i run Folding@Home on my 32 bit openSUSE running on a 64 AMD…

that is to say: you do not have to go to openSUSE 64 in order to run
folding@…


goldie

Weird tho, Folding@Home said otherwise, u need 64 bit OS but u gotta download some 32 bit libraries.

Anyway, i did that openprinting drivers installation instructions with no success. OpenSuse now recognizes there is a printer, but cannot print, also unplugging and plugging the printer again display no changes on OpenSuse.

PD: Also from that link you gave me, its got no downloadable drivers available

On Wed August 19 2009 09:36 am, whych wrote:

>
> If you had it working on openSuse-32 it should also work on 64 bit
> version.
> Look at ‘OpenPrinting database - Printer: Canon mp160’
> (http://www.linuxprinting.org/show_printer.cgi?recnum=Canon-mp160) for
> some instructions.
>
>
assas1n;

Canon places the filters in /usr/lib/cups; you need it in /usr/lib64/cups.
The easiest way to solve this is to set up a link:


su
ln -s /usr/lib/cups/filter/pstocanonij /usr/lib64/cups/filter

Note:pstocanonij may not be your Canon filter, but you can alter this to match
the Cannon filter in /usr/lib/cups/filter.


P. V.
“We’re all in this together, I’m pulling for you.” Red Green

OMG I LOVE YOU!!!

It worked!!!
Thanks soooooooooooooooo much my friend,you just saved me 200 dollars :stuck_out_tongue:

On Wed August 19 2009 06:06 pm, assas1n wrote:

>
> OMG I LOVE YOU!!!
>
>
> It worked!!!
> Thanks soooooooooooooooo much my friend,you just saved me 200 dollars
> :stuck_out_tongue:
>
>
assas1n;

Your welcome, glad to have helped you out. Enjoy your printer. For my own
education can you tell me if “pstocanonij” was the name of the Canon filter
for the mp160? I don’t have a Canon printer and just happen to know the
solution to this problem.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

per http://folding.stanford.edu/English/Download#ntoc1 version 6.02
for Linux/BSD is 32 bit…

version 6.24beta is 64, but did you READ the info on their beta
software? “As in the use of any beta software, please make sure to
back up your hard drive before installing. DO NOT not run a beta
client if you or your machines cannot tolerate even the slightest
instability or problems. Beta clients and servers performance may vary
significantly from standard FAH clients . . .”


goldie

Linux (x86) and BSD combined uniprocessor and SMP client (32-bit build; 64-bit OS required for SMP)

And yes, canon filter was named as you said, pstocanonij

dhcppc0:/home/gabriel/Documents # apt-get install scangearmp-common-1.00-2.i386.rpm
Leyendo listas de paquetes… Done
Construyendo árbol de dependencias… Done
Selecting scangearmp-common.32bit for ‘scangearmp-common-1.00-2.i386.rpm’
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
La siguiente información puede ayudar a resolver la situación:

The following packages have unmet dependencies:
scangearmp-common.32bit: Depends: libusb but it is not installable
E: Broken packages

assas1n wrote:
> Linux (x86) and BSD combined uniprocessor and SMP client (32-bit
> build; 64-bit OS required for SMP)

i can read that…and understand it, but i’m not sure you do:

you can run one instance of FAH 6.02 on a 32 bit single core machine
running openSUSE 32 bit…

you can run multiple instances (each in their own directory) of FAH
6.02 on a 32 bit mulit-core machine running openSUSE 32 bit, and load
all cores…

you can run one instance of FAH 6.02 on a 64 bit single core machine
running openSUSE 32 bit…

you can run multiple instances (each in their own directory) of FAH
6.02 on a 64 bit multiple processor/core machine running openSUSE 32
bit, and load all cores…

you can run one instance of FAH 6.02 on a 64 bit multiple-core machine
running openSUSE 64 bit, and load all cores…

you can run one instance of FAH 6.24beta on a 64 bit single core
machine running openSUSE 64 bit…

you can run one instance of FAH 6.24beta on a 64 bit multiple
processor/core machine running openSUSE 64 bit, and load all cores…

as i said originally “you do not have to go to openSUSE 64 in order to
run folding@…”

it is running now on my single core AMD64 with openSUSE 32, i’ve run
it for years…from http://folding.stanford.edu/English/Stats today’s
current newcredit stats for me: 65879 330 0


goldie

thing is, running a SMP client on a quad core gives much more ppd than running 4 simple clientsat the same time

assas1n wrote:
> thing is, running a SMP client on a quad core gives much more ppd than
> running 4 simple clientsat the same time

ok…personally, i think it is more trouble than worth to switch from
32 to 64 for me, and i’ll not switch until either i have the need
to, OR 64 irons out some more bugs/frustrations…

i loaded up up in about the 9.3 time frame and found it far too rough
around the edges and requiring too many workarounds…

i KNOW it is far better now but i’ll not ‘upgrade’ to 64 until i have
the need or am forced to…and, so far FAH does not force me or
you to install 64…apparently you wanted to in order to get the
last protein folded some seconds sooner than it would have been if you
had stayed with dependable/reliable/more fuss free 32…

which is not the same as saying: “i needed 64 bits to be able to fun
Folding@Home” which what i first responded to…


goldie

Well, as you know 64 bits does bring many performance improvement in many areas, such as video encoding/decoding, music, etc.

In order to fully take advantage of the quad core i bought, which is twice as expensive as an AMD X2, i have to install 64 bits.
Folding@Home does not only take seconds less to finish a WU but more like hours less.

PD: Main problem is only my scanner on 64 bits. EVERYTHING else until now is working flawlessly.

> but more like hours less.

WOW! i may be moving to 64 sooner than i thought…
thanks for that info…


goldie

I dont get ur point, look if you dont like 64 bits for whatever stupid reason, then dont use it, nobody is telling you otherwise.
What im saying is that im happy with 64, just as you are happy with 32.

sorry to bring back this old thread, but now im trying to get the scanner working.

I did this:

dhcppc0:/home/gabriel/Documents # rpm -ivh scangearmp-common-1.00-2.i386.rpm
error: Error de dependencias:
        libgimp-2.0.so.0 se necesita para scangearmp-common-1.00-2.i386
        libgimpbase-2.0.so.0 se necesita para scangearmp-common-1.00-2.i386
        libgimpcolor-2.0.so.0 se necesita para scangearmp-common-1.00-2.i386
        libgimpmath-2.0.so.0 se necesita para scangearmp-common-1.00-2.i386
        libusb se necesita para scangearmp-common-1.00-2.i386

Doing apt-get install scangearmp-common-1.00-2.i386.rpm does no good, says the dependencies cant be found.

Also:

dhcppc0:/home/gabriel # sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04a9 [Canon], product=0x1714 [MP160]) at libusb:001:012
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.