Allen RE > For candidate modem in: 04:08.0 > 0700 Serial controller: U.S. Robotics Device 0152 > Primary device ID: 16ec:0152 The Class 0700 devices are software modems, and the US Robotics software modems have never had support under Linux. Thus it is most likely that support under Linux cannnot be achieved. Nevertheless it would do no harm to run: $ sudo wvdialconf to attempt modem detection. But we expect there will be a failure: Sincerely: MarvS scanModem maintainer On Mon, Nov 5, 2012 at 6:38 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Allen, > > as scanModem's output to ModemData.txt explains, just run the following: > > 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 > > Can you connect to net with above command? > > Otherwise please post output of above commands so may try to help? > > Regards, > > > Antonio > > On Mon, Nov 5, 2012 at 4:32 PM, Allen Walker <auswalk@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 3.2.0-32-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=x86_64, Ubuntu , ALSA_version=1.0.24 >> Linux version 3.2.0-32-generic (buildd@batsu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 >> scanModem update of: 2011_08_08 >> >> Distrib_ID=Ubuntu >> DistribCodeName=precise >> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >> >> >> The dkms driver upgrade utilities are installed, >> >> >> 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 045e:0040 Microsoft Corp. Wheel Mouse Optical >> ID 06a3:8020 Saitek PLC Eclipse Keyboard >> ID 051d:0002 American Power Conversion Uninterruptible Power Supply >> 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: >> 04:08.0 Serial controller: U.S. Robotics Device 0152 (rev 02) >> 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) >> 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) >> High Definition Audio cards can host modem chips. >> >> For candidate card in slot 04:08.0, firmware information and bootup diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 04:08.0 16ec:0152 13a8:0128 Serial controller: U.S. Robotics Device 0152 >> >> Modem interrupt assignment and sharing: >> 16: 10905 0 IO-APIC-fasteoi snd_hda_intel, nvidia >> --- Bootup diagnostics for card in PCI slot 04:08.0 ---- >> [ 0.224164] pci 0000:04:08.0: [16ec:0152] type 0 class 0x000700 >> [ 0.224176] pci 0000:04:08.0: reg 10: [mem 0xcfeff000-0xcfeff3ff] >> [ 0.532413] serial 0000:04:08.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16 >> [ 0.532435] serial 0000:04:08.0: PCI INT A disabled >> >> The PCI slot 04:08.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:10.1, firmware information and bootup diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 00:10.1 10de:026c 10de:0162 Audio device: NVIDIA Corporation MCP51 High Definition Audio >> >> Modem interrupt assignment and sharing: >> 22: 995 0 IO-APIC-fasteoi ehci_hcd:usb1, snd_hda_intel >> --- Bootup diagnostics for card in PCI slot 00:10.1 ---- >> [ 0.216411] pci 0000:00:10.1: [10de:026c] type 0 class 0x000403 >> [ 0.216427] pci 0000:00:10.1: reg 10: [mem 0xcfff4000-0xcfff7fff] >> [ 0.216493] pci 0000:00:10.1: PME# supported from D3hot D3cold >> [ 0.216497] pci 0000:00:10.1: PME# disabled >> [ 6.283163] snd_hda_intel 0000:00:10.1: PCI INT B -> Link[APCI] -> GSI 22 (level, low) -> IRQ 22 >> [ 6.283191] snd_hda_intel 0000:00:10.1: setting latency timer to 64 >> [ 8.264161] input: HDA NVidia Line as /devices/pci0000:00/0000:00:10.1/sound/card0/input5 >> [ 8.264267] input: HDA NVidia Front Mic as /devices/pci0000:00/0000:00:10.1/sound/card0/input6 >> [ 8.264369] input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:10.1/sound/card0/input7 >> [ 8.264475] input: HDA NVidia Front Headphone as /devices/pci0000:00/0000:00:10.1/sound/card0/input8 >> [ 8.264564] input: HDA NVidia Line-Out Side as /devices/pci0000:00/0000:00:10.1/sound/card0/input9 >> [ 8.264653] input: HDA NVidia Line-Out CLFE as /devices/pci0000:00/0000:00:10.1/sound/card0/input10 >> [ 8.264738] input: HDA NVidia Line-Out Surround as /devices/pci0000:00/0000:00:10.1/sound/card0/input11 >> [ 8.264832] input: HDA NVidia Line-Out Front as /devices/pci0000:00/0000:00:10.1/sound/card0/input12 >> >> The PCI slot 00:10.1 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 01:00.1, firmware information and bootup diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 01:00.1 10de:0be3 3842:1302 Audio device: NVIDIA Corporation High Definition Audio Controller >> >> Modem interrupt assignment and sharing: >> 16: 10909 0 IO-APIC-fasteoi snd_hda_intel, nvidia >> --- Bootup diagnostics for card in PCI slot 01:00.1 ---- >> [ 0.216758] pci 0000:01:00.1: [10de:0be3] type 0 class 0x000403 >> [ 0.216768] pci 0000:01:00.1: reg 10: [mem 0xceffc000-0xceffffff] >> [ 8.265394] snd_hda_intel 0000:01:00.1: PCI INT B -> Link[AXV6] -> GSI 16 (level, low) -> IRQ 16 >> [ 8.265447] snd_hda_intel 0000:01:00.1: setting latency timer to 64 >> [ 9.152149] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input13 >> [ 9.152283] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input14 >> [ 9.152384] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input15 >> [ 9.152489] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input16 >> >> === Finished firmware and bootup diagnostics, next deducing cogent software. === >> >> A candidate modem is not transparent among the PCI devices: >> ------------------------------------------------ >> 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) >> 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev a1) >> 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev a1) >> 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev a1) >> 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) >> 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) >> 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS] (rev a2) >> 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) >> 04:08.0 Serial controller: U.S. Robotics Device 0152 (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:10.1: >> Modem chipset not detected on >> NAME="Audio device: NVIDIA Corporation MCP51 High Definition Audio " >> CLASS=0403 >> PCIDEV=10de:026c >> SUBSYS=10de:0162 >> IRQ=22 >> >> For candidate modem in: 00:10.1 >> 0403 Audio device: NVIDIA Corporation MCP51 High Definition Audio >> Primary device ID: 10de:026c >> Support type needed or chipset: >> >> >> >> Predictive diagnostics for card in bus 01:00.1: >> Modem chipset not detected on >> NAME="Audio device: NVIDIA Corporation High Definition Audio Controller " >> CLASS=0403 >> PCIDEV=10de:0be3 >> SUBSYS=3842:1302 >> IRQ=16 >> >> For candidate modem in: 01:00.1 >> 0403 Audio device: NVIDIA Corporation High Definition Audio Controller >> Primary device ID: 10de:0be3 >> Support type needed or chipset: >> >> >> >> Predictive diagnostics for card in bus 04:08.0: >> Modem chipset not detected on >> NAME="Serial controller: U.S. Robotics Device 0152 " >> CLASS=0700 >> PCIDEV=16ec:0152 >> SUBSYS=13a8:0128 >> IRQ=16 >> HDA2=00:10.1 >> HDA2=01:00.1 >> >> For candidate modem in: 04:08.0 >> 0700 Serial controller: U.S. Robotics Device 0152 >> Primary device ID: 16ec:0152 >> Support type needed or chipset: >> >> >> >> The base of the UDEV device file system is: /dev/.udev >> >> Versions adequately match for the compiler installed: 4.6.3 >> and the compiler used in kernel assembly: 4.6 >> >> linux-headers-3.2.0-32-generic resources needed for compiling are not manifestly ready! >> >> If compiling is necessary packages must be installed, providing: >> linux-headers-3.2.0-32-generic >> Compressed files at: /usr/src/linux-source-3.2.0.tar.bz2 >> >> >> 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 325744 Feb 4 2011 /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 >> 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 >> 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 -------- >>
