My comments starts with "GL>"
-----Original Message-----
From: Tim Waugh [mailto:twaugh@redhat.com]
Sent: Wed 5/5/2010 4:33 AM
To: George Liu
Cc: system-config-printer-devel@lists.fedorahosted.org; Till Kamppeter; Bin Li
Subject: RE: Tagging PPD package with DeviceID.
Hi George,
On Tue, 2010-05-04 at 17:26 -0700, George Liu wrote:
> I installed Fedora 13 Beta and tried out System-Config-Printer.
> "lpinfo --include-schemes=dnssd,snmp -l -v" found the following
> printers. None of the printers support 1284DeviceID MIB.
> * One with Bonjour support, (I guess CUPS retrieves device-id using
> Bonjour),
> -------------------------------------------------------------------------------------
> Device: uri = dnssd://RICOH%20Aficio%20MP%
> 20C3500._pdl-datastream._tcp.local/
> class = network
> info = RICOH Aficio MP C3500
> make-and-model = RICOH RICOH Aficio MP C3500
> device-id = MFG:RICOH;MDL:Aficio MP C3500
> location =
Unfortunately from the way this device-id is constructed I can tell that
this device does not correctly advertise its IEEE 1284 Device ID over
DNS-SD. Instead of using the 'usb_MFG' and 'usb_MDL' keys (which *must*
correspond with the IEEE 1284 Device ID 'MFG' and 'MDL' fields when
present), the printer is using either the 'product' or 'ty' field to
specify the printer's entire make-and-model name. This is not an IEEE
1284 Device ID.
GL> Can you elaborate? Here's a 1284DeviceID retrieved through Ricoh private MIB.
"MFG:RICOH;CMD:PJL,RCS,PCL,PCLXL,POSTSCRIPT;MDL:Aficio MP C3500;STS:10072/10033,0;CLS:PRINTER;DES:RICOH Aficio MP C3500;"
MFG field and MDL field matches, right?
When building PPD package, which part of the 1284DeviceID string is supposed to be used to tag the package?
> * Another without Bonjour support, and CUPS found it using SNMP.
> Device: uri = socket://172.30.4.243
> class = network
> info = RICOH Aficio MP 2550
> make-and-model = RICOH Aficio MP 2550
> device-id =
> location =
I think this is our best chance for getting an IEEE 1284 Device ID. As
you noted, neither this nor the other printer support the Printer MID.
But do they advertise their IEEE 1284 Device IDs via SNMP on another
OID?
> "Search for a printer driver to download" does not return any drivers.
George, that's something different. That goes directly to
openprinting.org, and isn't to do with "automatic printer driver
download".
GL> I'm confused. Does s-c-p has two mechanisms to find a driver? Openprinting.org and Fedora repository (with package tagged with deviceiD?)
> I then tried to build pycups and system-config-printer (Thanks for the
> instruction).
> I run the build version, and it gave me some log messages.
> Got PPDs
> No ID match for device socket://172.30.4.243:9100:
> <manufacturer>RICOH</manufacturer>
> <model>Aficio MP 2550</model>
> <description>RICOH Aficio MP 2550</description>
> <commandset></commandset>
> Using textonly.ppd (status: 3)
> Will fetch ppd? 0
> Got PPDs
> No ID match for device socket://172.30.4.173:9100:
> <manufacturer>RICOH</manufacturer>
> <model>Aficio MP C3500</model>
> <description>RICOH Aficio MP C3500</description>
> <commandset></commandset>
> Using textonly.ppd (status: 3)
> Will fetch ppd? 0
>
>
> <manufacturer> and <model> tag for both printers are correct. There's
> no <deviceid> tag for either of them. Is it right?
Those are XML versions of attempted Device ID look-ups. It's written
confusingly (fixed in git). Without the full '--debug' output it's hard
to say exactly what's going on.
Here's what I'd like you to do:
1. Apply the updates (click the star in the GNOME panel's notification
area, or run 'yum update'). After doing this, 'rpm -q cups' should say
cups-1.4.3-6.fc13.$arch.
2. Disable the firewall (su -c '/sbin/service iptables stop')
3. In the system-config-printer git repository you checked out, run:
./check-device-ids.py
Show me the output.
GL>
Skipping serial:/dev/ttyS1?baud=115200, insufficient data
Sending SNMP request to 172.30.4.243 for device-id
Skipping socket://172.30.4.243, insufficient data
Skipping parallel:/dev/lp0, insufficient data
Skipping lpd://172.30.4.228/, insufficient data
Skipping serial:/dev/ttyS0?baud=115200, insufficient data
Sending SNMP request to 172.30.4.14 for device-id
Skipping socket://172.30.4.14, insufficient data
Sending SNMP request to 172.30.4.156 for device-id
Skipping socket://172.30.4.156, insufficient data
Sending SNMP request to 172.30.4.173 for device-id
Skipping socket://172.30.4.173, insufficient data
Sending SNMP request to 172.30.4.207 for device-id
Skipping socket://172.30.4.207, insufficient data
Sending SNMP request to 172.30.4.48 for device-id
Skipping socket://172.30.4.48, insufficient data
Installing relevant drivers using session service
Fetching driver list
├── RICOH imagio MP C2800 (socket): MFG:RICOH;MDL:imagio MP C2800;CMD:PJL,RCS,R00;
│ (No drivers)
├── RICOH Aficio SP C420DN (socket): MFG:RICOH;MDL:Aficio SP C420DN;CMD:PJL,RCS,PCL,PCLXL,POSTSCRIPT,POSTSCRIPT,PCL,PCLXL;
│ (No drivers)
The very latest Ricoh devices supports port monitor MIB (like SP C420DN shown here)
Thanks,
Tim.
*/