Brett, ttyS2 is the modem port, judging from, [ 1.569627] 0000:02:0a.0: ttyS2 at I/O 0xc300 (irq = 18) is a 16550A Try making a symbolic link: # ln -sf /dev/ttyS2 /dev/modem Then try: # wvdialconf which should find the modem. If so, try the fax again specifying /dev/ttyS2 as the modem port. MarvS On Fri, Apr 3, 2009 at 10:35 AM, Brett Liggett <brett_h_l@xxxxxxxxx> wrote: > I am sending this file in hopes that anyone can assist. When I run efax I > get the following - > > efax: Fri Apr 3 08:35:26 2009 efax v 0.9a-001114 Copyright 1999 Ed Casas > efax: Fri Apr 3 08:35:26 2009 efax v 0.9a-001114 Copyright 1999 Ed Casas > efax: 35:26 compiled Jun 21 2006 05:59:09 > efax: 35:26 Error: can't open serial port /dev/modem: No such file or > directory > efax: 35:26 done, returning 2 (unrecoverable error) > > > 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.27-11-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.27-11-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu > 4.3.2-1ubuntu11) ) #1 SMP Thu Jan 29 19:24:39 UTC 2009 > scanModem update of: 2009_02_21 > > There are no blacklisted modem drivers in /etc/modprobe* files > Potentially useful modem drivers now loaded are: > > > Attached USB devices are: > ID 045e:009d Microsoft Corp. > If a cellphone is not detected, see > http://ubuntuforums.org/archive/index.php/t-878554.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 02:0a.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 02:0a.0 12b9:1008 12b9:00d3 Serial controller: 3Com > Corp, Modem Division 56K FaxModem Model 5610 > > Modem interrupt assignment and sharing: > 18: 4 IO-APIC-fasteoi ohci1394 > --- Bootup diagnostics for card in PCI slot 02:0a.0 ---- > [ 0.424449] PCI: 0000:02:0a.0 reg 10 io port: [c300, c307] > [ 0.424472] pci 0000:02:0a.0: supports D2 > [ 0.424474] pci 0000:02:0a.0: PME# supported from D0 D2 D3hot D3cold > [ 0.424477] pci 0000:02:0a.0: PME# disabled > [ 1.569440] serial 0000:02:0a.0: PCI INT A -> Link[APC3] -> GSI 18 > (level, low) -> IRQ 18 > [ 1.569627] 0000:02:0a.0: ttyS2 at I/O 0xc300 (irq = 18) is a 16550A > > The PCI slot 02:0a.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 02:0a.0: > Modem chipset detected on > NAME="Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 " > CLASS=0700 > PCIDEV=12b9:1008 > SUBSYS=12b9:00d3 > IRQ=18 > IDENT=USrobotics.serial > > For candidate modem in: 02:0a.0 > 0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 > Primary device ID: 12b9:1008 > Support type needed or chipset: USrobotics.serial > > > ----------------end Softmodem section -------------- > Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem > technology. > Their winmodems have no Linux support. Their controller chipset modems > are supported by the Linux serial drivers. > The PCI id 12b9:1008 modem is Supported. > > PCI ID Name Support status > ------------------------------------------------------------------------------- > 10b7:1006 3COM 0038TA AC101 - TF Mini-PCI winmodem, not > supported > 10b7:1007 3COM 3C556 V.90 Mini-PCI winmodem, not > supported > 12b9:1006 US Robotics 3cp803598 Voice winmodem, not > supported > 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not > supported > > 12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver > supported > 12b9:1008 US Robotics 3cp803598 serial driver > supported > sudo wvdialconf wvtest , should detect the modem. Read > DOCs/Testing.txt > ====== end 3COM section ======= > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.3.2 > and the compiler used in kernel assembly: 4.3.2 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.3 > linuc_headers base folder /lib/modules/2.6.27-11-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 277160 2008-11-20 13:58 /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:# 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 > /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 > /etc/modprobe.d/alsa-base: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 -------- > > >
