Nick, You have done everything according to instructions and your modem is not functioning correctly? Did you reboot and try it again? The wvdial packages have been updated for newer Ubuntu release wvdial_karmic.zip, but sadly the page at linmodems is currently down :( Details of the Request: URL: http://linmodems.technion.ac.il/packages/ Protocol: http Date and Time: Sunday 13 December 2009 03:01 Additional Information: linmodems.technion.ac.il: Socket operation timed out Description: The server linmodems.technion.ac.il refused to allow this computer to make a connection. For the other problem modem not found/responding, rebooting the machine and giving it a retry does it find the modem? Let us know and report back. Regards, Antonio On 12/13/09, Nick Wahl <nwahl@xxxxxxxxxxxxxx> wrote: > Thank you, Antonio, for your prompt help! > > I believe I did everything the way you recommended. However, I could > not get it to work (yet) and, even after reading up on possible causes > and trying possible solutions, I cannot tell why - which, of course, > tells you how much of an expert I am at this. > > Please have a look at what I did and my comments in ( ). > > Before I attempt more complicated possible solutions, I would > appreciate your advice. I am, therefore, also attaching dmesg.txt in > case you need it. > > Your help is very much appreciated. Thank you! - Nick > > ************************************* > Step 1 > nw@nw:~$ sudo dpkg -i hsfmodem*.deb > (Reading database ... 114040 files and directories currently installed.) > Unpacking hsfmodem (from > hsfmodem_7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb) ... > Setting up hsfmodem (7.80.02.05full-k2.6.31-14-generic-1.ubuntu) ... > Conexant HSF softmodem driver, version 7.80.02.05full > > Pre-built driver modules that seem compatible with your system were > found under > /usr/lib/hsfmodem/modules/binaries/linux-2.6.31-14-generic-SMP. > > Warning: no device detected by hsf driver - HDA modems may require reboot > > (Why wouldn't it be detected if it was detected by scanModem? I > couldn't find any evidence that it has been disabled. There is some > Firmware missing, but I can't tell if that has anything to do with > this. I would have liked to reboot the modem, but I don't know how to > do that.) > > Note: HDA support not compiled in the driver > > Note: kernel module snd-via82xx-modem overridden by hsfmc97via > Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis > Note: kernel module snd-atiixp-modem overridden by hsfmc97ati > > Step 2 > nw@nw:~$ sudo wvdialconf /etc/wvdial.conf > sudo: wvdialconf: command not found > nw@nw:~$ > > Steps 3 > nw@nw:/etc/wvdial$ sudo unzip wv*.zip > Archive: wvdial_jaunty_i386.zip > inflating: wvdial_jaunty_i386/debconf_1.5.26ubuntu3_all.deb > inflating: wvdial_jaunty_i386/libuniconf4.4_4.4.1-0.2ubuntu2_i386.deb > inflating: > wvdial_jaunty_i386/libwvstreams4.4-base_4.4.1-0.2ubuntu2_i386.deb > inflating: > wvdial_jaunty_i386/libwvstreams4.4-extras_4.4.1-0.2ubuntu2_i386.deb > inflating: wvdial_jaunty_i386/libxplc0.3.13_0.3.13-1build1_i386.deb > inflating: wvdial_jaunty_i386/Readme.txt.txt > inflating: wvdial_jaunty_i386/wvdial_1.60.1+nmu2_i386.deb > > (I am running Ubuntu 9.10 Karmic Koala, not Jaunty and the CPU is an > i686 not an i386. I cannot tell if that would have something to do > with it.) > > Step 4 > nw@nw:/etc/wvdial/wvdial_jaunty_i386$ sudo dpkg -i *.deb > dpkg: warning: downgrading debconf from 1.5.27ubuntu2 to 1.5.26ubuntu3. > (Reading database ... 115932 files and directories currently installed.) > Preparing to replace debconf 1.5.27ubuntu2 (using > debconf_1.5.26ubuntu3_all.deb) ... > Unpacking replacement debconf ... > Selecting previously deselected package libuniconf4.4. > Unpacking libuniconf4.4 (from libuniconf4.4_4.4.1-0.2ubuntu2_i386.deb) ... > Selecting previously deselected package libwvstreams4.4-base. > Unpacking libwvstreams4.4-base (from > libwvstreams4.4-base_4.4.1-0.2ubuntu2_i386.deb) ... > Selecting previously deselected package libwvstreams4.4-extras. > Unpacking libwvstreams4.4-extras (from > libwvstreams4.4-extras_4.4.1-0.2ubuntu2_i386.deb) ... > Selecting previously deselected package libxplc0.3.13. > Unpacking libxplc0.3.13 (from libxplc0.3.13_0.3.13-1build1_i386.deb) ... > Selecting previously deselected package wvdial. > Unpacking wvdial (from wvdial_1.60.1+nmu2_i386.deb) ... > Setting up debconf (1.5.26ubuntu3) ... > > Setting up libxplc0.3.13 (0.3.13-1build1) ... > > Setting up libwvstreams4.4-base (4.4.1-0.2ubuntu2) ... > > Setting up libwvstreams4.4-extras (4.4.1-0.2ubuntu2) ... > > Setting up libuniconf4.4 (4.4.1-0.2ubuntu2) ... > > Processing triggers for man-db ... > Setting up wvdial (1.60.1+nmu2) ... > > Sorry. You can retry the autodetection at any time by running > "wvdialconf". > (Or you can create /etc/wvdial.conf yourself.) > > Processing triggers for libc-bin ... > ldconfig deferred processing now taking place > nw@nw:/etc/wvdial/wvdial_jaunty_i386$ > > Step 5 (trying again:) > nw@nw:~$ 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? > > (Why wouldn't it be detected if scanModem did? It was not used by > another program and the info on setserial does not seem to apply here.) > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > (There are no FAQ at the above link.) > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > nw@nw:~$ > > (I don't want to try this, unless wvdial is the problem.) > > Step 6 > nw@nw:~$ sudo gedit /etc/wvdial.conf > [sudo] password for nw: > > (Details entered O.K.) > > Step 7 > nw@nw:~$ sudo wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot open /dev/modem: Input/output error > --> Cannot open /dev/modem: Input/output error > --> Cannot open /dev/modem: Input/output error > nw@nw:~$ > ******************************************** > > Antonio Olivares wrote: >> Nick, >> >> scanModem reports that you need hsfmodem drivers and that wvdial is >> not installed: >> >> For candidate modem in: 00:1b.0 >> 0403 Audio device: Intel Corporation 82801H >> Primary device ID: 8086:284b >> Subsystem PCI_id 103c:30d9 >> Softmodem codec or chipset from diagnostics: >> from Archives: >> >> >> >> Support type needed or chipset: hsfmodem >> >> >> 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.80.02.05full_k2.6.31_14_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. >> >> The dialer utility package WVDIAL does not appear to be installed on >> your System. >> For Ubuntu Jaunty users, there are at the bottom of >> http://linmodems.technion.ac.il/packages/: >> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems. >> wvdial_jaunty_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. >> >> Regards. >> >> >> Antonio >> >> On 11/30/09, Nick <nwahl@xxxxxxxxxxxxxx> 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_11_26 >>> >>> The dialer utility package WVDIAL does not appear to be installed on >>> your System. >>> For Ubuntu Jaunty users, there are at the bottom of >>> http://linmodems.technion.ac.il/packages/: >>> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems. >>> wvdial_jaunty_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 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse >>> ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device >>> 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 00:1b.0, firmware information and bootup >>> diagnostics are: >>> PCI slot PCI ID SubsystemID Name >>> ---------- --------- --------- -------------- >>> 00:1b.0 8086:284b 103c:30d9 Audio device: Intel Corporation 82801H >>> >>> Modem interrupt assignment and sharing: >>> 22: 1051 IO-APIC-fasteoi HDA Intel >>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>> [ 0.293090] pci 0000:00:1b.0: reg 10 64bit mmio: >>> [0x72400000-0x72403fff] >>> [ 0.293159] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>> [ 0.293164] pci 0000:00:1b.0: PME# disabled >>> [ 8.913160] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, >>> low) -> IRQ 22 >>> [ 8.913198] 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: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1 >>> 00-01: Conexant Digital : Conexant Digital : playback 1 >>> >>> about /proc/asound/cards: >>> ------------------------ >>> 0 [Intel ]: HDA-Intel - HDA Intel >>> HDA Intel at 0x72400000 irq 22 >>> >>> 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 00:1b.0: >>> Modem chipset detected on >>> NAME="Audio device: Intel Corporation 82801H " >>> CLASS=0403 >>> PCIDEV=8086:284b >>> SUBSYS=103c:30d9 >>> IRQ=22 >>> HDA=8086:284b >>> SOFT=8086:284b.HDA >>> IDENT=hsfmodem >>> Driver=hsfmodem-drivers >>> >>> For candidate modem in: 00:1b.0 >>> 0403 Audio device: Intel Corporation 82801H >>> Primary device ID: 8086:284b >>> Subsystem PCI_id 103c:30d9 >>> Softmodem codec or chipset from diagnostics: >>> from Archives: >>> >>> >>> >>> Support type needed or chipset: hsfmodem >>> >>> >>> 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.80.02.05full_k2.6.31_14_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. >>> >>> The directions following below need only be pursued, if the above >>> procedures are not adequate. >>> >>> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to >>> find the >>> hsfmodem package matching your System. For several Linux distros, >>> there are >>> precompiled drivers matched to specific kernels. These have within the >>> FileName, >>> your KernelVersion: 2.6.31_14_generic >>> They can be found through >>> http://www.linuxant.com/drivers/hsf/full/downloads.php >>> A more precise location may be given a few paragraphs below. >>> If an EXACT Match with your your KernelVersion is not found, one of the >>> "Generic packages with source" near the bottom of the page must be used. >>> Downloaded packages must be moved into the Linux partition (home >>> folder is OK) >>> and unzipped with: >>> unzip hsf*.zip >>> The installation command for a .deb suffic packages is, with root/adm >>> permission: >>> sudo dpkg -i hsf*.deb >>> while for .rpm suffix it is, with: >>> rpm -i hsf*.rpm >>> >>> Support for Conexant chips hosted on High Definition Audio cards may >>> require >>> installation of additional packages, one of the alsa-driver-linuxant >>> packages >>> on http://www.linuxant.com/alsa-driver/ At the same time download the >>> alsa-driver-1.0.17-1.patch , in case it prove to be later needed. >>> During the >>> hsfmodem install, there will be a message if there is necessary >>> installation of >>> alsa-driver-linuxant >>> >>> The installation command for a .deb suffic packages is, with root/adm >>> permission: >>> sudo dpkg -i hsf*.deb >>> while for .rpm suffix it is, with: >>> rpm -i hsf*.rpm >>> >>> There may a message that "Dependencies" are not satisfied. In this >>> case the Ubuntu/Debian packages to be installed are linux-libc-dev & >>> libc6-dev. Package >>> names may be different for other Linuxes. If not on your install CD, >>> these >>> packages can be searched for at http://packages.ubuntu.com. After >>> download, >>> they can be coinstalled with: >>> sudo dpkg -i li*.deb >>> Again try the alsa-driver-linuxant >>> >>> There may be a message that the patch must be applied. In this case >>> get the >>> ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2 >>> Under Linux, this package is unpacked with: >>> $ tar jxf alsa*.tar.bz2 >>> Next the patch is applied with: >>> $ patch -p0 < alsa-driver-1.0.17-1.patch >>> >>> See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html >>> for details on compiling and installing replacement snd-hda-intel + its >>> dependent drivers. >>> After the installation is completed, rerun the hsfmodem installation. >>> Reboot and try to detect the modem with Root permission: >>> sudo wvdialconf /etc/wvdial.conf >>> >>> Read DOCs/Conexant.txt >>> >>> Writing DOCs/Conexant.txt >>> >>> >>> 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-21 03: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/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 >>> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >>> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >>> Within any ancient /etc/devfs files: >>> >>> Within ancient kernel 2.4.n /etc/module.conf files: >>> >>> --------- end modem support lines -------- >>> >>> >>> >>> >> >> >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.339 / Virus Database: 270.14.88/2537 - Release Date: 11/30/09 >> 21:05:00 >> > > > >
