Re: David Hopkins, Australia, Linux Mint 6 Felicia kernel 2.6.27-7-generic

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

 



David,

Please send to the List as I'm traveling and only on line briefly
At this stage, after
> sudo slmodemd -c AUSTRALIA --alsa hw:0,6
leave it running.

Open another TAB or console and the modem should be detected by:
$ sudo wvdialconf

Edit in your personal information, removing the ; < >  symbols,  with
$ sudo gedit /etc/wvdial.conf
Because /dev/pts/N  ports are not yet sound competent, also add a line:
Carrier Check  =  no

Save. See the wvdial.txt  about some exceptional cases, rarely cogent
in Australia

Do:
$ ifconfig
to check which COMM channels are active. Shut any except lo "loopback"
with commands like:
$ sudo ifconfig eth0 down
$ ifconfig
again to check.
If other channels are open DNS will fail for the coming ppp0 channel.

Dialout with:
$ sudo wvdial

MarvS


On Wed, Feb 18, 2009 at 2:00 PM, David <davidhopkins@xxxxxxxxxxxxxxx> wrote:
> Marvin,
>
> I have advanced since previous email sent below. So I have answered all
> my questions below, by reading other documents as you suggested.
>
> So I'm up to the point where I have installed slmodemd and executed $
> sudo slmodemd -c AUSTRALIA --alsa hw:0,6. The terminal output is as
> follows:
> "Smartlink Soft Modem: version 2.9.11 Dec 16 2008 22:54:51
> symbolic link  '/dev/ttySL0 -> '/dev/pts/1' created.
> modem 'hw:0,6' created. TTY is '/dev/pts/1'
> Use 'dev/ttySL0' as modem device, Ctrl+C for termination."
>
> At the end of your last email you wrote:
> "Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
> through guidance." Where exactly do I find these .txt documents?
>
> Regards
> David Hopkins
>
> On Thu, 2009-02-19 at 06:13 +1000, David wrote:
>> Marvin,
>>
>> Thank you for your solution. Not there yet though, probably because of
>> my lack of Linux knowledge.
>>
>> Here is what happened so far:
>> 1. Successfully downloaded SLMODEMD_gcc4.2_alsa1.0.17.tar.gz into home
>> directory.
>> 2. Successfully unpacked tar using $ tar zxf
>> SLMODEMD_gcc4.2_alsa1.0.17.tar.gz (You specified $ tar zxf
>> SLMODEMD.gcc4.2.tar.gz - I assumed that was a typo?)
>> 3. The following is where I came unstuck:
>> $ cd SLMODEMD_gcc4.2_alsa1.0.17
>> $ sudo slmodemd -c AUSTRALIA --alsa hw:0,6
>> sudo: slmodemd: command not found
>>
>> And yet the executable slmodemd is certainly inside the folder
>> SLMODEMD_gcc4.2_alsa1.0.17? Also why did you choose hw:0,6?
>>
>> Regards
>> David Hopkins
>>
>> On Wed, 2009-02-18 at 09:08 -0800, Marvin Stodolsky wrote:
>> > David,
>> >
>> > Your Motorola modem chip is likely on the Subsystem of the HDAudio card:
>> > 01:00.1 0403: 1002:aa28
>> >     Subsystem: 1002:aa28
>> >     Flags: bus master, fast devsel, latency 0, IRQ 17
>> >     Memory at fdfec000 (32-bit, non-prefetchable) [size=16K]
>> >     Capabilities: <access denied>
>> >     Kernel driver in use: HDA Intel
>> >     Kernel modules: snd-hda-intel
>> >
>> >
>> >  Download from http://linmodems.technion.ac.il/packages/smartlink/
>> >  the packageSLMODEMD_gcc4.2_alsa1.0.17.tar.gz  having a compiled
>> > slmodemd. Unpack
>> > under Linux with:
>> >        $ tar zxf SLMODEMD.gcc4.2.tar.gz
>> >  and read instructions therein. But briefly, the modem is setup with command:
>> >        sudo slmodemd -c AUSTRALIA --alsa hw:0,6
>> >  reporting dynamic creation of ports:
>> >        /dev/ttySL0 --> /dev/pts/N   , with N some number
>> >  Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
>> > through guidance.
>> >
>> > MarvS
>> >
>> >
>> > On Tue, Feb 17, 2009 at 5:13 PM, David <davidhopkins@xxxxxxxxxxxxxxx> wrote:
>> > > MarvS,
>> > >
>> > > Since my previous email below, tried scanModem on both Ubuntu 8.10 (of
>> > > which Linux Mint 6 is a derivative) as well as openSUSE 11.1 on the same
>> > > notebook. Both these distros failed in exactly the same manner as with
>> > > Linux Mint 6.
>> > >
>> > > Also the dh2.txt file I sent you doesn't even list the modem, from what
>> > > I can see?
>> > >
>> > > Regards
>> > > David Hopkins
>> > >
>> > > On Wed, 2009-02-18 at 06:58 +1000, David wrote:
>> > >> MarvS,
>> > >>
>> > >> Thank you for your prompt response.
>> > >>
>> > >> Have carried out your instructions and attached dh.txt and dh2.txt.
>> > >>
>> > >> Please note that the first "bash" command didn't complete back to the $
>> > >> prompt, but nevertheless produced dh.txt. The second, three line command
>> > >> sequence did complete cleanly.
>> > >>
>> > >> Since sending you yesterdays email have noted other scanModem users have
>> > >> reported the same problem...
>> > >>
>> > >> Look forward to hearing back from you.
>> > >>
>> > >> Regards
>> > >> David Hopkins
>> > >>
>> > >> On Tue, 2009-02-17 at 11:45 -0800, Marvin Stodolsky wrote:
>> > >> > David,
>> > >> >
>> > >> > To help me do a bugfix, run:
>> > >> > $ bash -x ./scanModem 2>&1 | tee dh.txt
>> > >> > and send me the dh.txt directly.
>> > >> >
>> > >> > Also do
>> > >> > $ cat /proc/version  >> dh2.txt
>> > >> > $ lspci >> dh2.txt
>> > >> > $ lspci -nv >>  dh2.txt
>> > >> > which is basically what scanModem parses on.
>> > >> > Send me the dh2.txt, which should provide enough info assess which
>> > >> > Motorola SpeakerPhone chipset (there are a few types) your modem has.
>> > >> >
>> > >> > MarvS
>> > >> > scanModem maintainer
>> > >> >
>> > >> > On Mon, Feb 16, 2009 at 4:18 PM, David <davidhopkins@xxxxxxxxxxxxxxx> wrote:
>> > >> > > Hello,
>> > >> > >
>> > >> > > Running a new ASUS M51Vseries notebook with XP dual-boot arrangement.
>> > >> > > According to XP the name of the modem is "Motorola SM56 Speakerphone
>> > >> > > Modem", which works...
>> > >> > >
>> > >> > > ModemData.txt attached. Unfortunately "sudo ./scanModem" repeatedly
>> > >> > > fails to complete, always with the following lines, within quotes,
>> > >> > > output to the terminal:
>> > >> > > "UPDATE=2009_02_04
>> > >> > >  Continuing as this update is only two weeks old,
>> > >> > >  but the current Update is always at:  http://linmodems.technion.ac.il
>> > >> > >
>> > >> > > grep: 01:00.1: No such file or directory
>> > >> > > grep: 01:00.1: No such file or drectory".
>> > >> > >
>> > >> > > Would very much appreciate your advice.
>> > >> > >
>> > >> > > Regards
>> > >> > > David Hopkins
>> > >> > >
>> > >
>> > >
>
>

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

  Powered by Linux