David, Great progress, just one of those things that sometimes $ sudo wvdialconf /etc/wvdial.conf does not find the modem. Try to create one and add your username/password/ISP phone number and a line "Carrier Check = no" to your /etc/wvdial.conf file. Try the following cut + paste the following into an editor, save it as genWvdialconf and open up a terminal and type $ chmod +x genWvdialconf ================================ #!/bin/bash # # This script generates /etc/wvdial.conf so that user may just edit it echo "[Dialer Defaults]" >> /etc/wvdial.conf echo "Modem = /dev/modem" >> /etc/wvdial.conf echo "Baud = 57600" >> /etc/wvdial.conf echo "Init1 = ATZ" >> /etc/wvdial.conf echo "Init2 = ATQ0 V1 E1 S0=0 &C1 &D2" >> /etc/wvdial.conf echo "Init3 = " >> /etc/wvdial.conf echo "Area Code = " >> /etc/wvdial.conf echo "#Modem Type = Analog Modem" >> /etc/wvdial.conf echo "Phone = 1111111111" >> /etc/wvdial.conf echo "Username = 111111111" >> /etc/wvdial.conf echo "Password = 11111111111" >> /etc/wvdial.conf echo "Ask Password = 0" >> /etc/wvdial.conf echo "Dial Command = ATDT " >> /etc/wvdial.conf echo "Compuserve = 0 " >> /etc/wvdial.conf echo "Force Address = " >> /etc/wvdial.conf echo "Idle Seconds = 300" >> /etc/wvdial.conf echo "ISDN = 0" >> /etc/wvdial.conf echo "DialMessage2 =" >> /etc/wvdial.conf echo "Auto DNS = 1" >> /etc/wvdial.conf echo "Carrier Check = No" >> /etc/wvdial.conf echo "Stupid Mode = 1" >> /etc/wvdial.conf ================================ Then run it, and it as $ sudo ./genWvdialconf and it should generate a file /etc/wvdial.conf This file now you may edit it with sudo priviledges $ sudo gedit /etc/wvdial.conf and change the "111111s" to your username, password and ISP phone number. also, it would be nice if you can fix the wvdial.conf file and attempt to connect, but check to see if agrmodem.ko and agrserial.ko are loaded: $ lsmod | grep 'agr*' and then attempt to connect with your new modified file $ sudo wvdial and let us know if you could connect or not. Regards, Antonio On Sun, Jul 17, 2011 at 2:06 AM, david falls <davidfalls.acc@xxxxxxxxx> wrote: > Thanks for such a quick response. I ran them and it still just can't > seem to find the modem. After running what you suggested, I re-ran > the ScanModem. It added another line of info to the ModemData.txt > file (attached after the run commands), that looks promising, but I > still can't start the modem. Appreciate your help. > > David > > > *************************************************************** > > root@ubuntu:~# sudo wvdialconf /etc/wvdial.conf > Editing `/etc/wvdial.conf'. > > Scanning your serial ports for a modem. > > 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. > ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > Modem Port Scan<*1>: S2 S3 > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > root@ubuntu:~# > > *************************************************************** > > root@ubuntu:~# sudo modprobe agrmodem > root@ubuntu:~# sudo modprobe agrserial > root@ubuntu:~# > > *************************************************************** > > root@ubuntu:/usr/src/agrsm06pci-2.1.80# ./agr_softmodem start > Starting Agere Soft Modem > insmod: can't read > '/lib/modules/2.6.32-33-generic/kernel/drivers/char/agrmodem.ko': No > such file or directory > insmod: can't read > '/lib/modules/2.6.32-33-generic/kernel/drivers/char/agrserial.ko': No > such file or directory > ./agr_softmodem: line 29: /usr/lib/AgereSoftModem/AgereMdmDaemon: No > such file or directory > > *************************************************************** > > root@ubuntu:/usr/src/agrsm06pci-2.1.80# sudo wvdialconf /etc/wvdial.conf > Editing `/etc/wvdial.conf'. > > Scanning your serial ports for a modem. > > 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. > ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > Modem Port Scan<*1>: S2 S3 > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > root@ubuntu:/usr/src/agrsm06pci-2.1.80# > > *************************************************************** > > 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.32-33-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.21 > Linux version 2.6.32-33-generic (buildd@rothera) (gcc version 4.4.3 > (Ubuntu 4.4.3-4ubuntu5) ) #70-Ubuntu SMP Thu Jul 7 21:09:46 UTC 2011 > scanModem update of: 2011_02_04 > The modem symbolic link is /dev/modem -> /dev/ttyAGS3 > Distrib_ID=Ubuntu > DistribCodeName=lucid > AptRepositoryStem=http://us.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: > agrmodem agrserial > > 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:02.0 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem > High Definition Audio cards can host modem chips. > > For candidate card in slot 01:02.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 01:02.0 11c1:0620 11c1:0620 Communication controller: Agere Systems > Lucent V.92 Data/Fax Modem > > Modem interrupt assignment and sharing: > 17: 184 0 IO-APIC-fasteoi Intel ICH5 > --- Bootup diagnostics for card in PCI slot 01:02.0 ---- > [ 0.197230] pci 0000:01:02.0: reg 10 io port: [0xd000-0xd0ff] > [ 0.197286] pci 0000:01:02.0: PME# supported from D3hot D3cold > [ 0.197293] pci 0000:01:02.0: PME# disabled > [ 86.956392] pci 0000:01:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > > The PCI slot 01:02.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:02.0: > Modem chipset detected on > NAME="Communication controller: Agere Systems Lucent V.92 Data/Fax Modem" > CLASS=0780 > PCIDEV=11c1:0620 > SUBSYS=11c1:0620 > IRQ=17 > IDENT=agrsm > > For candidate modem in: 01:02.0 > 0780 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem > Primary device ID: 11c1:0620 > 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 > For the 11c11040 chip with kernels 2.6.31 and later a change in a > modules loading settingmay be necessary. > Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for > your Distro), change the phrase: > options snd-hda-intel power_save=10 > to: > options snd-hda-intel power_save=0 > or the agrsm drivers will not function. For Ubuntu related systems > this can be done with: > $ sudo gedit /etc/modprobe.d/alsa-base.conf > > 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.3 > and the compiler used in kernel assembly: 4.4.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.4 > linuc_headers base folder /lib/modules/2.6.32-33-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 273312 2010-03-06 20:59 /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 > > 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 eth1 > 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 12 > 2011-07-16 19:51 /dev/modem -> /dev/ttyAGS3 > 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 -------- > > *************************************************************************************************** > > > > On Sat, Jul 16, 2011 at 7:19 PM, Antonio Olivares > <olivares14031@xxxxxxxxx> wrote: >> David, >> >> For candidate card in slot 01:02.0, firmware information and bootup >> diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 01:02.0 11c1:0620 11c1:0620 Communication controller: Agere >> Systems Lucent V.92 Data/Fax Modem >> >> Modem interrupt assignment and sharing: >> 9: 0 0 IO-APIC-fasteoi acpi >> --- Bootup diagnostics for card in PCI slot 01:02.0 ---- >> [ 0.197241] pci 0000:01:02.0: reg 10 io port: [0xd000-0xd0ff] >> [ 0.197298] pci 0000:01:02.0: PME# supported from D3hot D3cold >> [ 0.197306] pci 0000:01:02.0: PME# disabled >> >> The PCI slot 01:02.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. >> >> You have installed the correct modem driver as per ModemData.txt >> generated by scanModem. The question becomes you can't access the >> modem, have you run >> >> $ sudo wvdialconf /etc/wvdial.conf >> >> If you have not, then please do so. If the modem is not found, then >> we need to proceed to : >> >> $ sudo modprobe agrmodem >> $ sudo modprobe agrserial >> >> Now depending on whether the agr_softmodem file installed in the rc.d/ >> directories, you may call >> $ sudo agr_softmodem start >> >> should start the modem, but you may refer to the file in >> Modem/DOCs/agrsm.txt or similar. >> >> then run >> $ sudo wvdialconf /etc/wvdial.conf >> >> and hopefully this will find the modem. Let us know how this goes. >> >> Regards, >> >> Antonio >> >> On Sun, Jul 17, 2011 at 12:58 AM, david falls <davidfalls.acc@xxxxxxxxx> wrote: >>> Can you please help me get my PCI modem enabled? I have attached the >>> Modemdata.txt file following this. Also, I have added the line >>> 'pci=routeirq' to the /etc/grub.d/40_custom file since I am running >>> Grub2 and read that this is the file to add arguments to for boot up. >>> I have installed agrsm06pci-2.1.80_20100106_i386.deb as a driver and >>> it said it installed successfully. I do not have an option in BIOS to >>> neither enable nor disable the card. What am I missing? Thank you in >>> advance, it is much appreciated. >>> >>> Cheers, >>> David >>> >>> >>> >>> 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.32-33-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.21 >>> Linux version 2.6.32-33-generic (buildd@rothera) (gcc version 4.4.3 >>> (Ubuntu 4.4.3-4ubuntu5) ) #70-Ubuntu SMP Thu Jul 7 21:09:46 UTC 2011 >>> scanModem update of: 2011_02_04 >>> >>> Distrib_ID=Ubuntu >>> DistribCodeName=lucid >>> AptRepositoryStem=http://us.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:02.0 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem >>> High Definition Audio cards can host modem chips. >>> >>> For candidate card in slot 01:02.0, firmware information and bootup >>> diagnostics are: >>> PCI slot PCI ID SubsystemID Name >>> ---------- --------- --------- -------------- >>> 01:02.0 11c1:0620 11c1:0620 Communication controller: Agere >>> Systems Lucent V.92 Data/Fax Modem >>> >>> Modem interrupt assignment and sharing: >>> 9: 0 0 IO-APIC-fasteoi acpi >>> --- Bootup diagnostics for card in PCI slot 01:02.0 ---- >>> [ 0.197241] pci 0000:01:02.0: reg 10 io port: [0xd000-0xd0ff] >>> [ 0.197298] pci 0000:01:02.0: PME# supported from D3hot D3cold >>> [ 0.197306] pci 0000:01:02.0: PME# disabled >>> >>> The PCI slot 01:02.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:02.0: >>> Modem chipset detected on >>> NAME="Communication controller: Agere Systems Lucent V.92 Data/Fax Modem" >>> CLASS=0780 >>> PCIDEV=11c1:0620 >>> SUBSYS=11c1:0620 >>> IRQ=9 >>> IDENT=agrsm >>> >>> For candidate modem in: 01:02.0 >>> 0780 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem >>> Primary device ID: 11c1:0620 >>> 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 >>> For the 11c11040 chip with kernels 2.6.31 and later a change in a >>> modules loading settingmay be necessary. >>> Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for >>> your Distro), change the phrase: >>> options snd-hda-intel power_save=10 >>> to: >>> options snd-hda-intel power_save=0 >>> or the agrsm drivers will not function. For Ubuntu related systems >>> this can be done with: >>> $ sudo gedit /etc/modprobe.d/alsa-base.conf >>> >>> 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.3 >>> and the compiler used in kernel assembly: 4.4.3 >>> >>> >>> >>> Minimal compiling resources appear complete: >>> make utility - /usr/bin/make >>> Compiler version 4.4 >>> linuc_headers base folder /lib/modules/2.6.32-33-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 273312 2010-03-06 20:59 /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 >>> >>> 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 eth1 >>> 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 -------- >>> >> >
