I'm going crazy here. My Samsung ML 1510 printer Just Worked (tm) with
whatever distro I was using when I first got it, and has gone on Just
Working through changes of machine, distro (I think) and version. I'm on
whatever is currently stable (Lenny?).

Yesterday I fiddled with the settings in kde control panel to try to make
the printer accessible over the LAN to my sprog's windoze (<ptui!>)
machine and borked printing locally. Attempting to get things working
again I planned to delete and reinstall the printer ... well the first bit
went OK but the gui add-printer wizard doesn't see any locally-attached
printer. http://localhost:631/ doesn't see any local printers either.

A bit of STFW suggested installing printconf, which says:

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

Configuring Samsung ML-1510 on usb:/dev/usb/lp0 with splix driver as queue
"ml1510".

There is neither a custom PPD file nor the driver database entry contains
sufficient data to build a PPD file.
    
Reloading Common Unix Printing System: cupsd. If printconf was unable to
install all of your printers, please visit http://www.linuxprinting.org/
for printer information and support from fellow users.

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

find -xdev / -name '*.ppd*'
finds a load of drivers in
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-QL-5100A-lj4dith.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2151NPS-Postscript.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2150PS-pxlmono.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-7000N-lj5gray.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-85-ljet4.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-7300-pxlmono.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-85-lj4dith.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2150-pxlmono.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2151N-ljet4d.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-1750-pxlmono.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-1450PS-lj4dith.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2151NPS-ljet4d.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-4500-gdi.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2150PS-ljet4d.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-7300N-ljet4.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2010-gdi.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-7000-lj5gray.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-4600-pxlmono.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-QL-5100A-ljet4.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-1430-gdi.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2551N-lj4dith.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2150PS-Postscript.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-1250-lj5gray.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2152W-pxlmono.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-4600-lj4dith.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-2550-lj4dith.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-1000-gdi.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-1010-gdi.ppd.gz
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/Samsung-ML-6000-ljet4.ppd.gz

 - note, no 1510 - so how did it ever work?

There's this splix driver, but no indication how to configure and use this.

I am completely out of my depth here! Any help?


-- 
John Stumbles

I used to be forgetful but now I ... um ....

On Mon, 02 Nov 2009 23:35:43 +0000, John Stumbles wrote:

> Yesterday I fiddled with the settings in kde control panel to try to
> make the printer accessible over the LAN to my sprog's windoze (<ptui!>)
> machine and borked printing locally. Attempting to get things working
> again I planned to delete and reinstall the printer ... well the first
> bit went OK but the gui add-printer wizard doesn't see any
> locally-attached printer. http://localhost:631/ doesn't see any local
> printers either.
>
Can't help with the ML-1510 PPD, but FYI CUPS is installed in Fedora 10 
with 'publish shared printers on this system' turned off, which stops the 
CUPS server from listening on 631 entirely: listening on localhost is 
disabled as well as listening on external network interfaces. So, after 
installing a current version this would stop localhost:631 from working, 
though it doesn't affect the Gnome CUPS configuration tool.


-- 
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |

John Stumbles  writes:

> A bit of STFW suggested installing printconf, which says:
>
> """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
>
> Configuring Samsung ML-1510 on usb:/dev/usb/lp0 with splix driver as queue
> "ml1510".
>
> There is neither a custom PPD file nor the driver database entry contains
> sufficient data to build a PPD file.


>  - note, no 1510 - so how did it ever work?
>
> There's this splix driver, but no indication how to configure and use this.


well, for a start, unles debian has changed since I used it ten years ago
...


apt-get install splix   :-)


then restart the cups daemon

you should then find that cups/printconf will have a ppd for the ML1510
listed when you try to reinstall your printer.


Good luck!

atb


Glyn

In article <hcnuq7$nv4$2@localhost.localdomain>,
	Martin Gregorie wrote:

> Can't help with the ML-1510 PPD, but FYI CUPS is installed in Fedora 10 
> with 'publish shared printers on this system' turned off, which stops the 
> CUPS server from listening on 631 entirely: listening on localhost is 
> disabled as well as listening on external network interfaces. So, after 
> installing a current version this would stop localhost:631 from working, 
> though it doesn't affect the Gnome CUPS configuration tool.

Debian has it listening only on localhost:

$ netstat -tln |grep :631
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN
tcp6       0      0 ::1:631                 :::*                    LISTEN

-- 
Paul Martin

On 3 Nov 2009, Glyn Millington told this:
> apt-get install splix   :-)

As a side note, all splix ever did for me was coredump (although that's
better than the Samsung-supplied proprietary CUPS filter, which ate all
memory, or tried to, and never printed a thing).

My ML-2250 works perfectly well with the ordinary pxlmono GhostScript
driver: you might try that.

On Thu, 05 Nov 2009 00:22:54 +0000
Nix  wrote:

> On 3 Nov 2009, Glyn Millington told this:
> > apt-get install splix   :-)
> 
> As a side note, all splix ever did for me was coredump (although that's
> better than the Samsung-supplied proprietary CUPS filter, which ate all
> memory, or tried to, and never printed a thing).
> 
> My ML-2250 works perfectly well with the ordinary pxlmono GhostScript
> driver: you might try that.

That's a PCL driver isn't it? I think the OP's 1510 is one of the
cheaper Samsungs which is more like a Winprinter. I've got a 1210 which
uses a gdi driver; I don't have (many) problems with it, except that it
doesn't show up as a supported model if I try to add it via CUPS' web
interface and I have to use foomatic-gui or whatever. The OP's 1510 is a
different beast again. Looks like I'm fortunate to have the older model
:-/.

-- 
TH * http://www.realh.co.uk

On Mon, 02 Nov 2009 23:35:43 +0000, John Stumbles wrote:

> I'm going crazy here....

Thanks to everyone who replied. 

In the end I found out what had changed in /etc from my rsync snapshot
backup system, restored the changed files and rebooted and it worked again. 

Not an ideal solution as I haven't really learned anything new, but
sometimes life's too short :-|

I found that there was (and after restoring it, again is) an
/etc/cups/ppd/Samsung.ppd which presumably makes it work, though where it
came from and why it's not with the others in
/usr/share/ppd/foomatic-rip/openprinting-gs-builtin/Samsung/ I don't know).


-- 
John Stumbles

Press any key to continue or any other key to exit