On Saturday, 13 July 2019 22:01:02 BST Rich Freeman wrote:
> On Sat, Jul 13, 2019 at 4:16 PM Wols Lists wrote:
> > On 13/07/19 20:23, Mick wrote:
> > > Thanks Corbin, I wonder if despite articles about microcode patch
> > > releases to deal with spectre and what not, there are just no patches
> >
On Sat, Jul 13, 2019 at 4:16 PM Wols Lists wrote:
>
> On 13/07/19 20:23, Mick wrote:
> > Thanks Corbin, I wonder if despite articles about microcode patch releases
> > to
> > deal with spectre and what not, there are just no patches made available for
> > my aging AMD CPUs.
>
> Or Spectre and
On 13/07/19 20:23, Mick wrote:
> Thanks Corbin, I wonder if despite articles about microcode patch releases to
> deal with spectre and what not, there are just no patches made available for
> my aging AMD CPUs.
Or Spectre and what not are Intel specific ...
I know a lot of the reports said
On Saturday, 13 July 2019 19:16:18 BST Corbin wrote:
> For reference, the .config file for the kernel should have something
>
> along the lines of this:
> > #
> > # Firmware loader
> > #
> > CONFIG_FW_LOADER=y
> > CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd.bin
> >
On 2019-07-12, Ian Zimmerman wrote:
> On 2019-07-11 21:28, Nuno Silva wrote:
>
>> vlock -n -a
>
> Does vlock work from an XWindow session? Or would I have to use it on
> top of whatever I do to lock the XWindow session - xscreensaver/i3lock
> etc?
It does work from inside X11 here. I can, for
For reference, the .config file for the kernel should have something
along the lines of this:
> #
> # Firmware loader
> #
> CONFIG_FW_LOADER=y
> CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd.bin
> amd-ucode/microcode_amd_fam15h.bin amdgpu/polaris10_ce.bin
> amdgpu/polaris10_ce_2.bin
On Saturday, 13 July 2019 18:42:27 BST Jack wrote:
>
> If linux-firmware is emerged with the savedconfig use flag, then only
> the firmware not deleted from the config file is left.
Yes. I used to do this, but gave up after a while.
> I did find a
> few extras based on the "failed to load..."
On 2019.07.13 13:18, Mick wrote:
On Saturday, 13 July 2019 17:21:40 BST Jack wrote:
> On 2019.07.12 08:18, Mick wrote:
[snip]
And, one question - if I have linux-firmware emerged with
savedconfig use flag set, what's the best/easiest way to hunt
through the actually available firmware,
On Saturday, 13 July 2019 18:18:35 BST Mick wrote:
> or
>
> xv -dc < /boot/EFI/... initramfs-XXX.img | cpio -idmv
Oops! Typo alert! xv should of course be 'xz'. I think you can also use
lzcat.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
On Saturday, 13 July 2019 17:21:40 BST Jack wrote:
> On 2019.07.12 08:18, Mick wrote:
> > https://www.bleepingcomputer.com/news/hardware/amd-releases-spectre-v2-mic
> > rocode-updates-for-cpus-going-back-to-2011/
> I have not yet done any further searching or digging, but that link
> seems to
On 2019-07-12, Nikos Chantziaras wrote:
> On 11/07/2019 20:59, Alan Grimes wrote:
>> 'ey, I have the 2.3 months into an 8-month computation blues...
>> [...]
>> So basically all gentoo updates will have to be done at the end of this
>> run, I'm not really sure when, sometime in the
On 2019.07.12 08:18, Mick wrote:
I'm looking at dmesg output which on my Intel CPUS of various
vintages shows
"microcode updated early ..." but two different AMD APUs of mine do
not show
the same, despite AMD apparently releasing microcode updates going
back to
2011:
On Saturday, 13 July 2019 02:13:00 BST Adam Carter wrote:
> grep fam /proc/cpuinfo
>
> -> 21 = 15h
> -> 22 = 16h
Yep, here's the laptop:
$ grep fam -m1 /proc/cpuinfo
cpu family : 21
and here's the dekstop:
$ grep fam -m1 /proc/cpuinfo
cpu family : 21
--
Regards,
Mick
Thank you both, for your replies.
On Saturday, 13 July 2019 01:56:30 BST Adam Carter wrote:
> > > $ dmesg | grep -i micro
> > > [0.622441] [drm] Loading ARUBA Microcode
> > > [5.763242] [drm] Loading hainan Microcode
> > > [6.653025] microcode: CPU0: patch_level=0x06001119
> > > [
14 matches
Mail list logo
