update_firmware not working anymore (cont.)

[Bas Gooren]

In reply to http://lists.us.dell.com/pipermail/linux-poweredge/2008-November/038038.html, and my earlier message which Patrick responded to.

Annoyed (insert smiley) by the fact that:
a) the bug in the inventory_collector I reported earlier is still not fixed
    -> /usr/lib/python2.4/site-packages/dell_dup/svm.py line 121 needs to read "int(device, 16)" instead of "int(device, 10)"
b) update_firmware is still not working.

The reason for posting here (again) is that I saw another libsmbios & dell-dup update, and still could not update my firmware.

Anyhow, I decided to look a little further, since I was able to fix the inventory_collector bug as well. I decided to dig deeper on the BIOS update not working.
After tracing the commands which update_firmware runs, I gathered that it runs "biosie.bin -u". So I ran a search on my system and found the file at

/usr/share/firmware/dell/dup/system_ven_0x1028_dev_0x01b2/dell_dup_componentid_00159_version_2.5.0/biosie.bin

When running it by hand ("./biosie.bin -u"), it reports exactly what I saw when tracing update_firmware:

<?xml version="1.0" encoding="UTF-8" ?><SVMExecution lang="en"><Device componentID= "159" display="BIOS" impactsTPMmeasurements="TRUE"><Application componentType= "BIOS" version="XXXX" display = "BIOS" ><Package version="XXXX"/><SPStatus result="false"><Message id="12">The BIOS HDR file is missing.</Message></SPStatus></Application></Device></SVMExecution>

It's missing a HDR file, while I see a file named "pe2950-020500C.hdr" neatly stashed in a subdirectory called "payload".

Then I ran some searches through Google, and noticed most Dell packages have the HDR file in the same directory... So I copied the file over to the main directory (next to biosie.bin) and re-ran "biosie.bin -u". Lo and behold, now the update worked. I rebooted the server and am now running the new BIOS.

So for the love of whatnot, can someone (at dell?) explain to me why this package will never work without manual intervention? Since update_firmware does not report any errors by itself, I wonder if other users on this list are still able to update their firmware through "yum update" and "update_firmware"...

I will try the other failing updates as well, possibly they have similar issues.

Regards,

Bas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20090120/d7a645ad/attachment.htm