Remote boot error

  • Thread starter Thread starter Shanky Sangie
  • Start date Start date
S

Shanky Sangie

hi all,

i am trying with PXE Remote Boot and i am using XPe SP1.

After SDI file getting downloaded the screen goes blank for few
minutes and the following blue screen error appears.

A kernel thread terminated while holding a mutex

Stop: 0x4000008A (some parameters)

i have gone thro' some informations that says this is the video
BIOS problem but i couldn't get any infm how to fix this bug?

Any solutions???

Thank u in advance.

shanky
 
Have you tried to boot from SDI localy?

If you are using /noguiboot in your boot.ini this could explain why you have
blank screen.
Try to use /sos instead of /noguiboot for diagnostic purposes only.

Regards,
Slobodan
 
hi slobodan
i have tried with the /noguiboot and /sos options seperately as well
as combined still the blank screen appears. the boot.ini file is as
follows

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect /noguiboot /sos

the switch /noguiboot doesn't work locally but /sos works well.

This kinda problem occurs with all motherboards having north bridge
VIA VT8601 chipset.

regards

shanky
 
Have you added Windows RAM Disk driver to your image?

Do you see anything image loading, progress bar, sos info, etc?

Don't use /noguiboot.
I was thinking more like:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
ramdisk(0)\windows="XPE RAM Disk"
/rdpath=multi(0)disk(0)rdisk(0)partition(1)\xpeimg.sdi /rdimageoffset=245760
/sos
ramdisk(0)\windows="XPE RAM Disk"
/rdpath=multi(0)disk(0)rdisk(0)partition(1)\xpeimg.sdi /rdimageoffset=245760
/debug /debugport=com1 /baudrate=115200

change rdimageoffset to valid offset value for your SDI file PART section.
change ARC paths also to reflect your target system.

This boot.ini should be on target system HDD, during the tests.

You can try to use /debug and RS232 cable with windbg.exe to remotely debug
your device.

Regards,
Slobodan

Shanky Sangie said:
hi slobodan
i have tried with the /noguiboot and /sos options seperately as well
as combined still the blank screen appears. the boot.ini file is as
follows

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect /noguiboot /sos

the switch /noguiboot doesn't work locally but /sos works well.

This kinda problem occurs with all motherboards having north bridge
VIA VT8601 chipset.

regards

shanky


"Slobodan Brcin" <[email protected]> wrote in message
Have you tried to boot from SDI localy?

If you are using /noguiboot in your boot.ini this could explain why you have
blank screen.
Try to use /sos instead of /noguiboot for diagnostic purposes only.

Regards,
Slobodan
Click to expand...
Click to expand...
 
Back
Top