Go to the Linuxant page: http://www.linuxant.com/drivers/hsf/index.php?PHPSESSID=ed8a86ac05fa3aa498260d65841b820d Your modem is listed there: If you computer is a dell computer you can go to their site and get a driver from them, read Conexant.txt in Modem/ folder. Otherwise, on the Linuxant page, download the hsf modem Note: (Cut and pasted from Conexant.txt generated from scanModem) -Find the HCF or HSF menu in the left part of the screen. -Read README. -Read INSTALLATION. -Click DOWNLOAD. -Accept conditions. -Find text: "You can download HCF (or HSF) modem packages from the driver download page." and click there. -Look for your distribution, your processor, and your kernel. -Download the matching file. -Read again and, if you do this under Windows, print the installation instructions matching the kind of driver file which you downloaded. -Now just follow these instructions. http://www.linuxant.com/drivers/hsf/downloads-patches.php has patches that may be necessary for recent kernels. A detailed software installation example is provided at: http://linmodems.technion.ac.il/archive-fourth/msg00350.html Regards, Antonio On Nov 21, 2007 11:08 AM, Dave Arsenault <dnarsenault@xxxxxxxxx> wrote: > I'm new to Linux. Can you help me get my modem > working? > > Thanks, > > Dave > > > ____________________________________________________________________________________ > Be a better sports nut! Let your teams follow you > with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ > 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.20-15-generic > With this Subject Line cogent experts will be alerted, and useful case names left in the Archive. > YourCountry will enable Country specific guidance. Your contry's local Linux experts > can be found through: http://www.linux.org/groups/index.html > 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.20-15-generic (root@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007 > scanModem update of: 20071114 > > > There are no blacklisted modem drivers in /etc/modprobe* files > > Potentially useful modem drivers now loaded are: > snd_atiixp_modem > > USB modem not detected by lsusb > > For candidate card, firmware information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:14.6 1002:4378 103c:30ae Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller > > Modem interrupt assignment and sharing: > 16: 569 IO-APIC-fasteoi ATI IXP, ATI IXP Modem > > > The Advanced Linux Sound Architecture (ALSA) packages providing audio support, > also includes drivers for some modems. The ALSA diagnostics are written during > bootup to /proc/asound/ folders. > > > A modem was not detected though HDA card diagnostics. But a possible Conexant modem chip > impervious to ALSA diagnostics is not excluded. > > > Deductions above are from information in > > /proc/asound/cards: > 0 [IXP ]: ATIIXP - ATI IXP > ATI IXP rev 2 with unknown codec at 0xc0003400, irq 16 > 1 [Modem ]: ATIIXP-MODEM - ATI IXP Modem > ATI IXP Modem rev 2 at 0xc0003800, irq 16 > > /proc/asound/pcm: > 00-00: ATI IXP AC97 : ATI IXP AC97 : playback 1 : capture 1 > 01-00: ATI IXP MC97 : ATI IXP MC97 : playback 1 : capture 1 > > A copy of /proc/asound had been copied to Modem/ALSAdave.tgz > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > > There is candidate modem software. > > For candidate modem in PCI bus: 00:14.6 > Class 0703: 1002:4378 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller > Primary PCI_id 1002:4378 > Subsystem PCI_id 103c:30ae > Softmodem codec or chipset from diagnostics: > from Archives: > > > Lacking a dsp (digital signal processing) chip, the modem is a software > intensive or "softmodem" type. Its primary controller manages the traffic > with the CPU. But the software needed is specified in the Subsystem. > ----------------------------------------- > Support type needed or chipset: > > Support can likely be achieved through two mutually exclusive alternatives: > 1) The hsfmodem software for Conexant chipset modems: Read Conexant.txt > The following ALSA alternative CANNOT work with Conexant modems. > > 2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for details, and > to test get the package SLMODEMD.gcc4.1.tar.gz from: > http://linmodems.technion.ac.il/packages/smartlink/ > > > scanModem could not identify the Support Type needed from diagnosics or archives. > If an alternative boot into Microsoft windows can be done, do mouse > clicks on: > Start > Settings > Control Panel > Classical View (for Window XP) > System > > Hardware > Device Manager > Modems > Click on the + > Modem. Double click to > expand the graphic. Manufacturer information may be displayed. For example, CXT > stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor > and device information. > Next do the Query Modem and record the ATI specifications displayed such as: > ATI3 - Agere SoftModem Version 2.1.22 > ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 > Try to identify the modem setup file, with name perhaps MODEM.INF. > If may contain chipset Vendor informaton. > > > 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 Conexant.txt > > Read Conexant.txt > > Writing Conexant.txt > > Writing Smartlink.txt > ============ end Smartlink section ===================== > > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.1.2 > and the compiler used in kernel assembly: 4.1.2 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder /lib/modules/2.6.20-15-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 libc6-dev (and for Debian/Ubuntu, linux-libc-dev). The also required headers of package libc6 are commonly installed by default. > > > > 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 pacakage > 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 269224 2007-04-04 22:41 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://phep2.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/YourSystem.txt concerning other COMM channels: eth0 eth0:avah > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for the 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:options snd-atiixp-modem index=-2 > /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 > /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 > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > >