TODO forever when life runs faster than you can afford

Trouble shooting

Αυτή η σελίδα υπάρχει και στα Ελληνικά.

Introduction

This page is meant to be a trouble shooting guide to Sakis3G script.

Before starting any trouble shooting session, please verify that your problem is not listed within known limitations (which means I do not plan fixing it), or within known problems (which implies that a fix should be expected within next months). Other than that, make sure you run latest Sakis3G version (available here) which includes all current fixes.

Maybe, one of the known solutions can help you:

• Check if your problem appears in F.A.Q. page.
• Unknown operator XXXXX
• Read here and here if your operator offers multiple APNs (FORCE_APN).

If none of the above instructions apply to your problem, you can attempt to trouble shoot (or even contribute your solution).

Contents

• Become super user
• Enable debug mode
• Record a log
• Report to author

Become super user

Unless problem resides in the procedure Sakis3G script uses to acquire root privileges, it is highly recommended to become super user prior to initiating debug session. This way you can be sure that environment is maintained within nested (calls to itself) Sakis3G calls. This is essentially required if you are using alwayssudo configuration variable.

Normal distributions (Debian)

$ su
Password:
#


Sudo distributions (Ubuntu)

$ sudo bash
Password:
#


(Back to contents)

Enable debug mode

Sakis3G script provides a way to enable debug output (aka. debug mode). To enable debug mode, you need to set DEBUG configuration variable. You can follow one of the following methods to enable DEBUG variable:

• Permanently enable it:
  
# vi -c "1,$ s/^#DEBUG=/DEBUG=/g" -c ":wq" sakis3g

• Enable it for current shell session:
  
# export DEBUG=on

• Enable it on-demand on command line:
  
# DEBUG=on sakis3g connect


In order to modify Sakis3G script, administration privileges may be required (see previous section).
(Back to contents)

Record a log

Executing Sakis3G script with no command line arguments, while DEBUG configuration variable is enabled, will lead into huge amount of output that will eventually exceed your terminal's history buffer. It is therefore required that you redirect debug output to a log file, so that you can easily review it later. Moreover, in order to avoid UI related output, it is recommended that you use "connect" command line argument. Use following command to store output to a log file:


# DEBUG=on sakis3g connect 2>&1 | tee sakis3g.log


This will lead into sakis3g.log containing a copy of what you are going to witness on your terminal.
(Back to contents)

Report to author

If output generated, failed to lead you into a safe conclusion on what your problem is, or, if you found a permanent solution to that problem that could help others too (read contributing section on this page), then you can send an email to Sakis3G author. My email address resides on "tel4u.gr", while my account name (local part) is "sakisd".

If you need me to help you, it would be convenient to also attach output of the following commands (after connecting modem and before executing Sakis3G script):


# dmesg
# uname -a
# /sbin/modinfo option
# /sbin/modinfo usbserial
# lsmod
# lsusb -v
# ls -l /usr/sbin/usb*modeswitch*
# ls -l /etc/usb*modeswitch*
# ls -l /etc/udev/rules.d


Finally, in order to make sure that I will read your email, please include "[sakis3g]" string into your email's subject. This will lead my email rules to not discard your email as spam/junk.
(Back to contents)