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
Klaus,
[ 0.760009] amdgpu :0d:00.0: amdgpu: RAS: optional ras ta ucode
is not available
[ 0.767012] amdgpu :0d:00.0: amdgpu: RAP: optional rap ta ucode
is not available
[ 0.767016] amdgpu :0d:00.0: amdgpu: SECUREDISPLAY: securedisplay
ta ucode is not available
It seems
RI*sdma*
> > > /lib/firmware/radeon/kaveri_sdma.bin
> > > /lib/firmware/radeon/KAVERI_sdma.bin
> > >
> > >
> > > I installed sys-firmware/amdgpu-ucode, but KAVERI is not found there
> > > either:
> > >
> > > find /lib/firmware/amdg
> Have you tried this firmware package instead, sys-firmware/amdgpu-ucode?
>
> Do you have the firmware included in your kernel config file?
>
> Device Drivers --->
> Generic Driver Options --->
> -*- Userspace firmware loading support
> [*] In
oes not seen to be available when
> > I use sys-kernel/linux-firmware:
> >
> > find /lib/firmware/radeon/ -iname KAVERI*sdma*
> > /lib/firmware/radeon/kaveri_sdma.bin
> > /lib/firmware/radeon/KAVERI_sdma.bin
> >
> >
> > I installed sys-firmwa
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=&qu
; > > when
> > >
> > > > > I use sys-kernel/linux-firmware:
> > > > >
> > > > > find /lib/firmware/radeon/ -iname KAVERI*sdma*
> > > > > /lib/firmware/radeon/kaveri_sdma.bin
> > > > > /lib/firmware/radeon/KAVER
t; >
> > when
> >
> > > > I use sys-kernel/linux-firmware:
> > > >
> > > > find /lib/firmware/radeon/ -iname KAVERI*sdma*
> > > > /lib/firmware/radeon/kaveri_sdma.bin
> > > > /lib/firmware/radeon/KAVERI_sdma.bin
> > >
On Tuesday 22 Dec 2015 23:02:12 you wrote:
> On Tuesday 22 Dec 2015 21:30:48 Alexander Kapshuk wrote:
> > 'legacy' seems to be disabled by default. See below.
> > # emerge -ap sys-firmware/amdgpu-ucode
> >
> > These are the packages that would be merged, in
On Tue, Jul 14, 2020 at 01:20:39PM -0400, Walter Dnes wrote:
> Still no wireless, but one bit of progress. It seems that the kernel
> does *NOT* like using subdirectories below /lib/firmware. I copied the
> ucode file to /lib/firmware and changed the path appropriately before
&
On Saturday 19 Dec 2015 17:15:04 Alexander Kapshuk wrote:
> > Have you tried this firmware package instead, sys-firmware/amdgpu-ucode?
> >
> > Do you have the firmware included in your kernel config file?
> >
> > Device Drivers --->
&g
On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote:
> On Sun, Dec 20, 2015 at 9:04 PM, Mick <michaelkintz...@gmail.com> wrote:
> > On Saturday 19 Dec 2015 17:15:04 Alexander Kapshuk wrote:
> > > > Have you tried this firmware package instead,
> >
> > sys
On Sun, Dec 20, 2015 at 9:04 PM, Mick <michaelkintz...@gmail.com> wrote:
> On Saturday 19 Dec 2015 17:15:04 Alexander Kapshuk wrote:
> > > Have you tried this firmware package instead,
> sys-firmware/amdgpu-ucode?
> > >
> > > Do you have the firmw
un, Dec 20, 2015 at 9:04 PM, Mick <michaelkintz...@gmail.com> wrote:
> > > On Saturday 19 Dec 2015 17:15:04 Alexander Kapshuk wrote:
> > > > > Have you tried this firmware package instead,
> > >
> > > sys-firmware/amdgpu-ucode?
&g
: amdgpu: RAS: optional ras ta ucode
is not available
[0.767012] amdgpu :0d:00.0: amdgpu: RAP: optional rap ta ucode
is not available
[0.767016] amdgpu :0d:00.0: amdgpu: SECUREDISPLAY: securedisplay
ta ucode is not available
[0.767276] amdgpu :0d:00.0: amdgpu: smu driver
t's an error on the wiki page.
Have you tried this firmware package instead, sys-firmware/amdgpu-ucode?
Do you have the firmware included in your kernel config file?
Device Drivers --->
Generic Driver Options --->
-*- Userspace firmwa
Hi Klaus,
CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd_fam19h.bin
amdgpu/psp_13_0_5_toc.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
[...]
What firmware blobs of linux-firmware has to be installed to support
the gpu of a ryzen-7900X?
CONFIG_EXTRA_FIRMWARE=?
I d
: 'platform': add driver amd-pmf
This is my .config
#
# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_FW_LOADER_PAGED_BUF=y
CONFIG_FW_LOADER_SYSFS=y
CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd_fam19h.bin
amdgpu/psp_13_0_5_toc.bin"
CONFIG_EXTRA_FIRMWARE_DIR=&quo
grep FIRMWARE /usr/src/linux/.config
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-3f-02 intel-ucode/06-3f-04 amdgpu/
polaris10_ce.bin amdgpu/polaris10_k_smc.bin amdgpu/polaris10_mc.bin amdgpu/
polaris10_me.bin amdgpu/polaris10_mec
Corbin Bird wrote:
> On 05/12/2018 03:20 PM, taii...@gmx.com wrote:
>> ^title
>> AMD has released them for all of the recent CPU's and I simply must have
>> them.
>>
>> It seems the last update to amd-ucode on linux-firmware was in 2016,
>> does anyone know
On 05/12/2018 03:20 PM, taii...@gmx.com wrote:
> ^title
> AMD has released them for all of the recent CPU's and I simply must have
> them.
>
> It seems the last update to amd-ucode on linux-firmware was in 2016,
> does anyone know whom I would contact about this who has the j
>
> > The Device Drivers section is exactly where the microcode is included.
> > CONFIG_EXTRA_FIRMWARE is the relevant symbol.
>
> Right. So which of the 95 files under /lib/firmware/intel-ucode do I
> specify? That's in addition to the 14 files I have for my amdgpu.
>
&
include list is radeon/bonaire_sdma1.bin which
doesn't exist on my system using sys-kernel/linux-firmware-20150812. So I'm
assuming it's an error on the wiki page.
Have you tried this firmware package instead, sys-firmware/amdgpu-ucode?
Do you have the firmware incl
re Version ENC: 1.15 DEC: 3 VEP: 0
Revision: 0
[2.924510] amdgpu :2a:00.0: amdgpu: Will use PSP to load VCN firmware
[2.945168] [drm] reserve 0x40 from 0xf47fc0 for PSP TMR
[3.004533] amdgpu :2a:00.0: amdgpu: RAS: optional ras ta ucode is not
available
[3.009017] a
ctly where the microcode is included.
> CONFIG_EXTRA_FIRMWARE is the relevant symbol.
Right. So which of the 95 files under /lib/firmware/intel-ucode do I
specify? That's in addition to the 14 files I have for my amdgpu.
--
Regards,
Peter.
evice Drivers;
>> > there's no such field under Firmware.
>>
>> The Device Drivers section is exactly where the microcode is included.
>> CONFIG_EXTRA_FIRMWARE is the relevant symbol.
>
> Right. So which of the 95 files under /lib/firmware/intel-ucode do I
> specify? Th
system using sys-kernel/linux-firmware-20150812.
> So I'm assuming it's an error on the wiki page.
>
Have you tried this firmware package instead, sys-firmware/amdgpu-ucode?
Do you have the firmware included in your kernel config file?
Device Drivers --->
Generic Dri
> ~sci-misc/boinc-7.4.42
> sys-apps/nvme-cli
> sys-boot/gummiboot
> ~sys-devel/clang-3.6.2
> ~sys-devel/llvm-3.6.2
> sys-firmware/amdgpu-ucode
> ~sys-kernel/gentoo-sources-4.4.6
> ~x11-drivers/xf86-video-amdgpu-1.0.1
In fact that wasn't enough. Everything was working bu
On Tuesday 22 Dec 2015 23:07:24 Mick wrote:
> On Tuesday 22 Dec 2015 23:02:12 you wrote:
> > On Tuesday 22 Dec 2015 21:30:48 Alexander Kapshuk wrote:
> > > 'legacy' seems to be disabled by default. See below.
> > > # emerge -ap sys-firmware/amdgpu-ucode
> >
On 05/20/2018 06:46 PM, Adam Carter wrote:
> How often does the linux-firmware package update? On a schedule or as
>
> needed?
>
>
> There's a version bump request bug in for these and new AMDGPU
> firmware. Hopefully it will get processed quickly.
>
> https://bug
and Intel Vt-D are switched on in the UEFI BIOS. I
can't see anything else in there that might affect this.
In case it's a GPU problem I've also tried all available versions of amdgpu-
ucode and linux-firmware. This is a new box with a Radeon R9 380 display card
which shows up thus:
# lspci -ns
Device Drivers section is exactly where the microcode is included.
> > CONFIG_EXTRA_FIRMWARE is the relevant symbol.
>
> Right. So which of the 95 files under /lib/firmware/intel-ucode do I
> specify? That's in addition to the 14 files I have for my amdgpu.
I found the simplest way to
t; there's no such field under Firmware.
> >
> > The Device Drivers section is exactly where the microcode is included.
> > CONFIG_EXTRA_FIRMWARE is the relevant symbol.
>
> Right. So which of the 95 files under /lib/firmware/intel-ucode do I
> specify? That's in
can see to do that in menuconfig is under Device Drivers;
> > > > there's no such field under Firmware.
> > >
> > > The Device Drivers section is exactly where the microcode is included.
> > > CONFIG_EXTRA_FIRMWARE is the relevant symbol.
> >
> &
;> installed software in a non-standard prefix.
>
>> Alternatively, you may set the environment variables AMDGPU_CFLAGS
>> and AMDGPU_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>
> [ ]
>
>> $ eix libdrm_amdgpu
>>
.. ]
> $ eix libdrm_amdgpu
> No matches found
> So, there is no libdrm_amdgpu in my updated portage tree but
> media-libs/mesa-13.0.5::gentoo seems to demand it!
> $ eix amdgpu
> * sys-firmware/amdgpu-ucode
> Available versions: 20160628 20161121 {legacy}
> Hom
/amdgpu-ucode
~sys-kernel/gentoo-sources-4.4.6
~x11-drivers/xf86-video-amdgpu-1.0.1
-
That's the excitement. The disappointment is with KMail. The reason I bought
the new box is that the old one had developed a hardware fault, somewhere in
the PCI region of the chipset
esktop.
>
> This may be a bad interaction with the xorg-driver for my AMD GPU, which
> has only been on the market for about a year. Though
> sys-firmware/amdgpu-ucode hasn't changed since June.
I found from Xorg.0.log that X11 wasn't finding an evdev module, even though
I had INPUT_DEVICES
> in the middle of another or on a blank background, and it's hard to see
> > just which is the currently active desktop.
> >
> > This may be a bad interaction with the xorg-driver for my AMD GPU, which
> > has only been on the market for about a year. Though
> &g
may be a bad interaction with the xorg-driver for my AMD GPU, which
> > > has only been on the market for about a year. Though
> > > sys-firmware/amdgpu-ucode hasn't changed since June.
> >
> > I found from Xorg.0.log that X11 wasn't finding an evdev module, even
> &g
e
> graphics card and the Intel CPU, and I've been declaring the file names in
> CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR. As the display works
> fine, and so does opencl on the GPU since I emerged dev-libs/amdgpu-pro-
> opencl, I assume that the firmware is being loaded.
. If I switch desktops too many times, or too often or
> something, the desktop becomes unusable until I reboot (I haven't tried just
> restarting xdm). It flickers rapidly, bits of one desktop are shown in the
> middle of another or on a blank background, and it's hard to see just which
> is the currently active desktop.
>
> This may be a bad interaction with the xorg-driver for my AMD GPU, which has
> only been on the market for about a year. Though sys-firmware/amdgpu-ucode
> hasn't changed since June.
I switch around a lot between 4 virtual desktops and 2 displays.
Haven't experienced that myself.
Difference: Using Intel CPU and Nvidia GPU.
--
Joost
hoped the problem I have had
been fixed, but no. If I switch desktops too many times, or too often or
something, the desktop becomes unusable until I reboot (I haven't tried just
restarting xdm). It flickers rapidly, bits of one desktop are shown in the
middle of another or on a blank background, and it's hard to see just which
is the currently active desktop.
This may be a bad interaction with the xorg-driver for my AMD GPU, which has
only been on the market for about a year. Though sys-firmware/amdgpu-ucode
hasn't changed since June.
--
Rgds
Peter
e ebuild environment file is located at
'/var/tmp/portage/media-libs/mesa-13.0.5/temp/environment'.
* Working directory:
'/var/tmp/portage/media-libs/mesa-13.0.5/work/mesa-13.0.5-abi_x86_32.x86'
* S: '/var/tmp/portage/media-libs/mesa-13.0.5/work/mesa-13.0.5'
$ eix libdrm_amdgpu
No matches found
44 matches
Mail list logo
