Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Did the RAM limits change for Home edition for 16.05.2 to 4GB?

Did the limits for RAM on Home edition get changed with SFOS 16.05.2 MR2? I'm only seeing 4GB after update. Still only showing 4GB after rolling back to SFOS 16.05.1 MR-1. I was seeing 6GB usable before upgrade.



This thread was automatically locked due to age.
Parents
  • Ok so I did a test upgrade from 16.01.3 to 16.05.1 to 16.05.2 on a virtual machine with 8GB of ram to try and simulate what those with physical HW with greater than 6GB are seeing. For those who are using virtual appliances running 16.05.2 try taking a snapshot/checkpoint and increasing your VMs memory to 8GB.

     

    Here's what 16.01.3 looks like booting up with 8GB of RAM.

    Here's its boot params


    16.05.1 boot after upgrade from 16.01.3

    its boot params

    16.05.2 boot image. Note on this one it first showed 8000MB, but as soon as I tried to sign into the cmdline the system rebooted and then showed 4968MB.

    Here's what 16.05.2 boot params look like after I was able to get signed in. To me it seems like before this release there wasn't a check/restriction being set but now with 16.05.2 it is doing a restriction via those kernel boot params. For whatever reason they're not getting applied correctly.

  • I wonder if all of this is causing my next problem.

    When the "Patterns" update .... the firewall stops working. ( Own post )


    If this is related to my singel 8GB and 64bits bios and the 6GB limit in the software i dont know.

    But if the problem resists over the next month, I have to go back to my SmoothWall again.

    Sadley.

  • I'm wondering if we need to open a new forum topic for this. I haven't seen any input from sophos for quite a while.

    I think at least 2 of us have discovered what the trigger was for having 4G of ram out of 8G. The mem=6G kernel option.

    It's not working like they thought and needs to be revisited. 

    As far as the answer on the memory license not changing for MR2 their previous statement that nothing was changed is WRONG.

    They introduced a kernel memory limit, and that kernel memory limit is not working as they intended on certain hardware configurations.

     

Reply
  • I'm wondering if we need to open a new forum topic for this. I haven't seen any input from sophos for quite a while.

    I think at least 2 of us have discovered what the trigger was for having 4G of ram out of 8G. The mem=6G kernel option.

    It's not working like they thought and needs to be revisited. 

    As far as the answer on the memory license not changing for MR2 their previous statement that nothing was changed is WRONG.

    They introduced a kernel memory limit, and that kernel memory limit is not working as they intended on certain hardware configurations.

     

Children