Hello, There are 2 parts to this message. Part 1: Question about Conexant modem ------------------------------------- I have the following configuration, and I have two questions. Q1. scanModem recommends I get the Conexant driver from Linuxant. Linuxant has 2 driver flavors, one is free (limited to 14.4K) and the other, for $20, is apparently unrestricted. My question is, I want to use this modem to build an answering machine i.e. only to listen and process incoming calls, so do I need to get the full version for twenty bucks or can I get by with the free version? (My configuration details are below.) Q2. Has anyone had success with the Linuxant driver for my specific modem type (PCI ID is below)? I have seen reports here and on other sites for 14f1:2f00 but not for 14f1:2013. I can't find that particular device on pcidatabase or any of the other PCI databases. (Of course, I intend to try it shortly, and will post my experience here.) Any help will be appreciated. TIA. -Sam My configuration: (ModemData.txt) -------------------------- System information ---------------------------- CPU=i686, Linux version 2.6.24-19-server (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 15:18:00 UTC 2008 scanModem update of: 2008_10_24 There are no blacklisted modem drivers in /etc/modprobe* files USB modems not recognized For candidate card in slot 03:07.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 03:07.0 14f1:2013 155d:8850 Communication controller: Conexant HSF 56k Data/Fax Modem [... more lines from ModemData.txt elided here but I can post them if needed ] Part 2: scanModem bug --------------------- When I first ran scanModem (downloaded about 4 hours ago from linmodems.org), I got the following. $ ./scanModem UPDATE=2008_10_24 Continuing as this update is only 2 weeks old, but the current Update is always at: http://linmodems.technion.ac.il Please rename this script scanModem, or some files will not print out. Abort with Ctrl-C, or wait 5 seconds to continue. grep: 01:05.1: No such file or directory grep: 01:05.1: No such file or directory [hangs] I traced this bug to the following lines in scanModem, and I fixed it. Perhaps someone can incorporate the fix in the next update. The bug appears when some of the shell variables have spaces in them, and the solution is to have grep process them correctly. $ diff oscanModem scanModem ## lines with '>' have my fix 473,474c473,474 < if $LSPCI -n 2>/dev/null | grep $HDAbus | grep Class >/dev/null ; then < HDAdev=$($LSPCI -n 2>/dev/null | grep $HDAbus | cut -d' ' -f4) --- > if $LSPCI -n 2>/dev/null | grep "$HDAbus" | grep Class >/dev/null ; then > HDAdev=$($LSPCI -n 2>/dev/null | grep "$HDAbus" | cut -d' ' -f4) 476c476 < HDAdev=$($LSPCI -n 2>/dev/null | grep $HDAbus | cut -d' ' -f3) --- > HDAdev=$($LSPCI -n 2>/dev/null | grep "$HDAbus" | cut -d' ' -f3) 478c478 < HDAold=$(grep $HDAdev $TMPM.hda 2>/dev/null) --- > HDAold=$(grep "$HDAdev" "$TMPM.hda" 2>/dev/null)
