help installing wvdial and smartlink modem driver

[goathunter]

Hello. I am new to linux. I cannot seem to connect to the internet. I have mandriva le 2005. I have a winmodem. Smartlink SmartPCI562 56k modem (revlo)

I tried to connect using kppp but screen would freeze on 'initialising modem'.

I then got wvdial-1.54.0-3mdk.i586.rpm Tried to install it using command line after reading instructions but with no success. Keep getting 'error no such command' or something like that.

Then I read that I needed a driver for my modem. I downloaded one form here http://www.smlink.com/content.aspx?id=132

Got it on my linux box but after reading the 'readme' I still am clueless on how to install the driver.

Anyway after failing to get the command line to work, (my fault I don't have any exp with cli) I clicked on the wvdial-1.54.0-3mdk.i586.rpm icon. It was in a folder I named 'cdstuff' After clicking install i got an error message.
It read 'some package requested can not be installed wvdial-1.54.0-3mdk.i586 (due to unsatisfied libwvstreams.so.3.74 continue?)

I clicked continue and it said package installed. However I do not know whever it is installed or not and if it is how to run it. Again no luck with command lines I got off google.

Now I go to google and download wvstreams-3.74-61.i586.rpm
I have it on a cd and am going to put it on my linux box. However regarding previous problems I've had I am thinking I will have problem with this as well so is their any trick to installing it?

Thanks for your time

[banzaikai]

Oh, my, my... where do we start?

What you've got, driver-wise, is called a "tarball". You download it, extract it to a folder, and then compile it. Once you've done one or two, it's actually pretty easy, but I'm guessing you're kinda new at this. Fortunately, we've got these things called "Newbie Help Files", and one just happens to deal with this very subject, here (http://www.justlinux.com/nhf/Installation/Compiling_Software.html) . Once the driver has been compiled and installed (use the "make install-amr" option), you should have the device listed as "/dev/ttySL0" when using KPPP to set it up. This is why it doesn't see anything now. You may also want to see if KPPP sees it at /dev/ttyS4 (com5 in ms-dos) before you do anything, as Mandriva may have seen it. In fact, open up your terminal and type:
/sbin/lsmod
/sbin/lspci -or- cat /proc/pci
to see what Mandriva has found, hardware/module-wise.

About those RPMs. What you're experiencing is called "Dependency Hell", and can be solved by installing (if not there already) a utility like YUM, APT, or Synaptic. My Fedora came with Yum, but I installed Apt and Synaptic just for grins. All work superbly at finding and downloading any dependencies that may be needed by your package. Try opening up a terminal (CLI) and typing the following (as root):
yum install wvdial
apt-get install wvdial
and see what happens. If installed, one of them will go out and get what you need, grab any deps, and install that sucker.
Of course, none of this'll work unless you're connected to the 'net.

But I think your biggest problem will be your installation method. In order for you to do all this, you'll need to have installed the "Development Packages", which include the source files and GCC utils and libraries. You may have to throw that Mandriva disk back in and pick up those extra packages.

There are also many threads here that have addressed each of these topics, and searching around first before posting anything else will help us out, as this can, and will, get to be a rather large can-o-worms for you if you're really new at it.

In short, I'd:
- make sure you've got the development packages and sources installed
- extract the tarball and run "make" and "make install-amr" for the driver
- reboot and run KPPP to see if you have the /dev/ttySL0 option.
- setup KPPP for your ISP
- $Profit!

And now you know why we all hate Winmodems.

Patience and determination will be your best tools here.

banzai "ATH" kai

[XiaoKJ]

Well, the smlink you have is not a winmodem (it is a very good linmodem, in fact.)

but, to install that, you have to know if you have compilers installed. for RPM-based distros, some of them do not have it installed by default.

however, wvdial is not what you need for the modem. KPPP is the GUI-dialer. you do not need wvdial since you already have KPPP installed. the modem driver is the other important one. you must install that. to do that, you have to be root, and run the installation procedure. try to understand what the README says.

[goathunter]

Thankyou so much for your help. Just off to set up the drivers (hopefully) now.
By the way I did finally manage to install wvdial.
Did a google for wvstreams-3.74-61.i586.rpm and tranferred it to my linux box with a cd-rw. Clicked on the icon and it installed. Then clicked on the wvdial icon and this time it installed properly. Then went to konsole/command line. Typed 'wvdial' and pressed enter. Loads up but won't detect my linmodem/winmodem. But I will do what you said and try to set up with kppp.
Thanks for your time and help.

[XiaoKJ]

actually, wvdial and KPPP are considered substitutes. Therefore, if you have one installed, you can forgo the other. Moreover, you can have both installed and just use one of them. Whichever you prefer.

Of course you cannot see the linmodem --- the driver is still not installed! even in windows, all devices need a driver or else nothing will work. in the case of Smlink, the driver is in a pre-compiled package that can be compiled and later modprobed. For winmodems, there would be almost no driver out there to make it functional within linux, and that is why it is called a winmodem --- a modem only usable with windows.

for that, we really have to thank smlink for giving us a modem that is usable in linux.

if you really cannot grasp the fundamentals of compiling, another route will be to use the debian distro, which has these things all part of apt. it is just that you must learn to install debian and master module-assistant, which, in part, is another bit of complex.

Well, if you don't have the time, stick to your RPM-based distro (which you have not told us what) and try to learn to compile from source.

Wait a minute, do you have the sources to your kernel installed? almost no package can compile a kernel module without the kernel sources installed...

[XiaoKJ]

I've read a bit of the installation instructions, and I see this
1. Build SRPM and RPM from tar.gz package:

In order to build RPM and SRPM run command:

# rpm -ta slmdm-2.X.X.tar.gz

It will build in your RPM directory:
- slmdm-2.X.X-Y.src.rpm - Source SRPM package
- slmdm-2.X.X-Y.i386.rpm - Core Modem RPM package
- slmdm-amr-2.X.X-Y.i386.rpm - AMR/CNR/PCI Modem driver
- slmdm-usb-2.X.X-Y.i386.rpm - USB Modem driver

2. Install

To install Modem core package run:

# rpm -i /path/to/slmdm-2.X.X-Y.i386.rpm

To install Modem hw driver run:

# rpm -i /path/to/slmdm-amr-2.X.X-Y.i386.rpm

if you are going to use AMR/CNR/PCI Modem, or

# rpm -i /path/to/slmdm-usb-2.X.X-Y.i386.rpm

if you are going to use SmartUSB56 Modem.

Note: currently you cannot install and use both AMR/CNR/PCI and USB Modems.

3. Uninstall.

# rpm -e slmdm slmdm-<amr|usb>
I think this is the critical part of the code that you should be running. the # sign means that you must run this as root. thus, the files will be run from the perspective of root. and also, you cannot modprobe this as a normal user. but you can make the system modprobe it as root by itself, and let you dial it as a user.

[banzaikai]

Well, the smlink you have is not a winmodem (it is a very good linmodem, in fact.)
I was wondering what Linux instructions and files were doing on that website ;)
My apologies to the SmartLink folks.

Now, since you'd be adding another step to all this by compiling an RPM from the tarball, I intentionally left it out. After all, once extracted, all goathunter needs to do is:
su (if not already logged in as root)
cd /directory/where/tarball/was/extracted/to
./make
./make install-amr
modprobe slmdm (maybe, the installer should do this for you)

Having to package the tarball and then run the resulting rpm after that is kinda redundant. It will also save time if he has to edit the makefile for the kernel_includes, as he'll have to redo the rpm all over again, where he just has to re-run the ./make after the edit.

Like I said, goathunter, it gets easy after you've done one or two...

banzai "./make coffee -2sugar -half&half" kai

[phlipant]

Did you run wvdialconf create before running wvdial?

[goathunter]

Thanks again for help. BTW I'm using mandiva le 2005
Oh, my, my... where do we start?

What you've got, driver-wise, is called a "tarball". You download it, extract it to a folder, and then compile it. Once you've done one or two, it's actually pretty easy, but I'm guessing you're kinda new at this. Fortunately, we've got these things called "Newbie Help Files", and one just happens to deal with this very subject, here . Once the driver has been compiled and installed (use the "make install-amr" option), you should have the device listed as "/dev/ttySL0" when using KPPP to set it up. This is why it doesn't see anything now. You may also want to see if KPPP sees it at /dev/ttyS4 (com5 in ms-dos) before you do anything, as Mandriva may have seen it. In fact, open up your terminal and type:
/sbin/lsmod
/sbin/lspci -or- cat /proc/pci
to see what Mandriva has found, hardware/module-wise.

Ok Printed out the newbie help file.
Did as it said.
I opened the shell-konsole.
I then clicked 'session'
Then 'New Root Console'
Konsole with yellowish-cream background came up.
I then typed into the konsole my root password and pressed enter.
Got [root@localhost ~] #

I went back to the desktop. I used cut and paste to put file 'slmodem-2.9.10.tar.gz' into 'file:/home/marcus/tmp'

Went back to my yellowish root console,
Typed 'tar xvzf slmodem-2.9.10.tar.gz'
Pressed enter.
Got
'tar:slmodem-2.9.10.tar.gz:cannot open:no search file or directry
tar: Error is not recoverable : exiting now
tar: Error exit delayed from previous errors'

So still no go.


Well, if you don't have the time, stick to your RPM-based distro (which you have not told us what) and try to learn to compile from source.

Wait a minute, do you have the sources to your kernel installed? almost no package can compile a kernel module without the kernel sources installed...

I am using Mandriva LE 2005. I don't know if I have the sources to my kernel installed. How do I find out and if need be how to install them?
Cheers

1. Build SRPM and RPM from tar.gz package:

In order to build RPM and SRPM run command:

# rpm -ta slmdm-2.X.X.tar.gz

It will build in your RPM directory:
- slmdm-2.X.X-Y.src.rpm - Source SRPM package
- slmdm-2.X.X-Y.i386.rpm - Core Modem RPM package
- slmdm-amr-2.X.X-Y.i386.rpm - AMR/CNR/PCI Modem driver
- slmdm-usb-2.X.X-Y.i386.rpm - USB Modem driver

2. Install

To install Modem core package run:

# rpm -i /path/to/slmdm-2.X.X-Y.i386.rpm

To install Modem hw driver run:

# rpm -i /path/to/slmdm-amr-2.X.X-Y.i386.rpm

if you are going to use AMR/CNR/PCI Modem, or

# rpm -i /path/to/slmdm-usb-2.X.X-Y.i386.rpm

if you are going to use SmartUSB56 Modem.

Note: currently you cannot install and use both AMR/CNR/PCI and USB Modems.

3. Uninstall.

# rpm -e slmdm slmdm-<amr|usb>

Thanks, I will try this.


I was wondering what Linux instructions and files were doing on that website
My apologies to the SmartLink folks.

Now, since you'd be adding another step to all this by compiling an RPM from the tarball, I intentionally left it out. After all, once extracted, all goathunter needs to do is:
su (if not already logged in as root)
cd /directory/where/tarball/was/extracted/to
./make
./make install-amr
modprobe slmdm (maybe, the installer should do this for you)

Having to package the tarball and then run the resulting rpm after that is kinda redundant. It will also save time if he has to edit the makefile for the kernel_includes, as he'll have to redo the rpm all over again, where he just has to re-run the ./make after the edit.

Like I said, goathunter, it gets easy after you've done one or two...

banzai "./make coffee -2sugar -half&half" kai

Thanks, I will try this as well.

Did you run wvdialconf create before running wvdial?

No I did not. How do I do that?
Cheers

Once again thanks for all the help. :)

[banzaikai]

Got [root@localhost ~] #
I went back to the desktop. I used cut and paste to put file 'slmodem-2.9.10.tar.gz' into 'file:/home/marcus/tmp'
Went back to my yellowish root console,
Typed 'tar xvzf slmodem-2.9.10.tar.gz'
Pressed enter.
Err... your root's home directory isn't your user's home directory. Try this:

Open terminal
su
(enter password)
cd /home/marcus/tmp
ls (to make sure file is in there)
tar -xvzf slmodem-2.9.10.tar.gz
cd slmodem-2.9.10 (it extracts to it's own directory)
make
make install-amr

I just got done DLing the file, and it works on my system as advertised, but I didn't run the make install-amr because the modem isn't in my machine, of course. It does use gcc, and all builds were shoved into the slmodem-2.9.10/modem/ directory (where they'll be installed with the final make command). So, yes, this file seems to work just fine, thank you.

The GUI-way of doing this depends on your distro. I'm not familiar with Mandriva, but in FC, there's an "Archive Manager" under "System Tools" that'll handle the tarball. You still need to use a terminal for the compiling, though.

You should've selected the development packages and sources when you first installed Mandriva. On FC, there'll be a checkbox at the bottom of the package list that says "Everything", but you can also check on the development section, and it'll install all relevent packages. If you need any of these, make won't work - and neither will the rpm packager. You'll see a bunch of errors, mostly dependencies. I'm sure you can just insert the Mandriva CD and select "Update/Install Packages", and then select the Devel/Source files from there. The important ones are kernel-source and the gcc/libs. The programming languages are also nice to have (Python, Ruby, etc.), because you never know what new utility is programmed in what.

banzai "Standard C" kai

[phlipant]

No I did not. How do I do that?
Cheers

Once again thanks for all the help. :)

just type

wvdialconf create

it will find and configure your modem parameters for wvdial.

[goathunter]

Hello again.

I tried your commands Open terminal
su
(enter password)
cd /home/marcus/tmp
ls (to make sure file is in there)
tar -xvzf slmodem-2.9.10.tar.gz
cd slmodem-2.9.10 (it extracts to it's own directory)
make
make install-amr

All worked fine until I got to make install-amr
I got this
[root@localhost slmodem-2.9.10]# make install-amr
make: *** No rule to make target `install-amr'. Stop.

So no go again.

I then tried this
[root@localhost slmodem-2.9.10]# make install

and got this

make -C modem all
make[1]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.11-6mdk/build
make[1]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
cc -I/lib/modules/2.6.11-6mdk/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.11
make[2]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make modules -C /lib/modules/2.6.11-6mdk/build SUBDIRS=/home/marcus/tmp/slmodem-2.9.10/drivers
make: *** /lib/modules/2.6.11-6mdk/build: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[2]: *** [all] Error 2
make[2]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make: *** [drivers] Error 2
[root@localhost slmodem-2.9.10]# ATI7
bash: ATI7: command not found
[root@localhost slmodem-2.9.10]#

Now what should I do?
BTW I have installed all the mandriva development tools. i went to install software and selected all of them.

Also I am not quite sure what to do once I have installed the drivers. Do they work automatically or is their more commands for me to type and if so once everything is done will everything load automatically when I connect with kppp or wvdial? The readme and the makefile have me mystified. :confused:



just type

wvdialconf create

it will find and configure your modem parameters for wvdial.

Cheers


Once again thanks for taking the time to read this and help me. It is much appreciated.

Quick edit.
Just wondering if I should start a new thread specific to my linmodem driver issue?

[sukamulya]

i'm also having the same problem as goathunter. i'm using mandriva LE 2005, with smartlink modem too, i'm new with linux too. i already do step by step like goathunter and still having the same problem as goathunter too.

[goathunter]

Hello again. I have found this: http://www.shakthimaan.com/Mambo/index.php?option=com_content&task=view&id=43&Itemid=59
I'm off to see if it works now. Just thought I would post it incase its of use to anyone.
Cheers

[sukamulya]

i think the problem is in KERNEL_DIR. i'm still working on it

[banzaikai]

Like I said, a big ol' can-o-worms...

All you need to do is edit the "makefile" in the slmodem directory to point to the correct location of your kernel files. As it happens, my FC3 box has them in the /lib/modules directory, where the makefile expects to see them, which is why it works perfectly on my system. If your files are somewhere else (as in the slackware item you've linked to), then you need to tell the makefile that. It's mentioned in the read.me file, by the way. I have no idea where Mandriva puts their source files... Anyone?

As far as the devel packages are concerned, yes, they'll just sit there until something comes along and uses them. It's mostly cc, gcc, python, ruby, etc., that are used by programmers to get things done. Like everything else, everyone has their favorites, so in order to use/install/compile anything, you have to make sure you've got what they used. And here I thought "C" was supposed to be the end-all to this mess.

So, just edit your makefile to:
KERNEL_DIR=/your/kernel/directory
re-run make, and it should then give you the install-amr option from there.

banzai "ruby-de-railed" kai

[goathunter]

Ok. managed to install the driver last night.
heres what I did.

uname -r

got

2.6.11-6mdk

Thats my kernel.

Then
su
password
# /usr/bin/updatedb

that 'updateb' makes a database of all files on harddrive to use when searching for a file

# /usr/bin/locate KERNEL-2.6.11

'locate' finds the file, in this case my kernel.

Then
# urpmi kernel-source

installing kernel-source-2.6-2.6.11-6mdk.i586.rpm from /var/ftp/pub/Mandrakelinux/media/main3
Preparing... #############################################
1/1: kernel-source-2.6 #############################################

that installs the kernel source.

the kernel source is at /var/ftp/pub/Mandrakelinux/media/main3


Now according to info I got on another forum I needed to install a program called ungrabwinmodem because of the kernel I was using. It can be found here http://linmodems.technion.ac.il/packages/smartlink/
Heres how I installed it.
I put the tar.gz file in /home/marcus
Then went to konsole and

# cd /home/marcus
ls (to make sure file is there)
# tar -xvzf ungrab-winmodem.tar.gz

this is what it spat out

ungrab-winmodem/
ungrab-winmodem/Makefile
ungrab-winmodem/ungrab-winmodem.c
ungrab-winmodem/Readme.txt

then

# cd ungrab-winmodem
# make

spits out this

make modules -C /lib/modules/2.6.11-6mdk/build SUBDIRS=/home/marcus/ungrab-winmodem
make[1]: Entering directory `/usr/src/linux-2.6.11-6mdk'
CC [M] /home/marcus/ungrab-winmodem/ungrab-winmodem.o
Building modules, stage 2.
MODPOST
CC /home/marcus/ungrab-winmodem/ungrab-winmodem.mod.o
LD [M] /home/marcus/ungrab-winmodem/ungrab-winmodem.ko
make[1]: Leaving directory `/usr/src/linux-2.6.11-6mdk'

Then

# make install

spits out this

make modules -C /lib/modules/2.6.11-6mdk/build SUBDIRS=/home/marcus/ungrab-winmodem
make[1]: Entering directory `/usr/src/linux-2.6.11-6mdk'
Building modules, stage 2.
MODPOST
make[1]: Leaving directory `/usr/src/linux-2.6.11-6mdk'
install -D -m 644 ungrab-winmodem.ko /lib/modules/2.6.11-6mdk/extra/ungrab-winmodem.ko
/sbin/depmod -a

Installed.


then to install the drivers.

]# cd /home/marcus/tmp
[root@localhost tmp]# ls (to see whats in the folder)

[root@localhost tmp]# cd slmodem-2.9.10

[root@localhost slmodem-2.9.10]# make

(this is what it put out)

make -C modem all
make[1]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/modem'
[root@localhost slmodem-2.9.10]# make install-amr
make: *** No rule to make target `install-amr'. Stop.

[root@localhost slmodem-2.9.10]# make install

(this is what it put out)

make -C modem all
make[1]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.11-6mdk/build
make[1]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
cc -I/lib/modules/2.6.11-6mdk/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.11-6mdk
make[2]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make modules -C /lib/modules/2.6.11-6mdk/build SUBDIRS=/home/marcus/tmp/slmodem-
make[3]: Entering directory `/usr/src/linux-2.6.11-6mdk'
CC [M] /home/marcus/tmp/slmodem-2.9.10/drivers/amrmo_init.o
/home/marcus/tmp/slmodem-2.9.10/drivers/amrmo_init.c: In function `amrmo_read':
/home/marcus/tmp/slmodem-2.9.10/drivers/amrmo_init.c:353: warning: ignoring retuttribute warn_unused_result
/home/marcus/tmp/slmodem-2.9.10/drivers/amrmo_init.c: In function `amrmo_write':
/home/marcus/tmp/slmodem-2.9.10/drivers/amrmo_init.c:366: warning: ignoring retu attribute warn_unused_result
CC [M] /home/marcus/tmp/slmodem-2.9.10/drivers/sysdep_amr.o
CC [M] /home/marcus/tmp/slmodem-2.9.10/drivers/st7554.o
/home/marcus/tmp/slmodem-2.9.10/drivers/st7554.c: In function `st7554_init':
/home/marcus/tmp/slmodem-2.9.10/drivers/st7554.c:1112: warning: implicit declara
LD [M] /home/marcus/tmp/slmodem-2.9.10/drivers/slamr.o
LD [M] /home/marcus/tmp/slmodem-2.9.10/drivers/slusb.o
Building modules, stage 2.
MODPOST
CC /home/marcus/tmp/slmodem-2.9.10/drivers/slamr.mod.o
LD [M] /home/marcus/tmp/slmodem-2.9.10/drivers/slamr.ko
CC /home/marcus/tmp/slmodem-2.9.10/drivers/slusb.mod.o
LD [M] /home/marcus/tmp/slmodem-2.9.10/drivers/slusb.ko
make[3]: Leaving directory `/usr/src/linux-2.6.11-6mdk'
make[2]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make[1]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make install -C drivers KERNEL_DIR=/lib/modules/2.6.11-6mdk/build
make[1]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
cc -I/lib/modules/2.6.11-6mdk/build/include -o kernel-ver kernel-ver.c
mkdir -p /dev
mknod -m 600 /dev/slamr0 c 212 0 ; mknod -m 600 /dev/slamr1 c 212 1 ; mknod /dev/slamr3 c 212 3 ; echo -n
mknod -m 600 /dev/slusb0 c 213 0 ; mknod -m 600 /dev/slusb1 c 213 1 ; mknod /dev/slusb3 c 213 3 ; echo -n
make install KERNEL_VER=2.6.11-6mdk
make[2]: Entering directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
install -D -m 644 slamr.ko /lib/modules/2.6.11-6mdk/extra/slamr.ko
install -D -m 644 slusb.ko /lib/modules/2.6.11-6mdk/extra/slusb.ko
/sbin/depmod -a
make[2]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
make[1]: Leaving directory `/home/marcus/tmp/slmodem-2.9.10/drivers'
install -D -m 755 modem/slmodemd /usr/sbin/slmodemd
rm -f -rf /var/lib/slmodem
install -d -D -m 755 /var/lib/slmodem

Now thats where my success ends. The driver is installed but it will not work. I read the readme and it says to set up the area codes. This is the commands I typed and what it gave me back.

[root@localhost slmodem-2.9.10]# AT+GCI+64
bash: AT+GCI+64: command not found
[root@localhost slmodem-2.9.10]# slmodemd --countrylist
02: ALGERIA
07: ARGENTINA
09: AUSTRALIA
0a: AUSTRIA
0c: BAHREIN
0f: BELGIUM
16: BRAZIL
1a: BRUNEI
1b: BULGARIA
20: CANADA
25: CHILE
26: CHINA
100: CTR21EUROPE
2d: CYPRUS
2e: CZECH_REPUBLIC
31: DENMARK
36: EGYPT
101: ESTONIA
3c: FINLAND
3d: FRANCE
42: GERMANY
46: GREECE
50: HONG_KONG
51: HUNGARY
52: ICELAND
53: INDIA
54: INDONESIA
57: IRELAND
58: ISRAEL
59: ITALY
00: JAPAN
5e: JORDAN
61: KOREA
62: KUWAIT
103: LATVIA
64: LEBANON
104: LITHUANIA
69: LUXEMBOURG
6c: MALAYSIA
70: MALTA
73: MEXICO
77: MOROCCO
7b: NETHERLANDS
7e: NEW_ZEALAND
82: NORWAY
83: OMAN
84: PAKISTAN
88: PERU
89: PHILIPPINES
8a: POLAND
8b: PORTUGAL
8e: ROMANIA
b8: RUSSIA
98: SAUDIARABIA
9c: SINGAPORE
c5: SLOVAKIA
c6: SLOVENIA
9f: SOUTHAFRICA
107: SOUTHKOREA
a0: SPAIN
a1: SRILANKA
a5: SWEDEN
a6: SWITZERLAND
108: TAIWAN
a9: THAILAND
ad: TUNISIA
ae: TURKEY
b3: UAE
b4: UK
b7: URUGUAY
b5: USA
bc: VIETNAM
[root@localhost slmodem-2.9.10]# AT+GCI=7e
bash: AT+GCI=7e: command not found

As you can see I tryed to install the country just like the readme says with no success.

Here is the readme

Smart Link Ltd.
wwwdotsmlinkdotcom
Sep 30, 2003


Smart Link Soft Modem for Linux
-------------------------------


Introduction
============

This is Smart Link Soft Modem for Linux version 2.9. It provides
full-featured 56K Voice Fax Modem.
This is implemented as generic application (slmodemd) and set of
hardware specific kernel-space drivers (slamr, slusb).
ALSA modem drivers may be used instead of proprietary ones (see ALSA mode).

Features
========

Modem: V.92, V.90, V.34, V.32bis, V.32, V.23, V.22, V.21, Bell 103/212.
Flow control: V.42.
Compression: V.44, V.42bis.
Fax: Class 1.
Voice: V253 like modem.
Multiple modems are supported.


Supported Hardware
==================

HAMR5600 based AMR/CNR/MDC/ACR modem cards on the following Southbridge
chips:
- Intel ICH0,ICH2, ICH3, ICH4
- Via 686A, 686B, 8231, 8233
- SiS 630
- ALI 1535.
SmartPCI56/561/562/563 based PCI modem cards.
SmartUSB56 based USB modem.



Requirements
============

CPU: Intel Pentium II, Celron. AMD K6, Cyrix 500MHz or higher.
Memory: 64MB.

OS: Linux 2.4. You need the kernel header files at least (or full kernel
source tree) installed and configured.
Linux 2.6. You need the full kernel source tree installed and configured.

Note: Most Linux Distributions have 'ready to use' kernel source package -
be sure that this is installed.


Installation
============

1. Unpack tar.gz package file:

$ gzip -dc slmodem-2.9.X.tar.gz | tar xf -

2. 'cd' to package directory:

$ cd slmodem-2.9.X

3. Review and edit 'Makefile' (if need):

In many cases you will need to correct path to your local kernel
source tree:

KERNEL_DIR=/path/to/linux

Default KERNEL_DIR is '/lib/modules/<kerne-version>/build'. Many Linux
Distributions use directory '/usr/src/linux-<version>' also.

Note: If you are using Linux kernel 2.4, only header files should be
available for build in $(KERNEL_DIR)/include

Another way to pass right value KERNEL_DIR is to use command line
parameter while running 'make':

$ make KERNEL_DIR=/path/to/linux ...

4. Run 'make' command to compile package:

$ make

5. Install. As 'root' user run:

# make install

It will install:

- application 'slmodemd' under '/usr/sbin' directory

- hardware specific drivers (kernel modules) 'slamr' and 'slusb'
under conventional kernel modules directory

- character device nodes '/dev/slamr0-3' with major number 212
(for pci modems) and '/dev/slusb0-3' with major number 213
(for usb modems).

- config modules for autoloading (by editing file '/etc/modules.conf')
(only with 2.4 kernels)

6. Config modem country.

Use AT+GCI=<T.35 country code> command to setup country.

Also you can setup default modem country by passing command line
parameter '--country=MY_COUNTRY' to program 'slmodemd'.

See output of 'slmodemd --countrylist' for a list of supported
country names and T.35 country codes (see also 'slmodemd --help').

Note: Command ATI7 shows currently installed country setting.

8. Uninstallation.

In package directory just type:

# make uninstall


Getting Started
===============

After successful installation and configuration:

1. Load modem driver.

Load your modem hardware specific kernel module:

# modprobe slamr

if you are using AMR/CNR/PCI modem, or

# modprobe slusb

if you are using SmartUSB56 Modem.

Note: this will be done automatically when modules were
configured for 'loading on demand'

Note: this is safe to load both 'alamr' and 'slusb' modules.

2. Run soft modem application.

# /usr/sbin/slmodemd [options] <device_name>

Where device name is appropriate device node for your modem
(look at output of 'dmesg' command).
Run '/usr/sbin/slmodemd --help' for details.

Examples:

# /usr/sbin/slmodemd --country=USA /dev/slamr0

, or for SmartUSB56 Modems:

# /usr/sbin/slmodemd --country=ITALY /dev/slusb0

3. Using the modem.

When 'slmodemd' is running this creates PTY (pseudo-terminal) to
emulate modem port device, also this creates symbolic link
like '/dev/ttySL0' (shown at startup).

Config your application to use this link '/dev/ttySL0' (or PTY node
itself) as modem port.

Note: Some application want 'to know' that they are working with
pseudo-terminal and may require additional configurations.

Known application notes:

- 'wvdial' requires option 'Carrier Check = no' in config file

- some versions of 'kppp' may not work properly with devices named
like '/dev/ttySL0'. To workaround this you may create symbolic link
'/dev/modem' ( # ln -s /dev/ttySL0 /dev/modem ) and use this link
as modem device with 'kppp'

4. Startup automation.

There are examples of startup scripts in 'scripts' directory.


ALSA mode
=========

ALSA has the built-in modem drivers included in 'alsa-driver' >= 1.0.2
and in Linux kernel >= 2.6.5. Currently there is 'intel8x0m' (snd-intel8x0m)
modem driver, which supports ICH based AC97 modems (MC97).

Recent 'alsa-driver' (>=1.0.6) has also support for NVidia NForce
(snd-intel8x0m) and ATI IXP (snd-atiixp-modem) based modems.

1. Configure your kernel and enable ALSA and ICH based modem support
( 'Device Drivers' -> 'Sound' -> 'Advanced Linux Sound Architecture' ->
'PCI devices' -> 'Intel i8x0/MX440; AMD768/8111 modems' ) .

2. Build and install kernel and modules as usual (make , make modules_install,
etc.). ICH modem driver modem module name is 'snd-intel8x0m'
(if was configured as module).

3. Build application 'slmodemd' with ALSA support. For this in
slmodem-2.9.x dir:

$ cd modem
$ make SUPPORT_ALSA=1

This will build 'slmodemd' with ALSA support. If compilation is failed
review Makefile (near ALSA_SUPPORT condition) and define right library
and/or CFLAGS

4. Use option '--alsa' when running 'slmodemd' and ALSA conventional
device name ('hw:0' or 'hw:1' for instance). If modem support in
the kernel was enabled as module module 'snd-intel8x0m' should be loaded.

Note: Recent version of 'alsa-lib' (>= 1.0.6) has built-in "modem" device
name support ('modem:0', 'modem:1', etc). It is recommended to use
those names with modems (mandatory with ATI IXP modems).

Note: When using ALSA modem driver you don't need to load other
modules ('slamr').


Troubleshooting
===============

If you get an error message during installation/configuration or loading
the modules try to see it in FAQ file.

Please report the problem to your modem provider or to us
(linux-support@smlinkdotcom).


Feedback
========

Please send any feedbacks to Smart Link. See the Smart Link
web site for contact information (wwwdotsmlindotcom) or to
linux-support@smlinkdotcom.



So, failing to set country code (btw I'm in New Zealand), I went to the next step. Since I'm using a PCI modem, I typed

[root@localhost slmodem-2.9.10]# modprobe slamr

and it spits out this

FATAL: Error inserting slamr (/lib/modules/2.6.11-6mdk/extra/slamr.ko): Unknown
symbol in module, or unknown parameter (see dmesg)

So I type

dmesg

and get

slamr: module license 'Smart Link Ltd.' taints kernel.
slamr: Unknown symbol get_device
slamr: Unknown symbol put_device
slamr: Unknown symbol device_release_driver
slusb: Unknown symbol usb_endpoint_halted
slamr: Unknown symbol get_device
slamr: Unknown symbol put_device
slamr: Unknown symbol device_release_driver

So I am stuck again. Can anyone tell me what to do now?
Cheers and thanks for your time.

[sukamulya]

hi goathunter,

can u send me ungrab-winmodem.tar.gz to me? the link is already dead. my e-mail is sukamulya@cbn.net.id

thank you

hope this will help u
http://66.218.71.231/language/translation/translatedPage.php?tt=url&text=http%3a//www.vivaolinux.com.br/artigos/verArtigo.php%3fcodigo=513&lp=pt_en&.intl=us&fr=moz2

[banzaikai]

This is getting really confusing, as I'm helping two completely different people with inherently the same problem. Bear with me.

Now, the "AT" command they're talking about is when the modem is up and running. The "Terminal" for a modem is not the terminal/shell/cli for Linux. So, if you're in a shell/terminal/cli, then you need to issue the command:

/usr/sbin/slmodemd --country=NEW_ZEALAND /dev/slamr0

but if you're in a modem's communication terminal, then the Hayes "AT" commands are:

AT+GCI=7e
AT&W
ATZ

to set things up so you won't have to do it over again.

Now, run /sbin/lsmod to see if the slamr module is actually loaded. It looks like it was built and installed, but there may have been an error. You may also want to reboot and see what dmesg says about it.

Something to note: my Fedora Core 3 has the SL0-4 drivers already installed! If this is getting all too much, I'd suggest getting FC3, and installing "Everything" (7GB will be used, don't do this on anything less than ~15GB, as you'll need room for the up2date files, too). I'll bet half your problems will go bye-bye. Although FC is a bit... different... from the previous RedHat distros, it now does things in seconds that used to take hours of configuring and playing around. I'm getting really comfortable with it.

banzai "whoodathunk?" kai

[goathunter]

okay still no go.

did
/usr/sbin/slmodemd --country=NEW_ZEALAND /dev/slamr0

got an error no such file command not found

Then did this

/sbin/lsmod

no the slamr module was not there.

so tried this and got these results

[root@localhost marcus]# cd /home/marcus/tmp/slmodem-2.9.10
[root@localhost slmodem-2.9.10]# /sbin/modprobe -r slamr
[root@localhost slmodem-2.9.10]# /sbin/modprobe ungrab-winmodem
[root@localhost slmodem-2.9.10]# /sbin/modprobe slamr
FATAL: Error inserting slamr (/lib/modules/2.6.11-6mdk/extra/slamr.ko): Unknownsymbol in module, or unknown parameter (see dmesg)
[root@localhost slmodem-2.9.10]#

Am i best to reinstall the slmodem drivers or see if I can download and install the /lib/modules/2.6.11-6mdk/extra/slamr.ko module seperatley?
Thanks for your time

PS
hi goathunter,

can u send me ungrab-winmodem.tar.gz to me? the link is already dead. my e-mail is sukamulya@cbn.net.id

thank you

sent to ur email. :)

[sukamulya]

finally made it with the modem. right now i'm connecting to the internet via linux.

hope this link will help you goathunter

http://mandrivausers.org/index.php?showtopic=26362

[goathunter]

Thanks, off to try it now. Did u get that ungrabwinmodem file i emailed you?

[sukamulya]

yup i got it. thanx

[goathunter]

Still couldn't get the driver to install so bit the bullet and bought a dynalink external serial modem. Sadly, I can't get that to work either.

http://www.justlinux.com/forum/showthread.php?p=823021#post823021