Re: Roan, Ukraine kernel 2.6.24-18-generic

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

 



my modem is Agere Systems HDA Modem


On Thu, 10 Jul 2008 17:59:04 -0400
 "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> wrote:
Roan,

I presume your modem is internal and Not one of
Attached USB devices:
ID 09da:000a A4 Tech Co., Ltd
ID 0c45:62c0 Microdia.

Read the Softmodem.txt for instructions for doing modem diagnositcs
under Microsoft.

MarvS

On Thu, Jul 10, 2008 at 1:07 PM, roan <roan@xxxxxxxx> wrote:
thx for an answer, Marvin
i did all as you said, but $ sudo wvdialconf /etc/wvdial.conf now says this:
$ sudo wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: Scanning ttySHSF0 first, /dev/modem is a link to it. Modem Port Scan<*1>: SHSF0 S0 S1 S2 S3 SHSF1 SHSF2 SHSF3
Modem Port Scan<*1>: SHSF4 SHSF5 SHSF6 SHSF7


Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?

what alse should i do?
thx in advance

On Thu, 10 Jul 2008 07:45:02 -0400
 "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> wrote:

Roan

Your most likely situation is:

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:284b.
If another modem card is present, then most likely 8086:284b 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:284b, as Conexant chips
are frequently not detectable by ALSA diagnostics

so try

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php download hsfmodem-7.68.00.07full_k2.6.24_18_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt  for details.
 Read DOCs/Conexant.txt

Please report back after thus testing,

MarvS



On Thu, Jul 10, 2008 at 7:16 AM, roan <roan@xxxxxxxx> 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.24-18-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.24-18-generic (buildd@terranova) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed May 28 20:27:26 UTC 2008
 scanModem update of:  2008_06_28

There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
 ID 09da:000a A4 Tech Co., Ltd
 ID 0c45:62c0 Microdia

USB modems not recognized

For candidate card in slot 00:1b.0, firmware information and bootup
diagnostics are:
 PCI slot       PCI ID          SubsystemID     Name
---------- --------- --------- -------------- 00:1b.0 8086:284b 1462:3fe9 Audio device: Intel
Corporation 82801H

 Modem interrupt assignment and sharing:
21: 407 392 IO-APIC-fasteoi uhci_hcd:usb4, HDA Intel --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- [ 34.842294] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low)
->
IRQ 21
[ 34.842316] PCI: Setting latency timer of device 0000:00:1b.0 to 64


===== 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.

 PCI slot 00:1b.0 has a High Definition Audio Card
 The drivers are in the kernel modules tree at:

 /lib/modules/2.6.24-18-generic/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko

/lib/modules/2.6.24-19-generic/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko

The ALSA verion is 1.0.15
The modem cards detected by "aplay -l"  are: None


The /proc/asound/pcm file reports:
-----------------------
00-02: ALC883 Analog : ALC883 Analog : capture 1
00-01: ALC883 Digital : ALC883 Digital : playback 1
00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 1

about /proc/asound/cards:
------------------------
 0 [Intel          ]: HDA-Intel - HDA Intel
                    HDA Intel at 0xf9ff8000 irq 21
=== Finished firmware and bootup diagnostics, next deducing cogent
software.
===

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
SATA
IDE Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M G
(rev
a1)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
Network
Connection (rev 02)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B
PCI Express Gigabit Ethernet controller (rev 01)
05:04.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller
(rev
02)
05:04.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD
Controller
(rev 01)
05:04.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev
02)
------------------------------------------------
 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 DOCs/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. From the Driver Details TAB, copy out the 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 /proc/asound/ audio+modem diagostics are being copied.
 Finished copy to Modem/ALSAroot.tgz

Predictive diagnostics for card in bus 00:1b.0:
      Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1462:3fe9
IRQ=21
HDA=8086:284b
SOFT=8086:284b.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:284b.
If another modem card is present, then most likely 8086:284b 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:284b, 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 82801H
    Primary device ID:  8086:284b
  Subsystem PCI_id  1462:3fe9
  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.2.tar.gz from:
      http://linmodems.technion.ac.il/packages/smartlink/

----------------end Softmodem section --------------

Writing DOCs/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
DOCs/Conexant.txt

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php download hsfmodem-7.68.00.07full_k2.6.24_18_generic_ubuntu_i386.deb.zip
 Under Linux unpack with:
 $ unzip hsfmodem*.zip
 Then install with:
 $ sudo dpkg -i hsfmodem*.deb
 Subsequently, the modem should be found with
 $ sudo wvdialconf /etc/wvdial.conf
 Edit in your personal information with:
 $ sudo gedit /etc/wvdial.conf
 and try dialing out with:
 $ sudo wvdial.
 See DOCs/Testing.txt  for details.
 Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt

Writing DOCs/Smartlink.txt
============ end Smartlink section =====================


 The base of the UDEV device file system is: /dev/.udev

Versions adequately match for the compiler installed: 4.2.3 and the compiler used in kernel assembly: 4.2.3


 Minimal compiling resources appear complete:
 make utility - /usr/bin/make
 Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.24-18-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.
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 269256 2007-10-04 22: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/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: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 --------
---
Professional hosting for everyone - http://www.host.ru


---
Professional hosting for everyone - http://www.host.ru


---
Professional hosting for everyone - http://www.host.ru

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

  Powered by Linux