On Tue, 06 Nov 2012, Stan Hoeppner wrote:
> So I'm left assuming that this initiative is the result of more and more
> Debian users purchasing systems sufficiently new enough that errata are
> being discovered, and new microcode being issued, after they receive
> their systems, and these folks aren
On 11/6/2012 10:08 AM, Henrique de Moraes Holschuh wrote:
> What I do know is that lack of microcode update support is a severe issue
> IMO.
Debian has survived and functioned very well with good stability, all
the while lacking microcode update capability for all these years. This
doesn't seem
On Tue, 06 Nov 2012, Stephan Seitz wrote:
> On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> >I would like to bring to your attention the improved support for system
> >processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
> >that was recently added to [
On Tue, 06 Nov 2012, Jon Dowland wrote:
> On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> > Microcode updates will be applied immediately when the microcode
> > packages are installed or updated: you don't have to reboot. You will
> > have to keep the packages instal
On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
I would like to bring to your attention the improved support for system
processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
that was recently added to [non-free] Wheezy.
Alas, this will not work for XE
On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote:
> Microcode updates will be applied immediately when the microcode
> packages are installed or updated: you don't have to reboot. You will
> have to keep the packages installed, though: as explained above, the
> microcode
On Mon, Nov 05, 2012 at 06:23:40PM -0300, Dr Beco wrote:
> Hoping to add some 'reference', so we can compare actual microcode
> versions, I find myself with
> $ cat /proc/cpuinfo | grep microcode
> microcode 0x1b
> ...
Slighly faster to type and run
$ grep microcode /proc/cpuinfo
On Tue, 06 Nov 2012, Erwan David wrote:
> On Mon, Nov 05, 2012 at 09:12:53PM CET, Henrique de Moraes Holschuh
> said:
> > Microcode updates will be applied immediately when the microcode
> > packages are installed or updated: you don't have to reboot. You will
> > have to keep the packages insta
On Mon, Nov 05, 2012 at 09:12:53PM CET, Henrique de Moraes Holschuh
said:
>
> Microcode updates will be applied immediately when the microcode
> packages are installed or updated: you don't have to reboot. You will
> have to keep the packages installed, though: as explained above, the
> microc
On Mon, 05 Nov 2012, Dr Beco wrote:
> Hoping to add some 'reference', so we can compare actual microcode
> versions, I find myself with
> $ cat /proc/cpuinfo | grep microcode
> microcode 0x1b
> ...
>
> Now, what is the version of the updated microcode?
cpuinfo lists the current microcode running
Le Mon 5/11/2012, Dr Beco disait
> On Mon, Nov 5, 2012 at 5:12 PM, Henrique de Moraes Holschuh
> wrote:
> > Hello all,
> >
> > I would like to bring to your attention the improved support for system
> > processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
> > that was recently add
On Mon, Nov 5, 2012 at 5:12 PM, Henrique de Moraes Holschuh
wrote:
> Hello all,
>
> I would like to bring to your attention the improved support for system
> processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
> that was recently added to [non-free] Wheezy.
Thanks Henrique for
Hello all,
I would like to bring to your attention the improved support for system
processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems
that was recently added to [non-free] Wheezy.
System Processors from Intel and AMD may need updates to their microcode
(sort of a control sequenc
13 matches
Mail list logo
