yes, i had a mistake with sunray3+, for some reason i thought these were the ones with the display.
it seems though that it does not work on sunray3 (with one display port). i had an installation recently with sunray3 (with 2 display ports) where the popup-gui worked. i managed to confuse the different types. this is kinda wierd. i can 100% confirm that i have this issue on the sunrays available in my lab, namely being sunray2fs (2ports), sunray270 and do not have the issue on an ancient sunray1. I will see if i can get my hands on 2 different sunray3. Any Ideas were to start debugging/looking for a cause is welcome! :) Regards, Philipp On Mon, 2012-02-27 at 09:35 -0500, Sean Walmsley wrote: > We have 5.2.5 with the "4.3_146928-05_2011.12.19.17.08" firmware installed > with Sunray 3+ units and > the pop-up GUI seems to be working properly for us. > > We typically enable the GUI for each Sunray type as follows: > > /opt/SUNWut/sbin/utfwadm -A -a -V -G force -f > /opt/SUNWut/lib/firmware/CoronaP8 > /opt/SUNWut/sbin/utfwadm -A -a -V -G force -f > /opt/SUNWut/lib/firmware/CoronaP9 > /opt/SUNWut/sbin/utfwadm -A -a -V -G force -f > /opt/SUNWut/lib/firmware/CoronaP10 > > (the -f <path> is likely redundant now that there is only one firmware) > > > On 02/27/12 06:30, Philipp Vymazal wrote: > > On Mon, 2012-02-27 at 12:05 +0100, Volker A. Brandt wrote: > >>> After setting utfwadm -AaV -G none > >>> > >>> the *parms* file include the enablegui setting, the sunrays load the > >>> firmware from the server, the enableGui file in /tftpboot gets > >>> created but stop+m/stop+s do not show the gui on the clients (after > >>> power-cycle) > >>> > >>> I have verified that the clients load the correct firmware from the > >>> right server (currently they are within an isolated subnet anyway) > >>> being "4.3_146928-05_2011.12.19.17.08" > >> > >> I have the same problem, but > >> > >> - I am using 5.2.1 > >> - the problem occurs with a 2FS > >> - the DTU is not even retrieving the parms file (checked with snoop) > >> > >> I am still investigating. The next step is setting up the "old-style" > >> DHCP provisioning, but I haven't had a chance to do that yet. > >> > >> > >> Regards -- Volker > > > > Interesting i just managed to "reproduce this issue" on my 2FS in the > > TestLab as well, on which (i am certain) the pop-gui worked a few weeks > > ago (i remember resetting to defaults via gui). I did have an upgrade > > from 4.2 to 5.2.5 recently. Pop-up gui does not appear neither anymore, > > at least i can debug this locally now. Will sniff the connection to see > > if the parms file gets transmitted, good idea. > > > > update: this seems to be sunray client specific > > > > sunray1: pop-up gui works > > sunray2fs: pop-up gui does not work > > sunray270: pop-up gui does not work > > sunray3+: pop-up gui does not work > > sunray3: assume it works, since i did an installation (5.2.5) recently > > with sunray3 and enabled the gui at the customer site. > > > > so this seems to be a bug introduced in 5.x? > > > > Regards, > > Philipp > > > > > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users -- IPS Gesellschaft für innovative EDV-Produkte und - Systeme GmbH Franzosengraben 10 A-1030 Wien Tel.: +43 1 796 86 86 - 53 Mobil: +43 664 3979491 E-Mail: [email protected] _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
