On Saturday 05 February 2011 15:28:22 Enrico Weigelt wrote:
> * Volker Armin Hemmann 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 ?
loaded. mi
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 i
On Saturday 05 February 2011 15:28:22 Enrico Weigelt wrote:
> * Volker Armin Hemmann 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 ?
loaded. mi
Enrico Weigelt [11-02-05 16:08]:
> * Volker Armin Hemmann 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
> --
> ---
* Volker Armin Hemmann 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
--
--
E
* Volker Armin Hemmann 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 interpreted an algol
bytecode (th
btw, very related:
http://blog.flameeyes.eu/2011/01/17/microupdates-for-microcodes
On Tue, Jan 18, 2011 at 12:56 PM, Mick wrote:
>
> 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 put this where ever it
On Tuesday 18 January 2011 21:13:49 Paul Hartman wrote:
> On Tue, Jan 18, 2011 at 2:56 PM, Mick wrote:
> > On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote:
> >> On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht
wrote:
> >> > On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
> >> >
> >> > wrote:
On Tue, Jan 18, 2011 at 2:56 PM, Mick wrote:
> On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote:
>> On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht wrote:
>> > On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
>> >
>> > wrote:
>> >> On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht
> wrote:
>> >>>
On Tuesday 18 January 2011 20:42:05 Paul Hartman wrote:
> On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht wrote:
> > On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
> >
> > wrote:
> >> On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht
wrote:
> >>> OK, I got it to load by hand:
> >>>
> >>> 1) emerge m
On Tue, Jan 18, 2011 at 12:21 PM, Mark Knecht wrote:
> On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
> wrote:
>> On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht wrote:
>>> OK, I got it to load by hand:
>>>
>>> 1) emerge microcode-ctl
>>>
>>> which also emerges microcode-data. Unfortunately microco
On Tue, Jan 18, 2011 at 9:55 AM, Paul Hartman
wrote:
> On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht 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 ver
On Tue, Jan 18, 2011 at 11:34 AM, Mark Knecht 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
portage as ~amd64 and
On Tuesday 18 January 2011 09:34:14 Mark Knecht wrote:
> On Tue, Jan 18, 2011 at 8:16 AM, Mark Knecht wrote:
> > On Tue, Jan 18, 2011 at 7:38 AM, Paul Hartman
> >
> > wrote:
> >> On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy
wrote:
> >>> The bios microcode update is likely an enable sett
On Tue, Jan 18, 2011 at 8:16 AM, Mark Knecht wrote:
> On Tue, Jan 18, 2011 at 7:38 AM, Paul Hartman
> wrote:
>> On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy
>> wrote:
>>> The bios microcode update is likely an enable setting rather than the
>>> bios actually updating the cpu. You need t
btw, very related:
http://blog.flameeyes.eu/2011/01/17/microupdates-for-microcodes
On Tue, Jan 18, 2011 at 7:38 AM, Paul Hartman
wrote:
> On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy
> 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) i
On Mon, Jan 17, 2011 at 10:29 PM, William Kenworthy 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 didn't realize they
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 [11-01-17 20:16]:
> > > On Monday 17 January 2011 18:21:48 meino.cra...@gmx.de wrote:
> > > > Hi,
> > > >
> > > > I have two questions:
> > > >
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
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 12:12:08 Mark Knecht wrote:
> On Mon, Jan 17, 2011 at 11:57 AM, wrote:
>
>
> > 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
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 unl
On Mon, Jan 17, 2011 at 11:57 AM, wrote:
> 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 AMD (who understa
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. AM
Volker Armin Hemmann [11-01-17 20:52]:
> On Monday 17 January 2011 20:19:04 meino.cra...@gmx.de wrote:
> > Volker Armin Hemmann [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
On Monday 17 January 2011 20:19:04 meino.cra...@gmx.de wrote:
> Volker Armin Hemmann [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
>
Volker Armin Hemmann [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 the module
> >
On Monday 17 January 2011 19:34:08 meino.cra...@gmx.de wrote:
> BRM [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 th
On Monday 17 January 2011 10:48:36 Mark Knecht wrote:
> On Mon, Jan 17, 2011 at 10:10 AM, BRM 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
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 ha
On Mon, Jan 17, 2011 at 10:10 AM, BRM 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 1090T)
>
>
BRM [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 about
- 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 runni
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)
2) Does anyone know, what these microcodes do? They are fixes for...
...what?
Thank
36 matches
Mail list logo
