3Dconnexion Forum

The message looks af if xdrvlib.c was not compiled and the linker can't find the xdrvlib.o ??

Are there any other warnings or errors before the linker message?

Please try this:

add the following lines to xdrvlib.h
or in case you did not #define LINUX only this

Hi Absum,

have you had a look to our SDK for Unix/Linux? If you want to work with it I can send you some documentation for it.

Uta
3Dconnexion

This post could help ...

Hi Allen, our current driver for the 3D navigation devices 3DxWareUnix still supports the Spaceball 4000 FLX. This driver is a user space driver and needs X. There is an SDK for this driver which can be easily integrated into a 3D application running with X. The vendor information (IBM, HP) can not ...

Hi aplachta,

I will send you a beta version of 3DxWareUnix. We did some modification concerning how to identify the logged in user.

Please let us know if this one works on your machine.

Thanks,

Uta
3Dconnexion

Hello mrbond, the SpaceNavigator was designed as an additional device used with the left hand (if you are right handed) to navigate in 3D. For example with Maya, ProE or Google Earth (hopefully with 3D navigation device support under Linux soon). There is no support to move the cursor with the Space...

This output looks as if root is logged in and the driver starts properly.

It seems as is the driver can not identify that the user is logged in. The system tells the driver that root is logged in.

Are you using a DSF (distributed file system)?

Uta

Hi, I assume the start of the driver comes from the /etc/inittab? When a user logs in and the icon does not show up, please check in the process list whether the driver is running as root or as the logged in user. And let me know. :) Could you please disable the entry from the inittab and launch the...

Hello rob, the problem (device in /dev/bus/usb instead of /proc/bus/usb)described in previous posts of this thread is solved with the current driver. Which is version 1.2.0 and available from our download site . Are you using this version? Which error message do you get? Is it an error because of th...

The keyboard commands are application specific. Depends which application you are using the keyboard commands differ. Thus please refer to the documentation of your application for more details about keyboard commands.

My guess is that when I try to start it from inittab it doesnt know where my $HOME is and therefor the writing permissions. I don't know where inittab reads ENV variables or the export rules. If you have any clue it would be great. The driver does not read an ENV variable, but requests this info fr...

Is there any way to extend logging? I would like to see what he tries to do. You can enable the logging if you extend the launch of the driver with the following options: /etc/3DxWare/daemon/3dxsrv -d usb -debug -E This writes a logfile /tmp/3DxWare.log. It is not really extended, but shows a littl...

Hi Qvistarn, There's a small change in inittab from old version to new version: Old: 3dx:234:respawn:/etc/3DxWare/daemon/3dxsrv -d /dev/usb0 >/dev/null 2>&1 New: 3d:234:respawn:/etc/3DxWare/daemon/3dxsrv -d /dev/usb0 </dev>/dev/null 2>&1 I hope this is a typo from you :? , because the line i...

Hi Qvistarn, the driver tries to write a files .3dxrc in the $HOME directory of the logged in user. And fails. And: yes, it looks like a permission problem. I can not believe that the logged in user has no write permission to his own $HOME directory??? Please try our latest driver version (version 1...