On Sat, 29 Sep 2012, Eric Valette wrote:
> On 29/09/2012 12:32, Henrique de Moraes Holschuh wrote:
> >If you want to use non-modular, built-in microcode, the documentation of
> >iucode-tool does explain how to trigger the microcode reload after boot. You
> >will have to add it to your system yourse
On 29/09/2012 12:32, Henrique de Moraes Holschuh wrote:
If you want to use non-modular, built-in microcode, the documentation of
iucode-tool does explain how to trigger the microcode reload after boot. You
will have to add it to your system yourself.
Fair enough. Already done. However, during
On Sat, 29 Sep 2012, Eric Valette wrote:
> On 29/09/2012 03:46, Henrique de Moraes Holschuh wrote:
> >1. No html, please.
> >
> >non-initrd is supported. Read the package documentation for the details.
>
> I did. I do not want to compile microcode tool as a module because
Currently using microco
On 29/09/2012 03:46, Henrique de Moraes Holschuh wrote:
1. No html, please.
non-initrd is supported. Read the package documentation for the details.
I did. I do not want to compile microcode tool as a module because
module loading juts slows down the boot process and contrarilly to many
o
> Henrique de Moraes Holschuh writes:
> On Fri, 28 Sep 2012, Eric Valette wrote:
>>
>>
>>
>>
>>
>> Reading the thread about microcode, I wonder why
[…]
> 1. No html, please.
And, especially, no /invalid/ HTML, please.
[…]
--
Advocating the
judici
On Fri, 28 Sep 2012, Eric Valette wrote:
>
>
>
>
>
>
> Reading the thread about microcode, I wonder why
> there is no more any /etc/init.d/microcode.ctl equivalent for
> people like building their own kernel without initrd.
>
> -- eric
>
>
>
Reading the thread about microcode, I wonder why
there is no more any /etc/init.d/microcode.ctl equivalent for
people like building their own kernel without initrd.
-- eric
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with
On Sep 13, Wolodja Wentland wrote:
> The main problem I see is that there seem to be essentially two types of
> packages in non-free right now, namely those that contain firmware/microcode
> (etc) and are crucial for correctly working hardware and the rest.
Yes, this was duly noted at the time th
On Thu, Sep 13, 2012 at 13:45 -0300, Henrique de Moraes Holschuh wrote:
> On Thu, 13 Sep 2012, Nikolaus Rath wrote:
> > I think this should be mentioned somewhere *much* more prominent. I
> > consider myself pretty tech-savy, but only stumbled upon this just now
> > on the this list. Can a non-fre
On Thu, 13 Sep 2012, Andrei POPESCU wrote:
> On Jo, 13 sep 12, 11:29:39, Nikolaus Rath wrote:
> > I think this should be mentioned somewhere *much* more prominent. I
> > consider myself pretty tech-savy, but only stumbled upon this just now
> > on the this list. Can a non-free package be made essen
On Thu, 13 Sep 2012, Nikolaus Rath wrote:
> Henrique de Moraes Holschuh writes:
> > On Thu, 13 Sep 2012, Wolodja Wentland wrote:
> >> On Mon, Sep 10, 2012 at 11:44 +0200, Marco d'Itri wrote:
> >> > Also, we should mention somewhere (the install documentation?) that
> >> > non-free should be enabl
On Jo, 13 sep 12, 11:29:39, Nikolaus Rath wrote:
>
> I think this should be mentioned somewhere *much* more prominent. I
> consider myself pretty tech-savy, but only stumbled upon this just now
> on the this list. Can a non-free package be made essential or
> required? It seems there is really abs
Henrique de Moraes Holschuh writes:
> On Thu, 13 Sep 2012, Wolodja Wentland wrote:
>> On Mon, Sep 10, 2012 at 11:44 +0200, Marco d'Itri wrote:
>> > Also, we should mention somewhere (the install documentation?) that
>> > non-free should be enabled to install microcode fixes which may be
>> > cri
13 matches
Mail list logo
