On Mon, 7 Jul 2008, Stuart F. Biggar wrote:
> Hopefully some x86 expert will respond. I have SRS 4.0 on SPARC
> with all recent patches. After running the firmware command
> on the server and power cycling a old SunRay, it shows the
> new firmware:
>
> [erdas:/space/patch/s10]# /opt/SUNWut/sbin/utfwadm -A -a -n all
> All the units served by "erdas" on the 192.168.128.0
> network interface, running firmware other than version
> "4.0_127553-03_2008.05.14.13.48" will be upgraded at their next
> power-on.
Inetersting; I have no private interfaces, so my command is slightly
different. But the output is VERY different:
[EMAIL PROTECTED] /opt/SUNWut/sbin/utfwadm -A -a -V -F -u
CoronaP1 4.0_48_2007.08.01.15.48
CoronaP2 4.0_48_2007.08.01.15.48
CoronaP3 4.0_48_2007.08.01.15.48
CoronaP4 4.0_48_2007.08.01.15.48
CoronaP5 4.0_48_2007.08.01.15.48
CoronaP6 4.0_48_2007.08.01.15.48
CoronaP7 4.0_48_2007.08.01.15.48
SunRayP8 4.0_48_2007.08.01.15.48
> Did you power cycle the SunRay after adding the patch and running
> the utfwadm command? (Before the command and powercycling, I had
> an older firmware version: 4.0_127553-01_2007.11.09.17.4, apparently
> from and earlier version of the patch.)
Not sure I did previously, but I definately power cycled the SunRay
just now. No dice... :-(
What does ls -l /opt/SUNWut/lib/firmware* say for you? Mine says
this:
[EMAIL PROTECTED] ls -l /opt/SUNWut/lib/firmware*
/opt/SUNWut/lib/firmware:
total 5242
drwxr-xr-x 2 root sys 512 Jul 5 14:41 .
drwxr-xr-x 17 root sys 3584 Jul 5 14:42 ..
-rwxr-xr-x 1 root sys 302663 Aug 1 2007 CoronaP1
-rwxr-xr-x 1 root sys 302804 Aug 1 2007 CoronaP2
-rwxr-xr-x 1 root sys 302806 Aug 1 2007 CoronaP3
-rwxr-xr-x 1 root sys 302925 Aug 1 2007 CoronaP4
-rwxr-xr-x 1 root sys 302926 Aug 1 2007 CoronaP5
-rwxr-xr-x 1 root sys 302926 Aug 1 2007 CoronaP6
-rwxr-xr-x 1 root sys 312070 Aug 1 2007 CoronaP7
-rwxr-xr-x 1 root sys 474453 Aug 1 2007 CoronaP8
/opt/SUNWut/lib/firmware_gui:
total 5242
drwxr-xr-x 2 root sys 512 Jul 5 14:41 .
drwxr-xr-x 17 root sys 3584 Jul 5 14:42 ..
-rwxr-xr-x 1 root sys 302693 Aug 1 2007 CoronaP1
-rwxr-xr-x 1 root sys 302804 Aug 1 2007 CoronaP2
-rwxr-xr-x 1 root sys 302804 Aug 1 2007 CoronaP3
-rwxr-xr-x 1 root sys 302917 Aug 1 2007 CoronaP4
-rwxr-xr-x 1 root sys 302918 Aug 1 2007 CoronaP5
-rwxr-xr-x 1 root sys 302918 Aug 1 2007 CoronaP6
-rwxr-xr-x 1 root sys 312085 Aug 1 2007 CoronaP7
-rwxr-xr-x 1 root sys 474456 Aug 1 2007 CoronaP8
So the directories were created on July 5th (correct), but the
firmware files are from August last year... I can't believe
that the x86 version of this patch has a big mistake like this
with the firmware, but I guess it's possible.
I might download the SPARC version of the patch and see what
the timestamp on its firmware files are. If they're more recent,
I might try copying them to /opt/SUNWut/lib and try to sync the
firmware again. Presumably the SunRay client FW is the same
regardless of the server platform?
--
Rich Teer, SCSA, SCNA, SCSECA
CEO,
My Online Home Inventory
URLs: http://www.rite-group.com/rich
http://www.linkedin.com/in/richteer
http://www.myonlinehomeinventory.com
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
