| 1 |
This is a summary of all my three posts before. Sorry for posting so |
| 2 |
many times but this one provide most complete information to start. |
| 3 |
|
| 4 |
Printer: Laserjet 3015. tested right now works with both USB and |
| 5 |
parallel port (tested using my notebook). This printer can take plain |
| 6 |
text input, that is "cat textfile > /dev/lp0" can get the text correctly |
| 7 |
printed using my notebook. |
| 8 |
|
| 9 |
Cable: the cable is tested (right now) to be working fine with SuSE 10.1 |
| 10 |
on my notebook. SuSE actually can automatically detect the printer model |
| 11 |
and find proper drive for it, also to print photos. Thus I assume the |
| 12 |
cable is bidirectional. |
| 13 |
|
| 14 |
Print server: Ultrasparc U5. Working here for two years without any |
| 15 |
problem. I cannot make the above printer and cable together work with |
| 16 |
this print server. |
| 17 |
|
| 18 |
Dmesg shows the parallel port is discovered, running in ECP mode, here |
| 19 |
are the related dmesg: |
| 20 |
|
| 21 |
sappho ~ # dmesg | grep -i parp |
| 22 |
parport0: PC-style at 0x1fff13043bc (0x1fff13047bc), irq 8687936, dma 0 |
| 23 |
[PCSPP,TRISTATE,COMPAT,ECP,DMA] |
| 24 |
lp0: using parport0 (interrupt-driven). |
| 25 |
Partition check: |
| 26 |
parport0: FIFO is stuck |
| 27 |
parport0: BUSY timeout (1) in compat_write_block_pio |
| 28 |
parport0: FIFO is stuck |
| 29 |
parport0: BUSY timeout (1) in compat_write_block_pio |
| 30 |
parport0: FIFO is stuck |
| 31 |
parport0: BUSY timeout (1) in compat_write_block_pio |
| 32 |
parport0: FIFO is stuck |
| 33 |
parport0: BUSY timeout (1) in compat_write_block_pio |
| 34 |
[repeat 242 times] |
| 35 |
(then repeat this message forever, fill up dmesg) |
| 36 |
|
| 37 |
Current behavior: |
| 38 |
|
| 39 |
# cat plaintext > /dev/lp0 |
| 40 |
This command hangs there forever. |
| 41 |
|
| 42 |
I think I don't need to bother look for cups debug message because |
| 43 |
basically the communication between the printer and the server cannot be |
| 44 |
established. Actually CUPS behave similiarly, a print job is sent but |
| 45 |
hangs there forever. |
| 46 |
|
| 47 |
Looks pretty much like the parallel port is not properly configured. A |
| 48 |
google with this error message doesn't produce helpful message for me |
| 49 |
yet. the message "irq 8687936, dma 0" doesn't make sense, I don't know |
| 50 |
if there exist "DMA 0", further I don't know if irq can be such big |
| 51 |
number on sparcs. I am thinking of specifying detailed I/O address, irq |
| 52 |
number (actually I wish to try none first) and DMA (I wish to try none |
| 53 |
first) as parameter to my parport-staticlly linked kernel, but I don't |
| 54 |
know what to specify as I/O address yet, I don't know if 0x1fff13043bc |
| 55 |
is an acceptable address, I'll try it when tonight I have the chance to |
| 56 |
reboot the server (cannot reboot now, there are still other people using |
| 57 |
that server.) |
| 58 |
|
| 59 |
Help very much welcomed and appreciated. Thanks in advance. |
| 60 |
|
| 61 |
-- |
| 62 |
gentoo-server@g.o mailing list |
Archives