On Tue, 2012-02-28 at 16:23 +0100, Jörg Barfurth wrote: > Am 28.02.12 09:58, schrieb Philipp Vymazal: > > Hello, > > > > Well in my Lab Case i have a different DHCP server (option 66 is set > > there pointing to the sunray server) but i dont use the SunRay DHCP > > server. I never have had issues with enabling/disabling the GUI in the > > past though and i know for sure that the firmware upgrade reached the > > sunray clients when i updated to 5.2.5 (distorted screen on clients on > > firmware upgrade, first 1/3 of the screen gets a wierd look in the newer > > firmwares when upgrading/loading). > > > > On another Site we have an SRS server (notebook) connected to Sunrays > > (switch inbetween) were the SRS DHCP is used, yet the GUI does not get > > enabled neither (all with LAN connections). > > > > My Lab Sunray1 and my Sunray2FS both have the identical firmware (since > > upgrade to 5.2.5). > > > > After looking abit deeper, it seems that my SunRay has the pop-up gui > > enabled no matter what (ignores utfwadm -Aa -N all -G off) and my > > Note that '-G off' does NOT mean that the GUI should be disabled. It > means that you cannot enable the GUI feature on DTUs that had it > disabled previously. It will not affect DTUs that had the feature > already enabled. > > The meanings of the options are: > > -G force: Unconditionally and automatically enable the GUI feature on > DTUs that use this parms file. The feature will remain enabled, if the > DTU subsequently is booted without a firmware server/parms file available. > > -G none: Allow the user to enable the GUI feature on DTUs that use this > parms file. The feature will actually be enabled only when the user > presses STOP-S/STOP-M. If that occurs, the feature will remain enabled > on future boots. If the feature was disabled and the user never presses > STOP-M/S the feature will remain disabled on future reboots without a > firmware server. > > - G prompt/-G $HASHED_PASSWORD: Same as -G none, but the user will be > asked for the provided password when she attempts to enable the GUI > feature, i.e. when she presses STOP-M for the first time (and only if > the GUI feature was disabled before that) > ['prompt' means that utfwadm prompts you for the password. The parms > file will contain the hashed password.] > > -G off: It is not possible to enable the GUI on a DTU that did not have > it enabled. > > The change from a DTU that had the GUI enabled to one that has the GUI > feature disabled (including on subsequent reboots) is controlled by the > -g option: > > -g force: Unconditionally and automatically disable the GUI feature. > > -g none: Allow the user to disable the GUI feature by using the > corresponding item in the DTU GUI menu. > > -g prompt/-g $HASHED_PASSWORD: If the user attempts to disable the GUI > feature by using the corresponding menu item, they will be asked for the > given password. > > -g off: It is not possible to disable the GUI on a DTU that did have it > enabled. > > > SunRay2FS has the pop-up gui disabled (cannot be enabled). > > > > I honestly dont know what i am missing. I know the Option66 is set > > correctly, i can see the SunRay communicating with the (right) Server > > (stop+n), > > STOP-N will show session connections. You need to verify that the DTU > uses the correct firmware server. > > > i see firmware upgrades if i order them, but i cant enable (or > > disable) the GUI. I cannot use the SRS DHCP server but iirc that is not > > a absolute requirement (as long as option66 is provided correctly). > > > > Can you show us: > > - utquery output of an affected DTU. This will indicate which firmware > server is in use and what parms settings the DTU has received. > > - the /tftpboot/SunRayP8.parms file from the firmware server > > > Either i have missed some obvious setting in the newer SRS versions or > > something doesnt work as expected? > > > > As pointed out, it is important that the DTU uses the right firmware > server, successfully gets a parms file from that server and that the > right enablegui/disablegui settings are in the parms file loaded by the DTU. > > If the DTU doesn't find a parms file, the transitions from non-GUI mode > to GUI mode or from GUI mode to non-GUI mode will be disallowed. (But > the DTU will retain the mode last used.) > > HTH > > -Jörg >
Hello Jörg, I finally managed to dig through whatever went wrong there, thanks for to your help. For some reason, one of the DTUs (2FS) was using the wrong tftpserver even though he managed to pull the correct firmware from the sunray server itself. however, it never pulled the *parms* files from there, instead it went to the wrong tftp server to ask for completely ancient ones. I managed to track down a rogue dhcp server (for some reason i never thought of that) and even due to all statistical unlikelyhood (both rays are connected to the same switch) one of the dtus always got a response from that rogue dhcp. that issue is now fixed, and both DTUs receive the right files from the correct server... I should have noticed that from the utquery output right away, somehow i missed it. sorry (and thanks) for all the inconvenience & time! feeling abit stupid now :) thanks again! regards, philipp _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
