Help installing modem USR5610 in FC6



Hi
I am at wits end. I have been trying to install this USR5610B modem in FC6
and I have not been able to.

In Windows, it is using COM2 and IRQ 11

I set it up like that with setserial and it did not work. I looked up the
modem and it says it uses irq 193. I set it up with irq 193 and it neither
works.

I have googled, and tested and followed quite a number of pages to no avail.
For now, I just want linux to recognnize and talk to the modem. Then I can
pick it up from there.
How can I do that?

This is the output of setserial
[root@localhost]# setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 16550A, Port: 0xcc00, IRQ: 193, Flags: spd_vhi
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3

This is the output of wvdialconf wvtest

[root@localhost]# wvdialconf wvtest
Scanning your serial ports for a modem.

Port Scan<*1>: Scanning ttyS1 first, /dev/modem is a link to it.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Port Scan<*1>: S2 S3


Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wvdial/

If you still have problems, send mail to wvdial-list@xxxxxxxxxxxxx


Here is the output of lspci -v
[root@localhost]# lspci -v
[snip]
05:0b.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610
(rev 01) (prog-if 02 [16550])
Subsystem: 3Com Corp, Modem Division Unknown device 00d3
Flags: medium devsel, IRQ 193
I/O ports at cc00 [size=8]
Capabilities: [dc] Power Management version 2

[root@localhost]# lspci -vv
[snip]
05:0b.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610
(rev 01) (prog-if 02 [16550])
Subsystem: 3Com Corp, Modem Division Unknown device 00d3
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 193
Region 0: I/O ports at cc00 [size=8]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA
PME(D0+,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-

here is the contents of /proc/interrupts
[root@localhost]# cat /proc/interrupts
0: 2060915 IO-APIC-edge timer
1: 57115 IO-APIC-edge i8042
6: 5 IO-APIC-edge floppy
7: 2 IO-APIC-edge parport0
8: 0 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
12: 157022 IO-APIC-edge i8042
14: 39122 IO-APIC-edge ide0
15: 142904 IO-APIC-edge ide1
193: 100000 IO-APIC-level via@pci:0000:01:00.0
201: 0 IO-APIC-level uhci_hcd:usb1
209: 26565 IO-APIC-level uhci_hcd:usb2, ehci_hcd:usb5, VIA8237
217: 0 IO-APIC-level uhci_hcd:usb3
225: 7356 IO-APIC-level uhci_hcd:usb4, eth0
233: 0 PCI-MSI libata
NMI: 641
LOC: 2060902
ERR: 0
MIS: 0

Here is the output of /proc/ioports
[root@localhost]# cat /proc/ioport
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0290-0297 : pnp 00:07
0376-0376 : ide1
0378-037a : parport0
037b-037f : parport0
03c0-03df : vga+
03f2-03f5 : floppy
03f6-03f6 : ide0
03f7-03f7 : floppy DIR
03f8-03ff : serial
0800-0803 : ACPI PM1a_EVT_BLK
0804-0805 : ACPI PM1a_CNT_BLK
0808-080b : ACPI PM_TMR
0820-0823 : ACPI GPE0_BLK
0cf8-0cff : PCI conf1
5010-5015 : ACPI CPU throttle
c000-cfff : PCI Bus #05
cc00-cc07 : 0000:05:0b.0
cc00-cc07 : serial
d000-d0ff : 0000:00:12.0
d000-d0ff : via-rhine
d400-d4ff : 0000:00:11.5
d400-d4ff : VIA8237
d880-d89f : 0000:00:10.3
d880-d89f : uhci_hcd
dc00-dc1f : 0000:00:10.2
dc00-dc1f : uhci_hcd
e000-e01f : 0000:00:10.1
e000-e01f : uhci_hcd
e080-e09f : 0000:00:10.0
e080-e09f : uhci_hcd
e400-e40f : 0000:00:0f.0
e400-e40f : ahci
e480-e483 : 0000:00:0f.0
e480-e483 : ahci
e800-e807 : 0000:00:0f.0
e800-e807 : ahci
e880-e883 : 0000:00:0f.0
e880-e883 : ahci
ec00-ec07 : 0000:00:0f.0
ec00-ec07 : ahci
fc00-fc0f : 0000:00:0f.1
fc00-fc07 : ide0
fc08-fc0f : ide1

Here is the relevant part of dmesg
[root@localhost]# cat /var/log/dmesg
[snip]
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
GSI 16 sharing vector 0xC1 and IRQ 16
ACPI: PCI Interrupt 0000:05:0b.0[A] -> GSI 16 (level, low) -> IRQ 193
0000:05:0b.0: ttyS1 at I/O 0xcc00 (irq = 193) is a 16550A

Could somebody pls guide me regarding what tests and what to setup to
install this modem?
Thanks
--
------------------------------
/\_/\
|O O| pepebuho@xxxxxxxxxxx
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: The hardware conflict that XP cant see!
    ... Try removing the modem from Device Manager and rebooting. ... different IRQ. ... > I have no choice but to hard reboot. ... > be a device, it may be a program, it may be an IRQ conflict', etcetera and so ...
    (microsoft.public.windowsxp.hardware)
  • Re: How to set up dial-up on debian after a wrong pppoe config
    ... From the sound of it the modem cannot echo it's responses to ... > is trying to use because it's a laptop with card services. ... an IRQ conflict will almost certainly ... updating with those package upgrade programs. ...
    (comp.os.linux.networking)
  • Re: modem/isapnp trouble SOLVED
    ... The modem did end up at ttyS0, ... my soundcard (isapnp Soundblaster) also seems to have ... ended up using new resources; at least the resources shown by ... it seemed that the soundcard had grabbed the IRQ ...
    (Debian-User)
  • The hardware conflict that XP cant see!
    ... be a device, it may be a program, it may be an IRQ conflict', etcetera and so ... My modem, my network card, my sound card, my video card, all my USB ... different resource settings until you could get combinations that didn’t ...
    (microsoft.public.windowsxp.hardware)
  • SIO Interrupt storms and unhanded interrupts
    ... IRQ assignments and boot with OpenBSD and not run into an interrupt storm ... The problem seems to be around how a PUC device (either a PCI ... modem or a PCI serial card) and the sharing of an interrupt (usually an USB ...
    (freebsd-current)