Re: Mike C, USA, CentOS release 6.2 (Final) Kernel kernel 2.6.32-220.23.1.el6.x86_64

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

 



Mike,

For one chipset hopefully it is a true serial modem,

For candidate card in slot 00:03.3, firmware information and bootup
diagnostics are:
 PCI slot       PCI ID          SubsystemID     Name
 ----------     ---------       ---------       --------------
 00:03.3        8086:2a07       17aa:20d4       Serial controller: Intel
Corporation Mobile PM965/GM965 KT Controller

 Modem interrupt assignment and sharing:
 17:         85         14   IO-APIC-fasteoi   uhci_hcd:usb6,
firewire_ohci
 --- Bootup diagnostics for card in PCI slot 00:03.3 ----
pci 0000:00:03.3: reg 10 io port: [0x1830-0x1837]
pci 0000:00:03.3: reg 14 32bit mmio: [0xfe224000-0xfe224fff]
serial 0000:00:03.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
0000:00:03.3: ttyS1 at I/O 0x1830 (irq = 17) is a 16550A


Try the following as root:
$ su -
passwd:
# wvdialconf /etc/wvdial.conf

let it run and send us the information that it outputs.  Hopefully it
finds /dev/ttyS1 as the modem port, and all that would remain is to
configure wvdial.conf with ISP phone number, username, and password
and attempt to connect with
# wvdial

Please send list(discuss@xxxxxxxxxxxxx) the output of wvdialconf
/etc/wvdial.conf

Regards,

Antonio

On Tue, Jul 3, 2012 at 5:38 PM, Mike Cavanagh <mike@xxxxxxxxxxxxxxxxxxx> wrote:
> Sorry I do not understand this better, but I am not sure where to
> start...
> I have a Lenovo (IBM) Thinkpad X61s with an internal Intel modem
> Looks like the modem Chipset is the PM965
> It is located in PCI slot 3.0
>
> I can see the message: "pci 0000:00:03.0: PME# disabled"  in the Dmesg,
> but I am not sure if it is relevant.  I assume it is.
>
> I assume I will need to find a driver, but no idea how to find it.
>
> Bsaed on the file below:
>         Does it appear I have a modem that can work or am I done at the
> start?
>         If it can work, does it look like I just need the proper
> configuration or do I need to compile drivers, etc.?
>
> Any help is much appreciated.
> Please let me know if you need more information.
> Thanks,
> Mike C.
>
>
> ModemData.Txt:-------------------------
>
>
> 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 CentOS release 6.2 (Final)
> Kernel  kernel 2.6.32-220.23.1.el6.x86_64
>  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=x86_64,  CentOS
> Kernel ,  ALSA_version=1.0.21
> Linux version 2.6.32-220.23.1.el6.x86_64
> (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.4.6 20110731 (Red
> Hat 4.4.6-3) (GCC) ) #1 SMP Mon Jun 18 18:58:52 BST 2012
>  scanModem update of:  2011_08_08
>
> /etc/lsb-release not found
>
>
> 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
>
>
> Some modem drivers can only be used in 32 bit modem on x86_64 systems,
> while some others are competent on x86_64 Systems.  Cases are:
> 1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
>
> for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem
> controllers.
> In both cases, 32 bit libraries must be installed to support the
> slmodemd helper having a precompiled 32 bit component.
> 2) For USB modems using the slusb.ko driver. 32 bit libraries must be
> installed to support the slmodemd helper having a precompiled 32 bit
> component
> 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are
> x86_64 competent.
> 4) agrsm packages for LSI/AgereSystems softmodems are not competent on
> x86_64 systems.
>
>  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 17ef:1000 Lenovo
>  ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
>  ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
>  ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
>  ID 058f:9254 Alcor Micro Corp. Hub
>  ID 04b4:2324 Cypress Semiconductor Corp.
>  ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
>  ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader
>  ID 06e1:d804 ADS Technologies, Inc.
>  ID 8086:0630 Intel Corp. Pocket PC Camera
> 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:03.0 Communication controller: Intel Corporation Mobile PM965/GM965
> MEI Controller (rev 0c)
> 00:03.3 Serial controller: Intel Corporation Mobile PM965/GM965 KT
> Controller (rev 0c)
> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> Controller (rev 03)
> High Definition Audio cards can host modem chips.
>
> For candidate card in slot 00:03.0, firmware information and bootup
> diagnostics are:
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:03.0        8086:2a04       17aa:20d1       Communication
> controller: Intel Corporation Mobile PM965/GM965 MEI Controller
>
>  Modem interrupt assignment and sharing:
>  --- Bootup diagnostics for card in PCI slot 00:03.0 ----
> pci 0000:00:03.0: reg 10 64bit mmio: [0xfe226000-0xfe22600f]
> pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:03.0: PME# disabled
> pci 0000:03:00.0: reg 10 64bit mmio: [0xfdf00000-0xfdf01fff]
> pci 0000:03:00.0: PME# supported from D0 D3hot D3collsd
> pci 0000:03:00.0: PME# disabled
> iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwlagn 0000:03:00.0: setting latency timer to 64
> iwlagn 0000:03:00.0: Detected Intel(R) Wireless WiFi Link 4965AGN,
> REV=0x4
> iwlagn 0000:03:00.0: device EEPROM VER=0x36, CALIB=0x5
> iwlagn 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
> iwlagn 0000:03:00.0: irq 29 for MSI/MSI-X
> iwlagn 0000:03:00.0: firmware: requesting iwlwifi-4965-2.ucode
> iwlagn 0000:03:00.0: loaded firmware version 228.61.2.24
>
>  The PCI slot 00:03.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:03.3, firmware information and bootup
> diagnostics are:
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:03.3        8086:2a07       17aa:20d4       Serial controller: Intel
> Corporation Mobile PM965/GM965 KT Controller
>
>  Modem interrupt assignment and sharing:
>  17:         85         14   IO-APIC-fasteoi   uhci_hcd:usb6,
> firewire_ohci
>  --- Bootup diagnostics for card in PCI slot 00:03.3 ----
> pci 0000:00:03.3: reg 10 io port: [0x1830-0x1837]
> pci 0000:00:03.3: reg 14 32bit mmio: [0xfe224000-0xfe224fff]
> serial 0000:00:03.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> 0000:00:03.3: ttyS1 at I/O 0x1830 (irq = 17) is a 16550A
>
> 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       17aa:20ac       Audio device: Intel
> Corporation 82801H
>
>  Modem interrupt assignment and sharing:
>  28:       1649        288   PCI-MSI-edge      hda_intel
>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> pci 0000:00:1b.0: reg 10 64bit mmio: [0xfe220000-0xfe223fff]
> pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1b.0: PME# disabled
> HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> HDA Intel 0000:00:1b.0: irq 28 for MSI/MSI-X
> 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 modem cards detected by "aplay -l"  are: None
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: AD198x Analog : AD198x Analog : playback 1 : capture 2
> 00-01: AD198x Digital : AD198x Digital : playback 1
>
> about /proc/asound/cards:
> ------------------------
>  0 [Intel          ]: HDA-Intel - HDA Intel
>                       HDA Intel at 0xfe220000 irq 28
>
>  PCI slot 00:1b.0 has a High Definition Audio Card
>  The drivers are in the kernel modules tree at:
>
> /lib/modules/2.6.32-220.el6.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko
> /lib/modules/2.6.32-220.17.1.el6.x86_64/kernel/sound/pci/hda/snd-hda-int
> el.ko
> /lib/modules/2.6.32-220.23.1.el6.x86_64/kernel/sound/pci/hda/snd-hda-int
> el.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. ===
>
> Predictive  diagnostics for card in bus 00:03.3:
>         Modem chipset  detected on
> NAME="Serial controller: Intel Corporation Mobile PM965/GM965 KT
> Controller "
> CLASS=0700
> PCIDEV=8086:2a07
> SUBSYS=17aa:20d4
> IRQ=17
> SOFT=8086:2a07.MC97
> IDENT=mc97
>
>  For candidate modem in:  00:03.3
>    0700 Serial controller: Intel Corporation Mobile PM965/GM965 KT
> Controller
>       Primary device ID:  8086:2a07
>     Subsystem PCI_id  17aa:20d4
>     Softmodem codec or chipset from diagnostics:
>                                from    Archives:
>
>
>
>
> The soft modem is in the ac97/mc97 category. However the diagnostics
> were not effective,
> and an archival record for is lacking for the modem codec of pair:
>         8086:2a07 17aa:20d4
> Try to acquire more information by running the modem diagnostics under a
> Microsoft boot,
> as described in SoftModem.txt
>
>
> Writing DOCs/Intel.txt
>
>
> Predictive  diagnostics for card in bus 00:03.0:
>         Modem chipset not detected on
> NAME="Communication controller: Intel Corporation Mobile PM965/GM965 MEI
> Controller "
> CLASS=0780
> PCIDEV=8086:2a04
> SUBSYS=17aa:20d1
> IRQ=10
> HDA2=00:1b.0
>
>  For candidate modem in:  00:03.0
>    0780 Communication controller: Intel Corporation Mobile PM965/GM965
> MEI Controller
>       Primary device ID:  8086:2a04
>  Support type needed or chipset:
>
>
>
> 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=17aa:20ac
> IRQ=28
>
>  For candidate modem in:  00:1b.0
>    0403 Audio device: Intel Corporation 82801H
>       Primary device ID:  8086:284b
>  Support type needed or chipset:
>
>
>  Completed candidate modem analyses.
>
>  The base of the UDEV device file system is: /dev/.udev
>
>  Versions adequately match for the compiler installed: 4.4.6
>              and the compiler used in kernel assembly: 4.4.6
>
>
>
>  Minimal compiling resources appear complete:
>    make utility - /usr/bin/make
>    Compiler version 4.4
>    linuc_headers base folder
> /lib/modules/2.6.32-220.23.1.el6.x86_64/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:
>         -r-xr-xr-x. 1 root root 359592 Aug 22  2010 /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)
>          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
>
> 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
> virbr0 wlan0
> 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:
>
>      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