how to use a modem which is on com3 port

Hi all

I Installed the QNX RTP about 10 days ago. Now, I want to get the packages
and I need to connect the my ISP for that, because I don’t have a CD burner.
How do I tell QNX that my modem is using com3 port ? there is no /dev/ser3.
How do I proceed ?

thanks

Frank

Com3 is a port that is used for a winmodem or a softmodem and QNX doesn’t
support those. You have to get a com1 or com2 modem instead

Frostie

“François Legault” <fr_legault@videotron.ca> wrote in message
news:TS%C5.105$Pf1.5506@weber.videotron.net

Hi all

I Installed the QNX RTP about 10 days ago. Now, I want to get the packages
and I need to connect the my ISP for that, because I don’t have a CD
burner.
How do I tell QNX that my modem is using com3 port ? there is no
/dev/ser3.
How do I proceed ?

thanks

Frank

Frostie <frustie@dds.nl> wrote in message
news:8rjvng$764$1@dinkel.civ.utwente.nl

Com3 is a port that is used for a winmodem or a softmodem and QNX doesn’t
support those. You have to get a com1 or com2 modem instead

Baloney!!

That problem may exist too, but I have a HARDWARE Modem at COM3 on my
system, and it works just fine…
The problem is that usually COM3 shares the same interrupt (IRQ 4) with COM1
which can cause problems in use also…
Therefore, the autodetection does not work correctly…
So… be aware that this is not necessarily the final solution to your
problem…

What I do, (and there are other ways also - probably better ways) is:
I created a small script:
slay devc-ser8250
sleep 1
devc-ser8250 3f8,4 2f8,3 3e8,4 &

and I run this when I first login.

You may have to make sure that those addresses and IRQs are correct for your
system…


Frostie

“François Legault” <> fr_legault@videotron.ca> > wrote in message
news:TS%C5.105$> Pf1.5506@weber.videotron.net> …
Hi all

I Installed the QNX RTP about 10 days ago. Now, I want to get the
packages
and I need to connect the my ISP for that, because I don’t have a CD
burner.
How do I tell QNX that my modem is using com3 port ? there is no
/dev/ser3.
How do I proceed ?

thanks

Frank
\

“Frostie” <frustie@dds.nl> wrote in message
news:8rjvng$764$1@dinkel.civ.utwente.nl

Com3 is a port that is used for a winmodem or a softmodem

That is not necessary true, a machine could well have a standard
modem install as com3.

However I don’t know how to get QRTP to autodectect other com port
other then com1 and com2. Probably a file in a enum directory but
I haven’t yet fully understood the details of the enum scheme.

You could start an extra serial driver manualy by doing
devc-ser8250 -u3 PORT,IRQ. Port and IRQ being specific to your device.
This will allow you to test if your modem is supported
(i.e if it’s NOT a win or soft modem). use “qtalk -m /dev/ser3” to see
if your modem responds.

If that works you could create a script (/etc/rc.d/rc.local ) and add
the command in the script.




support those. You have to get a com1 or com2 modem instead

That is not nec
Frostie

“François Legault” <> fr_legault@videotron.ca> > wrote in message
news:TS%C5.105$> Pf1.5506@weber.videotron.net> …
Hi all

I Installed the QNX RTP about 10 days ago. Now, I want to get the
packages
and I need to connect the my ISP for that, because I don’t have a CD
burner.
How do I tell QNX that my modem is using com3 port ? there is no
/dev/ser3.
How do I proceed ?

thanks

Frank
\

I was working on a similar problem yesterday and found the following which
might interrest you. By the way, I did not figured out the enum scheme yet
either but I managed to tweak it in a way so I can add new options to
devc-ser8250 that are applied automatically at startup…

  1. the file /etc/system/enum/devices/char seems to be the place where the
    driver is started, if you look at it, you’ll see the devc-ser8250 along with
    what seems to be a reference to a macro named $SER_OPTIONS. Though I think
    that this file should not be modified directly…

  2. the file /etc/system/enum/include/block seems to be the proper place to
    add new macro definition so I added the following line to it (BTW, I’m
    writing this from memory since I currently on my W95 system and I am too
    lazy to reboot into RTP just to get a copy of this right, but any way, look
    at the syntax under the enum-device utility documentation… you’ll be able
    to figure out)
    set(SER_OPTIONS, “-u3 2e8,5”)

The above line is the setup for my internal modem. Change it for
whatever you need. With this, the driver gets started with the new options
magically … at least until someone explains to me how the enum and boot
and autodetect stuff really works.

Although this had solved the problem of starting the devc-ser8250 driver
with my new options, my internal modem still doesn’t work. When I test it
with qtalk (e.g. qtalk -m /dev/ser3), I can write to the port (atdt for
example does take the phone line off the hook) but it seems that I cannot
read anything from that com-port.

If anyone has any idea… I’ll welcome them.

Marc Lupien <marclupien@hotmail.com> wrote:

I was working on a similar problem yesterday and found the following which
might interrest you. By the way, I did not figured out the enum scheme yet
either but I managed to tweak it in a way so I can add new options to
devc-ser8250 that are applied automatically at startup…

  1. the file /etc/system/enum/devices/char seems to be the place where the
    driver is started, if you look at it, you’ll see the devc-ser8250 along with
    what seems to be a reference to a macro named $SER_OPTIONS. Though I think
    that this file should not be modified directly…

  2. the file /etc/system/enum/include/block seems to be the proper place to
    add new macro definition so I added the following line to it (BTW, I’m
    writing this from memory since I currently on my W95 system and I am too
    lazy to reboot into RTP just to get a copy of this right, but any way, look
    at the syntax under the enum-device utility documentation… you’ll be able
    to figure out)
    set(SER_OPTIONS, “-u3 2e8,5”)

I used to ask the guy who wrote enum-device, he suggest the “right” way,
is create a “/etc/system/enum/include/char”, and put that line in it.
In fact, ANY file (even a block~) under /etc/system/enum/include will
be loaded/processed.

The above line is the setup for my internal modem. Change it for
whatever you need. With this, the driver gets started with the new options
magically … at least until someone explains to me how the enum and boot
and autodetect stuff really works.

Although this had solved the problem of starting the devc-ser8250 driver
with my new options, my internal modem still doesn’t work. When I test it
with qtalk (e.g. qtalk -m /dev/ser3), I can write to the port (atdt for
example does take the phone line off the hook) but it seems that I cannot
read anything from that com-port.

If anyone has any idea… I’ll welcome them.

If you do a “pidin arg | grep devc-ser8250”, does it started as you espect?
If you slay devc-ser8250, start it by hand (devc-ser8250 -u1 xx,xx -u2 xx,xx -u3 xx,xx)
Is it working?
Is it possiable that your modem is not in ECHO mode, so “at” didn’t return
a “OK” ?

-xtang

thanks for your input, I appreciate,
“Xiaodan Tang” <xtang@ottawa.com> wrote in message
news:8rm8bi$nqe$1@nntp.qnx.com

I used to ask the guy who wrote enum-device, he suggest the “right” way,
is create a “/etc/system/enum/include/char”, and put that line in it.
In fact, ANY file (even a block~) under /etc/system/enum/include will
be loaded/processed.

All right…

If you do a “pidin arg | grep devc-ser8250”, does it started as you
espect?
If you slay devc-ser8250, start it by hand (devc-ser8250 -u1 xx,xx -u2
xx,xx -u3 xx,xx)

Yes, it has the rights arguments,

Is it working?

No. Same behaviour when I start it manually (under root of course).

Is it possiable that your modem is not in ECHO mode, so “at” didn’t return
a “OK” ?

I tried sending these commands with no success. As stated earlier, I know
the modem receives the commands when I start ‘qtalk -m /dev/ser3’ because if
I type the command to change the speaker’s volume and then I type ATDT, I
hear the modem take the phone off the hook and the speaker has the proper
audio level (none, low, medium, high). I tried typing the verbose and echo
commands but no answer.

I’m wondering if there is an IRQ conflict somewhere but my modem is working
very well in W95 AND QNX4 and Linux. By the way, does some know if there is
a command that shows the IRQ lines used by the different drivers in the
system ? something like the old ‘sin irq’ on QNX4 ?

From reading all over the newsgroups, it seems I’m the only one with similar
problem. That suggests me that either something bizarre with my modem or
some other thing in my config is not what I think. Il try changing my modem
address and IRQ.

Thanks