آقا سلام!
من به طرز افتظاحی از ویندوز متنفرم ولی جه کار کنم که تا نتونم به لین مودممو بفهمونم نمی تونم از وین دست بردارم
من نتیجه ی برنامه ی اسکن مودم رو براتون می ذارم شاید کسی بتونه کمکم کنه چون من هیچی ازش نفهمیدم
در ظمن مودمم اینترنال روی پورت پی سی آی هستش
1stRead.txt:
If you want help from the email group Discuss@linmodems.org, 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@LINMODEMS.ORG ,
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/
Several informative files without diagnostics are in the DOCs subfolder.
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@linmodems.org
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.
ModemData.txt:
Only plain text email is forwarded by the Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.28-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. 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@Linmodems.org 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.28-14-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009
scanModem update of: 2009_07_17
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
Attached USB devices are:
ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
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
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@linmodems.org
For candidate card in slot 01:0b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:0b.0 12b9:1007 12b9:00a6 Communication controller: 3Com Corp, Modem Division USR 56k Internal WinModem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 01:0b.0 ----
[ 0.508165] pci 0000:01:0b.0: reg 10 32bit mmio: [0xd7fffc00-0xd7fffc3f]
[ 0.508174] pci 0000:01:0b.0: reg 14 32bit mmio: [0xd7fe0000-0xd7feffff]
[ 0.508182] pci 0000:01:0b.0: reg 18 32bit mmio: [0xd7ff0000-0xd7ff7fff]
[ 0.508191] pci 0000:01:0b.0: reg 1c io port: [0xb800-0xb83f]
[ 0.508219] pci 0000:01:0b.0: supports D2
[ 0.508221] pci 0000:01:0b.0: PME# supported from D0 D2 D3hot D3cold
[ 0.508265] pci 0000:01:0b.0: PME# disabled
The PCI slot 01: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 DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:2668 1043:81a6 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
16: 522800 0 IO-APIC-fasteoi uhci_hcd:usb5, radeon@pci:0000:04:00.0, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.505962] pci 0000:00:1b.0: reg 10 64bit mmio: [0xd6df8000-0xd6dfbfff]
[ 0.505997] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.506040] pci 0000:00:1b.0: PME# disabled
[ 9.622062] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 9.622161] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 1015.032583] HDA Intel 0000:00:1b.0: PCI INT A disabled
[ 1015.673045] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
[ 1015.673068] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1015.673075] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 6242.360690] HDA Intel 0000:00:1b.0: PCI INT A disabled
[ 6242.952532] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
[ 6242.952556] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6242.952563] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 6997.040678] HDA Intel 0000:00:1b.0: PCI INT A disabled
[ 6997.620533] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
[ 6997.620556] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6997.620563] HDA Intel 0000:00:1b.0: setting latency timer to 64
The PCI slot 00:1b.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 DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@linmodems.org
if help is needed.
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
The ALSA verion is 1.0.18
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-00: CMI9880 : CMI9880 : playback 1 : capture 2
00-01: CMI9880 Digital : CMI9880 Digital : playback 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xd6df8000 irq 16
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.28-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.28-13-generic/kernel/sound/pci/hda/snd-hda-intel.ko
UNEXPECTED HDA diagnostic outcome.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 01:0b.0:
Modem chipset detected on
NAME="Communication controller: 3Com Corp, Modem Division USR 56k Internal WinModem"
CLASS=0780
PCIDEV=12b9:1007
SUBSYS=12b9:00a6
IRQ=10
IDENT=3COM.winmodem
For candidate modem in: 01:0b.0
0780 Communication controller: 3Com Corp, Modem Division USR 56k Internal WinModem
Primary device ID: 12b9:1007
Support type needed or chipset: 3COM.winmodem
Under Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read DOCs/InfoGeneral.txt about alternatives.
Writing DOCs/Intel.txt
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
CLASS=0403
PCIDEV=8086:2668
SUBSYS=1043:81a6
IRQ=16
HDA=8086:2668
SOFT=8086:2668.HDA
High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
and many are supported by the ALSA audio+modem driver snd-hda-intel
A modem was not detected on HDA card 8086:2668.
If another modem card is present, then most likely 8086:2668 does not host a modem.
If another modem card has not been detected, then possibilities are:
1) A Conexant modem chip is present on 8086:2668, as Conexant chips
are frequently not detectable by ALSA diagnostics
2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
Try detection with Root permission:
sudo wvdialconf /etc/wvdial.conf
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary device ID: 8086:2668
Subsystem PCI_id 1043:81a6
Softmodem codec or chipset from diagnostics:
from Archives:
Support type needed or chipset:
Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.
2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.3.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
Writing DOCs/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.3.3
and the compiler used in kernel assembly: 4.3.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.28-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 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 pppd properties:
-rwsr-xr-- 1 root dip 277352 Feb 20 20:55 /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/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/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/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
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
Bootup.txt:
A modem device/card may be disabled at bootup, due to a variety of causes.
Look at the bootup diagnostics record dmesg.txt and try to garner some
understanding from it. Attach it to your query to discuss@linmodems.org
Possibilities therein are too diverse to be automagically processed by
scanModem. A line including the PCI
bus slot 00:1b.0 of your modem, and "disable" or "disabling" predicts problems,
though sometimes corrected later in the bootup. Similarly a line with "@"
in the interrupt (IRQ) for your 00:1b.0 slot is predictive of problems.
Possible corrections are:
1) Within the boot up BIOS, change from a Windows to a non-PNP/Other Operating System type.
Instructions for accessing BIOS are at:
http://linmodems.technion.ac.il/resources.html within: Additional Resourcces.
2a) Add an option "pci=routeirq" to the kernel boot up line.
Here is an example paragraph from /boot/grub/menu.lst :
title Ubuntu, kernel 2.6.15-26-686
root (hd0,6)
kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq
initrd /boot/initrd.img-2.6.15-26-686
savedefault
2b) Same as above, but use "pollirq" instead of "pci=routeirq".
3) Within some BIOS setups, IRQ assignments can be changed.
4) On non-laptop systems, moving the modem card to another slot has helped.
5) Blacklist as many drivers as possible. See
http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01593.html
6) Sometimes upgrading the kernel solves the problem.
7) Sometimes downgrading the kernel solves the problem.
8) Sometimes changing the Linux distribution solves the problem.
9) Get unloading.gz from http://linmodems.technion.ac.il/linmodems/
This script unloads excess drivers which may be competing for resources.
Before trying to set up the modem, do:
$ gunzip unloading.gz
$ chmod +x unloading
$ su - root
# ./unloading
Or for Ubuntu related Distros
$ sudo ./unloading
لطفا به دادم برسید!
موضوع: کمک در شناختن مودم (دفعات بازدید: 1178 بار)
