DSL SpeedTouch modem

From ArchWiki
Revision as of 20:22, 7 November 2005 by
Jump to: navigation, search
Newer udev (060 or so) puts itself as the hotplug program in 
/proc/sys/kernel/hotplug, but doesn't handle firmware loading requests, 
thus the automatic firmware loading as described below won't work. Best way 
to solve this problem is yet unclear.


This howto shows one way to get a working speedtouch USB modem. It uses the kernel driver, not the userspace driver. This howto assumes that your ISP uses PPPoA and not PPPoE. For info about PPPoE with these modems see first url below.

Important sites where most info comes from:

If the below instructions are not enough to get it working, then read the above sites.

The following steps are needed to get the modem working:

1) Make sure you have a kernel with the proper support (at least the modules pppgeneric, pppoatm, slhc, atm, usbatm and speedtch). The default Arch kernel should work: pacman -S kernel26

2) Install ppp: pacman -S ppp

3) Configure pppd's config files

Configuring pppd

###  /etc/ppp/peers/speedtch

# To connect to using this configuration file, do
#       pppd call speedtch

lcp-echo-interval 10
lcp-echo-failure 10
user "username@ispname"
holdoff 4
maxfail 25
plugin pppoatm.so
# Following entry is country/ISP dependent

The last entry depends on your country/ISP and is created from the VPI and VCI setting in the format VPI.VCI. A windows speedtouch diagnostic program may show you the VPI and VCI settings for your country/ISP.

This page has a VPI / VCI Setting List, which I have partially reproduced below.

Australia All Internet providers VPI:8 VCI:35
United Kingdom British Telecom VPI:0 VCI:38

You also need to configure /etc/ppp/pap-secrets or chap-secrets, depending on your ISP. If you want to use the DNS servers provided by your ISP then make a symlink /etc/resolv.conf pointing to /etc/ppp/resolv.conf:

cd etc
rm resolv.conf
ln -s ppp/resolv.conf resolv.conf

4) Configure hotplug:

Make an executable (chmod +x) file /etc/hotplug/usb/speedtch and put something like the next in it:

case $ACTION in
	if [[ ! -z "$SEQNUM" -a ! -f /tmp/bla ]]; then
		sleep 1;
		/usr/sbin/pppd call speedtch &> /tmp/bla;
		echo -e "--- $SEQNUM ---\n$DEVPATH" >> /tmp/bla;
	echo -n "speedtch unknown action: $ACTION" >> /tmp/unknown-action;

5) Now you have everything except the firmware loading. Easiest is if you let hotplug do it. The above script assumes that. If you want to do it manually then you'll need to do it in the above speedtch script with the appropriate sleeps to give the modem enough time.

If you have a zip like e.g. rev4fw.zip, then unzip it. It probably contains two files, a small one and a big one. Copy the small file to:


and the big one to:


The first one should be about 990 bytes, and the second one about 660Kb. If you don't get those two files, but only one, then follow the instructions of the second link above and use the firmware extractor (or download another firmware which has the two files). The lib/firmware/ most likely doesn't exist yet, just make it.

Make sure that the kernel supports firmware loading:

$ zcat /proc/config.gz || grep FW_LOADER

should tell that. The default Arch kernel is ok.

Now reboot and pray that it works. In dmesg you'll get something like the following if everything goes alright:

usbcore: registered new driver speedtch
usb 1-1: found stage 1 firmware speedtch-1.bin
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
usb 1-1: found stage 2 firmware speedtch-2.bin
ip_tables: (C) 2000-2002 Netfilter core team
ADSL line is synchronising
DSL line goes up
ADSL line is up (800 Kib/s down || 256 Kib/s up)

And the content of the /tmp/bla file should be something like:

Plugin pppoatm.so loaded.
PPPoATM plugin_init
PPPoATM setdevname - remove unwanted options
PPPoATM setdevname_pppoatm - SUCCESS:8.48
Using interface ppp0
Connect: ppp0 <--> 8.48
PAP authentication succeeded
local  IP address
remote IP address
primary   DNS address
secondary DNS address
--- 363 ---

For the origin of this doc, feedback or requests go to the Forum discussion