| 1 |
This FAQ is supposed to answer a lot of questions that users usually ask |
| 2 |
when they run into problems when installing or using the driver. It is |
| 3 |
still under development and answers such questions in no particular order. |
| 4 |
I suggest that you read all sections of this FAQ in case of problems, there |
| 5 |
may be valuable information even in sections where you didn't expect something |
| 6 |
to solve your problem. This is an early version of this FAQ, so suggestions |
| 7 |
for improvents in this FAQ are always welcome. |
| 8 |
|
| 9 |
|
| 10 |
Contents |
| 11 |
|
| 12 |
1. I have downloaded min12xxw, how do I build it? |
| 13 |
2. How can I test if min12xxw and the printer talk to each other? |
| 14 |
3. I've built min12xxw, how do I get my documents to print? |
| 15 |
4. When I print multiple documents one right after the other, some pages are |
| 16 |
incomplete, blank or missing. What's happening? |
| 17 |
5. Graphics printouts are too dark/show 'banding' instead of smoothly varying |
| 18 |
shades of grey. Can't one do this better? |
| 19 |
|
| 20 |
|
| 21 |
|
| 22 |
1. I have downloaded min12xxw, how do I build it? |
| 23 |
|
| 24 |
Unpack the archive containing min12xxw: |
| 25 |
|
| 26 |
gunzip -dc min12xxw-x.y.z.tar.gz | tar xvf - |
| 27 |
|
| 28 |
Replace x.y.z by the version number appropriate for the release you have. |
| 29 |
This should leave you with a directory with the sources of min12xxw named |
| 30 |
min12xxw-x.y.z. In order to use the driver, you need to build it first. |
| 31 |
You'll need a C compiler and a make utility (these are usually available on |
| 32 |
most Linux systems. If not, use the installation program that came with your |
| 33 |
distribution to install them (they can usually be found in a category called |
| 34 |
something like development)). To build the driver, type: |
| 35 |
|
| 36 |
cd min12xxw-x.y.z |
| 37 |
./configure |
| 38 |
make |
| 39 |
|
| 40 |
The first command brings you into the directory into which the sources were |
| 41 |
unpacked, the second has a look at the characeristics of your system from the |
| 42 |
point of view of a programmer to adapt the min12xxw sources to your system and |
| 43 |
the last command actually builds min12xxw. To be able to use it, you need to |
| 44 |
install it onto your system in a place where it can be easily found by other |
| 45 |
programs. To do so, you need to become root (log in as root and cd to the |
| 46 |
directory where you unpacked the min12xxw sources or use su or sudo): |
| 47 |
|
| 48 |
make install |
| 49 |
|
| 50 |
Afterwards, you may want to tidy up after the build process: |
| 51 |
|
| 52 |
make clean |
| 53 |
|
| 54 |
|
| 55 |
2. How can I test if min12xxw and the printer talk to each other? |
| 56 |
|
| 57 |
Now you can test if your PC and your printer talk to each other. Connect your |
| 58 |
printer to your PC and type one of the following lines: |
| 59 |
|
| 60 |
min12xxw -m 1300W -d /dev/lp0 -s |
| 61 |
min12xxw -m 1300W -d /dev/usb/lp0 -s |
| 62 |
|
| 63 |
Use the first line if you connected it to a parallel port, the second if you |
| 64 |
connected it via USB. You should also adapt the 1300W to the printer model you |
| 65 |
are actually using (e.g. if you have a 1250W, it should read ... -m 1250W ...) |
| 66 |
If you have more than one printer connected, or have several parallel ports, |
| 67 |
you may also have to use something like /dev/lp1 or /dev/usb/lp2 instead. |
| 68 |
Usually, the defaults are just fine. Note that you have to be root to use the |
| 69 |
driver in this way because it talks directly to the printer. You should see a |
| 70 |
message indicating the printer model, status, and how many pages it has |
| 71 |
already printed in its life. (See below for an example.) Please note that on |
| 72 |
other operating systems than Linux, the device file for the printer might be |
| 73 |
called differently (i.e. not something like /dev/lp0). Also, your OS might not |
| 74 |
support reading from a printer port. Some very old parallel ports do in fact |
| 75 |
not allow this because of different hardware used back then. If you have a |
| 76 |
a newer computer (anything sold after 1995, probably), you almost certainly |
| 77 |
have a parallel port that can read back from the printer. If you keep getting |
| 78 |
an error message, you have probably some kind of problem with the connection. |
| 79 |
Check again if all cables are securely attached and the printer is switched |
| 80 |
on. If this still doesn't help, ask someone to find out what is wrong with the |
| 81 |
connection (it might well be something on the software side of your PC). I |
| 82 |
can't do anything about this sort of problem from far away... |
| 83 |
If all goes well, you should see something like: |
| 84 |
|
| 85 |
mschiller5:~ # min12xxw -m 1200W -d /dev/usb/lp0 -s |
| 86 |
printer status: UMFG:MINOLTA-QMS;CMD:NA;MDL:PagePro 1200W;CLS:PRINTER;DES:MINOLTA-QMS PagePro 1200W; |
| 87 |
controller firmware version: 1A04 |
| 88 |
page counter: 3255 pages |
| 89 |
mschiller5:~ # |
| 90 |
|
| 91 |
This means that the driver talks to your PC. |
| 92 |
|
| 93 |
Please do also note that the procedure described above may or may not work on |
| 94 |
other operating systems. If you know how to make things work on your platform, |
| 95 |
feedback would be greatly appreciated. |
| 96 |
|
| 97 |
|
| 98 |
3. I've built min12xxw, how do I get my documents to print? |
| 99 |
|
| 100 |
Now the next question is how to make your applications print. I can't give you |
| 101 |
details on how to do this because details differ from distribution to |
| 102 |
distribution. What I'll give here is a description what happens below the |
| 103 |
surface and some hints where to turn to for help. |
| 104 |
|
| 105 |
We'll start with describing what happens with your print job on a normal Linux |
| 106 |
system when the printer is correctly installed. You application usually will |
| 107 |
produce a description of what is supposed to appear on paper. This description |
| 108 |
is done in a programming language called PostScript. This description is |
| 109 |
forwarded to the printer spooler. It puts all print jobs on the system into a |
| 110 |
queue and sends them to the printer one after the other. On their way there, |
| 111 |
they may need to be processed in order to make the desciption understandable |
| 112 |
for the printer. Clever (and usually expensive) printers understand |
| 113 |
postscript, but unfortunately, the 1[23]xxW series do not. A postscript |
| 114 |
interpreter called ghostscript reads the description and produces a bitmap |
| 115 |
which basically says which points on paper should become black an which should |
| 116 |
be left white. min12xxw takes this bitmap (which is not in a form the printer |
| 117 |
will understand) and convert it to something the printer will grasp. This is |
| 118 |
then sent to the printer which should start printing right away (assuming that |
| 119 |
it is powered up, of course). |
| 120 |
|
| 121 |
To make the printer work on your system, you have to tell the printer spooler |
| 122 |
how to run this postprocessing chain on the data that is sent by your |
| 123 |
applications. If you have a recent Linux distribution, you'll probably run |
| 124 |
CUPS as printer spooler, because it is easier to set up. Your distribution |
| 125 |
probably ships with a package containing CUPS, maybe it was already installed |
| 126 |
automatically. CUPS has the advantage that it reads files which describe how |
| 127 |
to run this postprocessing chain. The only thing you have to do is to download |
| 128 |
this description and make the configuration software of you distribution feed |
| 129 |
it into CUPS. Have a look at www.linuxprinting.org, they distribute these |
| 130 |
descriptions. They are called PPD files. The also have generic instructions on |
| 131 |
how to tell your distribution's configuration program to set up the printer. |
| 132 |
(I can't give specific steps here as this differs from distribution to |
| 133 |
distribution.) Once you have that set up, you should be able to print. Try |
| 134 |
|
| 135 |
echo Hello, world! | lpr |
| 136 |
|
| 137 |
from the command line. This should produce a page containing "Hello, world!" |
| 138 |
in a typewriter like font. If this works, you should also be able to print |
| 139 |
from your applications. |
| 140 |
|
| 141 |
Older systems often have LPRng or even some older lpr installed. Configuration |
| 142 |
is considerably more work there, even if it offers a great deal of |
| 143 |
flexibility. If you use LPRng, you'll probably know how to set it up, so I |
| 144 |
won't give much detail here. All I want to say is that the manual page of |
| 145 |
min12xxw will probably give you enough details to get things going. You can |
| 146 |
access the manual page with: |
| 147 |
|
| 148 |
man min12xxw |
| 149 |
|
| 150 |
This manual page will also give you the neccessary details to print without |
| 151 |
a spooling system for testing purposes, see the example given in the man |
| 152 |
page and tailor it to your situation (adjust printer model, resolution, |
| 153 |
paper size and tray used, and the filenames). |
| 154 |
|
| 155 |
|
| 156 |
4. When I print multiple documents one right after the other, some pages are |
| 157 |
incomplete, blank or missing. What's happening? |
| 158 |
|
| 159 |
This problem is known and I can see no easy fix for it. What happens is the |
| 160 |
following: The PC feeds the printer with print data for a print job. The |
| 161 |
printer takes this data into it's buffer and produces output. At the same |
| 162 |
time, it signals the PC that it is ready for new data. When the PC has the |
| 163 |
data for the next job ready, it starts sending it. However, the people at |
| 164 |
Minolta seem to have decided that the start of each print job sort of resets |
| 165 |
the printer and cancels printing the current page. That is why the previous |
| 166 |
print job might be truncated. In a windoof environment, the print spooler can |
| 167 |
monitor the printer status an decide to wait a little longer to send the data. |
| 168 |
The print spoolers used on Linux are not designed to behave like that, they |
| 169 |
rely on a well-behaved printer which is actually ready for new data when it |
| 170 |
says so. As I don't intend to write a printer spooler specifically for this |
| 171 |
type of printer, I can only suggest two workarounds: |
| 172 |
The first is to wait until the current job is ready before you send the next |
| 173 |
job. The second is to print all of the jobs to files, which you cat into lpr: |
| 174 |
|
| 175 |
cat file1 file2 file3 ... | lpr |
| 176 |
|
| 177 |
This will save you from waiting by making one big print job out of many small |
| 178 |
ones. While this is fine for single user systems, big multi user systems with |
| 179 |
a fair amount of things to be printed will probably not find these suggestions |
| 180 |
particularly useful. Unfortunately, I don't know what to do about this, the |
| 181 |
problem is in the printer protocol, and I can't change it. Maybe one could |
| 182 |
implement a sleeping cycle in the print spooler after each job, but this is |
| 183 |
quite a lot of work and will probably no be included in standard |
| 184 |
distributions. Upgrading your system's software would therefore mean having to |
| 185 |
start modifying the source of the spooler again... |
| 186 |
|
| 187 |
|
| 188 |
5. Graphics printouts are too dark/show 'banding' instead of smoothly varying |
| 189 |
shades of grey. Can't one do this better? |
| 190 |
|
| 191 |
This comes from the fact that ghostscript that is used to render the output, |
| 192 |
producing a black-and-white bitmap, does not know all the peculiarities of |
| 193 |
underlying device, that is our printer in this case. For example, when the |
| 194 |
toner is fixated on the paper (using heat - that is why the sheets of paper |
| 195 |
come out still warm...), it is somewhat smeared out and occupies a somewhat |
| 196 |
larger area than ghostscript's idealized model expects. That is why the |
| 197 |
output appears to be slightly too dark. Also, when working with shades of |
| 198 |
grey on a black and white device, you have to approximate the grey levels by |
| 199 |
effectively reducing the resolution and use many dots, some white, some black |
| 200 |
to represent a grey shade in the reduced resolution (the process is usually |
| 201 |
called dithering). While ghostscript's default dithering settings are quite |
| 202 |
good for a large amount of applications we need to tweak them a little. |
| 203 |
|
| 204 |
If you use CUPS, the maintainer of the PPD files has promised me to add these |
| 205 |
tweaks to the PPD files. They should be available shortly on |
| 206 |
<http://www.linuxprinting.org>. For those of you who use LPRng or something |
| 207 |
similar, here are the details of how to do it per hand: |
| 208 |
|
| 209 |
- You have to prepend the postscript input with a little postscript program |
| 210 |
that does a gamma correction, rendering the images a little brighter. |
| 211 |
This fragment looks as follows: |
| 212 |
|
| 213 |
%! |
| 214 |
/.fixtransfer { |
| 215 |
currentcolortransfer 4 { |
| 216 |
mark exch |
| 217 |
dup type dup /arraytype eq exch /packedarraytype eq or |
| 218 |
1 index xcheck and { /exec load } if |
| 219 |
1.0 /exp load |
| 220 |
] cvx 4 1 roll |
| 221 |
} repeat setcolortransfer |
| 222 |
} bind odef |
| 223 |
.fixtransfer |
| 224 |
/setpagedevice { setpagedevice .fixtransfer } bind odef |
| 225 |
|
| 226 |
Note the line "1.0 /exp load". You'll have to replace the number in this |
| 227 |
line depending on the gamma factor that you want. To be exact, you have to |
| 228 |
substitute the reciprocal of the gamma factor, i.e. for a gamma factor of |
| 229 |
2.0, you have to replace 1.0 by 0.5. These factors a given in the table |
| 230 |
below. |
| 231 |
|
| 232 |
- You also have to call ghostscript with a special option, namely |
| 233 |
-dDITHERPPI=LPI, where LPI is a number given in the table below. This |
| 234 |
option fine-tunes how ghostscript will "reduce" resolution to gain dots to |
| 235 |
simulate grey levels. (LPI is short for lines per inch - this gives you |
| 236 |
an idea how the resolution is being decreased for simulating greyscale...) |
| 237 |
|
| 238 |
- Unfortunately, gamma factor and LPI depend on the resolution and econo mode |
| 239 |
being used or not. The values given below may not be optimal, but seem to be |
| 240 |
good for most practical uses. They were found by much experimentation. |
| 241 |
|
| 242 |
resolution 1200 1200x600 600 300 1200 1200x600 600 300 |
| 243 |
econo mode * * * * |
| 244 |
gamma 1.8 1.6 1.6 1.6 1.2 1.0 1.0 1.0 |
| 245 |
LPI 105 90 75 60 105 90 75 60 |
| 246 |
|
| 247 |
If you find better settings, please let me know. |
| 248 |
|