On Thu, 08 Nov 2012, Christoph Egger wrote:
> Peter Samuelson writes:
> > ...But it does bring up the question of why intel-microcode and
> > amd64-microcode are not built on kFreeBSD or the Hurd. Maybe those
> > kernels lack a CPU microcode interface?
>
> http://www.freebsd.org/doc/faq/compatib
Hi!
Peter Samuelson writes:
> ...But it does bring up the question of why intel-microcode and
> amd64-microcode are not built on kFreeBSD or the Hurd. Maybe those
> kernels lack a CPU microcode interface?
http://www.freebsd.org/doc/faq/compatibility-processors.html
Though I rather doubt the li
> On Donnerstag, 8. November 2012, Ben Hutchings wrote:
> > > And an annoying technical detail makes it suboptimal to add the microcode
> > > packages as a recommendation of the firmware-linux-nonfree package.
> > ...which is that dpkg does not support architecture-specific relations
> > in binary
Hi,
On Donnerstag, 8. November 2012, Ben Hutchings wrote:
> > And an annoying technical detail makes it suboptimal to add the
microcode
> > packages as a recommendation of the firmware-linux-nonfree package.
> ...which is that dpkg does not support architecture-specific relations
> in binary pack
On Thu, 08 Nov 2012, Carlos Alberto Lopez Perez wrote:
> On 06/11/12 17:05, Henrique de Moraes Holschuh wrote:
> > Still, it did lead me to a possible cause: I am not trying to modprobe
> > "microcode" in the intel-microcode postinst. This can indeed cause the
> > failure to update microcode at p
On 06/11/12 17:05, Henrique de Moraes Holschuh wrote:
> Still, it did lead me to a possible cause: I am not trying to modprobe
> "microcode" in the intel-microcode postinst. This can indeed cause the
> failure to update microcode at package install time.
>
> I forget why I didn't do it that way
On Thu, 2012-11-08 at 02:35 +0200, Adrian Fita wrote:
> On 08/11/12 01:44, Ben Hutchings wrote:
> > On Wed, Nov 07, 2012 at 04:33:00PM -0200, Henrique de Moraes Holschuh wrote:
> >> On Wed, 07 Nov 2012, Adrian Fita wrote:
> >>> Fair enough, but how about having the linux-image packages recommend th
On 08/11/12 01:44, Ben Hutchings wrote:
> On Wed, Nov 07, 2012 at 04:33:00PM -0200, Henrique de Moraes Holschuh wrote:
>> On Wed, 07 Nov 2012, Adrian Fita wrote:
>>> Fair enough, but how about having the linux-image packages recommend the
>>> *microcode packages for installation so users won't get
On Wed, Nov 07, 2012 at 04:33:00PM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 07 Nov 2012, Adrian Fita wrote:
> > Fair enough, but how about having the linux-image packages recommend the
> > *microcode packages for installation so users won't get confused by the
> > message caused by the m
On Wed, 07 Nov 2012, Adrian Fita wrote:
> Fair enough, but how about having the linux-image packages recommend the
> *microcode packages for installation so users won't get confused by the
> message caused by the module trying to load the file with the microcode
> update and not finding it?
I don'
On 07/11/12 02:50, Henrique de Moraes Holschuh wrote:
> On Wed, 07 Nov 2012, Adrian Fita wrote:
>> My CPU is an AMD Turion(tm)X2 Dual Core Mobile RM-76, cpu family: 17, so
>> it doesn't need the amd64-microcode package which contains microcode
>> updates only for cpu families: 10h - 14h & 15h. But
On Wed, 07 Nov 2012, Nikolaus Rath wrote:
> Henrique de Moraes Holschuh writes:
> >> > # iucode_tool --scan-system -vv
> >> > iucode_tool: cpuid kernel driver unavailable, cannot scan system
> >> > processor signatures
> >
> > Hmm, that should happen only if iucode-tool is installed/configured af
Henrique de Moraes Holschuh writes:
>> > # iucode_tool --scan-system -vv
>> > iucode_tool: cpuid kernel driver unavailable, cannot scan system processor
>> > signatures
>
> Hmm, that should happen only if iucode-tool is installed/configured after
> intel-microcode.
I've seen this message too, du
Dropping users and adding pkg-xen-devel and debian-kernel.
On Tue, 2012-11-06 at 15:43 +0100, 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
On Wed, 07 Nov 2012, Adrian Fita wrote:
> My CPU is an AMD Turion(tm)X2 Dual Core Mobile RM-76, cpu family: 17, so
> it doesn't need the amd64-microcode package which contains microcode
> updates only for cpu families: 10h - 14h & 15h. But the microcode kernel
Family 17 (decimal) is family 11h (he
On 05/11/12 22:12, 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.
>
> System Processors from Intel an
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
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
21 matches
Mail list logo
