Hatem, scanModem does report that you chose the correct driver and it reports that you have some troubleIirq sharing?/) For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 00:1b.0 8086:293e 103c:30f7 Audio device: Intel Corporation 82801I Modem interrupt assignment and sharing: 34: 534 1019 PCI-MSI-edge HDA Intel --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- [ 0.533315] pci 0000:00:1b.0: reg 10 64bit mmio: [0xdf300000-0xdf303fff] [ 0.533365] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold [ 0.533369] pci 0000:00:1b.0: PME# disabled [ 17.096096] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 [ 17.096108] HDA Intel 0000:00:1b.0: PCI INT B -> GSI 22 (level, low) -> IRQ 22 [ 17.096180] HDA Intel 0000:00:1b.0: irq 34 for MSI/MSI-X [ 17.096223] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 17.245551] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10 [ 17.265332] input: HDA Intel Mic at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 [ 17.265407] input: HDA Intel HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12 The PCI slot 00:1b.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 sent us dmesg, but I can't find any line there to reference, the only thing I can point to is if you can read up on Modem/DOCs/Bootup.txt to try some things like acpi=off, or other kernel parameters and see if you can get access to the modem that way. Regards, Antonio On Sat, Nov 27, 2010 at 6:20 AM, Hatem Hasan <hatem.nady@xxxxxxxxx> wrote: > Dear All, > > I'm running Ubuntu lucid 32-bit, and as per scanModem, I have an > AgereSystems/LSI modem hosted on audio card. > I' ve downloaded and installed the required package for agrsm driver > "agrsm-11c11040_20091225_i386.deb", and installed > "agrsm-tools_0.0.1_all.deb" as well. > The problem is for unkown reason "for me", my system still cannot > detect the driver, and by running the command agrsm-test in the > terminal, it gave me the following: > > --------------------------------------------- > > hatem@HNH-PC:/$ sudo agrsm-test > > Found drivers for boot kernel 2.6.32-21-generic at: > /lib/modules/2.6.32-21-generic/extra/agrmodem.ko > /lib/modules/2.6.32-21-generic/extra/agrserial.ko > > > > FATAL: Module agrserial not found. > FATAL: Module agrmodem not found. > Loading drivers: > FATAL: Module agrmodem not found. > FATAL: Module agrserial not found. > ln: creating symbolic link `/dev/ttySAGR': File exists > FATAL: Error running install command for agrserial > > Drivers loaded: > > and symbolic link created: > lrwxrwxrwx 1 root root 12 2010-11-27 12:11 /dev/ttySAGR -> /dev/ttyAGS3 > > Checking for utility wvdialconf > Found /usr/bin/wvdialconf, preparing to run: > wvdialconf /etc/wvdial.conf > > Modem Port Scan<*1>: S0 S1 S2 S3 SAGR > > A reboot may be necessary before modem detection through: > sudo modprobe agrserial > Which will load agrmodem, agrserial and create the symbolic link needed for: > sudo wvdialconf > > > The installation record has been written to ./agrsm-test.txt > --------------------------------------------- > > I made reboot and repeated the command but still having the same > result. I attached with this message both dmesg.txt and ModemData.txt > > Your help is highly appreciated. Thanks. > > > -- > Kind Regards, > > Hatem Nady > > Petroleum Geologist, Egypt. >
