Marv, You did look at which version he is using right? -------------------------- System information ---------------------------- CPU=i686, Ubuntu , ALSA_version=1.0.18 Linux version 2.6.28-19-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #61-Ubuntu SMP Wed May 26 23:35:15 UTC 2010 scanModem update of: 2010_05_29 Distrib_ID=Ubuntu DistribCodeName=jaunty AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ He is using jaunty, so that is why I recommended that package. Did I do something wrong? Regards, Antonio On 6/24/10, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: >> Do download: >> http://linmodems.technion.ac.il/packages/wvdial_jaunty_i386.zip > ----- > No, this is outdated for your Ubuntu Lucid system > If you have an alternate Internet mode, do: > $ sudo apt-get update > $ sudo apt-get wvdial > > If not, start at: > http://packages.ubuntu.com/lucid/wvdial > in addition to wvdial, you will need its depedent packages: > libuniconf4.6 > libwvstreams4.6-base > libwvstreams4.6-extras > All the others on that page are likely installed already > One all downloaded and copied to your home folder, they can all be > installed with: > $ sudo dpkg -i *.deb > > MarvS > scanModem maintainer > > > > On Thu, Jun 24, 2010 at 4:27 PM, Antonio Olivares > <olivares14031@xxxxxxxxx> wrote: >> Robert, >> >> Do download: >> >> http://linmodems.technion.ac.il/packages/wvdial_jaunty_i386.zip >> >> unzip and install with >> $ sudo dpkg -i wvd* >> >> Regards, >> >> Antonio >> >> On 6/24/10, cpr-greenville <cpr-greenville@xxxxxxxxxxxxx> wrote: >>> How do I get mvdialconf? >>> >>> Results: >>> user@Ice-2-Go:~$ sudo wvdialconf /etc/wvdial.conf >>> [sudo] password for user: >>> sudo: wvdialconf: command not found >>> user@Ice-2-Go:~$ >>> >>> >>> >>> >>> On Thu, 2010-06-24 at 16:26 +0000, Antonio Olivares wrote: >>>> Robert, >>>> >>>> You may try to get the modem: >>>> >>>> Predictive diagnostics for card in bus 03:01.0: >>>> Modem chipset detected on >>>> NAME="Communication controller: Agere Systems Venus Modem " >>>> CLASS=0780 >>>> PCIDEV=11c1:0480 >>>> SUBSYS=11c1:5656 >>>> IRQ=17 >>>> IDENT=Agere.Venus_serial_drivers >>>> >>>> For candidate modem in: 03:01.0 >>>> 0780 Communication controller: Agere Systems Venus Modem >>>> Primary device ID: 11c1:0480 >>>> Support type needed or chipset: Agere.Venus_serial_drivers >>>> >>>> Using the native linux drivers. You will need to check by doing >>>> $ sudo wvdialconf /etc/wvdial.conf >>>> >>>> and hopefully it finds the modem port. Then you may edit file >>>> $ sudo gedit /etc/wvdial.conf >>>> >>>> and remove the ";" and add username/ISP phone/and password. First >>>> check to see if wvdialconf finds the modem. >>>> >>>> If the modem were not to respond for some reason or another, try to >>>> follow the advice provided by scanModem here: >>>> >>>> For candidate card in slot 03:01.0, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID SubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 03:01.0 11c1:0480 11c1:5656 Communication >>>> controller: Agere Systems >>>> Venus Modem >>>> >>>> Modem interrupt assignment and sharing: >>>> 17: 1 0 IO-APIC-fasteoi >>>> --- Bootup diagnostics for card in PCI slot 03:01.0 ---- >>>> [ 0.416396] pci 0000:03:01.0: reg 10 32bit mmio: >>>> [0xfebefc00-0xfebefcff] >>>> [ 0.416402] pci 0000:03:01.0: reg 14 io port: [0xe800-0xe8ff] >>>> [ 0.416408] pci 0000:03:01.0: reg 18 io port: [0xe400-0xe4ff] >>>> [ 0.416414] pci 0000:03:01.0: reg 1c io port: [0xe080-0xe087] >>>> [ 0.416436] pci 0000:03:01.0: supports D2 >>>> [ 0.416438] pci 0000:03:01.0: PME# supported from D2 D3hot D3cold >>>> [ 0.416441] pci 0000:03:01.0: PME# disabled >>>> [ 1.361374] serial 0000:03:01.0: PCI INT A -> GSI 17 (level, low) -> >>>> IRQ 17 >>>> [ 1.361455] 0000:03:01.0: ttyS2 at I/O 0xe800 (irq = 17) is a 16550A >>>> >>>> The PCI slot 03:01.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 6/24/10, CPR-Greenville <cpr-greenville@xxxxxxxxxxxxx> 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.28-19-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, Ubuntu , ALSA_version=1.0.18 >>>> > Linux version 2.6.28-19-generic (buildd@palmer) (gcc version 4.3.3 >>>> > (Ubuntu 4.3.3-5ubuntu4) ) #61-Ubuntu SMP Wed May 26 23:35:15 UTC 2010 >>>> > scanModem update of: 2010_05_29 >>>> > >>>> > Distrib_ID=Ubuntu >>>> > DistribCodeName=jaunty >>>> > AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >>>> > >>>> > >>>> > 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 045e:0009 Microsoft Corp. IntelliMouse >>>> > ID 046e:52ce Behavior Tech. Computer Corp. >>>> > 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: >>>> > 03:00.0 Communication controller: Conexant Systems, Inc. Device 10b4 >>>> > (rev 89) >>>> > 03:01.0 Communication controller: Agere Systems Venus Modem (V90, >>>> > 56KFlex) >>>> > 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High >>>> > Definition Audio Controller (rev 01) >>>> > High Definition Audio cards can host modem chips. >>>> > >>>> > For candidate card in slot 03:00.0, firmware information and bootup >>>> > diagnostics are: >>>> > PCI slot PCI ID SubsystemID Name >>>> > ---------- --------- --------- -------------- >>>> > 03:00.0 14f1:10b4 a0a0:010d Communication controller: >>>> > Conexant Systems, >>>> > Inc. Device 10b4 >>>> > >>>> > Modem interrupt assignment and sharing: >>>> > --- Bootup diagnostics for card in PCI slot 03:00.0 ---- >>>> > [ 0.416327] pci 0000:03:00.0: reg 10 32bit mmio: >>>> > [0xfebf0000-0xfebfffff] >>>> > [ 0.416333] pci 0000:03:00.0: reg 14 io port: [0xec00-0xec07] >>>> > [ 0.416362] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold >>>> > [ 0.416366] pci 0000:03:00.0: PME# disabled >>>> > >>>> > The PCI slot 03:00.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 03:01.0, firmware information and bootup >>>> > diagnostics are: >>>> > PCI slot PCI ID SubsystemID Name >>>> > ---------- --------- --------- -------------- >>>> > 03:01.0 11c1:0480 11c1:5656 Communication controller: >>>> > Agere Systems >>>> > Venus Modem >>>> > >>>> > Modem interrupt assignment and sharing: >>>> > 17: 1 0 IO-APIC-fasteoi >>>> > --- Bootup diagnostics for card in PCI slot 03:01.0 ---- >>>> > [ 0.416396] pci 0000:03:01.0: reg 10 32bit mmio: >>>> > [0xfebefc00-0xfebefcff] >>>> > [ 0.416402] pci 0000:03:01.0: reg 14 io port: [0xe800-0xe8ff] >>>> > [ 0.416408] pci 0000:03:01.0: reg 18 io port: [0xe400-0xe4ff] >>>> > [ 0.416414] pci 0000:03:01.0: reg 1c io port: [0xe080-0xe087] >>>> > [ 0.416436] pci 0000:03:01.0: supports D2 >>>> > [ 0.416438] pci 0000:03:01.0: PME# supported from D2 D3hot D3cold >>>> > [ 0.416441] pci 0000:03:01.0: PME# disabled >>>> > [ 1.361374] serial 0000:03:01.0: PCI INT A -> GSI 17 (level, low) >>>> > -> >>>> > IRQ 17 >>>> > [ 1.361455] 0000:03:01.0: ttyS2 at I/O 0xe800 (irq = 17) is a >>>> > 16550A >>>> > >>>> > The PCI slot 03:01.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:1b.0, firmware information and bootup >>>> > diagnostics are: >>>> > PCI slot PCI ID SubsystemID Name >>>> > ---------- --------- --------- -------------- >>>> > 00:1b.0 8086:27d8 1462:7529 Audio device: Intel >>>> > Corporation 82801G >>>> > >>>> > Modem interrupt assignment and sharing: >>>> > 16: 1839 1872 IO-APIC-fasteoi uhci_hcd:usb5, HDA >>>> > Intel >>>> > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>>> > [ 0.415441] pci 0000:00:1b.0: reg 10 64bit mmio: >>>> > [0xfe978000-0xfe97bfff] >>>> > [ 0.415467] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>>> > [ 0.415470] pci 0000:00:1b.0: PME# disabled >>>> > [ 7.479734] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, >>>> > low) >>>> > -> IRQ 16 >>>> > [ 7.479786] 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. >>>> > >>>> > >>>> > === Finished firmware and bootup diagnostics, next deducing cogent >>>> > software. === >>>> > >>>> > Predictive diagnostics for card in bus 03:00.0: >>>> > Modem chipset detected on >>>> > NAME="Communication controller: Conexant Systems, Inc. Device 10b4 " >>>> > CLASS=0780 >>>> > PCIDEV=14f1:10b4 >>>> > SUBSYS=a0a0:010d >>>> > IRQ=10 >>>> > HDA2=00:1b.0 >>>> > IDENT=hcfpcimodem >>>> > >>>> > For candidate modem in: 03:00.0 >>>> > 0780 Communication controller: Conexant Systems, Inc. Device 10b4 >>>> > Primary device ID: 14f1:10b4 >>>> > Support type needed or chipset: hcfpcimodem >>>> > >>>> > >>>> > >>>> > 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 >>>> > >>>> > The modem requires a hcflinmodem package. >>>> > >>>> > For all code packages from Linuxant.com, either a driver set matching >>>> > the boot kernel will be installed, >>>> > or the drivers will first be compiled and then installed. The expert >>>> > on >>>> > modem software for Linux is >>>> > "Support (Jonathan)" <modem.support@xxxxxxxxxxxx> >>>> > >>>> > From >>>> > http://www.linuxant.com/drivers/hcf/full/downloads-ubuntu-x86.php >>>> > download >>>> > hcfpcimodem-7.80.02.06full_k2.6.28_19_generic_ubuntu_i386.deb.zip >>>> > Under Linux unpack with: >>>> > $ unzip hcfpcimodem*.zip >>>> > Then install with: >>>> > $ sudo dpkg -i hcfpcimodem*.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. >>>> > 03:00.0 >>>> > 03:01.0 >>>> > Read DOCs/Conexant.txt >>>> > >>>> > Writing DOCs/Conexant.txt >>>> > >>>> > >>>> > >>>> > Predictive diagnostics for card in bus 03:01.0: >>>> > Modem chipset detected on >>>> > NAME="Communication controller: Agere Systems Venus Modem " >>>> > CLASS=0780 >>>> > PCIDEV=11c1:0480 >>>> > SUBSYS=11c1:5656 >>>> > IRQ=17 >>>> > IDENT=Agere.Venus_serial_drivers >>>> > >>>> > For candidate modem in: 03:01.0 >>>> > 0780 Communication controller: Agere Systems Venus Modem >>>> > Primary device ID: 11c1:0480 >>>> > Support type needed or chipset: Agere.Venus_serial_drivers >>>> > >>>> > >>>> > >>>> > >>>> > 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=1462:7529 >>>> > IRQ=16 >>>> > >>>> > For candidate modem in: 00:1b.0 >>>> > 0403 Audio device: Intel Corporation 82801G >>>> > Primary device ID: 8086:27d8 >>>> > 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.3.3 >>>> > and the compiler used in kernel assembly: 4.3.3 >>>> > >>>> > The patch utility is needed for compiling ALSA drivers, and possibly >>>> > others. >>>> > >>>> > >>>> > Minimal compiling resources appear complete: >>>> > make utility - /usr/bin/make >>>> > Compiler version 4.3 >>>> > linuc_headers base folder /lib/modules/2.6.28-19-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-20 12: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 >>>> > >>>> > 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 -------- >>>> > >>>> > I have a Multitec and a Aopen modem installed with Linux 9.2 running. >>>> > Can someone assist with getting one of the modems to communicate. I >>>> > will >>>> > remove whichever modem is not used. >>>> > >>>> > Thanks, >>>> > >>>> > Robert >>>> > cpr-greenville@xxxxxxxxxxxxx >>>> > >>>> > >>> >>> >> >
