Re: Printing problems
Ok, problem solved by adding either socket:// in case of JetDirect or lpd:// in case of unix-server in front of the queue-name.
Re: Printing Problems with Gnome
* Mark Phillips [EMAIL PROTECTED] [061113 15:13]: I am running Debian Etch and using the gnome desktop. I also have cups installed as well as some KDE apps. When I go to the CUPS printer administration page I can print test pages to all my networked printers. I can also print to the printers from Firefox and Kontact. However, I cannot print from Epiphany - the browser crashes each time I try to print. I went to Desktop-Administration-Printing and found both of my networked printers listed and they say they are ready. I tried printing test pages from there, and nothing printed. I checked the cups admin page, and jobs were submitted, but stopped for some unknown error. This is a long-standing bug (http://bugzilla.gnome.org/show_bug.cgi?id=374630) which I reported again yesterday when I encountered a web page (http://ezine.daemonnews.org/200210/ports.html) which crashed not only Ephiphany, but also Galeon. To be fair, the web page -- like so many, including many pages of the WordPress Codex -- appears to have composed without giving the slightest thought to the possibility that someone might like to print out a copy. When you print it with Firefox, the lines are truncated on the right-hand side, even if right and left margins are set to zero. This may be a contributing factor in the crashes with Epiphany and Galeon. Someone needs to publish a HOWTO on printer-friendly web pages. RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems with mozilla
On Friday 02 July 2004 10:07 pm, Marc Wilson wrote: In the meantime, Moz 1.6 works just fine when 'links -g' won't, and still prints when I want it to. Hrm did you compile your own links? Because the version I apt-got didn't seem to have the -g option compiled in. just wondering if there is a package I missed g. -- Microsoft: Our code is so bad it should be a crime to complain about it.
Re: Printing problems with mozilla
--- Brad Sims [EMAIL PROTECTED] wrote: Hrm did you compile your own links? Because the version I apt-got didn't seem to have the -g option compiled in. just wondering if there is a package I missed g. There used to be an unofficial package for it, but the repository seems to have vanished. Still, you don't need a package for it, just compile the source, which you'll find (by way of navigation) from here: http://atrey.karlin.mff.cuni.cz/~clock/twibright/links/ I use links2 for all my browsing, normally. -- Thomas Adam = The Linux Weekend Mechanic -- http://linuxgazette.net TAG Editor -- http://linuxgazette.net shrug We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :) -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ___ALL-NEW Yahoo! Messenger - so many all-new ways to express yourself http://uk.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems with mozilla
On Thu, Jul 01, 2004 at 05:39:39PM -0500, Brad Sims wrote: I just said heck with it and downgraded to 1.6, WTF do I need to run two seperate print daemons? Fsck me gently with a chainsaw, but between that and getting rid of Postscript printing; it adds up to an asinine decision on the parts of the devels. (And 99.5% of the time I agree with their decisions.) I keep meaning to file a bug about it on Mozilla. But I imagine it'll be ignored, so why bother? In the meantime, Moz 1.6 works just fine when 'links -g' won't, and still prints when I want it to. -- Marc Wilson | The world is moving so fast these days that the man [EMAIL PROTECTED] | who says it can't be done is generally interrupted | by someone doing it. -- E. Hubbard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems with mozilla
Brad Sims([EMAIL PROTECTED]) is reported to have said: no Xprint servers found... xprint starts with no errors... I did a apt-get purge and reinstall of xprt and friends, and mozilla and friends. echo $XPSERVERLIST returns blank and here is my output from xprint restart: [EMAIL PROTECTED]:~$ sudo /etc/init.d/xprint restart Restarting Xprint server(s): Xprt. Stopping Xprint servers: Xprt. Starting Xprint servers: Xprt. Cups is installed and working fine... However when I do a ps auxf: I do not see a xprint server listed I am not using cups so this may not help. My firefox stopped printing after the last upgrade and I had to install xprt-xprintorg xprt-common. I also could not find any printers. After much reading I finally got it working by adding this to my .bash_profile. XPSERVERLIST=`/etc/init.d/xprint get_xpserverlist` export XPSERVERLIST export LPDEST=lp+ My printcap has entries for 4 printers, lp, lpp, lp+, ep. If, after adding the above, you are printing 1/4 pages, don't forget to select the correct paper size. For some reason mine defaulted to A4 paper. Wayne -- Is reading in the bathroom considered Multi-Tasking. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems with mozilla
On Thursday 01 July 2004 7:06 am, Wayne Topa wrote: I am not using cups so this may not help. My firefox stopped printing after the last upgrade and I had to install xprt-xprintorg xprt-common. I also could not find any printers. After much reading I finally got it working by adding this to my .bash_profile. XPSERVERLIST=`/etc/init.d/xprint get_xpserverlist` export XPSERVERLIST export LPDEST=lp+ It looks like xprint is dying silently on startup. It's not found using ps, though no errors show on daemon restart. I just said heck with it and downgraded to 1.6, WTF do I need to run two seperate print daemons? Fsck me gently with a chainsaw, but between that and getting rid of Postscript printing; it adds up to an asinine decision on the parts of the devels. (And 99.5% of the time I agree with their decisions.) Bah, it prints and browses webpages. Thats all I need it to do. -- If women knew, if they even had the slightest idea of what men were thinking, they'd never stop slapping us. -- Larry Miller
Re: Printing problems w/CUPS, HP 5550, WP8
Marc Shapiro wrote: My old printer stopped working, AGAIN, so I decided that it was time for a new printer. After checking www.linuxprinting.org and looking to see what I could find available in my price range I found an HP Deskjet 5550. I decided to take advantage of changing printers to also change from LPRng to CUPS. I installed cupsys, cupsys-client, cupsys-bsd, foomatic-bin, and xpp, as well as all of their dependancies. The install went fine and I can print a text file with 'lpr filename'. Openoffice also seems to print OK. For WP8, however, I have to setup each printer in WordPerfect. WP8 is old enough that there is no option for a DJ 5550. I plan on using OpenOffice for most of my word processing, but I occaisionally get a file in WordPerfect format and OpenOffice does not have an import filter for it, so I have to fall back on my WP8. How do I get it to recognize my new printer? For WP8 to use cups printers you will have to make a printcap file in /etc. What I did was setup the printer in cups and verified it worked. Then I made a link (in konqueror I just copied the printcap.cups file back into /etc and made it a link) from printcap.cups and named it printcap. This is becuase WP was made before cups came out and looks for the printcap file. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems w/CUPS, HP 5550, WP8
Cage [EMAIL PROTECTED] wrote: For WP8 to use cups printers you will have to make a printcap file in /etc. What I did was setup the printer in cups and verified it worked. Then I made a link (in konqueror I just copied the printcap.cups file back into /etc and made it a link) from printcap.cups and named it printcap. This is becuase WP was made before cups came out and looks for the printcap file. Well, I made a link from /var/run/cups/printcap to /etc/printcap and that got Opera to print (which I noticed was not printing after my initial post), but WP8 is still not printing. It still thinks that it should be printing to my old printer even though that printer is not attatched to the system and is not in the current printcap file. I also have questions about Firebird and Thunderbird. Initially, they were not printing, either. I think that they started to work after I ran kudzu and let it configure the printer. Firebird now has only one printer option PostScript/default and printing to that works just fine. Thunderbird also has the same PostScript/default and if I print to it everything works. The problem is that, although it appears that it should be the default, it isn't. There are several other options, hpdeskjet5550@:64 (which is what does come up by default), xp_ps_spooldir_tmp_Xprintjobs@:64, and xp_pdf_spooldir_tmp_Xprintjobs@:64 are at the top of the printer list. Is there any way to get those first three not to show up, or, at least to get PostScript/default to actually be the default? -- Marc Shapiro If you drink melomel every day you will live to be 150, unless your wife shoots you first. -- Dr. Ferenc Androci -- (Winemaker, Little Hungary Farm Winery) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems....help???
I agree the list is active - subscribed to the normal 'user' list I get hundreds of messages a day. However, the digest version sends me nothing. I got the confirmation email saying I was subscribed, and resubscribing has no effect. Matt On 09/09/2002 08:02 PM, David Teague wrote: Matthew, This list is indeed active. I get from 25 to 100 messages a day. When you subscribed did you get a confirmation message? If you don't get such a message, or for some reason you don't send the confirmation back they kill your subscription. Are you using a spam filter or anything that might kill mailing list messages? David Teague -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems....help???
Hi! Is it possible you missed to autoload some of the necessary modules? What does lsmod (as root) give you? Christoph -- Kann man das klicken? -- Klaus Knopper -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems....help???
Matthew Claridge wrote: Its funny you should say that because when printtool tries to autodetect a printer, it says I don't have parallel port modules loaded. the output of lsmod looks like this: # lsmod Module Size Used byTainted: PF Mvnetd 9808 1 (unused) Mvnet 54998 0 [Mvnetd] Mvnetint 320 0 (unused) Mvw 4724 0 (unused) Mvmouse 872 0 (unused) Mvkbd984 0 (unused) Mvgic 3296 0 (unused) Mvdsp 1064 0 (unused) Mserial 6628 0 (unused) Mmpip 7172 0 (unused) Mmerge134264 0 [Mvnetd Mvnet Mvw Mvmouse Mvkbd Mvgic Mvdsp Mserial Mmpip] mki-adapter19344 0 [Mvnetd Mvnet Mvnetint Mvw Mvmouse Mvkbd Mvgic Mvdsp Mserial Mmpip Mmerge] emu10k155680 1 ac97_codec 9568 0 [emu10k1] sb_lib 32256 0 (unused) uart401 6016 0 [sb_lib] sound 52876 0 [emu10k1 sb_lib uart401] soundcore 3236 7 [emu10k1 sb_lib sound] tulip 37152 1 keybdev 1664 0 (unused) usbkbd 2816 0 (unused) input 3072 0 [keybdev usbkbd] usb-ohci 17472 0 (unused) usbcore48032 1 [usbkbd usb-ohci] Now I know there's no parport modules listed, but when I run modconf, the parport and parport-pc ARE selectedI've even tried deselecting them, rebooting and then reselecting them and rebooting again, but lsmod still doesn't list anything. maybe I broke something??? In my list of modules, I have the following loaded: parport parport_pc lp Since I don't see any of those in your 'lsmod results, I would say your printer port is not being initialized on boot-up. As a test, try to load each of these modules with modprobe and check if your printer works after loading them. If it fixes the problem, I would advise adding them to /etc/modules with any old text editor. I have had spotty luck using modconf here. Sometimes it works fine, other times it doesn't seem to insert the proper modules. I run the 2.4.18 kernel here with a mix of testing and unstable' packages, and I think my problem is probably in the mix that I have. Dunno about your setup, but you might be seeing the same things. I have found the above steps seem to be the most reliable way to get the proper modules loaded for me... Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing problems....help???
Donald R. Spoon wrote: In my list of modules, I have the following loaded: parport parport_pc lp Since I don't see any of those in your 'lsmod results, I would say your printer port is not being initialized on boot-up. As a test, try to load each of these modules with modprobe and check if your printer works after loading them. If it fixes the problem, I would advise adding them to /etc/modules with any old text editor. ok, tried using modprobe to load them, but that didn't fix the printing problem. I've added the modules to /etc/modules now and rebooted but still no printing ;o( even removing and reinstalling printtool (which at least got it going again last time) doesn't work anymore. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
Thanks for the Cups suggestion. I've now spent a little time evaluating that pathway. It smells a little like bait and switch. I have three printers - a 300 dpi HP LaserJet III, a 600 dpi HP LaserJet 4, and a 1200 dpi HP 8100 DN with duplexer. The later printer is used for data sheets, manuals, and catalogs, printed on 11 by 17 sheets. All printers accept PostScript. What I need to do is move PostScript files to them . . . period. What I don't need is something sitting between the document and the printer that limits resolution to 600 dpi. Of course I can pony up a few farthings and get support for 1200 dpi, but --- I originally managed to get lprng working under RH, so I think I'll spend some more time trying to get it working with Debian. Yes, the interface is nice, but in my case it's like using a flame thrower to make toast. -- Sincerely, David Smead http://www.amplepower.com. On Fri, 26 Apr 2002, dman wrote: On Thu, Apr 25, 2002 at 10:13:15PM -0700, David Smead wrote: | I'm running Woody with the 2.4.18 kernel. I can print using xpdq and pdq, | but when Iset up with lprngtool, the lpr command works in some cases and | not in others. | | Do these two packages interfere? I'd prefer to use lprng so that I don't | have to change the print command on several remote machines, otherwise I | just use pdq. IMO CUPS is better. It also provides an lpd interface so your other machines wouldn't even know the daemon changed. -D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
David == David Smead [EMAIL PROTECTED] writes: David I have three printers - a 300 dpi HP LaserJet III, a 600 David dpi HP LaserJet 4, and a 1200 dpi HP 8100 DN with duplexer. David The later printer is used for data sheets, manuals, and David catalogs, printed on 11 by 17 sheets. All printers accept David PostScript. What I need to do is move PostScript files to David them . . . period. If all of the accept PostScript, can't you just add yourself to the lp group, or whatever group that you arrange to have write access to the /dev nodes for you printer. Then you can just 'cat file.ps /dev/lp0' for example. This is of course only for the local computer. I guess if you're using lprng, you can just set up printcap to do the same. But don't know anything about setting up network printers. Sorry. If this is all garbage because I haven't followed the thread closely enough, just ignore. ^_^ Good luck! Marshal David What I don't need is something sitting between the document David and the printer that limits resolution to 600 dpi. Of David course I can pony up a few farthings and get support for David 1200 dpi, but --- I originally managed to get lprng working David under RH, so I think I'll spend some more time trying to David get it working with Debian. David Yes, the interface is nice, but in my case it's like using David a flame thrower to make toast. David -- Sincerely, David David Smead http://www.amplepower.com. David On Fri, 26 Apr 2002, dman wrote: On Thu, Apr 25, 2002 at 10:13:15PM -0700, David Smead wrote: | I'm running Woody with the 2.4.18 kernel. I can print using xpdq and pdq, | but when Iset up with lprngtool, the lpr command works in some cases and | not in others. | | Do these two packages interfere? I'd prefer to use lprng so that I don't | have to change the print command on several remote machines, otherwise I | just use pdq. IMO CUPS is better. It also provides an lpd interface so your other machines wouldn't even know the daemon changed. -D David -- To UNSUBSCRIBE, email to David [EMAIL PROTECTED] with a subject of David unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
On Sat, Apr 27, 2002 at 11:41:00PM -0700, David Smead wrote: | Thanks for the Cups suggestion. I've now spent a little time evaluating | that pathway. It smells a little like bait and switch. I understand what you are saying, but only if I stop at the drivers that EasySoft ships with CUPS. You need to look elsewhere for the rest of the drivers. For Real Printers (postscript) you can get a PPD from anywhere -- from Adobe, from HP, from Windows. (if you copy from windows be aware that it names the file *.SPD and is Mac-text format) | I have three printers - a 300 dpi HP LaserJet III, a 600 dpi HP LaserJet | 4, and a 1200 dpi HP 8100 DN with duplexer. The later printer is used for | data sheets, manuals, and catalogs, printed on 11 by 17 sheets. All | printers accept PostScript. What I need to do is move PostScript files to | them . . . period. I don't have any 8100s around here (I don't think) but I added that printer anyways and in the configuration options I have the following choices : Density:1-5 inclusive Economy Mode: Economy, Standard Ghostscript Resolution: 150, 300, 600, 1200 Memory Booster Technology: Auto, Off, On REt Setting: Dark, Light, Medium, Off Double Sided Printing: Off, Long Edge, Short Edge Media Source: Default, Manual, Tray [123] Page Size: lots | What I don't need is something sitting between the document and the | printer that limits resolution to 600 dpi. Of course I can pony up a few | farthings and get support for 1200 dpi, but --- I originally managed to | get lprng working under RH, so I think I'll spend some more time trying to | get it working with Debian. I think CUPS will do exactly what you want. The particular driver I'm mentioning here is HP LaserJet 8100, Foomatic + Postscript and is found in the cupsomatic-ppd package. I just took another look at it -- the description says it now it is only a transition to the foomatic-bin and foomatic-db packages, but that is incorrect. The foomatic-db package appears to only have drivers for printers handled by gimp-print. The PPDs for the rest of the printers are still in the cupsomatic-ppd package. I've been using it for quite a while now with several printers and rather like it. | Yes, the interface is nice, but in my case it's like using a flame | thrower to make toast. Some people like their toast black ;-). (I don't) -D -- He who scorns instruction will pay for it, but he who respects a command is rewarded. Proverbs 13:13 GnuPG key : http://dman.ddts.net/~dman/public_key.gpg pgpJXDcu1OO0Z.pgp Description: PGP signature
Re: printing problems
On Thursday 25 April 2002 10:13 pm, David Smead wrote: I'm running Woody with the 2.4.18 kernel. I can print using xpdq and pdq, but when Iset up with lprngtool, the lpr command works in some cases and not in others. Do these two packages interfere? I'd prefer to use lprng so that I don't have to change the print command on several remote machines, otherwise I just use pdq. is there a difference in the document formats between the cases where it does work and doesn't? ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
On Thu, Apr 25, 2002 at 10:13:15PM -0700, David Smead wrote: | I'm running Woody with the 2.4.18 kernel. I can print using xpdq and pdq, | but when Iset up with lprngtool, the lpr command works in some cases and | not in others. | | Do these two packages interfere? I'd prefer to use lprng so that I don't | have to change the print command on several remote machines, otherwise I | just use pdq. IMO CUPS is better. It also provides an lpd interface so your other machines wouldn't even know the daemon changed. -D -- If Microsoft would build a car... ... Occasionally your car would die on the freeway for no reason. You would have to pull over to the side of the road, close all of the car windows, shut it off, restart it, and reopen the windows before you could continue. For some reason you would simply accept this. GnuPG key : http://dman.ddts.net/~dman/public_key.gpg pgpDLbRiK1Iba.pgp Description: PGP signature
Re: printing problems
No, I didn't compile my own kernel. I started with the two floppies, and did a net install of stable. I downloaded the go-woody script and and let it rip and tried to act intelligent with the questions. I'm still running on the kernel from stable. More and more that looks like the problem. knuth:~# uname -a Linux knuth 2.2.19-idepci #1 Sat Jun 9 13:39:29 EST 2001 i686 unknown Should I bite the bullet and compile a kernel? -- Sincerely, David Smead http://www.amplepower.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
On Wed, Apr 24, 2002 at 09:10:30PM -0700, David Smead wrote: | No, I didn't compile my own kernel. | | I started with the two floppies, and did a net install of stable. | | I downloaded the go-woody script and and let it rip and tried to act | intelligent with the questions. | | I'm still running on the kernel from stable. More and more that looks | like the problem. | | knuth:~# uname -a | Linux knuth 2.2.19-idepci #1 Sat Jun 9 13:39:29 EST 2001 i686 unknown Ahh, yeah, definitely install a new kernel. The kernels that are built for boot-floppies are quite trimmed down due to size constraints on the floppies. I'd be kinda surprised if the installer supported printing :-). | Should I bite the bullet and compile a kernel? Either do that (use the 'kernel-package' tools) or just install a new kernel. Take your pick : apt-get install kernel-image-2.2.20 apt-get install kernel-image-2.4.18-386 Do note that if you move to a 2.4 kernel, some things are different. Most of the changes are not earth-shattering and some are really good changes, but you should be aware of them before/as you upgrade. -D -- Misfortune pursues the sinner, but prosperity is the reward for the righteous. Proverbs 13:21 pgpO6uALG6lDA.pgp Description: PGP signature
Re: printing problems
On Wed, Apr 24, 2002 at 03:10:47PM -0700, David Smead wrote: | | I'm apparently missing a driver. | | knuth:~# lpq ... | Status: cannot open '/dev/lp0' - 'No such device' | - | | knuth:~# ls -l /dev/lp0 | crw-rw1 root lp 6, 0 Jun 13 2001 /dev/lp0 This is meaningless. (well, all it means is you have an inode named lp0. You've got lots of inodes in /dev that you don't have hardware for) If you use devfs this becomes meaningful (the file won't exist unless the device and driver do). | --- | | knuth:~# lsmod | Module Size Used by | parport_pc 7276 0 (unused) | parport 6676 0 [parport_pc] # modprobe lp -D -- He is no fool who gives up what he cannot keep to gain what he cannot lose. --Jim Elliot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
begin dman [EMAIL PROTECTED] On Wed, Apr 24, 2002 at 03:10:47PM -0700, David Smead wrote: | | I'm apparently missing a driver. | | knuth:~# lpq ... | Status: cannot open '/dev/lp0' - 'No such device' | - | | knuth:~# ls -l /dev/lp0 | crw-rw1 root lp 6, 0 Jun 13 2001 /dev/lp0 This is meaningless. (well, all it means is you have an inode named lp0. You've got lots of inodes in /dev that you don't have hardware for) meaningless? the major and minor numbers are correct. the kernel certainly knows what major number 6 is. the parport driver (if present) knows what minor number 0 is. doesn't matter what you call the *file*. it's the major and minor numbers which matter. If you use devfs this becomes meaningful (the file won't exist unless the device and driver do). maybe. maybe not. depends on how devfsd is configured, doesn't it? p -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
On Wed, Apr 24, 2002 at 04:57:26PM -0700, Peter Jay Salzman wrote: | begin dman [EMAIL PROTECTED] | On Wed, Apr 24, 2002 at 03:10:47PM -0700, David Smead wrote: | | | | I'm apparently missing a driver. | | | | knuth:~# lpq | ... | | Status: cannot open '/dev/lp0' - 'No such device' | | | - | | | | knuth:~# ls -l /dev/lp0 | | crw-rw1 root lp 6, 0 Jun 13 2001 /dev/lp0 | | This is meaningless. (well, all it means is you have an inode named | lp0. You've got lots of inodes in /dev that you don't have hardware | for) | | meaningless? Linux doesn't see my SCSI disk, but look - /dev/sda1 is there. Actually, the machine has no SCSI disks or controllers. The presence of the device file has no bearing on the matter. | the major and minor numbers are correct. Ok, that is something worth verifying. | the kernel certainly knows what major number 6 is. the parport | driver (if present) knows what minor number 0 is. | | doesn't matter what you call the *file*. it's the major and minor | numbers which matter. | | If you use devfs this becomes meaningful (the file won't exist | unless the device and driver do). | | maybe. maybe not. # lsmod | grep lp lp 6208 0 # ls -l /dev/printers/0 /dev/lp0 crw-rw1 root lp 6, 0 Dec 31 1969 /dev/printers/0 lr-xr-xr-x1 root root 10 Apr 18 23:18 /dev/lp0 - printers/0 # rmmod lp # cd /lib/modules/2.4.18-custom.3/kernel/drivers/char/ # mv lp.o NOT-lp.o # (otherwise the kernel automatically loads it) # ls -l /dev/printers/0 /dev/lp0 ls: /dev/printers/0: No such file or directory ls: /dev/lp0: No such file or directory The device files exist when I have the driver loaded, and don't exist when I don't. That is why I said listing the file is meaningful only when using devfs. | depends on how devfsd is configured, doesn't it? Yeah, if you configure devfsd wrong and/or check the wrong file :-). -D -- Consider what God has done: Who can straighten what He has made crooked? Ecclesiastes 7:13 pgpMimyd9A16e.pgp Description: PGP signature
Re: printing problems
Thanks for the help. knuth:~# modprobe lp modprobe: Can't locate module lp I haven't been able to find what package this is in. -- Sincerely, David Smead http://www.amplepower.com. On Wed, 24 Apr 2002, dman wrote: On Wed, Apr 24, 2002 at 03:10:47PM -0700, David Smead wrote: | | I'm apparently missing a driver. | | knuth:~# lpq ... | Status: cannot open '/dev/lp0' - 'No such device' | - | | knuth:~# ls -l /dev/lp0 | crw-rw1 root lp 6, 0 Jun 13 2001 /dev/lp0 This is meaningless. (well, all it means is you have an inode named lp0. You've got lots of inodes in /dev that you don't have hardware for) If you use devfs this becomes meaningful (the file won't exist unless the device and driver do). | --- | | knuth:~# lsmod | Module Size Used by | parport_pc 7276 0 (unused) | parport 6676 0 [parport_pc] # modprobe lp -D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
Where will I find char-major-6 driver? -- Sincerely, David Smead http://www.amplepower.com. On Wed, 24 Apr 2002, dman wrote: On Wed, Apr 24, 2002 at 04:57:26PM -0700, Peter Jay Salzman wrote: | begin dman [EMAIL PROTECTED] | On Wed, Apr 24, 2002 at 03:10:47PM -0700, David Smead wrote: | | | | I'm apparently missing a driver. | | | | knuth:~# lpq | ... | | Status: cannot open '/dev/lp0' - 'No such device' | | | - | | | | knuth:~# ls -l /dev/lp0 | | crw-rw1 root lp 6, 0 Jun 13 2001 /dev/lp0 | | This is meaningless. (well, all it means is you have an inode named | lp0. You've got lots of inodes in /dev that you don't have hardware | for) | | meaningless? Linux doesn't see my SCSI disk, but look - /dev/sda1 is there. Actually, the machine has no SCSI disks or controllers. The presence of the device file has no bearing on the matter. | the major and minor numbers are correct. Ok, that is something worth verifying. | the kernel certainly knows what major number 6 is. the parport | driver (if present) knows what minor number 0 is. | | doesn't matter what you call the *file*. it's the major and minor | numbers which matter. | | If you use devfs this becomes meaningful (the file won't exist | unless the device and driver do). | | maybe. maybe not. # lsmod | grep lp lp 6208 0 # ls -l /dev/printers/0 /dev/lp0 crw-rw1 root lp 6, 0 Dec 31 1969 /dev/printers/0 lr-xr-xr-x1 root root 10 Apr 18 23:18 /dev/lp0 - printers/0 # rmmod lp # cd /lib/modules/2.4.18-custom.3/kernel/drivers/char/ # mv lp.o NOT-lp.o # (otherwise the kernel automatically loads it) # ls -l /dev/printers/0 /dev/lp0 ls: /dev/printers/0: No such file or directory ls: /dev/lp0: No such file or directory The device files exist when I have the driver loaded, and don't exist when I don't. That is why I said listing the file is meaningful only when using devfs. | depends on how devfsd is configured, doesn't it? Yeah, if you configure devfsd wrong and/or check the wrong file :-). -D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing problems
On Wed, Apr 24, 2002 at 05:49:15PM -0700, David Smead wrote: | Thanks for the help. | | knuth:~# modprobe lp | modprobe: Can't locate module lp | | I haven't been able to find what package this is in. kernel-image-version Did you compile your own kernel? CONFIG_PRINTER=m That module is /lib/modules/2.4.18-custom.3/kernel/drivers/char/lp.o on my system and provided by the kernel-image-2.4.18-custom.3 package I built. I also have duplicates of it for the stock kernel packages too. HTH, -D -- It took the computational power of three Commodore 64s to fly to the moon. It takes at least a 486 to run Windows 95. Something is wrong here. pgp2sO8ZoC2OO.pgp Description: PGP signature
Re: Printing Problems
On Sun, Apr 14, 2002 at 05:10:42PM -0400, [EMAIL PROTECTED] wrote: hii, Umm my printer has been messed up. It says it has to be on and online which is all the time but it keeps going back to the same message. Help me. so many printers are there in this cruel life, and which of thousands millions printers in the world is yours? Luca Pasquali - keta - GNU\Debian User I've to patch my brain and my heart, I've been hacked by the wings of love, lonelyness is for fools, society for suckers, the mountains are useful to rise up a little bit more to the sky contact me at: [EMAIL PROTECTED] [EMAIL PROTECTED] pgpGd1laKu1eL.pgp Description: PGP signature
Re: Printing Problems
On Sun, Apr 14, 2002 at 05:10:42PM -0400, [EMAIL PROTECTED] wrote: hii, Umm my printer has been messed up. It says it has to be on and online which is all the time but it keeps going back to the same message. Help me. What is your print system? What kind of printer do you have? A few more details on what you are doing when you get error message would help in diagnosing the problem. -- Jerome pgp4wOjciP6K4.pgp Description: PGP signature
Fw: Re: Printing problems - hostname bad
--- Dennis Krinke [EMAIL PROTECTED] wrote: Have you tried the apsfilter SETUP in /usr/share/apsfilter ? I was just having trouble seting up a printer with magicfilter, but apsfilter SETUP worked... Dennis Krinke On Monday 18 February 2002 08:59 pm, Steve Kennedy wrote: Resent-Sender: [EMAIL PROTECTED] The following message appeared after using dselect to install gs-aladdin, magicfilter and lprng: Starting printer spooler: 2002-01-26-17:52:22.445 Get_local_host: hostname 'debian' bad lprng. My /etc/hosts file is as follows: 127.0.0.1 localhost 216.191.62.2stn.net My /etc/network/interfaces reads: auto lo iface lo inet loopback If I try to print I get the following error: Get_local_host: hostname 'debian' bad I don't understand what this error means - debian was the default hostname when I installed the system. I'm running Woody with a 2.2.19 kernel with the following modules: Module Size Used by ppp_deflate39424 0 (autoclean) nls_cp437 3904 2 (autoclean) sb 33280 0 uart401 6148 0 [sb] sound 56480 0 [sb uart401] soundcore 2564 6 [sb sound] parport_probe 3392 0 (autoclean) parport_pc 7392 1 (autoclean) lp 4384 0 (unused) parport 7524 1 [parport_probe parport_pc lp] dummy976 0 (unused) bsd_comp3936 0 ppp20800 0 [ppp_deflate bsd_comp] slhc4304 0 [ppp] vfat9216 1 fat29312 1 [vfat] The printer is an HP DeskJet 932C. PPP and mail services work fine, but I am unable to print. I've read man pages, printing docs and linuxprinting.org. I tried installing CUPS but couldn't get it to see localhost:631.Right now, I'd be satisfied getting the most basic printing going using gs and lprng, but I'm stumped. Any advice? Thanks for the hint. I used apsfilterconfig to set up Apsfilter, and managed to print off a good-looking test page. But when I tried to print either an ASCII text or a .ps file I got the same Get_local_host: hostname 'debian' bad error message. Weird. Any other ideas?
Re: Printing problems - hostname bad
On Mon, 18 Feb 2002, Steve Kennedy wrote: The following message appeared after using dselect to install gs-aladdin, magicfilter and lprng: Starting printer spooler: 2002-01-26-17:52:22.445 Get_local_host: hostname 'debian' bad lprng. It means that your IP address does not reverse-resolve to your hostname, I think. Cameron Kerr -- [EMAIL PROTECTED] http://homepages.paradise.net.nz/~cameronk/
Re: Printing problems
I don't know what sort of printer you're using, but some printers have an option at the printer console itself to Print Separator Page or Print Separator Page After Each Job. Is it only under linux that you have this problem with this printer? If not, you may want to read your printer documentation and see if this is the case. l
Re: Printing problems
Ernesto Gonzalez Gomez [EMAIL PROTECTED] writes: After any job, I have a blank page. I tried printing to a file, and then coping this file to /dev/lp0, it works, but when I use lpr with the same file, I have again the blank page at the end. My printcap is: [snip] Afterward, Liam Black [EMAIL PROTECTED] writes: I don't know what sort of printer you're using, but some printers have an option at the printer console itself to Print Separator Page or Print Separator Page After Each Job. Is it only under linux that you have this problem with this printer? If not, you may want to read your printer documentation and see if this is the case. I have the exact same problem going from cupsomatic-ppd_0.20010420-3 to foomatic-bin_0.20020213-1, in fact I've filed a bug report, Bug#131786. It's definately a Debian-only problem. Didn't happen with the previous version of cupsomatic-ppd and doesn't happen from windoze. I'm using a HP ColorLaserJet 5M PS and cups (Debian cupsys 1.1.12-5 package) on Debian testing distribution. What filter are you using Ernesto? Magicfilter, cups, etc. What type of printer? Gary
Re: Printing problems
On Mon, Feb 11, 2002 at 12:44:58PM -0600, Ernesto Gonzalez Gomez wrote: coping this file to /dev/lp0, it works, but when I use lpr with the same file, I have again the blank page at the end. Could be a blank banner page. Have you tried lpr -h ? -- Johannes Franken Professional unix/network development mailto:[EMAIL PROTECTED] http://www.jfranken.de/
Re: Printing problems (FIXED!)
Rob Mahurin, 2002-Jan-17 08:20 -0500: After installing enscript and upgrading ghostview and gs-common, printing from netscape works: ii ghostview 1.5-27 a PostScript viewer for X11 ii gs-common 0.3.2 Common files for different Ghostscript relea ii enscript 1.6.2-4Converts ASCII text to Postscript, HTML, RTF Before I believe the problem was with converting html to postscript; html2ps produced output that crashed gv, that sort of thing. I was able to print plain text and .pdfs (produced by pdflatex, the one that worked yesterday is at http://web.utk.edu/~rmahurin/skool/syllabus.pdf) at least; I'm not sure what else I tested. I'm going to blame gs-common, since that was the only real dependency involved. Hope that helps. Let me know if I can test anything else for you. Rob Thanks Rob, this did help me. I did an update/upgrade and gs-common was upgraded. Then I checked and realized that ghostview was NOT installed. So I installed it and now my printing is working fine. Thanks to all on this thread for your help. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
Rob Mahurin, 2002-Jan-16 08:40 -0500: On Tue, Jan 15, 2002 at 07:38:04AM -0800, Jeff wrote: Error: /invalidfont in findfont Operand stack: --nostringval-- basefontdict So, I believe I have a font issue now. If you have some ideas on this, I'd really appreciate them. I'm pretty lost...still. Hi Jeff, I'm having this same problem (with an operand stack of F0 Times-Roman Font Times- after an upgrade this weekend from stable to testing. It seems to happen only from Netscape. Don't know that that helps much, but it was certainly refreshing to see the same error message on your message and on my printer :) Let me know if I can test anything for you. Rob Hey Rob, I'm still fighting with it. It happens printing from any application for me. Are you using lprng? magicfilter? What's an application that works and what is it's print command? Sorry to bombard you with questions...I appreciate you help. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
On Thu, Jan 17, 2002 at 03:11:51AM -0800, Jeff wrote: Rob Mahurin, 2002-Jan-16 08:40 -0500: On Tue, Jan 15, 2002 at 07:38:04AM -0800, Jeff wrote: Error: /invalidfont in findfont Operand stack: --nostringval-- basefontdict So, I believe I have a font issue now. If you have some ideas on this, I'd really appreciate them. I'm pretty lost...still. [..] I'm having this same problem (with an operand stack of F0 Times-Roman Font Times- after an upgrade this weekend from stable to testing. It seems to happen only from Netscape. [..] I'm still fighting with it. It happens printing from any application for me. Are you using lprng? magicfilter? What's an application that works and what is it's print command? Sorry to bombard you with questions...I appreciate you help. No problem ... I offered. You guessed my setup: lprng with magicfilter. All the programs I use just call lp. Here's a dpkg -l on lprng, magicfilter, gs, and all of their Depends: and Suggests: (I think) ii lprng 3.8.2-1lpr/lpd printer spooling system ii debconf1.0.22 Debian configuration management system ii libc6 2.2.4-7GNU C Library: Shared libraries and Timezone ii magicfilter1.2-49 automatic printer filter. ii gs 6.51-5 The Ghostscript Postscript interpreter un enscript none (no description available) ii bzip2 1.0.1-14 A high-quality block-sorting file compressor ii gzip 1.3.2-3The GNU compression utility. ii xpdf 0.93-4 Portable Document Format viewer for X11 ii libpaperg 1.1.2 Library for handling paper characteristics ii libgimpprint1 4.1.99-b1-1library necessary to use gimp-print programs ii libpng21.0.12-3 PNG library - runtime ii xlibs 4.1.0-11 X Window System client libraries ii zlib1g 1.1.3-18 compression library - runtime ii gs-common 0.3.1 Common files for different Ghostscript relea ii gsfonts6.0-2 Fonts for the ghostscript interpreter ii psfontmgr 0.10.1 PostScript font manager -- part of Defoma, D ii gs-pdfencrypt 1.0.4-6Provides support to view encrypted PDFs with After installing enscript and upgrading ghostview and gs-common, printing from netscape works: ii ghostview 1.5-27 a PostScript viewer for X11 ii gs-common 0.3.2 Common files for different Ghostscript relea ii enscript 1.6.2-4Converts ASCII text to Postscript, HTML, RTF Before I believe the problem was with converting html to postscript; html2ps produced output that crashed gv, that sort of thing. I was able to print plain text and .pdfs (produced by pdflatex, the one that worked yesterday is at http://web.utk.edu/~rmahurin/skool/syllabus.pdf) at least; I'm not sure what else I tested. I'm going to blame gs-common, since that was the only real dependency involved. Hope that helps. Let me know if I can test anything else for you. Rob -- Write yourself a threatening letter and pen a defiant reply.
Re: Printing problems
On Tue, Jan 15, 2002 at 07:38:04AM -0800, Jeff wrote: Error: /invalidfont in findfont Operand stack: --nostringval-- basefontdict So, I believe I have a font issue now. If you have some ideas on this, I'd really appreciate them. I'm pretty lost...still. Hi Jeff, I'm having this same problem (with an operand stack of F0 Times-Roman Font Times- after an upgrade this weekend from stable to testing. It seems to happen only from Netscape. Don't know that that helps much, but it was certainly refreshing to see the same error message on your message and on my printer :) Let me know if I can test anything for you. Rob -- Revenge is a meal best served cold.
Re: Printing problems
dman, 2002-Jan-14 14:04 -0500: On Mon, Jan 14, 2002 at 06:13:20PM +0200, Theo Bierman wrote: | On Mon, Jan 14, 2002 at 11:12:58AM -0500, dman wrote: | On Mon, Jan 14, 2002 at 06:00:10PM +0200, Theo Bierman wrote: | | Having trouble printing. As root everything is cool, but as a user | | when I run just a lpr I get the following: | | | | lpr | | lpr: cannot open printer description file | | | | Is this because my printcap file only allows root to print or is my | | user just not in the right group? | | What's | ls -l /etc/printcap | say? | | -rw---1 root root | | I thought of just giving myself rights but I cannot come right, | would I chown the file? Only root is allowed to read it right now. # chmod a+r /etc/printcap -D My printcap permissions are okay... -rw-r--r--1 root root 782 Jan 15 07:49 printcap thanks for checking...jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
Adam Majer, 2002-Jan-14 16:54 -0600: It's gs then.. The filter is set up correctly but gs doesn't seem to recognize pc13. I should have seen that before. gs -sDEVICE=pcl3 is the setting used by gs... It works here in unstable and woody [that device] Maybe try reinstalling gs? If your printing stopped working after an upgrade, maybe you need to upgrade it again [buggy package?] Hope this helps, Adam Thanks for you help Adam. We're make progress, I think. I purged gs and gsfonts, and re-installed them. Interestingly, gs included 2 more packages as depends that weren't installed before. This appears to have solved the device issue. Now it prints... Error: /invalidfont in findfont Operand stack: --nostringval-- basefontdict So, I believe I have a font issue now. If you have some ideas on this, I'd really appreciate them. I'm pretty lost...still. thanks again for your help...jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
Thus spake Jeff: Adam Majer, 2002-Jan-14 16:54 -0600: It's gs then.. The filter is set up correctly but gs doesn't seem to recognize pc13. I should have seen that before. gs -sDEVICE=pcl3 is the setting used by gs... It works here in unstable and woody [that device] Maybe try reinstalling gs? If your printing stopped working after an upgrade, maybe you need to upgrade it again [buggy package?] Hope this helps, Adam Thanks for you help Adam. We're make progress, I think. I purged gs and gsfonts, and re-installed them. Interestingly, gs included 2 more packages as depends that weren't installed before. This appears to have solved the device issue. Now it prints... Error: /invalidfont in findfont Operand stack: --nostringval-- basefontdict So, I believe I have a font issue now. If you have some ideas on this, I'd really appreciate them. I'm pretty lost...still. thanks again for your help...jc Try changing your printer driver - you could get one from www.linuxprinting.org - they often have print filters that work better than magicfilters. I had a similar problem getting CUPS to print with the stp driver - changing to the driver from gimpprint solved it for me. Steve -- On the whole, I'd rather be in Philadelphia. -- W.C. Fields' epitaph pgpuZVZZH0frK.pgp Description: PGP signature
Re: Printing problems
On Tue, Jan 15, 2002 at 07:38:04AM -0800, Jeff wrote: Adam Majer, 2002-Jan-14 16:54 -0600: I purged gs and gsfonts, and re-installed them. Interestingly, gs included 2 more packages as depends that weren't installed before. This appears to have solved the device issue. Now it prints... Error: /invalidfont in findfont Operand stack: --nostringval-- basefontdict So, I believe I have a font issue now. If you have some ideas on this, I'd really appreciate them. I'm pretty lost...still. This appears to look like a misconfigured filter - I got a message something like that on my DeskJet 500 a few months ago... But if you got 2 more package depends that weren't there before, your distro might be out of date... If you have fast net access, upgrade Debian to a more recent version, if not, try reconfiguring the magicfilter filter. Could you also post the reconfigured filter here? - Adam
Re: Printing problems
On Mon, Jan 14, 2002 at 06:00:10PM +0200, Theo Bierman wrote: | Hi | | Having trouble printing. As root everything is cool, but as a user | when I run just a lpr I get the following: | | lpr | lpr: cannot open printer description file | | Is this because my printcap file only allows root to print or is my | user just not in the right group? What's ls -l /etc/printcap say? -D -- Python is executable pseudocode. Perl is executable line noise.
Re: Printing problems
On Mon, Jan 14, 2002 at 11:12:58AM -0500, dman wrote: On Mon, Jan 14, 2002 at 06:00:10PM +0200, Theo Bierman wrote: | Hi | | Having trouble printing. As root everything is cool, but as a user | when I run just a lpr I get the following: | | lpr | lpr: cannot open printer description file | | Is this because my printcap file only allows root to print or is my | user just not in the right group? What's ls -l /etc/printcap say? -rw---1 root root I thought of just giving myself rights but I cannot come right, would I chown the file? -D -- Python is executable pseudocode. Perl is executable line noise. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---end quoted text--- -- Theo Bierman Customer Implementation Team UUNET S.A., a WorldCom Company Tel: +27 11 235-6621 Fax: +27 11 235-6501 E-Mail: [EMAIL PROTECTED] Customer Service Centre: 08600 UUNET / 08600 88638 http://www.uunet.co.za
Re: Printing problems
hi theo. whats the permissions on /etc/printcap? -jamie
Re: Printing problems
On Mon, Jan 14, 2002 at 11:29:12AM -0500, Jamie Oulman wrote: hi theo. whats the permissions on /etc/printcap? -rw---1 root root 392 Dec 20 13:47 printcap -jamie ---end quoted text--- -- Theo Bierman Customer Implementation Team UUNET S.A., a WorldCom Company Tel: +27 11 235-6621 Fax: +27 11 235-6501 E-Mail: [EMAIL PROTECTED] Customer Service Centre: 08600 UUNET / 08600 88638 http://www.uunet.co.za
Re: Printing problems
Stephen Gran, 2002-Jan-13 22:17 -0500: If it prints from an echo, you're halfway there. grep for pc13 (that is one-three and not el-three, right?) in your filter file - it is presumably trying to call ghostscript with that device specified, and ghostscript isn't compiled with it. I think unfortunately some devices can only be used with the commercial release of ghostscript, although I could be wrong. It may be as simple as a recompile, or it may involve changing drivers to use a free device. Hope that at least points you in the right direction. Steve I did the grep on all the magicfilters and found nothing. I checked on the ghostscript and found both of the following packages installed: ii gs 5.50-8 Postscript interpreter with X11 and svgalib ii gsfonts6.0-2 Fonts for the ghostscript interpreter So, I'm still looking for more information on the device (pc13). I'll try some straces on the process and see what that turns up. Thanks for your help. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
On Mon, Jan 14, 2002 at 06:13:20PM +0200, Theo Bierman wrote: | On Mon, Jan 14, 2002 at 11:12:58AM -0500, dman wrote: | On Mon, Jan 14, 2002 at 06:00:10PM +0200, Theo Bierman wrote: | | Having trouble printing. As root everything is cool, but as a user | | when I run just a lpr I get the following: | | | | lpr | | lpr: cannot open printer description file | | | | Is this because my printcap file only allows root to print or is my | | user just not in the right group? | | What's | ls -l /etc/printcap | say? | | -rw---1 root root | | I thought of just giving myself rights but I cannot come right, | would I chown the file? Only root is allowed to read it right now. # chmod a+r /etc/printcap -D -- Your beauty should not come from outward adornment, such as braided hair and the wearing of gold jewelry and fine clothes. Instead, it should be that of your inner self, the unfading beauty of a gentle and quiet spirit, which is of GREAT WORTH in God's sight. For this is the way the holy women of the past used to make themselves beautiful. I Peter 3:3-5
Re: Printing problems
On Sat, Jan 12, 2002 at 09:07:01PM -0800, Jeff wrote: echo test /dev/dsp I'm confused...I thought /dev/dsp was a sound device. Opps :) I meant lp0 but was thinking of something else.. And yes, the kernel is setup right. I posted the config in my original post. I sure it's right because this was working not too long ago. I tried: echo test /dev/lp0 and it printed the word test. Ok - so kernel works and printer works... I then install groff and tried printing with magicfilter printcap and it printed unknown device: pc13. I then changed to the printcap you suggested earlier and tried to print with lpr and got nothing to the printer, and lpq showed the job in error. It's gs then.. The filter is set up correctly but gs doesn't seem to recognize pc13. I should have seen that before. gs -sDEVICE=pcl3 is the setting used by gs... It works here in unstable and woody [that device] Maybe try reinstalling gs? If your printing stopped working after an upgrade, maybe you need to upgrade it again [buggy package?] Hope this helps, Adam
Re: Printing problems
Thus spake Jeff: Adam Majer, 2002-Jan-12 15:59 -0600: apt-get install groff Then you can format to ps... But first try something like echo test /dev/dsp Do you still get error with printing? If yes, do you have printer compiled in the kernel? - Adam I'm confused...I thought /dev/dsp was a sound device. Yes it is. And yes, the kernel is setup right. I posted the config in my original post. I sure it's right because this was working not too long ago. I tried: echo test /dev/lp0 and it printed the word test. I then install groff and tried printing with magicfilter printcap and it printed unknown device: pc13. I then changed to the printcap you suggested earlier and tried to print with lpr and got nothing to the printer, and lpq showed the job in error. thanks for you help...jc If it prints from an echo, you're halfway there. grep for pc13 (that is one-three and not el-three, right?) in your filter file - it is presumably trying to call ghostscript with that device specified, and ghostscript isn't compiled with it. I think unfortunately some devices can only be used with the commercial release of ghostscript, although I could be wrong. It may be as simple as a recompile, or it may involve changing drivers to use a free device. Hope that at least points you in the right direction. Steve -- Look, we play the Star Spangled Banner before every game. You want us to pay income taxes, too? -- Bill Veeck, Chicago White Sox pgpQQJZ8t7i2d.pgp Description: PGP signature
Re: Printing problems
Adam Majer, 2002-Jan-11 19:24 -0600: On Fri, Jan 11, 2002 at 04:08:44PM -0800, Jeff wrote: and the printer prints, but not the text. The output has words that look like the filter or enscript calls, e.g. '%%BoundingBox...' and '/.notdef' and '%!PS-Adobe-3.0' These are post script things. Your printer doesn't understand these. It should be using gs from the filter.. Check if you gave a correct pointer in your printcap file.. That's used by lpr. From the output it looks like the filter is never called. Okay, I checked in /etc/lprng and found a link to /etc/printcap. The link is good, and the default path to printcat for lprng is to this link. With my fiddling, I think I made it worse. Now when I try to print, the job show in error in the queue (lpq) and the printer prints Unknown device: pc13 and thats it. thanks, jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
Thus spake Jeff: Adam Majer, 2002-Jan-11 19:24 -0600: On Fri, Jan 11, 2002 at 04:08:44PM -0800, Jeff wrote: and the printer prints, but not the text. The output has words that look like the filter or enscript calls, e.g. '%%BoundingBox...' and '/.notdef' and '%!PS-Adobe-3.0' These are post script things. Your printer doesn't understand these. It should be using gs from the filter.. Check if you gave a correct pointer in your printcap file.. That's used by lpr. From the output it looks like the filter is never called. Okay, I checked in /etc/lprng and found a link to /etc/printcap. The link is good, and the default path to printcat for lprng is to this link. With my fiddling, I think I made it worse. Now when I try to print, the job show in error in the queue (lpq) and the printer prints Unknown device: pc13 and thats it. Try rerunning magicfilterconfig - it'll generate a clean /etc/printcap for you. Steve pgpB9z5N36zlE.pgp Description: PGP signature
Re: Printing problems
On Fri, Jan 11, 2002 at 10:24:57PM -0800, Jeff wrote: Adam Majer, 2002-Jan-11 19:24 -0600: On Fri, Jan 11, 2002 at 04:08:44PM -0800, Jeff wrote: and the printer prints, but not the text. The output has words that look like the filter or enscript calls, e.g. '%%BoundingBox...' and '/.notdef' and '%!PS-Adobe-3.0' These are post script things. Your printer doesn't understand these. It should be using gs from the filter.. Check if you gave a correct pointer in your printcap file.. That's used by lpr. From the output it looks like the filter is never called. Okay, I checked in /etc/lprng and found a link to /etc/printcap. The link is good, and the default path to printcat for lprng is to this link. With my fiddling, I think I made it worse. Now when I try to print, the job show in error in the queue (lpq) and the printer prints Unknown device: pc13 and thats it. Don't know. But I have /etc/printcap set like this: lp|ps|PS|PostScript|djps:\ :sd=/var/spool/lpd/lp:\ :mx#0:\ :pl#66:\ :pw#80:\ :lp=/dev/lp0:\ :if=/var/spool/lpd/lp/filter:\ :sh: sd - the location of spool directory if - input filter lp - printer device and /var/spool/lpd/lp/postscript/filter is symlinked to /etc/magicfilter/dj500 Try setup like that except you link to your printer.. Then try lpr with a PostScript file. Or print map page for something, eg. file man -t file | lpr
Re: Printing problems
Hi. I have problem with printing from RedHat to coputer with Debian (307-4). From another computer (Debian ...) printing works good. From computer with RedHat: ~$ lpr printcap ~$ lpq Printer: [EMAIL PROTECTED] 'galprint' (dest [EMAIL PROTECTED]) Queue: no printable jobs in queue Server: no server active ^ Status: job 'cfA300localhost.localdomain' saved at 15:56:29.307 Rank Owner/ID Class Job Files Size Time done root A 300 printcap 107 15:56:29 Printer: [EMAIL PROTECTED] 'Printer1 auto' Queue: no printable jobs in queue Status: job 'cfA020ADDR307-4.mao.kiev.ua' saved at 16:02:41.222 ~$ When I am printig from this computer to other (no Debian) printing works! This is mystery!!! I am using LPRng on all computers.
Re: Printing problems
On Fri, Jan 11, 2002 at 04:08:44PM -0800, Jeff wrote: I'm having some trouble. This used to work, and all-of-a-sudden it isn't now. I have a woody/2.4.16 system with an HP Deskjet 952C on the parallel port. I use LPRNG and MAGICFILTER with the dj690c-filter, and this has worked fine in the past. I've done a few apt-get update/upgrades since last I printed, so I'm suspicious of something that might have changed in an upgrade. My BIOS setting for the port is ECP and my kernel settings are: CONFIG_PARPORT=y CONFIG_PARPORT_PC=y CONFIG_PARPORT_PC_CML1=y CONFIG_PARPORT_1284=y CONFIG_PRINTER=y The following lines show up in /var/log/dmesg: parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] parport0: irq 7 detected parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) lp0: using parport0 (polling). I can send data to the printer using: cat text.file /dev/lp0 and... lpr text.file and... enscript -1 -G text.file and the printer prints, but not the text. The output has words that look like the filter or enscript calls, e.g. '%%BoundingBox...' and '/.notdef' and '%!PS-Adobe-3.0' This is messing with me...I feel like I'm close, but I'm missing something small. I've purged and reinstalled LPRNG and MAGICFILTER, and even tried using LPR, but no luck. Any help will much appreciated. thanks, jc -- Jeff Coppock Systems Engineer Diggin' DebianAdmin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] What is the content of /etc/printcap ? -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln
Re: Printing problems
Joachim Fahnenmueller, 2002-Jan-12 09:43 +0100: On Fri, Jan 11, 2002 at 04:08:44PM -0800, Jeff wrote: I'm having some trouble. This used to work, and all-of-a-sudden it isn't now. I have a woody/2.4.16 system with an HP Deskjet 952C on the parallel port. I use LPRNG and MAGICFILTER with the dj690c-filter, and this has worked fine in the past. I've done a few apt-get update/upgrades since last I printed, so I'm suspicious of something that might have changed in an upgrade. snip What is the content of /etc/printcap ? lp|dj952c|HP Deskjet 952C:\ :lp=/dev/lp0:sd=/var/spool/lpd/dj952c:\ :sh:pw#80:pl#66:px#1440:mx#0:\ :if=/etc/magicfilter/dj690c-filter:\ :af=/var/log/lp-acct:lf=/var/log/lp-errs: This is generated using 'magicfilterconf'. I've recreated it a few times. thanks, jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
Adam Majer, 2002-Jan-12 02:46 -0600: Don't know. But I have /etc/printcap set like this: lp|ps|PS|PostScript|djps:\ :sd=/var/spool/lpd/lp:\ :mx#0:\ :pl#66:\ :pw#80:\ :lp=/dev/lp0:\ :if=/var/spool/lpd/lp/filter:\ :sh: sd - the location of spool directory if - input filter lp - printer device and /var/spool/lpd/lp/postscript/filter is symlinked to /etc/magicfilter/dj500 Try setup like that except you link to your printer.. Then try lpr with a PostScript file. Or print map page for something, eg. file man -t file | lpr Thanks for the suggestion, it didn't work. I'm still getting the unknown device: pc13 error. I feel like I'm moving backwards on this! I put the symlink in /var/spool/lpd/lp as filter pointing to /etc/magicfilter/dj... and changed the lp line in your printcap to match up to my printer. I tried your printcap as is first, then changed the lp line, but no luck. man -t ... didn't work, it got [212] $ man -t file /usr/bin/groff: can't find `DESC' file /usr/bin/groff:fatal error: invalid device `ps' man: command exited with status 768: /usr/bin/zsoelim /tmp/zman9jrbHR | /usr/bin/groff -mandoc I'm sure that I'm doing something wrong, just don't know what. thanks for you help. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
On Sat, Jan 12, 2002 at 07:35:56AM -0800, Jeff wrote: Adam Majer, 2002-Jan-12 02:46 -0600: Try setup like that except you link to your printer.. Then try lpr with a PostScript file. Or print map page for something, eg. file man -t file | lpr Thanks for the suggestion, it didn't work. I'm still getting the unknown device: pc13 error. I feel like I'm moving backwards on this! I put the symlink in /var/spool/lpd/lp as filter pointing to /etc/magicfilter/dj... and changed the lp line in your printcap to match up to my printer. I tried your printcap as is first, then changed the lp line, but no luck. man -t ... didn't work, it got [212] $ man -t file /usr/bin/groff: can't find `DESC' file /usr/bin/groff:fatal error: invalid device `ps' man: command exited with status 768: /usr/bin/zsoelim /tmp/zman9jrbHR | /usr/bin/groff -mandoc I'm sure that I'm doing something wrong, just don't know what. apt-get install groff Then you can format to ps... But first try something like echo test /dev/dsp Do you still get error with printing? If yes, do you have printer compiled in the kernel? - Adam
Re: Printing problems
On Sat, Jan 12, 2002 at 04:13:00PM +0200, Petrov M.I. wrote: Hi. I have problem with printing from RedHat to coputer with Debian (307-4). From another computer (Debian ...) printing works good. From computer with RedHat: ~$ lpr printcap ~$ lpq Printer: [EMAIL PROTECTED] 'galprint' (dest [EMAIL PROTECTED]) Hmmm.. localhost? Doesn't seem to be right if you are printing to another host Queue: no printable jobs in queue Server: no server active ^ Status: job 'cfA300localhost.localdomain' saved at 15:56:29.307 Rank Owner/ID Class Job Files Size Time done root A 300 printcap 107 15:56:29 Printer: [EMAIL PROTECTED] 'Printer1 auto' Queue: no printable jobs in queue Status: job 'cfA020ADDR307-4.mao.kiev.ua' saved at 16:02:41.222 See, here you have some sort of a domain not localhost. ~$ When I am printig from this computer to other (no Debian) printing works! This is mystery!!! I am using LPRng on all computers. Check if you have setup RedHat to address for Debian machine and that on Debian you actually accept the address of RedHat machine for printing. - Adam
Re: Printing problems
Adam Majer, 2002-Jan-12 15:59 -0600: apt-get install groff Then you can format to ps... But first try something like echo test /dev/dsp Do you still get error with printing? If yes, do you have printer compiled in the kernel? - Adam I'm confused...I thought /dev/dsp was a sound device. And yes, the kernel is setup right. I posted the config in my original post. I sure it's right because this was working not too long ago. I tried: echo test /dev/lp0 and it printed the word test. I then install groff and tried printing with magicfilter printcap and it printed unknown device: pc13. I then changed to the printcap you suggested earlier and tried to print with lpr and got nothing to the printer, and lpq showed the job in error. thanks for you help...jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: Printing problems
On Fri, Jan 11, 2002 at 04:08:44PM -0800, Jeff wrote: and the printer prints, but not the text. The output has words that look like the filter or enscript calls, e.g. '%%BoundingBox...' and '/.notdef' and '%!PS-Adobe-3.0' These are post script things. Your printer doesn't understand these. It should be using gs from the filter.. Check if you gave a correct pointer in your printcap file.. That's used by lpr. From the output it looks like the filter is never called.
Re: printing problems
begin: [EMAIL PROTECTED] [EMAIL PROTECTED] quote Hi, I have a hewlett packard deskjet 697C. I have been able to print from off the Web on this printer before. In the past day, every time I print, the paper just run through without any printing on it. It does even try to print. Please need help or any suggestions? if it spits out paper, your printer is recognized by the kernel AND the spooler is working. this narrows down the problem considerably. exactly what application are you using to print the blank pages? try another application. can other applications print ok? pete -- PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D PGP Public Key: finger [EMAIL PROTECTED]
Re: Printing problems with pdq Kernel 2.4.4
Volker Schlecht wrote: On Mon, May 14, 2001 at 09:19:49PM +0200, Volker Schlecht wrote: Kernel Versions: 2.4.2 2.4.4 pdq: 2.2.1-4 on Woody When I tell pdq to print a given (Postscript) document, it tells me that it doesn't know how to print this filetype and cancels. According to my boot messages though, the Kernel sets up /dev/lp0 and recognizes my printer (well, it reads the vendor information). I just got what I hope is a hint as to where the problem might be buried. I just upgraded file to 3.33-5 from unstable and tested again - and, behold, printing worked with 2.4.4 - until I tried to play with pdq a little and see what it would do with a pdf file. Of course it refused to print the pdf, but subseqently refused to print all other files (which it printed flawlessly before). With Kernel 2.4.2 a pdf would not irritate pdq in any way. (Keep the flamethrowers in your pocket. Apparently it _has_ something to do with the Kernel, since this is the only thing that changed between tests) I'm still puzzled, though, and would love to hear if anyone has an idea about what may be behind all this. Nothing to add, only to say that with a similar configuration (here using sid), suddenly happened i can print ps file only one time, the second attempt result in a pdq/gs error (something about failing to decode the file). Seems we are at least two with the same problem, but don't know where (i.e. for what package) to file a bug report in. I will exclude gs cause it in hold (i've build it myself to include the stp driver) for ages (the version installed is still the 5.10-11, now in sid there is the 5.50-7, probably need to upgrade =). It's strange, after a reboot i can print again, but only the first time. Not tried yet with a older kernel... Andrea
Re: Printing problems with pdq Kernel 2.4.4
On Mon, May 14, 2001 at 09:19:49PM +0200, Volker Schlecht wrote: Kernel Versions: 2.4.2 2.4.4 pdq: 2.2.1-4 on Woody When I tell pdq to print a given (Postscript) document, it tells me that it doesn't know how to print this filetype and cancels. According to my boot messages though, the Kernel sets up /dev/lp0 and recognizes my printer (well, it reads the vendor information). I just got what I hope is a hint as to where the problem might be buried. I just upgraded file to 3.33-5 from unstable and tested again - and, behold, printing worked with 2.4.4 - until I tried to play with pdq a little and see what it would do with a pdf file. Of course it refused to print the pdf, but subseqently refused to print all other files (which it printed flawlessly before). With Kernel 2.4.2 a pdf would not irritate pdq in any way. (Keep the flamethrowers in your pocket. Apparently it _has_ something to do with the Kernel, since this is the only thing that changed between tests) I'm still puzzled, though, and would love to hear if anyone has an idea about what may be behind all this. regards, Volker (Who is unspeakably glad that the document he needed printed was an order for a Laser printer capable of PostScript :)) -- I'd love to go out with you, but I've been scheduled for a karma transplant.
Re: Printing problems using CUPS
When you look at the http cups interface and add a printer, the second item you choose is the port. If the ports are not listed THEN: Check which version of cups you are running (cups manual has the version number on th efront page. You get to it via the html interface and 'help' If the version # is lower than 1.1.6 than upgrade to 1.1.6 (latest) which has a bug fix for this. BTW, it took wayyy too much time and wyy too much banging my head against the wall to figure this out. See also another thread on the list if you are planning to use Kups with cups. There also still might be a problem with gimp-print if you are going to use that as well. I am still working on these items Jens On Wed, 21 Mar 2001 20:54:00 +0100, you wrote: Hi, I'm trying to setup my printer using CUPS. The problem is CUPS doesn't see my printer at all : socrate:/home/alci# lpinfo -v file file Nevertheless, the kernel recognizes it : socrate:/home/alci# cat /proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 ttyS 5 cua 6 lp ... Where should I look for ? (I'm using kernel 2.4.2, parport and printer are compiled in the kernel and not as modules, but I guess it should be ok). Franck
Re: Printing Problems-SOLVED
I, [EMAIL PROTECTED], also want to set up my Exson Stylus Color 600. How did you get it going. And yes I would like the script. thanks John - Original Message - From: Dale Morris [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, February 28, 2001 5:20 AM Subject: Re: Printing Problems-SOLVED I was able to get this working with a script that one of the list members supplied me with. If you need it please email me and I will send it to you. Dale Morris [EMAIL PROTECTED] wrote: I've been installing debian most all day, so I'm probably missing something really obvious here, but I'm having a real problem with the printer setup. How do I get printing setup correctly in debian? I have installed lprng and magic filter but I can't get it to print. I have also tried printtool, but that doesn't work either. And of course apsfilter. My printer is an Epson Stylus Color 600. I've set it up to print at 720dpi on plain paper. Does anyone have a working printcap file for this printer that they will send to me? I want to be able to print using the command lp so I can print messages from mutt or slrn, Here's what I get when I try to print a simple text file: [EMAIL PROTECTED]:~/writing$ lp quills request id is [EMAIL PROTECTED] ..at this point nothing happens.. so I issue lpq command [EMAIL PROTECTED]:~/writing$ lpq Printer: [EMAIL PROTECTED] 'Epson Stylus Color' Queue: no printable jobs in queue Status: removing job '[EMAIL PROTECTED]' - ABORT at 20:13:55.027 Filter_status: lp is ready and printing Printing used to be quite easy to setup using printtool, but it doesn't work for me now.. any help on this one is greatly appreciated. I've attached a copy of my existing printcap file.. thanks dale -- You are entitled to your actions...not the results --Bhagavad Gita # # Copyright (c) 1983 Regents of the University of California. # All rights reserved. # # Redistribution and use in source and binary forms are permitted # provided that this notice is preserved and that due credit is given # to the University of California at Berkeley. The name of the University # may not be used to endorse or promote products derived from this # software without specific prior written permission. This software # is provided ``as is'' without express or implied warranty. # # @(#)etc.printcap 5.2 (Berkeley) 5/5/88 # # This file was generated by /usr/sbin/magicfilterconfig. # lp|lp|Epson Stylus Color:\ :lp=/dev/lp0:sd=/var/spool/lpd/lp:\ :sh:pw#80:pl#66:px#1440:mx#0:\ :if=/etc/magicfilter/[EMAIL PROTECTED]:\ :af=/var/log/lp-acct:lf=/var/log/lp-errs: -- You are entitled to your actions...not the results --Bhagavad Gita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing Problems-SOLVED
I was able to get this working with a script that one of the list members supplied me with. If you need it please email me and I will send it to you. Dale Morris [EMAIL PROTECTED] wrote: I've been installing debian most all day, so I'm probably missing something really obvious here, but I'm having a real problem with the printer setup. How do I get printing setup correctly in debian? I have installed lprng and magic filter but I can't get it to print. I have also tried printtool, but that doesn't work either. And of course apsfilter. My printer is an Epson Stylus Color 600. I've set it up to print at 720dpi on plain paper. Does anyone have a working printcap file for this printer that they will send to me? I want to be able to print using the command lp so I can print messages from mutt or slrn, Here's what I get when I try to print a simple text file: [EMAIL PROTECTED]:~/writing$ lp quills request id is [EMAIL PROTECTED] ..at this point nothing happens.. so I issue lpq command [EMAIL PROTECTED]:~/writing$ lpq Printer: [EMAIL PROTECTED] 'Epson Stylus Color' Queue: no printable jobs in queue Status: removing job '[EMAIL PROTECTED]' - ABORT at 20:13:55.027 Filter_status: lp is ready and printing Printing used to be quite easy to setup using printtool, but it doesn't work for me now.. any help on this one is greatly appreciated. I've attached a copy of my existing printcap file.. thanks dale -- You are entitled to your actions...not the results --Bhagavad Gita # # Copyright (c) 1983 Regents of the University of California. # All rights reserved. # # Redistribution and use in source and binary forms are permitted # provided that this notice is preserved and that due credit is given # to the University of California at Berkeley. The name of the University # may not be used to endorse or promote products derived from this # software without specific prior written permission. This software # is provided ``as is'' without express or implied warranty. # # @(#)etc.printcap5.2 (Berkeley) 5/5/88 # # This file was generated by /usr/sbin/magicfilterconfig. # lp|lp|Epson Stylus Color:\ :lp=/dev/lp0:sd=/var/spool/lpd/lp:\ :sh:pw#80:pl#66:px#1440:mx#0:\ :if=/etc/magicfilter/[EMAIL PROTECTED]:\ :af=/var/log/lp-acct:lf=/var/log/lp-errs: -- You are entitled to your actions...not the results --Bhagavad Gita
Re: Printing Problems
I've found magicfilterconfig to be quite reliable. Primitive but reliable. And, I can't seem to get printtool to work either. At least it fails at setting up my local Canon BJ30 printer. It works fine with the BJ600 driver in magicfilter. Harald
Re: Printing Problems
My problem also with an Epson SC 600. [EMAIL PROTECTED] - Original Message - From: Dale Morris [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Monday, February 26, 2001 8:46 PM Subject: Printing Problems I've been installing debian most all day, so I'm probably missing something really obvious here, but I'm having a real problem with the printer setup. How do I get printing setup correctly in debian? I have installed lprng and magic filter but I can't get it to print. I have also tried printtool, but that doesn't work either. And of course apsfilter. My printer is an Epson Stylus Color 600. I've set it up to print at 720dpi on plain paper. Does anyone have a working printcap file for this printer that they will send to me? I want to be able to print using the command lp so I can print messages from mutt or slrn, Here's what I get when I try to print a simple text file: [EMAIL PROTECTED]:~/writing$ lp quills request id is [EMAIL PROTECTED] ..at this point nothing happens.. so I issue lpq command [EMAIL PROTECTED]:~/writing$ lpq Printer: [EMAIL PROTECTED] 'Epson Stylus Color' Queue: no printable jobs in queue Status: removing job '[EMAIL PROTECTED]' - ABORT at 20:13:55.027 Filter_status: lp is ready and printing Printing used to be quite easy to setup using printtool, but it doesn't work for me now.. any help on this one is greatly appreciated. I've attached a copy of my existing printcap file.. thanks dale -- You are entitled to your actions...not the results --Bhagavad Gita
Re: Printing problems
Ho-Kuo Chan wrote: Hello, I am running Debian potato and have set up an SMB printer with Printtool (3.53-1) and LPRng (3.2-11). The printer is an HP LaserJet 8100 DN. It was working fine until recently, I think a package update may have caused the problem. The problem is that when I send ... I noticed that there is no /var/spool/lpd/lp/filter file. Could this be the problem? I have tried i am having the exact same problem. t
Re: Printing problems!
First I used TCP/IP to connect to the printer, but there was a problem with postscript containing binary data. They never came out. After that I start using AppleTalk (pap) to connect to the printer, but we still getting some errors and lost printouts. Do you have problems with printouts for your PC's ? Uwe
Re: Printing problems!
Hi everyone! Our company is a small publishing house and we got some troubles with printing on our HP LaserJet 5MP. We got Linux box acting as print spooler for WinPC and MACs and HP LaserJet 5MP connected to network with external Jet Direct EX PLUS card. We are using Netatalk 1.4b2+asun2 and Samba1.9.18p10-7 for file sharing and together with LPRng 3.5.2-1.3 for printing. First I used TCP/IP to connect to the printer, but there was a problem with postscript containing binary data. They never came out. After that I start using AppleTalk (pap) to connect to the printer, but we still getting some errors and lost printouts. Unfortunately I start using Linux just last summer, so I¹m just beginner and need some help! Also have a look at: http://www.giub.unibe.ch/~eugster/appleprint.html; - and - http://gdr.free.fr/linux2.html; Uwe
Re: Printing problems!
Only very large printfiles (~60Mb) from PC's didn't print! -- From: [EMAIL PROTECTED] To: Juris Valdmanis [EMAIL PROTECTED] Subject: Re: Printing problems! Date: Fri, Feb 18, 2000, 2:55 PM First I used TCP/IP to connect to the printer, but there was a problem with postscript containing binary data. They never came out. After that I start using AppleTalk (pap) to connect to the printer, but we still getting some errors and lost printouts. Do you have problems with printouts for your PC's ? Uwe
Re: Printing Problems
Did you check ipchains and /etc/hosts.deny ??? Just a quick thought, Onno At 09:13 AM 11/16/99 -0700, Sean McIlwain wrote: I am still attempting to print to my serial printer using lpr. I tried to following: 1)root# ifconfig lo 127.0.0.1 2)root# route add -host 127.0.0.1 lo 3)reboot and made sure that the lpd started up correctly. 4)root# lpr test.txt I still get the same result as before transfer to [EMAIL PROTECTED] failed What else could be wrong? I also tried to telnet into 127.0.0.1 but I got an Connection Refused error.
Re: Printing Problems
Well, a couple of things could be going wrong. for starters, if you did steps 1 2 by hand, then rebooted, your hand made changes may be lost... this is highly likely if it didn't work initially on boot. what id recommend doing instead of rebooting.. is this: 0. cold boot the computer (this step is optional ; 1. stop the lpd service (/etc/init.d/lprng stop) 2. ifconfig lo 127.0.0.1 3. route add -host 127.0.0.1 lo 4. start the lpd service (/etc/init.d/lprng start) 5. lpr test.txt if step 5 doesnt work, try: 6. telnet 127.0.0.1 printer (or whatever entry is in /etc/services for printing, i forget the specific name) also, make sure that you have an entry somewhat similar to this in the /etc/hosts file: 127.0.0.1 localhost.localdomain localhost or just 127.0.0.1 localhost finally, an outside shot would be to look in /etc/hosts.deny and see if there are any lpd entries.(this is probably not your problem, but i thought id throw it out) have you checked in /var/log/syslog or /var/log/messages, or /var/log/lp*, etc. system log files to see if there is an error with your printcap or lprng config files?(Maybe others on the list have already addressed some of these topics?) I hope this helps you, Josh On Tue, 16 Nov 1999, Sean McIlwain wrote: I am still attempting to print to my serial printer using lpr. I tried to following: 1)root# ifconfig lo 127.0.0.1 2)root# route add -host 127.0.0.1 lo 3)reboot and made sure that the lpd started up correctly. 4)root# lpr test.txt I still get the same result as before transfer to [EMAIL PROTECTED] failed What else could be wrong? I also tried to telnet into 127.0.0.1 but I got an Connection Refused error. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: printing problems
On Mon, Nov 15, 1999 at 02:10:39AM -0700, Sean McIlwain wrote: I'm having problems using lpr on my system when I type lpr test.txt I get the following connection to 'localhost' failed - Connection refused transfer to [EMAIL PROTECTED] failed 1) did you set up a loopback-device? (/sbin/ifconfig) 2) did you set up a route to localhost (/sbin/route) 3) did you start lpd? Jan
Re: Printing problems
Mono wrote: thinks that it's been printed and nothing turns up in the spool. Where, exactly, is my printer? In order to know which /dev/lp* is connected actually to your printer you can use a simple test as root (or user pertaining to group lp) in order to have write permission to the device: # ls -l /dev/lp* # echo Hello world /dev/lp0 # echo Hello world /dev/lp1 ... -- Conrado Badenas (Assistant Lecturer) Department of Thermodynamics. University of Valencia c/. Doctor Moliner, 50 | e-m: [EMAIL PROTECTED] 46100 Burjassot (Valencia) | Phn: +34-63864350 SPAIN| Fax: +34-63983385
Re: Printing Problems Con't
Do you mean that nothing at all is printed when you try to print from Netscape? Or do you get partial printouts? I don't know if this will pertain to you, but I had problems printing everything that wasn't plain-text. I installed the gs-aladdin package to replace the default gs package, re-ran magicfilterconfig, and I was good to go. Maybe you can try that. HTH, Mark -Original Message- From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: debian-user@lists.debian.org debian-user@lists.debian.org Date: Tuesday, March 16, 1999 3:19 PM Subject: Printing Problems Con't First off, let me say thanks to those of you who helped me get remote printing to work. Now, I am still having a small problem with the remote printing. Nothing will print from netscape. I can print using the lp command, and with most programs (xemacs, tkrat, etc). Any idea what might be going on?
Re: Printing problems
Patrick Colbeck wrote: I haven't made any changes to my printing setup but all of a sudden I have started getting this error when trying to print no connect permissions I am using Debian 2.0 upgraded to Slink and I do an update by APT every week. My last update was yesterday perhaps this may have casued the problem ? You probably have lprng_3.5.2-1.2 installed which has a bug with permissions. lprng_3.5.2-1.3.deb fixes the bug and it should available at the mirrors. If that does not help, check the mailing list archives and see what Chuck Stickelman [EMAIL PROTECTED] wrote under subject LPRng - Solved!! // Heikki -- Heikki Vatiainen * [EMAIL PROTECTED] Tampere University of Technology * Tampere, Finland
Re: Printing problems
On Tue Feb 02, 1999 at 03:39:23PM +0300, Heikki Vatiainen wrote: Patrick Colbeck wrote: I haven't made any changes to my printing setup but all of a sudden I have started getting this error when trying to print no connect permissions I am using Debian 2.0 upgraded to Slink and I do an update by APT every week. My last update was yesterday perhaps this may have casued the problem ? You probably have lprng_3.5.2-1.2 installed which has a bug with permissions. lprng_3.5.2-1.3.deb fixes the bug and it should available at the mirrors. If that does not help, check the mailing list archives and see what Chuck Stickelman [EMAIL PROTECTED] wrote under subject LPRng - Solved!! // Heikki Thanks very much the new lprng fixed the problem straight away. Pat -- Patrick Colbeck email: [EMAIL PROTECTED] Senior Analysttel: you dont seriously expect me to Azlan Ltd give that out on the internet do you ?
Re: printing problems
On Wed, 20 Jan 1999, John Cuson wrote: last week i started working on printing to a networked printer that uses an hp jetdirect card. i can get the print jobs to the printer, but the output is not appropriately formatted. when i simply lpr a test file, it appears that i am not getting line feeds...the first line of text is printed, but is never wrapped. when i try to print a man page by piping the output to lpr as suggested in the printing usage howto i get blank pages, though if i remove the intervening pipe to the col program i do get one character at the far right margin of the page. here are the relevant lines from /etc/printcap: [snip] i've looked around in the faqs and howto's, the 2nd edition of running linux, and the various docs for this distribution (debian), but i'm not finding anything that seems directly pertinent. does anyone have any suggestions? /usr/doc/HOWTO/Printing-HOWTO.gz Section 11.5 HTH, Brandon +--- ---+ | Brandon Mitchell * [EMAIL PROTECTED] * http://bhmit1.home.ml.org/ | | The above is a completely random sequence of bits, any relation to | | an actual message is purely accidental. |
Re: Printing Problems
On Sun, 25 Oct 1998, Lance Hoffmeyer wrote: I have been trying to follow the Printing-HOWTO instructions, but to no avail. In my printcap I have lp :sd:/var/spool/lpd/lp:\ :mx#0\ :lp=/dev/lp1:\ :sh: I'm no expert, but it looks to me like you have several typos. I believe there should be :\ on the end of line 0, and on line 1 the : following :sd should be =, and on line 2 there should be : before \. I'd try these changes and see what happens. Kent
Re: printing problems
Bradley Bell wrote:
I need to print to an HP Laserjet 5Si printer which is hooked up to a
netware network,
Can anybody point me to any resources on printing to netware printers?
I've studied and tried every trick in the IPX- and Printing-HOWTO, and
the instructions there are pretty insufficient when it comes to this
problem.
At the moment, I can almost print text files using nprint, but they come
out staircased and sideways, and with no banner page.
If anybody else has gotten this working, can I see your printcap and
filter files?
Yeah, it works fine here. I use a combination of magicfilter (debian
package) and nprint. We have a number of printers all hooked up to a
host called ics1. I wrote a wrapper for nprint to make the
authentification and to be able to send data to nprint by stdin.
Attached are the makefiles, source, printcap, and a magicfilter file for
one of the printers.
My set up is like this:
/etc/printer/ics1/.nwclient -- authentification (holds ICS1/username
password)
/Makefile -- rules to make a printer
/tess-ps-1 -- one of the printers.
/nw-printer.c -- source to generate a wrapper for each
printer
/tess-ps -- a wrapper binary generated by the
makefile
You will probably need to make small changes to Makefile and printcap.
Also change a magicfilter generate filter to get it to use the wrapper.
Hope the attachments help you on your way,
DirkSHELL=/bin/sh
NW_WHERE=-DHOME=\/etc/printer/ics1\ -DSERVER=\ics1\
CC=gcc -Wall -W -Werror
all: tess-ps tess-tinte tess-ps-kyo37
tess-ps : tess-ps.o
gcc -o $@ $^
chown root.root $@
chmod ug+s $@
tess-ps.o: nw-printer.c
gcc -o $@ -c $^ -Wall -W -Werror $(NW_WHERE) -DQUEUE=\tess-ps\
tess-tinte : tess-tinte.o
gcc -o $@ $^
chown root.root $@
chmod ug+s $@
tess-tinte.o: nw-printer.c
gcc -o $@ -c $^ -Wall -W -Werror $(NW_WHERE) -DQUEUE=\tess-tinte\
tess-ps-kyo37 : tess-ps-kyo37.o
gcc -o $@ $^
chown root.root $@
chmod ug+s $@
tess-ps-kyo37.o: nw-printer.c
gcc -o $@ -c $^ -Wall -W -Werror $(NW_WHERE) -DQUEUE=\tess-ps-kyo37\
/* -*- c -*-
Dirk Bonne
wrapper for nprint, to get authentification working and
make it accept data from the stdin ---magicfilter prefers
this.
*/
#include stdlib.h
#include stdio.h
#include errno.h
#include string.h
#include unistd.h
#include pwd.h
#include sys/types.h
#include sys/stat.h
#define WHO_CAN_RUN_ME daemon
int
main(int argc, char** argv)
{
int ret;
char tmpfile[512] = /tmp/tmpXX;
char cmd[1024];
struct passwd* pass;
int fd;
char tmpbuf[8192];
ssize_t nread;
if(argc != 1) {
fprintf(stderr, usage: %s\n, argv[0]);
return 1;
}
if(!(pass = getpwnam(WHO_CAN_RUN_ME))) {
fprintf(stderr, getpwname failed for WHO_CAN_RUN_ME : %s,
strerror(errno));
return 1;
}
if(getuid() != 0 getuid() != pass-pw_uid) {
fprintf(stderr, only root or WHO_CAN_RUN_ME can run me, not
you(%d)!\n,
getuid());
return 1;
}
if(-1 == setreuid(geteuid(), geteuid())) {
fprintf(stderr, setreuid: %s\n, strerror(errno));
return 1;
}
setenv(HOME, HOME, 1); /* so nprint can find .nwclient */
/* nprint wants a file: */
if(-1 == (fd=mkstemp(tmpfile))) {
fprintf(stderr, mkstemp failed: %s\n, strerror(errno));
return 1;
}
while(0 != (nread = read(STDIN_FILENO, tmpbuf, sizeof(tmpbuf {
if(nread == -1) {
if(errno != EINTR) {
fprintf(stderr, read on stdin failed: %s\n, strerror(errno));
return 1;
}
} else {
ssize_t nwrite;
const char* p = tmpbuf;
while(nread 0 0 != (nwrite = write(fd, p, nread))) {
nread -= nwrite; /* potentially hangs, if nwrite is zero */
p += nwrite;
}
if(nwrite == -1) {
fprintf(stderr, write failed: %s\n, strerror(errno));
return 1;
}
}
}
close(fd);
sprintf(cmd, strace /usr/bin/nprint -S SERVER -q QUEUE %s 12,
tmpfile);
fprintf(stderr, %s\n, cmd);
fprintf(stderr, %s\n, getenv(HOME));
system(env 12);
system(id 12);
ret = system(cmd);
if(ret == -1) {
fprintf(stderr, system(%s): %s, cmd, strerror(errno));
return 1;
} else if(ret == 127) {
fprintf(stderr, call of /bin/sh failed for ´%s´\n, cmd);
return 1;
} else {
unlink(tmpfile);
return ret;
}
}
#!/usr/sbin/magicfilter
# Dirk Bonne
# PostScript
#0 %! postscript
#0 \004%! postscript
0 %! filter /etc/printer/ics1/tess-ps
0 \004%! filter /etc/printer/ics1/tess-ps
# TeX DVI
0 \367\002fpipe /usr/bin/dvips -D 600 -R -q -F -f
# compress'd data
0 \037\235pipe/bin/gzip -cdq
# packed, gzipped, frozen and SCO LZH data
0 \037\036pipe/bin/gzip -cdq
0 \037\213pipe/bin/gzip -cdq
0
Re: printing problems
On: Thu, 1 Oct 1998 12:14:53 -0700 (PDT) Bradley Bell writes: I need to print to an HP Laserjet 5Si printer which is hooked up to a netware network, Can anybody point me to any resources on printing to netware printers? I've studied and tried every trick in the IPX- and Printing-HOWTO, and the instructions there are pretty insufficient when it comes to this problem. At the moment, I can almost print text files using nprint, but they come out staircased and sideways, and with no banner page. If anybody else has gotten this working, can I see your printcap and filter files? If nprint seems to send your file transparently to the user (at least it didn't convert LF-CR/LF) you can use a printcap which just calls a script for printing. Here is a sample entry for the smbprint command, change it accordingly: smb:lp=/dev/null:sd=/usr/spool/smb:sh:if=/usr/local/samba/smbprint You should probably chain it with magicfilter to provide automatic Postscript-PCL conversion if your printer do not nativly support postscript (I assume, you should let magicfilter print to remote printer smb on localhost with the above printcap entry). Torsten
Re: printing problems
thanks, I have gotten it to work, partly. Those files will help greatly. I've gotten it to work so far by downloading the new beta of the redhat printtools package and installing it with alien. It works, but is far from optimal. I still would like to get it to print the banner page, and I still have to figure out how to specify *which tray to be the paper source*. oh well, any clues greatly appreciated. -brad On Fri, 2 Oct 1998, Dirk Bonne wrote: Bradley Bell wrote: I need to print to an HP Laserjet 5Si printer which is hooked up to a netware network, Can anybody point me to any resources on printing to netware printers? I've studied and tried every trick in the IPX- and Printing-HOWTO, and the instructions there are pretty insufficient when it comes to this problem. At the moment, I can almost print text files using nprint, but they come out staircased and sideways, and with no banner page. If anybody else has gotten this working, can I see your printcap and filter files? Yeah, it works fine here. I use a combination of magicfilter (debian package) and nprint. We have a number of printers all hooked up to a host called ics1. I wrote a wrapper for nprint to make the authentification and to be able to send data to nprint by stdin. Attached are the makefiles, source, printcap, and a magicfilter file for one of the printers. My set up is like this: /etc/printer/ics1/.nwclient -- authentification (holds ICS1/username password) /Makefile -- rules to make a printer /tess-ps-1 -- one of the printers. /nw-printer.c -- source to generate a wrapper for each printer /tess-ps -- a wrapper binary generated by the makefile You will probably need to make small changes to Makefile and printcap. Also change a magicfilter generate filter to get it to use the wrapper. Hope the attachments help you on your way, Dirk
Re: Printing problems
Ian Lynagh wrote: Hi all! I was wondering if anyone could help me resolve a printing prblem I have got? I have an HP LaserJet 4L. If I do lpr textfile.txt then it works fine. However, printing in lyx appears to work fine, but nothing is printed :-( [snip] Save your money - someday it may be worth something. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Are you using the 'lpr' package or the 'lprng' package? I had the same problem when using the 'lprng' package. I switched back to the regular 'lpr' and the problem was solved. Its kind of a lame way to fix it but it works. If you need to keep 'lprng' then there is another package for HP printers called 'cti-ifhp' (I think) that might help. Mark. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Printing problems
In article [EMAIL PROTECTED], Mark Harrison m0192@ remove_thisozemail.com.au@ozemail.com.au writes Ian Lynagh wrote: I have an HP LaserJet 4L. If I do lpr textfile.txt then it works fine. However, printing in lyx appears to work fine, but nothing is printed :-( Are you using the 'lpr' package or the 'lprng' package? I was using lprng. I had the same problem when using the 'lprng' package. I switched back to the regular 'lpr' and the problem was solved. Its kind of a lame way to fix it but it works. If you need to keep 'lprng' then there is another package for HP printers called 'cti-ifhp' (I think) that might help. Using lpr seems to work :-) I'll try lprng with cti-ifhp and see if that works too. Thanks Ian -- Ian Lynagh - [EMAIL PROTECTED] http://home.sol.no/~balchen/igloo/ Discoveries are made by not following instructions. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Printing Problems
Installed lpr and aspfilter ... but when I try to print I get this message: 'waiting for lp to become ready (offline ?)' I have tried /dev/lp0 through 4 and it still says that the printer isn't ready when it is. Could it be because I am going from the printer port to the zip drive to the printer? Most likely yes... If you didn't compile ppa and lp as modules when you compiled your kernel it won't work. So, recompile kernel with ppa and lp as modules; when you want to print do: 'rmmod ppa ; insmod lp' and when you want to access the ZIPdrive 'rmmod lp ; insmod ppa' Kludgy, yes... there's a (experimental?) patch so that the printer and ZIP may coexist without you having to do rmmod/insmod all the time: http://www.cyberelk.demon.co.uk/parport.html I haven't tried this one myself... /Michael -- |Linux: Turn on...Tune in...Fork out... | |Michael Tempsch, member of Ballistic Wizards, TIP#088, POG#130 | | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | Cell.Phone:+46 705487554 URL:http://www.dtek.chalmers.se/%7Ed1temp | -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Printing Problems
Ok, it was the zipdrive causing the non-printing .. but now another small problem has started ... I am getting the stair stepping now... This prints but stairsteps: lp|Generic dot-matrix printer entry:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/lp:\ :tf=/etc/filter.pcl:\ :af=/var/log/lp-acct:\ :lf=/var/log/lp-errs:\ :pl#66:\ :pw#80:\ :pc#150:\ :mx#0:\ :rp=text:\ :sh: This is the apsfilter setup ... but doesn't print anything at all .. just keeps the files in the que: lp|lp2|bj200-letter-auto-mono|bj200 auto mono:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/bj200-letter-auto-mono:\ :lf=/var/spool/lpd/bj200-letter-auto-mono/log:\ :af=/var/spool/lpd/bj200-letter-auto-mono/acct:\ :if=/usr/lib/apsfilter/filter/aps-bj200-letter-ascii-mono:\ :mx#0:\ :sh: :rp=text:\ Any ideas what I have going wrong here? I have tried eveything I know from when I had this problem 15 months ago ... :\ Chad On Fri, 5 Sep 1997, Michael Tempsch wrote: Could it be because I am going from the printer port to the zip drive to the printer? Most likely yes... If you didn't compile ppa and lp as modules when you compiled your kernel it won't work. So, recompile kernel with ppa and lp as modules; when you want to print do: 'rmmod ppa ; insmod lp' and when you want to access the ZIPdrive 'rmmod lp ; insmod ppa' Kludgy, yes... there's a (experimental?) patch so that the printer and ZIP may coexist without you having to do rmmod/insmod all the time: http://www.cyberelk.demon.co.uk/parport.html I haven't tried this one myself... /Michael -- |Linux: Turn on...Tune in...Fork out... | |Michael Tempsch, member of Ballistic Wizards, TIP#088, POG#130 | | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | Cell.Phone:+46 705487554 URL:http://www.dtek.chalmers.se/%7Ed1temp | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Chad D. Zimmerman [EMAIL PROTECTED] Southwest Technology Development Institute New Mexico State University --- HP: http://dabcc-www.nmsu.edu/~chad/ DBP: http://dabcc-www.nmsu.edu/~chad/Debian/ LCAO: http://dabcc-www.nmsu.edu/~chad/Las_Cruces_Art/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Printing Problems
Fixed my own problem ... replaced apsfilter with magicfilter and now it prints fine... go figure :\ On Fri, 5 Sep 1997, Chad D. Zimmerman wrote: Ok, it was the zipdrive causing the non-printing .. but now another small problem has started ... I am getting the stair stepping now... This prints but stairsteps: lp|Generic dot-matrix printer entry:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/lp:\ :tf=/etc/filter.pcl:\ :af=/var/log/lp-acct:\ :lf=/var/log/lp-errs:\ :pl#66:\ :pw#80:\ :pc#150:\ :mx#0:\ :rp=text:\ :sh: This is the apsfilter setup ... but doesn't print anything at all .. just keeps the files in the que: lp|lp2|bj200-letter-auto-mono|bj200 auto mono:\ :lp=/dev/lp1:\ :sd=/var/spool/lpd/bj200-letter-auto-mono:\ :lf=/var/spool/lpd/bj200-letter-auto-mono/log:\ :af=/var/spool/lpd/bj200-letter-auto-mono/acct:\ :if=/usr/lib/apsfilter/filter/aps-bj200-letter-ascii-mono:\ :mx#0:\ :sh: :rp=text:\ Any ideas what I have going wrong here? I have tried eveything I know from when I had this problem 15 months ago ... :\ Chad On Fri, 5 Sep 1997, Michael Tempsch wrote: Could it be because I am going from the printer port to the zip drive to the printer? Most likely yes... If you didn't compile ppa and lp as modules when you compiled your kernel it won't work. So, recompile kernel with ppa and lp as modules; when you want to print do: 'rmmod ppa ; insmod lp' and when you want to access the ZIPdrive 'rmmod lp ; insmod ppa' Kludgy, yes... there's a (experimental?) patch so that the printer and ZIP may coexist without you having to do rmmod/insmod all the time: http://www.cyberelk.demon.co.uk/parport.html I haven't tried this one myself... /Michael -- |Linux: Turn on...Tune in...Fork out... | |Michael Tempsch, member of Ballistic Wizards, TIP#088, POG#130 | | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | Cell.Phone:+46 705487554 URL:http://www.dtek.chalmers.se/%7Ed1temp | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Chad D. Zimmerman [EMAIL PROTECTED] Southwest Technology Development Institute New Mexico State University --- HP: http://dabcc-www.nmsu.edu/~chad/ DBP: http://dabcc-www.nmsu.edu/~chad/Debian/ LCAO: http://dabcc-www.nmsu.edu/~chad/Las_Cruces_Art/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Chad D.. Zimmerman [EMAIL PROTECTED] Southwest Technology Development Institute New Mexico State University --- HP: http://dabcc-www.nmsu.edu/~chad/ DBP: http://dabcc-www.nmsu.edu/~chad/Debian/ LCAO: http://dabcc-www.nmsu.edu/~chad/Las_Cruces_Art/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Printing problems ...
On Mon, 7 Jul 1997, Eddie Katz wrote: When the kernel boots I have a message: lp0 at 0x0378, (irq = 7) Then when I try printing (LPRNG) I get an error message Status: Cannot open '/dev/lp1' - 'No such device or address', sleeping 10 at 17 Why is it trying /dev/lp1 since the kernel loaded /dev/lp0 ??? It sounds like you are using a 2.1.x kernel with a printcap file configured for an earlier kernel. /dev/lp1 used to be the (probably incorrect) default. This was changed to /dev/lp0 in 2.1.?? Check you /etc/printcap to be sure. Also if someone has a lpd.conf with one local printer and one remote as an exa mple I would appreciate it. I have no lpd.conf file. Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] AX.25:[EMAIL PROTECTED] http://www.primenet.com/~nielsen -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
