Jon, Tomorrow I will send you a compiled driver package. MarvS On 8/7/07, Jonathan Walford <subtlesabotage@xxxxxxxxxxx> wrote: > Thank you very much in advance for the advice you can give me on my problem. > I'm very new to Linux and I appreciate all the help I can get! > > Here's the text from ModemData.txt: > > Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List > Server. > Do use the following as the email Subject Line: > SomeName, YourCountry Ubuntu 6.10 kernel 2.6.17-10-generic > This will alert cogent experts, and distinguish cases in the Archives. > YourCountry will enable Country Code guidance. > Occassionally responses are blocked by an Internet Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org . > Local Linux experts can be found through: > http://www.linux.org/groups/index.html > -------------------------- System information ---------------------------- > CPU=i686, Ubuntu 6.10 > Linux version 2.6.17-10-generic (root@vernadsky) (gcc version 4.1.2 20060928 > (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Fri Oct 13 18:45:35 UTC 2006 > (Ubuntu 2.6.17-10.33-generic) > scanModem update of: 2007_August_04 > > > ALSAversion 1.0.11 > USB modem not detected by lsusb > > Modem or host audio card candidates have firmware information: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:10.0 125d:2898 Communication controller: ESS Technology ES2898 Modem > > Modem interrupt assignment and sharing: > > --- Bootup diagnostics for card in PCI slot 00:10.0 ---- > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > =================================== > The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not functional!! > The CPU cannot control the modem until this situation is corrected!! > Possible corrections are: > 1) Within the boot up BIOS, change from a Windows to a non-PNP/Other > Operating System type. > Instructions for accessing BIOS are at: > http://linmodems.technion.ac.il/resources.html within: Additional > Resourcces. > 2a) Add an option "pci=routeirq" to the kernel boot up line. > Here is an example paragraph from /boot/grub/menu.lst : > title Ubuntu, kernel 2.6.15-26-686 > root (hd0,6) > kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq > initrd /boot/initrd.img-2.6.15-26-686 > savedefault > 2b) Same as above, but use "pollirq" instead of "pci=routeirq". > 3) Within some BIOS setups, IRQ assignments can be changed. > 4) On non-laptop systems, moving the modem card to another slot has > helped. > 5) Sometimes upgrading the kernel changes IRQ assignment. > ===================================== > > PCIbus=00:10.0 > 00:10.0 Communication controller: ESS Technology ES2898 Modem (rev 02) > Flags: fast devsel, IRQ 255 > I/O ports at a000 [disabled] [size=8] > Capabilities: <access denied> > > > For candidate modem in PCI bus: 00:10.0 > Class 0780: 125d:2898 Communication controller: ESS Technology ES2898 > Modem > Primary PCI_id 125d:2898 > Support type needed or chipset: ESS.com > > > > Vendor=125d is ESS Technologies, http://www.esstech.com/ > The PCI id 125d:2898 modems are Supported under 2.6.n kernels. > > The driver resources for 125d:2898 modems should be downloaded > from http://tx.technion.ac.il/~raindel/ess_2.6-v0.3.tar.gz , benefitting > from an update by Jeff Trull. There are brief instructions at > http://ubuntuforums.org/showthread.php?t=185079 > Under Linux, unpack with: > $ tar zxf ess_2.6-v0.3.tar.gz > Move into the folder wit: > $ cd ess_2.6-v0.3 > Browse the files therein and run as Root the: > $ sudo ./setup > > The setup program creates a port: > $ ls -l /dev/ttyS_ESS0 > crw-rw-rw- 1 root root 62, 64 2006-09-23 23:08 /dev/ttyS_ESS0 > and a symbolic link to it: > /dev/modem --> /dev/ttyS_ESS0 > Specify either /dev/modem or /dev/ttyS_ESS0 as the modem port for dialer > utilities. > A file is installed: > /etc/udev/rules.d/ess.rules , with line: > "KERNEL=\"ttyS_ESS0\", SYMLINK=\"modem\"" > which supports automated port creation during driver loading. > > If the drivers do not autoload during bootup, they can be loaded by: > $ sudo modprobe esscom > after which the driver interdependencies can be displayed by: > $ lsmod | grep esscom > esscom 16580 0 > esscom_hw 421328 1 esscom > linmodems 345678 2 esscom esscom_hw > > The modem should be found by: > $ sudo wvdialconf wvtest > See wvdial.txt and Testing.txt for follow through details. > =============== > For 2.4.n Linux kernels and are there some kludges of fading utility: > http://linmodems.technion.ac.il/archive-fourth/msg00317.html > (2004Feb08) > http://andrew.cait.org/ess/ > http://sidlo.penguin.cz/ES2838/index_en.html > http://tx.technion.ac.il/~raindel/ > http://phep2.technion.ac.il/linmodems/archive/msg04424.html > > There was only formal support under for Linux for kernels 2.2.2. > ====== end ESS.com section ======= > > > 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.17-10-generic > > > If a driver compilation files with message including some lack of some > FileName.h (stdio.h for example. > Some additional kernel-header files need installation to /usr/include. > For Debian/Ubuntu related distributions, run the following command to > display the needed package list: > $ sudo apt-get -s install linux-kernel-devel > While some of the files may be on the install CD, others may have to be > found through http://packages.ubuntu.com > > For Ubunut feisty, additional packages required were: > build-essential curl debhelper dpkg-dev g++ g++-4.1 gettext git-core gitk > html2text intltool-debian kernel-package kernel-wedge libc6-dev > libcurl3-gnutls libdigest-sha1-perl liberror-perl libstdc++6-4.1-dev > linux-libc-dev po-debconf rcs tcl8.4 tk8.4 > > > Checking pppd properties: > -rwsr-xr-- 1 root dip 260920 2006-07-10 12:13 /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 > auth > 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: > /etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink > /etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", SYMLINK+="modem" > 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 -------- > > Jonathan Walford > > _________________________________________________________________ > Get Cultured With Arts & Culture Festivals On Live Maps > http://local.live.com/?mkt=en-ca&v=2&cid=A6D6BDB4586E357F!2010&encType=1&style=h&FORM=SERNEP > >
