Must that node be created from outside the script or is this a failure of the script (or is it unnecessary using USB?)?įor the USB HASP hardlock, you don't have to create a device node, since you don't need this for USB. This is an addition to my previouus message - in the meantime I also found out that the installation script fpr the dongle did not create a device node (well at least nothing calles /dev/Hardlock), although run as root. (2) half a line of comment seems to be missing in the same startup script) (1) an export command for a shell PATH variable pointing to a library is commented out in the startup script as downloaded. (There are two suspicious things in my download: The aksusbd reports to /var/log/messages correctly (I didn't install the parport driver but that's not needed for the usb dongle - right?).Is this still the dongle driver problem as reproted earlier in this forum or has something else gone wrong? ![]() Rights can't be the source of the problem (as starting BV as root doesn't help). ![]() The /tmp/.aksusb domain socket is created. The Hardlock is known to the system (lsusb command reveals the alladin hardlock). ![]() Although installation seems to be succesful and is completed with no error reported Brainvoyager can't find the hardlock. I tried to install and run BV QX RC3 on a Suse 8.2 System. Topic: Problem finding USB hardlock under Linux ![]() Profile | register | preferences | faq | search Problem finding USB hardlock under Linux - BrainVoyager Discussion Forum
0 Comments
Leave a Reply. |