Ok will change OS to 32bits... and send data agains, thanks. --~--~---------~--~---------~--~---------~--~---------~--~---------~--~------- -- Luis Fernando Gramajo P. http://www.guatewireless.org --~--~---------~--~---------~--~---------~--~---------~--~---------~--~------- On Wed, Nov 10, 2010 at 6: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 >> --~--~---------~--~---------~--~---------~--~---------~--~---------~--~------- >> >
