Kyocera Mita FS-1020D
Now I wanted my black and white laser printer, en, bring FS-1020D Kyocera Mita
, to work. After clicking on 'System Preferences - Advanced - Printer Configuration' you have to 'New Printer - New Network Printer "select. Then the dialog displays, also on my USB connected printer (must have been turned on before, of course). Since there is no button to add a locally connected printer, the button seems to just be mislabeled, because you can not install it as I said only network printer.
Because the printer is PostScript capable (at that time I had taken when buying it, so it definitely works on Linux), it could be him with a generic PostScript driver and running. It is better, however, if any, to use a special driver for the specific printer model (if available).
(K) Ubuntu 9.04 already drivers for this model. It is recommended that the Sunday, May 3, 2009
8 Horsepower Mtd Snowblower
Foomatic / gutenprint . After selection of the same but the error message comes There was an error during the CUPS operation: 'server-error-internal-error' . Alternatively you can use the Foomatic / Postscript
who can install it without complaint. However, I'm not sure if all drivers are supported in this printer-specific functions, as is the case with the more specific gutenprint driver. 
why I have chosen a different path! on Kyocera support page there is a PPD file to download for this printer model. After unpacking can be found in the folder "German" PPD files for many printers, including the FS-1020D. If your printer is installed on the KDE Wizard is chosen in the second step, "Provide PPD file" and specify the path to the model-specific PPD file. Now the installation works fine and it should also "special functions" of the model, eg, duplex, additional memory, toner save, save paper, etc. unterstützr. On my printer at least this was the way a short test has shown.
UPDATE: I have a bug
UPDATE2: The problem is solved (see above shoulder), let's see how long does it take until the update is played regularly ...
UPDATE: I have a bug
put up for it. UPDATE2: The problem is solved (see above shoulder), let's see how long does it take until the update is played regularly ...
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment