On Tuesday 06 October 2009 17:07:31 denbigh1974@xxxxxxx wrote: > Hello > > I posted here > http://ubuntuforums.org/showthread.php?t=1277358 > to explain my problem but the thread ran out of steam. I was hoping that > perhaps you could assist? > > I have a p.c. with an Intel 537EP faxmodem card installed in a PCI slot. > I want to use this to send out faxes from my desktop and preferably to > use with GnomePPP also. > > The p.c. dual boots into Windows XP (where I am experienced) or Ubuntu > 9.04 (where I am a complete novice). In Windows, my modem is detected on > COM3 > > I booted up into Ubuntu and ran scanModem. Here is an extract from the > resulting ModemData.txt file: > > For candidate card in slot 03:01.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 03:01.0 8086:1080 8086:1000 Modem: Intel Corporation FA82537EP > 56K V.92 Data/Fax Modem PCI > > Modem interrupt assignment and sharing: > 17: 2974 0 IO-APIC-fasteoi Intel ICH5, serial > --- Bootup diagnostics for card in PCI slot 03:01.0 ---- > [ 0.455494] pci 0000:03:01.0: reg 10 32bit mmio: [0xfeaff000-0xfeafffff] > [ 0.455501] pci 0000:03:01.0: reg 14 io port: [0xbc00-0xbcff] > [ 0.455536] pci 0000:03:01.0: PME# supported from D0 D3hot D3cold > [ 0.455541] pci 0000:03:01.0: PME# disabled > [ 1.505776] serial 0000:03:01.0: PCI INT A -> GSI 17 (level, low) -> > IRQ 17 > [ 1.505908] 0000:03:01.0: ttyS1 at I/O 0xbc08 (irq = 17) is a 16450 > [ 1.505989] 0000:03:01.0: ttyS2 at I/O 0xbc10 (irq = 17) is a 8250 > [ 1.506071] 0000:03:01.0: ttyS3 at I/O 0xbc18 (irq = 17) is a 16450 > [ 1.506096] Couldn't register serial port 0000:03:01.0: -28 > > 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. > > > === Finished firmware and bootup diagnostics, next deducing cogent > software. === > > Predictive diagnostics for card in bus 03:01.0: > Modem chipset detected on > NAME="Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI " > CLASS=0703 > PCIDEV=8086:1080 > SUBSYS=8086:1000 > IRQ=17 > IDENT=INTEL537EP > > For candidate modem in: 03:01.0 > 0703 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI > Primary device ID: 8086:1080 > Support type needed or chipset: INTEL537EP > > > > > > I downloaded and installed the 537EP driver (deb file, I don't know how > to compile tar files yet) from > http://groups.google.com/group/ubuntu-modems/web/modem-driver-downloads-for >-537ep > > I have now managed to get Efax-gtk working with the modem if I use > Ubuntu 9.04 kernel 2.6.28-11. It doesn't work with kernel 2.6.28-15. > > I had to play experiment with different init strings and hardware > parameters before it would work in Ubuntu 9.04 kernel 2.6.28-11. If I > use the following Efax-gtk settings, I can successfully send a fax: > > IDENTITY > CSID name and number as necessary > > MODEM > Serial Device: 537 > Lock file: /var/lock > Capabilities: 1,5,0,2,0,0,0,0 > Rings: 2 > Modem Class: Class 2 > Dial Mode: Tone > > PARAMS > Initialisation Params: Z &F&D2&C1&K3S7 &K3 (copied these from Windows XP) > Reset Params: Z > Other Params: > > > > I can also get wvdial to dial out if my wvdial.conf file is edited as > follows: > > [Dialer Defaults] > Modem = /dev/537 > Baud = 9600 > Init1 = ATZ > Init2 = AT&F&D2&C1&K3S7=55 > Init3 = AT&K3 > Phone = 08450792829 > Username = Steve > Password = ******** > # New PPPD = yes > > > What I can't do is get Gnome PPP to recognise /dev/537. When I run Gnome > PPP the init strings are different from those in wvdial.conf and the > modem can't be found. I can't modify the default the init 2 string in > Gnome PPP and when I test for a modem none can be found. > > I just wondered if you had any suggestions, please? (I am a beginner so > would appreciate cut-and-paste text to insert into Nautilus.) > > Many thanks > Steve Francis This is EXACTLY what I want to do, using openSUSE 11.1. My level of experience is about the same as Steve's. I followed the instructions on the LinModem website and when the driver I downloaded failed to compile, I asked for help from this mailing list (after much googling!) Unfortunately, my appeal for help only seem to have triggered World War 3 !!! Can we start afresh? Can anyone offer any constructive suggestions for a poor openSuse user? Thanks Lawson
