Hi,
Maybe someone can help me. I installed QNX RTP onto my computer
yesterday but have yet to try the Voyager browser. I have read the Help
files but I may have overlooked something obvious.
The problem is that “devc-ser8250” currently only starts up ports 1 and
2 but my internal modem is on port 3. So I launch “devc-ser8250 -u3
3e8,3”. “ser3” then appears under /dev as it should. I then send an
AT command to the modem but cannot communicate with it. The port
address of ‘3e8’ is one that I determined under my main OS (Windows
98). Unfortunately, I can’t seem to determine the interrupt being used
for this device under Windows so I simply tried IRQ 3, then 4, 5, 6 …
none worked.
The modem is an AOPEN 56k. Is it simply because “devc-ser8250” is not
the proper driver? I noticed that in the QNX site under “Hardware
Supported” there are no entries for modems, except for PCMCIA modems.
Are only external devices supported?
Best regards,
Marcel Leclerc
Hi Marcel,
I have the same modem, and the same configuration…
My solution was similar to yours - except -
I “slay” devc-ser8250 first (it was started at boot with only ser1 and
ser2),
then I start a devc-ser8250 with all three ser ports explicitly defined on
the command line.
The modem interrupt is “shared” with one of the other ser ports. (I don’t
remember offhand whether it was IRQ3 or IRQ4 )
This works fine on my machine, since the ser1 and ser2 ports are on the
motherboard, and the AOPEN modem is a PCI modem.
Other hardware situations may cause problems with sharing of an interrupt in
this case.
Regards,
Stephen Munnings
Corman Technologies Inc.
Marcel Leclerc <amassinf@amassdata.com> wrote in message
news:3A92F167.CB36A6D5@amassdata.com…
Hi,
Maybe someone can help me. I installed QNX RTP onto my computer
yesterday but have yet to try the Voyager browser. I have read the Help
files but I may have overlooked something obvious.
The problem is that “devc-ser8250” currently only starts up ports 1 and
2 but my internal modem is on port 3. So I launch “devc-ser8250 -u3
3e8,3”. “ser3” then appears under /dev as it should. I then send an
AT command to the modem but cannot communicate with it. The port
address of ‘3e8’ is one that I determined under my main OS (Windows
98). Unfortunately, I can’t seem to determine the interrupt being used
for this device under Windows so I simply tried IRQ 3, then 4, 5, 6 …
none worked.
The modem is an AOPEN 56k. Is it simply because “devc-ser8250” is not
the proper driver? I noticed that in the QNX site under “Hardware
Supported” there are no entries for modems, except for PCMCIA modems.
Are only external devices supported?
Best regards,
Marcel Leclerc
Marcel, in another group, reports that his modem is an Acer FM56-PM, which
Acer’s
web site lists as a controller-less modem. I am not aware of anyone posting
a driver for
controller-less modems under RTP. If it is not a controller-less modem,
then following
your intructions should also work for him.
Hi Marcel,
I have the same modem, and the same configuration…
My solution was similar to yours - except -
I “slay” devc-ser8250 first (it was started at boot with only ser1 and
ser2),
then I start a devc-ser8250 with all three ser ports explicitly defined
on
the command line.
The modem interrupt is “shared” with one of the other ser ports. (I don’t
remember offhand whether it was IRQ3 or IRQ4 )
This works fine on my machine, since the ser1 and ser2 ports are on the
motherboard, and the AOPEN modem is a PCI modem.
Other hardware situations may cause problems with sharing of an interrupt
in
this case.
Regards,
Stephen Munnings
Corman Technologies Inc.
Marcel Leclerc <> amassinf@amassdata.com> > wrote in message
news:> 3A92F167.CB36A6D5@amassdata.com> …
Hi,
Maybe someone can help me. I installed QNX RTP onto my computer
yesterday but have yet to try the Voyager browser. I have read the Help
files but I may have overlooked something obvious.
The problem is that “devc-ser8250” currently only starts up ports 1 and
2 but my internal modem is on port 3. So I launch “devc-ser8250 -u3
3e8,3”. “ser3” then appears under /dev as it should. I then send an
AT command to the modem but cannot communicate with it. The port
address of ‘3e8’ is one that I determined under my main OS (Windows
98). Unfortunately, I can’t seem to determine the interrupt being used
for this device under Windows so I simply tried IRQ 3, then 4, 5, 6 …
none worked.
The modem is an AOPEN 56k. Is it simply because “devc-ser8250” is not
the proper driver? I noticed that in the QNX site under “Hardware
Supported” there are no entries for modems, except for PCMCIA modems.
Are only external devices supported?
Best regards,
Marcel Leclerc
I guess I did not look at the model numbers very carefully… Mine is an
AOPEN FM56-ITU/2 - not the FM56-PM
Sorry for the confusion…
Dave Nickerson <dnickerson@qnx.com> wrote in message
news:9714kn$500$1@nntp.qnx.com…
Marcel, in another group, reports that his modem is an Acer FM56-PM, which
Acer’s
web site lists as a controller-less modem. I am not aware of anyone
posting
a driver for
controller-less modems under RTP. If it is not a controller-less modem,
then following
your intructions should also work for him.
I have the same modem, and the same configuration…
My solution was similar to yours - except -
I “slay” devc-ser8250 first (it was started at boot with only ser1 and
ser2),
then I start a devc-ser8250 with all three ser ports explicitly
defined
on
the command line.
The modem interrupt is “shared” with one of the other ser ports. (I
don’t
remember offhand whether it was IRQ3 or IRQ4 )
This works fine on my machine, since the ser1 and ser2 ports are on the
motherboard, and the AOPEN modem is a PCI modem.
Other hardware situations may cause problems with sharing of an
interrupt
in
this case.
Regards,
Stephen Munnings
Corman Technologies Inc.
Marcel Leclerc <> amassinf@amassdata.com> > wrote in message
news:> 3A92F167.CB36A6D5@amassdata.com> …
Hi,
Maybe someone can help me. I installed QNX RTP onto my computer
yesterday but have yet to try the Voyager browser. I have read the
Help
files but I may have overlooked something obvious.
The problem is that “devc-ser8250” currently only starts up ports 1
and
2 but my internal modem is on port 3. So I launch “devc-ser8250 -u3
3e8,3”. “ser3” then appears under /dev as it should. I then send an
AT command to the modem but cannot communicate with it. The port
address of ‘3e8’ is one that I determined under my main OS (Windows
98). Unfortunately, I can’t seem to determine the interrupt being
used
for this device under Windows so I simply tried IRQ 3, then 4, 5, 6
…
none worked.
The modem is an AOPEN 56k. Is it simply because “devc-ser8250” is not
the proper driver? I noticed that in the QNX site under “Hardware
Supported” there are no entries for modems, except for PCMCIA modems.
Are only external devices supported?
Best regards,
Marcel Leclerc
\