Marsi4eg
Regular Contributor
I have already written about usb print server 'death' after some time of printer's inactivity. (Asuswrt-Merlin 378.52 is available)
Re-plugging a printer helps but only for ONE printing. (need to replug every time I need to print).
After a few days even replugging doesn't help. Everytime there is an error that the printer is busy, Print server stucks with the name of connected printer even if it's powered off long time ago.
Also the print server dies if no printer was connected and the uptime is long. New connections just doesn't work.
This is NOT a compatibility issue! Print server works fine and IS compatible with my printer after restarting the router. And something goes wrong (it becames incompatible?) after some time.
I have rolled back my second router (N16) to 374.43 because I clearly remember that all was fine with that firmware. And that's true - no issues with 374.43 firmware.
Tested for 4 days and everytime I could print. The printer correctly detects, every printing task is logged reporting current printer state. Works like a clock. The log is beautiful:
The other interesting thing that ASUS Device Discovery tool shows that my AC66U have a connected printer even if it does not. At the same time, WebUI of router doesn't show any connected device. Looks like print server is really getting stuck in some state and cannot recognize when the new printer or the same one is connected again, and reports 'Device is busy' error.
So please RMerlin, I know that you cannot test this properly by your side - I could help in testing. Maybe you could take a look and merge some code from the older release, to make printserver work again. I already were making tests for more than two weeks to figure something out - and I think I did this... the next step is to look into the code but I'm not a good programmer
Re-plugging a printer helps but only for ONE printing. (need to replug every time I need to print).
After a few days even replugging doesn't help. Everytime there is an error that the printer is busy, Print server stucks with the name of connected printer even if it's powered off long time ago.
Also the print server dies if no printer was connected and the uptime is long. New connections just doesn't work.
This is NOT a compatibility issue! Print server works fine and IS compatible with my printer after restarting the router. And something goes wrong (it becames incompatible?) after some time.
I have rolled back my second router (N16) to 374.43 because I clearly remember that all was fine with that firmware. And that's true - no issues with 374.43 firmware.
Tested for 4 days and everytime I could print. The printer correctly detects, every printing task is logged reporting current printer state. Works like a clock. The log is beautiful:
Code:
May 10 23:02:55 kernel: usb 1-1: new high speed USB device using ehci_hcd and address 3
May 10 23:02:55 kernel: usb 1-1: configuration #1 chosen from 1 choice
May 10 23:02:55 kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3272
May 10 23:02:55 kernel: drivers/usb/class/usblp.c: usblp0 Device ID string [59]='MFG:Samsung;CMD:SPLC;MDL:CLP-300;CLS:PRINTER;STATUS:BUSY;' // warm-up
May 10 23:04:00 kernel: drivers/usb/class/usblp.c: usblp0 Device ID string [59/max 1552]='MFG:Samsung;CMD:SPLC;MDL:CLP-300;CLS:PRINTER;STATUS:IDLE;' // sent first task
May 10 23:04:00 kernel: drivers/usb/class/usblp.c: Parsing USBLPID...
May 10 23:11:02 kernel: drivers/usb/class/usblp.c: usblp0 Device ID string [59/max 1552]='MFG:Samsung;CMD:SPLC;MDL:CLP-300;CLS:PRINTER;STATUS:IDLE;' // second task
May 10 23:11:02 kernel: drivers/usb/class/usblp.c: Parsing USBLPID...
May 10 23:17:14 kernel: drivers/usb/class/usblp.c: usblp0 Device ID string [59/max 1552]='MFG:Samsung;CMD:SPLC;MDL:CLP-300;CLS:PRINTER;STATUS:IDLE;' // third etc.
May 10 23:17:14 kernel: drivers/usb/class/usblp.c: Parsing USBLPID...
May 10 23:18:28 kernel: drivers/usb/class/usblp.c: usblp0 Device ID string [59/max 1552]='MFG:Samsung;CMD:SPLC;MDL:CLP-300;CLS:PRINTER;STATUS:IDLE;'
May 10 23:18:28 kernel: drivers/usb/class/usblp.c: Parsing USBLPID...
May 10 23:40:02 kernel: usb 1-1: USB disconnect, address 3 // powered off
The other interesting thing that ASUS Device Discovery tool shows that my AC66U have a connected printer even if it does not. At the same time, WebUI of router doesn't show any connected device. Looks like print server is really getting stuck in some state and cannot recognize when the new printer or the same one is connected again, and reports 'Device is busy' error.
So please RMerlin, I know that you cannot test this properly by your side - I could help in testing. Maybe you could take a look and merge some code from the older release, to make printserver work again. I already were making tests for more than two weeks to figure something out - and I think I did this... the next step is to look into the code but I'm not a good programmer
Last edited: