Trident or V2 ? - Was: DOS App AUTOEXEC loader so VESA drive

Followed the instructions. output of sin shows procnto
I assume that means SMP didn’t take? Everything from
RedHat 7.1, SuSE 7.0 Pro, Win2K, and even BeOS 5.0
see both processors. am I doing something wrong?

I did :

mkifs -vv /boot/build/qnxbasesmp.build /.smpboot
cp /.boot /.save.boot
cp /.altboot /.save.altboot
cp /.smpboot /.boot
cp /.save.boot /.altboot

Basically, smpkernel to copied to booting kernel copied to altboot



Tony

Oh, system specifics:

RioWorks PDVIA-LS dual slot-1 (integrated Intel 82559 10/100 ether,
integrated dual channel ncr/LSI 53C1010-66 UWSCSI3)

VIA Apollo 133A Chipset
Dual P3/500, Katmai core
256MB PC-133 DIMM, Micron
IBM 13.6GB ATA66 drive


also, there anything in RTP equivalent to BSD/Linux’s /proc/cpuinfo, or
dmesg, hell, even /var/log/messages would suffice?!?!?


Tony
“Tony Mori” <tonym@compusource.net> wrote in message
news:9f4ued$29l$1@inn.qnx.com

Followed the instructions. output of sin shows procnto
I assume that means SMP didn’t take? Everything from
RedHat 7.1, SuSE 7.0 Pro, Win2K, and even BeOS 5.0
see both processors. am I doing something wrong?

I did :

mkifs -vv /boot/build/qnxbasesmp.build /.smpboot
cp /.boot /.save.boot
cp /.altboot /.save.altboot
cp /.smpboot /.boot
cp /.save.boot /.altboot

Basically, smpkernel to copied to booting kernel copied to altboot



Tony

Tony Mori <tonym@compusource.net> wrote:

also, there anything in RTP equivalent to BSD/Linux’s /proc/cpuinfo, or
dmesg, hell, even /var/log/messages would suffice?!?!?

Yeah, the baby is called pidin. Try running “pidin in”. On my
SMP test machine…

cdm@x86dual → pidin in
CPU:X86 Processors:2 FreeMem:111Mb/127Mb BootTime:May 31 03:12:31 GMT 2001
Processor1: 586 Pentium (P54C) Stepping 12 166Mhz FPU
Processor2: 586 Pentium (P54C) Stepping 12 167Mhz FPU

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

“Chris McKillop” <cdm@qnx.com> wrote in message
news:9f51c1$l9t$1@nntp.qnx.com

Tony Mori <> tonym@compusource.net> > wrote:

also, there anything in RTP equivalent to BSD/Linux’s /proc/cpuinfo, or
dmesg, hell, even /var/log/messages would suffice?!?!?


Yeah, the baby is called pidin. Try running “pidin in”. On my
SMP test machine…

cdm@x86dual → pidin in
CPU:X86 Processors:2 FreeMem:111Mb/127Mb BootTime:May 31 03:12:31 GMT 2001
Processor1: 586 Pentium (P54C) Stepping 12 166Mhz FPU
Processor2: 586 Pentium (P54C) Stepping 12 167Mhz FPU

Thanks! Actually, when I got home, rebooted out of Win2K Pro, and into RTP,
and voila!
There’s 2 “cpu” symbols on the bottom right, similar to BeOS’ layout in
‘Pulse’. Don’t know
what happened, but it sees both now.


Tony

hey guys im just wondering, is there a QNX driver for the DFE530TX ? or
does
it come with the iso, because i wasnt able to configure my network because
it didnt see en0 or what ever it says in that tiny little screen shot for
the configuration. my connection is static ip not dhcp so i know my
ip,gateway,and dns, ip’s are i cant find a place to put them in, so to
speak. btw i installed it under a windows partition, would that change
anything ?

Ibrahim Fazel Poor wrote:

hey guys im just wondering, is there a QNX driver for the DFE530TX ? or
does
it come with the iso, because i wasnt able to configure my network because
it didnt see en0 or what ever it says in that tiny little screen shot for
the configuration. my connection is static ip not dhcp so i know my
ip,gateway,and dns, ip’s are i cant find a place to put them in, so to
speak. btw i installed it under a windows partition, would that change
anything ?

Yes it is supported. devn-via-rhine.so is the driver.
You can start it by typing “io-net -dvia-rhine -ptcpip” in a shell.

If that doesn’t work take the Vendor and Device ID supplied by
typing “pci -v” in a shell and start the driver like this:
“io-net -dvia-rhine did=0xdevice id,vid0xvendor id -ptcpip”


Regards,

Anders Hasselqvist
hassel@acc.umu.se
http://good-deed.dhs.org/

Hi Ibrahim,

Please don’t cross post on the newgroups

Thanks

E.


Ibrahim Fazel Poor <irax@abac.com> wrote:

hey guys im just wondering, is there a QNX driver for the DFE530TX ? or
does
it come with the iso, because i wasnt able to configure my network because
it didnt see en0 or what ever it says in that tiny little screen shot for
the configuration. my connection is static ip not dhcp so i know my
ip,gateway,and dns, ip’s are i cant find a place to put them in, so to
speak. btw i installed it under a windows partition, would that change
anything ?

sure will do. :stuck_out_tongue:
“Hardware Support Account” <hw@qnx.com> wrote in message
news:9lbhko$npk$5@nntp.qnx.com

Hi Ibrahim,

Please don’t cross post on the newgroups

Thanks

E.


Ibrahim Fazel Poor <> irax@abac.com> > wrote:

hey guys im just wondering, is there a QNX driver for the DFE530TX ? or
does
it come with the iso, because i wasnt able to configure my network
because
it didnt see en0 or what ever it says in that tiny little screen shot
for
the configuration. my connection is static ip not dhcp so i know my
ip,gateway,and dns, ip’s are i cant find a place to put them in, so to
speak. btw i installed it under a windows partition, would that change
anything ?






\

thnx for the help. befor my sound worked, now it doesnt… its a onboard
soundcard intel p3 820 mobo ney help ?
“Anders Hasselqvist” <hassel@acc.umu.se> wrote in message
news:3B793C31.F962EFC4@acc.umu.se

Ibrahim Fazel Poor wrote:

hey guys im just wondering, is there a QNX driver for the DFE530TX ? or
does
it come with the iso, because i wasnt able to configure my network
because
it didnt see en0 or what ever it says in that tiny little screen shot
for
the configuration. my connection is static ip not dhcp so i know my
ip,gateway,and dns, ip’s are i cant find a place to put them in, so to
speak. btw i installed it under a windows partition, would that change
anything ?

Yes it is supported. devn-via-rhine.so is the driver.
You can start it by typing “io-net -dvia-rhine -ptcpip” in a shell.

If that doesn’t work take the Vendor and Device ID supplied by
typing “pci -v” in a shell and start the driver like this:
“io-net -dvia-rhine did=0xdevice id,vid0xvendor id -ptcpip”


Regards,

Anders Hasselqvist
hassel@acc.umu.se
http://good-deed.dhs.org/

Another EMACS and/or Sun user?

http://staff.qnx.com/~cdm/mkkbd

Thanks a lot!! I got it.
I hope that ‘mkkbd’ will be contained again in the next release.

n2kra@orn.com <n2kra@orn.com> wrote:

Another EMACS and/or Sun user?

Neither of them, but I prefer the arrangement.

Thanks again.

---- Toshio KATAYAMA

You can try starting the driver manually and see if that helps.


Regards,
Dave B.

Andreas Heinz wrote:

Hello.
I’ve got a logitech-3-botton-wheel-mouse an usb-keyboard.
The keyboard works, but the mouse seems not to be detected by the OS.
usb -vvv shows nothing but ‘no such device’.
What’s the fix???
Is there a workaround?
Help is appreciated.
Thanx a lot
Andi
A supplement:

Tried something from chat.
Now mousepointer appears, but no moving.
Keyboard works , but only in Photon.
Here are the steps I have done:

  1. add /sbin/devu-uhci &
    /sbin/devu-mouse &
    waitfor /dev/usbmouse0
    /sbin/devu-kbd &
    waitfor /dev/usbkbd0
    to
    /etc/rc.d/rc.local
    and
    chmod 777 to make it nice and executable.
  2. add kbd -R fd -d/dev/usbkbd0
    msoft fd -d/dev/usbmouse0
    to
    /etc/system/trap/input.localhost
    (localhost is still my hostname)

Now here’s the output from usb -vv :

Device Adress : 1
Vendor :0x60b (SOLIDYEAR)
Produkt :0x2101 (SOLIDYEAR USB)
Device Release :r2.00
Class :0x00 (Independant per Interface)
Max PacketSize :8
Configurations :1
Configuration :1
Attributes :0xa0 (Bus-Powered, Remote-wakeup)
Max Power :100mA
Interface :1/0(ps2mouse)
Class :0x03(HID)
Subclass :0x01 (Boot interface
Protocol :0x02(Mouse)


Device Adress :2
Vendor :0x046d (Logitech)
Product : 0xc001 (USB Mouse)
Device Release :r4.00
Class :0x00 (Independant per Interface)
Max PacketSize :8
Configurations :1
Configuration :1
Attributes :0xa0 (Bus-Powered,Remote-wakeup)
MaxPower :50mA
Interfaces :1
Interface :0/0
Class :0x03(HID)
Subclass :0x01 (Boot Interface)
Protocol :0x02 (Mouse)


end of ‘usb -vv’

I tested if both devices are in /dev
and really: /dev/usbmouse0, /dev/usbkbd0 and /dev/kbd exists.


The issues from ‘inputtrap -vv’ are:

Probing :keyboard
/dev/kbd exists, using …
Probing :ps2
Probing:sermouse
Attempting PnP comm enumeration on /dev/ser1
comm enumeration failed on /dev/ser1

Attempting PnP comm enumeration on /dev/ser2
comm enumeration failed on /dev/ser2

Hi Andreas,
fd -d/dev/usbkbd0
Make certain that the input.{host} info is on the same line

E.g.

kbd -R fd -d/dev/usbkbd0 msoft fd -d/dev/usbmouse0

Regards,

Erick.



Andreas Heinz <andi@andreasheinz.com> wrote:

Andreas Heinz wrote:

Hello.
I’ve got a logitech-3-botton-wheel-mouse an usb-keyboard.
The keyboard works, but the mouse seems not to be detected by the OS.
usb -vvv shows nothing but ‘no such device’.
What’s the fix???
Is there a workaround?
Help is appreciated.
Thanx a lot
Andi
A supplement:
Tried something from chat.
Now mousepointer appears, but no moving.
Keyboard works , but only in Photon.
Here are the steps I have done:

  1. add /sbin/devu-uhci &
    /sbin/devu-mouse &
    waitfor /dev/usbmouse0
    /sbin/devu-kbd &
    waitfor /dev/usbkbd0
    to
    /etc/rc.d/rc.local
    and
    chmod 777 to make it nice and executable.
  2. add kbd -R fd -d/dev/usbkbd0
    msoft fd -d/dev/usbmouse0
    to
    /etc/system/trap/input.localhost
    (localhost is still my hostname)

Now here’s the output from usb -vv :

Device Adress : 1
Vendor :0x60b (SOLIDYEAR)
Produkt :0x2101 (SOLIDYEAR USB)
Device Release :r2.00
Class :0x00 (Independant per Interface)
Max PacketSize :8
Configurations :1
Configuration :1
Attributes :0xa0 (Bus-Powered, Remote-wakeup)
Max Power :100mA
Interface :1/0(ps2mouse)
Class :0x03(HID)
Subclass :0x01 (Boot interface
Protocol :0x02(Mouse)



Device Adress :2
Vendor :0x046d (Logitech)
Product : 0xc001 (USB Mouse)
Device Release :r4.00
Class :0x00 (Independant per Interface)
Max PacketSize :8
Configurations :1
Configuration :1
Attributes :0xa0 (Bus-Powered,Remote-wakeup)
MaxPower :50mA
Interfaces :1
Interface :0/0
Class :0x03(HID)
Subclass :0x01 (Boot Interface)
Protocol :0x02 (Mouse)



end of ‘usb -vv’

I tested if both devices are in /dev
and really: /dev/usbmouse0, /dev/usbkbd0 and /dev/kbd exists.



The issues from ‘inputtrap -vv’ are:

Probing :keyboard
/dev/kbd exists, using …
Probing :ps2
Probing:sermouse
Attempting PnP comm enumeration on /dev/ser1
comm enumeration failed on /dev/ser1

Attempting PnP comm enumeration on /dev/ser2
comm enumeration failed on /dev/ser2

alain.bonnefoy@icbt.com sed in <3DE47B0C.70305@icbt.com>

I don’t understand how env vars are inherited!

I have to export the TERMINFO env var.
I tried to export it in /etc/rc.d/rc.sysinit, /etc/rc.d/rc.local, no
way! when I’m in photon and launch a shell, TERMINFO doesn’t exist!

I don’t want to put in hundreds of profiles, shell rc or I don’t know
which private init file!

export TERMINFO=whatever
works perfectly even in /etc/rc.d/rc.local on my installation.


see ksh(1), tinit(1), diskboot(1) for more info.

kabe

This is being copied from qdn.public.neutrino.
I guess no one looks there.


I’m starting to port code from QNX4 to QNX6. So far, I’m still writing
very simply stuff to prove that my techniques are correct. And I don’t
understand what I’m seeing.

I have a server process that waits for a message. When it receives that
message it displays if and replies to it. How much simpler can you get?

I then wrote a simple client to test it. They both worked, until I
also ran psin to monitor what was going on. The scenario is as follows.

I start my server.
I start psin
I start my client. It displays some connection information.
It then sleeps for 20 seconds via sleep(20);
I go to the psin console and do a Ctrl-R to refresh the screen.
{Goofey stuff happens}
After 20 seconds, the client MsgSend()s to the server.
The server replies.
The client ends.

Both client and server are being run from a pterm. They are text mode
non-photon apps.

The Goofey stuff is that strange graphical character appear on the
screen. They appear WHEN I do the refresh in psin. Once they appear
the pterms will no longer display normal text, BUT they DO appear
to display digits appropriately when their supposed to. But letters
(a-x, A-Z) come out as graphical characters.

Slaying the pterm and reloading it does go back to normal.

I can run my tests 1000 times without doing a refresh in psin and the
pterm won’t do anything strange or unexpected.

What is psin doing to my program and what should I be doing to deal
with it properly?

It feels like my server is getting a messaeg like a ‘sin ve’ message in
QNX4 and just doesn’t know what to do with it. BUT even if that were
the case, why does it display any graphical crap on te screen?


Brian B <BBarcley@everrest.net> wrote:

I have confirmed that me server is receiving 3 messages from psin.
They are all coming from psin/thread 1 coid/11. And the lengths
are 60, 16, and 4 bytes respectivly.

Does anyone know WHY this is happening?

My server is receiving 3 messages from psin when psin does a refresh,
Ctrl-R. It doesn’t seam to send any messages when it is first loaded.

Also, what SHOULD my server do to reply to these messages?


Brian B <BBarcley@everrest.net> wrote:

Brian B <> BBarcley@everrest.net> > wrote:
I have confirmed that me server is receiving 3 messages from psin.
They are all coming from psin/thread 1 coid/11. And the lengths
are 60, 16, and 4 bytes respectivly.

Does anyone know WHY this is happening?

My server is receiving 3 messages from psin when psin does a refresh,
Ctrl-R. It doesn’t seam to send any messages when it is first loaded.

Also, what SHOULD my server do to reply to these messages?

This is what I am consistantly receiving.

server1: SenderPid=32698415, SenderTid=1, SenderCoid=11, SenderLen=60, RecvLen=60
server1: The message was:
15 01 3C 00 00 00 00 00 A6 7F 04 08 2B 30 F4 01 …<… …+0…
03 00 00 00 01 00 00 00 02 00 00 40 03 00 00 00 …@…
05 00 00 00 06 00 00 00 09 00 00 00 53 59 53 4E …SYSN
41 4D 45 3D 6E 74 6F 00 2E 2F 62 69 AME=nto…/bi
server1: SenderPid=32698415, SenderTid=1, SenderCoid=11, SenderLen=16, RecvLen=16
server1: The message was:
0E 01 10 00 00 00 00 00 00 02 00 00 00 00 00 00 …
server1: SenderPid=32698415, SenderTid=1, SenderCoid=11, SenderLen=4, RecvLen=4
server1: The message was:
16 01 04 00 …

This is very consisent. The only variable seams to be that sometimes
the SenderCoid is 11 and sometimes it is 12. The pid is always that
of psin.

HELP!

#/** PhEDIT attribute block
#-11:16777215
#0:237:default:-3:-3:0
#237:3788:TextFont09:0:-1:0
#** PhEDIT attribute block ends (-0000140)**/

Brian B <BBarcley@everrest.net> wrote:

This is being copied from qdn.public.neutrino.
I guess no one looks there.

D’oh! I just replied there!

Cheers,
-RK


I’m starting to port code from QNX4 to QNX6. So far, I’m still writing
very simply stuff to prove that my techniques are correct. And I don’t
understand what I’m seeing.

I have a server process that waits for a message. When it receives that
message it displays if and replies to it. How much simpler can you get?

I then wrote a simple client to test it. They both worked, until I
also ran psin to monitor what was going on. The scenario is as follows.

I start my server.
I start psin
I start my client. It displays some connection information.
It then sleeps for 20 seconds via sleep(20);
I go to the psin console and do a Ctrl-R to refresh the screen.
{Goofey stuff happens}
After 20 seconds, the client MsgSend()s to the server.
The server replies.
The client ends.

Both client and server are being run from a pterm. They are text mode
non-photon apps.

The Goofey stuff is that strange graphical character appear on the
screen. They appear WHEN I do the refresh in psin. Once they appear
the pterms will no longer display normal text, BUT they DO appear
to display digits appropriately when their supposed to. But letters
(a-x, A-Z) come out as graphical characters.

Slaying the pterm and reloading it does go back to normal.

I can run my tests 1000 times without doing a refresh in psin and the
pterm won’t do anything strange or unexpected.

What is psin doing to my program and what should I be doing to deal
with it properly?

It feels like my server is getting a messaeg like a ‘sin ve’ message in
QNX4 and just doesn’t know what to do with it. BUT even if that were
the case, why does it display any graphical crap on te screen?


Brian B <> BBarcley@everrest.net> > wrote:
I have confirmed that me server is receiving 3 messages from psin.
They are all coming from psin/thread 1 coid/11. And the lengths
are 60, 16, and 4 bytes respectivly.

Does anyone know WHY this is happening?

My server is receiving 3 messages from psin when psin does a refresh,
Ctrl-R. It doesn’t seam to send any messages when it is first loaded.

Also, what SHOULD my server do to reply to these messages?


Brian B <> BBarcley@everrest.net> > wrote:
Brian B <> BBarcley@everrest.net> > wrote:
I have confirmed that me server is receiving 3 messages from psin.
They are all coming from psin/thread 1 coid/11. And the lengths
are 60, 16, and 4 bytes respectivly.

Does anyone know WHY this is happening?

My server is receiving 3 messages from psin when psin does a refresh,
Ctrl-R. It doesn’t seam to send any messages when it is first loaded.

Also, what SHOULD my server do to reply to these messages?

This is what I am consistantly receiving.

server1: SenderPid=32698415, SenderTid=1, SenderCoid=11, SenderLen=60, RecvLen=60
server1: The message was:
15 01 3C 00 00 00 00 00 A6 7F 04 08 2B 30 F4 01 …<… …+0…
03 00 00 00 01 00 00 00 02 00 00 40 03 00 00 00 …@…
05 00 00 00 06 00 00 00 09 00 00 00 53 59 53 4E …SYSN
41 4D 45 3D 6E 74 6F 00 2E 2F 62 69 AME=nto…/bi
server1: SenderPid=32698415, SenderTid=1, SenderCoid=11, SenderLen=16, RecvLen=16
server1: The message was:
0E 01 10 00 00 00 00 00 00 02 00 00 00 00 00 00 …
server1: SenderPid=32698415, SenderTid=1, SenderCoid=11, SenderLen=4, RecvLen=4
server1: The message was:
16 01 04 00 …

This is very consisent. The only variable seams to be that sometimes
the SenderCoid is 11 and sometimes it is 12. The pid is always that
of psin.

HELP!

#/** PhEDIT attribute block
#-11:16777215
#0:237:default:-3:-3:0
#237:3788:TextFont09:0> :-1:> 0
#** PhEDIT attribute block ends (-0000140)**/


Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.