modem acerferrari 3200 e k.2.6.7

[trapanator]

Originariamente inviato da ^[H3ad-Tr1p]^
ecco,qualcosa in + e' successo
ho copiato il tar nella home ed infatti mi ha compilato correttamente i sorgenti,xo' mi ha cmq restituito 1 errore
vi posto qui il risultato con l errore,come vedete e' 1 po' meglio dell altro ma continua a nn andare


root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10# make install
make -C modem all
make[1]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.7/build
make[1]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
cc -I/lib/modules/2.6.7/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.7
make[2]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make modules -C /lib/modules/2.6.7/build SUBDIRS=/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers
make[3]: Entering directory `/usr/src/linux-2.6.7'
Makefile:434: .config: No such file or directory
Building modules, stage 2.
/usr/src/linux-2.6.7/scripts/Makefile.modpost:38: .config: No such file or directory
make[4]: *** No rule to make target `.config'. Stop.
make[3]: *** [modules] Error 2
make[3]: Leaving directory `/usr/src/linux-2.6.7'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make: *** [drivers] Error 2
root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10#

Mancano i sorgenti del kernel....
.config è il file che contiene le scelte che hai fatto.

Prova a fare :

ls /usr/src/linux/.config

[^[H3ad-Tr1p]^]

Originariamente inviato da trapanator
Mancano i sorgenti del kernel....
.config è il file che contiene le scelte che hai fatto.

Prova a fare :

ls /usr/src/linux/.config

siccome ho installato il kernel 2.6. nn ricordo se ho scelto di installare i sorgenti oppure no

ls /usr/src/linux/.config mi dice che nn esiste,xo' in usr/src/ e' presente 1 dir che si chiama /linux che xo' e' 1 collegamento (credo) che punta a linux 2.6.7;all interno di quest ultima e' presente 1 file che si chiama .config.cmd
adesso nn so se e' la stessa cosa

se in caso i sorgenti del kernell nn li ho installati li posso installare ora?e come?

[trapanator]

Originariamente inviato da ^[H3ad-Tr1p]^
siccome ho installato il kernel 2.6. nn ricordo se ho scelto di installare i sorgenti oppure no

ls /usr/src/linux/.config mi dice che nn esiste,xo' in usr/src/ e' presente 1 dir che si chiama /linux che xo' e' 1 collegamento (credo) che punta a linux 2.6.7;all interno di quest ultima e' presente 1 file che si chiama .config.cmd
adesso nn so se e' la stessa cosa

se in caso i sorgenti del kernell nn li ho installati li posso installare ora?e come?

installali si trovano sul testing...

mettiti nel cd della slackware in questa cartella:

/testing/source/linux-2.6.x/

e fai

installpkg linux-2.6.7.tar.bz2

da root.

[^[H3ad-Tr1p]^]

Originariamente inviato da trapanator
installali si trovano sul testing...

mettiti nel cd della slackware in questa cartella:

/testing/source/linux-2.6.x/

e fai

installpkg linux-2.6.7.tar.bz2

da root.

ho fatto in 1 altro modo ed ha funzato
ho postato il messggio poi ho fatto partire la slack e mi son riletto le istruzioni che ho usato x installare il 2.6.7
adesso nelle mie dir c'e' 1 casino da cinema,c'e' il vecchio kernel il nuovo eccc ecc...ma mi sono accorto che sulle istruzioni mi diceva di spostare il .config in /boot

nn ho capito xche' da boot facendo copia e incolla il file in /linux quando lo andavo ad aprire,anche se era in /linux puntava alla dir originale /boot da dove lo avevo copiato...cmq ne ho creato 1 nuovo e dal file .config presente in boot ho copiato il contenuto del file nel .config nuovo in /linux

ora mi ha installato i drive...xo' adesso il modem continua a nn funzare

prima di spararmi mi sai dire come fare a farlo funzare?nel senso che usando kppp ho messo tutte le impostazioni dell account ,faccio interroga modem e settato come /ttysy (mi sembra xche' x il momnto scrivo ancora da win che ho sullo stesso pc) ed il modem viene rilavato
quando faccio "connetti"mi dice inizializzazione modem e rimane cosi' in eterno senza che mi componga il numero

/dev/modem nn funziona
ho provato a montare /dev/modem ma mi dice che nn lo trova ne in fstab che in mntab

in questi file xo' ho sempre montato periferiche di archiviazione o partizioni,1 periferica di questo tipo come la monto visto che nei file in questione ti chiede il tipo di filesystem ecc ecc..?

cmq fai tu

nelle specifiche tecniche mi dice "Modem integrato 56K V.92 (con approvazione internazionale PTT), Wake-on-Ring ready " nn so se e' 1 modem normale o 1 win modem che mi sembra diano dei problemi


tnx cmq,ancora qualche passo e se riesco a far funzare il modem x connnettermi in rete posso quasi levare win

[trapanator]

dopo aver fato make install fai:

modprobe slamr

e fai lsmod
dimmi cosa ti dice la riga con 'slamr' (o slmodem) alla prima colonna

[^[H3ad-Tr1p]^]

Originariamente inviato da trapanator
dopo aver fato make install fai:

modprobe slamr

e fai lsmod
dimmi cosa ti dice la riga con 'slamr' (o slmodem) alla prima colonna

questo e' l output completo...ho gia installato con checkinstal ma facendo make install sembra installare cmq...va be',questo poi lo vedo in 1 altro momento

cmq con slmodem mi dice che il modulo nn c e'


root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10# make install
make -C modem all
make[1]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/modem'
make[1]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.7/build
make[1]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
cc -I/lib/modules/2.6.7/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.7
make[2]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make modules -C /lib/modules/2.6.7/build SUBDIRS=/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers
make[3]: Entering directory `/usr/src/linux-2.6.7'
Building modules, stage 2.
MODPOST
make[3]: Leaving directory `/usr/src/linux-2.6.7'
make[2]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make[1]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make install -C drivers KERNEL_DIR=/lib/modules/2.6.7/build
make[1]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
cc -I/lib/modules/2.6.7/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 -m 600 /dev/slamr2 c 212 2 ; mknod -m 600 /dev/slamr3 c 212 3 ; echo -n
mknod: `/dev/slamr0': File exists
mknod -m 600 /dev/slusb0 c 213 0 ; mknod -m 600 /dev/slusb1 c 213 1 ; mknod -m 600 /dev/slusb2 c 213 2 ; mknod -m 600 /dev/slusb3 c 213 3 ; echo -n
make install KERNEL_VER=2.6.7
make[2]: Entering directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
install -D -m 644 slamr.ko /lib/modules/2.6.7/extra/slamr.ko
install -D -m 644 slusb.ko /lib/modules/2.6.7/extra/slusb.ko
/sbin/depmod -a
make[2]: Leaving directory `/home/Headtrip/z_VARIE/drive/slmodem-2.9.10/drivers'
make[1]: Leaving directory `/home/Headtrip/z_VARIE/drive/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
root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10# modprobe slamr
root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10# modprobe slmodem
FATAL: Module slmodem not found.
root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10# lsmod
Module Size Used by
ipv6 283904 14
ohci_hcd 38404 0
pciehp 100620 0
pci_hotplug 13700 1 pciehp
slamr 410952 0
ds 21896 4
yenta_socket 22528 0
pcmcia_core 74312 2 ds,yenta_socket
rtc 18124 0
joydev 11200 0
evdev 10880 0
root@darkstar:/home/Headtrip/z_VARIE/drive/slmodem-2.9.10#

[trapanator]

dopo modprobe slasr fai dmesg.
Dimmi cosa ti dicono le ultime 10 righe

[^[H3ad-Tr1p]^]

Originariamente inviato da trapanator
dopo modprobe slasr fai dmesg.
Dimmi cosa ti dicono le ultime 10 righe

qui ci sono le ultime 1 po + di 10 ma nn tante

ALSA sound/pci/via82xx.c:737: invalid via82xx_cur_ptr, using last valid pointer
[ACPI Debug] String: Length 0x12, "CMBatt - _BST.BAT1"
[ACPI Debug] String: Length 0x08, "QUERY_09"
[ACPI Debug] String: Length 0x0D, "CMBatt - SMSL"
[ACPI Debug] Integer: 0x0000000000000FE1
[ACPI Debug] String: Length 0x12, "CMBatt - CHBP.BAT1"
[ACPI Debug] String: Length 0x1B, "CMBatt - BAT1 still present"
[ACPI Debug] String: Length 0x12, "CMBatt - UPBI.BAT1"
[ACPI Debug] Package: Size 0x0D Elements Ptr - f7a84e28
[ACPI Debug] String: Length 0x12, "CMBatt - UPBS.BAT1"
[ACPI Debug] Package: Size 0x04 Elements Ptr - f7a83680
[ACPI Debug] String: Length 0x12, "CMBatt - UPBH.BAT1"
[ACPI Debug] Package: Size 0x03 Elements Ptr - f7ffc144
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"

[trapanator]

Originariamente inviato da ^[H3ad-Tr1p]^
qui ci sono le ultime 1 po + di 10 ma nn tante

ALSA sound/pci/via82xx.c:737: invalid via82xx_cur_ptr, using last valid pointer
[ACPI Debug] String: Length 0x12, "CMBatt - _BST.BAT1"
[ACPI Debug] String: Length 0x08, "QUERY_09"
[ACPI Debug] String: Length 0x0D, "CMBatt - SMSL"
[ACPI Debug] Integer: 0x0000000000000FE1
[ACPI Debug] String: Length 0x12, "CMBatt - CHBP.BAT1"
[ACPI Debug] String: Length 0x1B, "CMBatt - BAT1 still present"
[ACPI Debug] String: Length 0x12, "CMBatt - UPBI.BAT1"
[ACPI Debug] Package: Size 0x0D Elements Ptr - f7a84e28
[ACPI Debug] String: Length 0x12, "CMBatt - UPBS.BAT1"
[ACPI Debug] Package: Size 0x04 Elements Ptr - f7a83680
[ACPI Debug] String: Length 0x12, "CMBatt - UPBH.BAT1"
[ACPI Debug] Package: Size 0x03 Elements Ptr - f7ffc144
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"
[ACPI Debug] String: Length 0x08, "QUERY_20"

azz... questo e' l'output di ACPI, proprio quello che non mi interessa mi servirebbe quello di slasr (dovresti trovare qualcosa con questa parola)

[^[H3ad-Tr1p]^]

Originariamente inviato da trapanator
azz... questo e' l'output di ACPI, proprio quello che non mi interessa mi servirebbe quello di slasr (dovresti trovare qualcosa con questa parola)

infatti mi sembrava strano che volessi queste righe,le righe di slasr le avevo trovate,volevo postarle ...adesso provvedo

[^[H3ad-Tr1p]^]

nn me lo da +
la prima volta che lo avevo fatto mi aveva dato qualcosa che riguardava slmodem ma adesso mi da solo acpi e driver alsa

come mai

[^[H3ad-Tr1p]^]

ho usato 1 softwerino di test che ho trovato su http://linmodems.org e che produce 6 file .txt dei quali quello di testing (e' 1 po' lungo ma te lo ripropongo)
io in eng faccio x ora ancora molta fatica ma mi sembra di aver capito che dopo l installazione di slmodem che mi viene supportato dovrei ricompilare il kernel in modo da attivare il modulo in questione o qualcosa del genere

nn ho ben capito se devo ricompilare o installare altro

mi saprai dire ?


MODEM TESTING

0) Please install the Smart tester/dialer package WVDIAL.
It enables an automated functionality test of the ModemDriver + Hardware combination. Open a console and login with
# su - root
Then run the test
# wvdialconf /etc/wvdial.conf
which checks ports with name format /dev/ttySn, with a success output looking like:
ttySLT0<*1>: ATQ0 V1 E1 -- OK
ttySLT0<*1>: ATQ0 V1 E1 Z -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
etc.
The /etc/wvdial.conf written looks like:
[Dialer Defaults]
Modem = /dev/ttySLT0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password>

For systems using the SmartLink slmodem drivers,
the following line should be added to its /etc/wvdial.conf
Carrier Check = no
So after editing in your personal information:
[Dialer Defaults]
Modem = /dev/ttySLT0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = DialupPhoneNumber
Username = Your_Login_Name
# for MSN.net, use instead
# Username = MSN/Your_Login_Name
Password = Your_Password
# if usging the SmartLink slmodem drivers, uncomment:
# Carrier Check = no

The lines above beginning with " # " are not read as code.
Remove the " # " to activate a line. Then try getting on line with:
# wvdial


A dial out with wvdial will then display like:
# wvdial &
--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 M1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT3019178111
--> Waiting for carrier.
ATDT3019178111
CONNECT 53333 V42bis
--> Carrier detected. Waiting for prompt.
** APX1.LNH.MD.RCN.NET Terminal Server **
Login:
--> Looks like a login prompt.
--> Sending: marvstod
marvstod
Password:
--> Looks like a password prompt.
--> Sending: (password)
Entering PPP Session.
IP address is 66.44.1.6
MTU is 1006.
--> Looks like a welcome message.
--> Starting pppd at Sat Jul 26 13:59:03 2003
--> pid of pppd: 2404
: pppd 2.4.1 started by root, uid 0
: Using interface ppp0
: Connect: ppp0 <--> /dev/tts/LT0
: kernel does not support PPP filtering
Jul 26 13:59:08 stodolsklap kernel: PPP BSD Compression module registered
Jul 26 13:59:08 stodolsklap kernel: PPP Deflate Compression module registered
: local IP address 66.44.1.6
: remote IP address 208.59.89.132
: primary DNS address 207.172.3.8

The & above puts the process in the background,
allowing further usage of the command prompt. To stop a backgrounded process:
# fg wvdial
# Ctrl -C

The following steps should be worked through in case of a failure.

1) Check for a symbolic link:
ls -l /dev/modem
which should display something like
/dev/modem --> /dev/WinModemPort
Some Distros may set a default
/dev/modem --> /dev/ttyS0 (or 1,2,3)
which are for Controller Chip modems only.
If represent,as Root:
# rm -f /dev/modem
# ln -s /dev/WinModemPort /dev/modem
If may prove necessary to disable a default BOOT UP setup for Controller Chip modems,
to prevent resetting of the unwanted default link.
Note that the Smartlink slmodem ports are an exception. The /dev/modem link should be set as:
ln -s /dev/ttySL0 /dev/modem

2) Loading drivers
Do FIRST read INSTRUCTIONS files provided with the modem driver resource.
Some may have installed to /usr/share/doc/Modem_or_Driver_Name/
For RPM using distros, documentation files will be listed through
rpm -q -d packageName (less the version part, sometimes)
and all directly installed files can be listed by
rpm -q -l packageName
Depending upon your installation, the modem drivers may/may_not be autoloaded.
Login as Root in a console with:
# su - root
# lsmod
If the modem drivers are not already loaded onto the kernel, insert them with command
# modprobe ModuleDriver
If there are multiple drivers such as the lt_modem.o and lt_serial.o pair,
inserting the serial like driver first
# modprobe lt_serial
ALSO will autoload all modules it depends on, through a reading of dependency files
written to /lib/modules/2.6.7/ during boot up through the "depmod -a" command.
In constrast
# insmod lt_serial
would only attempt loading of that single driver and will FAIL, if its dependency on
lt_modem.o has been satisfied by prior lt_modem.o insertion.

3) Do read "man wvdial" and /usr/share/doc/vwdial documentation
sometime browse the documentation that is written to /usr/share/doc/wvdial/
Therein are instructions for setting up alternative dialouts.

%%% This wvdialconf action if successful generates the files:
/etc/ppp/peers/wvdial
/etc/ppp/peers/wvdial-pipe
in addition to the /etc/wvdial.conf

Many Users prefer to use the dialout utility KPPP. This is fine.
But each User MUST run the configuration process separately.
In principle, different Users on the same Linux System could
have different Internet providers and/or use different modems.

4) Preparation for dialout if other COMM modes are active.
Concurrent ethernet capability will compete for
the Domain Name Service (DNS) needed for browser naviagation. So as root:
# /sbin/ifconfig eth0 down
before starting a dialout!
With a Mandrake installation, it will be necessary to:
# /etc/init.d/network stop

5) Internet clients such as Netscape, Mozilla, Explorer etc.
should be CLOSED during your first dial out trials.
Should a URL on the Internet be specifed as the default URL/connect,
then the Client may compete with ppp for connectivity functions.
After PPP functionality has been verified, the effects of opened
or launched browsers can be checked

If you have installed the DIALD (dial on demand) package, stop it for initial tests:
# /etc/init.d/diald stop
Otherwise diald function will be initiated with modem usage,
and could compilate issues. Test diald only after ppp by itself is fine.

If your internet provider assigns DNS dynamically then add to /etc/ppp/options:
usepeerdns

To analyze a dialout attempt, it is useful to display kernel messages with:
# tail -f /var/log/messages &
The & puts the commanded process in the "background" allowing recovery of the command prompt.

Some dialer packages (kppp etc) may automate the above steps.


6) Note that for some Linux distributions (Mandrake for one),
maintain modules in compressed module.gz format, if modem service was not specified
during the Linux installation. A subsequent installation of any dialer package:
wvdial - PPP dialer with built-in intelligence.
kppp - PPP dialer for KDE
dtmfdial - A DTMF Tone Dialer
gkdial - Gtk-based PPP dial-up configuration tool.
gkdial-gnome - GNOME-based PPP dial-up configuration tool.
masqdialer - daemon for remote control of masqueraded dialup links
will stimulate unpacking of ppp related modules during bootup.

The cogent ppp related modules loaded during such a CONNECT are displayed within the output from:
# lsmod
ppp_deflate 3512 1 (autoclean)
zlib_inflate 18980 0 (autoclean) [ppp_deflate]
zlib_deflate 18648 0 (autoclean) [ppp_deflate]
bsd_comp 4440 0 (autoclean)
ppp_async 7744 1 (autoclean)
ppp_generic 16380 3 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 5264 1 (autoclean) [ppp_generic

For ealier 2.4.nn kernels, loading of these modules may require the following lines within
/etc/module.conf :
### automate ppp modules loading ###
alias /dev/ppp ppp_generic
alias char-major-108 ppp_generic
alias tty-ldisc-3 ppp_async
alias tty-ldisc-14 ppp_synctty
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
### end ppp block ####
For more recent kernels with their modutils,
these lines are no longer needed.

7) For potential causes of a NO DIALTONE failure, read the Post-install.html
at http://linmodems.technion.ac.il/ Not setting the Country Code may be
and additional problem.

COUNTRY CODE Issues
====================
The modem which you purchase locally or abroad may not be preset
with the proper Country Code setting. An incorrect setting can
hinder acquisition of dial tone.
Inclusion of an X3 (dial without wainting) in the modem Init string
of under wvdial, including in /etc/wvdial.conf a line
Stupid Mode = yes

Dialtone recognition depends on the setting of country
and/or local phone line equipment.

To properly get dialtone for your country phone experiment use
AT+GCI=xx where xx is country code in hexidecimal format.
Theoretically there could be 256 different countries but
not all are valid. Tables in manuals are way off date,
you have to write a small script to try all combinations
for yourself if you can't guess by chance.

After country select you can check textual name of the country it represents.
For example:
at+gci=00
OK
ati9
Japan

If you can't find exact country, choose the nearest one available.
Nearby countries tend to have similar equipment and compatible dialtones.

These comments from: Emard <emard@softhome.net>
=================

8) After a successful CONNECT, the Domain Name Service (DNS) needed
for Browser navigation can be checked with:
# ping corel.com
PING corel.com (206.47.20.85): 56 data bytes
64 bytes from 206.47.20.85: icmp_seq=0 ttl=52 time=209.1 ms
64 bytes from 206.47.20.85: icmp_seq=1 ttl=52 time=189.9 ms
64 bytes from 206.47.20.85: icmp_seq=2 ttl=52 time=180.0 ms
64 bytes from 206.47.20.85: icmp_seq=3 ttl=52 time=179.9 ms
# Ctrl-C
aborts ping
--- corel.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 179.9/189.7/209.1 ms

# ping 206.47.20.85
PING 206.47.20.85 (206.47.20.85): 56 data bytes
64 bytes from 206.47.20.85: icmp_seq=0 ttl=52 time=179.8 ms
64 bytes from 206.47.20.85: icmp_seq=1 ttl=52 time=190.0 ms
64 bytes from 206.47.20.85: icmp_seq=2 ttl=52 time=170.0 ms
# Ctrl-C
aborts ping

Should there be a success with:
# ping 206.47.20.85
BUT a failure with the named address:
ping corel.com
Then DNS has not been acquired.
Note that failure to stop ethernet service
# /sbin/ifconfig eth0 down
before starting a dialout, will commonly block DNS under ppp.

To terminate the wvdial session, bring the action to the foreground (fg):
# fg wvdial
Ctrl-C to terminate:
wvdial
Caught signal #2! Attempting to exit gracefully...
: secondary DNS address 207.172.3.9
: Terminating on signal 15.
: Connection terminated.
: Connect time 7.8 minutes.
--> Disconnecting at Sat Jul 26 14:06:53 2003

9) The Debian distribution provides a utility:
# pppconfig
for setting up a chatscript for ppp initiation.
Most dialers do use chatscripts and will produce similar records.
Below is the record of a dial out initiated by:

# pon
: pppd 2.4.1 started by marv, uid 1000
: abort on (BUSY)
: abort on (NO CARRIER)
: abort on (VOICE)
: abort on (NO DIALTONE)
: abort on (NO DIAL TONE)
: abort on (NO ANSWER)
: abort on (DELAYED)
: send (ATZ^M)
: expect (OK)
: ATZ^M^M
: OK
: -- got it
: send (ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M)
: expect (OK)
: ^M
: ATQ0V1E1M0S0=0W2&C1&D2+FCLASS=0^M^M
: OK
: -- got it
: send (ATDT3019178111^M)
: expect (CONNECT)
: ^M
: ATDT3019178111^M^M
: CONNECT
: -- got it
: send (\d)
: Serial connection established.
: Using interface ppp0
: Connect: ppp0 <--> /dev/modem
: kernel does not support PPP filtering
Jul 26 14:08:39 stodolsklap kernel: PPP BSD Compression module registered
Jul 26 14:08:39 stodolsklap kernel: PPP Deflate Compression module registered
: local IP address 66.44.1.195
: remote IP address 208.59.89.132
: primary DNS address 207.172.3.8

Once your first CONNECT has been established, than in the future if should suffice
just to use your dialer of choice: wvdial , kppp .gnomeppp or whatever.

Good surfing to you.

10) GENERAL ITEMS

If attemped insertion of a modem driver evokes a complaint like:
unresolved symbol do_SAK_R9a0bcb74
then the kernel-headers using in compiling the modem drivers
do not match those of your current kernel whose KernelVersion is displayed by:
uname -r
and whose kernel config file is often located at /boot/config-KernelVersion
The section above "COMPILING DRIVERS, for Newbies" relates how to make corrections.

There are definitely IPs whose login protocols are Linux hostile.
If you cannot achieve a login, try another Internet Provider (IP).
or ask for someone on discuss@linmodems.org to test your IP.

Many driver packages provide for loading modem drivers on bootup.
Here is a description on how to set it up, if necessary:
http://linmodems.technion.ac.il/arch.../msg00451.html

PLEASE include the diagnostic output of the following Root command in any problem reports:
# setserial -agv /dev/ttyS*

For instructions on having modem drivers loaded on bootup,
particularly the SmartLink slmodem drivers see:
http://linmodems.technion.ac.il/arch.../msg00451.html
For automated removel of drivers after a PPP session see:
http://linmodems.technion.ac.il/arch.../msg00145.html

For general upto date advice:
http://linmodems.technion.ac.il/
http://linmodems.technion.ac.il/resources.html
available in Russian at http://linmodems.nm.ru
for a general PCI_ID database
http://www.pcidatabase.com/
the original Linux winmodems URL is:
http://linmodems.org
with a mailing list on Winmodems:
discuss@linmodems.org
whose archives can be searched at:
http://linmodems.technion.ac.il/ (near bottom of the page)
There is an extensive modem database at:
http://start.at/modem/
Locate your local Linux groups through:
http://www.linux.org/groups/index.html
USB modem information: http://www.linux-usb.org/USB-guide/x332.html
Laptop users should browase http://tuxmobil.org/modem_linux_add1.html
For debugging ppp:
http://www.cisco.com/warp/public/471...gotiation.html

---------- end FOLLOW UP STEPS ---------------

[^[H3ad-Tr1p]^]

1 domanda

ma il modem come lo chiamo se le TTYxx sono seriali?

io ho provato a montarlo con ls -s /dev/ttySLT0 /dev/modem

xo' mi dice anche che nn e' montato in fstab ed in mntab

nn ci capisco + 1 cazzo

[trapanator]

Originariamente inviato da ^[H3ad-Tr1p]^
1 domanda

ma il modem come lo chiamo se le TTYxx sono seriali?

io ho provato a montarlo con ls -s /dev/ttySLT0 /dev/modem

xo' mi dice anche che nn e' montato in fstab ed in mntab

nn ci capisco + 1 cazzo

c'e' scritto anche nel README del pacchetto del modem

per i modem USB sono i /dev/tts/ttsUSB0

per gli altri (come il tuo) /dev/tts/ttsA e qualcosa

(comunque guarda nel readme)

poi devi linkare il /dev/modem a quello:

ln -s /dev/tts/ttsUSB0 /dev/modem

e vedrai che ti funziona, se ti funziona!