IS the ‘seedres’ utility still needed in RTP boot images? I don’t see it in newer systems.
What does/did it do? It doesn’t seem to be documented.
–
Bill Caroselli – Q-TPS Consulting
1-(626) 824-7983
qtps@earthlink.net
The seedres utility is there to read the PnP BIOS and assign resources
to procnto’s resource database (I/O ports, IRQs etc.). this was a
“temporary” utility written some time ago, but seems to have become
“permanent”! That is why there is no documentation on the utility.
It is still needed if you want drivers to assign non-conflicting resources.
Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
IS the ‘seedres’ utility still needed in RTP boot images? I don’t see it in newer systems.
What does/did it do? It doesn’t seem to be documented.
–
Bill Caroselli – Q-TPS Consulting
1-(626) 824-7983
qtps@earthlink.net
OK. Thanks Hugh.
I am working on CompactPCI/X86 hardware and 6.2.0 SE system. I’m building
my own boot image. It does boot, but . . .
If I include seedres I get an error at boot time that reads:
“Unable to allocate resource: Invalid argument”
I have confirmed that it is seedres that is doing this by moving it
around (changing the order) and using display_msg’s.
What is missing for seedres to do it’s thing without an error?
Also, if the BIOS screen has “PnP OS” turned off (mine does), is seedres
still required? Or is that what is causing te error?
Hugh Brown <hsbrown@qnx.com> wrote:
HB > The seedres utility is there to read the PnP BIOS and assign resources
HB > to procnto’s resource database (I/O ports, IRQs etc.). this was a
HB > “temporary” utility written some time ago, but seems to have become
HB > “permanent”! That is why there is no documentation on the utility.
HB > It is still needed if you want drivers to assign non-conflicting resources.
HB > Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
IS the ‘seedres’ utility still needed in RTP boot images? I don’t see it in newer systems.
What does/did it do? It doesn’t seem to be documented.
Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
OK. Thanks Hugh.
I am working on CompactPCI/X86 hardware and 6.2.0 SE system. I’m building
my own boot image. It does boot, but . . .If I include seedres I get an error at boot time that reads:
“Unable to allocate resource: Invalid argument”I have confirmed that it is seedres that is doing this by moving it
around (changing the order) and using display_msg’s.What is missing for seedres to do it’s thing without an error?
This is most probably caused by the PnP BIOS returning a value that
procnto does not agree with. If you start seedres with a ‘-v’ argument
you should see the values that it is trying to seed to the resource
database. You must start seedres before pci-bios and seedres must not
be started in the background.
Also, if the BIOS screen has “PnP OS” turned off (mine does), is seedres
still required? Or is that what is causing te error?Hugh Brown <> hsbrown@qnx.com> > wrote:
HB > The seedres utility is there to read the PnP BIOS and assign resources
HB > to procnto’s resource database (I/O ports, IRQs etc.). this was a
HB > “temporary” utility written some time ago, but seems to have become
HB > “permanent”! That is why there is no documentation on the utility.
HB > It is still needed if you want drivers to assign non-conflicting resources.HB > Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
IS the ‘seedres’ utility still needed in RTP boot images? I don’t see it in newer systems.What does/did it do? It doesn’t seem to be documented.
Hugh Brown <hsbrown@qnx.com> wrote:
: The seedres utility is there to read the PnP BIOS and assign resources
: to procnto’s resource database (I/O ports, IRQs etc.). this was a
: “temporary” utility written some time ago, but seems to have become
: “permanent”! That is why there is no documentation on the utility.
: It is still needed if you want drivers to assign non-conflicting resources.
I’ve added a page for seedres to the Utilities Reference.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
Hugh Brown <hsbrown@qnx.com> wrote:
HB > Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
OK. Thanks Hugh.
I am working on CompactPCI/X86 hardware and 6.2.0 SE system. I’m building
my own boot image. It does boot, but . . .If I include seedres I get an error at boot time that reads:
“Unable to allocate resource: Invalid argument”I have confirmed that it is seedres that is doing this by moving it
around (changing the order) and using display_msg’s.What is missing for seedres to do it’s thing without an error?
HB > This is most probably caused by the PnP BIOS returning a value that
HB > procnto does not agree with. If you start seedres with a ‘-v’ argument
HB > you should see the values that it is trying to seed to the resource
HB > database. You must start seedres before pci-bios and seedres must not
HB > be started in the background.
I put -v on the seedres line. There were many lines of cryptic output.
I’ve reproduces a few lines output in case they help to isolate what
seedres may be complaining about.
Attach Start 4000 - End 40bf - Flags 8402
Attach Start 2 - End 2 - Flags 8401
Unable to allocate resource: Invalid argument
Attach Start 280 - End 28f - Flags 8402
Attach Start 4 - End 4 - Flags 8401
If more of this output is needed where can it be redirected to?
There is no hard drive configured yet. Is there any kind of RAM-
disk that can be written to while the system is booting?
It will be kind of necessary to get rid of anything that looks like the
system is NOT booting properly. This is a system that we will need to
give to a cusomer.
Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
Hugh Brown <> hsbrown@qnx.com> > wrote:
HB > Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
OK. Thanks Hugh.I am working on CompactPCI/X86 hardware and 6.2.0 SE system. I’m building
my own boot image. It does boot, but . . .If I include seedres I get an error at boot time that reads:
“Unable to allocate resource: Invalid argument”I have confirmed that it is seedres that is doing this by moving it
around (changing the order) and using display_msg’s.What is missing for seedres to do it’s thing without an error?
HB > This is most probably caused by the PnP BIOS returning a value that
HB > procnto does not agree with. If you start seedres with a ‘-v’ argument
HB > you should see the values that it is trying to seed to the resource
HB > database. You must start seedres before pci-bios and seedres must not
HB > be started in the background.I put -v on the seedres line. There were many lines of cryptic output.
I’ve reproduces a few lines output in case they help to isolate what
seedres may be complaining about.Attach Start 4000 - End 40bf - Flags 8402
Attach Start 2 - End 2 - Flags 8401
Unable to allocate resource: Invalid argument
Attach Start 280 - End 28f - Flags 8402
Attach Start 4 - End 4 - Flags 8401
It is only complaining about IRQ 2, which I presume has already been
seeded by startup. This is not serious. If you want to get rid of the
message, just re-direct stderr to /dev/null.
If more of this output is needed where can it be redirected to?
There is no hard drive configured yet. Is there any kind of RAM-
disk that can be written to while the system is booting?It will be kind of necessary to get rid of anything that looks like the
system is NOT booting properly. This is a system that we will need to
give to a cusomer.
Hugh Brown <hsbrown@qnx.com> wrote:
HB > Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
I put -v on the seedres line. There were many lines of cryptic output.
I’ve reproduces a few lines output in case they help to isolate what
seedres may be complaining about.Attach Start 4000 - End 40bf - Flags 8402
Attach Start 2 - End 2 - Flags 8401
Unable to allocate resource: Invalid argument
Attach Start 280 - End 28f - Flags 8402
Attach Start 4 - End 4 - Flags 8401
HB > It is only complaining about IRQ 2, which I presume has already been
HB > seeded by startup. This is not serious. If you want to get rid of the
HB > message, just re-direct stderr to /dev/null.
Thanks for trying. But seedres does not seem to honor > /dev/null or
2> /dev/null. At least not at this stage of the build image.
Have you tried
reopen /dev/null
That will send all output to the bit bucket.
Then you can reopen to a console or serial port only if you want output.
Good Luck,
John
“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:bh83jc$12o$2@inn.qnx.com…
Hugh Brown <> hsbrown@qnx.com> > wrote:
HB > Previously, Bill Caroselli wrote in qdn.public.qnxrtp.installation:
I put -v on the seedres line. There were many lines of cryptic output.
I’ve reproduces a few lines output in case they help to isolate what
seedres may be complaining about.Attach Start 4000 - End 40bf - Flags 8402
Attach Start 2 - End 2 - Flags 8401
Unable to allocate resource: Invalid argument
Attach Start 280 - End 28f - Flags 8402
Attach Start 4 - End 4 - Flags 8401
HB > It is only complaining about IRQ 2, which I presume has already been
HB > seeded by startup. This is not serious. If you want to get rid of the
HB > message, just re-direct stderr to /dev/null.Thanks for trying. But seedres does not seem to honor > /dev/null or
2> /dev/null. At least not at this stage of the build image.