I have an ISA, nonPNP, internal with jumpers.
I’ve used BeOS, linux(wvdial) and windows on this modem. It seems that they
all connected to the modem to the ISP fine except QNX. I pulled the modem 4
times to flip the jumpers and messed with it. I’ve used /sbin/devc-ser8250
number of times. My config is -u1 3e8,4 and it seems that QNX still can’t
find my modem.
I talked to people on IRC (irc.qnxstart.com and efnet) they dun have a clue.
I seriously dun wanna go back to linux.
Sakui
Denise LeMay <iceviolet@earthlink.net> wrote:
I have an ISA, nonPNP, internal with jumpers.
I’ve used BeOS, linux(wvdial) and windows on this modem. It seems that they
all connected to the modem to the ISP fine except QNX. I pulled the modem 4
times to flip the jumpers and messed with it. I’ve used /sbin/devc-ser8250
number of times. My config is -u1 3e8,4 and it seems that QNX still can’t
find my modem.I talked to people on IRC (irc.qnxstart.com and efnet) they dun have a clue.
I seriously dun wanna go back to linux.
It seemed to me that there was still a potential problem with the
enumerators detecting the internal modems (this problem might be
corrected now … so I might be providing false hope). Did you
kill the previous inistance of the serial driver that started
when the system started?
Something along the lines of:
Thomas
Well, I used the slay command, but not the -f switch command.
i used the enum-legacy and it got nothing.
my question is there gonna be an update real soon to update the modem
problem? if not i’m gonna switch back to linux. I wanna give a chance to
this wonderful OS. Graphically, this is better than beos and windows and
linux (IMHO).
btw, when I “su” it seem that the paths are screwed up. how can i edit the
file that load this stuff at bootup?
Sakui
Thomas Fletcher wrote in message <960scb$2i3$1@nntp.qnx.com>…
Denise LeMay <> iceviolet@earthlink.net> > wrote:
I have an ISA, nonPNP, internal with jumpers.I’ve used BeOS, linux(wvdial) and windows on this modem. It seems that
they
all connected to the modem to the ISP fine except QNX. I pulled the
modem 4
times to flip the jumpers and messed with it. I’ve used
/sbin/devc-ser8250
number of times. My config is -u1 3e8,4 and it seems that QNX still
can’t
find my modem.I talked to people on IRC (irc.qnxstart.com and efnet) they dun have a
clue.
I seriously dun wanna go back to linux.It seemed to me that there was still a potential problem with the
enumerators detecting the internal modems (this problem might be
corrected now … so I might be providing false hope). Did you
kill the previous inistance of the serial driver that started
when the system started?Something along the lines of:
slay -f devc-ser8250
/sbin/devc-ser8250 -u1 3e8,4
Thomas
On 9 Feb 2001 13:46:51 GMT, Thomas Fletcher <thomasf@qnx.com> wrote:
Denise LeMay <> iceviolet@earthlink.net> > wrote:
I have an ISA, nonPNP, internal with jumpers.SNIP
Did you
kill the previous inistance of the serial driver that started
when the system started?Something along the lines of:
slay -f devc-ser8250
/sbin/devc-ser8250 -u1 3e8,4
I’m also having a similar problem (ser3,2e8,3). I created the
rc.local file and put the expected commands. I did not use the -f
option on slay but it did show that it created the serial3 device.
However when I used the slay command, it removed the ser1 and ser2
devices. I do not use the ser1 (yet) but I will have a need for the
ser2. So I removed the slay command. I’ll try it with the slay
command and see how it goes. How do I have the ser2 and ser3 devices
up at the same time?
Sorry to but into this thread, but I’m hoping for a resolution also.
Thanks
Dave E.
Thomas
su -
instead of just plain su, runs /root/.profile and stuff
Denise LeMay <iceviolet@earthlink.net> wrote in message
news:9613gq$5eq$1@inn.qnx.com…
…serial probs…
btw, when I “su” it seem that the paths are screwed up. how can i edit
the
file that load this stuff at bootup?Sakui
This was the answer I got from someone earlier to the same ? Just type
devc-ser8250 -u3 3e8,4 & this should work ,you can also create a
rc.local file and this will be started at boot up. The -u3 is the port so
you’ll have to set to the port you need.
Bill
“David E. Edwards” wrote:
On 9 Feb 2001 13:46:51 GMT, Thomas Fletcher <> thomasf@qnx.com> > wrote:
Denise LeMay <> iceviolet@earthlink.net> > wrote:
I have an ISA, nonPNP, internal with jumpers.SNIP
Did you
kill the previous inistance of the serial driver that started
when the system started?Something along the lines of:
slay -f devc-ser8250
/sbin/devc-ser8250 -u1 3e8,4
I’m also having a similar problem (ser3,2e8,3). I created the
rc.local file and put the expected commands. I did not use the -f
option on slay but it did show that it created the serial3 device.
However when I used the slay command, it removed the ser1 and ser2
devices. I do not use the ser1 (yet) but I will have a need for the
ser2. So I removed the slay command. I’ll try it with the slay
command and see how it goes. How do I have the ser2 and ser3 devices
up at the same time?
Sorry to but into this thread, but I’m hoping for a resolution also.
Thanks
Dave E.Thomas
I tried it - still no results - not even a glimmer from my modem. I
have sound turned on but no sound out. - nothing. Just ATZ on the
terminal window and then “connection Failed”
Dave E.
On Fri, 09 Feb 2001 15:38:34 -0600, bcmc@sk.sympatico.ca wrote:
This was the answer I got from someone earlier to the same ? Just type
devc-ser8250 -u3 3e8,4 & this should work ,you can also create a
rc.local file and this will be started at boot up. The -u3 is the port so
you’ll have to set to the port you need.Bill
“David E. Edwards” wrote:On 9 Feb 2001 13:46:51 GMT, Thomas Fletcher <> thomasf@qnx.com> > wrote:
Denise LeMay <> iceviolet@earthlink.net> > wrote:
I have an ISA, nonPNP, internal with jumpers.SNIP
Did you
kill the previous inistance of the serial driver that started
when the system started?Something along the lines of:
slay -f devc-ser8250
/sbin/devc-ser8250 -u1 3e8,4
I’m also having a similar problem (ser3,2e8,3). I created the
rc.local file and put the expected commands. I did not use the -f
option on slay but it did show that it created the serial3 device.
However when I used the slay command, it removed the ser1 and ser2
devices. I do not use the ser1 (yet) but I will have a need for the
ser2. So I removed the slay command. I’ll try it with the slay
command and see how it goes. How do I have the ser2 and ser3 devices
up at the same time?
Sorry to but into this thread, but I’m hoping for a resolution also.
Thanks
Dave E.Thomas