On Saturday 05 February 2011 15:28:22 Enrico Weigelt wrote:
* Volker Armin Hemmann volkerar...@googlemail.com wrote:
and that is all the intel stuff. For AMD all you have to do is:
modprobe -r microcode modprobe microcode
Is the microcode permanently flashed or loaded into some
internal
* Volker Armin Hemmann volkerar...@googlemail.com wrote:
the CPU. All CPUs use microcode. For decades. Google, or go straight to
wikipedia.
http://en.wikipedia.org/wiki/Microcode
Borroughs' large systems (b6500+) were designed as microcode
machines from ground up, which essentially
* Volker Armin Hemmann volkerar...@googlemail.com wrote:
and that is all the intel stuff. For AMD all you have to do is:
modprobe -r microcode modprobe microcode
Is the microcode permanently flashed or loaded into some
internal RAM ?
cu
--
Enrico Weigelt weig...@metux.de [11-02-05 16:08]:
* Volker Armin Hemmann volkerar...@googlemail.com wrote:
and that is all the intel stuff. For AMD all you have to do is:
modprobe -r microcode modprobe microcode
Is the microcode permanently flashed or loaded into some
internal RAM ?
On Saturday 05 February 2011 15:28:22 Enrico Weigelt wrote:
* Volker Armin Hemmann volkerar...@googlemail.com wrote:
and that is all the intel stuff. For AMD all you have to do is:
modprobe -r microcode modprobe microcode
Is the microcode permanently flashed or loaded into some
internal
Am 05.02.2011 14:34, schrieb Enrico Weigelt:
BTW: I'm currently designing an emode/microcode-base computer
architecture built on an matrix of nanocores, they don't have a
concept of main memory, instead a relatively large (linear
addressable) register memory, part of the register space is
btw, very related:
http://blog.flameeyes.eu/2011/01/17/microupdates-for-microcodes
On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy bi...@iinet.net.au wrote:
The bios microcode update is likely an enable setting rather than the
bios actually updating the cpu. You need to do some reading/asking of
the manufacturers (not here) if it bothers you.
Thanks for the links, I
On Tue, Jan 18, 2011 at 7:38 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy bi...@iinet.net.au
wrote:
The bios microcode update is likely an enable setting rather than the
bios actually updating the cpu. You need to do some
btw, very related:
http://blog.flameeyes.eu/2011/01/17/microupdates-for-microcodes
On Tue, Jan 18, 2011 at 8:16 AM, Mark Knecht markkne...@gmail.com wrote:
On Tue, Jan 18, 2011 at 7:38 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy bi...@iinet.net.au
wrote:
The bios microcode update is likely an enable setting
On Tuesday 18 January 2011 09:34:14 Mark Knecht wrote:
On Tue, Jan 18, 2011 at 8:16 AM, Mark Knecht markkne...@gmail.com wrote:
On Tue, Jan 18, 2011 at 7:38 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy bi...@iinet.net.au
On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht markkne...@gmail.com wrote:
OK, I got it to load by hand:
1) emerge microcode-ctl
which also emerges microcode-data. Unfortunately microcode-data looks
to be out of date.
The ebuild for newer versions (including the latest 20101123) is in
On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht markkne...@gmail.com wrote:
OK, I got it to load by hand:
1) emerge microcode-ctl
which also emerges microcode-data. Unfortunately microcode-data looks
to be out
On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht markkne...@gmail.com wrote:
On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht markkne...@gmail.com wrote:
OK, I got it to load by hand:
1) emerge microcode-ctl
which
On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote:
On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht markkne...@gmail.com wrote:
On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht markkne...@gmail.com
wrote:
On Tue, Jan 18, 2011 at 2:56 PM, Mick michaelkintz...@gmail.com wrote:
On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote:
On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht markkne...@gmail.com wrote:
On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
On
On Tuesday 18 January 2011 21:13:49 Paul Hartman wrote:
On Tue, Jan 18, 2011 at 2:56 PM, Mick michaelkintz...@gmail.com wrote:
On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote:
On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht markkne...@gmail.com
wrote:
On Tue, Jan 18, 2011 at 9:55 AM,
On Tue, Jan 18, 2011 at 12:56 PM, Mick michaelkintz...@gmail.com wrote:
SNIP
Is the /etc/microcode.dat path a bug, now that firmware is typically placed in
/lib/firmware?
Shall I create a symlink or raise a bug report?
--
Regards,
Mick
Mick,
I don't think so. Seems to me Gentoo can
- Original Message
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my Crosshair
IV Formula to activate microcodes push in the CPU by the module
microcode ? (AMD Phenom X6 1090T)
Not sure about BIOS, but the Linux Kernel you are running
BRM bm_witn...@yahoo.com [11-01-17 19:16]:
- Original Message
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my Crosshair
IV Formula to activate microcodes push in the CPU by the module
microcode ? (AMD Phenom X6 1090T)
Not sure
On Mon, Jan 17, 2011 at 10:10 AM, BRM bm_witn...@yahoo.com wrote:
- Original Message
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my Crosshair
IV Formula to activate microcodes push in the CPU by the module
microcode ? (AMD Phenom X6
On Monday 17 January 2011 18:21:48 meino.cra...@gmx.de wrote:
Hi,
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my Crosshair
IV Formula to activate microcodes push in the CPU by the module
microcode ? (AMD Phenom X6 1090T)
you ALWAYS have to
On Monday 17 January 2011 10:48:36 Mark Knecht wrote:
On Mon, Jan 17, 2011 at 10:10 AM, BRM bm_witn...@yahoo.com wrote:
- Original Message
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my Crosshair
IV Formula to activate microcodes
On Monday 17 January 2011 19:34:08 meino.cra...@gmx.de wrote:
BRM bm_witn...@yahoo.com [11-01-17 19:16]:
- Original Message
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my
Crosshair
IV Formula to activate microcodes push in
Volker Armin Hemmann volkerar...@googlemail.com [11-01-17 20:16]:
On Monday 17 January 2011 18:21:48 meino.cra...@gmx.de wrote:
Hi,
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my Crosshair
IV Formula to activate microcodes push in the CPU by
On Monday 17 January 2011 20:19:04 meino.cra...@gmx.de wrote:
Volker Armin Hemmann volkerar...@googlemail.com [11-01-17 20:16]:
On Monday 17 January 2011 18:21:48 meino.cra...@gmx.de wrote:
Hi,
I have two questions:
1) Do I have to enable microcode updates in the BIOS of my
Volker Armin Hemmann volkerar...@googlemail.com [11-01-17 20:52]:
On Monday 17 January 2011 20:19:04 meino.cra...@gmx.de wrote:
Volker Armin Hemmann volkerar...@googlemail.com [11-01-17 20:16]:
On Monday 17 January 2011 18:21:48 meino.cra...@gmx.de wrote:
Hi,
I have two
As he said in the previous message, there are almost never changelogs for
microcode updates.
I do, however, have to disagree with *never* disabling microcode updates.
If I recall properly, the AMD Phenom II 720 was able to be unlocked to 4
cores via a misconfiguration that enabled it with ACC.
On Mon, Jan 17, 2011 at 11:57 AM, meino.cra...@gmx.de wrote:
SNIP
So...why should I try unknown code patched into my CPU.
It looks like install this virus from the security point
of view, doesn't ist?
That was my point.
I think the idea Volker is suggesting is the micro-code updates go
from
On Monday 17 January 2011 15:13:54 Jason Weisberger wrote:
As he said in the previous message, there are almost never changelogs for
microcode updates.
I do, however, have to disagree with *never* disabling microcode updates.
If I recall properly, the AMD Phenom II 720 was able to be
On Monday 17 January 2011 12:12:08 Mark Knecht wrote:
On Mon, Jan 17, 2011 at 11:57 AM, meino.cra...@gmx.de wrote:
SNIP
So...why should I try unknown code patched into my CPU.
It looks like install this virus from the security point
of view, doesn't ist?
That was my point.
I
The word probably implies that you have no idea what the statistics were
on getting a perfectly good core were or why they disabled entire batches of
cores based on an error from one.
You are just overdriving your point. If he doesn't want to enable updation
of microcode, it won't hurt anything.
On Monday 17 January 2011 16:59:26 Jason Weisberger wrote:
The word probably implies that you have no idea what the statistics were
on getting a perfectly good core were or why they disabled entire batches of
cores based on an error from one.
You are just overdriving your point. If he
On Mon, 2011-01-17 at 20:46 +0100, Volker Armin Hemmann wrote:
On Monday 17 January 2011 20:19:04 meino.cra...@gmx.de wrote:
Volker Armin Hemmann volkerar...@googlemail.com [11-01-17 20:16]:
On Monday 17 January 2011 18:21:48 meino.cra...@gmx.de wrote:
Hi,
I have two questions:
35 matches
Mail list logo
