I attempted to include devf-bigsur in my build file and it was not found
because it was not in the default search path. When I went to root to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsur
Should I just move one of these into the MKIFS_PATH?
Which one:-)
I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files to be in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy from
this drivers-2.1.3 directory?
Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was not found
because it was not in the default search path. When I went to root to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsurShould I just move one of these into the MKIFS_PATH?
Which one:-)
Looks like either the files where deleted from their installed directories,
or the package filesystem is not being used (or it is not using the “real”
filesystem you think it is).
The fact that your disk is showing under /fs seems to indicate that it is
not the primary disk. In which case fs-pkg is not “looking” at that disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so unless you
tweaked the configuration this is your problem.
Regards,
Joe
Joseph Witherspoon <jspoon@us.ibm.com> wrote in message
news:cpd3k6$3ef$1@inn.qnx.com…
I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files to be in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy from
this drivers-2.1.3 directory?Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was not found
because it was not in the default search path. When I went to root to
find, there were two version found:
: find . -name devf-bigsur/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsur
Should I just move one of these into the MKIFS_PATH?
Which one:-)
\
in looking at my 6.21 system, I have three entries, included the one where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver version. I
am guessing that maybe I should re-install or is it ok to just link to the
2.1.4 version for 6.30 QNX?
Joe Mammone wrote:
Looks like either the files where deleted from their installed directories,
or the package filesystem is not being used (or it is not using the “real”
filesystem you think it is).The fact that your disk is showing under /fs seems to indicate that it is
not the primary disk. In which case fs-pkg is not “looking” at that disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so unless you
tweaked the configuration this is your problem.Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …
I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files to be in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy from
this drivers-2.1.3 directory?Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was not found
because it was not in the default search path. When I went to root to
find, there were two version found:
: find . -name devf-bigsur/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsur
Should I just move one of these into the MKIFS_PATH?
Which one:-)
\
QNX 6.3.0 does not use the package filesystem, this is way when you access
your 6.2.1 disk you do not see /shle/sbin/devf-bigsur. In 6.2.1 /shle/sbin
is actually a virtual filesystem created by fs-pkg.
Why aren’t you using the 6.3.0 bigsur amanda BSP for 6.3.0 development? You
can download it from myQNX.
This way you’ll have the 6.3.0 flash driver for your 6.3.0 target rather
then running a 6.2.1 driver on 6.3.0 target.
Regards,
Joe
Joseph Witherspoon <jspoon@us.ibm.com> wrote in message
news:cpkls1$loe$1@inn.qnx.com…
in looking at my 6.21 system, I have three entries, included the one where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver version. I
am guessing that maybe I should re-install or is it ok to just link to the
2.1.4 version for 6.30 QNX?Joe Mammone wrote:
Looks like either the files where deleted from their installed
directories,
or the package filesystem is not being used (or it is not using the
“real”
filesystem you think it is).The fact that your disk is showing under /fs seems to indicate that it
is
not the primary disk. In which case fs-pkg is not “looking” at that
disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so unless
you
tweaked the configuration this is your problem.Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …
I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files to
be in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy
from
this drivers-2.1.3 directory?Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was not
found
because it was not in the default search path. When I went to root
to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsurShould I just move one of these into the MKIFS_PATH?
Which one:-)
\
I am sorry, I must have missed something… I reinstalled my 6.3.0 system
and got the same results (only appear under /fs and not under /shle/sbin
and still two versions of devf-bigsur). I also reinstalled the binary
6.3.0 bigusre-amanda BSP and that did not change anything. What step was
supposed to determine which version to use and put it under /shle/sbin?
Joe Mammone wrote:
QNX 6.3.0 does not use the package filesystem, this is way when you access
your 6.2.1 disk you do not see /shle/sbin/devf-bigsur. In 6.2.1 /shle/sbin
is actually a virtual filesystem created by fs-pkg.Why aren’t you using the 6.3.0 bigsur amanda BSP for 6.3.0 development? You
can download it from myQNX.
This way you’ll have the 6.3.0 flash driver for your 6.3.0 target rather
then running a 6.2.1 driver on 6.3.0 target.Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpkls1$loe$> 1@inn.qnx.com> …
in looking at my 6.21 system, I have three entries, included the one where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver version. I
am guessing that maybe I should re-install or is it ok to just link to the
2.1.4 version for 6.30 QNX?Joe Mammone wrote:
Looks like either the files where deleted from their installed
directories,
or the package filesystem is not being used (or it is not using the
“real”
filesystem you think it is).The fact that your disk is showing under /fs seems to indicate that it
is
not the primary disk. In which case fs-pkg is not “looking” at that
disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so unless
you
tweaked the configuration this is your problem.Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …
I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files to
be in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy
from
this drivers-2.1.3 directory?Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was not
found
because it was not in the default search path. When I went to root
to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsurShould I just move one of these into the MKIFS_PATH?
Which one:-)
\
Joseph,
You need to get the Flash Filesystem and Embedding TDK in order to get the flash driver for your 6.3.0 BSP.
Thanks,
-Jay.
Joseph Witherspoon wrote:
I am sorry, I must have missed something… I reinstalled my 6.3.0 system
and got the same results (only appear under /fs and not under /shle/sbin
and still two versions of devf-bigsur). I also reinstalled the binary
6.3.0 bigusre-amanda BSP and that did not change anything. What step was
supposed to determine which version to use and put it under /shle/sbin?Joe Mammone wrote:
QNX 6.3.0 does not use the package filesystem, this is way when you access
your 6.2.1 disk you do not see /shle/sbin/devf-bigsur. In 6.2.1 /shle/sbin
is actually a virtual filesystem created by fs-pkg.
Why aren’t you using the 6.3.0 bigsur amanda BSP for 6.3.0 development? You
can download it from myQNX.
This way you’ll have the 6.3.0 flash driver for your 6.3.0 target rather
then running a 6.2.1 driver on 6.3.0 target.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpkls1$loe$> 1@inn.qnx.com> …in looking at my 6.21 system, I have three entries, included the one where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver version. I
am guessing that maybe I should re-install or is it ok to just link to the
2.1.4 version for 6.30 QNX?Joe Mammone wrote:
Looks like either the files where deleted from their installeddirectories,
or the package filesystem is not being used (or it is not using the
“real”
filesystem you think it is).
The fact that your disk is showing under /fs seems to indicate that it
is
not the primary disk. In which case fs-pkg is not “looking” at that
disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so unless
you
tweaked the configuration this is your problem.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files tobe in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy
from
this drivers-2.1.3 directory?
Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was notfound
because it was not in the default search path. When I went to root
to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigsur/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigsur
Should I just move one of these into the MKIFS_PATH?
Which one:-)
\
Ahh…that’s right. Good call Jay.
-Joe
Jay Greig <greig@qnx.com> wrote in message news:cpkpbr$o7r$1@inn.qnx.com…
Joseph,
You need to get the Flash Filesystem and Embedding TDK in order to get the
flash driver for your 6.3.0 BSP.Thanks,
-Jay.Joseph Witherspoon wrote:
I am sorry, I must have missed something… I reinstalled my 6.3.0
system
and got the same results (only appear under /fs and not under /shle/sbin
and still two versions of devf-bigsur). I also reinstalled the binary
6.3.0 bigusre-amanda BSP and that did not change anything. What step
was
supposed to determine which version to use and put it under /shle/sbin?Joe Mammone wrote:
QNX 6.3.0 does not use the package filesystem, this is way when you
access
your 6.2.1 disk you do not see /shle/sbin/devf-bigsur. In 6.2.1
/shle/sbin
is actually a virtual filesystem created by fs-pkg.
Why aren’t you using the 6.3.0 bigsur amanda BSP for 6.3.0 development?
You
can download it from myQNX.
This way you’ll have the 6.3.0 flash driver for your 6.3.0 target rather
then running a 6.2.1 driver on 6.3.0 target.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpkls1$loe$> 1@inn.qnx.com> …in looking at my 6.21 system, I have three entries, included the one
where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver version.
I
am guessing that maybe I should re-install or is it ok to just link to
the
2.1.4 version for 6.30 QNX?Joe Mammone wrote:
Looks like either the files where deleted from their installeddirectories,
or the package filesystem is not being used (or it is not using the
“real”
filesystem you think it is).
The fact that your disk is showing under /fs seems to indicate that it
is
not the primary disk. In which case fs-pkg is not “looking” at that
disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so
unlessyou
tweaked the configuration this is your problem.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files tobe in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy
from
this drivers-2.1.3 directory?
Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was notfound
because it was not in the default search path. When I went to root
to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigs
ur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigs
urShould I just move one of these into the MKIFS_PATH?
Which one:-)
\
When I tried to download the Flash TDK, it said I needed another
license… Is that an extra cost item now? How do I find out how to get
the license? Thx.
Joe Mammone wrote:
Ahh…that’s right. Good call Jay.
-Joe
Jay Greig <> greig@qnx.com> > wrote in message news:cpkpbr$o7r$> 1@inn.qnx.com> …
Joseph,You need to get the Flash Filesystem and Embedding TDK in order to get the
flash driver for your 6.3.0 BSP.Thanks,
-Jay.Joseph Witherspoon wrote:
I am sorry, I must have missed something… I reinstalled my 6.3.0
system
and got the same results (only appear under /fs and not under /shle/sbin
and still two versions of devf-bigsur). I also reinstalled the binary
6.3.0 bigusre-amanda BSP and that did not change anything. What step
was
supposed to determine which version to use and put it under /shle/sbin?Joe Mammone wrote:
QNX 6.3.0 does not use the package filesystem, this is way when you
access
your 6.2.1 disk you do not see /shle/sbin/devf-bigsur. In 6.2.1
/shle/sbin
is actually a virtual filesystem created by fs-pkg.
Why aren’t you using the 6.3.0 bigsur amanda BSP for 6.3.0 development?
You
can download it from myQNX.
This way you’ll have the 6.3.0 flash driver for your 6.3.0 target rather
then running a 6.2.1 driver on 6.3.0 target.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpkls1$loe$> 1@inn.qnx.com> …in looking at my 6.21 system, I have three entries, included the one
where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver version.
I
am guessing that maybe I should re-install or is it ok to just link to
the
2.1.4 version for 6.30 QNX?Joe Mammone wrote:
Looks like either the files where deleted from their installeddirectories,
or the package filesystem is not being used (or it is not using the
“real”
filesystem you think it is).
The fact that your disk is showing under /fs seems to indicate that it
is
not the primary disk. In which case fs-pkg is not “looking” at that
disk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so
unlessyou
tweaked the configuration this is your problem.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …I found a similar situation with flashctl, except there is only one
version of it (drivers-2.1.3). I would have expected these files tobe in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to copy
from
this drivers-2.1.3 directory?
Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was notfound
because it was not in the default search path. When I went to root
to
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigs
ur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigs
urShould I just move one of these into the MKIFS_PATH?
Which one:-)
\
TDKs are separate products. You will need to contact your sales rep for
details on getting a TDK.
-Joe
Joseph Witherspoon <jspoon@us.ibm.com> wrote in message
news:cpsn66$q32$1@inn.qnx.com…
When I tried to download the Flash TDK, it said I needed another
license… Is that an extra cost item now? How do I find out how to get
the license? Thx.Joe Mammone wrote:
Ahh…that’s right. Good call Jay.
-Joe
Jay Greig <> greig@qnx.com> > wrote in message
news:cpkpbr$o7r$> 1@inn.qnx.com> …
Joseph,You need to get the Flash Filesystem and Embedding TDK in order to get
the
flash driver for your 6.3.0 BSP.Thanks,
-Jay.Joseph Witherspoon wrote:
I am sorry, I must have missed something… I reinstalled my 6.3.0
system
and got the same results (only appear under /fs and not under
/shle/sbin
and still two versions of devf-bigsur). I also reinstalled the
binary
6.3.0 bigusre-amanda BSP and that did not change anything. What
step
was
supposed to determine which version to use and put it under
/shle/sbin?Joe Mammone wrote:
QNX 6.3.0 does not use the package filesystem, this is way when you
access
your 6.2.1 disk you do not see /shle/sbin/devf-bigsur. In 6.2.1
/shle/sbin
is actually a virtual filesystem created by fs-pkg.
Why aren’t you using the 6.3.0 bigsur amanda BSP for 6.3.0
development?
You
can download it from myQNX.
This way you’ll have the 6.3.0 flash driver for your 6.3.0 target
rather
then running a 6.2.1 driver on 6.3.0 target.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpkls1$loe$> 1@inn.qnx.com> …in looking at my 6.21 system, I have three entries, included the
one
where
I expected to find it:
/shle/sbin/devf-bigsur and the size matches the 2.1.4 driver
version.
I
am guessing that maybe I should re-install or is it ok to just link
to
the
2.1.4 version for 6.30 QNX?Joe Mammone wrote:
Looks like either the files where deleted from their installeddirectories,
or the package filesystem is not being used (or it is not using
the“real”
filesystem you think it is).
The fact that your disk is showing under /fs seems to indicate
that itis
not the primary disk. In which case fs-pkg is not “looking” at
thatdisk. By
default fs-pkg will operate on the filesystem mounted at ‘/’, so
unlessyou
tweaked the configuration this is your problem.
Regards,
Joe
Joseph Witherspoon <> jspoon@us.ibm.com> > wrote in message
news:cpd3k6$3ef$> 1@inn.qnx.com> …I found a similar situation with flashctl, except there is only
one
version of it (drivers-2.1.3). I would have expected these files
tobe in
$QNX_TARGET/$PROCESSOR/sbin or something similar. Is it ok to
copyfrom
this drivers-2.1.3 directory?
Joseph Witherspoon wrote:
I attempted to include devf-bigsur in my build file and it was
notfound
because it was not in the default search path. When I went to
rootto
find, there were two version found:
: find . -name devf-bigsur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.3/shle/sbin/devf-bigs
ur
/fs/hd0-qnx4-2/pkgs/repository/qnx/os-se/drivers-2.1.4/shle/sbin/devf-bigs
urShould I just move one of these into the MKIFS_PATH?
Which one:-)
\