On 15 March 2010 12:40, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Nick, > > You have chosen the correct driver. > $ sudo wvdialconf /etc/wvdial.conf > sometimes does not find the modem port. You may try and create a > wvdial.conf file like I instructed Robin to do, but in his case the > modem is not responding. Maybe you can follow scanModem's advice > here: > > For candidate card in slot 01:01.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 01:01.0 11c1:048c 11c1:044c Communication > controller: Agere Systems > V.92 56K WinModem > > Modem interrupt assignment and sharing: > 15: 23507 IO-APIC-edge ata_piix > --- Bootup diagnostics for card in PCI slot 01:01.0 ---- > [ 0.108552] pci 0000:01:01.0: reg 10 32bit mmio: [0xfe5ffc00-0xfe5ffcff] > [ 0.108561] pci 0000:01:01.0: reg 14 io port: [0xbc00-0xbc07] > [ 0.108570] pci 0000:01:01.0: reg 18 io port: [0xb800-0xb8ff] > [ 0.108611] pci 0000:01:01.0: supports D2 > [ 0.108614] pci 0000:01:01.0: PME# supported from D2 D3hot D3cold > [ 0.108619] pci 0000:01:01.0: PME# disabled > > The PCI slot 01:01.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. > > What does output of > $ sudo lsmod | grep 'agrmodem' > and > $ sudo lsmod | grep 'agrserial' > with > $ dmesg | grep 'agr*.' That '.' should be before '*', not after. > and > $ sudo ls /dev/modem -l > and see if it is pointing at > /dev/ttyAGR3 or similar? > > Joshua what would you recommend for Nick to try? Check the modules and symlinks, as you've suggested. If that all checks out, he may have to downgrade to 2.6.29.*, as this code has not been shown to work beyond that. It compiles, but there may be underlying changes to protocols. It's probably time I looked at Nikolay's updates to the other agrsm code and see what I can do with this. > Regards, > > Antonio > > On 3/14/10, Nick <soapduk@xxxxxxxxx> wrote: >> Hi, I'm new to installing dial-up modems on Linux. >> >> I've trying to get a 'Lite-on' d-1156l#/a1a modem working on Xubuntu. >> >> Chipset: Agere Systems V.92 56K WinModem >> >> I've run Scan Modem and by the recommendation of ModemData.txt I have >> downloaded and installed the following file (driver?): >> >> agrsm048pci-2.1.60_20100108_i386.deb. >> >> wvdialconf fails to find a device. It says to use SetSerial so I tried >> the autoconfig but I'm not sure how to use it. >> >> Not sure what to do next. >> >> Thanks for your time. >> >> Nick >> >> 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.31-14-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, Ubuntu , ALSA_version=1.0.20 >> Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 >> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 >> scanModem update of: 2010_02_25 >> >> Distrib_ID=Ubuntu >> DistribCodeName=karmic >> AptRepositoryStem=http://nz.archive.ubuntu.com/ubuntu/ >> >> >> The dkms driver upgrade utilities are installed, >> >> There are no blacklisted modem drivers in /etc/modprobe* files >> >> Potentially useful modem drivers now loaded are: >> >> >> If a USB modem or cellphone is attached and was not detected, please >> provide available information in your request to discuss@xxxxxxxxxxxxx >> >> Candidate PCI devices with modem chips are: >> 01:01.0 Communication controller: Agere Systems V.92 56K WinModem (rev 03) >> High Definition Audio cards can host modem chips. >> >> For candidate card in slot 01:01.0, firmware information and bootup >> diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 01:01.0 11c1:048c 11c1:044c Communication controller: Agere Systems >> V.92 56K WinModem >> >> Modem interrupt assignment and sharing: >> 15: 23507 IO-APIC-edge ata_piix >> --- Bootup diagnostics for card in PCI slot 01:01.0 ---- >> [ 0.108552] pci 0000:01:01.0: reg 10 32bit mmio: [0xfe5ffc00-0xfe5ffcff] >> [ 0.108561] pci 0000:01:01.0: reg 14 io port: [0xbc00-0xbc07] >> [ 0.108570] pci 0000:01:01.0: reg 18 io port: [0xb800-0xb8ff] >> [ 0.108611] pci 0000:01:01.0: supports D2 >> [ 0.108614] pci 0000:01:01.0: PME# supported from D2 D3hot D3cold >> [ 0.108619] pci 0000:01:01.0: PME# disabled >> >> The PCI slot 01:01.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. >> >> >> === Finished firmware and bootup diagnostics, next deducing cogent software. >> === >> >> Predictive diagnostics for card in bus 01:01.0: >> Modem chipset detected on >> NAME="Communication controller: Agere Systems V.92 56K WinModem " >> CLASS=0780 >> PCIDEV=11c1:048c >> SUBSYS=11c1:044c >> IRQ=5 >> IDENT=agrsm >> >> For candidate modem in: 01:01.0 >> 0780 Communication controller: Agere Systems V.92 56K WinModem >> Primary device ID: 11c1:048c >> Support type needed or chipset: agrsm >> >> >> >> The AgereSystems/LSI agrsm code supports compiling of a agrmodem + >> agrserial driver pair. >> There are a few different chipsets which use this driver pair, but >> they use different code resources: >> Chipsets KV* PackageNames (most current as of November 2009) >> ---------------------------------------------------------------------------------------------- >> 11c1:048c and 11c1:048f >> 2.6.29 agrsm048pci-2.1.60_20100108_i386.deb or >> agrsm048pci-2.1.60_20100108.tar.gz >> 11c1:0620 2.6.31 >> agrsm06pci-2.1.80_20100106_i386.deb or >> agrsm06pci-2.1.80~20100106.tar.gz !! >> 11c11040 (on HDA audio cards) 2.6.31 >> agrsm-11c11040_20091225_i386.deb or >> agrsm-11c11040-2.1.80~20091225.tar.bz2 !! >> All available at: >> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ >> Additionally there are; >> automation & testing agrsm-tools_0.0.1_all.deb or >> agrsm-tools-0.0.1-2.noarch.rpm >> General background agrsm_howto.txt >> ------------------------------------------------------------------------------------------------ >> * KV == latest kernel release with a reported success >> !! Latest update with major credit to Nikolay Zhuravlev >> But see conflict issue: >> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html >> Report from Bjorn Wielens: >> Please note- trying to load the modules on a OpenSuSE 11.2 system gives >> an error about the module_version symbol. Using: >> # modprobe --force agrmodem >> # modprobe --force agrserial >> is necessary to load the drivers, and does not appear to cause ill effects. >> >> >> All of the above packages are dkms competent. This means that if your >> Linux distros dkms package >> is previously installed, if provides for future updates matching >> forthcoming kernels. >> >> -------------- end Agere Systems section ------------------- >> >> Completed candidate modem analyses. >> >> The base of the UDEV device file system is: /dev/.udev >> >> Versions adequately match for the compiler installed: 4.4.1 >> and the compiler used in kernel assembly: 4.4.1 >> >> >> >> Minimal compiling resources appear complete: >> make utility - /usr/bin/make >> Compiler version 4.4 >> linuc_headers base folder /lib/modules/2.6.31-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 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 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 >> >> For guidance on FAX usage, get from >> http://linmodems.technion.ac.il/packages/ get faxing.tar.gz >> It has samples for a modem using port /dev/ttySL0, which must be >> changed to match your modem's port. >> >> 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: >> slmodemd created symbolic link /dev/ttySL0: >> Within /etc/udev/ files: >> >> 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: >> >> --------- end modem support lines -------- >> > -- Joshua Crawford ... http://geocities.com/mortarn http://www.rewardscentral.com.au/Join/Default.aspx?refer=mortarn Be rewarded! Join RewardsCentral today!
