[Touch-packages] [Bug 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics

2017-05-14 Thread Henrique de Moraes Holschuh
This is a Kabilake system, the intel-microcode does not support it as of 20161104 or 20170511 (upcoming release, to be uploaded in the next few days). Please ensure your BIOS/UEFI is up-to-date, latest known-to-be-available microcode is revision 0x58, so it is not impossible that there are availab

[Touch-packages] [Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.

2016-10-11 Thread Henrique de Moraes Holschuh
FWIW, here are some points to consider when implementing this: 1. A multi-processor system may contain processors that differ in stepping, or for other reasons (e.g. ARM big.LITTLE). This *is* quite common on x86 servers and workstations. So, you might have more than one processor model to list.

[Touch-packages] [Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.

2016-10-11 Thread Henrique de Moraes Holschuh
(BTW: if reporting microcode revision in hexadecimal, it should be prefixed with 0x for clarity). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1444682 Title:

[Touch-packages] [Bug 1475042] Re: ubuntu 15.04 wireless network driver doesn't connect: always "trying to connect" animation

2016-02-04 Thread Henrique de Moraes Holschuh
This bug is filled against the wrong package, "intel-microcode" is only related to CPU microcode, not to wireless card microcode, or drivers... I do not know to which package this bug should be reassigned. -- You received this bug notification because you are a member of Ubuntu Touch seeded pack

[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

2014-12-03 Thread Henrique de Moraes Holschuh
You will want the newer intel-microcode packages, then. This means a resync with Debian is highly advised. Exactly due to the issue brought to the front by the Intel Haswell microcode update that disabled TSX, Debian has switched to enforcing that automated microcode updates be done only through