Luis http://pci-ids.ucw.cz/read/PC/ does not report a Vendor designation 00b9 But 10b9:5451 M5451 PCI AC-Link Controller Audio Device can host a modem chip , so Iet's guess that the firmware has been mislabeled 10b9:5451 would be supported by the slmodem software, but only under i386 architechtures, not you x86_64 processor Should you choose to do a 32 bit installation, the modem might be serviced. fFom http://linmodems.technion.ac.il/packages/smartlink/ get the ungrab-winmodem.tar.gz and slmodem-2.9.11-20100718.tar.gz to more directly compile and install your own drivers. MarvS On Wed, Nov 10, 2010 at 7:53 AM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Luis, > > You are running 64 bit linux on your machine and scanModem was unable > to detect a Modem: > > A candidate modem is not transparent among the PCI devices: > ------------------------------------------------ > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset > Integrated Graphics Controller (rev 03) > 00:02.1 Display controller: Intel Corporation 4 Series Chipset > Integrated Graphics Controller (rev 03) > 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD > Audio Controller > 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port > SATA IDE Controller > 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller > 00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port > SATA IDE Controller > 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) > 03:00.0 Modem: Device 00b9:5451 > ------------------------------------------------ > Â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 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 > > You would probably need to try and send us dmesg.txt as instructed here: > > Candidate PCI devices with modem chips are: > 03:00.0 Modem: Device 00b9:5451 > 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD > Audio Controller > High Definition Audio cards can host modem chips. > > For candidate card in slot 03:00.0, firmware information and bootup > diagnostics are: > ÂPCI slot    PCI ID     ÂSubsystemID   Name > Â----------   ---------    ---------    -------------- > Â03:00.0    Â00b9:5451    00a5:5451    Modem: Device 00b9:5451 > > ÂModem interrupt assignment and sharing: > Â16:     Â0     Â0  IO-APIC-fasteoi  uhci_hcd:usb3 > Â--- Bootup diagnostics for card in PCI slot 03:00.0 ---- > [  Â0.314519] pci 0000:03:00.0: reg 10 32bit mmio: [0xfe370000-0xfe37ffff] > [  Â0.314560] pci 0000:03:00.0: PME# supported from D3hot D3cold > [  Â0.314563] pci 0000:03:00.0: PME# disabled > [  Â0.542357] serial 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [  Â0.542361] serial 0000:03:00.0: PCI INT A disabled > > ÂThe PCI slot 03:00.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 > > or > > For candidate card in slot 00:1b.0, firmware information and bootup > diagnostics are: > ÂPCI slot    PCI ID     ÂSubsystemID   Name > Â----------   ---------    ---------    -------------- > Â00:1b.0    Â8086:3a3e    103c:3664    Audio device: Intel Corporation 82801JI > > ÂModem interrupt assignment and sharing: > Â22:    Â213    Â212  IO-APIC-fasteoi  HDA Intel > Â--- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [  Â0.313512] pci 0000:00:1b.0: reg 10 64bit mmio: [0xfe9f4000-0xfe9f7fff] > [  Â0.313548] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold > [  Â0.313551] pci 0000:00:1b.0: PME# disabled > [  Â6.631757] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, > low) -> IRQ 22 > [  Â6.631785] HDA Intel 0000:00:1b.0: setting latency timer to 64 > [  Â6.859425] input: HDA Digital PCBeep as > /devices/pci0000:00/0000:00:1b.0/input/input5 > > Â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. > > but in case we are able to determine if the modem is indeed supported > the drivers would be more appropriate for 32 bit linux, unless the > modems would be supported by Linuxant drivers?, but that would require > more information. ÂHope this helps. > > Regards, > > Antonio > > On Tue, Nov 9, 2010 at 6:42 PM, Luis Fernando Gramajo P. > <fher98@xxxxxxxxx> wrote: >> Im trying to setup a RAS callback server but cant get the modem >> working, help please. >> >> >> --~--~---------~--~---------~--~---------~--~---------~--~---------~--~------- >> -- Luis Fernando Gramajo P. >> >> http://www.guatewireless.org >> --~--~---------~--~---------~--~---------~--~---------~--~---------~--~------- >> >
