mkifs problems adding network support

QNX Newsgroups (Archives) qdn.public.qnxrtp.installation
#1

Hi,

I am in the progress of preparing a boot-floppy for a system containing a
network-application
In the progress of adding support for TCP/IP I end up in trouble.

When building the boot-image without any support for network, the system
comes up nice and easy,
but when adding support for network strange things happens. I have broken
down the problem
into this:

From the fully funtional build-file I simply add the ping-command (in
[data=copy]-section),
(never run it though) then the system stops after the initial Loading
…

I can’t see why the aditional ping command would generate such difference?

Has anyone seen this problem, and have a solution?

Thanks,
Gunnar

#2

I ran into a problem once where my boot image crossed the magical memory
size (640k??) and slogged over into the “memory hole” where the VGA and
whatnot is (although this was on an AMD Elan SC400 embedded system).
Perhaps your problem is somehow related to boot image size. What all you
got in there? If you can take out stuff like devc-8250 and run it from disk
or over the network perhaps you can scrounge up enough space for the
critical stuff (console & disk or console & network plus support files
should be all you need).

-Warren


“Gunnar Boström” <gunnar.bostrom@optonova.se> wrote in message
news:8ur66r$7pi$1@inn.qnx.com…

Hi,

I am in the progress of preparing a boot-floppy for a system containing a
network-application
In the progress of adding support for TCP/IP I end up in trouble.

When building the boot-image without any support for network, the system
comes up nice and easy,
but when adding support for network strange things happens. I have broken
down the problem
into this:

From the fully funtional build-file I simply add the ping-command (in
[data=copy]-section),
(never run it though) then the system stops after the initial Loading
…

I can’t see why the aditional ping command would generate such difference?

Has anyone seen this problem, and have a solution?

Thanks,
Gunnar

#3

The 640K boundary is what you hit. When an X86 processor starts up it is in real mode ( remember dos??) and only the first meg -64K is available to any program. One of the first things Qnx does when it boots is switch to protected mode.

Do any of you remeber the NS486SFX? it was the only X86-ish processor that came up in protected mode (but it had no mmu).


Previously, Warren Peece wrote in qdn.public.qnxrtp.installation:
{ I ran into a problem once where my boot image crossed the magical memory
{ size (640k??) and slogged over into the “memory hole” where the VGA and
{ whatnot is (although this was on an AMD Elan SC400 embedded system).
{ Perhaps your problem is somehow related to boot image size. What all you
{ got in there? If you can take out stuff like devc-8250 and run it from disk
{ or over the network perhaps you can scrounge up enough space for the
{ critical stuff (console & disk or console & network plus support files
{ should be all you need).
{
{ -Warren
{
{

\

Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8

#4

Yeah I was doing a NOBIOS IPL, so I was already in protected mode when the
image was loaded and ran into my memory gap. I thought there may be a
different limitation imposed on a PC BIOS loaded boot image however, I’m not
positive. Since then I’ve managed to decipher the Elan disfiguration
registers enough to give me contiguous memory from 0 up through 8 meg (my
system max) with no holes so I’m good to go…

-Warren



“Pat Ford” <pford@qnx.com> wrote in message
news:Voyager.001114085536.30836H@funnel.qnx.com…

The 640K boundary is what you hit. When an X86 processor starts up it is
in real mode ( remember dos??) and only the first meg -64K is available to

any program. One of the first things Qnx does when it boots is switch to
protected mode.

Do any of you remeber the NS486SFX? it was the only X86-ish processor
that came up in protected mode (but it had no mmu).


Previously, Warren Peece wrote in qdn.public.qnxrtp.installation:
{ I ran into a problem once where my boot image crossed the magical memory
{ size (640k??) and slogged over into the “memory hole” where the VGA and
{ whatnot is (although this was on an AMD Elan SC400 embedded system).
{ Perhaps your problem is somehow related to boot image size. What all
you
{ got in there? If you can take out stuff like devc-8250 and run it from
disk
{ or over the network perhaps you can scrounge up enough space for the
{ critical stuff (console & disk or console & network plus support files
{ should be all you need).
{
{ -Warren
{
{

\

Pat Ford email: > pford@qnx.com
QNX Software Systems, Ltd. WWW: > http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8

#5

Elan disfiguration registers

LOL! I got to remember that one

#6

Previously, Warren Peece wrote in qdn.public.qnxrtp.installation:
{ Yeah I was doing a NOBIOS IPL, so I was already in protected mode when the
{ image was loaded and ran into my memory gap. I thought there may be a
{ different limitation imposed on a PC BIOS

pc bios is 16 bit ( seg:offset)

{loaded boot image however, I’m not
{ positive. Since then I’ve managed to decipher the Elan disfiguration
{ registers enough to give me contiguous memory from 0 up through 8 meg (my
{ system max) with no holes so I’m good to go…

cool

{
{ -Warren
{
{
{
{ “Pat Ford” <pford@qnx.com> wrote in message
{ news:Voyager.001114085536.30836H@funnel.qnx.com…
{ > The 640K boundary is what you hit. When an X86 processor starts up it is
{ in real mode ( remember dos??) and only the first meg -64K is available to
{ any program. One of the first things Qnx does when it boots is switch to
{ protected mode.
{ >
{ > Do any of you remeber the NS486SFX? it was the only X86-ish processor
{ that came up in protected mode (but it had no mmu).
{ >
{ >
{ > Previously, Warren Peece wrote in qdn.public.qnxrtp.installation:
{ > { I ran into a problem once where my boot image crossed the magical memory
{ > { size (640k??) and slogged over into the “memory hole” where the VGA and
{ > { whatnot is (although this was on an AMD Elan SC400 embedded system).
{ > { Perhaps your problem is somehow related to boot image size. What all
{ you
{ > { got in there? If you can take out stuff like devc-8250 and run it from
{ disk
{ > { or over the network perhaps you can scrounge up enough space for the
{ > { critical stuff (console & disk or console & network plus support files
{ > { should be all you need).
{ > {
{ > { -Warren
{ > {
{ > {
{ >
{ >
{ > –
{ > Pat Ford email: pford@qnx.com
{ > QNX Software Systems, Ltd. WWW: http://www.qnx.com
{ > (613) 591-0931 (voice) mail: 175 Terence Matthews
{ > (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
{ >
{
{
{

–
Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8