mikael persson wrote:
oh, that sounds good. I have absolutely no idea which revision. I found no details about that anywhere on the modem or in the driver info. It is purple/pink if that is of some help. Hopefully that won't doom it, I've seen that everyone mentions the silver one..
The purple one is revision 2 and AFAICT it's easier to set up than the silver (revision 4) modem. You may find Geoff Horn's suggestion better since he actually has 9.2 and may well be using a revision 2 modem. One particular thing to be careful of is that you get the right drivers installed in the right order. I don't know what these are for the revision 2 modem. The way I got it to work was to use the speedtouch 1.3 driver from http://speedtouch.sourceforge.net/index.php?/download.en.html combined with the kernel module, which is included in SuSE 9.1. speedtouch-1.3: Download speedtouch-1.3.tar.bz2 from http://speedtouch.sourceforge.net/index.php?/download.en.html to a directory (say ~/src). Open a Konsole (or xterm or similar) $ cd ~/src $ tar jxvf speedtouch-1.3.tar.bz2 $ cd speedtouch-1.3 $ ./configure If you get warnings here, install compilers, linkers, etc., from the SuSE CDs using YaST - try package groups, development, or search for whatever appears to be missing. $ make $ su (and enter root password) # make install This creates the program /usr/local/sbin/modem_run, which you need later. You may also find it helpful to do the $ ./configure as $ ./configure --enable-debug --enable-syslog then when testing, you can see the output in the system log view (YaST=>misc) or from a konsole as root with # tail -f /var/log/messages You now need the modem microcode. It comes in the form of two files: (ZZZLP1.eni and ZZZLP2.eni for the silver modem). If you installed on a dual boot system, you can probably find them in /windows/C/Program Files/Thomson/SpeedTouch USB/Bin I created a new directory # mkdir /etc/ppp/peers/speedtouch and copied the two files there as a convenient location for them. Now you can test if the modem actually does anything when you try to load the microcode: as root (all on one line) # /usr/local/sbin/modem_run -a /etc/ppp/peers/speedtouch/ZZZLP1.eni -f /etc/ppp/peers/speedtouch/ZZZLP2.eni -k -v 1 You should see some new information on the system log, some flashing lights on the modem and both eyes should turn yellow-green (initial the frog is winking red in the right eye) If all of that works, you need (at least on 9.1) a couple of extra changes to make it all work correctly. First, set pppoatm as a module loaded on boot: YaST>System>/etc/sysconfig editor - System + Kernel - MODULES_LOADED_ON_BOOT. Just type in 'pppoatm' without the quotes. This loads pppoatm at boot time so that the modem can initialise automatically. Second, to get it to run automatically, you should create a hotplug script. Mine contains the following lines: (the bits between the ============ - watch out for line-wrapping - the bit starting if .. should be two lines, the first ending with \) ======================================================================= #!/bin/bash case $ACTION in add) echo "Uploading speedtouch microcode (/etc/hotplug/usb/speedtch)" if /usr/local/sbin/modem_run -a /etc/ppp/peers/speedtouch/ZZZLP1.eni \ -f /etc/ppp/peers/speedtouch/ZZZLP2.eni -k -v 1; then echo "Speedtouch microcode loaded" else echo "Speedtouch microcode not loaded" fi ;; remove) : ;; esac ======================================================================= I saved this as root as /etc/hotplug/usb/speedtch. It should be executable (I think); so do # chmod +x /etc/hotplug/usb/speedtch to make sure. That should have dealt with the microcode. The next part is getting a connection. IIRC, YaST was fine: YaST=>Network=>DSL=>configure and use default settings or follow suggestions. You should use PPPOATM and I chose hotplug as the device activation and 0.38 for the VPI/VCI (btinternet) You'll have to fill in the provider's details. Test with kinternet (which will need some reconfiguring if you haven't removed te seetings for the old modem) or $ cinternet -i dsl0 --start -- JDL