Bugzilla – Bug 116516
Samsung ML-1510 printer is not detected on the first run
Last modified: 2005-09-13 14:40:31 UTC
My Samsung ML-1510 printer is not detected properly in the first run of yast printer. It gets listed, but when I click on continue a few times, it complains no manufacturer/model was selected. When I go back to the start screen of yast printer, select the printer again and click on continue a few times, it at least recognizes that this is s samsung printer, but it still doesn't know the model number. Will attach y2logs in a few seconds.
Created attachment 49625 [details] y2logs.tar.bz2
If you need any other info, please tell me.
Carl-Daniel, is your USB printer found by the CUPS backend? I.e. what results root@host# /usr/lib/cups/backend/usb It should detect and report your printer like on my workstation (also RC1): direct usb://HP/LaserJet%201220 "HP LaserJet 1220" "USB Printer #1" Michal, could you please have a look at the YaST log files. I don't see any obvious problem here.
direct usb://Samsung/ML-1510_700 "Samsung ML-1510_700" "USB Printer #1" direct usb:/dev/usblp1 "Unknown" "USB Printer #2" direct usb:/dev/usblp2 "Unknown" "USB Printer #3" direct usb:/dev/usblp3 "Unknown" "USB Printer #4" direct usb:/dev/usblp4 "Unknown" "USB Printer #5" direct usb:/dev/usblp5 "Unknown" "USB Printer #6" direct usb:/dev/usblp6 "Unknown" "USB Printer #7" direct usb:/dev/usblp7 "Unknown" "USB Printer #8" direct usb:/dev/usblp8 "Unknown" "USB Printer #9" direct usb:/dev/usblp9 "Unknown" "USB Printer #10" direct usb:/dev/usblp10 "Unknown" "USB Printer #11" direct usb:/dev/usblp11 "Unknown" "USB Printer #12" direct usb:/dev/usblp12 "Unknown" "USB Printer #13" direct usb:/dev/usblp13 "Unknown" "USB Printer #14" direct usb:/dev/usblp14 "Unknown" "USB Printer #15" direct usb:/dev/usblp15 "Unknown" "USB Printer #16" Well, the printer was found even in the first try. The problem was with Yast: - in the first try, it saw the printer, but couldn't associate vendor and device - in the second try, it saw the printer and associated the vendor, but not the device.
Unfortunately ;-) I don't have a printer for which YaST fails to find a matching PPD file. Michal, what should the workflow be in YaST (with new WizardHW) if it detects a printer but cannot find a matching PPD file?
Johannes, is it possible to teach YaST that my printer "Samsung ML-1510_700" is a "Samsung ML-1510"? Would it be possible to teach YaST to find the longest common prefix between the printer ID and and all supported printer IDs and suggest the best match?
Regarding comment #6 first question: YaST itself is reletively dumb regarding model name matching. What YaST does is a exact match for meaningful characters (*). E.g. blanks, '-' and '/' are ignored and case doesn't matter. All information is stored in the PPD files, see http://portal.suse.com/sdb/en/2004/03/jsmeix_print-einrichten-91.html "General information on setting up PostScript printers" how YaST finds matching PPD files. It does the same for non-PostScript printers. Regarding comment #6 second question: "longest common prefix" is totally impossible because it leads to wrong results. Often models with similar names understand the same printer language so that "longest common prefix" would work. But often models with similar names do not understand the same printer language so that "longest common prefix" would find wrong PPD files and lead to non-working printer setups. This is what I will strictly avoid: YaST does a semi-automated setup which doesn't work. Because then almost no customer will try out another model name (i.e. another PPD file) manually. Instead they do complain that "printing doesn't work". Summary: The one and only correct solution is: If YaST cannot find a matching(*) PPD file, then YaST must show the manufacturer and model selection screen so that the user can select a PPD file manually. This way the user knows that he selected a not perfectly matching model (i.e. a not perfectly matching PPD file) and if this doesn't work the user would try out other models (i.e. other PPD files).
fixed I reproduce it by delete my printer from ppd ;-) when you try edit unconfigured not known printer, sequence changes and you jump to the model dialog instead of global edit dialog
Thanks! Another question: How do I add my printer to a specific ppd file?
I don't have an experience, but google says: foomatic-ppdfile - create ppd file and after add your ppd to ppd database (in yast2 printer)
Thanks! I'll submit the changed ppd file to linuxprinting.org.
Regarding comment #9: 1. Find a PPD which works well for your printer. 2. Copy this PPD in /Usr/share/cups/model/ to a similar file name. 3. Edit in the new PPD the entries for *Manufacturer: *ModelName: *ShortNickName: *NickName: so that they match to your printer model name. 4. Restart YaST and see that it will work fine if you did the above steps correctly.
Hm. There is already a matching PPD (Samsung-ML-1510-gdi.ppd) for my printer, even using exactly the right model number. I wonder why it wasn't selected by YaST2.