Try the same again by browsing to the /var/log directory, and click the messages file (the one Volker refers to). You won't be able to view the contents as you don't have permission to do so - you need root permissions - so you need to start up "File Manager Super User Mode" (start, system, file manager menu), enter your root password, then you can navigate to the /var/log directory, now you can right click it and open in kate. Careful what you do here though!
There are alot of lines in this file! In this situation it can be better to use the command line and grep to narrow down what you need to find - but I'll have to leave that to someone else to tell you about (cause I don't know what it is you need to find).
And there are command line options for this sort of thing, but this will get you going initially. Works for me anyway. Maybe someone would like to elaborate further or provide "better" ways of doing this?
Roger
Deane Foreman wrote:
I may be looking at the resources tab for the modem in the wrong place because all the information it gives me is the bit rate, which is zero. There is a tab for Drivers, but it is disabled.
You'll have to give me very basic instructions for the use of lsmod and the modprobe line I'm afraid. Is this something I use through the command line interface? I have set up a Terminal Sessions button on the taskbar (thanks Roger) but there are two options that begin with "Root" (Root Shell and Midnight Commander?? from memory - I'm in windoze typing this).
Also, I don't understand what you mean by editor, or how to load a file into one.
I do hope windoze and the graphical user interface hasn't ruined me for real computing....
Deane
----- Original Message ----- From: "Volker Kuhlmann" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, May 16, 2005 12:43 PM
Subject: Re: Configuring USB ADSL modem in SUSE
I note that Suse is detecting my modem (Dynalink ALE070 with Globespanvirata (Conexant??)chipset when I look under:
SUSE Hardware tool>Unknown device>Globespan USB-ADSL Modem.
That might not be proof that Linux can handle that modem. Every USB device has an identification string, which can always be read by Linux.
I "inserted" the device using the harware tool and it reports that the driver is loaded, and it should be possible to use the device.
Lookup in the resources tab what driver it has loaded (the modprobe line(s)). Then check with lsmod that that module is indeed loaded.
You can also try and load the module from root's command line, which might be more informative. Make sure the module is not loaded (easiest to reboot), check that with lsmod. The type the modprobe command and see if it says anything interesting. Immediately after load the file /var/log/messages into your favourite editor and read from the end(!) backwards, looking for any line related to the module loading.
This should show any low level communication problems with kernel and modem.
If you're certain that the modem is functional under Linux, you can try to connect to your ISP. Modems sold in NZ should be preconfigured for NZ's line parameters, however if you use yast then it's theoretically possible that yast overrides those values which it can control.
Then you need to get your user name and password just right... :)
Volker
-- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
