I installed the package through unmenu and followed the instructions in the main p910nd thread for configuring the rest.

I have the port and everything setup on Windows according to the thread and have tried to print to the server however nothing is showing up in the syslog so I clearly don't have the server setup correctly. The only thing that doesn't seem to be in order is the dev/usblp* folder. In my dev folder I have: "/dev/usb/lp0" & "/dev/usb/lp1"

Is the fix as simple as creating usblp0 in the dev folder and symlinking it to the appropriate unraid created directory (ie. "dev/usb/lp0")?

 

Relevant Information:

 

I am running unraid v5.0.5

unMenu Version 1.6 Revision: 278

The printer is a Canon Pixma MP830.

 

I installed the package through unMenu's package manger setting:

-the printer port as usblp0

-Bidirectional support YES

-RC script Installed

 

I did not add the two lines from Dase's instructions to my go file as I did not think I would need them since I installed the package through unmenu.

 

Here is my syslog output from connecting the printer (you can find the full log attached below). I believe usblp1 is the memory card reader or something along those lines since underneath it says "Direct-Access Canon MP830Storage"

Jun 29 16:44:58 VOID kernel: usb 1-5: new high-speed USB device number 4 using ehci-pci (Drive related)

Jun 29 16:44:58 VOID kernel: usblp 1-5:1.1: usblp0: USB Bidirectional printer dev 4 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1713 (Drive related)

Jun 29 16:44:58 VOID kernel: scsi8 : usb-storage 1-5:1.2 (Drive related)

Jun 29 16:44:58 VOID kernel: usblp 1-5:1.3: usblp1: USB Bidirectional printer dev 4 if 3 alt 0 proto 2 vid 0x04A9 pid 0x1713 (Drive related)

Jun 29 16:44:59 VOID kernel: scsi 8:0:0:0: Direct-Access    Canon    MP830Storage    0107 PQ: 0 ANSI: 2 (Drive related)

Jun 29 16:44:59 VOID kernel: sd 8:0:0:0: Attached scsi generic sg8 type 0 (Drive related)

Jun 29 16:44:59 VOID kernel: sd 8:0:0:0: [sdi] Attached SCSI removable disk (Drive related)

 

These are the commands and their outputs that were suggested in the original thread:

 

strings /boot/packages/p910nd-0.93/p910nd | grep subsys

/var/lock/subsys/p910%cd

 

ls -ld /var/log/subsys

drwxrwxrwx 2 root root 40 2014-06-29 17:31 /var/log/subsys/

 

ls -ld /var/lock/subsys

drwxr-xr-x 2 root root 0 2014-06-29 17:31 /var/lock/subsys/

 

ls -l /var/lock/subsys

total 0

-rw-rw-rw- 1 root root 0 2014-06-29 17:31 apcupsd

-rw-r--r-- 1 root root 0 2014-06-29 17:31 p9100d

ls -l /dev/usblp*

/bin/ls: cannot access /dev/usblp*: No such file or directory

 

ps -ef | grep p910

root      2243    1  0 17:31 ?        00:00:00 /usr/sbin/p9100d -f /dev/usblp0      -b

root      3460  3292  0 17:33 pts/0    00:00:00 grep p910

 

 

Thanks for the help,

-Chris

syslog-2014-06-29.txt

Anyone have some pointers? I would rather not do this through trial and error if it can be avoided. From what I understand about unraid it unpacks a fresh copy of the kernel at every boot so would creating a new folder in /dev/ even work?

Anyone have some pointers? I would rather not do this through trial and error if it can be avoided. From what I understand about unraid it unpacks a fresh copy of the kernel at every boot so would creating a new folder in /dev/ even work?

You are correct about something in /dev/ not surviving reboots.    The only way to do something like that is to add the appropriate commands to your 'go' file to create on each boot. 

 

As to whether it will help with your particular problem I have no idea.

I have tried configuring it in unmenu as usb/lp0 & lp1 to see if that would fix the issue and still no dice. Nothing from p910nd is showing up in the syslog however as I noted above the process is indeed running.

I checked the print processor settings and it is set to use raw so that isn't the issue either.

I'm not sure what else to check, does anyone have this successfully working on 5.0.5?