R50 Addon Not Enabled by Default

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • May 31, 2013 at 1:20 pm #7877
    epa80
    Participant
    • Total Post: 208
    • Jacked into The Matrix
    • ★★★★★★

    We’re currently utilizing about 150 R50 units in production, running on 11.1.052. In our Addons folder, we have 2 addons:

    dhclient_hostname-1-0.sletc11sp1.rpm
    xset_no_blank-1-0.sletc11sp1.rpm

    What we’re experiencing is, out of the box and configured for first use, the devices pull down their INI as expected, and within Novell Addon Manager inside the Linux OS, we see the Addons there. However, we’re always seeing the no_blank add on not enabled. We have to manually go in, check it, execute it, and restart the terminal. On the dhclient addon, this isn’t the case.

    I’ve attached pictures of what we’re seeing. Has anyone experienced this? Is it working as designed or is there something I am missing?

    Thanks in advance.

    https://docs.google.com/file/d/0B2HDiJIo35eHVUx5b2FDOUJ3Ukk/edit?usp=sharing

    https://docs.google.com/file/d/0B2HDiJIo35eHVUx5b2FDOUJ3Ukk/edit?usp=sharing%5B/img%5D

    June 4, 2013 at 10:30 am #23912
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Add
    NewAddons=xset_no_blank-1-0.sletc11sp1.rpm
    to your wlx.ini and all should be good.

    CG

    June 4, 2013 at 11:37 am #23924
    Lavarius
    Participant
    • Total Post: 56
    • Back Stage Pass
    • ★★★★

    I’ve had luck in the NewAddons field stopping at the Dash before the version. So for my configurations it would look like NewAddons=xset_no_blank

    I’ve also noticed that the NewAddons line can be a little finicky. I’ve had some luck moving items around in order on the line and that helped.

    It does install correctly if checked manually though?

    also, your pictures are coming up the same for me, both showing the dhclient not checked.

    June 4, 2013 at 12:08 pm #23926
    epa80
    Participant
    • Total Post: 208
    • Jacked into The Matrix
    • ★★★★★★

    I discovered our issue. Our ini has always been set as:

    NewAddons=dhclient_hostname-1-0.sletc11sp1.rpm
    NewAddons=xset_no_blank-1-0.sletc11sp1.rpm

    I never realized the NewAddons line had to be 1 line, with each addon separated with a comma, as seen below:

    NewAddons=dhclient_hostname-1-0.sletc11sp1.rpm,xset_no_blank-1-0.sletc11sp1.rpm

    Upon testing this out, it looks like it is now working like we expect. I flashed a Terminal back to out of the box, applied this change, and both addons came up enabled.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.