Have recently configured an Aeon board to boot from Disk on chip and am
having troubles getting the video to work. The same drivers on the same
board work with vesabios.ms and Pg.vga4 however, with the DOC it is not
working. Any thoughts??
Doug Rixmann
“Doug Rixmann” <rixmannd@rdsdata.com> wrote in message
news:9qktie$bso$1@inn.qnx.com…
Have recently configured an Aeon board to boot from Disk on chip and am
having troubles getting the video to work. The same drivers on the same
board work with vesabios.ms and Pg.vga4 however, with the DOC it is not
working. Any thoughts??
Are you sure the DOC has all the necessary files?
Doug Rixmann
The DOC has all the files (way too many if you ask me). We started off
limiting the files that we were putting on there until it didn’t work and
we then added everything and when it works, will take the other files
out.
When trying to run Photon or any other graphics related program, we are
getting vesabios stuck in a READY — state.
In article <9qlbn4$jc5$1@inn.qnx.com>, “Mario Charest”
<mcharest@voidzinformatic.com> wrote:
“Doug Rixmann” <> rixmannd@rdsdata.com> > wrote in message
news:9qktie$bso$> 1@inn.qnx.com> …
Have recently configured an Aeon board to boot from Disk on chip and am
having troubles getting the video to work. The same drivers on the same
board work with vesabios.ms and Pg.vga4 however, with the DOC it is not
working. Any thoughts??
Are you sure the DOC has all the necessary files?Doug Rixmann
“Doug Rixmann” <rixmannd@rdsdata.com> wrote in message
news:9qn22h$lf2$1@inn.qnx.com…
The DOC has all the files (way too many if you ask me). We started off
limiting the files that we were putting on there until it didn’t work and
we then added everything and when it works, will take the other files
out.When trying to run Photon or any other graphics related program, we are
getting vesabios stuck in a READY — state.
How are you coming to that conclusion ( via telnet?).
That strange, it’s my impression Pg.vga4 doesn’t depends
on any configuration files.
“Doug Rixmann” <> rixmannd@rdsdata.com> > wrote in message
news:9qn22h$lf2$> 1@inn.qnx.com> …
The DOC has all the files (way too many if you ask me). We started off
limiting the files that we were putting on there until it didn’t work and
we then added everything and when it works, will take the other files
out.When trying to run Photon or any other graphics related program, we are
getting vesabios stuck in a READY — state.
Do you have a correct .licenses file on the DOC? Is nameloc running?
The conclusion is via the network connection. It is networked into our
QNX network of nodes.
In article <9qn6k4$o4f$1@inn.qnx.com>, “Mario Charest”
<mcharest@clipzinformatic.com> wrote:
“Doug Rixmann” <> rixmannd@rdsdata.com> > wrote in message
news:9qn22h$lf2$> 1@inn.qnx.com> …
The DOC has all the files (way too many if you ask me). We started off
limiting the files that we were putting on there until it didn’t work
and we then added everything and when it works, will take the other
files out.When trying to run Photon or any other graphics related program, we are
getting vesabios stuck in a READY — state.
How are you coming to that conclusion ( via telnet?)That strange, it’s my impression Pg.vga4 doesn’t depends on any
configuration files.
Licenses file is correct. We had that issue but got around it. Update: we
have tracked down the problem to the memory address of the DOC. We are
booting from a HD and the DOC disabled through motherboard switches and
are able to start Photon. With the DOC enabled (but not mounted), we are unable to
start Photon.
In article Voyager.011018113219.182A@node1, “Pete DiMarco”
<peted@ifspurity.nospam.com> wrote:
“Doug Rixmann” <> rixmannd@rdsdata.com> > wrote in message
news:9qn22h$lf2$> 1@inn.qnx.com> …
The DOC has all the files (way too many if you ask me). We started
off limiting the files that we were putting on there until it didn’t
work and we then added everything and when it works, will take the
other files out.When trying to run Photon or any other graphics related program, we
are getting vesabios stuck in a READY — state.Do you have a correct .licenses file on the DOC? Is nameloc running?
- Pete
Do you have the latest DOC drivers? It is possible to use the DOC with
old drivers and the problems will not always be immediately apparent.
Latest QNX TrueFFS driver I beleive is version 4.2 (Fsys.diskonchip).
They are available from the M-Systems website.
Another thing to check is the DOC address settings. We used an Aaeon
board and found the manual listed the DOC addressing incorrectly,
(We use an Aaeon SBC-357/4M).
-Paul
Doug Rixmann wrote:
Licenses file is correct. We had that issue but got around it. Update: we
have tracked down the problem to the memory address of the DOC. We are
booting from a HD and the DOC disabled through motherboard switches and
are able to start Photon. With the DOC enabled (but not mounted), we are unable to
start Photon.In article Voyager.011018113219.182A@node1, “Pete DiMarco”
peted@ifspurity.nospam.com> > wrote:“Doug Rixmann” <> rixmannd@rdsdata.com> > wrote in message
news:9qn22h$lf2$> 1@inn.qnx.com> …
The DOC has all the files (way too many if you ask me). We started
off limiting the files that we were putting on there until it didn’t
work and we then added everything and when it works, will take the
other files out.When trying to run Photon or any other graphics related program, we
are getting vesabios stuck in a READY — state.Do you have a correct .licenses file on the DOC? Is nameloc running?
- Pete