Gary, Read InforGeneral.txt about the different modem chip types. Least troublesome are the Controller Chipset modems, supported by serial drivers in every Linux Distro. MarvS On Dec 22, 2007 2:50 AM, Gary Pocklington <gary.pocklington@xxxxxxxxxx> wrote: > My modem has not got a supportable chipset from this report. What are the > best options to move forward with this? > > 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.15-26-386 > 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.15-26-386 (buildd@terranova) (gcc version 4.0.3 (Ubuntu > 4.0.3-1ubuntu5)) #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 > scanModem update of: 2007-20-07 > > > There are no blacklisted modem drivers in /etc/modprobe* files > > The Advanced Linux Sound Architecture (ALSA) packages providing audio > support on your System, > also includes drivers for some modems. High Definition Audio (HDA) cards can > themselves host > a softmodem chipset, with both audio+modem supported by a snd-hda-intel > driver. > The ALSA diagnostics are written during bootup to /proc/asound/ folders. > > > Modem not detected though HDA card diagnostics, though not excluding > a possible Conexant modem chip impervious to ALSA diagnostics. > Proceeding through alternative possibilties. > > Summary card and chipset information is in: > /proc/asound/cards: > 0 [rev50 ]: VIA686A - VIA 82C686A/B rev50 > VIA 82C686A/B rev50 with ALC100,100P at 0xdc00, irq 5 > > /proc/asound/pcm: > 00-00: VIA 82C686A/B rev50 : VIA 82C686A/B rev50 : playback 1 : capture 1 > > A copy of /proc/asound had been copied to Modem/ALSAgazzer.tgz > USB modem not detected by lsusb > > For candidate card, firmware information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 0000:00:09.0 1813:4000 Communication controller: Ambient Technologies Inc > HaM controllerless modem > > Modem interrupt assignment and sharing: > --- Bootup diagnostics for card in PCI slot 0000:00:09.0 ---- > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > PCIbus=0000:00:09.0 > 0000:00:09.0 Communication controller: Ambient Technologies Inc HaM > controllerless modem (rev 02) > Flags: medium devsel, IRQ 11 > Memory at de000000 (32-bit, non-prefetchable) [size=4K] > I/O ports at ec00 [size=256] > Capabilities: <available only to root> > > > There is candidate modem software. > > For candidate modem in PCI bus: 0000:00:09.0 > Class 0780: 1813:4000 Communication controller: Ambient Technologies Inc > HaM controllerless modem > Primary PCI_id 1813:4000 > Support type needed or chipset: AmbientTech > Under Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read > InfoGeneral.txt about alternatives. > > > Vendor=1813 Ambient Tech was acquired by Intel with its HaM (Host assisted > Modem) chipsets. > There is no support under 2.6.n kernels!! > Intel-v92ham-453.tgz 2.4.n kernels was the FINAL 2.4.n update for HaM > modems, available at: > http://linmodems.technion.ac.il/packages/Intel/ham/ > http://developer.intel.com/design/modems/support/drivers.htm > It is NOT functional when compiled under 2.6.n kernels. > But under the 2.4.nn kernels, all HaM chipsets were supported, > with a single EXCEPTION: the odd PCI_ID 1813:4100 modems. For the > explanation, see message: > > http://linmodems.org/cgi-bin/ezmlm-cgi?1:mss:9448:200210:fbhcoigfcimgkjdedja > d > ====== end AmbientTech section ======= > > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > The kernel was compiled with gcc version 4.0.3 and a compiler is not > installed > > > If compiling a modem driver proves to be necessary, one of the two > procedures must be followed. > If not yet on the Internet, put the Dapper install CD in the drive > Open a terminal and therein: > $ sudo apt-get install gcc-4.0 make > Additionally the package linux-headers-2.6.15-26-386 must be downloaded. > Go to http://packages.ubuntu.com/ and search for > linux-headers-2.6.15-26-386 > After downloading, it can be installed with: > $ sudo dpkg -i linux-header*.deb > > Or alternatively if online through Ethernet do: > $ sudo apt-get update > $ sudo apt-get install build-essential > will do all the necessary installations mentioned above. > > In either installation case, set a symbolic link which will be expected > later: > $ sudo ln -s /usr/bin/gcc-4.0 /usr/bin/gcc > After check with: > $ ls -l /usr/bin/gcc* > which should display: > lrwxrwxrwx 1 root root 16 2006-07-09 21:53 /usr/bin/gcc -> > /usr/bin/gcc-4.0 > -rwxr-xr-x 1 root root 93584 2006-04-20 18:22 /usr/bin/gcc-4.0 > -rwxr-xr-x 1 root root 16245 2006-04-20 18:13 /usr/bin/gccbug-4.0 > > linux-headers-2.6.15-26-386 resources needed for compiling are not > manifestly ready! > > If compiling is necessary packages must be installed, providing: > gcc-4.0 make linux-headers-2.6.15-26-386 > > > 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 257720 2006-07-05 14:00 /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 -------- > > > >
