Troubleshooting
From Usb-adsl-modem-manager
Contents |
Overview
Problems can be spit into distinct Area's
- Manager doesn't start
- Modem Not Detected
- Firmware Not Loaded
- Firmware Extraction Problems
- Modem Not Synchronizing
- Modem can't Authenticate
- Can't see internet (modem authenticated)
Manager Doesn't Start
The manager should have a presence in your Tray
The best way to get any debug up is to open a Terminal, and enter
usbadslmodemmanager
This should give you some error messages
If you get the Error we are not alone!
Then this means that your trying to start a second Manager
kill all the running ones : like this
pkill usbadslmodemmanager
then try again
Other error's should be understandable, if not get on the forums or email me
Old versions (pre-0.5.0) may give you this Error
trayicon.so: wrong ELF class: ELFCLASS32 then your probably running the 32bit install on a 64bit Version of Ubuntu you can fix this by downloading a i686.deb version from the releases directory
Modem Not Detected
If when you plug the modem in, the Tray icon stays at Modem not detected, two thing my be the problem
- USB port has no IRQ
- Modem is not supported
IRQ is assigned by your Bios, some bioses have a Assign IRQ to USB option
The current supported modems are : Speedtouch 330 v0-4 Any other modems won't work
Firmware Not Loaded
This happens when either
- An firmware extract went wrong
- Conflicting firmware files in /lib/firmware
- Your trying to run the i386 package on a 64bit (i686) Install (go get the right DEB package)
If the firmware extract went wrong simply unplug and replug the modem, then if it doesn't prompt you right click on the tray icon and choose re-extract firmware
If this isn't helping then its likely that a previous attempt to get the modem working has left firmware files in the hotplug firmware directory
you can have a peek at what happens when your trying to load the Firmware by entering (in a terminal)
dmesg
or
more /var/log/syslog
so firstly you can only delete files in /lib/firmware as root
sudo su cd /lib/firmware ls -l
now you should see
-rw-r--r-- 1 root root 991 2007-06-02 14:46 speedtch-1.bin -rw-r--r-- 1 root root 762650 2007-06-02 14:46 speedtch-2.bin
any other .bin files are either : other devices or conflicting files
now be careful and only remove files you suspect to be other speedtouch bin files
you may also find more of them in the directories within /lib/firmware/
drwxr-xr-x 4 root root 4096 2007-03-13 23:44 2.6.17-10-generic drwxr-xr-x 4 root root 4096 2007-04-11 23:16 2.6.17-11-generic drwxr-xr-x 4 root root 4096 2007-04-28 15:08 2.6.20-15-generic drwxr-xr-x 4 root root 4096 2007-05-28 19:33 2.6.20-16-generic
if you CD into these
cd /usr/lib/2.6.20-16-generic link titl ls -l
Now to remove and bad bin files use
rm <NAME OF FILE>
be carefull
Firmware Extraction Problems
Sometimes it will ask again when you re-plug, its a Timing BUG, just click no and re-plug the modem
Modem Not Synchronizing
This only happens when the DSL line is not connected into the modem , or you don't have a filter between teh modem and the socket
Also if you Local Exchange is down.
Modem can't Authenticate
This is a common problem
Here's a Checklist
- Make sure your entering your USERNAME, not your Email Address
- Usernames with no @ in them can make the program hang
- Your password (and username) will be CaSE SenSitIvE
- You must choose PPPoA or PPPoE depending on the type of authentications your ISP supports
- Your VC and VI setting must be correct for your country Table here
- PPPoE requires libatm1 package (you need to type)
require libatm1 package
If you using PPPoA and you keep getting can't authenticate, then you need to see whats happening
So setup the manager to use PPPoE then close it
then type (replace 0.38 with your VC and VI settings)
br2684ctl -b -c 0 -a 0.38
This may give you the error
br2684ctl: error while loading shared libraries: libatm.so.1: cannot open shared object file: No such file or directory
if this is the case then you need to get the library
sudo apt-get install libatm1
unfortunately this can only be done on an internet connected PC, you can do it on another PC then take the file from
/var/cache/apt/archive
and put it onto a USB pen then place it on your PC in the same location, then re-run the apt-get command
The Most common Problem
also it may be time to check to see that your the only PPP attempting to authenticate if you have tried other people scripts you may have something else trying to do a ppp authenticate too we will need to get rid of it.
This will show you a list of processing running (containing the string ppp)
sudo ps -ef | grep ppp
should give you some processes - one will be
ppp usbadslmodem
thats ours, if there are others you will need to kill them
sudo kill -9 <PROCESS NUMBER>
and you may have to work out whats starting them there will be a file for the connection in
/etc/ppp/peers
and maybe a startup script in
/etc/init.d
or
/etc/rc2.d/ /etc/rc3.d/
Can't see internet
Ok just a sanity check : you have chosen Connect from the Tray icon : good
No here is Where you MUST use Debug to work out what's wrong (see top of page)
So start in a terminal then try to connect, what you should see is some kind of attempt to authenticate, This should end with some kind of IP address being detected (and a hover over tray icon should show this)
For PPPoA & PPPoE the
/etc/resolv.conf
should have been linked to
/etc/ppp/resolve.conf
you can check this by typing
ls -l /etc/resolv.conf
Ok next
PPPoE works my making an interface named ppp0 and nas0 these will be visible in
ifconfig
if you have a ppp0 and a ppp1 then an old script (or another script you once tried) has made a ppp0 and is hogging it
you need to remove this and try to reconnect again using the tray icon
