From: Maurizio Loreti on
Hello, world -

I have yesterday installed Fedora Core-3 on a brand new PC at home;
that PC has a PCI modem card from US-Robotics (model 5661A). The
modem card worked perfectly under Windows XP at the first attempt.

With FC3 Linux, 'lspci' told me:

> lspci
....
01:01.0 Communication controller: U.S. Robotics: Unknown device 2f00 (rev 01)
....
> lspci -v
....
01:01.0 Communication controller: U.S. Robotics: Unknown device 2f00 (rev 01)
Subsystem: U.S. Robotics: Unknown device 010c
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at ff8f0000 (32-bit, non-prefetchable) [size=64K]
I/O ports at bc00 [size=8]
Capabilities: [40] Power Management version 2
....
>

(that are, in a different format, the same informations I could obtain
from Windows about the modem card). When bootstrapping, the only info
shown about serial lines is the following:

> dmesg | grep -i tty
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>

As root, I tried

> setserial /dev/ttyS4 irq 10 port 0xbc00
> setserial /dev/ttyS4 ^fourport ^auto_irq skip_test spd_vhi
> setserial -a /dev/ttyS4
/dev/ttyS4, Line 4, UART: unknown, Port: 0xbc00, IRQ: 10
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_vhi skip_test
>

In the same moment, in /var/log/messages these lines appeared:

Feb 6 15:39:50 mlinux kernel: ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 11 (level, low) -> IRQ 11
Feb 6 15:39:50 mlinux kernel: [drm] Initialized i915 1.1.0 20040405 on minor 0:
Feb 6 15:39:50 mlinux kernel: mtrr: base(0xf0020000) is not aligned on a size(0x800000) boundary

So, the OS didn't like my setup. Anyhow I tried with minicom,
defining the serial device as being /dev/ttyS4 with 115200 8N1, and
tryng to send "AT", "ATZ", "AT S7=45 S0=0 L2 V1 X3 &C1 E1 Q0" and
every other command I could imagine: no answer, and nothing in
/var/log/messages.

Can somebody help me suggesting what to try next?

Thank you in advance, Maurizio

--
Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html
Dept. of Physics, Univ. of Padova, Italy ROT13: ybergv(a)cq.vasa.vg
From: Moe Trin on
In article <rmzmygrfbd.fsf(a)mlinux.pd.infn.it>, Maurizio Loreti wrote:

>I have yesterday installed Fedora Core-3 on a brand new PC at home;
>that PC has a PCI modem card from US-Robotics (model 5661A). The
>modem card worked perfectly under Windows XP at the first attempt.

Doing a search on google doesn't turn up much information on this
model number, but what it does makes it look very much like a winmodem.
Notice that unlike the 3CP5610 (and similar) USR does not mention anything
except windoze. Can you look _in windoze_ and see how large the "driver"
is?

>01:01.0 Communication controller: U.S. Robotics: Unknown device 2f00 (rev 01)
> Subsystem: U.S. Robotics: Unknown device 010c
> Flags: bus master, medium devsel, latency 32, IRQ 10
> Memory at ff8f0000 (32-bit, non-prefetchable) [size=64K]
> I/O ports at bc00 [size=8]
> Capabilities: [40] Power Management version 2

I don't like the idea that with FC3, the device is unknown.

>When bootstrapping, the only info shown about serial lines is the following:
>
>> dmesg | grep -i tty
>ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

That's the on-board serial port.

>As root, I tried
>
> setserial /dev/ttyS4 irq 10 port 0xbc00

I would have used a different port, but that is the correct words to get
a 3CP5610 working.

>> setserial /dev/ttyS4 ^fourport ^auto_irq skip_test spd_vhi

Not needed. The 'spd_vhi' is useless, and the auto_irq MIGHT be causing
a problem.

>> setserial -a /dev/ttyS4
>/dev/ttyS4, Line 4, UART: unknown, Port: 0xbc00, IRQ: 10

UART unknown - the serial driver section of the kernel can't see any
hardware there.

>In the same moment, in /var/log/messages these lines appeared:
>
>Feb 6 15:39:50 mlinux kernel: ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 11
> (level, low) -> IRQ 11
>Feb 6 15:39:50 mlinux kernel: [drm] Initialized i915 1.1.0 20040405 on
> minor 0:
>Feb 6 15:39:50 mlinux kernel: mtrr: base(0xf0020000) is not aligned on a
> size(0x800000) boundary

I don't know that this is related to the modem - the addresses are not the
same.

>So, the OS didn't like my setup. Anyhow I tried with minicom,
>defining the serial device as being /dev/ttyS4 with 115200 8N1, and
>tryng to send "AT", "ATZ", "AT S7=45 S0=0 L2 V1 X3 &C1 E1 Q0" and
>every other command I could imagine: no answer, and nothing in
>/var/log/messages.

Normally, USR wants 'AT&F1' as the init string - this should be found
in the manual.

>Can somebody help me suggesting what to try next?

I'd look at the windoze installation and the 'driver' specifically. In
windoze, nearly everything has drivers, including genuine hardware
modems. In that case, the driver consists of a bitmap of an icon, and the
modem init strings - usually a small file or two. If the driver is larger
than 3000 or 4000 bytes, you probably have a winmodem.

Old guy

From: Maurizio Loreti on
ibuprofin(a)painkiller.example.tld (Moe Trin) writes:

> Doing a search on google doesn't turn up much information on this
> model number, but what it does makes it look very much like a winmodem.

Thank you very much for your kind answer. Yes, it turned out that
this model is a winmodem --- so, it seems, I'm out of luck :-(

--
Maurizio Loreti http://www.pd.infn.it/~loreti/mlo.html
Dept. of Physics, Univ. of Padova, Italy ROT13: ybergv(a)cq.vasa.vg