I am still working on trying to get dialup internet working in one way
or another. I gave up on the laptop for now, because it would not
upgrade. I think I finally got everything installed properly on my
desktop computer, but it seems that wvdial cannot find my modem.
Following are the results of running agrsm-test, sudo
wvdialconf /etc/wvdial.conf, and sudo wvdial. I have also attached a
copy of ModemData.text for this computer, in case it makes a difference.
The drivers are loaded, the symbolic link has been created, and I have
put the line "Modem = /dev/ttySAGR" into wvdial.conf, but still wvdial
does not seem to be able to communicate with my usb modem. Can you
please help me figure out what else I am missing?
------------------------------------------------------------------------------
agrsm-test:
Loading drivers:
Drivers loaded:
agrserial 9981 0
agrmodem 1332700 1
snd 54148 17
agrmodem,snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_hwdep,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
and symbolic link created:
lrwxrwxrwx 1 root root 12 2010-05-23 13:39 /dev/ttySAGR -> /dev/ttyAGS3
Checking for utility wvdialconf
Found /usr/bin/wvdialconf, preparing to run:
wvdialconf /etc/wvdial.conf
A file /etc/wvdial.conf already exists, first renaming
to /etc/wvdial.201005233905
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
A reboot may be necessary before modem detection through:
sudo modprobe agrserial
Which will load agrmodem, agrserial and create the symbolic link needed
for:
sudo wvdialconf
The installation record has been written to ./agrsm-test.txt
------------------------------------------------------------------------------
sudo wvdialconf /etc/wvdial.conf:
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://open.nit.ca/wiki/?WvDial
If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
------------------------------------------------------------------------------
sudo wvdial:
--> WvDial: Internet dialer version 1.60
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding.
------------------------------------------------------------------------------
Since wvdial.conf could not be created automatically, I tried to
manually edit it as follows:
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Baud = 115200
Modem = /dev/ttySAGR
Phone = xxxxxxx
Password = xxxxxxx
Username = xxxxxxx
New PPPD = yes
------------------------------------------------------------------------------
Thanks.
Debbie
Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.32-21-generic
With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in YourCountry
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@xxxxxxxxxxxxx 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, Ubuntu , ALSA_version=1.0.21
Linux version 2.6.32-21-generic (buildd@rothera) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010
scanModem update of: 2010_03_18
Distrib_ID=Ubuntu
DistribCodeName=lucid
AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/
The dkms driver upgrade utilities are installed,
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
agrmodem agrserial
Attached USB devices are:
ID 047e:2892 Agere Systems, Inc. (Lucent) Systems Soft Modem
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html
A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
Candidate PCI devices with modem chips are:
High Definition Audio cards can host modem chips.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 004:
Modem chipset detected on
SLOT="Bus 004 Device 002:"
NAME="Agere Systems, Inc. (Lucent) Systems Soft Modem"
bus=004
USBmodemID=047e:2892
IDENT=agrsm
Driver=agrsm
For a detailed USB cellphone usage report, see http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html
For candidate modem in: 004
Agere Systems, Inc. (Lucent) Systems Soft Modem
Primary device ID: 047e:2892
Support type needed or chipset: agrsm
The AgereSystems/LSI agrsm code supports compiling of a agrmodem + agrserial driver pair.
There are a few different chipsets which use this driver pair, but they use different code resources:
Chipsets KV* PackageNames (most current as of November 2009)
----------------------------------------------------------------------------------------------
11c1:048c and 11c1:048f 2.6.29 agrsm048pci-2.1.60_20100108_i386.deb or agrsm048pci-2.1.60_20100108.tar.gz
11c1:0620 2.6.31 agrsm06pci-2.1.80_20100106_i386.deb or agrsm06pci-2.1.80~20100106.tar.gz !!
11c11040 (on HDA audio cards) 2.6.31 agrsm-11c11040_20091225_i386.deb or agrsm-11c11040-2.1.80~20091225.tar.bz2 !!
All available at: http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
Additionally there are;
automation & testing agrsm-tools_0.0.1_all.deb or agrsm-tools-0.0.1-2.noarch.rpm
General background agrsm_howto.txt
------------------------------------------------------------------------------------------------
* KV == latest kernel release with a reported success
!! Latest update with major credit to Nikolay Zhuravlev
But see conflict issue: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html
For the 11c11040 chip with kernels 2.6.31 and later a change in a modules loading settingmay be necessary.
Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for your Distro), change the phrase:
options snd-hda-intel power_save=10
to:
options snd-hda-intel power_save=0
or the agrsm drivers will not function. For Ubuntu related systems this can be done with:
$ sudo gedit /etc/modprobe.d/alsa-base.conf
Report from Bjorn Wielens:
Please note- trying to load the modules on a OpenSuSE 11.2 system gives
an error about the module_version symbol. Using:
# modprobe --force agrmodem
# modprobe --force agrserial
is necessary to load the drivers, and does not appear to cause ill effects.
All of the above packages are dkms competent. This means that if your Linux distros dkms package
is previously installed, if provides for future updates matching forthcoming kernels.
-------------- end Agere Systems section -------------------
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.4.3
and the compiler used in kernel assembly: 4.4.3
The patch utility is needed for compiling ALSA drivers, and possibly others.
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.32-21-generic/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 needed. The also required headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages, for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
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 packages.
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
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/agrsm.conf:## setup agrsm modem with only: "sudo modprobe agrserial"
/etc/modprobe.d/agrsm.conf:install agrserial /sbin/modprobe --ignore-install agrmodem ; /sbin/modprobe --ignore-install agrserial && \
/etc/modprobe.d/agrsm.conf:remove agrserial /sbin/modprobe -r --ignore-remove agrserial ; /sbin/modprobe -r --ignore-remove agrmodem && { if test -L /dev/ttySAGR; then rm /dev/ttySAGR; fi } ; true
/etc/modprobe.d/agrsm.conf:# to automate bootup "sudo modprobe agrmodem"
/etc/modprobe.d/agrsm.conf:## to setup agrsm modem with only: "sudo modprobe agrmodem"
/etc/modprobe.d/agrsm.conf:# install agrmodem /sbin/modprobe --ignore-install agrmodem && \
/etc/modprobe.d/agrsm.conf:## of effects of agrmodem and agrserial loading
/etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
