Whitney Most likely there is a Conexant modem chip on the SUBSYS=1043:8330 or the High Definition Audio card PCIDEV=8086:27d8 But best first follow the directions in SoftModem.txt to run the modem Diagnostics under a Microsoft boot. Also copy out the driver info under the DriverDetails TAB MarvS scanModem diagnostics On Sat, Nov 1, 2008 at 11:28 AM, Whitney Wesley <acertifiedcomputergeek@xxxxxxxxx> 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 Debian GNU/Linux 4.0 kernel 2.6.21.4-eeepc > 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, Debian GNU/Linux 4.0 > Linux version 2.6.21.4-eeepc (root@i386-coreos) (gcc version 4.1.2 > 20061115 (prerelease) (Debian 4.1.1-21)) #2 Tue Jul 8 12:00:00 EDT > 2008 > scanModem update of: 2008_10_24 > > There are no blacklisted modem drivers in /etc/modprobe* files > Attached USB devices are: > ID 0af0:d033 Option > > USB modems not recognized > > For candidate card in slot 00:1b.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1b.0 8086:27d8 1043:8330 Audio device: Intel Corporation 82801G > > Modem interrupt assignment and sharing: > 4: 1513 XT-PIC-XT HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [ 20.956800] ACPI: PCI Interrupt 0000:00:1b.0[A] -> Link [LNKG] -> > GSI 4 (level, low) -> IRQ 4 > [ 20.956830] PCI: Setting latency timer of device 0000:00:1b.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.16 > The modem cards detected by "aplay -l" are: None > > > The /proc/asound/pcm file reports: > ----------------------- > 00-00: ALC269 Analog : ALC269 Analog : playback 1 : capture 1 > > about /proc/asound/cards: > ------------------------ > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xf7db8000 irq 4 > > PCI slot 00:1b.0 has a High Definition Audio Card > The drivers are in the kernel modules tree at: > /lib/modules/2.6.21.4-eeepc/kernel/sound/pci/hda/snd-hda-intel.ko > === Finished firmware and bootup diagnostics, next deducing cogent software. === > > A candidate modem is not evident among the PCI devices: > ------------------------------------------------ > 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME > Express Integrated Graphics Controller (rev 03) > 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, > 943/940GML Express Integrated Graphics Controller (rev 03) > 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High > Definition Audio Controller (rev 02) > 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) > SATA IDE Controller (rev 02) > 01:00.0 Ethernet controller: Atheros Corp. L1e Gigabit Ethernet Adapter (rev b0) > 02:00.0 Ethernet controller: Atheros Communications Inc. AR242x > 802.11abg Wireless PCI Express Adapter (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. > > The /proc/asound/ audio+modem diagostics are being copied. > Finished copy to Modem/ALSAuser.tgz > > Predictive diagnostics for card in bus 00:1b.0: > Modem chipset not detected on > NAME="Audio device: Intel Corporation 82801G " > CLASS=0403 > PCIDEV=8086:27d8 > SUBSYS=1043:8330 > IRQ=4 > HDA=8086:27d8 > SOFT=8086:27d8.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 8086:27d8. > If another modem card is present, then most likely 8086:27d8 does not > host a modem. > If another modem card has not been detected, then possibilities are: > 1) A Conexant modem chip is present on 8086:27d8, 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:1b.0 > 0403 Audio device: Intel Corporation 82801G > Primary device ID: 8086:27d8 > Subsystem PCI_id 1043:8330 > 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 -------------- > > Writing DOCs/Intel.txt > > 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.21.4_eeepc > 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 > 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 ===================== > > > The base of the UDEV device file system is: /dev/.udev > > The kernel was compiled with gcc version 4.1.2 and a compiler is not installed > > linux-headers-2.6.21.4-eeepc resources needed for compiling are not > manifestly ready! > > If compiling is necessary packages must be installed, providing: > gcc-4.1 linux-headers-2.6.21.4-eeepc > > For Debian and some related distributions, a package > kernel-kbuild-2.6-21 may be needed to support driver compiling. > > > 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 > auth > 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: ath0 eth0 wifi0 > 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: > /etc/udev/rules.d/50-xandros-udev.rules:# usb modems > /etc/udev/rules.d/049_hso-udev.rules:SUBSYSTEM=="tty", > SYSFS{hsotype}=="Modem", SYMLINK+="wmodem0" > 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 -------- >
