Alexei, Try to follow the advice suggested in the Modem Interrupt section provided by scanModem and report back to list. Regards, Antonio ---------- Forwarded message ---------- From: Alexei Timashkov <timashkov@xxxxxxxxx> Date: Mon, 2 Nov 2009 12:47:50 +0300 Subject: Re: I need help with my hard-modem To: Antonio Olivares <olivares14031@xxxxxxxxx> Thank you, Antonio! I have it found by wvdialconf wvtest one out of two times. but even when it does find it on /dev/ttyS1, the wvdial fails because the modem is not responding =( I have a link /dev/modem to /dev/ttyS1, but this also doesn't work... seems that ttyS1 itself is not responding, and I don't know why =((( yours truly, Alexey. 2009/11/2 Antonio Olivares <olivares14031@xxxxxxxxx>: > Alexei, > > Your modem is supported through native serial driver as reported by > scanModem. To access your modem, run > $ sudo wvdialconf /etc/wvdial.conf > and it should find your modem: > > <quote> > For candidate modem in: 05:07.0 > 0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 > Primary device ID: 12b9:1008 > Support type needed or chipset: USrobotics.serial > > > Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem technology. > Their winmodems have no Linux support. Their controller chipset modems > are supported by the Linux serial drivers. > The PCI id 12b9:1008 modem is Supported. > > PCI ID Name Support status > ------------------------------------------------------------------------------- > 12b9:1008 US Robotics 3cp803598 serial driver supported > sudo wvdialconf wvtest , should detect the modem. Read DOCs/Testing.txt > ====== end 3COM section ======= > </quote> > > If wvdialconf does not find the modem, it could be because of: > > For candidate card in slot 05:07.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 05:07.0 12b9:1008 12b9:00d3 Serial controller: 3Com Corp, Modem > Division 56K FaxModem Model 5610 > > Modem interrupt assignment and sharing: > 17: 396 IO-APIC-fasteoi eth0, serial > --- Bootup diagnostics for card in PCI slot 05:07.0 ---- > [ 0.091260] pci 0000:05:07.0: reg 10 io port: [0xa000-0xa007] > [ 0.091287] pci 0000:05:07.0: supports D2 > [ 0.091290] pci 0000:05:07.0: PME# supported from D0 D2 D3hot D3cold > [ 0.091293] pci 0000:05:07.0: PME# disabled > [ 0.799714] serial 0000:05:07.0: PCI INT A -> Link[APC2] -> GSI 17 > (level, low) -> IRQ 17 > [ 0.799766] 0000:05:07.0: ttyS1 at I/O 0xa000 (irq = 17) is a 16550A > > The PCI slot 05:07.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. > > Regards, > > Antonio > > On 11/1/09, Alexei Timashkov <timashkov@xxxxxxxxx> wrote: >> Thank you guys, in advance! >> > -- Alexei Timashkov phone +7-901-304-5199 email timashkov@xxxxxxxxx skype a.timashkov ICQ 130512445
