Re: MohsenHosseini, Iran kernel 2.6.31-14-generic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mohsen,

scanModem recommends martian-full-20080625.tar.gz package for your modem:

Predictive  diagnostics for card in bus 02:00.0:
        Modem chipset  detected on
 NAME="Communication controller: Agere Systems LT WinModem "
 CLASS=0780
 PCIDEV=11c1:044c
 SUBSYS=11c1:044c
 IRQ=10
 IDENT=Agere.DSP

  For candidate modem in:  02:00.0
   0780 Communication controller: Agere Systems LT WinModem
      Primary device ID:  11c1:044c
  Support type needed or chipset:        Agere.DSP

Download:

http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/martian-full-20080625.tar.gz

http://packages.ubuntu.com/karmic/libc6-dev

http://packages.ubuntu.com/karmic/linux-libc-dev

After downloading the above packages and copying them to your home
directory in Ubuntu, please do

$ sudo dpkg -i libc6-dev
and
$ sudo dpkg -i linux-libc-dev
after successful installation of these packages please do the
following install wvdial packages suggested too, and run
$ tar -zxvf martian-full-20080625.tar.gz
$ cd martian-full-20080625/
$ make all
$ sudo make install
$ sudo modprobe martian_dev
$ sudo martian_modem

Fireup another terminal/tab then when wvdial is installed(see below) run
$ sudo wvdialconf /etc/wvdial.conf

it will scan and hopefully find /dev/ttySM0 as the modem port.  You
should edit the file /etc/wvdial.conf with your favorite editor as
$ sudo ?name-of-editor? /etc/wvdial.conf
and remove the ";" and add your phone ISP/username and password and a
line "Carrier Check = no" save the file and attempt a dialout.


Also scanModem detects that wvdial was not installed on your system:

The dialer utility package WVDIAL does not appear to be installed on
 your System.
 For Ubuntu users, there are at the bottom of
 http://linmodems.technion.ac.il/packages/
 packages with the files necessary to install wvdial, with names like:
     wvdial_jaunty_amd64.zip   for x86_64, 64 bit bus systems.
     wvdial_jaunty_i386.zip    for 32 bit systems.
     wvdial_karmic_i386.zip    for 32 bit systems.
 These are about 1 MB in size.  After downloaded and copied into your
 Linux partition:
 $ unzip wv*.zip
 Within the new folder:
 $ sudo dpkg -i *.deb
 will  complete the wvdial installation
 Please read Modem/DOCs/wvdial.txt for usage information.

Should the above procedures not work, send us dmesg.txt as suggested below:

For candidate card in slot 02:00.0, firmware information and bootup
 diagnostics are:
  PCI slot       PCI ID          SubsystemID     Name
  ----------     ---------       ---------       --------------
  02:00.0        11c1:044c       11c1:044c       Communication
controller: Agere Systems
 LT WinModem

  Modem interrupt assignment and sharing:
  --- Bootup diagnostics for card in PCI slot 02:00.0 ----
 [    0.177995] pci 0000:02:00.0: reg 10 32bit mmio: [0xfebffc00-0xfebffcff]
 [    0.178001] pci 0000:02:00.0: reg 14 io port: [0xec00-0xec07]
 [    0.178007] pci 0000:02:00.0: reg 18 io port: [0xe800-0xe8ff]
 [    0.178041] pci 0000:02:00.0: supports D2
 [    0.178043] pci 0000:02:00.0: PME# supported from D2 D3hot
 [    0.178046] pci 0000:02:00.0: PME# disabled

  The PCI slot 02:00.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@xxxxxxxxxxxxx
  if help is needed.


Kind Regards,

Antonio

On 12/19/09, mohsen hosseini <mohsenhosseini2001@xxxxxxxxx> wrote:
>  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.31-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@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.31-14-generic (buildd@rothera) (gcc version 4.4.1
> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
>  scanModem update of:  2009_12_10
>
> The dialer utility package WVDIAL does not appear to be installed on
> your System.
> For Ubuntu users, there are at the bottom of
> http://linmodems.technion.ac.il/packages/
> packages with the files necessary to install wvdial, with names like:
>      wvdial_jaunty_amd64.zip   for x86_64, 64 bit bus systems.
>      wvdial_jaunty_i386.zip    for 32 bit systems.
>      wvdial_karmic_i386.zip    for 32 bit systems.
> These are about 1 MB in size.  After downloaded and copied into your
> Linux partition:
> $ unzip wv*.zip
> Within the new folder:
> $ sudo dpkg -i *.deb
> will  complete the wvdial installation
> Please read Modem/DOCs/wvdial.txt for usage information.
>
> Presently install your Linux Distributions dkms package. It provides
> for automated driver updates,
> following upgrade of your kernel.  For details see
> http://linux.dell.com/projects.shtml#dkms
>
>  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 0cf2:6230 ENE Technology, Inc.
> 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@xxxxxxxxxxxxx
>
> For candidate card in slot 02:00.0, firmware information and bootup
> diagnostics are:
>  PCI slot	PCI ID		SubsystemID	Name
>  ----------	---------	---------	--------------
>  02:00.0	11c1:044c	11c1:044c	Communication controller: Agere Systems
> LT WinModem
>
>  Modem interrupt assignment and sharing:
>  --- Bootup diagnostics for card in PCI slot 02:00.0 ----
> [    0.177995] pci 0000:02:00.0: reg 10 32bit mmio: [0xfebffc00-0xfebffcff]
> [    0.178001] pci 0000:02:00.0: reg 14 io port: [0xec00-0xec07]
> [    0.178007] pci 0000:02:00.0: reg 18 io port: [0xe800-0xe8ff]
> [    0.178041] pci 0000:02:00.0: supports D2
> [    0.178043] pci 0000:02:00.0: PME# supported from D2 D3hot
> [    0.178046] pci 0000:02:00.0: PME# disabled
>
>  The PCI slot 02:00.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@xxxxxxxxxxxxx
>  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:27d8	1043:8345	Audio device: Intel Corporation 82801G
>
>  Modem interrupt assignment and sharing:
>  16:        836        839   IO-APIC-fasteoi   uhci_hcd:usb5, HDA Intel
>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [    0.177239] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf9ffc000-0xf9ffffff]
> [    0.177276] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [    0.177279] pci 0000:00:1b.0: PME# disabled
> [    6.896709] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level,
> low) -> IRQ 16
> [    6.896728] 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@xxxxxxxxxxxxx
>  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.20
> The modem cards detected by "aplay -l"  are: None
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: VT1708B Analog : VT1708B Analog : playback 2 : capture 2
> 00-01: VT1708B Digital : VT1708B Digital : playback 1
>
> about /proc/asound/cards:
> ------------------------
>  0 [Intel          ]: HDA-Intel - HDA Intel
>                       HDA Intel at 0xf9ffc000 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.31-14-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 02:00.0:
> 	Modem chipset  detected on
> NAME="Communication controller: Agere Systems LT WinModem "
> CLASS=0780
> PCIDEV=11c1:044c
> SUBSYS=11c1:044c
> IRQ=10
> IDENT=Agere.DSP
>
>  For candidate modem in:  02:00.0
>    0780 Communication controller: Agere Systems LT WinModem
>       Primary device ID:  11c1:044c
>  Support type needed or chipset:	Agere.DSP
>
>
>
> Writing DOCs/Intel.txt
>
>
> Predictive  diagnostics for card in bus 00:1b.0:
> 	Modem chipset not detected on
> NAME="Audio device: Intel Corporation 82801G "
> CLASS=0403
> PCIDEV=8086:27d8
> SUBSYS=1043:8345
> IRQ=16
> HDA=8086:27d8
> SOFT=8086:27d8.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:27d8.
>  If another modem card is present, then most likely 8086:27d8 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:27d8, 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 82801G
>       Primary device ID:  8086:27d8
>     Subsystem PCI_id  1043:8345
>     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.4.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.4.1
>              and the compiler used in kernel assembly: 4.4.1
>
>  The patch utility is needed and 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.31-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 2009-02-20 20:25 /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 --------
>

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux