In case of keyboard and mouse failures when booting earlier kernels, Ozan sent the following workaround. <quote> Thanks guys, Now it works my agrsm chipset modem in ubuntu. And hint for ubuntu. Sometimes when you return old kernel in ubuntu mouse and keyboard doesnt function. To solve problem boot your old kernel in recovery mode. You need to reinstall hal-info packet. and to reinstall this packet run this command. sudo apt-get --reinstall install hal-info Best regards, Ozan Sirin </quote> This in case that happens, otherwise things should work fine. Regards, Antonio On 7/16/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > Hugo, > > First read > http://linmodems.technion.ac.il/bigarch/archive-nineth/msg01316.html > > More general info follows. > MarvS > ============ > > Packages "agrsm" provide resources for compiling the agrmodem + > agrserial driver pair. > > For the 11c11040 (VEN_11C1&DEV_1040) modem chips on High Definition > Audio cards, the driver resource > is called dkms-agrsm and maintained at > http://linux.zsolttech.com/linmodem/agrsm/ , > There are a few installation formats. First install your Distro's dkms > package > The dkms toolset automates compiling, including compiling of needed > update drivers > when an update kernel is installed. Test if already installed with: > dkms --help > If not installed or on your installation media, check your > distribution's repository. > See the example at > http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03863.html > For Ubuntu, the repository is at http://packages.ubuntu.com. Comments > are more general compiling support are below. > > http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ has copies > and some updates > in Debian installation formats and related documentation and tools. > There is a agrsm_howto.txt, though it's leading compilation section is > not needed for all cases below. > There are a few cases of support implementation, depending on the host > system and particular chip type. > The agrsm-tools package creates symbolic links and runs a first functional > test, > provided the wvdial package is installed. > Upon download and copying into your Linux partition, installation can > be done with: > $ sudo dpkg -i agrsm*.deb > or one of the more sophisticated installation tools. > > For a few Ubuntu kernels, driver installation packagea are at > agrsm-2.6.27-7-generic_2.6.27-7.14_i386.deb > agrsm-2.6.27-9-generic_2.6.27-9.14_i386.deb > for 2.6.27-7-generic and 2.6.27-9-generic kernels ONLY. > Resources are at http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > > For the modem chips 11c1:0620, 11c1:0630 and 11c1:048c(or f), the > current confirmed support is with the > agrsm-20090418.tar.gz at > http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > See Josh Crawford's report: > http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00475.html. > The 11c1:0620 chipset is also supported by the dkms-agrsm package > (reports Hugo Canelli) > > For implementation guidance, get the agrsm_howto.txt from > http://linmodems.technion.ac.il/packages/ltmodem/11c1040/ . > However the leading compiling section should be skipped for > installation done with dkms tools. > For Debian/Ubuntu related systems also get the from > http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ > the agrsm-tools_0.0.1_all.deb. Though lacking drivers, it automates > setup of symbolic links initiated by > $ sudo modprobe agrserial > and also has a utility, called by: > $ sudo agrsm-test > > For kernels earlier than 2.6.26 the more laborious procedures. > A simplest route is to get from > http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ one of: > kernel-2.6.21.0-22.i686.rpm > linux-image-2.6.21.0-22_2.6.21.0-22_i386.deb > as their module set contains the drivers, but just for kernel 2.6.21.0-22. > > For the Ubuntu 2.6.24-19-generic kernel, there is a driver package > agrsm-ubuntu8.04.1-2.6.24-19-generic.tar.gz > > For kernels between 2.6.21 and 2.6.26 read the > HOWTO-Agere-11c11040-HDA.html, > which relates a laborious procedure involving kernel-source code. > > A single root/adm command: > modprobe agrserial > will provide for loading both drivers and symbolic /dev/ttySAGR link > creation, > if the following two lines to some file in the /etc/modprobe folders. > > install agrserial /sbin/modprobe --ignore-install agrmodem ; > /sbin/modprobe --ignore-install agrserial && \ > test -e /dev/ttySAGR || ln -s /dev/ttyAGS3 /dev/ttySAGR > remove agrserial /sbin/modprobe -r --ignore-remove agrserial ; > /sbin/modprobe -r --ignore-remove agrmodem && { if test -L > /dev/ttySAGR; then rm /dev/ttySAGR; fi } ; true > > They will alternatively be installed by the package > agrsm-tools_0.0.1_all.deb > > > On Thu, Jul 16, 2009 at 1:03 PM, hugo ferrandes<hugoferrandes@xxxxxxxx> > wrote: >> Marvin Stodolsky a écrit : >>> >>> Hugo, >>> >>> We need more info >>> >>> Many modems for which scanModem fails have Conexant chips. >>> >>> >From http://www.linuxant.com/drivers/modemident.php >>> >>> get the ListModem tool, which will report on Conexant chipset modems >>> >>> >>> >>> If the above tests fail, please provide any independent information >>> available on your modem. >>> >>> If an alternative boot into Microsoft windows can be done, do mouse >>> >>> clicks on: >>> >>> Start > Settings > Control Panel > Classical View (for Window XP) > >>> System >>> >>> >>>> >>>> Hardware > Device Manager > Modems > Click on the + > Modem. Double >>>> click >>>> to >>>> >>> >>> expand the graphic. Manufacturer information may be displayed. For >>> example, CXT >>> >>> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or >>> vendor >>> >>> and device information. From the Driver Details TAB, copy out the >>> VENdor and DEVice information. >>> >>> Next do the Query Modem and record the ATI specifications displayed such >>> as: >>> >>> ATI3 - Agere SoftModem Version 2.1.22 >>> >>> ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 >>> >>> Try to identify the modem setup file, with name perhaps MODEM.INF. >>> >>> If may contain chipset Vendor informaton. >>> >>> >>> On Thu, Jul 16, 2009 at 4:58 AM, hugo ferrandes<hugoferrandes@xxxxxxxx> >>> wrote: >>> >>>> >>>> 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-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.28-11-generic (buildd@palmer) (gcc version 4.3.3 >>>> (Ubuntu >>>> 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 >>>> >>>> scanModem update of: 2009_07_02 >>>> >>>> >>>> >>>> The dialer utility package WVDIAL does not appear to be installed on >>>> your >>>> System. >>>> >>>> Please read Modem/DOCs/wvdial.txt >>>> >>>> >>>> >>>> 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 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive >>>> >>>> ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse >>>> >>>> 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:14.2, firmware information and bootup >>>> diagnostics are: >>>> >>>> PCI slot PCI ID SubsystemID Name >>>> >>>> ---------- --------- --------- -------------- >>>> >>>> 00:14.2 1002:437b 1179:ff00 Audio device: ATI Technologies Inc >>>> IXP >>>> SB4x0 High Definition Audio Controller >>>> >>>> >>>> >>>> Modem interrupt assignment and sharing: >>>> >>>> 16: 4716 IO-APIC-fasteoi ohci1394, HDA Intel >>>> >>>> --- Bootup diagnostics for card in PCI slot 00:14.2 ---- >>>> >>>> [ 0.698088] pci 0000:00:14.2: reg 10 64bit mmio: >>>> [0xd0500000-0xd0503fff] >>>> >>>> [ 0.698144] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold >>>> >>>> [ 0.698150] pci 0000:00:14.2: PME# disabled >>>> >>>> [ 12.896537] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) >>>> -> >>>> IRQ 16 >>>> >>>> >>>> >>>> The PCI slot 00:14.2 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: ALC861 Analog : ALC861 Analog : playback 1 : capture 1 >>>> >>>> >>>> >>>> about /proc/asound/cards: >>>> >>>> ------------------------ >>>> >>>> 0 [SB ]: HDA-Intel - HDA ATI SB >>>> >>>> HDA ATI SB at 0xd0500000 irq 16 >>>> >>>> >>>> >>>> PCI slot 00:14.2 has a High Definition Audio Card >>>> >>>> The drivers are in the kernel modules tree at: >>>> >>>> /lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko >>>> >>>> UNEXPECTED HDA diagnostic outcome. >>>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>> software. >>>> === >>>> >>>> >>>> >>>> A candidate modem is not evident among the PCI devices: >>>> >>>> ------------------------------------------------ >>>> >>>> 00:12.0 IDE interface: ATI Technologies Inc IXP SB400 Serial ATA >>>> Controller >>>> (rev 80) >>>> >>>> 00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 82) >>>> >>>> 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller >>>> (rev >>>> 80) >>>> >>>> 00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition >>>> Audio >>>> Controller (rev 01) >>>> >>>> 01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon >>>> Xpress >>>> 200M] >>>> >>>> 02:00.0 Ethernet controller: Atheros Communications Inc. AR242x >>>> 802.11abg >>>> Wireless PCI Express Adapter (rev 01) >>>> >>>> 09:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE >>>> 1394 OHCI Link Layer Controller (rev c0) >>>> >>>> 09:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. >>>> RTL-8139/8139C/8139C+ (rev 10) >>>> >>>> ------------------------------------------------ >>>> >>>> with USB and bridge devices not displayed. >>>> >>>> >>>> >>>> If your modem is connected by an external serial cable, >>>> >>>> or mounted internally on an ISA card, scanModem would not access it. >>>> >>>> Try with Root permission >>>> >>>> $ sudo wvdialconf /etc/wvdial.conf >>>> >>>> to detect these modem types and some USB modems. >>>> >>>> If the detection is successful, read the DOCs/wvdial.txt . >>>> >>>> Edit the /etc/wvdial.conf with Root permission: >>>> >>>> sudo gedit /etc/wvdial.conf >>>> >>>> will be able to dial out with Root permission: >>>> >>>> sudo wvdial >>>> >>>> >>>> >>>> Many modems for which scanModem fails have Conexant chips. >>>> >>>> From http://www.linuxant.com/drivers/modemident.php >>>> >>>> get the ListModem tool, which will report on Conexant chipset modems >>>> >>>> >>>> >>>> If the above tests fail, please provide any independent information >>>> available on your modem. >>>> >>>> If an alternative boot into Microsoft windows can be done, do mouse >>>> >>>> clicks on: >>>> >>>> Start > Settings > Control Panel > Classical View (for Window XP) > >>>> System >>>> >>>> >>>>> >>>>> Hardware > Device Manager > Modems > Click on the + > Modem. Double >>>>> click >>>>> to >>>>> >>>> >>>> expand the graphic. Manufacturer information may be displayed. For >>>> example, >>>> CXT >>>> >>>> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID >>>> or >>>> vendor >>>> >>>> and device information. From the Driver Details TAB, copy out the VENdor >>>> and >>>> DEVice information. >>>> >>>> Next do the Query Modem and record the ATI specifications displayed such >>>> as: >>>> >>>> ATI3 - Agere SoftModem Version 2.1.22 >>>> >>>> ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 >>>> >>>> Try to identify the modem setup file, with name perhaps MODEM.INF. >>>> >>>> If may contain chipset Vendor informaton. >>>> >>>> >>>> >>>> >>>> >>>> Predictive diagnostics for card in bus 00:14.2: >>>> >>>> Modem chipset not detected on >>>> >>>> NAME="Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio >>>> Controller " >>>> >>>> CLASS=0403 >>>> >>>> PCIDEV=1002:437b >>>> >>>> SUBSYS=1179:ff00 >>>> >>>> IRQ=16 >>>> >>>> HDA=1002:437b >>>> >>>> SOFT=1002:437b.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 1002:437b. >>>> >>>> If another modem card is present, then most likely 1002:437b does not >>>> host a >>>> modem. >>>> >>>> If another modem card has not been detected, then possibilities are: >>>> >>>> 1) A Conexant modem chip is present on 1002:437b, 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:14.2 >>>> >>>> 0403 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio >>>> Controller >>>> >>>> Primary device ID: 1002:437b >>>> >>>> Subsystem PCI_id 1179:ff00 >>>> >>>> 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/ >>>> >>>> >>>> >>>> >>>> >>>> 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.28_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 dpkg -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.28_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 >>>> >>>> >>>> >>>> Writing DOCs/Smartlink.txt >>>> >>>> ============ end Smartlink section ===================== >>>> >>>> >>>> >>>> >>>> >>>> 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 >>>> >>>> >>>> >>>> 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.28-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 277352 2009-02-20 18: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 >>>> wlan0 >>>> wmaster0 >>>> >>>> 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 -------- >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> Marvin, >> With windows i had: >> >> MODEM: >> Toshiba software modem >> Agere >> Emplacement 65535 (Internal High Definition Audio Bus) >> port: COM3 >> ID hardware:HDAUDIO\FUNC_02&VEN_11C1&DEV_1040&SUBSYS_11790001&REV_1002 >> >> DRIVER: >> Agere >> 17/03/2006 >> 2.1.68.0 >> Microsoft Windows Hardware Compatibility Publisher >> >> >> >
