Tom, The ESScom 125d:2838 chipset modems are not supported under Linux. Compiling is necessary packages must be installed, providing: gcc-4.1 kernel-devel-2.6.15-1.2054_FC5 Then from http://linmodems.technion.ac.il/packages/Intel/Philippe.Vouters/ get the intel-536EP-2.56.76.0_2008_03_22.tar.bz2 Unpack under Linux with: tar jxf intel*.tar.bz2 And follow directions in the new folder. MarvS On Mon, Jul 21, 2008 at 10:36 AM, Tom Douglas <tompdoug-putergeek@xxxxxxxxx> wrote: > <P>Folks, I have the following (or attached) ModemData.txt file produced and am not sure what it's all telling me.</P> > <P> </P> > <P>The ESS.com modem has been installed for a while and, with this modem alone, showed that Linux does not support it.</P> > <P> </P> > <P>The Tiger Jet, I'm told, is an ISDN device, installed in preparation for asterisk (Phone PBX). Am I properly understanding that Intel has a Linux driver? It looks like driver updates are no longer being made.</P> > <P> </P> > <P>Thank you!</P> > <P> </P> > <P>Tom D.<BR>Denver</P> > <P> </P> > <P>------------------------</P> > <P> </P><FONT size=2> > <P>Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,</P> > <P>as HTML can contain viruses. Use as the email Subject Line:</P> > <P>YourName, YourCountry Fedora Core release 5 (Bordeaux)</P> > <P>Kernel kernel 2.6.15-1.2054_FC5 </P> > <P>With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.</P> > <P>YourCountry will enable Country specific guidance. Linux experts in YourCountry </P> > <P>can be found through: http://www.linux.org/groups/index.html.</P> > <P>They will know your Country's modem code, which may be essential for dialup service.</P> > <P>Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet Provider mail filters.</P> > <P>So in a day, also check the Archived responses at http://www.linmodems.org </P> > <P>-------------------------- System information ----------------------------</P> > <P>CPU=i686, Fedora Core release 5 (Bordeaux)</P> > <P>Kernel </P> > <P>Linux version 2.6.15-1.2054_FC5 (bhcompile@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 Tue Mar 14 15:48:33 EST 2006</P> > <P>scanModem update of: 2008_07_12</P> > <P>There are no blacklisted modem drivers in /etc/modprobe* files </P> > <P>Checking /proc/bus/usb/devices</P> > <P>USB modem not detected among /proc/bus/usb/devices.</P> > <P>For candidate card in slot 02:0c.0, firmware information and bootup diagnostics are:</P> > <P>PCI slot PCI ID SubsystemID Name</P> > <P>---------- --------- --------- --------------</P> > <P>02:0c.0 125d:2838 125d:2838 Communication controller: ESS Technology ES2838/2839 SuperLink Modem </P> > <P>Modem interrupt assignment and sharing: </P> > <P>9: 1 XT-PIC acpi, Intel 82801BA-ICH2</P> > <P>--- Bootup diagnostics for card in PCI slot 02:0c.0 ----</P> > <P>For candidate card in slot 02:0d.0, firmware information and bootup diagnostics are:</P> > <P>PCI slot PCI ID SubsystemID Name</P> > <P>---------- --------- --------- --------------</P> > <P>02:0d.0 e159:0001 8086:0003 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface</P> > <P>Modem interrupt assignment and sharing: </P> > <P>11: 4362 XT-PIC eth0</P> > <P>--- Bootup diagnostics for card in PCI slot 02:0d.0 ----</P> > <P>=== Finished firmware and bootup diagnostics, next deducing cogent software. ===</P> > <P>Predictive diagnostics for card in bus 02:0c.0:</P> > <P>Modem chipset detected on</P> > <P>NAME="Communication controller: ESS Technology ES2838/2839 SuperLink Modem "</P> > <P>CLASS=0780</P> > <P>PCIDEV=125d:2838</P> > <P>SUBSYS=125d:2838</P> > <P>IRQ=9</P> > <P>IDENT=ESS.com</P> > <P>For candidate modem in: 02:0c.0</P> > <P>0780 Communication controller: ESS Technology ES2838/2839 SuperLink Modem </P> > <P>Primary device ID: 125d:2838</P> > <P>Support type needed or chipset: ESS.com</P> > <P></P> > <P>----------------end Softmodem section --------------</P> > <P>Vendor e159 is Tiger Jet , http://www.tjnet.com/</P> > <P>Controller e159:0001 translates PCI commands to the serial link used by</P> > <P>the silabs DAA from the si3034, si3044 and si3056 family.</P> > <P>The e159:0001 with SubSystem 8086:0003 is TJ320 v2.0 </P> > <P>is the first and still most common of the Intel537 modem family.</P> > <P>However primary controller chip can have broader uses: http://www.tjnet.com/chips/tiger320.htm</P> > <P>Though having its own driver package under 2.4.n. kernels,</P> > <P>support (if any) from Intel is now included within the Intel-537EP package.</P> > <P>====== end Tigerjet section =======</P> > <P>For Ubuntu Linux users with Intel 536 and 537 chipsets the are driver </P> > <P>installation packages available.</P> > <P>But since 2006, Intel appears to have ceased updates for Linux.</P> > <P>For the INTEL537 and INTEL536 chipset modems, the most current support is provided at:</P> > <P>http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/</P> > <P></P> > <P>But regular support is not available, see: http://archives.linmodems.org/24939</P> > <P>:</P> > <P>The outdated official Intel support packages can be accessed through:</P> > <P>http://developer.intel.com/design/modems/support/drivers.htm</P> > <P>Read DOCs/Intel.txt and Modem/DOCs/YourSystem.txt for follow through guidance.</P> > <P> </P> > <P>Writing DOCs/Intel.txt</P> > <P> </P> > <P>Predictive diagnostics for card in bus 02:0d.0:</P> > <P>Modem chipset detected on</P> > <P>NAME="Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface"</P> > <P>CLASS=0780</P> > <P>PCIDEV=e159:0001</P> > <P>SUBSYS=8086:0003</P> > <P>IRQ=11</P> > <P>IDENT=INTEL537</P> > <P>For candidate modem in: 02:0d.0</P> > <P>0780 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface</P> > <P>Primary device ID: e159:0001</P> > <P>Support type needed or chipset: INTEL537</P> > <P></P> > <P>----------------end Softmodem section --------------</P> > <P>Completed candidate modem analyses.</P> > <P>The base of the UDEV device file system is: /dev/.udev</P> > <P>The kernel was compiled with gcc version 4.1.0 and a compiler is not installed</P> > <P>linux-headers-2.6.15-1.2054_FC5 resources needed for compiling are not manifestly ready!</P> > <P>If compiling is necessary packages must be installed, providing:</P> > <P>gcc-4.1 kernel-source-2.6.15-1.2054_FC5</P> > <P> </P> > <P>If a driver compilation fails, with message including some lack of some FileName.h (stdio.h for example), then</P> > <P>Some additional kernel-header files need installation to /usr/include. The minimal additional packages are libc6-dev</P> > <P>and any of its dependents, under Ubuntu linux-libc-dev</P> > <P>If an alternate ethernet connection is available,</P> > <P>$ apt-get update</P> > <P>$ apt-get -s install linux-kernel-devel</P> > <P>will install needed packages.</P> > <P>For Debian/Ubuntu related distributions, run the following command to display the needed package list:</P> > <P>Otherwise packages have to be found through http://packages.ubuntu.com</P> > <P>Once downloaded and transferred into a Linux partition,</P> > <P>they can be installed alltogether with:</P> > <P>$ sudo dpkg -i *.deb</P> > <P> </P> > <P>Checking pppd properties:</P> > <P>-r-xr-xr-x 1 root root 308292 Feb 12 2006 /usr/sbin/pppd</P> > <P>In case of an "error 17" "serial loopback" problem, see:</P> > <P>http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html</P> > <P>To enable dialout without Root permission do:</P> > <P>$ su - root (not for Ubuntu)</P> > <P>chmod a+x /usr/sbin/pppd</P> > <P>or under Ubuntu related Linuxes</P> > <P>chmod a+x /usr/sbin/pppd</P> > <P>Checking settings of: /etc/ppp/options</P> > <P>lock</P> > <P>In case of a message like:</P> > <P>Warning: Could not modify /etc/ppp/pap-secrets: Permission denied</P> > <P>see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html</P> > <P>Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1</P> > <P>Which can interfere with Browser naviagation.</P> > <P>Don't worry about the following, it is for experts should trouble shooting be necessary.</P> > <P>==========================================================</P> > <P>Checking for modem support lines:</P> > <P>--------------------------------------</P> > <P>/device/modem symbolic link: </P> > <P>slmodemd created symbolic link /dev/ttySL0: </P> > <P>Within /etc/udev/ files:</P> > <P>/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp", MODE="0660"</P> > <P>Within /etc/modprobe.conf files:</P> > <P>Within any ancient /etc/devfs files:</P> > <P>Within ancient kernel 2.4.n /etc/module.conf files:</P> > <P>--------- end modem support lines --------</P> > <P> </P></FONT>
