- This topic is empty.
-
Posts
-
S10 Firmware Pull to USB Failing
Hello All,
I’m new to WYSE systems as of last week so please be patient..
WYSE hardware in use is Model SXO; Part No 902110-03L.
I have been asked to PULL the firmware from an existing S10 thin client and then PUSH it to another.
The firmware version in question is 6.3.0_22 and I am attempting to use version 1.16.0.6 of the WYSE USB firmware tool.
Initially I had problems getting the USB key bootable at all. I then found that if I used a 16GB key that was not made by SANdisk I could get it to work.
In the firmware tool I am asked to select the appropriate OS, we are using WTOS. For WTOS there are two options, ARM/T10/X10J or Xenith/Xenith Pro.
If I select the ARM option I cannot boot my S10 to Linux at all, I get the error message;
Booting Linux
kernel /kernel/vmlinux rw root=/dev/ram ramdisk_size=131072 vga=785 splash=silent ide_generic.probe_mask=0x03
Error 15: File not foundIf I select Xentih then I am able to boot into the pull utility to the point where I am asked to confirm if I wish to perform a pull operation. I answer yes and presented with the error message;
Copy Image to USB Failed
After which the system prompts for a reboot.
There are two files in the image directory of the device after the pull fail. CommandsXML.xml and Merlin.txt.
The CommandsXML file contains the following;
&V02|&IMAC=00806473fca9|OI=1|&SI=1|&IN=1|&ER=1|Merlin-Process-FAILURE_[Sun_Apr_23_19:23:03_2006]Copy image to USB failed|
2.5.4 | and the Merlin file contains the following;
12894d306c0b11da9ce4cafebeefffff
0
0
par1.img
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
bios.img
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
cmos.img
WdmCommand.c[2957]:
in fetchImagingComponents
WdmCommand.c[3758]:
URL path is :/mnt/ImageWdmCommand.c[3764]:
:’uploadImageToServer’WdmCommand.c[3765]:
:’/mnt/Image’WdmCommand.c[3764]:
:’uploadImageToServer’WdmCommand.c[3765]:
:’/mnt/Image’WdmCommand.c[3764]:
:’uploadImageToServer’WdmCommand.c[3765]:
:’/mnt/Image’WdmCommand.c[2012]:
Image is valid
RegistryLayer.c[137]:
About to open registry: ‘/tmp/system.conf’
RegistryLayer.c[205]:
About to close registry
WdmCommand.c[1157]:
Command received, commandName=’uploadImageToServer’
ImagingCommands.c[8268]:
after upload image to server 65
ImagingCommands.c[8308]:
uploadImageToServer1 :: system manufacturer is
ImagingCommands.c[8309]:
upImageToServer2 :: system class is
ImagingCommands.c[8334]:
upImageToServer ::going to execute sys command.
BiosCmos.c[33]:
PlatformBiosCmosInit for platform Callisto
…
BiosCmos.c[40]:
PlatformBiosCmosInit :: Comparing supported platform Proteus and Callisto
…
BiosCmos.c[40]:
PlatformBiosCmosInit :: Comparing supported platform Wyse Z Class Thin Client and Callisto
…
BiosCmos.c[40]:
PlatformBiosCmosInit :: Comparing supported platform Cisco VXC Class Thin Client and Callisto
…
BiosCmos.c[40]:
PlatformBiosCmosInit :: Comparing supported platform Wyse XM Class Thin Client and Callisto
…
BiosCmos.c[50]:PlatformBiosCmosInit Failed !!!
ImagingCommands.c[8396]: upImageToServer ::checking security key.
EepromFunctions.c[1354]:
Calling BEFORE read eeprom
EepromFunctions.c[1358]:
Calling AFTER read eeprom
EepromFunctions.c[1193]:
Entering fillRtlEepromAsset()
EepromFunctions.c[1363]:
Calling AFTER PARSE
ImagingCommands.c[8489]:
Got valid uploadImage command
ImagingCommands.c[8490]:
channel = ‘0’
ImagingCommands.c[8491]:
drive = ‘0’
ImagingCommands.c[8496]:
Read entire drive
ImagingCommands.c[10181]:
ConstructDeviceName :: Device Name isImagingCommands.c[8505]: Device name:
ImagingCommands.c[8617]:
serverlocation: /mnt/Image/par1.img
ImagingCommands.c[8623]:
Reading from
ImagingCommands.c[8624]:
Upload image to server using http
ImagingCommands.c[8644]:
disk size= 0
ImagingCommands.c[179]:
Number of Sectors is = 0ImagingCommands.c[200]:
Skipping to next method to calculate Number of Sectors is = 0ImagingCommands.c[208]:
Total Drive Size in bytes = 0UsbClient.c[80]: In PUT: deviceLocation:
UsbClient.c[81]:
In PUT: serverLocation: /mnt/Image/par1.img
UsbClient.c[82]:
In PUT: SplitPull: No
UsbClient.c[84]:usbClientFilePut: Error, could not open device file ”
UsbClient.c[248]:
response Code, usbClientFilePut: 134667924
ImagingCommands.c[8853]:
after upload image to server 100
WdmCommand.c[913]:
Error executing command ‘uploadImageToServer’
WdmCommand.c[914]:‘Command’, contents=NULL
‘source’, contents=NULL
‘media’, contents=NULL
‘ide’, contents=NULL
‘channel’, ‘0’
‘drive’, ‘0’
‘scope’, ‘
‘
‘drive’, ”
‘destination’, ‘par1.img’RegistryLayer.c[137]: About to open registry: ‘/tmp/system.conf’
RegistryLayer.c[205]:
About to close registry
AssetData.c[82]:
illegal character ‘:’ found in mac
AssetData.c[82]:
illegal character ‘:’ found in mac
AssetData.c[82]:
illegal character ‘:’ found in mac
AssetData.c[82]:
illegal character ‘:’ found in mac
AssetData.c[82]:
illegal character ‘:’ found in mac
AssetData.c[82]:
illegal character ‘
‘ found in mac
AssetData.c[925]:
done creating preboot clientData
WdmCommand.c[1174]:Encountered error executing command ; going to exit now.
WdmCommand.c[1199]:
**** THE URL PATH HERE IS =’/mnt/Image’
EepromFunctions.c[1354]:Calling BEFORE read eeprom
EepromFunctions.c[1358]:
Calling AFTER read eeprom
EepromFunctions.c[1193]:
Entering fillRtlEepromAsset()
EepromFunctions.c[1363]:
Calling AFTER PARSE
WdmCommand.c[1326]:
Calling upload merlin error log
RegistryLayer.c[137]:
About to open registry: ‘/tmp/system.conf’
RegistryLayer.c[205]:
About to close registry
RegistryLayer.c[137]:
About to open registry: ‘/tmp/system.conf’
RegistryLayer.c[205]:
About to close registry
WdmCommand.c[861]:
Calling upload log file to the location: /mnt/Image/Merlin.log
WdmCommand.c[862]:
log file location: /tmp/wdm.log
UsbClient.c[80]:
In PUT: deviceLocation: /tmp/wdm.log
UsbClient.c[81]:
In PUT: serverLocation: /mnt/Image/Merlin.log
UsbClient.c[82]:
In PUT: SplitPull: No
UsbClient.c[92]:
In PUT: in splitfile: 10
UsbClient.c[93]:
In PUT: serverLocation: /mnt/Image/Merlin.log
UsbClient.c[101]:
In PUT: in splitfile: 2
UsbClient.c[22]: totalBytesWritten: 0
UsbClient.c[23]: UploadSize: 0I’m looking for some help in interpreting these log files and understanding what is going wrong. To my novice eyes it looks like my terminal is not supported by the Xenith USB key. If this is the case what should I be doing???
Any help would be greatly appreciated….
MoJo.
- You must be logged in to reply to this topic.