ModemData.txt says:
BEGIN
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.
END
Have you at least read these instructions?
If you did, what went wrong?
Jacques
Dinesh Hegde wrote:
I need suggestion based on my ModemData.txt which i have attached here.
Thanks
------------------------------------------------------------------------
Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Fedora Core release 6 (Zod)
Kernel kernel 2.6.18-1.2798.fc6
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through: http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686, Fedora Core release 6 (Zod)
Kernel
Linux version 2.6.18-1.2798.fc6 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:54:20 EDT 2006
scanModem update of: 2007_Feb_28
USB modem not detected by lsusb
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
05:0b.0 2000:2800 1801:2800 Modem: Smart Link Ltd. Unknown device 2800
Modem interrupt assignment and sharing:
--- Bootup diagnositcs for card in PCI slot 05:0b.0 ----
ACPI: PCI Interrupt 0000:05:0b.0[A] -> GSI 16 (level, low) -> IRQ 193
ACPI: PCI interrupt for device 0000:05:0b.0 disabled
The PCI slot 05:0b.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
For candidate modem in PCI bus: 05:0b.0
Class 0703: 2000:2800 Modem: Smart Link Ltd. Unknown device 2800
Primary PCI_id 2000:2800
Support type needed or chipset: slamr
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.
Writing Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.1
and the compiler used in kernel assembly: 4.1.1
Kernel-header resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
kernel-source-2.6.18-1.2798.fc6
Checking pppd properties:
-r-xr-xr-x 1 root root 312956 Jul 25 2006 /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)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
lock
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
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/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp", MODE="0660"
Within /etc/modprobe.conf files:
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
