Martin, Communication controller: Agere Systems Device 0630 " CLASS=0780 , PCIDEV=11c1:0630 is a modem we haven't encountered before under Linux. There is service for a 11c1:0630 chipset modem through a agrsm package, for compiling an agrmodem+agrserial driver pair. I'll add 11c1:0630 to the agrsm recognition codes and sent it to you, tonight or tomorrow. MarvS On Fri, Apr 3, 2009 at 6:32 PM, Martin Lupcke <mossianin_lbcmi@xxxxxxxxxx> wrote: > I recently purchased an EMachines model EL1200. It has a modem in it that I > am trying to get running because it is the only means of connecting to the > internet. The modem itself has an LSI label on the front with and Anatel > label on the back. There does not appear to any other obvious labelling. > I have tried several things including using the Windows drivers from the > EMachines website with ndiswrapper (I did not have the presence of mind to > try to get the Windows information before I wiped the drive.) I have > searched the archives for the PCIID that appears for this modem. I did find > a similar ID (11c10480, I believe) but that did not work. All to no avail. > Below is the output from scanModem's ModemData.txt file. Any assistance you > can offer to get this modem working would be appreciated. > > Thanks. > > ===Begin 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 PCLinuxOS release 2009 (PCLinuxOS) for i586 > Kernel 2.6.26.8.tex3 on an i686 / kernel 2.6.26.8.tex3 > 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, PCLinuxOS release 2009 (PCLinuxOS) for i586 > Kernel 2.6.26.8.tex3 on an i686 / > Linux version 2.6.26.8.tex3 (cyril@localhost) (gcc version 4.1.1 20060724 > (prerelease) (4.1.1-4pclos2007)) #1 SMP Mon Jan 12 04:33:38 CST 2009 > scanModem update of: 2009_02_21 > The modem symbolic link is /dev/modem -> ttyS0 > 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 0bc2:0888 Seagate RSS LLC > ID 0bda:0151 Realtek Semiconductor Corp. Mass Stroage Device > 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 03:00.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 03:00.0 11c1:0630 11c1:0630 Communication controller: Agere Systems > Device 0630 > > Modem interrupt assignment and sharing: > --- Bootup diagnostics for card in PCI slot 03:00.0 ---- > > 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 1025:0153 Audio device: nVidia Corporation MCP61 > High Definition Audio > > Modem interrupt assignment and sharing: > 22: 8522 IO-APIC-fasteoi ehci_hcd:usb1, HDA Intel > --- Bootup diagnostics for card in PCI slot 00:05.0 ---- > ACPI: PCI Interrupt 0000:00:05.0[B] -> Link [AAZA] -> GSI 22 (level, low) -> > IRQ 22 > PCI: Setting latency timer of device 0000:00:05.0 to 64 > > > ===== 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: ALC888 Analog : ALC888 Analog : playback 1 : capture 1 > 00-04: ALC888 Analog : ALC888 Analog : capture 1 > > about /proc/asound/cards: > ------------------------ > 0 [NVidia ]: HDA-Intel - HDA NVidia > HDA NVidia at 0xfe024000 irq 22 > > PCI slot 00:05.0 has a High Definition Audio Card > The drivers are in the kernel modules tree at: > > UNEXPECTED HDA diagnostic outcome. > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > > A candidate modem is not evident among the PCI devices: > ------------------------------------------------ > 00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1) > 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2) > 00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2) > 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev > a2) > 00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2) > 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) > 00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) > 00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) > 00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6150SE nForce > 430 (rev a2) > 03:00.0 Communication controller: Agere Systems Device 0630 (rev 01) > ------------------------------------------------ > 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 > $ 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: > gedit /etc/wvdial.conf > will be able to dial out with Root permission: > 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:05.0: > Modem chipset not detected on > NAME="Audio device: nVidia Corporation MCP61 High Definition Audio " > CLASS=0403 > PCIDEV=10de:03f0 > SUBSYS=1025:0153 > IRQ=22 > 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: > 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 1025:0153 > 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.1.tar.gz from: > http://linmodems.technion.ac.il/packages/smartlink/ > > ----------------end Softmodem section -------------- > > 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.26.8.tex3 > 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: > 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: > 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: > 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: > wvdialconf /etc/wvdial.conf > > Start at http://www.linuxant.com/drivers/hsf/full for > eventually download of a hsfmodem-7.68.00.12full_k.???.zip package > with ??? the package type (deb, rpm, tar etc) > These packages have compiled drivers but will also compile a driver, > if there is a mismatch between the resident kernel and provided driver. > The generic hsfmodem-7.68.00.12full.tar.gz package only provides compiling > support > > Read DOCs/Conexant.txt > > Writing DOCs/Conexant.txt > > Writing DOCs/Smartlink.txt > ============ end Smartlink section ===================== > > > Predictive diagnostics for card in bus 03:00.0: > Modem chipset not detected on > NAME="Communication controller: Agere Systems Device 0630 " > CLASS=0780 > PCIDEV=11c1:0630 > SUBSYS=11c1:0630 > IRQ=10 > > For candidate modem in: 03:00.0 > 0780 Communication controller: Agere Systems Device 0630 > Primary device ID: 11c1:0630 > Support type needed or chipset: > > ----------------end Softmodem section -------------- > > scanModem could not identify the Support Type needed from diagnosics or > archives. > 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. > 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. > > > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.1.1 > and the compiler used in kernel assembly: 4.1.1 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder /lib/modules/2.6.26.8.tex3/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-t 1 root root 304536 Nov 6 2006 /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) > chmod a+x /usr/sbin/pppd > or under Ubuntu related Linuxes > chmod a+x /usr/sbin/pppd > > Checking settings of: /etc/ppp/options > lock > noauth > noipdefault > usepeerdns > > 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. > ========================================================== > > L modem ttyS0 > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: lrwxrwxrwx 1 root root 5 Apr 3 17:49 > /dev/modem -> ttyS0 > slmodemd created symbolic link /dev/ttySL0: Within /etc/udev/ files: > /etc/udev/devices.d/modem.nodes:L modem ttyS0 > Within /etc/modprobe.conf files: > > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > >
