FAQ for Connector settings

Connector FAQ

August 2002 by Jakub.

Installation stops with error - ldconfig not found

Seems the command ldconfig is not part of out-of-box Zaurus. Will get fixed in future releases.
Connector doesn't connect to my phone. The log says error: Cannot get socket

This can be due to the affix_rfcomm module not being loaded. Try modprobe affix_rfcomm.
Another way is to change the /etc/pcmcia/affix_uart.conf from
```
device "affix_uart_cs"
class "affix_uart" module "affix_uart_cs"
```
to
```
device "affix_uart_cs"
class "affix_uart" module "affix","affix_rfcomm","affix_uart_cs"
```
Cannot open device /dev/bty0

Firstly, Zaurus doesn't use devfs. Secondly, Zaurus seems to re-create the /dev/ directory after restart. Future versions of Connector should take care of this. For current versions create the devices manually as
```
mknod -m 0644 /dev/bty0 c 60 0
mknod -m 0644 /dev/bty1 c 60 1
mknod -m 0644 /dev/bty2 c 60 2
mknod -m 0644 /dev/bty3 c 60 3
mknod -m 0644 /dev/bty4 c 60 4
...
```

Cannot get connection with the default settings

The settings in the provided files are mine own. They must get customized by editting the files
```
/etc/ppp/peers/DUN
/etc/chatscripts/DUN
```
Use your operator's specific settings for these! You can use the pppconfig utility to make this easier. If you already have working connect script (e.g. for the infrared or cable) just switch from default to user-defined and type in something like
```
pppd /dev/bty%l call YOUR_SCRIPT &
```

Last updated on Wednesday, 15-Jan-2003 21:25:29 UTC. You are the [an error occurred while processing this directive]. visitor on our pages.