Franz, Please send to the List, not me directly. After rebooting, again run > sudo wvdialconf /etc/wvdial.conf If the modem is not detected, run $ sudo hsfconfig --diagnose will write a file to the /tmp/ folder which should be sent to "Support (Jonathan)" <support@xxxxxxxxxxxx>, the expert on this software MarvS On Thu, Mar 26, 2009 at 11:32 PM, Franz <francesco3@xxxxxxxxxx> wrote: > Dear Marvin > thanks for your help > > I installed the driver you suggested, with no error message, but then, with > sudo wvdialconf /etc/wvdial.conf > > I only get: > > "Scanning your serial ports for a modem. > > Modem Port Scan<*1>: S0 S1 S2 S3 > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial?" > > Any suggestion > > Regards > Francesco > > > > > 2009/3/26 Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> >> >> Pronto: >> >> First try: >> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >> download hsfmodem-7.80.02.02full_k2.6.27_11_generic_ubuntu_i386.deb.zip >> Under Linux unpack with: >> $ unzip hsfmodem*.zip >> Then install with: >> $ sudo dpkg -i hsfmodem*.deb >> Follow any output guidance, about additional software needed. >> >> Subsequently, the modem should be found with >> $ sudo wvdialconf /etc/wvdial.conf >> Edit in your personal information with: >> $ sudo gedit /etc/wvdial.conf >> and try dialing out with: >> $ sudo wvdial. >> See DOCs/Testing.txt for details. >> >> Read DOCs/Conexant.txt >> >> The expert on this software is "Support (Jonathan)" <support@xxxxxxxxxxxx>, >> >> MarvS >> >> On Thu, Mar 26, 2009 at 9:28 AM, PRONTO 0765200012 >> <francesco3@xxxxxxxxxx> wrote: >> > I am new to linux and trying to use efax-gtk on my ubuntu 8.10 machine >> > (a Vaio SZ laptop with internal prebuilt modem), but only got >> > input-output errors. >> > >> > So maybe the fax-modem is not installed, so I run scanModem and >> > enclose the ModemData.txt file. >> > >> > Thanks for any help. >> > >> > I live between Switzerland and Uruguay. Now I am in Montevideo >> > >> > Franz >> > >> > ModemData.txt: >> > >> > 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.27-11-generic >> > With this Subject Line cogent experts will be alerted, and useful >> > case names left in the Archive. >> > YourCountry will enable Country specific guidance. Linux experts in YourCountry >> > can be found through: http://www.linux.org/groups/index.html. >> > They will know your Country's modem code, which may be essential for >> > dialup service. >> > 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.27-11-generic (buildd@rothera) (gcc version 4.3.2 >> > (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Jan 29 19:24:39 UTC 2009 >> > scanModem update of: 2009_03_01 >> > >> > There are no blacklisted modem drivers in /etc/modprobe* files >> > Potentially useful modem drivers now loaded are: >> > snd_hda_intel >> > >> > Attached USB devices are: >> > ID 04e8:326c Samsung Electronics Co., Ltd ML-2010P Mono Laser Printer >> > ID 04d2:9801 Altec Lansing Technologies >> > ID 05ca:1830 Ricoh Co., Ltd Visual Communication Camera VGP-VCC2 >> > ID 054c:0281 Sony Corp. >> > ID 1058:0702 Western Digital Technologies, Inc. Passport External HDD >> > ID 0409:005a NEC Corp. HighSpeed Hub >> > ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader >> > If a cellphone is not detected, see >> > http://ubuntuforums.org/archive/index.php/t-878554.html >> > >> > If a USB modem or cellphone is attached and was not detected, please >> > provide available information in your request to discuss@xxxxxxxxxxxxx >> > >> > For candidate card in slot 00:1b.0, firmware information and bootup >> > diagnostics are: >> > PCI slot PCI ID SubsystemID Name >> > ---------- --------- --------- -------------- >> > 00:1b.0 8086:27d8 104d:81e6 Audio device: Intel Corporation 82801G >> > >> > Modem interrupt assignment and sharing: >> > 21: 3857373 0 IO-APIC-fasteoi ohci1394, HDA Intel >> > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> > [ 0.536489] PCI: 0000:00:1b.0 reg 10 64bit mmio: [f8440000, f8443fff] >> > [ 0.536489] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >> > [ 0.536489] pci 0000:00:1b.0: PME# disabled >> > [ 11.113736] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >> > [ 11.113748] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, >> > low) -> IRQ 21 >> > [ 11.113777] HDA Intel 0000:00:1b.0: setting latency timer to 64 >> > [50051.724066] HDA Intel 0000:00:1b.0: PCI INT A disabled >> > [50051.740127] HDA Intel 0000:00:1b.0: power state changed by ACPI to D3 >> > [50052.042361] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >> > [50052.042421] HDA Intel 0000:00:1b.0: restoring config space at >> > offset 0x3 (was 0x0, writing 0x10) >> > [50052.043042] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >> > [50052.043056] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, >> > low) -> IRQ 21 >> > [50052.043068] HDA Intel 0000:00:1b.0: setting latency timer to 64 >> > >> > The PCI slot 00:1b.0 of the modem card may be disabled early in >> > a bootup process, but then enabled later. If modem drivers load >> > but the modem is not responsive, read DOCs/Bootup.txt about possible fixes. >> > Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >> > if help is needed. >> > >> > >> > >> > ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== >> > The ALSA packages provide audio support and also drivers for some modems. >> > ALSA diagnostics are written during bootup to /proc/asound/ folders. >> > >> > The ALSA verion is 1.0.17 >> > The modem cards detected by "aplay -l" are: None >> > >> > >> > The /proc/asound/pcm file reports: >> > ----------------------- >> > 01-00: USB Audio : USB Audio : playback 1 >> > 00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 1 >> > >> > about /proc/asound/cards: >> > ------------------------ >> > 0 [Intel ]: HDA-Intel - HDA Intel >> > HDA Intel at 0xf8440000 irq 21 >> > 1 [Audio ]: USB-Audio - Altec Lansing XT1 - USB Audio >> > Altec Lansing Technologies, Inc. Altec Lansing >> > XT1 - USB Audio at usb-0000:00:1 >> > >> > PCI slot 00:1b.0 has a High Definition Audio Card >> > The drivers are in the kernel modules tree at: >> > /lib/modules/2.6.27-9- >> > generic/kernel/sound/pci/hda/snd-hda-intel.ko >> > /lib/modules/2.6.27-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> > /lib/modules/2.6.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> > The modem codec file for the HDA card is: /proc/asound/card0/codec#1 >> > -------------------------------------------------------- >> > Codec: Conexant ID 2bfa >> > Address: 1 >> > Vendor Id: 0x14f12bfa >> > Subsystem Id: 0x104d0200 >> > Revision Id: 0x90000 >> > Modem Function Group: 0x2 >> > >> > The audio card hosts a softmodem chip: 0x14f12bfa >> > >> > 14f1 is the Conexant Vendor ID, and 0x14f12bfa a softmodem chipset. >> > Get a hsfmodem package through http://www.linuxant.com >> > >> > If not a Conexant modem, the driver hsfmodem-drivers with its dependent drivers: >> > >> > ---------- >> > provide audio + modem support with the modem chip residing on the subsystem. >> > Any particular card can host any one of several soft modem chips. >> > >> > === Finished firmware and bootup diagnostics, next deducing cogent software. === >> > >> > Predictive diagnostics for card in bus 00:1b.0: >> > Modem chipset detected on >> > NAME="Audio device: Intel Corporation 82801G " >> > CLASS=0403 >> > PCIDEV=8086:27d8 >> > SUBSYS=104d:81e6 >> > IRQ=21 >> > HDA=8086:27d8 >> > SOFT=8086:27d8.HDA >> > CHIP=0x14f12bfa >> > CodecClass=14f1 >> > IDENT=hsfmodem >> > Driver=hsfmodem-drivers >> > >> > For candidate modem in: 00:1b.0 >> > 0403 Audio device: Intel Corporation 82801G >> > Primary device ID: 8086:27d8 >> > Subsystem PCI_id 104d:81e6 >> > Softmodem codec or chipset from diagnostics: 0x14f12bfa >> > from Archives: >> > The HDA card softmodem chip is 0x14f12bfa >> > >> > >> > Support type needed or chipset: hsfmodem >> > >> > >> > Writing DOCs/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 DOCs/Conexant.txt >> > >> > >> > Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the >> > hsfmodem package matching your System. For several Linux distros, there are >> > precompiled drivers matched to specific kernels. These have within the FileName, >> > your KernelVersion: 2.6.27_11_generic >> > They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php >> > A more precise location may be given a few paragraphs below. >> > If an EXACT Match with your your KernelVersion is not found, one of the >> > "Generic packages with source" near the bottom of the page must be used. >> > Downloaded packages must be moved into the Linux partition (home folder is OK) >> > and unzipped with: >> > unzip hsf*.zip >> > The installation command for a .deb suffic packages is, with root/adm >> > permission: >> > sudo dpkg -i hsf*.deb >> > while for .rpm suffix it is, with: >> > rpm -i hsf*.rpm >> > >> > Support for Conexant chips hosted on High Definition Audio cards may require >> > installation of additional packages, one of the alsa-driver-linuxant packages >> > on http://www.linuxant.com/alsa-driver/ At the same time download the >> > alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the >> > hsfmodem install, there will be a message if there is necessary installation of >> > alsa-driver-linuxant >> > >> > The installation command for a .deb suffic packages is, with root/adm >> > permission: >> > sudo alsa* -i hsf*.deb >> > while for .rpm suffix it is, with: >> > rpm -i hsf*.rpm >> > >> > There may a message that "Dependencies" are not satisfied. In this >> > case the Ubuntu/Debian packages to be installed are linux-libc-dev & >> > libc6-dev. Package >> > names may be different for other Linuxes. If not on your install CD, these >> > packages can be searched for at http://packages.ubuntu.com. After download, >> > they can be coinstalled with: >> > sudo dpkg -i li*.deb >> > Again try the alsa-driver-linuxant >> > >> > There may be a message that the patch must be applied. In this case get the >> > ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2 >> > Under Linux, this package is unpacked with: >> > $ tar jxf alsa*.tar.bz2 >> > Next the patch is applied with: >> > $ patch -p0 < alsa-driver-1.0.17-1.patch >> > >> > See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html >> > for details on compiling and installing replacement snd-hda-intel + its >> > dependent drivers. >> > After the installation is completed, rerun the hsfmodem installation. >> > Reboot and try to detect the modem with Root permission: >> > sudo wvdialconf /etc/wvdial.conf >> > >> > From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >> > download hsfmodem-7.80.02.02full_k2.6.27_11_generic_ubuntu_i386.deb.zip >> > Under Linux unpack with: >> > $ unzip hsfmodem*.zip >> > Then install with: >> > $ sudo dpkg -i hsfmodem*.deb >> > Subsequently, the modem should be found with >> > $ sudo wvdialconf /etc/wvdial.conf >> > Edit in your personal information with: >> > $ sudo gedit /etc/wvdial.conf >> > and try dialing out with: >> > $ sudo wvdial. >> > See DOCs/Testing.txt for details. >> > >> > Read DOCs/Conexant.txt >> > >> > Writing DOCs/Conexant.txt >> > >> > >> > Completed candidate modem analyses. >> > >> > The base of the UDEV device file system is: /dev/.udev >> > >> > Versions adequately match for the compiler installed: 4.3.2 >> > and the compiler used in kernel assembly: 4.3.2 >> > >> > The patch utility is needed and is needed for compiling ALSA drivers, >> > and possibly others. >> > >> > >> > Minimal compiling resources appear complete: >> > make utility - /usr/bin/make >> > Compiler version 4.3 >> > linuc_headers base folder /lib/modules/2.6.27-11-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 needed. The also >> > required headers of package libc6 are commonly installed by default. >> > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev >> > packages, for kernels 2.6.24 and later versions. >> > In not included on your install CD, search for them at >> > http://packages.ubuntu.com >> > or comparable Repository for other Linux distros. >> > When compiling ALSA drivers, the utility "patch" will also be needed. >> > >> > >> > >> > >> > 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 packages. >> > 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 277160 2008-11-20 18:58 /usr/sbin/pppd >> > >> > In case of an "error 17" "serial loopback" problem, see: >> > http://linmodems.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/DOCs/YourSystem.txt concerning other COMM channels: eth0 >> > ppp0 vmnet1 vmnet8 vnet0 >> > Which can interfere with Browser naviagation. >> > >> > Don't worry about the following, it is for 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 -------- >> > >
