Announcement

Collapse
No announcement yet.

Ubuntu 16.04.2 LTS Delayed A Second Time

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • dungeon
    replied
    Originally posted by franglais125 View Post
    Curious, what do you mean exactly? Genuine question here
    I think that he means, how for example If you turn on your brain sun it is white, but without brain if you turn off your eyes then sun is black, otherwise yellow or red, etc...

    Debian Stable is just main repo, after release that sort of never get changed. Contrib and non-free repos are not part of the distro. Further, updates and security are handled by separate repos also, both recommeded but optional, one currently mandatory and one not. Everything else other than main is optional, including backports, etc...

    Now, someone might think of Debian Stable also as everything that happen around main in future after release, stable is not stable for new hardware normally so future needs fixes or just some upgrades because of that, but beware that new upgrades might have regressions... but sun is sun regardless of color opinion, as everything is relative and depends on POV .
    Last edited by dungeon; 01 February 2017, 09:03 PM.

    Leave a comment:


  • dungeon
    replied
    Originally posted by bridgman View Post
    Exactly the opposite, really - the open source drivers are "shipped to work with one kernel and one X" (since they live upstream) while AMDGPU-PRO and proprietary drivers are shipped to work with multiple kernels and multiple X versions. You may be confusing the current state with an early development state, where we were just starting to implement the Kernel Compatibility Layer and corresponding logic in the X driver.
    I mentioned "sort of" as am talking of what is shipped and not what is the goal... Just check reality, go and ask AMDGPU-PRO users "does PRO driver work with multiple kernels and X versions in comparision to opensource drivers"?

    In both cases you need to rebuild something to have compatibility isn't it, so exactly the same, really... only model/method differ and who will rebuild what

    Mixed combinations no...
    Michael will continue to complain, yes Users will continue to ask why, yes

    Or... stay with me now, this is pretty radical stuff...
    That is not so radical... most radical is to say to average Joe user to file useful bug
    Last edited by dungeon; 01 February 2017, 08:23 PM.

    Leave a comment:


  • franglais125
    replied
    Originally posted by dh04000 View Post

    Debian Stable != Release Quality Stable
    Curious, what do you mean exactly? Genuine question here

    Leave a comment:


  • rdeleonp
    replied
    Originally posted by bridgman View Post
    Mixed combinations no, but AFAIK the plan is to support both stacks - non-HWE plus latest HWE.
    Sweet!

    Leave a comment:


  • bridgman
    replied
    Originally posted by dungeon View Post
    ... particulary AMDGPU-PRO which is sort of shipped to work with one kernel and one X
    Exactly the opposite, really - the open source drivers are "shipped to work with one kernel and one X" (since they live upstream) while AMDGPU-PRO and proprietary drivers are shipped to work with multiple kernels and multiple X versions. You may be confusing the current state with an early development state, where we were just starting to implement the Kernel Compatibility Layer and corresponding logic in the X driver.

    Originally posted by dungeon View Post
    What AMDGPU-PRO will do there in another 6 months when 16.04.3 is there i dunno, then also X will be different major version... they might, but for now does not sounds to me they will support both stacks, not to mention mixed combinations
    Mixed combinations no, but AFAIK the plan is to support both stacks - non-HWE plus latest HWE.

    Originally posted by dungeon View Post
    Expect shit on any upgrade, that way you may learn to avoid it
    You can try it even now just enable proposed repo and expect shit to happen If shit does not happen by happy, otherwise fix it or complain
    Or... stay with me now, this is pretty radical stuff... you could check to make sure that the driver you have installed supports the new HWE version before upgrading, and if not, that a new version is available which does support it.

    Leave a comment:


  • dungeon
    replied
    Originally posted by tjaalton View Post
    The kernel is not available yet.
    AFAIR it was there, this:

    https://launchpad.net/ubuntu/+source/linux-hwe-edge

    but OK proposed is temporary repo, things are sometimes there and sometimes get removed

    That linux-hwe "4.8.0-37.39~16.04.1" must me in some repo i guess

    https://launchpad.net/~canonical-ker...ive/ubuntu/ppa

    Sounds weird to me that kernel is not in proposed
    Last edited by dungeon; 01 February 2017, 08:33 AM.

    Leave a comment:


  • tjaalton
    replied
    Originally posted by dungeon View Post
    You can try it even now just enable proposed repo and expect shit to happen If shit does not happen by happy, otherwise fix it or complain
    Only shit that'll happen is that you get newer mesa (12.0.6) if upgrading to -proposed. Getting the X stack (which is pretty much the same anyway apart from some minor driver updates) needs 'apt --install-recommends install xserver-xorg-hwe-16.04'. The kernel is not available yet.

    Leave a comment:


  • dungeon
    replied
    Originally posted by Morbis55 View Post
    "albeit for AMDGPU-PRO users, this will cause issues"
    What issues are you refering to?
    Upgrades related issues . Third party is always affected when you upgrade kernel/x, particulary AMDGPU-PRO which is sort of shipped to work with one kernel and one X

    What AMDGPU-PRO will do there in another 6 months when 16.04.3 is there i dunno, then also X will be different major version... they might, but for now does not sounds to me they will support both stacks, not to mention mixed combinations

    Expect shit on any upgrade, that way you may learn to avoid it

    Originally posted by Morbis55 View Post
    How can you go to the HWE Stack and get the newer kernel and stuff?
    You can try it even now just enable proposed repo and expect shit to happen If shit does not happen by happy, otherwise fix it or complain
    Last edited by dungeon; 01 February 2017, 05:32 AM.

    Leave a comment:


  • tjaalton
    replied
    Originally posted by bridgman View Post

    My understanding is that you will stay on the non-HWE stack unless you explicitly accept the upgrade to 16.04.2, if you do accept it then you will be automatically upgrade to .3, .4, .5 etc... Same if you download and install an HWE image - you follow the HWE upgrade path from that point.
    Yep, 16.04.2 and up will have a rolling enablement stack, more details at

    https://wiki.ubuntu.com/Kernel/Rolli...nablementStack

    Same applies to the X stack apart from Mesa which will be backported around the same time but unrenamed so that it'll replace the original version.

    Leave a comment:


  • bridgman
    replied
    Originally posted by Morbis55 View Post
    How can you go to the HWE Stack and get the newer kernel and stuff?
    After 16.04.2 is officially released of course, but how do you do that?
    As far as I understood, you will stay on 16.04.1 and Kernel 4.4 if you don't upgrade manually right?
    Will there be a message asking me to upgrae? Is there a option I have to check first? Do I have to use a command?

    "albeit for AMDGPU-PRO users, this will cause issues"
    What issues are you refering to?
    My understanding is that you will stay on the non-HWE stack unless you explicitly accept the upgrade to 16.04.2, if you do accept it then you will be automatically upgrade to .3, .4, .5 etc... Same if you download and install an HWE image - you follow the HWE upgrade path from that point.

    re: AMDGPU-PRO, what Michael means is that if we don't release an AMDGPU-PRO that works with 16.04.2 (which will have the 16.10 graphics stack) then upgrading to 16.04.2 will cause problems when the upgrade logic attempts to re-install the kernel driver.

    Leave a comment:

Working...
X