Wesley, I am sorry, but you are right. This scanModem returns the same results as the other one. My gut feeling is that the martian code will serve this modem. I guess it will not hurt to try it out. Carefully read the page http://martian.barrelsoutofbond.org/ Download the latest driver either from there or from http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ You can look at a compiling example and a readme http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/Compile.Example.html and the readme http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/Readme-NOW.html Hope this works out. Sorry for making you do double work, when the newer scanModem returns the same thing. Regards, Antonio --- Wesley Platt <wesley.platt@xxxxxxxxx> wrote: > Here are the contents of my ModemData.txt file. What > do I do next? > -------------------------- System information > ---------------------------- > CPU=i686, Ubuntu 7.04 > 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: 2007_May_11 > > > ALSAversion 1.0.13 > USB modem not detected by lsusb > > Modem or host audio card candidates have firmware > information: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:13.0 11c1:0441 158d:5517 Communication > controller: Agere Systems > 56k WinModem > > Modem interrupt assignment and sharing: > 11: 25397 XT-PIC-XT > r128@pci:0000:01:00.0 > > --- Bootup diagnositcs for card in PCI slot 00:13.0 > ---- > > === Finished modem firmware and bootup diagnostics > section. === > === Next deducing cogent software === > > Completed candidate modem analyses. > > 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 > > Kernel-header resources needed for compiling are > not manifestly ready! > > If compiling is necessary packages must be > installed, providing: > linux-headers-2.6.20-15-generic > > > 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 > > > 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 -------- > ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265
