Friends,
I have never seen / used UNIX or LINUX, so, this is all very new to me.
I do like QNX, however, I am having a bit of trouble with the modem 
When
I go in to the network to configure my modem, it detects it at /dev/ser1
(COM1), well, my modem is on COM2, so I went in to the terminal and typed in
qtalk -m /dev/ser1 and it says there was a modem, but most of the stuff in
there was disable, when I changed the 1 to a 2, no modem was found. When I
create the dialer and used /dev/ser1, it locks the mouse and never dials,
nothing happens. My modem (as far as I know) is a real modem (Zoom Internal
V90 faxmodem) It has a lucent chipset (this is not the issue!) but it’s not
a winmodem. I have searched the KB, and there was an article about making a
rc.local file, I did that, didn’t work. I guess what I am trying to say is,
is it my modem, is my modem not supported, or is this a bug? I’m hopeing in
the next version (whenever that is) my issue will hopefully be solved 
If
anyone can help, that would be great, if anyone had the same issue as I did,
and fixed it, please let me know, thanks!
Mike.
Hi Michael,
There wasn’t any modem detection of internal modems in the Sept 26th
release of the RTP. If you know your base address and IRQ for the card
then login in as the root user and run a new copy of devc-ser8250 with
the base address and the IRQ.
/sbin/devc-ser8250 -u 0xBase_Address, IRQ
However if the modem is either a win modem (which you mentioned it is
not) this won’t work. Or if this still doesn’t work then it may be
caused by an inproper initalization of the modem. If thats the case you
can try booting to Windows and checking the base address(port) and IRQ
under there and retry it again in QNX with the new IRQ and port.
Also make sure that the modem is not PCI.
Take care!
Erick.
Michael Abson <mabson_msp@msn.com> wrote:
Friends,
I have never seen / used UNIX or LINUX, so, this is all very new to me.
I do like QNX, however, I am having a bit of trouble with the modem > > When
I go in to the network to configure my modem, it detects it at /dev/ser1
(COM1), well, my modem is on COM2, so I went in to the terminal and typed in
qtalk -m /dev/ser1 and it says there was a modem, but most of the stuff in
there was disable, when I changed the 1 to a 2, no modem was found. When I
create the dialer and used /dev/ser1, it locks the mouse and never dials,
nothing happens. My modem (as far as I know) is a real modem (Zoom Internal
V90 faxmodem) It has a lucent chipset (this is not the issue!) but it’s not
a winmodem. I have searched the KB, and there was an article about making a
rc.local file, I did that, didn’t work. I guess what I am trying to say is,
is it my modem, is my modem not supported, or is this a bug? I’m hopeing in
the next version (whenever that is) my issue will hopefully be solved > > If
anyone can help, that would be great, if anyone had the same issue as I did,
and fixed it, please let me know, thanks! >
Mike.
Erick,
I tried what you suggested, and I still couldn’t get anything to work
unfortunately I noticed that QNX doesn’t even detect /dev/ser2, only
/dev/ser1 (COM1 - My Mouse). I don’t have a PCI modem. I couldn’t really
try init strings, because of the fact that COM2 wasn’t detected. I went in
to my BIOS and changed some things, but nothing I did allowed QNX to detect
my COM2 port. When I tried the /sbin command you suggested, the terminal
window didn’t execute anything, it kinda froze actually, I had exit the
window. If only I could get QNX to detect my COM2! Lol. When I went in to
the /dev folder, only ser1 was listed, I’m all out of ideas. Here is
something interesting though. That 1.44MB demo that QNX has, that allows
one to access the net without a HDD, well, I installed that, the program did
actually dectect my modem on COM2, I even got online, but I couldn’t surf
anywhere (MSN must be one of the ISP’s that doesn’t work correctly with the
software?). Thanks for the help though, I really did appreciate the help
Mike.
Hi Michael,
I think you are almost there, try the following:
-
the -u option by default is unit #1, meaning serial port 1. Try changing
this to -u2.
-
make sure that when you specify the base address, that you have 0x in it.
e.g. devc-ser8250 -u2 0x2f8,3 &
Once you have this you can put this into a startup script so you won’t have
to type this each time you boot into QNX.
To do this follow this link:
http://qdn.qnx.com/support/bok/solution.qnx?10121
Good luck!
Erick.
Michael Abson <mabson_msp@email.msn.com> wrote:
Erick,
I tried what you suggested, and I still couldn’t get anything to work
unfortunately > > I noticed that QNX doesn’t even detect /dev/ser2, only
/dev/ser1 (COM1 - My Mouse). I don’t have a PCI modem. I couldn’t really
try init strings, because of the fact that COM2 wasn’t detected. I went in
to my BIOS and changed some things, but nothing I did allowed QNX to detect
my COM2 port. When I tried the /sbin command you suggested, the terminal
window didn’t execute anything, it kinda froze actually, I had exit the
window. If only I could get QNX to detect my COM2! Lol. When I went in to
the /dev folder, only ser1 was listed, I’m all out of ideas. Here is
something interesting though. That 1.44MB demo that QNX has, that allows
one to access the net without a HDD, well, I installed that, the program did
actually dectect my modem on COM2, I even got online, but I couldn’t surf
anywhere (MSN must be one of the ISP’s that doesn’t work correctly with the
software?). Thanks for the help though, I really did appreciate the help >
Mike.