On 08/09/13 09:38, Henrique de Moraes Holschuh wrote:
> For a P4, which is extremely unlikely to get
> any further microcode updates (unlikely but not impossible, as there are
> "embedded" P4 parts that have a 10-year support life and might still get an
> update for whatever reason),
I guess the N
On Mon, Sep 9, 2013 at 12:55 AM, Henrique de Moraes Holschuh
wrote:
> On Sun, 08 Sep 2013, Joel Rees wrote:
>> I was hoping that AMD was not going to have the license and
>> non-visibility issue that plagues the Intel processor microcode
>> updates. But I find this original announcement from when
(Thanks for obliging, Henrik. ;-)
On Sun, Sep 8, 2013 at 5:34 PM, Henrik Ahlgren wrote:
> On Sun, Sep 08, 2013 at 08:00:12AM +0900, Joel Rees wrote:
>> (1) This requires enabling two repositories that I have been avoiding
>> enabling, contrib and non-free. That means I have to watch the
>> reposi
On 9/09/2013 2:18 AM, Volker Birk wrote:
> On Sun, Sep 08, 2013 at 12:55:05PM -0300, Henrique de Moraes Holschuh wrote:
>> Note that even the internal errata/fix information is bound to be really
>> uninteresting anyway. Backdoors would not be documented anywhere, heck, it
>> is very likely that o
On Sun, 08 Sep 2013, Joel Rees wrote:
> I was hoping that AMD was not going to have the license and
> non-visibility issue that plagues the Intel processor microcode
> updates. But I find this original announcement from when Henrique made
> the updater tool available:
>
> http://lists.debian.org/d
On Sun, 08 Sep 2013, Henrik Ahlgren wrote:
> > or synaptic to look for new tools, right? Or can we just enable those
> > two repositories long enough to load Henrique's tool and the microcode
> > updates, then disable them again?
>
> Why do you feel that you even need to ask? You are free to handl
On Sun, Sep 08, 2013 at 08:00:12AM +0900, Joel Rees wrote:
> (1) This requires enabling two repositories that I have been avoiding
> enabling, contrib and non-free. That means I have to watch the
> repository more carefully when using
>
> apt-cache search
>
> or synaptic to look for new tools
* Henrique de Moraes Holschuh [2013-09-07 18:55 -0300]:
> On Sat, 07 Sep 2013, Elimar Riesebieter wrote:
> > * Elimar Riesebieter [2013-09-07 15:32 +0200]:
> > > ACK, loaded as module. Thanks for the hint. But I can't find a note
> > > on how to verify the new microcode is loaded?
> >
> > $ dme
* On 2013 07 Sep 16:40 -0500, Henrique de Moraes Holschuh wrote:
> On Sat, 07 Sep 2013, Nate Bargmann wrote:
> > I have an older P4 system with hyperthreading and it seems the updated
> > microcode was loaded when I installed the package:
>
> It was loaded, but the messages you sent do not imply a
On Sun, 08 Sep 2013, shirish शिरीष wrote:
> microcode bundle 1: /lib/firmware/intel-ucode/06-17-0a
> 01/001: sig 0x0001067a, pf mask 0xa0, 2010-09-28, rev 0x0a0b, size 8192
> 01/002: sig 0x0001067a, pf mask 0x11, 2010-09-28, rev 0x0a0b, size 8192
> 01/003: sig 0x0001067a, pf mask 0x44, 2010-0
(I kind of hope this starts a flame war large enough to embarrass the
corporate culprits into behaving themselves about this. Apologies in
advance when I step on toes.)
I was hoping that AMD was not going to have the license and
non-visibility issue that plagues the Intel processor microcode
updat
in-line :-
On 9/8/13, Henrique de Moraes Holschuh wrote:
> On Sat, 07 Sep 2013, shirish शिरीष wrote:
>> I also read the README.gz and realized it's kinda pointless till Intel
>> starts distributing some sort of errata and changelog information
>
> They do distribute some information, but only to
On Sat, 07 Sep 2013, Elimar Riesebieter wrote:
> * Elimar Riesebieter [2013-09-07 15:32 +0200]:
> > ACK, loaded as module. Thanks for the hint. But I can't find a note
> > on how to verify the new microcode is loaded?
>
> $ dmesg | grep micro
> microcode: CPU0 sig=0x10676, pf=0x80, revision=0x610
On Sat, 07 Sep 2013, shirish शिरीष wrote:
> I also read the README.gz and realized it's kinda pointless till Intel
> starts distributing some sort of errata and changelog information
They do distribute some information, but only to Intel hardware partners
which have access to microcode updates dir
On Sat, 07 Sep 2013, Nate Bargmann wrote:
> I have an older P4 system with hyperthreading and it seems the updated
> microcode was loaded when I installed the package:
It was loaded, but the messages you sent do not imply an update took place.
Check for microcode messages with "updated". If you f
at bottom :-
On 9/7/13, Henrique de Moraes Holschuh wrote:
> On Sat, 07 Sep 2013, shirish शिरीष wrote:
>> Would installing the intel processor microcode package and the
>> icu-tools have any benefit to me ?
>>
>> cpuid -1 | grep 'Intel Pentium'
>> family = Intel Pentium Pro/II/III
I have an older P4 system with hyperthreading and it seems the updated
microcode was loaded when I installed the package:
Sep 7 08:29:23 kernel: [1268878.007882] platform microcode:
firmware: agent loaded intel-ucode/0f-04-01 into memory
Sep 7 08:29:23 kernel: [1268878.007943] platform microcode
* Elimar Riesebieter [2013-09-07 15:32 +0200]:
> ACK, loaded as module. Thanks for the hint. But I can't find a note
> on how to verify the new microcode is loaded?
$ dmesg | grep micro
microcode: CPU0 sig=0x10676, pf=0x80, revision=0x610
microcode: CPU1 sig=0x10676, pf=0x80, revision=0x610
micr
* Henrique de Moraes Holschuh [2013-09-07 09:13 -0300]:
> > * Henrique de Moraes Holschuh [2013-09-03 09:05 -0300]:
[...]
> The two easy ways are: either you start using initramfs, or you
> need to make sure the microcode driver is a module (it is a module in the
> standard Debian kernel), and t
On Sat, 07 Sep 2013, Elimar Riesebieter wrote:
> * Henrique de Moraes Holschuh [2013-09-03 09:05 -0300]:
> > You must also update the initramfs so that the processor microcode will be
> > updated after a reboot/power off. The packages will try to do it
> > automatically for the running kernel and
On Sat, 07 Sep 2013, shirish शिरीष wrote:
> Would installing the intel processor microcode package and the
> icu-tools have any benefit to me ?
>
> cpuid -1 | grep 'Intel Pentium'
> family = Intel Pentium Pro/II/III/Celeron/Core/Core
> 2/Atom, AMD Athlon/Duron, Cyrix M2, VIA C3 (6)
* Henrique de Moraes Holschuh [2013-09-03 09:05 -0300]:
[...]
> You must also update the initramfs so that the processor microcode will be
> updated after a reboot/power off. The packages will try to do it
> automatically for the running kernel and that should be enough for most
> users.
>
> Ho
Dear Henrique de Moraes Holschuh and all,
Sorry for being late to the party. I installed Debian about a month ago.
Would installing the intel processor microcode package and the
icu-tools have any benefit to me ?
cpuid -1 | grep 'Intel Pentium'
family = Intel Pentium Pro/II/III/C
On Wed, 04 Sep 2013, David Guntner wrote:
> used because of the scale of how many CPUs are affected. It's
> "non-free" in the sense that they hold patents, etc., on the code that
> restrict how you can use it and so on.
It is non-free because of the license attached to the microcode
distribution,
Carlo grabbed a keyboard and wrote:
> Hi Verde Denim, I like to think with free software, I saw that it is a
> non-free, can we trust of it ? Or this isn't againt debian free software
> guidelines? Why Intel doesn't give a free microcode???
Please don't top post in a E-Mail reply, *especially* on
On 09/03/2013 08:42 PM, Vincent Lefevre wrote:
> On 2013-09-03 16:20:56 -0700, David Christensen wrote:
>> On 09/03/13 05:05, Henrique de Moraes Holschuh wrote:
>>> THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL
>>> MICROPROCESSORS.
>> Please provide a URL to the intel.com web page t
Hi Verde Denim, I like to think with free software, I saw that it is a
non-free, can we trust of it ? Or this isn't againt debian free software
guidelines? Why Intel doesn't give a free microcode???
thanks.
Carlo.
2013/9/4 Verde Denim
> On 09/03/2013 08:42 PM, Vincent Lefevre wrote:
> > On 20
On 2013-09-04 08:49:47 +0700, Rick Valenzuela wrote:
> On 09/04/2013 07:42 AM, Vincent Lefevre wrote:
> > "apt-get changelog intel-microcode" leads you to:
> >
> > https://bugs.launchpad.net/intel/+bug/1212497
> >
> > which provides the URL to the intel.com web page:
> >
> > https://download
On 09/04/2013 07:42 AM, Vincent Lefevre wrote:
> "apt-get changelog intel-microcode" leads you to:
>
> https://bugs.launchpad.net/intel/+bug/1212497
>
> which provides the URL to the intel.com web page:
>
> https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23082
There's also
On 2013-09-03 16:20:56 -0700, David Christensen wrote:
> On 09/03/13 05:05, Henrique de Moraes Holschuh wrote:
> >THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL
> >MICROPROCESSORS.
>
> Please provide a URL to the intel.com web page that tells us about the
> microcode update.
"apt-g
On 09/03/13 05:05, Henrique de Moraes Holschuh wrote:
THIS ANNOUNCEMENT IS ONLY RELEVANT TO SYSTEMS THAT HAVE INTEL
MICROPROCESSORS.
Please provide a URL to the intel.com web page that tells us about the
microcode update.
TIA,
David
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.d
On Tue, 03 Sep 2013, Henrique de Moraes Holschuh wrote:
> Alternatively, you can install the packages manually. To get the updated
> packages directly, please install the current "intel-microcode" and
> "iucode-tool" packages normally, then download and install the updated
> "intel-microcode" pack
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
On Thu,02.Apr.09, 12:38:53, John W Foster wrote:
[snip unwanted message]
> Why is this on a Debian List???
Because it's spam? Please do not answer (and definitely don't quote) to
messages that look like spam.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enou
On Wed, 2009-04-01 at 18:25 +, Tzafrir Cohen wrote:
> On Wed, Apr 01, 2009 at 11:30:10PM +0530, Jeffrin Jose wrote:
> > hello all,
> >
> > I have a good news to announce.
> > I have started a Fundamnetal Research(as i call ) on Installers and
> > Builders.
> >
> > You can see the scratch wor
On Wed, 2009-04-01 at 23:30 +0530, Jeffrin Jose wrote:
> hello all,
>
> I have a good news to announce.
> I have started a Fundamnetal Research(as i call ) on Installers and
> Builders.
>
> You can see the scratch work at
> http://www.trueangle.org/ and
> http://www.gnuresearch.com/
> All supp
On Wed, Apr 01, 2009 at 11:30:10PM +0530, Jeffrin Jose wrote:
> hello all,
>
> I have a good news to announce.
> I have started a Fundamnetal Research(as i call ) on Installers and
> Builders.
>
> You can see the scratch work at
> http-//www_trueangle_org/ and
> http-//www_gnuresearch_com/
(URL
> From: [EMAIL PROTECTED] (Bruce Perens)
> ...
> We will do this by producing a CD "master" (actually an ISO image file)
> of each release ...
Excellent! (The quality of the CD distribution depends only on Debian, not
on CD manufacturers.)
Daniel
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-
49 matches
Mail list logo
