Janberk, With/proc/asound/pcm:00-01: Conexant Digital : Conexant Digital : playback 100-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1----Subsystem PCI_id 1734:10adall but certainly has a Conexant softmodem chip. There is a diagnostic tool at www.linuxant.com , which will run aproprietary test that scanModem cannot But I expect the modem will be detected now through the installedhsf* drivers, if you run:$ sudo wvdialconf /etc/wvdial.conf If so put i your dialout info with$ sudo gedit /etc/wvdial.conf and dialout with$ sudo wvdial MarvSscanModem maintainer On Nov 28, 2007 7:15 AM, Janberk Sahin <janberks@xxxxxxxxx> wrote:> Jacques,>> Thank you for your quick answer.>> I got the latest of scanModem, but the output is the same as previous.>> Unfortunately I don't have Windows on the machine. I totally gave it> up for Ubuntu few months ago. And unfortunately again, I am not> experienced at all, I even don't know the odd word "kernel"s meaning.>> You said I should try the two solutions. In that part of the> ModemData.txt, ıt says read Conexant.txt and Smartlink.txt. I did. In> Connexant.txt, it said for 14f1:2f00 chip set a driver was available.> I installed that one ignoring the notifications regarding the "kernel"> consistency. And it didnt work as expected.>> I really didnt get what you meant by saying "try the solutions".> Should I install and try all drivers I can find for Conexant and> Smartlink? If so, I would be happy if you could direct me to a> starting point.>> The workers of the firm giving ADSL service here in Turkey has gone to> a strike, so I can't get ADSL right now. This is why I am so desperate> on this subject. Therefore, any help is appreciated too much.>> Thanks & Regards,> Janberk>>> On Nov 28, 2007 11:44 AM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote:> > Janberk,> >> > First of all, the version of scanModem which you used is obsolete.> > Please always take the last from http://linmodems.technion.ac.il/packages> >> > Second, you would get the chip Id if the modem was an independent PCI> > unit, but recent systems use the HDA sound system to support the modem.> > The only way to identify the modem part of the chipset is by detecting> > the codecs of the modem.> > Your ModemData.txt does not show it, perhaps because it could not find> > it, perhaps because you have used an interim incomplete scanModem.> >> > Finally, since you look experienced, read ModemData.txt again, below> > "Support type needed or chipset:" and try the two suggestions.> > Also, if you have Windows in the same computer, querying ATI for I=1 to> > 10 while using a hyperterminal to talk to the modem will show something> > for the driver such as Conexant or SmartLink or else, saving you trying> > the wrong one(s).> >> > Jacques> >> >> > Janberk Sahin wrote:> > > Hi,> > >> > > I used to think I was capable of handling the difficulties I face in> > > Linux, until I tried to get my modem work in Ubuntu Gutsy.> > >> > > Here I present you the ScanModem output of my laptop (fujitsu-siemens,> > > amilio pro with Intel duo processor) and give my best appreciations> > > for any help about what I should do. I couldn't work out even the> > > chipset of the device from the ModemData.txt :(((.> > >> > > Thanks,> > > Janberk> > >> > > -------------------------- System information ----------------------------> > > CPU=i686,> > > Linux version 2.6.22-14-generic (buildd@palmer) (gcc version 4.1.3> > > 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14> > > 23:05:12 GMT 2007> > > scanModem update of: 20071030> > > The modem symbolic link is /dev/modem -> ttySHSF0> > >> > > There are no blacklisted modem drivers in /etc/modprobe* files> > >> > > Potentially useful modem drivers now loaded are:> > > hsfusbcd2> > > hsfmc97sis> > > hsfmc97ati> > > hsfmc97ali> > > hsfmc97via> > > hsfmc97ich> > > hsfpcibasic2> > > hsfserial> > > hsfengine> > > hsfosspec> > > hsfsoar> > >> > >> > > The Advanced Linux Sound Architecture (ALSA) packages providing audio> > > support on your System,> > > also includes drivers for some modems. Diagnostics are under the> > > /proc/asound/ folders.> > >> > > For modems using the snd-hda-intel audio+modem driver, upgrades to> > > a new ALSA version are sometimes necessary to achieve function.> > > See for example:> > > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg02144.html.> > > Audio cards with the ALC883 chipset may require an upgrade to ALSA> > > version 1.0.15 for modem support, see> > > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg02577.html> > >> > > Copying ALSA diagnostics to Modem/ALSAjanberk.tgz> > > ALSAversion = 1.0.14> > >> > > Summary card and chipset information is in:> > > /proc/asound/cards:> > > 0 [Intel ]: HDA-Intel - HDA Intel> > > HDA Intel at 0xdc240000 irq 23> > >> > > /proc/asound/pcm:> > > 00-01: Conexant Digital : Conexant Digital : playback 1> > > 00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1> > >> > > USB modem not detected by lsusb> > >> > > For candidate card, firmware information and bootup diagnostics are:> > >> > > PCI slot PCI ID SubsystemID Name> > > ---------- --------- --------- --------------> > > 00:1b.0 8086:27d8 1734:10ad Audio device: Intel Corporation 82801G> > >> > > Modem interrupt assignment and sharing:> > > 23: 609436 0 IO-APIC-fasteoi HDA Intel> > > --- Bootup diagnostics for card in PCI slot 00:1b.0 ----> > > [ 16.872000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level,> > > low) -> IRQ 23> > > [ 16.872000] PCI: Setting latency timer of device 0000:00:1b.0 to 64> > >> > > === Finished modem firmware and bootup diagnostics section. ===> > > === Next deducing cogent software ===> > >> > > The High Defintion Audio card with PCI ID 8086:27d8 may host a soft> > > modem chip.> > > Bootup diagnostics lack ALSA data.> > >> > > Modem not detected though HDA card diagnostics, though not excluding> > > a possible Conexant modem chip impervious to ALSA diagnostics.> > > Proceeding through alternative possibilties.> > >> > >> > > There is candidate modem software.> > >> > > For candidate modem in PCI bus: 00:1b.0> > > Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G> > > Primary PCI_id 8086:27d8> > > Subsystem PCI_id 1734:10ad> > > Softmodem codec or chipset from diagnostics:> > > from Archives:> > >> > >> > > Lacking a dsp (digital signal processing) chip, the modem is a software> > > intensive or "softmodem" type. Its primary controller manages the traffic> > > with the CPU. But the software needed is specified in the Subsystem.> > > -----------------------------> > > ------------> > > Support type needed or chipset:> > >> > > Support can likely be achieved through two mutually exclusive alternatives:> > > 1) The hsfmodem software for Conexant chipset modems: Read Conexant.txt> > > The following ALSA alternative CANNOT work with Conexant modems.> > >> > > 2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for details, and> > > to test get the package SLMODEMD.gcc4.1.tar.gz from:> > > http://linmodems.technion.ac.il/packages/smartlink/> > >> > > Already loaded into the kernel is snd-hda-intel and audio drivers it> > > depends on,> > > displayed by: lsmod | grep snd_hda_intel> > > Module Size Used by> > > -------------------------------------> > > snd_hda_intel 263712 5> > > snd_pcm 80388 3 snd_hda_intel,snd_pcm_oss> > > snd 54660 17> > > snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device> > > snd_page_alloc 11400 2 snd_hda_intel,snd_pcm> > >> > >> > > Writing Intel.txt> > >> > > For owners of a Dell PCs with Conexant HSF modems, a driver source> > > package with full speed enabled is available, but requires driver> > > compiling. Read Conexant.txt> > >> > > Read Conexant.txt> > >> > > Writing Conexant.txt> > >> > > Writing Smartlink.txt> > > ============ end Smartlink section =====================> > >> > >> > > The base of the UDEV device file system is: /dev/.udev> > >> > > Versions adequately match for the compiler installed: 4.1.3> > > and the compiler used in kernel assembly: 4.1.3> > >> > >> > >> > > Minimal compiling resources appear complete:> > > make utility - /usr/bin/make> > > Compiler version 4.1> > > linuc_headers base folder /lib/modules/2.6.22-14-generic/build> > >> > > However some compilations and executable functions may need additional files,> > > in the FileNames.h (so called kernel "h"eaders) collection installed> > > in /usr/include/ .> > > For martian_modem, additional required packages are libc6-dev (and> > > for Debian/Ubuntu, linux-libc-dev). The also required headers of> > > package libc6 are commonly installed by default.> > >> > >> > >> > > 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 269256 2007-10-04 22:57 /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> > >> > > Read Modem/YourSystem.txt concerning other COMM channels: eth0 eth1> > > Which can interfere with Browser naviagation.> > >> > > 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: lrwxrwxrwx 1 root root 8> > > 2007-11-19 10:45 /dev/modem -> ttySHSF0> > > slmodemd created symbolic link /dev/ttySL0:> > > Within /etc/udev/ files:> > > /etc/udev/rules.d/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"> > > Within /etc/modprobe.conf files:> > > /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> > > /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/hsf:alias /dev/modem /dev/ttySHSF> > > /etc/modprobe.d/hsf.conflicts:install snd-via82xx-modem /bin/true #> > > temporarily disabled by hsf - conflicts with hsfmc97via> > > /etc/modprobe.d/hsf.conflicts:install snd-atiixp-modem /bin/true #> > > temporarily disabled by hsf - conflicts with hsfmc97ati> > > Within any ancient /etc/devfs files:> > > /etc/devfs/conf.d/hsf.conf:LOOKUP ^(ttySHSF[0-9]|modem$) EXECUTE> > > nice /sbin/modprobe /dev/ttySHSF> > > /etc/devfs/conf.d/hsf.conf:REGISTER ^ttySHSF0$ CFUNCTION GLOBAL> > > symlink $devname modem> > > /etc/devfs/conf.d/hsf.conf:UNREGISTER ^ttySHSF0$ CFUNCTION GLOBAL> > > unlink modem> > > Within ancient kernel 2.4.n /etc/module.conf files:> > >> > > --------- end modem support lines --------> >>>>> --> Janberk Şahin> Enerji Ticaret Uzmanı> Kapasitif Danışmanlık>
