OK. I downloaded the Martian-Modem-20071011-for-slax module from http://www.mpchopper.com/slaxmodules/dlmodules/martian-full-20071011-for-slax.lzm and the wvdial-1.60 module from SonOfFree's GSpace account. Activating them from KDE and calling them from Konsole as described in scanModem's AGERE_DSP.txt they appeared to work--they found my modem and successfully logged into my ISP.
But then stange things started happening. Though I was supposedly connected to the Internet neither Konqueror or Firefox could load any Web pages. Worse, after logging off I could no longer connect again using wvdial, not even in shell (text mode).
This is my wvdial.out file:
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT2284114
--> Waiting for carrier.
ATDT2284114
CONNECT 42666 V44
--> Carrier detected. Waiting for prompt.
Level 3 Comm nas7.chi1 UQKT2
Username:/login:/Login:
--> Looks like a login prompt.
--> Sending: tg_harris@usnetizen.net
tg_harris@usnetizen.net
Password:
--> Looks like a password prompt.
--> Sending: (password)
Proxied: User: tg_harris@usnetizen.net already logged onto system 1 time(s).
Username:/login:/Login:
--> Looks like a login prompt.
--> Sending: tg_harris@usnetizen.net
tg_harris@usnetizen.net
Password:
--> Looks like a password prompt.
--> Sending: (password)
Proxied: User: tg_harris@usnetizen.net already logged onto system 1 time(s).
Username:/login:/Login:
--> Looks like a login prompt.
--> Sending: tg_harris@usnetizen.net
tg_harris@usnetizen.net
Password:
--> Don't know what to do! Starting pppd and hoping for the best.
--> Starting pppd at Wed Mar 12 22:00:58 2008
--> Pid of pppd: 13899
--> pppd: ø§[06][08]0¥[06][08]
--> Using interface ppp0
--> pppd: ø§[06][08]0¥[06][08]
--> pppd: ø§[06][08]0¥[06][08]
--> pppd: ø§[06][08]0¥[06][08]
--> pppd: ø§[06][08]0¥[06][08]
--> pppd: ø§[06][08]0¥[06][08]
--> Disconnecting at Wed Mar 12 22:01:02 2008
--> The PPP daemon has died: Authentication error.
--> We failed to authenticate ourselves to the peer.
--> Maybe bad account or password? (exit code = 19)
--> man pppd explains pppd error codes in more detail.
--> I guess that's it for now, exiting
--> The PPP daemon has died. (exit code = 19)
Worse, I could no longer log in even from Windows. Fortunately that problem was straigtened out by this morning.
Still, what am I doing wrong?
How do I use martian and wvdial?
Even better, how do I set up kppp and Martian so I can dial from X?
Whew. Well, it's a winmodem, and my best advice is to smash it with a hammer, and buy a cheap serial port modem off ebay. That'll work with any puter using no special software whatever. If time and irritation-reduction means anything to you, it'll be cheap at the price.
Then exit /etc/rwvdial to look like the following:
root@slax:~# cat /etc/wvdial.conf
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
Phone = 7072000 Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT7072000
--> Waiting for carrier.
ATDT7072000
CONNECT 49333 V42bis
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Mar 14 19:21:32 2008
--> Pid of pppd: 5134
--> Using interface ppp0
--> pppd: 0¥[06][08](¨[06][08]
--> pppd: 0¥[06][08](¨[06][08]
--> pppd: 0¥[06][08](¨[06][08]
--> pppd: 0¥[06][08](¨[06][08]
--> local IP address 66.201.10.244
--> pppd: 0¥[06][08](¨[06][08]
--> remote IP address 66.201.8.7
--> pppd: 0¥[06][08](¨[06][08]
--> primary DNS address 66.201.0.203
--> pppd: 0¥[06][08](¨[06][08]
--> secondary DNS address 66.94.120.9
--> pppd: 0¥[06][08](¨[06][08]
If wvdial does not get you connected to the internet, try to create a symbolic link
# ln -s /dev/ttySL0 /dev/modem
configure KPPP to use /dev/modem and try your connection, then when connected, do a
# cat /etc/resolv.conf
and you should see some numbers and a # kppp temp entry.
Use these numbers if you are going back to using wvdial.
BTW,
when you get an error 19, you either did not disconnect and pppd thinks that you are still connected and you cannot get back to logining in.
The above are for compiling hands on from the code and how steps look and have changed. They wre created using Slax-6.0rc3. Now, the new martian-full-20070711-for-slax requires no compiling, it does all the work for you. All you need to do is query the modem with wvdial if you plan to use it, and change the init strings a bit, add carrier check = no like explained above.
you may do a
root@slax:~# cat /etc/rc.d/rc.martian
and open it up with an editor and change the device to whatever device name you want
@tonio
do you have a ready module for the smartlink modem?
if not, and you plan to make one, i can provide the last drivers slmodem-2.9.11-20080126.tar.gz
i am a noob and don't know to make one :) (not yet at least).
I had the smartlink modem working but for older slax 6.0.rc3 and not the latest one.
To create a tgz file, all you need is get the src2pkg module and download the source slmodem-2.9.11-20070228.tar.gz which has the fix to compile in in kernel 2.6.24, the code compiles, but the modem is not functioning. Whenever new code gets released and I know that the slmodem-2.9.11-2008XXYY code is working, I plan to create a module for slmodemd+ungrab-winmodem together later on when all is working.
Download src2pkg modules from posturmodules page(s)
src2pkg name-of-pkg.tar.(gz)(bz2)../
thanks for your info.
i gave a look to your how-to and it looks very good, though i am afraid that it is something that my limited linux knowledge can't grasp yet.
i'll wait for your module :)
some days before i found on the net the 20080126 version of the drivers, so if you need them just tell me.
root@slax:/tmp# ./scanModem
UPDATE=2008_03_15
Continuing as this update is a only 1 weeks old,
but the current Update is always at: http://linmodems.technion.ac.il
Identifying PCI bus slots with candidate modems.
=== Finished modem firmware and bootup diagnostics
section. ===
=== Next deducing cogent software ===
Running PCIbus cases
Analysing card in PCI bus 00:0a.0, writing to
scanout.00:0a.0
Using scanout.00:0a.0 data, and writing guidance to
ModemData.txt
Read Smartlink.txt
Writing Smartlink.txt
Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing
these files with more detailed Information:
root@slax:/tmp# cat Modem/ModemData.txt
Only plain text email is forwarded by the
Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject
Line:
YourName, YourCountry
===============================================================================
Welcome to Slax
6.0.2
===============================================================================
The system is up and running now.
Login as "root" with password "toor", both without
quotes, lowercase.
If you're new to Slax, visit http://www.slax.org/ for
more info.
After you login, try the following commands:
mc ....... to start Midnight Commander
(edit/copy/move/create/delete files)
startx ... to run Xwindow system with KDE in VESA
mode 1024x768 at 75Hz
xconf .... to autoconfigure your graphics card for
better performance
Other commands you may find useful (for experts
only!):
activate ..... to insert (install) Slax module into
the system on the fly
deactivate ... to remove (uninstall) Slax module from
the root filesystem
mkfileswap ... to create a special file on your
harddisk for virtual RAM
When finished, use "poweroff" or "reboot" command and
wait until it completes
===============================================================================
kernel 2.6.24
With this Subject Line cogent experts will be
alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance.
Your contry's local Linux experts
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be
essential for dialup service.
Responses from Discuss@Linmodems.org are sometimes
blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information
----------------------------
CPU=i686,
===============================================================================
Welcome to Slax
6.0.2
===============================================================================
The system is up and running now.
Login as "root" with password "toor", both without
quotes, lowercase.
If you're new to Slax, visit http://www.slax.org/ for
more info.
After you login, try the following commands:
mc ....... to start Midnight Commander
(edit/copy/move/create/delete files)
startx ... to run Xwindow system with KDE in VESA
mode 1024x768 at 75Hz
xconf .... to autoconfigure your graphics card for
better performance
Other commands you may find useful (for experts
only!):
activate ..... to insert (install) Slax module into
the system on the fly
deactivate ... to remove (uninstall) Slax module from
the root filesystem
mkfileswap ... to create a special file on your
harddisk for virtual RAM
When finished, use "poweroff" or "reboot" command and
wait until it completes
===============================================================================
Linux version 2.6.24 (root@slax) (gcc version 4.2.3)
#1 SMP Wed Feb 27 14:33:25 GMT 2008
scanModem update of: 2008_03_15
The slmodemd set symbolic link is /dev/ttySL0 ->
/dev/pts/0
The Advanced Linux Sound Architecture (ALSA) packages
providing audio support,
also includes drivers for some modems. The ALSA
diagnostics are written during
bootup to /proc/asound/ folders.
The ALSA verion is 1.0.16
The modem cards detected by "aplay -l" are:
The /proc/asound/pcm file reports:
-----------------------
00-01: VIA 8237 : VIA 8237 : playback 1 : capture 1
00-00: VIA 8237 : VIA 8237 : playback 4 : capture 1
about /proc/asound/cards:
------------------------
0 [V8237 ]: VIA8237 - VIA 8237
VIA 8237 with ALC650F at 0xe800,
irq 21
USB modem not detected by lsusb
For candidate card in slot 00:0a.0, firmware
information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- ---------
--------------
00:0a.0 163c:3052 163c:3052 Modem:
Smart Link Ltd. SmartLink SmartPCI562 56K Modem
Modem interrupt assignment and sharing:
16: 393603 IO-APIC-fasteoi SL1900
--- Bootup diagnostics for card in PCI slot 00:0a.0
----
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level,
low) -> IRQ 16
0000:00:0a.0: ttyS2 at I/O 0xb008 (irq = 16) is a
16450
0000:00:0a.0: ttyS3 at I/O 0xb010 (irq = 16) is a 8250
Couldn't register serial port 0000:00:0a.0: -28
ACPI: PCI interrupt for device 0000:00:0a.0 disabled
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level,
low) -> IRQ 16
The PCI slot 00:0a.0 of the modem card may be
disabled early in
a bootup process, but then enabled later. If modem
drivers load
but the modem is not responsive, read Bootup.txt
about possible fixes.
Send dmesg.txt along with ModemData.txt to
discuss@linmodems.org
if help is needed.
=== Finished modem firmware and bootup diagnostics
section. ===
=== Next deducing cogent software ===
Predictive diagnostics for card in bus 00:0a.0:
Modem chipset detected on
CLASS="Class 0703: 163c:3052"
NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K
Modem "
PCIDEV=163c:3052
SUBSYS=163c:3052
IRQ=16
IDENT=slamr
For candidate modem in: 00:0a.0
Class 0703: 163c:3052 Modem: Smart Link Ltd.
SmartLink SmartPCI562 56K Modem
Primary PCI_id 163c:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility. Read the
Smartlink.txt and Modem/YourSystem.txt for follow
through guidance.
For 2.6.24 compiling drivers is necessary. As of
October 2007 the current packages at http://linmodems.technion.ac.il/packages/smartlink/
are the
ungrab-winmodem-20070505.tar.gz and
slmodem-2.9.11-20080126.tar.gz
Writing Smartlink.txt
============ end Smartlink section
=====================
Completed candidate modem analyses.
The base of the UDEV device file system is:
/dev/.udev
Versions adequately match for the compiler installed:
4.2.3
and the compiler used in kernel assembly:
4.2.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.24/build
However some compilations and executable functions
may need additional files,
in the FileNames.h (so called kernel "h"eaders)
collection installed in /usr/include/ .
For martian_modem, additional required packages are
libc6-dev (and for Debian/Ubuntu, linux-libc-dev).
The also required headers of package libc6 are
commonly installed by default.
If a driver compilation fails, with message including
some lack of some FileName.h (stdio.h for example),
then
Some additional kernel-header files need installation
to /usr/include. The minimal additional packages are
libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed package
For Debian/Ubuntu related distributions, run the
following command to display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux
partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Read Modem/YourSystem.txt concerning other COMM
channels: ppp0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for the
experts
should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
lrwxrwxrwx 1 root root 10 Mar 16 06:00 /dev/ttySL0 ->
/dev/pts/0
Within /etc/udev/ files:
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",
NAME="modems/mwave", GROUP="uucp"
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist:# ALSA modules to support
sound modems. These should be loaded manually
/etc/modprobe.d/blacklist:blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist:blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf
files:
--------- end modem support lines --------
root@slax:/tmp#
The important lines are
Predictive diagnostics for card in bus 00:0a.0:
Modem chipset detected on
CLASS="Class 0703: 163c:3052"
NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K
Modem "
PCIDEV=163c:3052
SUBSYS=163c:3052
IRQ=16
IDENT=slamr
For candidate modem in: 00:0a.0
Class 0703: 163c:3052 Modem: Smart Link Ltd.
SmartLink SmartPCI562 56K Modem
Primary PCI_id 163c:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility. Read the
Smartlink.txt and Modem/YourSystem.txt for follow
through guidance.
For 2.6.24 compiling drivers is necessary. As of
October 2007 the current packages at http://linmodems.technion.ac.il/packages/smartlink/
are the
ungrab-winmodem-20070505.tar.gz and
slmodem-2.9.11-20080126.tar.gz
Writing Smartlink.txt
============ end Smartlink section
=====================
If you use wvdial.conf you will need lines Carrier Check = no and Stupid Mode = yes and it should look like and also add DNS(Domain nameserver to /etc/resolv.conf). Kppp takes care of this automaticlly, so if wvdial does not work for you, try KPPP but select keep trying to connect till it does, otherwise you will get no carrier.
I had previously tried to connect with slmodem-2.9.11-20080126 and a newer one slmodem-2.9.11-20080226.tar.gz, but both failed to make modem dialout. I changed back to older code and made a little change *line 620 of slmodem-2.9.11-20070813/drivers/amrmo_init.c ***
Line 620 becomes
ret = request_irq(amrmo->irq, &amrmo_pci_interrupt,IRQF_SHARED,
-SA_IRQF
+IRQF_SHARED
When troubleshooting the modem, please try to do the following
When the module is activated, it
complains that the module
slamr.(ko) was not found. Then if one as a user tries
the following, it works, I tried to automate it like
the martian_modem, but it is not working as well as it
should.
if you run dmesg and see
# dmesg
look for
slamr: module license 'Smart Link Ltd.' taints kernel.
slamr: SmartLink AMRMO modem.
slamr: device 163c:3052 is grabbed by another driver
device 163c:3052 is grabbed by driver serial: try to
release
then you have to run
# depmod -a
check for slamr.ko, slusb.ko and ungrab-winmodem.ko in
/lib/modules/2.6.24/extra
root@slax:~# ls -l /lib/modules/2.6.24/extra/
total 571
-rw-r--r-- 1 root root 554688 Mar 16 04:03 slamr.ko
-rw-r--r-- 1 root root 22272 Mar 16 04:03 slusb.ko
-rw-r--r-- 1 root root 6968 Mar 16 04:03
ungrab-winmodem.ko
root@slax:~#
the slmodemd-20070813-for-slax.lzm module which configures smartlink modems, is not working as best it should. I have modified /etc/rc.d/rc.slmodemd to not give error message. I can get it to do that, but module still does not get loaded, configuring a bit makes it work, though.
root@slax:~# activate slmodemd-2.9.11-20070813-for-slax.lzm
module file is stored inside the union, moving to /mnt/live/memory/modules first...
Loading ungrab-winmodem driver from kernel
root@slax:~#
if you run wvdialconf
root@slax:~# wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan: S2 S3
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Stopping it and restarting from command line works
root@slax:~# /etc/rc.d/rc.slmodemd stop
Shutting down SmartLink modem daemon
slmodemd: no process killed
root@slax:~# /etc/rc.d/rc.slmodemd start
Starting SmartLink modem daemon: /usr/sbin/slmodemd
root@slax:~# wvd
wvdial wvdialconf
root@slax:~# wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan: S2 S3
WvModem: Cannot get information for serial port.
ttySL0: ATQ0 V1 E1 -- OK
ttySL0: ATQ0 V1 E1 Z -- OK
ttySL0: ATQ0 V1 E1 S0=0 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySL0: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0: Speed 4800: AT -- OK
ttySL0: Speed 9600: AT -- OK
ttySL0: Speed 19200: AT -- OK
ttySL0: Speed 38400: AT -- OK
ttySL0: Speed 57600: AT -- OK
ttySL0: Speed 115200: AT -- OK
ttySL0: Speed 230400: AT -- OK
ttySL0: Speed 460800: AT -- OK
ttySL0: Max speed is 460800; that should be safe.
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySL0.
/etc/wvdial.conf: Can't open '/etc/wvdial.conf' for reading: No such file or directory
/etc/wvdial.conf: ...starting with blank configuration.
Modem configuration written to /etc/wvdial.conf.
ttySL0: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
root@slax:~#
Here are the modifications that I have made, and hopefully the slmodemd-20070813-for-slax.lzm can be made to work nicely. User needs to remember to turn off eth0 device, ifconfig eth0 down, ifconfig eth1 down, ifconfig ethX down
root@slax:~# cat /etc/rc.d/rc.slmodemd
#!/bin/sh
#
# rc.slmodemd
#
# Start slmodemd daemon for SmartLink
#
# SLMODEMD_DEVICE=/dev/slusb0 was set to /dev/slamr0
# modified by Antonio A. Olivares
# olivares14031@yahoo.com
# run depmod -a to ensure modules become available
/sbin/depmod -a
sleep 3
# check to see if ungrab-winmodem is running, otherwise load it
if [ `/sbin/lsmod | grep -c ${UNGRAB_DEVICE}` -lt "1" ]; then
echo "Loading ungrab-winmodem driver from kernel"; modprobe ungrab-winmodem;
exit 0
fi
# check to see if slamr is running, otherwise load it
if [ `/sbin/lsmod | grep -c ${SLAMR_DEVICE}` -lt "1" ]; then
echo "slamr module is not loaded!"; modprobe slamr;
exit 0
fi
# create /dev/slamr0 if it does not exist
if [ ! -e $SLMODEMD_DEVICE ]; then
mkdir -p /dev
mknod -m 600 /dev/slamr0 c 242 0
fi
slmodemd_start()
{
if [ -x /usr/sbin/slmodemd ]; then
echo -n "Starting SmartLink modem daemon: "
echo "/usr/sbin/slmodemd"
/usr/sbin/slmodemd --country=$SLMODEMD_COUNTRY $SLMODEMD_DEVICE 1>/dev/null 2>/dev/null &
fi
}
if [ "$SLMODEMD_DEVICE" ]; then readonly SLMODEMD_DEVICE; fi
if [ -z $SLMODEMD_DEVICE ]; then
echo "slmodemd: SLMODEMD_DEVICE not set. You can set it in /etc/rc.d/rc.slmodemd file or as environment variable."
exit 5
fi
I am working on it, and I am close to getting it better. I will try to send a newer slmodemd-2.9.11-20070813-for-slax.lzm to get into modules pages after the fixes and a better way to make it work.
I got it to work. I am going to send new module to SonofFree's GSpace account *delete old one* and to MChopper and all who need it.
This is the new rc.slmodemd that activates slmodemd when module is activated. One little thing is that user needs to close all ethX devices to achieve a good connection, and configure /etc/resolv.conf with nameservers to achieve a good connection.
root@slax:~# cat /etc/rc.d/rc.slmodemd
#!/bin/sh
#
# rc.slmodemd
#
# Start slmodemd daemon for SmartLink
#
# SLMODEMD_DEVICE=/dev/slusb0 was set to /dev/slamr0
# modified by Antonio A. Olivares
# olivares14031@yahoo.com
if [ "$SLMODEMD_DEVICE" ]; then readonly SLMODEMD_DEVICE; fi
if [ -z $SLMODEMD_DEVICE ]; then
echo "slmodemd: SLMODEMD_DEVICE not set. You can set it in /etc/rc.d/rc.slmodemd file or as environment variable."
exit 5
fi
case "$1" in
'start')
slmodemd_start
;;
'stop')
slmodemd_stop
;;
'restart')
slmodemd_restart
;;
*)
echo "usage $0 start|stop|restart"
esac
root@slax:~#
root@slax:~# activate slmodemd-20070813.lzm
module file is stored inside the union, moving to /mnt/live/memory/modules first...
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
root@slax:~# activate wvdial-1.60.lzm
module file is stored inside the union, moving to /mnt/live/memory/modules first...
root@slax:~# wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan: S2 S3
WvModem: Cannot get information for serial port.
ttySL0: ATQ0 V1 E1 -- OK
ttySL0: ATQ0 V1 E1 Z -- OK
ttySL0: ATQ0 V1 E1 S0=0 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySL0: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0: Speed 4800: AT -- OK
ttySL0: Speed 9600: AT -- OK
ttySL0: Speed 19200: AT -- OK
ttySL0: Speed 38400: AT -- OK
ttySL0: Speed 57600: AT -- OK
ttySL0: Speed 115200: AT -- OK
ttySL0: Speed 230400: AT -- OK
ttySL0: Speed 460800: AT -- OK
ttySL0: Max speed is 460800; that should be safe.
ttySL0: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySL0.
/etc/wvdial.conf: Can't open '/etc/wvdial.conf' for reading: No such file or directory
/etc/wvdial.conf: ...starting with blank configuration.
Modem configuration written to /etc/wvdial.conf.
ttySL0: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
root@slax:~#
If you use slmodemd-2.9.11-20070813-slax-6.0.3.lzm*
After connected for a while, and you disconnect and then try again, and you see
root@slax:~# wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.
Try to restart slmodemd by doing the following:
root@slax:~# /etc/rc.d/rc.slmodemd stop
root@slax:~# /etc/rc.d/rc.slmodemd start or
root@slax:~# /etc/rc.d/rc.slmodemd restart
root@slax:~# /etc/rc.d/rc.slmodemd stop
Shutting down SmartLink modem daemon
root@slax:~# /etc/rc.d/rc.slmodemd start
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
/usr/bin/mknod: `/dev/slamr0': File exists
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
root@slax:~# wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
OK
--> Modem initialized.
--> Sending: ATDT7072000
--> Waiting for carrier.
ATDT7072000
CONNECT 49333
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Wed Mar 19 01:55:48 2008
--> Pid of pppd: 28051
--> Using interface ppp0
--> pppd: ø§[06][08]°ª[06][08]
--> pppd: ø§[06][08]°ª[06][08]
--> pppd: ø§[06][08]°ª[06][08]
--> pppd: ø§[06][08]°ª[06][08]
--> local IP address 66.201.10.226
--> pppd: ø§[06][08]°ª[06][08]
--> remote IP address 66.201.8.7
--> pppd: ø§[06][08]°ª[06][08]
--> primary DNS address 66.201.0.203
--> pppd: ø§[06][08]°ª[06][08]
--> secondary DNS address 66.94.120.9
--> pppd: ø§[06][08]°ª[06][08]
and you get that above, Then you need to check if slamr.ko,slusb.ko, and ungrab-winmodem.ko exist in /lib/modules/2.6.24.3/extra/
root@slax:~# ls -l /lib/modules/2.6.24.3/extra/
total 571
-rw-r--r-- 1 root root 554560 Mar 18 22:32 slamr.ko
-rw-r--r-- 1 root root 22272 Mar 18 22:32 slusb.ko
-rw-r--r-- 1 root root 6840 Mar 18 22:32 ungrab-winmodem.ko
root@slax:~#
I test the module by doing
root@slax:~# ls -l
total 572
drwx---r-x 2 root root 47 Nov 16 10:26 Desktop/
-rw-r--r-- 1 root root 577536 Mar 20 14:06 slmodemd-2.9.11-20070813-slax-6.0.3.lzm
root@slax:~# activate slmodemd-2.9.11-20070813-slax-6.0.3.lzm
module file is stored inside the union, moving to /mnt/live/memory/modules first...
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
root@slax:~# ls /dev/ttySL0 -l
lrwxrwxrwx 1 root root 10 Mar 20 14:07 /dev/ttySL0 -> /dev/pts/2
root@slax:~#
It does not happen in my case, it did happen with the previous module, something was not loading properly.
root@slax:~# /etc/rc.d/rc.slmodemd stop
Shutting down SmartLink modem daemon
root@slax:~# /etc/rc.d/rc.slmodemd start
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
/usr/bin/mknod: `/dev/slamr0': File exists
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
root@slax:~# /etc/rc.d/rc.slmodemd restart
Shutting down SmartLink modem daemon
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
/usr/bin/mknod: `/dev/slamr0': File exists
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
Wrong link, sorry blues. Your correction is right it is the slmodemd-2.9.11-20070813-slax-6.0.3.lzm. The above still applies. Last night I connected. Then disconnected. This morning I tried to connect and got the message Modem Not Responding. So I restarted and all is well. Note I use wvdial this is what I see. "--> Modem not responding.", If you use KPPP, please select the following options:
To summarize what was done to configure KPPP this is what is done.
(1) Click on configure
(2) Click on manual setup
(3) Type Connection Name and Phone No.
(4) Leave everything else as is.
(5) Next click on modems New
(6) and type slmodemd and choose ttySL0 as the device
then click on modem tab
you then click on Modem Commands
Initialization string 2:
(10) Type ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 and click OK and OK again
You will return back to this screen
(11) Click on Misc Tab and check tab with "dock into panel" and "Automatic redial on NO CARRIER"
(12) Click on OK
(13) Type in Connection Name and Password
root@slax:~# wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
OK
--> Modem initialized.
--> Sending: ATDT7072000
--> Waiting for carrier.
ATDT7072000
CONNECT 49333
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Mar 21 02:18:46 2008
--> Pid of pppd: 18666
--> Using interface ppp0
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> local IP address 66.201.10.162
--> pppd: àk[06][08]è§[06][08]
--> remote IP address 66.201.8.7
--> pppd: àk[06][08]è§[06][08]
--> primary DNS address 66.201.0.203
--> pppd: àk[06][08]è§[06][08]
--> secondary DNS address 66.94.120.9
--> pppd: àk[06][08]è§[06][08]
Caught signal 2: Attempting to exit gracefully...
--> Terminating on signal 15
--> pppd: àk[06][08]è§[06][08]
--> Connect time 50.4 minutes.
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> Disconnecting at Fri Mar 21 03:09:14 2008
root@slax:~# wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.
root@slax:~# /etc/rc.d/rc.slmodemd stop
Shutting down SmartLink modem daemon
root@slax:~# /etc/rc.d/rc.slmodemd start
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
/usr/bin/mknod: `/dev/slamr0': File exists
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
root@slax:~# lsmod | grep slamr
slamr 427816 2
root@slax:~# wvd
wvdial wvdialconf
root@slax:~# wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
OK
--> Modem initialized.
--> Sending: ATDT7072000
--> Waiting for carrier.
ATDT7072000
CONNECT 50667
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Mar 21 13:47:23 2008
--> Pid of pppd: 24257
--> Using interface ppp0
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> local IP address 66.201.10.76
--> pppd: àk[06][08]è§[06][08]
--> remote IP address 66.201.8.7
--> pppd: àk[06][08]è§[06][08]
--> primary DNS address 66.201.0.203
--> pppd: àk[06][08]è§[06][08]
--> secondary DNS address 66.94.120.9
--> pppd: àk[06][08]è§[06][08]
thanks tonio for your help.
so, here is the problem: it cannot find the slamr module because there is no 'extra' directory under /lib/modules/2.6.24.3/
there is one under /lib/modules/2.6.24/ so i tried moving it into 2.6.24.3 but then when restarting the slmodemd it gives an incorrect module error.
what can i do? how to get the correct version?
and why do i have the wrong version by the way?
PS. i must say that i had 6.0.2 installed and i "upgraded" to 6.0.3 by overwriting all the files (slax and boot directories). i just kept the slaxsave.dat changes.
this may be the problem?
so, here is the problem: it cannot find the slamr module because there is no 'extra' directory under /lib/modules/2.6.24.3/
there is one under /lib/modules/2.6.24/ so i tried moving it into 2.6.24.3 but then when restarting the slmodemd it gives an incorrect module error.
what can i do? how to get the correct version?
and why do i have the wrong version by the way?
but not in slax 6.0.3. Slax 6.0.3 has 2.6.24.3 kernel while slax 6.0.2 has 2.6.24 that is why the module is incorrect. If you switch to the Misc page and scroll to the bottom in bhunter736's(Brad's) page,
you will find a slmodemd-2.9.11-20070813-slax-6.0.3.lzm which should work with slax-6.0.3. There are minor quirks of course, the modem sometimes does not respond and one has to stop and start modem again to gain functionality back
root@slax:~# /etc/rc.d/rc.slmodemd start
Loading ungrab-winmodem driver from kernel
Creating /dev/slamr0 for slmodemd
/usr/bin/mknod: `/dev/slamr0': File exists
Modprobing slamr
Starting SmartLink modem daemon: /usr/sbin/slmodemd
But once connected, I have surfed a good time. Sometimes the line gets dropped and the connection dies, so I restart modem again using the above code and connect again.
root@slax:~# wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
OK
--> Modem initialized.
--> Sending: ATDT7072000
--> Waiting for carrier.
ATDT7072000
CONNECT 46667
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sat Mar 22 00:02:42 2008
--> Pid of pppd: 21785
--> Using interface ppp0
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> local IP address 66.201.10.157
--> pppd: àk[06][08]è§[06][08]
--> remote IP address 66.201.8.7
--> pppd: àk[06][08]è§[06][08]
--> primary DNS address 66.201.0.203
--> pppd: àk[06][08]è§[06][08]
--> secondary DNS address 66.94.120.9
--> pppd: àk[06][08]è§[06][08]
Caught signal 2: Attempting to exit gracefully...
--> Terminating on signal 15
--> pppd: àk[06][08]è§[06][08]
--> Connect time 154.0 minutes.
--> pppd: àk[06][08]è§[06][08]
--> pppd: àk[06][08]è§[06][08]
--> Disconnecting at Sat Mar 22 02:36:40 2008
Change to the new slmodemd file and report back. Hopefully it will work for you.
thanks again tonio.
i had the correct module for 6.0.3, but to cut any doubt i downloaded it again.
it still didn't work.
so, i tried starting a fresh Slax without changes and configuring again the modem, and everything went into place, now it works. i can't understand why, though.
i hope i will not have to trash my slaxsave.dat at each Slax new version...
