Marvin, I did all the tests using the root user. I don't like to use the sudo command, so the first thing I do after opening the terminal is "sudo /bin/bash". I have also done the compilation of the driver (setup script) using superuser permissions. Thanks, Antonio. --- El mar 27-oct-09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> escribió: > De: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> > Asunto: Re: Antonio Robirosa, Argentina, kernel 2.6.28-16-generic > Para: estante23-sitio@xxxxxxxxxxxx > Cc: discuss@xxxxxxxxxxxxx > Fecha: martes, 27 de octubre de 2009, 11:00 pm > Please double check that you run > wvdialconf with root permissions: > $ sudo wvdialconf > or > $ sudo su root > # wvdialconf > > MarvS > scanModem maintainer > > On Tue, Oct 27, 2009 at 6:35 PM, <estante23-sitio@xxxxxxxxxxxx> > wrote: > > Marvin and Antonio, > > > > Thanks for your quick reply. Following your advise I > read Bootup.txt and I did these tests: > > > > - I went to the BIOS and look for a setting saying > something similar to "non-PNP/Other Operating System" but I > couldn't find anything. > > - I added "pci=routeirq" and "pollirq" (one at the > time) to the kernel boot up line. > > - I went to the BIOS and turned off the onboard > features one at the time (LAN, Audio, IDE Ports, Floppy, > Serial ports, paralel ports) > > - I put the modem in another PCI slot and repeat the > last three tests. > > - I downloaded the script "unloading.gz" and run it. > It unload most of the modules, including the mouse driver. I > load the 3 modules of the modem and I tried with wvdial to > dial out. > > > > In every case, wvdial says there is no response from > the modem. > > > > - I also read the Pctel.txt and issue the modprob and > lsmod commands: > > > > root@athlon-areco:~# depmod -a > > root@athlon-areco:~# modprobe pctel > > root@athlon-areco:~# lsmod | grep pct > > pctel 19972 0 > > pctel_hw 1119332 1 pctel > > linmodem 39072 1 pctel > > root@athlon-areco:~# ls -l /dev/ttyS_* > > crw-rw---- 1 root dialout 62, 64 2009-10-27 18:26 > /dev/ttyS_PCTEL0 > > root@athlon-areco:~# wvdialconf > > Editing `/etc/wvdial.conf'. > > > > Scanning your serial ports for a modem. > > > > Modem Port Scan<*1>: Scanning ttyS_PCTEL0 first, > /dev/modem is a link to it. > > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- failed with 2400 > baud, next try: 9600 baud > > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- failed with 9600 > baud, next try: 115200 baud > > ttyS_PCTEL0<*1>: ATQ0 V1 E1 -- and failed too at > 115200, giving up. > > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, > next try: 9600 baud > > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, > next try: 115200 baud > > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at > 115200, giving up. > > Modem Port Scan<*1>: S1 S2 S3 > > > > > > Sorry, no modem was detected! Is it in use by > another program? > > Did you configure it properly with setserial? > > > > > > > > After changing PCI slot of the modem, modemData.txt > contains: > > > > Modem interrupt assignment and sharing: > > 19: 0 15 > IO-APIC-fasteoi > > --- Bootup diagnostics for card in PCI slot 01:08.0 > ---- > > [ 0.912879] pci 0000:01:08.0: reg 10 io port: > [0xec00-0xec3f] > > [ 0.912919] pci 0000:01:08.0: supports D2 > > [ 0.912924] pci 0000:01:08.0: PME# supported from > D0 D2 D3hot > > [ 0.912930] pci 0000:01:08.0: PME# disabled > > [ 10.924429] pctel_hw 0000:01:08.0: PCI INT A -> > Link[LNKA] -> GSI 19 (level, low) -> IRQ 19 > > [ 10.924434] pctel_pci(233): PCTel > device[0000:01:08.0](0x40) found 134d:7890 (rev 01), > iobase=0xec00, irq=19. > > > > At the end of this email, I have included the updated > ModemData.txt file. > > > > I have check dsmesg and I don't see any other module > using IRQ 19. But I would like to be sure. > > > > I would like to ask you if there is anything I could > do to try to find out why the modem is not responding. > Although I don't have much experience with C, I'm a Java > programmer and this machine is brand new, so I could do some > risky tests, if that is required. I would like to keep using > Ubuntu on this machine. > > > > Thanks, > > > > Antonio. > > > > Modem.txt file (2009-10-27) > > --------------------------- > > 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.28-16-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.28-16-generic (buildd@vernadsky) > (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #55-Ubuntu SMP > Tue Oct 20 19:48:24 UTC 2009 > > scanModem update of: 2009_09_15 > > The modem symbolic link is /dev/modem -> > ttyS_PCTEL0 > > > > The dkms driver upgrade utilities are installed, > > > > 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 0458:002e KYE Systems Corp. (Mouse Systems) > > If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html > > A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.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 01:08.0, firmware > information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID > Name > > ---------- --------- --------- > -------------- > > 01:08.0 134d:7890 134d:0001 > Communication controller: PCTel Inc HSP MicroModem 56 > > > > Modem interrupt assignment and sharing: > > 19: 0 15 > IO-APIC-fasteoi > > --- Bootup diagnostics for card in PCI slot 01:08.0 > ---- > > [ 0.912879] pci 0000:01:08.0: reg 10 io port: > [0xec00-0xec3f] > > [ 0.912919] pci 0000:01:08.0: supports D2 > > [ 0.912924] pci 0000:01:08.0: PME# supported from > D0 D2 D3hot > > [ 0.912930] pci 0000:01:08.0: PME# disabled > > [ 10.924429] pctel_hw 0000:01:08.0: PCI INT A -> > Link[LNKA] -> GSI 19 (level, low) -> IRQ 19 > > [ 10.924434] pctel_pci(233): PCTel > device[0000:01:08.0](0x40) found 134d:7890 (rev 01), > iobase=0xec00, irq=19. > > > > The PCI slot 01:08.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. > > > > > > For candidate card in slot 00:05.0, firmware > information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID > Name > > ---------- --------- --------- > -------------- > > 00:05.0 10de:03f0 1849:3662 > Audio device: nVidia Corporation MCP61 High Definition > Audio > > > > Modem interrupt assignment and sharing: > > 21: 12 1681 IO-APIC-fasteoi > ehci_hcd:usb1, HDA Intel > > --- Bootup diagnostics for card in PCI slot 00:05.0 > ---- > > [ 0.912081] pci 0000:00:05.0: reg 10 32bit mmio: > [0xfbff8000-0xfbffbfff] > > [ 0.912111] pci 0000:00:05.0: PME# supported from > D3hot D3cold > > [ 0.912117] pci 0000:00:05.0: PME# disabled > > [ 2.464020] pci 0000:00:05.0: Enabling HT MSI > Mapping > > [ 11.021305] HDA Intel 0000:00:05.0: PCI INT B > -> Link[LAZA] -> GSI 21 (level, low) -> IRQ 21 > > [ 11.021364] HDA Intel 0000:00:05.0: setting > latency timer to 64 > > > > The PCI slot 00:05.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.18 > > The modem cards detected by "aplay -l" are: None > > > > > > The /proc/asound/pcm file reports: > > ----------------------- > > 00-00: ALC662 Analog : ALC662 Analog : playback 1 : > capture 1 > > 00-01: ALC662 Digital : ALC662 Digital : playback 1 : > capture 1 > > > > about /proc/asound/cards: > > ------------------------ > > 0 [NVidia ]: HDA-Intel - HDA NVidia > > HDA NVidia at > 0xfbff8000 irq 21 > > > > PCI slot 00:05.0 has a High Definition Audio Card > > The drivers are in the kernel modules tree at: > > > /lib/modules/2.6.28-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko > > > /lib/modules/2.6.28-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko > > UNEXPECTED HDA diagnostic outcome. > > === Finished firmware and bootup diagnostics, next > deducing cogent software. === > > > > Predictive diagnostics for card in bus 01:08.0: > > Modem chipset detected on > > NAME="Communication controller: PCTel Inc HSP > MicroModem 56 " > > CLASS=0780 > > PCIDEV=134d:7890 > > SUBSYS=134d:0001 > > IRQ=19 > > IDENT=PCTEL > > > > For candidate modem in: 01:08.0 > > 0780 Communication controller: PCTel Inc HSP > MicroModem 56 > > Primary device ID: 134d:7890 > > Support type needed or chipset: PCTEL > > > > > > At http://linmodems.technion.ac.il/pctel-linux > > Get the pctel-0.9.7-9-rht-10.tar.gz > > Unpack under Linux with: > > tar zxf pctel*.tar.gz > > and read instuctions therein. > > Read DOCs/Pctel.txt and Modem/DOCs/YourSystem.txt > for follow through guidance. > > > > Writing DOCs/Pctel.txt > > > > > > Predictive diagnostics for card in bus 00:05.0: > > Modem chipset not detected on > > NAME="Audio device: nVidia Corporation MCP61 High > Definition Audio " > > CLASS=0403 > > PCIDEV=10de:03f0 > > SUBSYS=1849:3662 > > IRQ=21 > > HDA=10de:03f0 > > SOFT=10de:03f0.HDA > > > > > > High Definition Audio (HDA) cards MAY host a modem > chip in their Subsystem, > > and many are supported by the ALSA audio+modem > driver snd-hda-intel > > A modem was not detected on HDA card 10de:03f0. > > If another modem card is present, then most likely > 10de:03f0 does not host a modem. > > If another modem card has not been detected, then > possibilities are: > > 1) A Conexant modem chip is present on > 10de:03f0, as Conexant chips > > are frequently not detectable by ALSA diagnostics > > 2) The modem may be of the older non-PCI > Controller Chipset (hardware) type. > > Try detection with Root permission: > > sudo wvdialconf /etc/wvdial.conf > > > > For candidate modem in: 00:05.0 > > 0403 Audio device: nVidia Corporation MCP61 High > Definition Audio > > Primary device ID: 10de:03f0 > > Subsystem PCI_id 1849:3662 > > Softmodem codec or chipset from diagnostics: > > from > Archives: > > > > > > > > Support type needed or chipset: > > > > Support can likely be achieved through two mutually > exclusive alternatives: > > 1) The hsfmodem software for Conexant chipset modems: > Read DOCs/Conexant.txt > > The following ALSA alternative CANNOT work with > Conexant modems. > > > > 2) An ALSA modem driver plus slmodemd. Read > DOCs/Smartlink.txt for details, and > > to test get the package SLMODEMD.gcc4.3.tar.gz from: > > http://linmodems.technion.ac.il/packages/smartlink/ > > > > Writing DOCs/Smartlink.txt > > ============ end Smartlink section > ===================== > > > > Completed candidate modem analyses. > > > > The base of the UDEV device file system is: > /dev/.udev > > > > Versions adequately match for the compiler > installed: 4.3.3 > > and the compiler used in kernel > assembly: 4.3.3 > > > > > > > > Minimal compiling resources appear complete: > > make utility - /usr/bin/make > > Compiler version 4.3 > > linuc_headers base folder > /lib/modules/2.6.28-16-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. > > > > > > Compressed files at: > /usr/src/linux-source-2.6.28.tar.bz2 > > > > > > 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 277352 2009-02-20 > 15:25 /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 > > 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: lrwxrwxrwx 1 > root root 11 2009-10-27 18:26 /dev/modem -> ttyS_PCTEL0 > > slmodemd created symbolic link /dev/ttySL0: > > Within /etc/udev/ files: > > > /etc/udev/rules.d/70-pctel.rules:KERNEL=="ttyS_PCTEL0", > SYMLINK="modem" > > Within /etc/modprobe.conf files: > > /etc/modprobe.d/blacklist-modem.conf:# Uncomment these > entries in order to blacklist unwanted modem drivers > > /etc/modprobe.d/blacklist-modem.conf:# blacklist > snd-atiixp-modem > > /etc/modprobe.d/blacklist-modem.conf:# blacklist > snd-via82xx-modem > > /etc/modprobe.d/alsa-base.conf:options > snd-atiixp-modem index=-2 > > /etc/modprobe.d/alsa-base.conf:options > snd-via82xx-modem index=-2 > > Within any ancient /etc/devfs files: > > > > Within ancient kernel 2.4.n /etc/module.conf > files: > > /etc/modules:linmodem > > /etc/modules~:linmodem > > --------- end modem support lines -------- > > > > > > > > Yahoo! Cocina > > > > Encontra las mejores recetas con Yahoo! Cocina. > > > > > > http://ar.mujer.yahoo.com/cocina/ > > > Yahoo! Cocina Encontra las mejores recetas con Yahoo! Cocina. http://ar.mujer.yahoo.com/cocina/
