Re: Raymond Kongola, Tanzania kernel 2.6.24-19-lpia

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

 



Ray,

ATM I have few ideas, but you may see this document to see if it helps you out

http://jcostom.wordpress.com/2008/09/02/howto-verizon-um175-usb-evdo-card-under-ubuntu-hardy/

Regards,

Antonio

On Wed, Feb 16, 2011 at 3:15 PM,  <raykongstar@xxxxxxxxx> wrote:
> Sorry for a late reply,refer to our previous conversation below to recall my problem! I have used wvdialconf /etc/wvdialconf but it [ubuntu kernel 2.6.24-19-lpia] did not detect any modem so i then went on to the next one [lsusb, to check my usb ports if they have any devices] and bus 002 had one with ID 0eab:c893 which happened to be the same address detected by your very own scanMODEM [refer my modemDATA.txt], AND the model of my 3G EVDO USB MODEM is "u893"! So did scan modem detect my modem or it's merely coincidental? I hope that way u can help me better, so scanMODEM detected my modem but it couldn't idk ,"sort it out"? See below:
> Attached USB devices are:
>  ID 0eab:c893
> 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
>
> Regards [Antonio]!
>
> -original message-
> Subject: Re: Raymond Kongola, Tanzania kernel 2.6.24-19-lpia
> From: Antonio Olivares <olivares14031@xxxxxxxxx>
> Date: 13/02/2011 21:25
>
> Ray,
>
> Ok, you may try the following:
>
> $ sudo wvdialconf /etc/wvdial.conf
>
> and see if it finds the modem port?
>
> Send us the output of
> $ sudo lsusb
> to see if this posts useful information regarding your usb modem.
>
> scanModem also reported the following:
>
>
> If a USB modem or cellphone is attached and was not detected, please
> provide available information in your request to discuss@xxxxxxxxxxxxx
> '
> Hope this helps,
>
> Antonio
>
> On Sun, Feb 13, 2011 at 12:21 AM,  <raykongstar@xxxxxxxxx> wrote:
>> So it's a fail for me, i mean scanMODEM couldn't identify my PCI modems . Unfortunately i don't have a dual boot system (with WinXP) in this notebook...it's a mini dell n-series notebook and it had ubuntu hardy on it by default, so maybe i can do a manufacturer check and get the vendor id as you suggested!  But my interest wasn't for this PCI modem,it was for an attached USB modem which i guess scanmodem couldnt digg, here is some of the useful info including chipset type of that USB modem which i happen to dont have the drivers:
>>
>> H/W
>> Interface Type:USB Type
>> Baudrate:Default 230,400 bps
>> (Changeable)
>> Transmitting (Max. Data Rate):
>> Forward Link 2.4Mbps / Reverse
>> Link 153.6kbps
>> Supply Voltage:5V
>> S/W
>> CDMA Specification:1x RTT / EVDO
>> Applied
>> Data ServiceIS-707A, IS-707A-1
>> SMS:MO & MT Support
>> PRL (Preferred Roaming
>> List):Support
>> Authentification:Support
>> Number of NAM support: 5
>> DM (Diagnostic
>> Monitor):Qualcomm CAIT
>> Transmitter
>> Frequency Range:824.64 ~
>> 848.37 MHz / 1851.25 ~ 1908.75
>> MHz
>> Band Width:1.25 MHz
>> Type of Oscillation:PLL
>> Synthesizer
>> Receiver
>> Frequency Range:869.64 ~
>> 893.37 MHz / 1931.25 ~ 1988.75
>> MHz
>> Modulation Method:QPSK
>> Receiver Sensitivity:-104dBm
>> (FER = 0.5%)
>> Common RF Impedance50 ohm
>> Mechanical
>> Dimensions (W x D x H):56 x 54 x
>> 12.7 mm
>> Weight:about 50 g
>> Antenna:Single Band Diversity
>> antenna
>> LED:PCMCIA Card LED 1 / Green
>> and Red
>>
>> -original message-
>> Subject: Re: Raymond Kongola, Tanzania kernel 2.6.24-19-lpia
>> From: Antonio Olivares <olivares14031@xxxxxxxxx>
>> Date: 13/02/2011 18:37
>>
>> Ray,
>>
>> scanModem could not find a modem among the pci devices.  If you have a
>> dual-boot system you may try:
>>
>>  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.
>>
>> Otherwise, your modem could be supported by hsfmodem drivers:
>>
>> 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 you try the drivers fro linuxant and they are unresponsive, it
>> could be the following:
>>
>>
>> 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   1028:02b0   Audio device: Intel Corporation 82801G
>>
>>  Modem interrupt assignment and sharing:
>>  21:       1307          0   IO-APIC-fasteoi   HDA Intel
>>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>> [   17.941950] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level,
>> low) -> IRQ 21
>> [   17.941998] PCI: Setting latency timer of device 0000:00:1b.0 to 64
>> [  897.505603] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
>> [    0.852865] PM: Writing back config space on device 0000:00:1b.0 at
>> offset 1 (was 100006, writing 100002)
>> [    0.852912] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level,
>> low) -> IRQ 21
>> [    0.852931] PCI: Setting latency timer of device 0000:00:1b.0 to 64
>> [  955.232292] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
>> [    0.803979] PM: Writing back config space on device 0000:00:1b.0 at
>> offset 1 (was 100006, writing 100002)
>> [    0.804026] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level,
>> low) -> IRQ 21
>> [    0.804045] PCI: Setting latency timer of device 0000:00:1b.0 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.
>>
>> Regards,
>>
>> Antonio
>>
>> On Sun, Feb 13, 2011 at 1:12 AM,  <raykongstar@xxxxxxxxx> wrote:
>>> ** Thanks very much for your response, here are the contents of the modemdata.txt**
>>>
>>> --------------------------  System information ----------------------------
>>> CPU=i686,  Ubuntu ,  ALSA_version=1.0.16
>>> Linux version 2.6.24-19-lpia (root@macbook) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon Nov 3 15:25:26 UTC 2008
>>>  scanModem update of:  2010_12_12
>>>
>>> Distrib_ID=Ubuntu
>>> DistribCodeName=hardy
>>>
>>>
>>> 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 0eab:c893
>>> 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
>>>
>>> Candidate PCI devices with modem chips are:
>>> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
>>> High Definition Audio cards can host modem chips.
>>>
>>> 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   1028:02b0   Audio device: Intel Corporation 82801G
>>>
>>>  Modem interrupt assignment and sharing:
>>>  21:       1307          0   IO-APIC-fasteoi   HDA Intel
>>>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>>> [   17.941950] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
>>> [   17.941998] PCI: Setting latency timer of device 0000:00:1b.0 to 64
>>> [  897.505603] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
>>> [    0.852865] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
>>> [    0.852912] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
>>> [    0.852931] PCI: Setting latency timer of device 0000:00:1b.0 to 64
>>> [  955.232292] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
>>> [    0.803979] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
>>> [    0.804026] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
>>> [    0.804045] PCI: Setting latency timer of device 0000:00:1b.0 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 modem cards detected by "aplay -l"  are: None
>>>
>>>
>>> The /proc/asound/pcm file reports:
>>> -----------------------
>>> 00-04: ALC268 Analog : ALC268 Analog : capture 1
>>> 00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1
>>>
>>> about /proc/asound/cards:
>>> ------------------------
>>>  0 [Intel          ]: HDA-Intel - HDA Intel
>>>                      HDA Intel at 0xf0540000 irq 21
>>>
>>>  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-19-lpia/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko
>>>
>>>  The HDA diagnostics did not recognize a modem chip on the audio subsystem,
>>>  though a Conexant chip modem might not be recognized.
>>>
>>> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>>>
>>> A candidate modem is not transparent among the PCI devices:
>>> ------------------------------------------------
>>> 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
>>> 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
>>> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
>>> 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
>>> 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
>>> 02:00.0 System peripheral: JMicron Technologies, Inc. Unknown device 2382
>>> 02:00.2 SD Host controller: JMicron Technologies, Inc. Unknown device 2381
>>> 02:00.3 System peripheral: JMicron Technologies, Inc. Unknown device 2383
>>> 03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
>>> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev 02)
>>> ------------------------------------------------
>>>  with USB, bridge, and RAM devices not displayed.
>>> If a High Definition Audio card is present, if might be hosted on the Subsystem.
>>>
>>> If your modem is an
>>>   external USB type,
>>>   connected by an external serial cable,
>>>   or mounted internally on an ISA card,
>>> then 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.
>>>
>>>
>>> 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=1028:02b0
>>> IRQ=21
>>> HDA2=00:1b.0
>>> SOFT=8086:27d8.HDA
>>>
>>>  For candidate modem in:  00:1b.0
>>>   0403 Audio device: Intel Corporation 82801G
>>>      Primary device ID:  8086:27d8
>>>    Subsystem PCI_id  1028:02b0
>>>    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_alsa1.0.16.tar.gz from:
>>>   http://linmodems.technion.ac.il/packages/smartlink/
>>>
>>>
>>>  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
>>>
>>>  linux-headers-2.6.24-19-lpia resources needed for compiling are not manifestly ready!
>>>  The patch utility is needed for compiling ALSA drivers, and possibly others.
>>>
>>>  If compiling is necessary packages must be installed, providing:
>>>    linux-headers-2.6.24-19-lpia
>>>
>>>
>>> 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 261032 2007-10-04 19:37 /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
>>>
>>> For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/  get faxing.tar.gz
>>> It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
>>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1
>>> 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 --------
>>>
>>>
>>
>>
>
>



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

  Powered by Linux