Hi,
I’ve just installed QNX 6.1.0 on my old Pentium 200 laptop with 16MB ram
since I was under the impression QNX could be scaled to work great on
older machines.
The thing is, photon eats up nearly all the ram, and a swapfile doesn’t
seem to help. AND the big problem is that pkg-installer crashes with
“bus error” or some kind of “…memory…” error while getting
repository data from either internet or the install cd. I have assumed
this has to do with the fact that I only have 16mb’s of ram (though I
might be wrong). I have tried slay:ing every unnecessary process, shelf,
pwm etc leaving only a terminal running under photon and the memory
hungry io-graphics (1mb) but I still get the same errors.
I untared the patchA in linux and sent it to the laptop and overwrote
the old files (including pkg-installer) but this didn’t seem to help at all.
Please help me because I want to play with compilers on it, and for that
I need to be able to use pkg-installer to install them =(.
Hi,
I’ve just installed QNX 6.1.0 on my old Pentium 200 laptop with 16MB ram
since I was under the impression QNX could be scaled to work great on
older machines.
QNXRTP should work fine on your laptop without Photon . And I believe it can work with Photon too
Try to reduce cache size for hard disk driver, it uses too much memory by default. Read carefully
docs for devb-eide and io-blk.so (you can find html docs under /usr/help/…). Try to slay
devb-eide and restart with new arguments. After you find optimal cache size, you can want to write
arguments of devb-eide in the file /etc/system/enum/include/block
Hi,
I’ve just installed QNX 6.1.0 on my old Pentium 200 laptop with 16MB ram
since I was under the impression QNX could be scaled to work great on
older machines.
QNXRTP should work fine on your laptop without Photon > > . And I believe it can work with Photon too
Try to reduce cache size for hard disk driver, it uses too much memory by default. Read carefully
docs for devb-eide and io-blk.so (you can find html docs under /usr/help/…). Try to slay
devb-eide and restart with new arguments. After you find optimal cache size, you can want to write
arguments of devb-eide in the file /etc/system/enum/include/block
Best regards,
Eduard.
Thanks for the tips. I have tried messing with the cache and alloc
settings as much as possible, but still devb-eide’s memory footprint
hasn’t changed at all and “sin args|pipe more” doesn’t show my
alloc=xxk,cache=xxk settings at all, should it be like that?
Also, fs-pkg eats as much or more ram than devb-eide, what is this
really used for? killing it kills my entire fs, but I thought this was
something used only by the pkg-installer?
Thanks for the tips. I have tried messing with the cache and alloc
settings as much as possible, but still devb-eide’s memory footprint
hasn’t changed at all and “sin args|pipe more” doesn’t show my
alloc=xxk,cache=xxk settings at all, should it be like that?
Sorry if I miss something. I will look deeply into this problem. I know in QRTP6.0 it required to
rebuild image. But I think it is not required in QRTP6.1. And I’m more familiar with “pidin”
command Is anybody who knows more about QRTP with small RAM configuration? I guess slaying and
restarting devb-eide is enough, maybe it’s wrong assumption.
Also, fs-pkg eats as much or more ram than devb-eide, what is this
really used for? killing it kills my entire fs, but I thought this was
something used only by the pkg-installer?
No. I don’t quite understand what is package file system (I cannot explain it). Simply don’t kill
it
Hi,
I’ve just installed QNX 6.1.0 on my old Pentium 200 laptop with 16MB ram
since I was under the impression QNX could be scaled to work great on
older machines.
QNXRTP should work fine on your laptop without Photon > > . And I believe it can work with Photon
too
Try to reduce cache size for hard disk driver, it uses too much memory by default. Read
carefully
docs for devb-eide and io-blk.so (you can find html docs under /usr/help/…). Try to slay
devb-eide and restart with new arguments. After you find optimal cache size, you can want to
write
arguments of devb-eide in the file /etc/system/enum/include/block
I’m sorry. The main conception was right, but I was wrong in details
Try the next way:
Edit the custom.build file. You’ll have to insert command to start devb-eide before diskboot
command and to put -xdevb-eide option for diskboot. See my custom.build file below
mkifs ./custom.build /.boot
shutdown
After reboot (press Esc and verify all steps if troubles occur)
7) # pidin mem |grep devb-eide
and # pidin arg |grep devb-eide
to verify memory usage by hard disk driver.
File “custom.build”
====================================
Best regards,
Eduard.
Thanks for the tips. I have tried messing with the cache and alloc
settings as much as possible, but still devb-eide’s memory footprint
hasn’t changed at all and “sin args|pipe more” doesn’t show my
alloc=xxk,cache=xxk settings at all, should it be like that?
Also, fs-pkg eats as much or more ram than devb-eide, what is this
really used for? killing it kills my entire fs, but I thought this was
something used only by the pkg-installer?
/proc/boot is placed in memory. I guess the comment gives a clearly explanation on it. During
bootup diskboot has devb-* files under /proc/boot/. No disk access yet, so drivers for hdd are
included to image. unlink_list removes these files at the end of bootup procedure. You could simply
remove extra drivers (SCSI) from image. I think it is a better idea . That’s because my build
file is standard build file (see /boot/build/qnxbasedma.build in your system) with minor change.
unlink_list is a QNXRTP 6.1 feature
Thanks Eduard, it’s hard to stay on top of these things…
Scott
ed1k wrote:
Hello Scott,
/proc/boot is placed in memory. I guess the comment gives a clearly explanation on it. During
bootup diskboot has devb-* files under /proc/boot/. No disk access yet, so drivers for hdd are
included to image. unlink_list removes these files at the end of bootup procedure. You could simply
remove extra drivers (SCSI) from image. I think it is a better idea > > . That’s because my build
file is standard build file (see /boot/build/qnxbasedma.build in your system) with minor change.
unlink_list is a QNXRTP 6.1 feature >