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.15-23-386
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.15-23-386 (buildd@rothera) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Tue May 23 13:49:40 UTC 2006
scanModem update of: 2008_01_22
There are no blacklisted modem drivers in /etc/modprobe* files
PCI slot 0000:00:1b.0 has a High Definition Audio Card
New HDA card type:
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 /proc/asound/pcm file reports:
-----------------------
00-00: HDA Generic : HDA Generic : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xe20c0000 irq 201
USB modem not detected by lsusb
For candidate card in slot 0000:01:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
0000:01:00.0 1057:3052 1057:3020 Modem: Motorola: Unknown device 3052
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 0000:01:00.0 ----
[4294668.467000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 20 (level, low) -> IRQ 169
[4294668.467000] 0000:01:00.0: ttyS5 at I/O 0xa008 (irq = 169) is a 16450
[4294668.467000] 0000:01:00.0: ttyS6 at I/O 0xa010 (irq = 169) is a 8250
[4294668.467000] 0000:01:00.0: ttyS7 at I/O 0xa018 (irq = 169) is a 16450
[4294668.467000] 0000:01:00.0: ttyS8 at I/O 0xa020 (irq = 169) is a 8250
[4294668.467000] 0000:01:00.0: ttyS9 at I/O 0xa028 (irq = 169) is a 8250
For candidate card in slot 0000:00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
0000:00:1b.0 8086:27d8 1458:a002 0403: Intel Corporation 82801G
Modem interrupt assignment and sharing:
201: 31765 IO-APIC-level uhci_hcd:usb4, HDA Intel, i915@pci:0000:00:02.0
--- Bootup diagnostics for card in PCI slot 0000:00:1b.0 ----
[4294678.065000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 201
[4294678.065000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
For candidate modem in PCI bus: 0000:00:1b.0
Class 0403: 8086:27d8 0403: Intel Corporation 82801G
Primary PCI_id 8086:27d8
Subsystem PCI_id 1458:a002
Softmodem codec or chipset from diagnostics:
from Archives:
Lacking a dsp (digital signal processing) chip, the modem is a software
intensive or "softmodem" type. Its primary controller manages the traffic
with the CPU. But the software needed is specified in the Subsystem.
-----------------------------------------
Support type needed or chipset:
Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.
2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.0.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Writing Intel.txt
For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read Conexant.txt
Read Conexant.txt
Writing Conexant.txt
Writing Smartlink.txt
============ end Smartlink section =====================
For candidate modem in PCI bus: 0000:01:00.0
Class 0703: 1057:3052 Modem: Motorola: Unknown device 3052
Primary PCI_id 1057:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage, read the Smartlink.txt
The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility. Read the
Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
Download slamr-2.6.15-23-386.tar.gz from http://linmodems.technion.il/packages/smartlink/Ubuntu/
under Linux, open a terminal and unpack with:
$ tar zxvf slamr*.tar.gz
Move into the unpacked folder
$ cd slamr-2.6.15-23-386
Look around
$ ls
Run the
$ sudo ./setup
Afterwards do:
$ slmodemd --help
$ slmodemd --countrylist &> Clist.txt
If not in the USA, look for your COUNTRY_NAME therein.
Do and edit with:
$ sudo gedit /etc/default/sl-modem-daemon
and therein replace the USA in the line:
SLMODEMD_COUNTRY=USA
This will provide for the correct Country setting in the automated:
slmodemd -c COUNTRY /dev/slamr0
Read the Smartlink.txt and YourSystem.txt
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
The kernel was compiled with gcc version 4.0.3 and a compiler is not installed
If compiling a modem driver proves to be necessary, one of the two procedures must be followed.
If not yet on the Internet, put the Dapper install CD in the drive
Open a terminal and therein:
$ sudo apt-get install gcc-4.0 make
Additionally the package linux-headers-2.6.15-23-386 must be downloaded.
Go to http://packages.ubuntu.com/ and search for linux-headers-2.6.15-23-386
After downloading, it can be installed with:
$ sudo dpkg -i linux-header*.deb
Or alternatively if online through Ethernet do:
$ sudo apt-get update
$ sudo apt-get install build-essential
will do all the necessary installations mentioned above.
In either installation case, set a symbolic link which will be expected later:
$ sudo ln -s /usr/bin/gcc-4.0 /usr/bin/gcc
After check with:
$ ls -l /usr/bin/gcc*
which should display:
lrwxrwxrwx 1 root root 16 2006-07-09 21:53 /usr/bin/gcc -> /usr/bin/gcc-4.0
-rwxr-xr-x 1 root root 93584 2006-04-20 18:22 /usr/bin/gcc-4.0
-rwxr-xr-x 1 root root 16245 2006-04-20 18:13 /usr/bin/gccbug-4.0
linux-headers-2.6.15-23-386 resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
gcc-4.0 make linux-headers-2.6.15-23-386
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 257720 2006-02-23 22:33 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://phep2.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
auth
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:
/etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink
/etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", SYMLINK+="modem"
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 --------
