Thanks very much Marvin,
That was a silly mistake wasn't it? I grabbed the wrong file. Here's
the contents of ModemData.txt.
Cheers,
M@.
=====
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.22-14-generic
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@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,
Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3
20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12
07:42:25 UTC 2008
scanModem update of: 2008_02_20
There are no blacklisted modem drivers in /etc/modprobe* files
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 /proc/asound/ audio+modem diagostics are being copied.
Finished copy to Modem/ALSAroot.tgz
The ALSA verion is 1.0.14
The modem cards detected by "aplay -l" are:
The /proc/asound/pcm file reports:
-----------------------
00-01: Intel ICH - MIC ADC : Intel 82801AA-ICH - MIC ADC : capture 1
00-00: Intel ICH : Intel 82801AA-ICH : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [I82801AAICH ]: ICH - Intel 82801AA-ICH
Intel 82801AA-ICH with AD1881A at irq 5
1 [UART ]: MPU-401 UART - MPU-401 UART
MPU-401 UART at 0x330, irq 10
USB modem not detected by lsusb
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:01.0 VGA compatible controller: Intel Corporation 82810 (CGC)
Chipset Graphics Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801AA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801AA SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97
Audio Controller (rev 02)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
------------------------------------------------
with USB and bridge devices not displayed.
If your modem is connected by an external serial cable,
or mounted internally on an ISA card, scanModem would not access it.
Try with Root permission
$ sudo wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
sudo gedit /etc/wvdial.conf
will be able to dial out with Root permission:
sudo wvdial
Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems
If the above tests fail, please provide any independent information
available on your modem.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.3
and the compiler used in kernel assembly: 4.1.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
linuc_headers base folder /lib/modules/2.6.22-14-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 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
Checking pppd properties:
-rwsr-xr-- 1 root dip 269256 2007-10-05 05:57 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
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
Read Modem/YourSystem.txt concerning other COMM channels: eth0
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:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to
blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
On Wed, Mar 5, 2008 at 12:48 AM, Marvin Stodolsky
<marvin.stodolsky@xxxxxxxxx> wrote:
> Matt
>
> Send us the output of ModemData.txt
> ./scanModem mostly parses the output of
> $ lspci
> $ lspci -nv
> looking for the modem sections therein,
> which is sometimes embedded in a High Definition Audio card.
>
> MarvS
>
>
>
> On Tue, Mar 4, 2008 at 5:25 AM, M@ <matt@xxxxxxxxxxx> wrote:
> > G'day LinModems,
> >
> > I'm sorry I didn't join the list as per the instructions at
> > 1stRead.txt, but I went to http://www.linmodems.org and was unable to
> > see where to join.
> >
> > I had hoped to be able to work this out for myself. Unfortunately,
> > more than 15 years experience with Windows and a few months experience
> > with Linux have not enabled me to understand the output of your
> > program.
> >
> > I should mention that I was connected to the Internet via my home LAN
> > while I performed the test. My intention is to remove the NIC from
> > the machine once I have set up the modem.
> >
> > The following is the contents of my ModemData.txt file. I hope you
> > can help me find a driver for my modem.
> >
> > Best Regards,
> >
> > M@.
> > Matt Walsh.
> >
> > =====
> >
> > If you want help from the email group Discuss@xxxxxxxxxxxxx, PLEASE
> > join the List
> > at http://www.linmodems.org . Otherwise your messages will be delayed
> > until the evening,
> > waiting for someone to verify it is not junk mail, before forwarding
> > through the List server.
> >
> > The files in this Modem/ folder have the following roles:
> >
> > ModemData.txt - Diagnostics and accumulated information cogent to your
> > modem and host system.
> > This is the ONLY file which should be sent to the List
> > DISCUSS@xxxxxxxxxxxxx ,
> > if further help is needed. Send your email and attachments as
> > plain text as
> > other formats are rejected by the List Server, to avoid virus transmission.
> > Always send the ENTIRE ModemData.txt, as It includes subtle
> > diagnostic ouputs needed
> > to best guide you. Please in the covering email mention your
> > Country, to enable Country
> > specific advice.
> > Always use the most recent update of scanModem accessed ONLY at
> > http://linmodems.technion.ac.il/packages/scanModem.gz
> > to produce ModemData.txt
> > URLs to cogent advice are regularly updated, so your problem may
> > be solved therein.
> > Please Do NOT send Do NOT send other files in this folder Modem/
> >
> > A file(s) specific to your modem chipset will be written, such as:
> > Smartlink.txt, Conexant.txt, Intel.txt , etc
> >
> > YourModem.txt - Guidance about operating your particular System, for
> > your benefit
> > It should NOT be sent to Discuss@xxxxxxxxxxxxx
> >
> > Rational.txt - Motivations of this scanModem package.
> >
> > DriverCompiling.txt - Explains the roles of additional files which
> > may have to be installed
> > to support compiling of modem drivers, and the steps to take.
> >
> > SoftModem.txt - Information and instructions about "soft modems".
> > For these modems, additional steps may be necessary for choice of
> > supporting software.
> > The primary PCI ID is that of the host audio or modem controller,
> > which can support diverse Subsystems. It is the chipset of the
> > Subsystem which determines the software needed.
> >
> > ModemTesting.txt SHOULD be read, but after drivers have been installed.
> >
> > InfoGeneral.txt has general information about the status of winmodem
> > support under Linux,
> > Do read it if ModemData.txt reports that your current modem is
> > not supported under Linux.
> >
> > Unsubscribe.txt - Howto terminate email tranmissions from the List.
> >
> > If you are Linux newcomer, please do locate your local Linux group through:
> > http://www.linux.org/groups/index.html . If you are not
> > comfortable with English,
> > a local Linux user can often be of substantial assistance in
> > getting you on to the Internet.
> >
>
