Printing (well anything) using lpd...

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Printing (well anything) using lpd...

Bryan Brake
*tried sending this to the "newbies" list, but was kicked back*

I have been hampered with this for a few years now, and at most times,
it was easier to copy the file to a Windows box and print.  But I'm
tired of having to do this, and have begun researching how to print to
a printer on the network.  I recently bought a Brother 9840CDW, which
supports lpd and postscript.  It also allows for FTP of files to queue
among other things.  It's probably more printer (scanner, fax, copier)
than I need, but I'm tired of HP printers and the toner issues they
have.  It is a really nice printer in Windows, and the scanner is most
excellent and fast.  And according to the LInux foundation site
(http://www.linuxfoundation.org/collaborate/workgroups/openprinting)
it works perfectly.  Of course, I have to take this with a grain of
salt, because of Linux's willingness to add proprietary drivers,
firmware, etc.

I am running a -current built with a vanilla GENERIC.MP (dmesg and
printcap below).
 It's valid as of the 24th of January 2011.  I have googled several
sites, and found a site that was able to help me get a running config.
 This meant I was able to successfully send something over my network
to the printer.  I've sent a copy of the /etc/printcap to the printer,
and while it does print the first line of the text correctly, the next
line begins where the first line ends, but one line down


example:


blah blah blah
                        blah blah blah


the interesting thing is, the burst page, which prints after the job
completes, prints correctly, with lines printing correctly.  Truly
frustrating.  And in a moment of ignorance, I wasted about 50 pages of
paper when I sent a PDF to the printer.  Tons of garbage on the the
page, sometimes on both sides.  I was able to purge the queue with
'lpc' but ended up powercycling the printer to kill the printing.

I've been reading the printcap man page, lpd, lpr, and the following sites:

http://www.linuxfoundation.org/collaborate/workgroups/openprinting
http://www.wonkity.com/~wblock/docs/html/lpdprinting.html
http://www.digitalissues.co.uk/html/os/unix/bsd.html (this helped me
get connected to my networked printer)
http://onlamp.com/pub/a/bsd/2004/07/08/FreeBSD_Basics.html?page=1
(Darrin Chandler's blog directed me here when he was having issues)

I've been to other sites and forums where people are using samba to
print.  But I am having enough trouble with a simple text file to
setup samba just to print.  Has anyone been able to print regular
text, pdfs, and possibly images on a printer? I tried using 'pdf2ps',
but this only cut down the amount of wasted paper with gibberish on it
by 25 or so pages.

I've got the network portion down, but I think that I don't know
enough about how filters work.  Do people create their own, or are
there any 'recipes' out there that I can modify to work with my
printer?

If you have a site that I should be reading, or a man page that I
missed, please let me know, and I'll study it. I do have ghostscript
installed, and I tried using apsfilter, but it didn't appear to work.
I configured everything, using the GS Driver option #2, but everything
still printed the same gibberish and text still printed like the
above.

Regards,
Bryan

/etc/printcap:
#       $OpenBSD: printcap,v 1.4 2003/03/28 21:32:30 jmc Exp $

#lp|local line printer:\
#       :lp=/dev/lp:sd=/var/spool/output:lf=/var/log/lpd-errs:

lp|9840CDN:\
        :sd=/var/spool/output/9840CDN:\
        :lp=:\
        :rm=9840CDN:\
        :rp=9840CDN:

'9840CDN' is the printer, I put it wrong in both my printcap, and in
/etc/hosts.  The printer is the *9840CDW*

dmesg:

OpenBSD 4.9-beta (GENERIC.MP) #34: Mon Jan 24 12:26:44 CST 2011
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3707031552 (3535MB)
avail mem = 3594342400 (3427MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf6530 (57 entries)
bios0: vendor Dell Inc. version "A24" date 08/19/2010
bios0: Dell Inc. Latitude E6500
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET DMAR APIC ASF! MCFG SLIC SSDT
acpi0: wakeup devices PCI0(S4) PCIE(S4) USB1(S0) USB2(S0) USB3(S0)
USB4(S0) USB5(S0) USB6(
S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S4) RP02(S4) RP03(S4) RP04(S3)
RP05(S3) RP06(S5) LID_(
S3) PBTN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU P8800 @ 2.66GHz, 2660.46 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,AC
PI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,
SSE4.1,XSAVE,NXE,LONG
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: apic clock running at 266MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P8800 @ 2.66GHz, 2660.00 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,AC
PI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,
SSE4.1,XSAVE,NXE,LONG
cpu1: 3MB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiprt0 at acpi0: bus 3 (PCIE)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 11 (RP01)
acpiprt3 at acpi0: bus -1 (RP02)
acpiprt4 at acpi0: bus 12 (RP03)
acpiprt5 at acpi0: bus 13 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus 0 (PCI0)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpitz0 at acpi0: critical temperature 107 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model "DELL KY26603" serial 5171 type LION oem "Sanyo"
acpibat1 at acpi0: BAT1 not present
acpivideo0 at acpi0: VID_
acpivideo1 at acpi0: VID_
acpivout0 at acpivideo1: CRT_
acpivout1 at acpivideo1: LCD_
acpivout2 at acpivideo1: DP__
acpivout3 at acpivideo1: DP2_
acpivout4 at acpivideo1: DVI_
acpivout5 at acpivideo1: DVI2
acpivideo2 at acpi0: VID2
cpu0: Enhanced SpeedStep 2660 MHz: speeds: 2668, 2667, 2134, 1600, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xe0000000, size 0x10000000
inteldrm0 at vga1: apic 2 int 16 (irq 11)
drm0 at inteldrm0
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: apic 2
int 22 (irq 10), add
ress 00:26:b9:c5:4b:48
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2
int 20 (irq 7)
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2
int 21 (irq 4)
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2
int 22 (irq 10)
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2
int 22 (irq 10)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03:
apic 2 int 21 (irq 4)
azalia0: codecs: IDT 92HD71B7, Intel/0x2802, using IDT 92HD71B7
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: apic 2
int 16 (irq 0)
pci1 at ppb0 bus 11
ppb1 at pci0 dev 28 function 2 "Intel 82801I PCIE" rev 0x03: apic 2
int 18 (irq 0)
pci2 at ppb1 bus 12
ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03: apic 2
int 19 (irq 0)
pci3 at ppb2 bus 13
uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x03: apic 2
int 20 (irq 7)
uhci4 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x03: apic 2
int 21 (irq 4)
uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x03: apic 2
int 22 (irq 10)
ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x03: apic 2
int 20 (irq 7)
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x93
pci4 at ppb3 bus 3
cbb0 at pci4 dev 1 function 0 "Ricoh 5C476 CardBus" rev 0xba: apic 2
int 19 (irq 10)
"Ricoh 5C832 Firewire" rev 0x04 at pci4 dev 1 function 1 not configured
sdhc0 at pci4 dev 1 function 2 "Ricoh 5C822 SD/MMC" rev 0x21: apic 2
int 18 (irq 11)
sdmmc0 at sdhc0
"Ricoh 5C843 MMC" rev 0x11 at pci4 dev 1 function 3 not configured
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 4 device 0 cacheline 0x10, lattimer 0x20
pcmcia0 at cardslot0
pcib0 at pci0 dev 31 function 0 "Intel 82801IEM LPC" rev 0x03
ahci0 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x03: apic 2
int 19 (irq 10), AHCI 1.2
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: <ATA, WDC WD2500BEVS-2, 01.0> SCSI3 0/direct fixed
sd0: 238475MB, 512 bytes/sec, 488397168 sec total
cd0 at scsibus0 targ 1 lun 0: <TSSTcorp, DVD+-RW TS-U633A, DW10> ATAPI
5/cdrom removable
ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x03: apic
2 int 17 (irq 3)
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL5 SO-DIMM
spdmem1 at iic0 addr 0x52: 2GB DDR2 SDRAM non-parity PC2-6400CL5 SO-DIMM
usb2 at uhci0: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci1: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci2: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb5 at uhci3: USB revision 1.0
uhub5 at usb5 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb6 at uhci4: USB revision 1.0
uhub6 at usb6 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb7 at uhci5: USB revision 1.0
uhub7 at usb7 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
mtrr: Pentium Pro MTRR support
ugen0 at uhub4 port 1 "Broadcom Corp 5880" rev 1.10/1.01 addr 2
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
root on sd0a swap on sd0b dump on sd0b
rum0 at uhub1 port 4 "Ralink Technology RT2573" rev 2.00/0.01 addr 2
rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:0e:3b:1e:f0:14
uhidev0 at uhub5 port 2 configuration 1 interface 0 "Primax Kensington
Eagle Trackball" re
v 2.00/6.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
wsmouse1 detached
ums0 detached
uhidev0 detached
uhidev0 at uhub5 port 1 configuration 1 interface 0 "Primax Kensington
Eagle Trackball" re
v 2.00/6.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

patrick keshishian
I'm not sure your printer support Postscript. It supports PCL-6 and
BR-Script 3 (whatever the hell the latter may be)

Try using gs to convert your postscript files to pcl3 and feeding those to
lpr.

$ gs -dNOPAUSE -sDEVICE=pcl3 -sOutputFile=/tmp/junk%d.pcl3 letter.ps
$ lpr /tmp/junk*.pcl3

--patrick


On Sat, Jan 29, 2011 at 8:48 PM, Bryan <[hidden email]> wrote:

> *tried sending this to the "newbies" list, but was kicked back*
>
> I have been hampered with this for a few years now, and at most times,
> it was easier to copy the file to a Windows box and print.  But I'm
> tired of having to do this, and have begun researching how to print to
> a printer on the network.  I recently bought a Brother 9840CDW, which
> supports lpd and postscript.  It also allows for FTP of files to queue
> among other things.  It's probably more printer (scanner, fax, copier)
> than I need, but I'm tired of HP printers and the toner issues they
> have.  It is a really nice printer in Windows, and the scanner is most
> excellent and fast.  And according to the LInux foundation site
> (http://www.linuxfoundation.org/collaborate/workgroups/openprinting)
> it works perfectly.  Of course, I have to take this with a grain of
> salt, because of Linux's willingness to add proprietary drivers,
> firmware, etc.
>
> I am running a -current built with a vanilla GENERIC.MP (dmesg and
> printcap below).
>  It's valid as of the 24th of January 2011.  I have googled several
> sites, and found a site that was able to help me get a running config.
>  This meant I was able to successfully send something over my network
> to the printer.  I've sent a copy of the /etc/printcap to the printer,
> and while it does print the first line of the text correctly, the next
> line begins where the first line ends, but one line down
>
>
> example:
>
>
> blah blah blah
>                        blah blah blah
>
>
> the interesting thing is, the burst page, which prints after the job
> completes, prints correctly, with lines printing correctly.  Truly
> frustrating.  And in a moment of ignorance, I wasted about 50 pages of
> paper when I sent a PDF to the printer.  Tons of garbage on the the
> page, sometimes on both sides.  I was able to purge the queue with
> 'lpc' but ended up powercycling the printer to kill the printing.
>
> I've been reading the printcap man page, lpd, lpr, and the following sites:
>
> http://www.linuxfoundation.org/collaborate/workgroups/openprinting
> http://www.wonkity.com/~wblock/docs/html/lpdprinting.html
> http://www.digitalissues.co.uk/html/os/unix/bsd.html (this helped me
> get connected to my networked printer)
> http://onlamp.com/pub/a/bsd/2004/07/08/FreeBSD_Basics.html?page=1
> (Darrin Chandler's blog directed me here when he was having issues)
>
> I've been to other sites and forums where people are using samba to
> print.  But I am having enough trouble with a simple text file to
> setup samba just to print.  Has anyone been able to print regular
> text, pdfs, and possibly images on a printer? I tried using 'pdf2ps',
> but this only cut down the amount of wasted paper with gibberish on it
> by 25 or so pages.
>
> I've got the network portion down, but I think that I don't know
> enough about how filters work.  Do people create their own, or are
> there any 'recipes' out there that I can modify to work with my
> printer?
>
> If you have a site that I should be reading, or a man page that I
> missed, please let me know, and I'll study it. I do have ghostscript
> installed, and I tried using apsfilter, but it didn't appear to work.
> I configured everything, using the GS Driver option #2, but everything
> still printed the same gibberish and text still printed like the
> above.
>
> Regards,
> Bryan
>
> /etc/printcap:
> #       $OpenBSD: printcap,v 1.4 2003/03/28 21:32:30 jmc Exp $
>
> #lp|local line printer:\
> #       :lp=/dev/lp:sd=/var/spool/output:lf=/var/log/lpd-errs:
>
> lp|9840CDN:\
>        :sd=/var/spool/output/9840CDN:\
>        :lp=:\
>        :rm=9840CDN:\
>        :rp=9840CDN:
>
> '9840CDN' is the printer, I put it wrong in both my printcap, and in
> /etc/hosts.  The printer is the *9840CDW*
>
> dmesg:
>
> OpenBSD 4.9-beta (GENERIC.MP) #34: Mon Jan 24 12:26:44 CST 2011
>    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 3707031552 (3535MB)
> avail mem = 3594342400 (3427MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf6530 (57 entries)
> bios0: vendor Dell Inc. version "A24" date 08/19/2010
> bios0: Dell Inc. Latitude E6500
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP HPET DMAR APIC ASF! MCFG SLIC SSDT
> acpi0: wakeup devices PCI0(S4) PCIE(S4) USB1(S0) USB2(S0) USB3(S0)
> USB4(S0) USB5(S0) USB6(
> S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S4) RP02(S4) RP03(S4) RP04(S3)
> RP05(S3) RP06(S5) LID_(
> S3) PBTN(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 Duo CPU P8800 @ 2.66GHz, 2660.46 MHz
> cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,AC
>
PI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX
16,xTPR,PDCM,
> SSE4.1,XSAVE,NXE,LONG
> cpu0: 3MB 64b/line 8-way L2 cache
> cpu0: apic clock running at 266MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Duo CPU P8800 @ 2.66GHz, 2660.00 MHz
> cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,AC
>
PI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX
16,xTPR,PDCM,

> SSE4.1,XSAVE,NXE,LONG
> cpu1: 3MB 64b/line 8-way L2 cache
> ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 2
> acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
> acpiprt0 at acpi0: bus 3 (PCIE)
> acpiprt1 at acpi0: bus -1 (AGP_)
> acpiprt2 at acpi0: bus 11 (RP01)
> acpiprt3 at acpi0: bus -1 (RP02)
> acpiprt4 at acpi0: bus 12 (RP03)
> acpiprt5 at acpi0: bus 13 (RP04)
> acpiprt6 at acpi0: bus -1 (RP05)
> acpiprt7 at acpi0: bus -1 (RP06)
> acpiprt8 at acpi0: bus 0 (PCI0)
> acpiec0 at acpi0
> acpicpu0 at acpi0: C3, C2, C1, PSS
> acpicpu1 at acpi0: C3, C2, C1, PSS
> acpitz0 at acpi0: critical temperature 107 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: PBTN
> acpibtn2 at acpi0: SBTN
> acpiac0 at acpi0: AC unit offline
> acpibat0 at acpi0: BAT0 model "DELL KY26603" serial 5171 type LION oem
"Sanyo"

> acpibat1 at acpi0: BAT1 not present
> acpivideo0 at acpi0: VID_
> acpivideo1 at acpi0: VID_
> acpivout0 at acpivideo1: CRT_
> acpivout1 at acpivideo1: LCD_
> acpivout2 at acpivideo1: DP__
> acpivout3 at acpivideo1: DP2_
> acpivout4 at acpivideo1: DVI_
> acpivout5 at acpivideo1: DVI2
> acpivideo2 at acpi0: VID2
> cpu0: Enhanced SpeedStep 2660 MHz: speeds: 2668, 2667, 2134, 1600, 800 MHz
> pci0 at mainbus0 bus 0
> pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
> vga1 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> intagp0 at vga1
> agp0 at intagp0: aperture at 0xe0000000, size 0x10000000
> inteldrm0 at vga1: apic 2 int 16 (irq 11)
> drm0 at inteldrm0
> "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
> em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: apic 2
> int 22 (irq 10), add
> ress 00:26:b9:c5:4b:48
> uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2
> int 20 (irq 7)
> uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2
> int 21 (irq 4)
> uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2
> int 22 (irq 10)
> ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2
> int 22 (irq 10)
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03:
> apic 2 int 21 (irq 4)
> azalia0: codecs: IDT 92HD71B7, Intel/0x2802, using IDT 92HD71B7
> audio0 at azalia0
> ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: apic 2
> int 16 (irq 0)
> pci1 at ppb0 bus 11
> ppb1 at pci0 dev 28 function 2 "Intel 82801I PCIE" rev 0x03: apic 2
> int 18 (irq 0)
> pci2 at ppb1 bus 12
> ppb2 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03: apic 2
> int 19 (irq 0)
> pci3 at ppb2 bus 13
> uhci3 at pci0 dev 29 function 0 "Intel 82801I USB" rev 0x03: apic 2
> int 20 (irq 7)
> uhci4 at pci0 dev 29 function 1 "Intel 82801I USB" rev 0x03: apic 2
> int 21 (irq 4)
> uhci5 at pci0 dev 29 function 2 "Intel 82801I USB" rev 0x03: apic 2
> int 22 (irq 10)
> ehci1 at pci0 dev 29 function 7 "Intel 82801I USB" rev 0x03: apic 2
> int 20 (irq 7)
> usb1 at ehci1: USB revision 2.0
> uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x93
> pci4 at ppb3 bus 3
> cbb0 at pci4 dev 1 function 0 "Ricoh 5C476 CardBus" rev 0xba: apic 2
> int 19 (irq 10)
> "Ricoh 5C832 Firewire" rev 0x04 at pci4 dev 1 function 1 not configured
> sdhc0 at pci4 dev 1 function 2 "Ricoh 5C822 SD/MMC" rev 0x21: apic 2
> int 18 (irq 11)
> sdmmc0 at sdhc0
> "Ricoh 5C843 MMC" rev 0x11 at pci4 dev 1 function 3 not configured
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 4 device 0 cacheline 0x10, lattimer 0x20
> pcmcia0 at cardslot0
> pcib0 at pci0 dev 31 function 0 "Intel 82801IEM LPC" rev 0x03
> ahci0 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x03: apic 2
> int 19 (irq 10), AHCI 1.2
> scsibus0 at ahci0: 32 targets
> sd0 at scsibus0 targ 0 lun 0: <ATA, WDC WD2500BEVS-2, 01.0> SCSI3 0/direct
fixed

> sd0: 238475MB, 512 bytes/sec, 488397168 sec total
> cd0 at scsibus0 targ 1 lun 0: <TSSTcorp, DVD+-RW TS-U633A, DW10> ATAPI
> 5/cdrom removable
> ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x03: apic
> 2 int 17 (irq 3)
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL5 SO-DIMM
> spdmem1 at iic0 addr 0x52: 2GB DDR2 SDRAM non-parity PC2-6400CL5 SO-DIMM
> usb2 at uhci0: USB revision 1.0
> uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb3 at uhci1: USB revision 1.0
> uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb4 at uhci2: USB revision 1.0
> uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb5 at uhci3: USB revision 1.0
> uhub5 at usb5 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb6 at uhci4: USB revision 1.0
> uhub6 at usb6 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> usb7 at uhci5: USB revision 1.0
> uhub7 at usb7 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> mtrr: Pentium Pro MTRR support
> ugen0 at uhub4 port 1 "Broadcom Corp 5880" rev 1.10/1.01 addr 2
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> root on sd0a swap on sd0b dump on sd0b
> rum0 at uhub1 port 4 "Ralink Technology RT2573" rev 2.00/0.01 addr 2
> rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528, address 00:0e:3b:1e:f0:14
> uhidev0 at uhub5 port 2 configuration 1 interface 0 "Primax Kensington
> Eagle Trackball" re
> v 2.00/6.00 addr 2
> uhidev0: iclass 3/1
> ums0 at uhidev0: 3 buttons, Z dir
> wsmouse1 at ums0 mux 0
> wsmouse1 detached
> ums0 detached
> uhidev0 detached
> uhidev0 at uhub5 port 1 configuration 1 interface 0 "Primax Kensington
> Eagle Trackball" re
> v 2.00/6.00 addr 2
> uhidev0: iclass 3/1
> ums0 at uhidev0: 3 buttons, Z dir
> wsmouse1 at ums0 mux 0

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

David Hoskin-3
In reply to this post by Bryan Brake
To test, try manually converting whatever you want to print with
ghostscript, and then printing the result.

I found that the filter script included with ghostscript didn't work,
but with some hacking I got it to work.  It does some horrible shell
hacks to "autoconfig", and if you just edit in the correct gs filter
for your device it should work fine.

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Bryan Brake
In reply to this post by patrick keshishian
On Sun, Jan 30, 2011 at 01:17, patrick keshishian <[hidden email]> wrote:
> I'm not sure your printer support Postscript. It supports PCL-6 and
> BR-Script 3 (whatever the hell the latter may be)
>
> Try using gs to convert your postscript files to pcl3 and feeding those to lpr.
>
> $ gs -dNOPAUSE -sDEVICE=pcl3 -sOutputFile=/tmp/junk%d.pcl3 letter.ps
> $ lpr /tmp/junk*.pcl3
>
> --patrick

It supports Postscript, and even has it's own lpd running so that you
can FTP files to it to print.

Huh... I had never actually tried the upload via FTP, but when I did
that, the file didn't print correctly either.  With the way my
printcap is setup, I'm not actually doing anything to the files before
they are sent to the printer.  So the Printer's filters aren't working
either?  I think I may need to check the printer as well as my laptop
config...

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Christian Weisgerber
In reply to this post by patrick keshishian
patrick keshishian <[hidden email]> wrote:

> I'm not sure your printer support Postscript. It supports PCL-6 and
> BR-Script 3 (whatever the hell the latter may be)

It's PostScript 3, but Brother didn't buy the firmware from Adobe
and used a different implementation.

--
Christian "naddy" Weisgerber                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Bryan Brake
On Sun, Jan 30, 2011 at 10:10, Christian Weisgerber <[hidden email]>
wrote:

> patrick keshishian <[hidden email]> wrote:
>
>> I'm not sure your printer support Postscript. It supports PCL-6 and
>> BR-Script 3 (whatever the hell the latter may be)
>
> It's PostScript 3, but Brother didn't buy the firmware from Adobe
> and used a different implementation.
>
> --
> Christian "naddy" Weisgerber B  B  B  B  B  B  B  B  B  B  B  B
B [hidden email]
>
>

So I'm going to have to mess with the filters to get .ps files to
print with the implementation of BR Script?  Guess it won't kill me to
figure that out...

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Christian Weisgerber
In reply to this post by Bryan Brake
Bryan <[hidden email]> wrote:

> I recently bought a Brother 9840CDW, which supports lpd and postscript.

>  It's valid as of the 24th of January 2011.  I have googled several
> sites, and found a site that was able to help me get a running config.
>  This meant I was able to successfully send something over my network
> to the printer.

There's an example entry "remote line printer" in /etc/printcap.
All you need to do is uncomment it and put in the DNS name of the
printer.

> I've sent a copy of the /etc/printcap to the printer,
> and while it does print the first line of the text correctly, the next
> line begins where the first line ends, but one line down

You say it's a PostScript printer but you didn't send it PostScript,
so what did you expect?

Actually, your printer happily accepts plain text.  However, Unix
terminates lines by a simple ASCII line feed character (0x0A, '\n').
Printers interpret this literally as a line feed and expect an
additional carriage return character (0x0D, '\r') to also start
printing from the beginning of the line.  You could use for instance
this to add the carriage returns:

$ perl -lpe '$_.="\r"' file | lpr

Or you can use a2ps or mpage from ports to turn plain text into
PostScript.

> And in a moment of ignorance, I wasted about 50 pages of paper
> when I sent a PDF to the printer.

You say it's a PostScript printer but you didn't send it PostScript,
so what did you expect?

Grab xpdf from ports to view and print the PDF file.  xpdf will
convert PDF to PostScript for printing.

> I've got the network portion down, but I think that I don't know
> enough about how filters work.  Do people create their own, or are
> there any 'recipes' out there that I can modify to work with my
> printer?

There are two approaches here.

(1) You take care to only send PostScript files to the printer.
    This isn't much of an inconvenience, since any X11 program with
    a print button will likely generate PostScript.

(2) You install something like apsfilter or magicfilter from ports
    to act as an input filter that will try to recognize the type
    of a file and automatically convert it to PostScript before
    passing it on to the printer.

Personally I find (1) to be sufficient and (2) not worth the hassle,
but your milage may vary.

--
Christian "naddy" Weisgerber                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Ted Unangst-2
In reply to this post by Bryan Brake
On Sat, Jan 29, 2011 at 11:48 PM, Bryan <[hidden email]> wrote:

> I have been hampered with this for a few years now, and at most times,
> it was easier to copy the file to a Windows box and print.  But I'm
> tired of having to do this, and have begun researching how to print to
> a printer on the network.  I recently bought a Brother 9840CDW, which
> supports lpd and postscript.  It also allows for FTP of files to queue
> among other things.  It's probably more printer (scanner, fax, copier)
> than I need, but I'm tired of HP printers and the toner issues they
> have.  It is a really nice printer in Windows, and the scanner is most
> excellent and fast.  And according to the LInux foundation site
> (http://www.linuxfoundation.org/collaborate/workgroups/openprinting)
> it works perfectly.  Of course, I have to take this with a grain of
> salt, because of Linux's willingness to add proprietary drivers,
> firmware, etc.

While I think it's possible to print using lpd, and people have done
it, I found it to be about 10x easier to install cups and use that.

You go to localhost:631, type in the printer's name, upload a ppd file
downloaded from linuxprinting, and done.

You can make lpd and postscript work if you know how they work, but
figuring things out if you don't can take a long time.

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Bryan Brake
In reply to this post by Christian Weisgerber
On Sun, Jan 30, 2011 at 10:47, Christian Weisgerber <[hidden email]>
wrote:

> Bryan <[hidden email]> wrote:
>
>> I recently bought a Brother 9840CDW, which supports lpd and postscript.
>
>> B It's valid as of the 24th of January 2011. B I have googled several
>> sites, and found a site that was able to help me get a running config.
>> B This meant I was able to successfully send something over my network
>> to the printer.
>
> There's an example entry "remote line printer" in /etc/printcap.
> All you need to do is uncomment it and put in the DNS name of the
> printer.
>
>> I've sent a copy of the /etc/printcap to the printer,
>> and while it does print the first line of the text correctly, the next
>> line begins where the first line ends, but one line down
>
> You say it's a PostScript printer but you didn't send it PostScript,
> so what did you expect?
>

I did convert a pdf to ps using 'pdf2ps', but it still printed
gibberish.  I installed xpdf, and I see that now there is a 'pdftops'

> Actually, your printer happily accepts plain text. B However, Unix
> terminates lines by a simple ASCII line feed character (0x0A, '\n').
> Printers interpret this literally as a line feed and expect an
> additional carriage return character (0x0D, '\r') to also start
> printing from the beginning of the line. B You could use for instance
> this to add the carriage returns:
>
> $ perl -lpe '$_.="\r"' file | lpr
>

I had an example text file with the following output in it...



!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdef
"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefg
#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefgh
$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghi
%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghij


with your bit of perl, it prints correctly.  Without it, it prints
with the output similiar to below.


> Or you can use a2ps or mpage from ports to turn plain text into
> PostScript.
>
>> And in a moment of ignorance, I wasted about 50 pages of paper
>> when I sent a PDF to the printer.
>
> You say it's a PostScript printer but you didn't send it PostScript,
> so what did you expect?
>
> Grab xpdf from ports to view and print the PDF file. B xpdf will
> convert PDF to PostScript for printing.
>

Yea, that failed too...  here is a rough example of what it looks like:

%!PS-Adobe-3.0
                          % Produced by xpdf/pdftops 3.02

         %%Creator: Qt 3.3.8

and i power cycled the printer before I lost another 9 or ten pages.
I created the pdf in kword, and it has one line that says "This is a
test to print."  Renders just fine in xpdf and zathura, but the
printer prints the above.  This is similiar to how the text file I
sent last night looks like.

> There are two approaches here.
>
> (1) You take care to only send PostScript files to the printer.
> B  B This isn't much of an inconvenience, since any X11 program with
> B  B a print button will likely generate PostScript.
>
> (2) You install something like apsfilter or magicfilter from ports
> B  B to act as an input filter that will try to recognize the type
> B  B of a file and automatically convert it to PostScript before
> B  B passing it on to the printer.
>
> Personally I find (1) to be sufficient and (2) not worth the hassle,
> but your milage may vary.

If xpdf didn't work, I doubt any program with a 'print' button is
going to "just work".

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

j4nKy
In reply to this post by Ted Unangst-2
On Sun, Jan 30, 2011 at 12:57:20PM -0500, Ted Unangst wrote:

> On Sat, Jan 29, 2011 at 11:48 PM, Bryan <[hidden email]> wrote:
> > I have been hampered with this for a few years now, and at most times,
> > it was easier to copy the file to a Windows box and print.  But I'm
> > tired of having to do this, and have begun researching how to print to
> > a printer on the network.  I recently bought a Brother 9840CDW, which
> > supports lpd and postscript.  It also allows for FTP of files to queue
> > among other things.  It's probably more printer (scanner, fax, copier)
> > than I need, but I'm tired of HP printers and the toner issues they
> > have.  It is a really nice printer in Windows, and the scanner is most
> > excellent and fast.  And according to the LInux foundation site
> > (http://www.linuxfoundation.org/collaborate/workgroups/openprinting)
> > it works perfectly.  Of course, I have to take this with a grain of
> > salt, because of Linux's willingness to add proprietary drivers,
> > firmware, etc.
>
> While I think it's possible to print using lpd, and people have done
> it, I found it to be about 10x easier to install cups and use that.

cups may be a little eaier to set up, but when I used it a lot, it was
an endless source of headaches to keep running.

> You go to localhost:631, type in the printer's name, upload a ppd file
> downloaded from linuxprinting, and done.

careful.  those downloaded ppds may expect a different configuration
of software packages than what's in OpenBSD's packages.  ppds and the
tools to create them are provided in the OpenBSD packages collection.

> You can make lpd and postscript work if you know how they work, but
> figuring things out if you don't can take a long time.

foomatic is pretty easy to set up.  basically any printer that is
supported by any kind of "free" software will work.  check out
openprinting.org's printer database.  (the foomatic developers
are also responsible for openprinting.org.) it'll tell you what you
need to print with your printer.  then follow the directions (i.e.
basically cut-n-paste) in /usr/local/share/doc/pkg-readmes/foomatic-*.

I've used lpd/foomatic for epson and hp printers (gutenprint and
hpijs/hplip drivers).  often people claim they only work with cups,
but this is simply not true.

fwiw, cups uses foomatic internally.  that's how it supports all those
printers.

--
[hidden email]
SDF Public Access UNIX System - http://sdf.lonestar.org

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

patrick keshishian
In reply to this post by Bryan Brake
On Sun, Jan 30, 2011 at 7:30 AM, Bryan <[hidden email]> wrote:
> On Sun, Jan 30, 2011 at 01:17, patrick keshishian <[hidden email]>
wrote:
>> I'm not sure your printer support Postscript. It supports PCL-6 and
>> BR-Script 3 (whatever the hell the latter may be)
>>
>> Try using gs to convert your postscript files to pcl3 and feeding those to
lpr.
>>
>> $ gs -dNOPAUSE -sDEVICE=pcl3 -sOutputFile=/tmp/junk%d.pcl3 letter.ps
>> $ lpr /tmp/junk*.pcl3
>>
>> --patrick
>
> It supports Postscript, and even has it's own lpd running so that you
> can FTP files to it to print.

You keep saying and thinking that it supports post script. It does
not. Otherwise feeding it a postscript file would print the document,
not the postscript text/source.

I have a brother printer at home. It does not support postscript, only
PCL-3. I print using lpd in base (no need for disgusting software such
as CUPS).

I have a HP printer at the office that _does_ support postscript and
when I feed it postscript documents they print as expected.

Have fun playing with filters and configurations.
--patrick



>
> Huh... I had never actually tried the upload via FTP, but when I did
> that, the file didn't print correctly either.  With the way my
> printcap is setup, I'm not actually doing anything to the files before
> they are sent to the printer.  So the Printer's filters aren't working
> either?  I think I may need to check the printer as well as my laptop
> config...

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Dennis den Brok-2
patrick keshishian <[hidden email]> schrieb:
> You keep saying and thinking that it supports post script. It does
> not. Otherwise feeding it a postscript file would print the document,
> not the postscript text/source.

This may actually depend on the configuration. For instance, a
Kyocera Mita FS1030-D, without "fo" in its printcap(5) entry,
produces output similar to the original poster's printer. (This
under NetBSD, though.)

--
Dennis den Brok

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Sean Kamath
In reply to this post by patrick keshishian
On Jan 30, 2011, at 12:06 PM, patrick keshishian wrote:
>> It supports Postscript, and even has it's own lpd running so that you
>> can FTP files to it to print.
>
> You keep saying and thinking that it supports post script. It does
> not. Otherwise feeding it a postscript file would print the document,
> not the postscript text/source.

A really minor nit: The printer *may* support PostScript, but only in a
specific fashion.

For example, many printers from the mid-90's only recognized the %!
immediately preceded by a ^D or a new connection (any data send between the
two (i.e., a ^D followed by a NL then a !%, or a new connection with a control
character sent before the %!, would switch it to PCL).  Likewise, some
printers default to a PCL queue with LDP unless you explicitly name the queue
you're printing to "ps" or "postscript".

Debugging this crap is a pain in the ass, but not impossible.  If you want to
check your printers to confirm it prints postscript, send it these two lines:

%!
newpath clippath stroke showpage

These four commands were the smallest PostScript I could figure out to send to
a printer to print something without burning up tons of toner.  It should
produce a small line all the way around the page.

You can send that to the printer with FTP.  If it works as expected, then your
printer supports PostScript.  If it doesn't. . . Well, maybe you need to read
the docs on your printer to figure out how to send it PostScript.

Also, most printers will have a config page you can print out from the front
panel.  One thing that should show on the Config Page is the PostScript
version.  That's another way to tell if your printer supports PostScript.

Your printer might also accept connections on port 9100 -- you can literally
telnet to that port and type the above commands.

I don't know if OpenBSD's "lpr" command can connect to a remote server
directly, as Sun's can.  You can telnet to the LPD port and try and fake it,
but you have to know the magic NULL-prefixed commands.

Your best bet is to scour the documentation for your printer.

Good luck.

Sean

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Bryan Brake
On Sun, Jan 30, 2011 at 15:51, Sean Kamath <[hidden email]> wrote:

> On Jan 30, 2011, at 12:06 PM, patrick keshishian wrote:
>>> It supports Postscript, and even has it's own lpd running so that you
>>> can FTP files to it to print.
>>
>> You keep saying and thinking that it supports post script. It does
>> not. Otherwise feeding it a postscript file would print the document,
>> not the postscript text/source.
>
> A really minor nit: The printer *may* support PostScript, but only in a
> sp34ecific fashion.
>

Yea, the printer doesn't do "Postscript" (ARRRGGHHH!), but after I
configured cups, which was not too painful, I've been able to print
the .ps file, and the .pdf file that I had created earlier.  I was
even able to print the .png that I had in the directory.  I printed
across three pages, but it printed...  the only thing that didn't
print was a .doc that I had, which did not print in kword, but
libreoffice works just fine.

Honestly, this is leaps and bounds ahead of where I was two weeks ago.

I still want to figure out the lpd, but for now, cups is working fine
with the ppd supplied by Brother...

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Jan Stary
In reply to this post by Bryan Brake
On Jan 30 10:23:29, Bryan wrote:

> On Sun, Jan 30, 2011 at 10:10, Christian Weisgerber <[hidden email]>
> wrote:
> > patrick keshishian <[hidden email]> wrote:
> >
> >> I'm not sure your printer support Postscript. It supports PCL-6 and
> >> BR-Script 3 (whatever the hell the latter may be)
> >
> > It's PostScript 3, but Brother didn't buy the firmware from Adobe
> > and used a different implementation.
> >
> > --
> > Christian "naddy" Weisgerber B  B  B  B  B  B  B  B  B  B  B  B
> B [hidden email]
> >
> >
>
> So I'm going to have to mess with the filters to get .ps files to
> print with the implementation of BR Script?  Guess it won't kill me to
> figure that out...

If your printer really speaks postscript, you don't have to mess with anything.
If it prints the PS source instead of the document, it probably does not
support postscript.

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Jan Stary
In reply to this post by Dennis den Brok-2
On Jan 30 21:47:40, Dennis den Brok wrote:
> patrick keshishian <[hidden email]> schrieb:
> > You keep saying and thinking that it supports post script. It does
> > not. Otherwise feeding it a postscript file would print the document,
> > not the postscript text/source.
>
> This may actually depend on the configuration.

Whether a given printer supports postscripts
is of course not a matter of configuration.

> For instance, a
> Kyocera Mita FS1030-D, without "fo" in its printcap(5) entry,
> produces output similar to the original poster's printer. (This
> under NetBSD, though.)

"fo" just forces a form feed;
it doesn't "turn PS support on/off" or whatever.

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Jan Stary
In reply to this post by Bryan Brake
On Jan 30 19:30:46, Bryan wrote:

> On Sun, Jan 30, 2011 at 15:51, Sean Kamath <[hidden email]> wrote:
> > On Jan 30, 2011, at 12:06 PM, patrick keshishian wrote:
> >>> It supports Postscript, and even has it's own lpd running so that you
> >>> can FTP files to it to print.
> >>
> >> You keep saying and thinking that it supports post script. It does
> >> not. Otherwise feeding it a postscript file would print the document,
> >> not the postscript text/source.
> >
> > A really minor nit: The printer *may* support PostScript, but only in a
> > sp34ecific fashion.
> >
>
> Yea, the printer doesn't do "Postscript" (ARRRGGHHH!), but after I
> configured cups, which was not too painful, I've been able to print
> the .ps file, and the .pdf file that I had created earlier.  I was
> even able to print the .png that I had in the directory.  I printed
> across three pages, but it printed...  the only thing that didn't
> print was a .doc that I had, which did not print in kword, but
> libreoffice works just fine.
>
> Honestly, this is leaps and bounds ahead of where I was two weeks ago.
>
> I still want to figure out the lpd, but for now, cups is working fine
> with the ppd supplied by Brother...

With the same PPD file, you should be able to print with lpd.
This is what works for me eith a non-postcript HP printer
(the PPD file coes from one of the foomatic* packages):

lp|HP Color laserJet 2600n:\
        :lp=/dev/ulpt0:\
        :af=/etc/foomatic/HP-Color_LaserJet_2600n.ppd:\
        :if=/usr/local/bin/foomatic-rip:\
        :sd=/var/spool/output:\
        :lf=/var/log/lpd-errs:\
        :sh:

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Dennis den Brok-2
In reply to this post by Jan Stary
Jan Stary <[hidden email]> schrieb:
> "fo" just forces a form feed;
> it doesn't "turn PS support on/off" or whatever.

Certainly not, but it seems the printer is picky about recognizing
PostScript as such. I don't know what data actually hits the wire,
maybe there is some bogus data sent before the actual PostScript,
but the form feed apparently cures that. Funnily, I only need this
under NetBSD.  Under OpenBSD, it does not have any effect, printing
always works, or rather works even worse but with pleasant effect:
first, an essentially blank page with a few characters sprinkled
across is printed, but then the PostScript sent is printed correctly.

As this is still a problem for me and I don't know how to fix it,
maybe I may hijack this thread and ask for a possible solution?

Thanks,
Dennis den Brok

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Otto Moerbeek
On Mon, Jan 31, 2011 at 09:37:24AM +0000, Dennis den Brok wrote:

> Jan Stary <[hidden email]> schrieb:
> > "fo" just forces a form feed;
> > it doesn't "turn PS support on/off" or whatever.
>
> Certainly not, but it seems the printer is picky about recognizing
> PostScript as such. I don't know what data actually hits the wire,
> maybe there is some bogus data sent before the actual PostScript,
> but the form feed apparently cures that. Funnily, I only need this
> under NetBSD.  Under OpenBSD, it does not have any effect, printing
> always works, or rather works even worse but with pleasant effect:
> first, an essentially blank page with a few characters sprinkled
> across is printed, but then the PostScript sent is printed correctly.
>
> As this is still a problem for me and I don't know how to fix it,
> maybe I may hijack this thread and ask for a possible solution?
>
> Thanks,
> Dennis den Brok

printcap sh is your friend.

        -Otto

Reply | Threaded
Open this post in threaded view
|

Re: Printing (well anything) using lpd...

Dennis den Brok-2
Otto Moerbeek <[hidden email]> schrieb:
> printcap sh is your friend.

It is indeed, thank you.

--
Dennis den Brok

12