I took a look that the Foomatic database on linuxprinting.org and after
going down the rabbit hole, It looks like this printer probably will
require a Brother supplied driver that doesn't currently look to have
been built for Solaris. You might take a look at
http://solutions.brother.com/linux/en_us/index.html for information on
their open source drivers.
-Norm
Alok Aggarwal wrote:
>
> On Thu, 17 Jan 2008, Norm Jacobs wrote:
>
>> From the message that you are supplying, it sounds like you have your
>> system misconfigured to go directly to the printer and I don't know
>> what protocol (I am assuming that the printer is at 192.168.1.103).
>> You might try to use presto with the network attached printer
>> detection support now in Solaris. If you enable the SNMP based
>> printer discovery service
>> (svc:/network/device-discovery/printers:snmp) via the command line
>> (svcadm) or GUI (start->administration->services), magic should happen.
>> # svcadm enable svc:/network/device-discovery/printers:snmp
>
> Yep, 192.168.1.103 is the printer and it changes
> every time the printer reboots and re-acquires a
> new DHCP address. I just enabled this
> service and viola! The brother printer identified itself
> as being MFC-420CN (instead of MFC-440CN) which seems
> plausible. And, it selected the SUNWfoomatic(S):Foomatic/hl7x0
> driver for it.
>
>> The SNMP based network attached printer discovery service probes the
>> network for printers every 60 seconds (configurable). As it finds
>> new printers, it adds them to the HAL device tree, which causes the
>> OSPM (part of your JDS/GNOME desktop session) to prompt you create a
>> queue with a pre-filled "Add Printer" dialog. Since I don't know for
>> certain if this printer supports SNMP, I don't know if it will be
>> autodetected. Also, since we don't appear to have a PPD file for
>> that exact model and I don't know what PDLs it supports, I can't
>> steer you to a substitute make/model to select. FWIW, I know that
>> some Brothers printers purposefully respond to SNMP get requests for
>> HP private mib extensions effectively pretending to be an HP LaserJet
>> printer. I would guess that choosing one of the HP LaserJet
>> mfg/models that closely resembles your printer might work. At any
>> rate, If you get a chance, I would be interested in the information
>> that goes into the HAL device tree for your printer. You can
>> retrieve it with
>> zsh$ for udi in $(hal-find-by-capability --capability printer) ;
>> do ; lshal --show $udi --long ; done
>
> Here's the HAL device that was created -
>
> udi = '/org/freedesktop/Hal/devices/network_attached/LLADDR_008077A8FDBA'
> printer.commandset = {'HBP', 'BRPJL'} (string list)
> info.product = 'MFC-420CN' (string)
> info.callouts.add = {'hald-probe-network-printer'} (string list)
> info.udi =
> '/org/freedesktop/Hal/devices/network_attached/LLADDR_008077A8FDBA'
> (string)
> printer.product = 'MFC-420CN' (string)
> printer.vendor = 'Brother' (string)
> printer.serial = 'BROD6F549369' (string)
> printer.device = 'socket://192.168.1.101:9100' (string)
> network_device.address = '192.168.1.101' (string)
> info.capabilities = {'printer', 'network_device'} (string list)
> info.category = 'printer' (string)
> info.parent = '/org/freedesktop/Hal/devices/network_attached' (string)
>
> So, it looks the printer discovery service created a
> print queue for me at 192.168.1.101:9100. However, if
> I try sending a print job to this queue, it says -
>
> request id is 192.168.1.101:9100-152 (1 file(s))
>
> but nothing ever happens. What am I missing?
>
> Thanks,
> Alok
