Re: Modem Scan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I am doing this - on the other hand what seems to happen is that the
slmodemd terminates by saying

Segmentation fault

and the the wvdial also then writes... (bla bla removed this time)

--> Disconnecting st Sun Oct 18 12:56:10 2009

and both Terminal windows go back to prompt.

On 18/10/2009, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote:
> Dear Denver,
>
> I too, and certainly Marv as well, are ecited.
>
> But please, just think, how can we help you when you cut the bla bla
> whuch contains messages intended to decribe what is happening?
>
> A simple way to proceed is to give the wvdial command as follows:
>
>
> sudo wvdial  |  tee denver.txt
>
> where the symbol | between wvdial and tee is a vertical bar usually
> found on the same key as \
>
> On the keyboard it is usually printed as broken in the middle.
>
> You will see the output as before but it will also be "piped" (copied)
> to a new file arbitrarily named by me denver.txt
>
> Please send us that file after wvdial has exited.
>
> Thanks.
>
> Jacques
>
>
>
>
> Denver Chiwakira wrote:
>
>> Great, we're one finger from the solution...
>>
>> I'm now dialing but it keeps cutting off after the lines below...
>>
>> --> Modem Initialised
>> --> Sending ATDT330001
>> --> Waiting for carrier
>> --> Disconnecting at Sun Oct 18 bla bla bla
>>
>> I added the Carrier Check = no line as well.
>>
>> I'm excited...
>>
>> On 18/10/2009, Denver Chiwakira <denversdesk@xxxxxxxxx> wrote:
>>
>>> Let me give this a try...
>>>
>>> On 18/10/2009, Jacques Goldberg <goldberg@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>
>>>> Congratulations.
>>>> Now it is Ok as concerns starting slmodem
>>>> But the way to create your wvdial.conf is not by fishing something with
>>>> the same name on the net.
>>>>
>>>> You MUST run (ONCE is enough, not at every boot):
>>>> sudo wvdialconf /etc/wvdial.conf
>>>>
>>>> This way wvdialconf will discover YOUR modem while a file found at
>>>> random
>>>> has a definition for any of very different modems. By the way the file
>>>> which you found is for an external hardware modem ...
>>>>
>>>> One wvdialconf will have found your modem (and remember, slmodemd MUST
>>>> BE
>>>> RUNNING while you use wvdialconf, as well as wvdial, so the wvdialconf
>>>> and
>>>> later the wvdial commands must be given in an other
>>>> window/console/terminal, not in the one where slmodemd is running)
>>>> you must edit the file /etc/wvdial.conf just written by wvdialconf
>>>> In the three lines  Phone, Username, Password:
>>>> a- remove the leading ;
>>>> b- replace the container symbol <Username> by the user name given to you
>>>> by your ISP. Do the same for the phone and password fields
>>>> c-add one line anywhere in the file if it is not yet present. The line
>>>> is
>>>>
>>>> Carrier Check = no
>>>>
>>>> d-save the file.
>>>> Only then you are ready to try a connection.
>>>>
>>>> Jacques
>>>>
>>>> On Sun, 18 Oct 2009, Denver Chiwakira wrote:
>>>>
>>>>
>>>>> Date: Sun, 18 Oct 2009 09:21:46 +0200
>>>>> From: Denver Chiwakira <denversdesk@xxxxxxxxx>
>>>>> To: Jacques Goldberg <Jacques.Goldberg@xxxxxxx>
>>>>> Cc: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
>>>>> Subject: Re: Modem Scan
>>>>> Resent-Date: Sun, 18 Oct 2009 09:22:05 +0200 (IST)
>>>>> Resent-From: <Jacques.Goldberg@xxxxxxx>
>>>>>
>>>>> I don't know if I'm making things worse but... I have just run the
>>>>> command
>>>>>
>>>>> sudo slmodemd -c USA  /dev/slamr0
>>>>>
>>>>> and the response was
>>>>>
>>>>> SmartLink Soft Modem: version 2.9.11 Mar  6 2009 00:36:34
>>>>> symbolic link `/dev/ttySL0' -> `/dev/pts/1' created.
>>>>> modem `slamr0' created. TTY is `/dev/pts/1'
>>>>> Use `/dev/ttySL0' as modem device, Ctrl+C for termination.
>>>>>
>>>>> Now I'm attrempting to edit the wvdial.conf and manually add the
>>>>> settings
>>>>>
>>>>> I saw a sample like this on the net...
>>>>>
>>>>> [Dialer Defaults]
>>>>> Modem = /dev/ttyS1
>>>>> Baud = 115200
>>>>> Init1 = ATZ
>>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
>>>>> Phone = 555-1212
>>>>> Username = my_login_name
>>>>> Password = my_login_password
>>>>>
>>>>> Am not too sure about the Init1 & Init2 though.... I hope I wont make
>>>>> things worse here...
>>>>>
>>>>>
>>>>>
>>>>> On 18/10/2009, Denver Chiwakira <denversdesk@xxxxxxxxx> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The new file still gave me the same error ....
>>>>>>
>>>>>> ...........
>>>>>> ...........
>>>>>> slmodemd -c USA  /dev/slamr0
>>>>>> Checking for success
>>>>>> Port creation with slmodemd failed.
>>>>>> Read the Slamr.txt record, other *.txt files and the sample
>>>>>> wvdial.conf
>>>>>> .
>>>>>>
>>>>>> Am I doing something wrong. I execute that file as follows
>>>>>>
>>>>>> $ tar -zxvf slamr-2.6.28-11-generic.tar.gz
>>>>>> run
>>>>>> $ sudo ./setup
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 17/10/2009, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote:
>>>>>>
>>>>>>> Done - Jacques
>>>>>>>
>>>>>>>
>>>>>>> Marvin Stodolsky wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Jacques,
>>>>>>>>     Please replace the current package.
>>>>>>>>
>>>>>>>> Denver,
>>>>>>>>     Just delete the old one and use this update.
>>>>>>>>
>>>>>>>> MarvS
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Oct 15, 2009 at 7:19 PM, Marvin Stodolsky
>>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Denver,
>>>>>>>>>
>>>>>>>>> The problem is the initial setup was:
>>>>>>>>>   slmodemd -c  /dev/slamr0
>>>>>>>>> which should have been
>>>>>>>>>   slmodemd -c USA  /dev/slamr0
>>>>>>>>>
>>>>>>>>> This defective package should have been replaced at the Linmodems
>>>>>>>>> site,
>>>>>>>>> but I've just sent the replacement direct to you.
>>>>>>>>>
>>>>>>>>> MarvS
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Oct 15, 2009 at 5:21 PM, Antonio Olivares
>>>>>>>>> <olivares14031@xxxxxxxxx> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Denver,
>>>>>>>>>>
>>>>>>>>>> I have connection problems and I am seldom online, so I am
>>>>>>>>>> resending
>>>>>>>>>> this to list and see if they can provide better guidance:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> installing drivers for kernel version 2.6.28-11-generic
>>>>>>>>>>
>>>>>>>>>> Writing record to ./Slamr.txt
>>>>>>>>>> Installing the Debian packages supporting autoloading
>>>>>>>>>> (Reading database ... 102049 files and directories currently
>>>>>>>>>> installed.)
>>>>>>>>>> Preparing to replace sl-modem-daemon 2.9.11~20080817-3ubuntu2
>>>>>>>>>> (using
>>>>>>>>>> sl-modem-daemon_2.9.11~20080817-3ubuntu2_i386.deb) ...
>>>>>>>>>> Shutting down SmartLink Modem driver normally ... no slmodemd
>>>>>>>>>> daemon
>>>>>>>>>> running.
>>>>>>>>>> Unloading modem driver from kernel ... slamr.
>>>>>>>>>> Unpacking replacement sl-modem-daemon ...
>>>>>>>>>> Setting up sl-modem-daemon (2.9.11~20080817-3ubuntu2) ...
>>>>>>>>>> The system user `Slmodemd' already exists. Exiting.
>>>>>>>>>> Not starting SmartLink modem daemon (options not set in
>>>>>>>>>> /etc/default/slmodemd)
>>>>>>>>>>
>>>>>>>>>> Processing triggers for man-db ...
>>>>>>>>>>
>>>>>>>>>> Copying over newer files
>>>>>>>>>> Making folder /lib/modules/2.6.28-11-generic/extra
>>>>>>>>>> Copying drivers to /lib/modules/2.6.28-11-generic/extra
>>>>>>>>>> Checking driver install
>>>>>>>>>> slamr.ko
>>>>>>>>>> slusb.ko
>>>>>>>>>> ungrab-winmodem.ko
>>>>>>>>>> Copying newer slmodemd to /usr/sbin/
>>>>>>>>>> Checking slmodemd version. Should be 2.9.11
>>>>>>>>>> SmartLink Soft Modem: version 2.9.11 May 18 2009 18:31:59
>>>>>>>>>> Finished installs.
>>>>>>>>>> Informing the System
>>>>>>>>>>
>>>>>>>>>> Starting function tests, loading drivers:
>>>>>>>>>> Running diagnostic:
>>>>>>>>>>
>>>>>>>>>> [ 6118.803655] slamr: module license 'Smart Link Ltd.' taints
>>>>>>>>>> kernel.
>>>>>>>>>> [ 6118.818926] slamr: SmartLink AMRMO modem.
>>>>>>>>>> [ 6118.819053] slamr: probe 2000:2800 SL2800 card...
>>>>>>>>>> [ 6118.819082] slamr 0000:00:0b.0: PCI INT A -> GSI 19 (level,
>>>>>>>>>> low)
>>>>>>>>>> ->
>>>>>>>>>> IRQ 19
>>>>>>>>>> [ 6118.820222] slamr: slamr0 is SL2800 card.
>>>>>>>>>> [11063.304155] slamr 0000:00:0b.0: PCI INT A disabled
>>>>>>>>>> [11074.853482] slamr: SmartLink AMRMO modem.
>>>>>>>>>> [11074.853648] slamr: probe 2000:2800 SL2800 card...
>>>>>>>>>> [11074.853688] slamr 0000:00:0b.0: PCI INT A -> GSI 19 (level,
>>>>>>>>>> low)
>>>>>>>>>> ->
>>>>>>>>>> IRQ 19
>>>>>>>>>> [11074.855508] slamr: slamr0 is SL2800 card.
>>>>>>>>>> ports should be created by:
>>>>>>>>>> slmodemd -c  /dev/slamr0
>>>>>>>>>> Checking for success
>>>>>>>>>> Port creation with slmodemd failed.
>>>>>>>>>> Read the Slamr.txt record, other *.txt files and the sample
>>>>>>>>>> wvdial.conf
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Antonio
>>>>>>>>>>
>>>>>>>>>> On 10/15/09, Denver Chiwakira <denversdesk@xxxxxxxxx> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for the help Antonio. I managed to install the WVDIAL but
>>>>>>>>>>> the
>>>>>>>>>>> slamr-2.6.28-11-generic is giving me some errors as attached.
>>>>>>>>>>>
>>>>>>>>>>> On running the WVDIAL diagnostics it says that is cannot find
>>>>>>>>>>> "/dev/modem" . I suspect that there is a problem with the
>>>>>>>>>>> installation
>>>>>>>>>>> of the slamr-2.6.28-11-generic. To make things worse I also tried
>>>>>>>>>>> the
>>>>>>>>>>> provided in slmodem-2.9.11-20090222.tar.gz and
>>>>>>>>>>> ungrab-winmodem-20090716.tar.gz but still no "/dev/modem" .
>>>>>>>>>>>
>>>>>>>>>>> I'm quite new to the Ubuntu (version 9.08) and am slowly learning
>>>>>>>>>>> my
>>>>>>>>>>> way around it. I still feel far though.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Denver
>>>>>>>>>>>
>>>>>>>>>>> On 14/10/2009, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Denver,
>>>>>>>>>>>>
>>>>>>>>>>>> scanModem reports that your modem is supported by slamr which is
>>>>>>>>>>>> provided in slmodem-2.9.11-20090222.tar.gz and
>>>>>>>>>>>> ungrab-winmodem-20090716.tar.gz.
>>>>>>>>>>>>
>>>>>>>>>>>> But you can even do better than that with a preloaded slamr
>>>>>>>>>>>> found
>>>>>>>>>>>> in
>>>>>>>>>>>>
>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/slamr-2.6.28-11-generic.tar.gz
>>>>>>>>>>>>
>>>>>>>>>>>> Do download it, copy it to your linux partition and extract it
>>>>>>>>>>>> $ tar -zxvf slamr-2.6.28-11-generic.tar.gz
>>>>>>>>>>>> run
>>>>>>>>>>>> $ sudo ./setup
>>>>>>>>>>>>
>>>>>>>>>>>> and everything should be ready to go, except installation of
>>>>>>>>>>>> wvdial
>>>>>>>>>>>> which was not found on your system according to scanModem.
>>>>>>>>>>>>
>>>>>>>>>>>> Predictive  diagnostics for card in bus 00:0b.0:
>>>>>>>>>>>>      Modem chipset  detected on
>>>>>>>>>>>> NAME="Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT "
>>>>>>>>>>>> CLASS=0703
>>>>>>>>>>>> PCIDEV=2000:2800
>>>>>>>>>>>> SUBSYS=163c:2800
>>>>>>>>>>>> IRQ=19
>>>>>>>>>>>> IDENT=slamr
>>>>>>>>>>>>
>>>>>>>>>>>>  For candidate modem in:  00:0b.0
>>>>>>>>>>>>    0703 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT
>>>>>>>>>>>>       Primary device ID:  2000:2800
>>>>>>>>>>>>  Support type needed or chipset:     slamr
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> The modem is supported by the Smartlink
>>>>>>>>>>>> plus the slmodemd helper utility.  Read the
>>>>>>>>>>>> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
>>>>>>>>>>>> through
>>>>>>>>>>>> guidance.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> For 2.6.28-11-generic 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
>>>>>>>>>>>>
>>>>>>>>>>>> The dialer utility package WVDIAL does not appear to be
>>>>>>>>>>>> installed
>>>>>>>>>>>> on
>>>>>>>>>>>> your System.
>>>>>>>>>>>> For Ubuntu Jaunty users, there are at the bottom of
>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/:
>>>>>>>>>>>>      wvdial_jaunty_amd64.zip   for x86_64, 64 bit bus systems.
>>>>>>>>>>>>      wvdial_jaunty_i386.zip    for 32 bit systems.
>>>>>>>>>>>> These are about 1 MB in size.  After downloaded and copied into
>>>>>>>>>>>> your
>>>>>>>>>>>> Linux partition:
>>>>>>>>>>>> $ unzip wv*.zip
>>>>>>>>>>>> Within the new folder:
>>>>>>>>>>>> $ sudo dpkg -i *.deb
>>>>>>>>>>>> will  complete the wvdial installation
>>>>>>>>>>>> Please read Modem/DOCs/wvdial.txt for usage information.
>>>>>>>>>>>>
>>>>>>>>>>>> After installation of wvdial and slamr driver, run
>>>>>>>>>>>> $ sudo wvdialconf /etc/wvdial
>>>>>>>>>>>> edit it
>>>>>>>>>>>> $ sudo gedit /etc/wvdial.conf
>>>>>>>>>>>> and remove the ";" and add your username, password and ISP's
>>>>>>>>>>>> phone
>>>>>>>>>>>> number add a line "Carrier Check = no" to your /etc/wvdial.conf
>>>>>>>>>>>> file.
>>>>>>>>>>>> Try to dialout and if you encounter trouble please report back
>>>>>>>>>>>> to
>>>>>>>>>>>> list
>>>>>>>>>>>> not me as I have been having connection The dialer utility
>>>>>>>>>>>> package
>>>>>>>>>>>> WVDIAL does not appear to be installed on your System.
>>>>>>>>>>>> For Ubuntu Jaunty users, there are at the bottom of
>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/:
>>>>>>>>>>>>      wvdial_jaunty_amd64.zip   for x86_64, 64 bit bus systems.
>>>>>>>>>>>>      wvdial_jaunty_i386.zip    for 32 bit systems.
>>>>>>>>>>>> These are about 1 MB in size.  After downloaded and copied into
>>>>>>>>>>>> your
>>>>>>>>>>>> Linux partition:
>>>>>>>>>>>> $ unzip wv*.zip
>>>>>>>>>>>> Within the new folder:
>>>>>>>>>>>> $ sudo dpkg -i *.deb
>>>>>>>>>>>> will  complete the wvdial installation
>>>>>>>>>>>> Please read Modem/DOCs/wvdial.txt for usage information.
>>>>>>>>>>>>
>>>>>>>>>>>> After installation of wvdial and slamr module, run
>>>>>>>>>>>> $ sudo wvdialconf /etc/wvdial.conf
>>>>>>>>>>>> and it should find /dev/ttySL0 as the modem port. edit the file
>>>>>>>>>>>> with
>>>>>>>>>>>> $ sudo gedit /etc/wvdial.conf
>>>>>>>>>>>> and remove the ";" and add your username, password and ISP's
>>>>>>>>>>>> phone
>>>>>>>>>>>> number and a line "Carrier Check = no", try to establish a
>>>>>>>>>>>> connection.
>>>>>>>>>>>>  If you encounter difficulties, please let us know (list) as I
>>>>>>>>>>>> have
>>>>>>>>>>>> been having connection problems at home.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Antonio
>>>>>>>>>>>>
>>>>>>>>>>>> On 10/14/09, Denver Chiwakira <denversdesk@xxxxxxxxx> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> I'm a begginer - is my modem compatible?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>
>
>

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux