Sponsored Content
Top Forums UNIX for Dummies Questions & Answers how does cups recognize a new driver? Post 302235341 by vickenyon on Thursday 11th of September 2008 09:02:44 PM
Old 09-11-2008
how does cups recognize a new driver?

hi there,
i am attempting to recognize a network printer on my red hat box. i know the IP, i have procured the correct driver, however, CUPS (nor the add printer utility) doesn't recognize the driver nor the printer type. i am assuming this has to do with the location of the driver. can anyone tell me how to update my printer drivers so i can finally print? thanks a million.

ps. driver: Samsung-ML-3051ND-Postscript.ppd
printer: samsung ML-3051ND
 

10 More Discussions You Might Find Interesting

1. Solaris

SUNWglmr -- rasctrl environment monitoring driver for i2c or SCSI device driver ?

I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies

2. Programming

How to recognize that the server is currently unavailable?

hi all How to recognize that the server is currently unavailable? by programatically.give some example. am using fedora5 AMD cheers (2 Replies)
Discussion started by: munna_dude
2 Replies

3. Red Hat

Need a single printer driver added to CUPS

Just got an HP OfficeJet L7680 printer but there are no drivers for it in RHEL5. I just want to add the single driver without installing hplip 3.9.8. It's going to be connected with USB. Is this possible and if so how? (1 Reply)
Discussion started by: deloev
1 Replies

4. UNIX for Dummies Questions & Answers

Making a ppd driver for Minolta 3100 on CUPS/Ubuntu

Hello I have a Minolta QMS Magicolor 3100 printer. A driver is available (Minolta-magicolor_3100-Postscript.ppd) for Linux, installed using foomatic, but it does not work properly. The resolution is at it's lowest and a poor quality grainy print results. The printer works fine under Windows XP... (0 Replies)
Discussion started by: bwallum
0 Replies

5. UNIX for Dummies Questions & Answers

Query for printer driver in CUPS

I have a RHEL 4 (probably not important, but whatever) machine with a few dozen network printers set up in CUPS. I would like to replicate this on a second machine. With lpinfo I'm able to get the queue name and device information (socket://ipaddress or whatnot), but I haven't get figured out... (0 Replies)
Discussion started by: kknigga
0 Replies

6. UNIX for Dummies Questions & Answers

boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd

Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
3 Replies

7. Red Hat

Driver fails to recognize monitor type ...

Hello, Please help me if you could to resolve the problem with NVIDIA driver. I have Lenovo T61p. I installed RHAT6 Open Client and then downloaded and installed NVIDIA driver version 270.41.06. The product is Quadro FX 570. My laptop display type is LVDS. After installation everything works... (1 Reply)
Discussion started by: susja
1 Replies

8. Debian

CUPS Cannot recognize lp0

I am trying to print from Debian and receive the following message: "Unable to open device file"/dev/lp0": Permission Denied" The permissions for lp0 are 666. Advice and comments, please. :wall: Thanks (0 Replies)
Discussion started by: woofy613
0 Replies

9. Hardware

Difference between platform driver,codec driver and Machine driver

In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

10. Shell Programming and Scripting

How to recognize the Shell?

Hello All I am working on Red Hat Enterprise Linux Server release 5.1 when I logged on to the shell and then write echo $SHELL it shows me the result /bin/bash and when I write csh, the prompt changes and I feel that I am now working upon C shell but when I do echo $SHELL it shows me the... (9 Replies)
Discussion started by: adisky123
9 Replies
FOOMATIC-CONFIGURE(1)					      General Commands Manual					     FOOMATIC-CONFIGURE(1)

NAME
foomatic-configure - the main configuration program of the foomatic printing system. SYNOPSIS
foomatic-configure [OPTION]... foomatic-configure -n queuename [ -N description ] [ -L location ] [ -c con- nect ] [ -d driver ] [ -p printer ] [ --ppd ppdfile ] [ -s spooler ] [ -C [ sourcespooler ] source- queue ] [ -o option1=value1 -o option2 ... ] [ -q ] foomatic-configure -D -n queuename [ -s spooler ] [ -q ] foomatic-configure -R -n queuename [ -s spooler ] [ -q ] foomatic-configure -Q [ -s spooler ] [ -n queuename ] [ -r ] foomatic-configure -P [ -s spooler ] [ -n queuename ] [ -d driver ] [ -p printer ] [ --ppd ppdfile ] [ index ] foomatic-configure -X -p printer | -d driver | -p printer -d driver foomatic-configure -O foomatic-configure -h foomatic-configure --help DESCRIPTION
foomatic-configure is a program to set up and configure print queues for every known spooler (CUPS, LPRng, LPD, GNUlpr, PPR, PDQ. CPS, no spooler) and every valid printer/driver combo in the Foomatic database or every PPD file coming with PostScript printers. As RIP filter (Raster Image Processor, translation from PostScript to the native language of the printer) always foomatic-rip(1) will be used, except for PPD files of PostScript printers under CUPS or PPR, they will be used without RIP filter. It also comprises half of a programatic API for user tools: you can learn and control everything about the static properties of print queues here. With the sister program foomatic-printjob(1), you can do everything related to the print queue's dynamic state: submit jobs, and query, cancel, reorder, and redirect them. Options -n queuename Configure this print queue -N Name/Description Use this proper human-readable name/description -L Location Short phrase describing this printer's location -c connection Printer is connected thusly (ex file:/dev/lp0) -d driver Foomatic database name for desired printer driver -p printer Foomatic id for printer --ppd ppdfile PPD file, for example the one supplied by the manufacturer of a PostScript printer -s spooler Explicit spooler type (cups, lpd, lprng, pdq, ppr, direct) -o option=value Set the default of option to value -o option Turn on option by default -D Set this queue as the default queue (just give -n queuename) -R Remove this whole queue entirely (just give -n queuename) -C [ sourcespooler ] sourcequeue Copy sourcequeue from sourcespooler (or the current one if sourcespooler is not given) into the queue given by -n queuename (of the current spooler). -Q Query existing configuration (gives XML summary) -r List also remotely defined queues (CUPS only) -P [ index ] Get Perl dump of current configuration (as a Perl array named QUEUES, the first index is index, or zero if index is not given) -O Print XML Overview of all known printer/drivers (this shows also the Foomatic IDs of the printers) -X Print XML data for -p printer and/or -d driver object -q Run quietly Commands No commands, just options SEE ALSO
foomatic-printjob(1), foomatic-rip(1) EXIT STATUS
foomatic-configure returns 0 if no errors occurred. AUTHOR
Manfred Wassmann <manolo@NCC-1701.B.Shuttle.de> for the foomatic project using comments from the source. BUGS
foomatic-configure currently cannot handle printcap files in the lprng style. As lprng can use BSD style printcaps this is not much of a problem, as long as the GUI based print manager lprngtool is not used. The difference between those formats is, that BSD style requires continuation lines in printer definitions to be ended with a colon and the newline character to be escaped with a backslash. Lprng has no such restriction. To use a printcap file generated or edited with lprngtool with foomatic-configure it is necessary to add : to the end of all but the last line of every printer definition, just as shown below: #comment # primary printer name lp #alternate names |lp2|lp3 |Example of a printer :sd=/usr/spool/LPD/lp :rw:lp=/dev/lp:mx#100 : must be converted to: #comment # primary printer name lp |lp2|lp3 |Example of a printer :sd=/usr/spool/LPD/lp: :rw:lp=/dev/lp:mx#100: This manpage may be out of date. Foomatic Project 2002-01-06 FOOMATIC-CONFIGURE(1)
All times are GMT -4. The time now is 03:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy