This is a mis-understanding: ----------------------------------------------- RE: Connexant commercial drivers are available for certain modem chipsets, just not Intel. They are also kernel specific, so when you automatically update a kernel, you need to buy a new driver. ----------------------------------------------- WWW.Linuxant.com supports diverse Conexant chipsets, from ancient Legacy designs to the newert chips hosted on High Definition Audio cards. The hsfmodem code packages at the bottom of http://www.linuxant.com/drivers/hsf/full/downloads.php can be compiled with resources for any Linux kernel release. But additionally, Linuxant provides the nice service of compiling drivers matched with emerging kernels of the more popular distros. Purchase of the software key enabling full speed service, also provides for free updates to emerging kernels. One certainly does NOT have to pay for support for each new kernel. The major problem with maintaining modem services is the component of the modem code, pre-compiled (and thus encrypted) by the chip manufacture. This Closed Source protects (whether we like it or not) the chip makers most crucial Proprietary Information. This Closed Source component cannot as a consequence be debugged/optimized against evolving Linux code. Nethertheless, volunteers associated with this List (for various periods) have able to keep a variety of modems functional, for routine dialup connections and also fax services for many of them. It isn't an issue of the capabilities of diverse contributors/maintainers, but rather that the Linux debug toolset cannot work with Closed Source code. Moreover some chip manufacturers have over the years provided updates of the Closed Source component. Certainly the best solution if a modem is essential for one's CONNECT to the Internet, is to buy a Controller Chipset modem (which may be external or internal) and is supported by Open Source Linux code. But for those with laptops, and poorer/foreign Users, this is not a feasible solution. To compensate, many of we List participants do whatever is possible to aid Linux newbies. MarvS scanModem maintainer On Tue, Oct 6, 2009 at 6:05 PM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > Denbigh, > > > Here are several constructive suggestions: > > > You can FAX with kernel 2.6.28-11 - this proves that your modem driver > works, THUS: > > > First suggestion: no need to buy any hardware nor software, beware of panic > generators. > > > Second suggestion: think well, do you REALLY need a newer kernel? Can't you > stick to 2.6.28.-11 until an automatic installer for 2.6.28-15 will become > available? > > > Third suggestion: trust the experimental physicist who writes to you here. > Work step by step to set up your PPP connection. With kernel 2.6.28-11, use > wvdial first, not yet GnomePPP (which as far as I remember itself uses > wvdial), to debug your connections. wvdialconf, the configuration tool going > with wvdial, will set up the strings, but much more important, it gives > debugging information (hidden by more "friendly" commands such as GnomePPP). > > Once wvdial will work, you can play with GUI's such as GnomePPP -- if you > have nothing better to do : I use wvdial since Fall of year 2000 and have > not yet felt the need to waste one minute for anything else. > > > The key question is of course, do you absolutely need kernel 2.6.28-15? This > is an insisting question to a novice: the file which you have installed for > your modem needs to be generated for 2.6.28-15, which is not straightforward > for a novice, even may seem frightening the first time you do it. Some > people believe that they always need the last version, immediately. Some > think that what counts is to be able to do their work (I belong to that > second category, since 1961: take a look at http://cern.ch, see what > frontier science is doing, most of us using kernel 2.6.9, soon moving to > 2.6.18 , not 28, not 31, because we have other concerns than "having the > most recent one"). > > > Also, unfortunately, from time to time some novice advisors pop up in this > discussion, eventually fooling people like you in need of support for a > 2.6.28 kernel with their own problem with for example 2.6.31, scaring you > with the need to buy another modem while your own works fine, and quoting > prices in units of thousands of dollars while all you need is offred free to > you - except perhaps your time invested in asking yourself what exactly you > need, in this case which kernel. > > > Jacques > > > > 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 > >
