Faraz, Might be an issue with x86_64 versus i686? Since your machine is 64 bit -------------------------- System information ---------------------------- CPU=x86_64, Ubuntu , ALSA_version= Linux version 2.6.31-20-generic (buildd@yellow) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu SMP Mon Feb 8 09:02:26 UTC 2010 scanModem update of: 2010_02_25 The modem symbolic link is /dev/modem -> /dev/ttySHSF0 Distrib_ID=Ubuntu DistribCodeName=karmic AptRepositoryStem=http://th.archive.ubuntu.com/ubuntu/ Presently install your Linux Distributions dkms package. It provides for automated driver updates, following upgrade of your kernel. For details see http://linux.dell.com/projects.shtml#dkms Some modem drivers can only be used in 32 bit modem on x86_64 systems, while some others are competent on x86_64 Systems. Cases are: 1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem controllers. In both cases, 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component. 2) For USB modems using the slusb.ko driver. 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are x86_64 competent. 4) agrsm packages for LSI/AgereSystems softmodems are not competent on x86_64 systems. There are no blacklisted modem drivers in /etc/modprobe* files ATM, there are no x86_64 bit alsa drivers for your 2.6.31-? Ubuntu Kernel :( http://www.linuxant.com/alsa-driver/downloads-ubuntu-x86_64.php Jonathan, Is there a package that he can use?, or does the all deb package he used OK? Thanks, Antonio On 3/14/10, Faraz Faghri <faraz.faghri@xxxxxxxxx> wrote: > Thanks Antonio, > > I got the modem installed following the linuxant guide by installing: > alsa-driver-linuxant_1.0.20.3_all.deb > hsfmodem-7.80.02.05x86_64full.tar.gz > > but now there is conflict between alsa and pulseaudio; pulseaudio is > unable of detecting my audio device. I definitely want to use > pulseaudio and no modem sound would not bother me. but I am not sure > by removing the alsa package my modem would work properly, since in > the first try I installed the hsfmodem without alsa and it didn't > detect my modem. > > I appreciate your help. > > On Mon, Mar 15, 2010 at 12:02 AM, Antonio Olivares > <olivares14031@xxxxxxxxx> wrote: >> Faraz, >> >> A pci modem is not detected through the devices. See recommendations >> given by scanModem: >> >> A candidate modem is not transparent among the PCI devices: >> ------------------------------------------------ >> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series >> Chipset Integrated Graphics Controller (rev 07) >> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset >> Integrated Graphics Controller (rev 07) >> 00:03.0 Communication controller: Intel Corporation Mobile 4 Series >> Chipset MEI Controller (rev 07) >> 00:03.2 IDE interface: Intel Corporation Mobile 4 Series Chipset PT >> IDER Controller (rev 07) >> 00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset >> AMT SOL Redirection (rev 07) >> 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network >> Connection (rev 03) >> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio >> Controller (rev 03) >> 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI >> Controller (rev 03) >> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller >> (rev 03) >> 03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN >> [Shiloh] Network Connection >> ------------------------------------------------ >> with USB, bridge, and RAM devices not displayed. >> If a High Definition Audio card is present, if might be hosted on the >> Subsystem. >> >> If your modem is an >> external USB type, >> connected by an external serial cable, >> or mounted internally on an ISA card, >> then scanModem would not access it. >> >> Try this first >> >> Try with Root permission >> (1) $ 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 >> >> >> Try this if step (1) did not return any results >> >> (2) >> 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. >> >> scanModem also reports that you have a driver apparently installed: >> >> The modem symbolic link is /dev/modem -> /dev/ttySHSF0 >> >> Hopefully >> $ sudo wvdialconf /etc/wvdial.conf >> >> finds it. Let us know if it does or not. If it does not find the >> modem port, and you can boot into windows, please run the tests >> suggested above and report back. >> >> Regards, >> >> Antonio >> >> >> >> >> >> On 3/14/10, Faraz Faghri <faraz.faghri@xxxxxxxxx> wrote: >>> Hi, >>> >>> I have a ThinkPad X200 with and I am not able finding the suitable way >>> of installing the modem. >>> The scanmodem log is attached. >>> >>> Could anyone guide me through the installation, please. >>> Thanks in advance. >>> >> >
