The HP DRIVER USES HPLIP. ALL DRIVERS USE CUPS. IT ALL WORKS... AT 1PPM
I have added a screen-shot showing that the driver provided by HP.com is indeed HPLIP
(why wouldn't it be ?)
The interesting part is when booting the same hardware on Windoz 7 the printer responds as expected. Print starts nearly immediately and prints as advertised 17ppm.
So... The burning question is why not in Linux.
The HP driver came with a folder full of printer id files... ML-4050DMVps.ppd was one I didn't try. Does anyone know what the DMV stands for ? Looked on Bing.com, and didn't see anything remotely proper.
***** RESOLVED *****
I had removed CUPS this morning and tested. Seemed like the printer responded right away, and printed fast. I then reinstalled CUPS using "
sudo apt-get install cups" and it again went back to very slow. So this evening I used "
sudo apt-get purge cups" and tested a 5 page print... printer responded to print command within a second, and printed 5 pages with correct speed.
I'd say that for Network Printers CUPS is a mistake. HPLIP seems to be all that is required. Now the removal of CUPS may impact the use of other printers on this machine, but will find that out later. I don't print color very often, and so the LaserJet suits my needs more economically, and with much greater quality
Thank you to those providing their thoughts. Sadly none of them worked. Some tips on checking your Network Printer follows:
Network printer
Make sure the printer is turned on and connected to your network. In the case of a WLAN (wireless) printer the printer needs to be configured to use your wireless network.
Check the printer's configuration by printing a configuration page via the printer's front panel menus. This gives information about the IP address of the printer and about the protocols it supports (JetDirect/AppSocket, LPD, IPP, SMB/Windows, ...).
You can also find the printer's IP address via the configuration web interface of your router. Many routers you can configure that the printer always gets the same IP and you can also assign a host name.
To change the printer's configuration either use the printer's front panel menus or the printer's web configuration interface. To access this web interface, enter the IP address of the printer into the address or URL line of a web browser.
If your printer is supposed to connect via WLAN and it does not get an IP address, make sure that your WLAN is turned on and that the correct network name (SSID) and password are set by the front panel menus of the printer. If the printer has no front panel menus, you have to connct it with an ethernet cable first and configure the WLAN access through the web interface. On some HP printers there is WLAN connection but no ethernet connection. These you have to connect via USB and then use the hp-wificonfig tool from the hplip-gui package to configure them.
Set up the printer via system-config-printer ("Add" button). Wait around 15 seconds for the network scan (spinning icon must disappear). Usually you should select the default connection type as system-config-printer tries to find the best possibility. Generally use HP printers through the HPLIP connection, other printers preferably with DNS-SD connections (will continue to work whn the router changes the IP of the printer) and from the protocols use preferably AppSocket/jetDirect. The implementation of IPP in the printer's firmware has often bugs. Make sure the desired protocols and DNS-SD/mDNS/BonJour support are active in the printer's hardware configuration.
Open a terminal/console and run the commands:
$ ping <IP of the printer>
$ nmap <IP of the printer>
Replace "<IP of the printer>" by the printer's IP address. The first command checks whether you can access the printer through the network, the second shows which port numbers are used by the printer and through this which protocols are active (80: Has web interface, 139: SMB, 443: encrypted IPP or encrypted web interface, 515: LPD, 631: IPP, 9100: JetDirect/AppSocket). Install the "nmap" package if needed.
Run the commands:
$ /usr/lib/cups/backend/snmp
$ sudo /usr/lib/cups/backend/dnssd
The output shows whether the printers get found by CUPS or system-config-printer and with which device URIs and protocols.
Run the command
$ /usr/lib/cups/backend/snmp <IP of the printer>
if a printer does not get found by the simple "/usr/lib/cups/backend/snmp" call.
Find out if your printer gets detected by CUPS:
$ lpinfo -v
Run the commands:
$ avahi-browse -a -v -t -r
$ avahi-browse -a -v -c -r
These commands show whether your printer is visible via DNS-SD/mDNS/BonJour.
Run
$ ifconfig
$ route
to check general network health.
Attach the output of the above commands to the bug report.
Note that problems cannot only caused by CUPS but also by the kernel (package "linux"), HPLIP (package "hplip"), and several third-party printer drivers.