4.4. Troubleshooting FAQ

4.4.1. When running ./ins_all I get a kernel mismatch error ?
4.4.2. When installing the driver when it tries to load myserial.o I get a segmentation fault ?
4.4.3. On my Laptop the driver seemed to install fine but I can't access my modem on /dev/modem ?

4.4.1. When running ./ins_all I get a kernel mismatch error ?

This means that the driver thinks that you don't have the appropriate kernel version, if you have a variant of the kernel (such as the one that has non-standard name) then you can still get the driver to work by loading up the file ins_all in a text editor and replacing all of the "insmod -m" commands with "insmod -f -m".

4.4.2. When installing the driver when it tries to load myserial.o I get a segmentation fault ?

This is caused by your computer trying to get Plug-and-Play to work with your modem. You can stop it doing this by going to your BIOS and setting an option which tells it not to do that. The settings name varies from BIOS to BIOS but is normally something like PnP OS.

4.4.3. On my Laptop the driver seemed to install fine but I can't access my modem on /dev/modem ?

This is often caused by the modem's device number clashing with that of PCMCIA, you can check if this is the case by entering the command,

[user@localhost]$ ls -l /dev/ | grep 254

You'll see the hsf0 device listed with the major number of 254, if any other device also has the major number of 254 it means there is a clash. You can fix this problem by loading up the ins_all file and change the line which reads "mknod /dev/cnxt c 254 64" to "mknod /dev/cnxt c 253 64".