Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
> > Comparing firmware between kernels 4.12.12 and 4.14.7 I see: > > $ ls -l /usr/src/linux-4.12.12-gentoo/firmware/radeon/RV730* > -rw-r--r-- 1 root root 5440 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_me.bin > -rw-r--r-- 1 root root 454 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_me.bin.gen.S > -rw-r--r-- 1 root root 6704 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_me.bin.gen.o > -rw-r--r-- 1 root root 14972 Jul 3 00:07 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_me.bin.ihex > -rw-r--r-- 1 root root 3392 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_pfp.bin > -rw-r--r-- 1 root root 461 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_pfp.bin.gen.S > -rw-r--r-- 1 root root 4656 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_pfp.bin.gen.o > -rw-r--r-- 1 root root 9340 Jul 3 00:07 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_pfp.bin.ihex > -rw-r--r-- 1 root root 467 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_smc.bin.gen.S > -rw-r--r-- 1 root root 17952 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ > firmware/radeon/RV730_smc.bin.gen.o > > > $ ls -l /usr/src/linux-4.14.7-gentoo/firmware/radeon/RV730* > -rw-r--r-- 1 root root 467 Dec 20 11:46 /usr/src/linux-4.14.7-gentoo/ > firmware/radeon/RV730_smc.bin.gen.S > -rw-r--r-- 1 root root 17952 Dec 20 11:46 /usr/src/linux-4.14.7-gentoo/ > firmware/radeon/RV730_smc.bin.gen.o > > > As you can see above there is a marked difference between the firmware > built > by the two kernels. In any case, my '/lib/firmware/' path contains: > > $ ls -l /lib/firmware/radeon/RV730* > -rw-r--r-- 1 root root 5440 Dec 20 17:29 /lib/firmware/radeon/RV730_me. > bin > -rw-r--r-- 1 root root 3392 Dec 20 17:29 /lib/firmware/radeon/RV730_ > pfp.bin > -rw-r--r-- 1 root root 16684 Dec 20 17:29 /lib/firmware/radeon/RV730_ > smc.bin > Earlier I saw CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1e-05 radeon/R700_rlc.bin radeon/RV730_smc.bin radeon/RV710_uvd.bin" For radeon/R700_rlc.bin $ find /lib/firmware/ -name \*R700\* /lib/firmware/radeon/R700_rlc.bin For radeon/RV730_smc.bin $ find /lib/firmware/ -name \*RV730\* /lib/firmware/radeon/RV730_pfp.bin /lib/firmware/radeon/RV730_smc.bin /lib/firmware/radeon/RV730_me.bin For adeon/RV710_uvd.bin $ find /lib/firmware/ -name \*RV710\* /lib/firmware/radeon/RV710_me.bin /lib/firmware/radeon/RV710_pfp.bin /lib/firmware/radeon/RV710_smc.bin /lib/firmware/radeon/RV710_uvd.bin So it looks like you're trying to load firmware from three different models. Run lspci -v to determine which is correct one, then load all the firmwares for that model.
Re: [gentoo-user] Where are the AMD microcode updates for spectre?
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 whom I would contact about this who has the juice to do >> it? I need fam15h. >> >> AMD is being annoying and not releasing them to the plebians only OEM >> partners - I assume perhaps to encourage people to buy new hardware as >> most OEM's won't release BIOS updates for older boards. >> >> Thanks. > . > > Emerge this package : "sys-kernel/linux-firmware" > > You can find the blobs in : /lib/firmware/amd-ucode/ > > If you already have "sys-kernel/linux-firmware" emerged and the blobs > aren't showing, un-merge it, and the re-emerge it. > > . > > Gentoo does have the newer microcode blobs stashed on a server ( > somewhere ). > > That does pull in the blobs for : > > Fam10h ( microcode_amd.bin ) > > Fam15h ( microcode_amd_fam15h.bin ) > > Fam16h ( microcode_amd_fam16h.bin ) > > Fam17h ( microcode_amd_fam17h.bin ) > > . > > If you have an AMDGPU and use the "amdgpu" driver, firmware will be here > : /lib/firmware/amdgpu > > . > > Corbin > If it helps the OP, I haven't done anything special, just regular updates and I have this here: root@fireball / # ls -al /lib/firmware/amd-ucode/microcode_amd* -rw-r--r-- 1 root root 12684 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd.bin -rw-r--r-- 1 root root 490 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd.bin.asc -rw-r--r-- 1 root root 7876 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd_fam15h.bin -rw-r--r-- 1 root root 473 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd_fam15h.bin.asc -rw-r--r-- 1 root root 3510 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd_fam16h.bin -rw-r--r-- 1 root root 473 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd_fam16h.bin.asc -rw-r--r-- 1 root root 3252 Jan 7 18:19 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin root@fireball / # equery list -p linux-firmware * Searching for linux-firmware ... [IP-] [ ] sys-kernel/linux-firmware-20180103-r1:0 [-P-] [ ~] sys-kernel/linux-firmware-20180213:0 [-P-] [ ~] sys-kernel/linux-firmware-20180314:0 [-P-] [ ~] sys-kernel/linux-firmware-20180412:0 [-P-] [ ~] sys-kernel/linux-firmware-20180416:0 [-P-] [ -] sys-kernel/linux-firmware-:0 root@fireball / # genlop -t linux-firmware * sys-kernel/linux-firmware <<< SNIP old stuff >>> Thu Dec 7 02:00:18 2017 >>> sys-kernel/linux-firmware-20170314 merge time: 2 minutes and 51 seconds. Sun Jan 7 18:21:19 2018 >>> sys-kernel/linux-firmware-20180103-r1 merge time: 33 minutes and 21 seconds. root@fireball / # It seems based on the time stamp and genlop, it was installed back in January. I update at least once a week, twice on occasion if I know there is a big update for say KDE or something. Hope that helps. Gives something for the OP to compare to if nothing else. ;-) Dale :-) :-)
Re: [gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
On 12/13/2020 04:33 PM, Neil Bothwick wrote:
> On Sun, 13 Dec 2020 11:52:51 -0700, the...@sys-concept.com wrote:
>
>> I have "linux-firmware" installed but there is a "?" mark beside it
>>
>> eix linux-firmware
>> [?] sys-kernel/linux-firmware
>> Installed versions: 20201022-r3
>>
> It means the version you have installed is no longer in the tree. You
> should update to the latest.
>
Something is wrong, I just --sync and reinstall linux-firmware but the output
is still the same:
eix linux-firmware
[?] sys-kernel/linux-firmware
Available versions: 20200316^bsd 20200421^bsd 20200519^bsd 20200619^bsd
20200721^bsd 20200817^bsd 20200918^bsd 20201022-r2^bstd ***l^bstd
{initramfs +redistributable savedconfig unknown-license}
Installed versions: 20201022-r3^bst(05:30:05 PM
12/13/2020)(redistributable -initramfs -savedconfig -unknown-license)
Homepage:
https://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git
Description: Linux firmware files
Re: [gentoo-user] Eliminating unwanted linux-firmware blobs.
On Fri, Jun 28, 2024, 18:28 Vitaliy Perekhovy wrote: > On Fri, Jun 28, 2024 at 04:17:23PM -, Grant Edwards wrote: > > Is there any graceful way to handle the elimination of unwanted > > linux-firmware blobs when doing an update? > > > > I believe I understand the process as outlined at > > https://wiki.gentoo.org/wiki/Linux_firmware: > > > > 1. install/upgrade sys-kernel/linux-firmware > > 2. edit /etc/portage/savedconfig/sys-kernel/linux-firmware-ddmm > > 3. re-emerge sys-kernel/linux-firmware with the savedcofnig USE flag > > > > I've tried that a few times, but it's rather annoying to have to do > > that every time linux-firmware gets updated. > > > > AFAICT, the list of three or four blobs that I actually need on a > > specific machine never changes. > > > > It seems like there ought to be a way to configure that required > > firmware list and have the emerge -u "just work", but I can't find > > it. Have I missed something? > > > > Yes, I know... > > Disk space is cheap. > > Premature optimization ... > > etc. > > > > It still annoys me. > > > > -- > > Grant > > Save your firmware list in > /etc/portage/savedconfig/sys-kernel/linux-firmware > That's it. > > -- > Best regards, > Vitaliy Perekhovy > After every update to sys-kernel/linux-firmware, you may get the following output: * IMPORTANT: config file '/etc/portage/savedconfig/sys-kernel/linux-firmware-20240610' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. It's a good idea to compare this file to your current file to see if any firmware blobs have gotten updates. However, it's important to then discard this file by choosing `z` in dispatch-conf. Regards, Waldo >
Re: [gentoo-user] Eliminating unwanted linux-firmware blobs.
On Fri, Jun 28, 2024 at 04:17:23PM -, Grant Edwards wrote: > Is there any graceful way to handle the elimination of unwanted > linux-firmware blobs when doing an update? > > I believe I understand the process as outlined at > https://wiki.gentoo.org/wiki/Linux_firmware: > > 1. install/upgrade sys-kernel/linux-firmware > 2. edit /etc/portage/savedconfig/sys-kernel/linux-firmware-ddmm > 3. re-emerge sys-kernel/linux-firmware with the savedcofnig USE flag > > I've tried that a few times, but it's rather annoying to have to do > that every time linux-firmware gets updated. > > AFAICT, the list of three or four blobs that I actually need on a > specific machine never changes. > > It seems like there ought to be a way to configure that required > firmware list and have the emerge -u "just work", but I can't find > it. Have I missed something? > > Yes, I know... > Disk space is cheap. > Premature optimization ... > etc. > > It still annoys me. > > -- > Grant Save your firmware list in /etc/portage/savedconfig/sys-kernel/linux-firmware That's it. -- Best regards, Vitaliy Perekhovy signature.asc Description: PGP signature
Re: [gentoo-user] Eliminating unwanted linux-firmware blobs.
Remove the date.so it becomes /etc/portage/savedconfig/sys-kernel/linux-firmware then it applies to all of them and not the specified version. Hope that helps From: Grant Edwards Sent: Friday, June 28, 2024 12:17 PM To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Eliminating unwanted linux-firmware blobs. Is there any graceful way to handle the elimination of unwanted linux-firmware blobs when doing an update? I believe I understand the process as outlined at https://wiki.gentoo.org/wiki/Linux_firmware: 1. install/upgrade sys-kernel/linux-firmware 2. edit /etc/portage/savedconfig/sys-kernel/linux-firmware-ddmm 3. re-emerge sys-kernel/linux-firmware with the savedcofnig USE flag I've tried that a few times, but it's rather annoying to have to do that every time linux-firmware gets updated. AFAICT, the list of three or four blobs that I actually need on a specific machine never changes. It seems like there ought to be a way to configure that required firmware list and have the emerge -u "just work", but I can't find it. Have I missed something? Yes, I know... Disk space is cheap. Premature optimization ... etc. It still annoys me. -- Grant
Re: [gentoo-user] r8169 unable to apply firmware patch
>> Maybe you have an older firmware installed from a different package? >> Run emerge -p linux-firmware on that box to see if there's a blocker. > > linux-firmware is blocked by radeon-ucode and rt61-firmware, I'm guessing that radeon-ucode and rt61-firmware and all the others are being deprecated in favour of linux-firmware, but i don't recall seeing an elog on it. > but now > that I look closer I realize that ifconfig doesn't show an eth0 > interface at all even though lspci -v shows: > > Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI > Express Gigabit Ethernet controller > ... > Kernel driver in use: r8169 > > Shouldn't the eth0 interface appear in ifconfig once the r8169 driver > is loaded? dmesg has no mention of eth0 or r8169. That's odd. Does that box still have the failed loading firmware error? Perhaps missing firmware stops eth0 from being created. I'd try installing linux-fireware and trying again (assuming you havent already). >>> I guess linux-firmware is a package released by the kernel folks >>> containing certain firmware blobs? It looks like rt73 is in there but >>> not b43. >> >> Maybe these? >> /lib/firmware/brcm/bcm4329-fullmac-4.bin >> /lib/firmware/brcm/bcm4329-fullmac-4.txt >> /lib/firmware/brcm/bcm43xx-0.fw >> /lib/firmware/brcm/bcm43xx_hdr-0.fw >> /lib/firmware/LICENCE.broadcom_bcm43xx > > Right again. The contents of /lib/firmware/b43 and /lib/firmware/brcm > are completely different, but you think either one will work with a > b43 device? The driver will know which one it wants. You could grep the source for the firmware file names to see which it pulls in.
Re: [gentoo-user] r8169 unable to apply firmware patch
> That fixed it. Thank you very much. I'm a little puzzled because I > don't get the "unable to apply firmware patch" messages on my desktop > which also uses the r8169 driver and doesn't have linux-firmware > installed. Maybe you have an older firmware installed from a different package? Run emerge -p linux-firmware on that box to see if there's a blocker. > I guess linux-firmware is a package released by the kernel folks > containing certain firmware blobs? It looks like rt73 is in there but > not b43. Maybe these? /lib/firmware/brcm/bcm4329-fullmac-4.bin /lib/firmware/brcm/bcm4329-fullmac-4.txt /lib/firmware/brcm/bcm43xx-0.fw /lib/firmware/brcm/bcm43xx_hdr-0.fw /lib/firmware/LICENCE.broadcom_bcm43xx
Re: [gentoo-user] r8169 unable to apply firmware patch
>> That fixed it. Thank you very much. I'm a little puzzled because I >> don't get the "unable to apply firmware patch" messages on my desktop >> which also uses the r8169 driver and doesn't have linux-firmware >> installed. > > Maybe you have an older firmware installed from a different package? > Run emerge -p linux-firmware on that box to see if there's a blocker. linux-firmware is blocked by radeon-ucode and rt61-firmware, but now that I look closer I realize that ifconfig doesn't show an eth0 interface at all even though lspci -v shows: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller ... Kernel driver in use: r8169 Shouldn't the eth0 interface appear in ifconfig once the r8169 driver is loaded? dmesg has no mention of eth0 or r8169. >> I guess linux-firmware is a package released by the kernel folks >> containing certain firmware blobs? It looks like rt73 is in there but >> not b43. > > Maybe these? > /lib/firmware/brcm/bcm4329-fullmac-4.bin > /lib/firmware/brcm/bcm4329-fullmac-4.txt > /lib/firmware/brcm/bcm43xx-0.fw > /lib/firmware/brcm/bcm43xx_hdr-0.fw > /lib/firmware/LICENCE.broadcom_bcm43xx Right again. The contents of /lib/firmware/b43 and /lib/firmware/brcm are completely different, but you think either one will work with a b43 device? - Grant
[gentoo-user] Eliminating unwanted linux-firmware blobs.
Is there any graceful way to handle the elimination of unwanted linux-firmware blobs when doing an update? I believe I understand the process as outlined at https://wiki.gentoo.org/wiki/Linux_firmware: 1. install/upgrade sys-kernel/linux-firmware 2. edit /etc/portage/savedconfig/sys-kernel/linux-firmware-ddmm 3. re-emerge sys-kernel/linux-firmware with the savedcofnig USE flag I've tried that a few times, but it's rather annoying to have to do that every time linux-firmware gets updated. AFAICT, the list of three or four blobs that I actually need on a specific machine never changes. It seems like there ought to be a way to configure that required firmware list and have the emerge -u "just work", but I can't find it. Have I missed something? Yes, I know... Disk space is cheap. Premature optimization ... etc. It still annoys me. -- Grant
Re: [gentoo-user] Loading a Firmware Module By hand?
On Mon, 18 Dec 2017 19:15:04 + Hunter Jozwiak wrote: On 12/18/17, Mick wrote: On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote: Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version 9 as well, but that didn't help matters, either. Nor did compiling the firmware into the kernel; either 4.14 is too old, or it is too new. I'd think they are both too new? I tried copying the firmware my live iso was using, but that didn't help either. If the live iso works, start with using the same kernel release and linux- firmware version, to see if this works as expected on your installation. Then update kernel sources and firmware to the latest stable and see if this works too. From there on you can move into ~arch to find the version at which things break. -- Regards, Mick Okay, here are the dmesg messages: https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/ The present kernel configuration, as of yesterday evening: https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/ Make and model of the offending card: Qualcomm 6174 revision 20. Not exactly what the -2 error means, but I will try as Mick suggested and work my way forwards to see what I can get working. Hi, I was a little bit confused from your earlier mentioned /lib/firmware/ath10k/QCABLEFAGD/HW3.0 I wonder where this firmware come from. I cannot find it, neither with the identifier ‘QCABLEFAGD’ nor an upper cased ‘HW3.0’ directory in [1][2][3][4]. Your log tells an other story now. As far as I can tell: “Direct firmware load for […] failed with error -2” comes from _request_firmware and fw_get_filesystem_firmware functions in file [5]. The symbolic error name ENOENT, see `man 3 errno`, means something like ‘No such element’ or ‘No such file or directory’. Even CONFIG_EXTRA_FIRMWARE_DIR defaults to ‘/lib/firmware’, there should be whether an entry ‘# CONFIG_EXTRA_FIRMWARE_DIR is not set’ or something like ‘CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"’ in your config. Its unclear to me why it is not there. If you want to build into the kernel again, check ‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set: CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" Hope that helps. [1] <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ath10k> [2] <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/ath/ath10k/hw.h?h=v4.14.7> [3] <https://github.com/kvalo/ath10k-firmware> [4] <https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware> [5] <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/base/firmware_class.c?h=v4.14.7#n386> -- Regards, floyd
Re: [gentoo-user] which microcode gets loaded?
Hello, On Mon, 14 May 2018, tu...@posteo.de wrote: [..] >cat /proc/cpuinfo (from one of the six cores): >processor : 4 >vendor_id : AuthenticAMD >cpu family : 16 ^^ decimal = 10h(ex) >model : 10 >model name : AMD Phenom(tm) II X6 1090T Processor [..] >from linux-firmware (related lines): >/lib/firmware/amd-ucode/microcode_amd.bin >/lib/firmware/amd-ucode/microcode_amd_fam15h.bin >/lib/firmware/amd-ucode/microcode_amd_fam16h.bin *** >/lib/firmware/amd-ucode/microcode_amd_fam17h.bin > >(***) I think, these microcodes do I need... Nope. You need microcode_amd.bin, if any. Go into the git-repo for sys-kernel/linux-firmware[1] and you'll find that the non-versioned microcode_amd.bin is for fam10h - fam14h. HTH, -dnh [1] https://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git -- I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams
Re: [gentoo-user] No wifi
One thing I should've mentioned in the first post is that booting from the minimal install USB, wlan0 does show up, so the hardware works. On Tue, Jul 14, 2020 at 05:59:37AM +0100, Ashley Dixon wrote > > It doesn't look like it's loading the firmware. Are there any obvious > firmware-loading errors in dmesg ? What is ASPM and what is error -2? BTW, on my first attempt, when I accidentally tried a non-existant firmware path, the kernel compile died early on. Here is what I get in dmesg with ucode 8.83.5.1-1 [0.728996] Intel(R) Wireless WiFi driver for Linux [0.728998] Copyright(c) 2003- 2015 Intel Corporation [0.729099] iwlwifi :03:00.0: can't disable ASPM; OS doesn't have ASPM control [0.729298] iwlwifi :03:00.0: Direct firmware load for iwlwifi-5000-5.ucode failed with error -2 [0.729311] iwlwifi :03:00.0: Direct firmware load for iwlwifi-5000-4.ucode failed with error -2 [0.729322] iwlwifi :03:00.0: Direct firmware load for iwlwifi-5000-3.ucode failed with error -2 [0.729334] iwlwifi :03:00.0: Direct firmware load for iwlwifi-5000-2.ucode failed with error -2 [0.729346] iwlwifi :03:00.0: Direct firmware load for iwlwifi-5000-1.ucode failed with error -2 [0.729351] iwlwifi :03:00.0: no suitable firmware found! [0.729354] iwlwifi :03:00.0: minimum version required: iwlwifi-5000-1 [0.729359] iwlwifi :03:00.0: maximum version supported: iwlwifi-5000-5 [0.729362] iwlwifi :03:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > That looks fine, although why are you using such an outdated version > of the microcode ? For kernels 2.6.38+, you can use 8.83.5.1-1. The way the items lined up on the webpage, I mis-interpreted it to mean one driver for 5100AGN, one for 5300AGN, and one for 5350AGN. See attachment. > Perhaps it would be better to install it from > the Gentoo-provided firmware package ? Amend > /etc/portage/savedconfig/sys-kernel/linux-firmware to include the > appropriate entries (listing at [1]), and emerge `linux-firmware` > with the `savedconfig` USE-flag. > > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ I'll do that next if there's nothing obvious here. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Loading a Firmware Module By hand?
On 12/18/17, Floyd Anderson wrote: > On Mon, 18 Dec 2017 19:15:04 + > Hunter Jozwiak wrote: >>On 12/18/17, Mick wrote: >>> On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote: >>>> Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version >>>> 9 as well, but that didn't help matters, either. Nor did >>>> compiling the firmware into the kernel; either 4.14 is too old, or it >>>> is too new. >>> >>> I'd think they are both too new? >>> >>>> I tried copying the firmware my live iso was using, but >>>> that didn't help either. >>> >>> If the live iso works, start with using the same kernel release and >>> linux- >>> firmware version, to see if this works as expected on your installation. >>> Then >>> update kernel sources and firmware to the latest stable and see if this >>> works >>> too. >>> >>> From there on you can move into ~arch to find the version at which >>> things >>> break. >>> -- >>> Regards, >>> Mick >>Okay, here are the dmesg messages: >>https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/ >>The present kernel configuration, as of yesterday evening: >>https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/ >>Make and model of the offending card: Qualcomm 6174 revision 20. >>Not exactly what the -2 error means, but I will try as Mick suggested >>and work my way forwards to see what I can get working. >> > > Hi, > > I was a little bit confused from your earlier mentioned > > /lib/firmware/ath10k/QCABLEFAGD/HW3.0 > > I wonder where this firmware come from. I cannot find it, neither with > the identifier ‘QCABLEFAGD’ nor an upper cased ‘HW3.0’ directory in > [1][2][3][4]. > > Your log tells an other story now. As far as I can tell: > > “Direct firmware load for […] failed with error -2” > > comes from _request_firmware and fw_get_filesystem_firmware functions in > file [5]. The symbolic error name ENOENT, see `man 3 errno`, means > something like ‘No such element’ or ‘No such file or directory’. > > Even CONFIG_EXTRA_FIRMWARE_DIR defaults to ‘/lib/firmware’, there should > be whether an entry ‘# CONFIG_EXTRA_FIRMWARE_DIR is not set’ or > something like ‘CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"’ in your > config. Its unclear to me why it is not there. > > If you want to build into the kernel again, check > ‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set: > > CONFIG_FIRMWARE_IN_KERNEL=y > CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin" > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" > > Hope that helps. > > > [1] > <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ath10k> > [2] > <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/net/wireless/ath/ath10k/hw.h?h=v4.14.7> > [3] <https://github.com/kvalo/ath10k-firmware> > [4] <https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware> > [5] > <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/base/firmware_class.c?h=v4.14.7#n386> > > > > -- > Regards, > floyd > > > That particular firmware does not exist. I am trying to figure how far back I need to rollback the kernel. Sabayon's live ISO is using 4.13.0, but that is no longer in the tree. Not sure if I need to go back to the 4.12 ebuilds, or if 4.13.5 will suit my needs; perhaps there is a bit of source code that I can look at to see what is being used for the firmware?
Re: [gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
On Monday, 14 December 2020 08:36:03 GMT Neil Bothwick wrote:
> On Sun, 13 Dec 2020 17:32:12 -0700, the...@sys-concept.com wrote:
> > > It means the version you have installed is no longer in the tree. You
> > > should update to the latest.
> >
> > Something is wrong, I just --sync and reinstall linux-firmware but the
> > output is still the same:
> >
> > eix linux-firmware
> > [?] sys-kernel/linux-firmware
> >
> > Available versions: 20200316^bsd 20200421^bsd 20200519^bsd
> >
> > 20200619^bsd 20200721^bsd 20200817^bsd 20200918^bsd 20201022-r2^bstd
> > ***l^bstd {initramfs +redistributable savedconfig
> > unknown-license} Installed versions: 20201022-r3^
> > 20201022-r3^bst(05:30:05 PM 12/13/2020)(redistributable -initramfs
> > -savedconfig -unknown-license)
>
> This shows that you have 20201022-r3 installed but eix says the latest
> available is 20201022-r2 so you have a version it thinks is not in the
> tree.
>
> Did you run eix-update after syncing?
Just sync'ed and on the mirror I used there is no 20201022-r2 version:
$ eix linux-firmware
[I] sys-kernel/linux-firmware
Available versions: 20200316^bsd 20200421^bsd 20200519^bsd 20200619^bsd
20200721^bsd 20200817^bsd 20200918^bsd 20201022-r3^bstd ***l^bstd
{initramfs +redistributable savedconfig unknown-license}
Installed versions: 20201022-r3^bst(08:50:57 26/11/20)(redistributable -
initramfs -savedconfig -unknown-license)
Homepage:https://git.kernel.org/?p=linux/kernel/git/firmware/
linux-firmware.git
Description: Linux firmware files
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
On Wednesday, 20 December 2017 17:27:25 GMT Mike Gilbert wrote: > On Wed, Dec 20, 2017 at 11:51 AM, Mick wrote: > > What step am I missing to arrive at a bootable kernel with all necessary > > firmware? > > Are you using an initramfs? Does the initramfs contain the necessary > firmware blobs? Thanks again Mike, no I am not using an initramfs. I just had a further look to see why the 4.14.7 does not boot. I discovered radeon/RV730_pfp.bin blob does not load and xserver segfaults. CPU microcode and WiFi firmware loads fine. So seems more relevant to a radeon firmware problem. Some additional observations: When I boot with 4.14.7 the xserver segfaults: == ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570, ATI Radeon HD 5670, ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270, ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS, AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS, ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI, MULLINS, KAVERI, HAWAII [30.806] (++) using VT number 7 [30.808] (EE) [30.808] (EE) Backtrace: [30.808] (EE) 0: /usr/bin/X (xorg_backtrace+0x4a) [0x55f50ff8d4aa] [30.808] (EE) 1: /usr/bin/X (0x55f50fde+0x1b1199) [0x55f50ff91199] [30.808] (EE) 2: /lib64/libpthread.so.0 (0x7f32631b+0x13d30) [0x7f32631c3d30] [30.808] (EE) 3: /usr/bin/X (xf86PlatformDeviceCheckBusID+0xa7) [0x55f50fe950e7] [30.808] (EE) 4: /usr/bin/X (0x55f50fde+0xaf8f2) [0x55f50fe8f8f2] [30.809] (EE) 5: /usr/bin/X (xf86CallDriverProbe+0xb0) [0x55f50fe67970] [30.809] (EE) 6: /usr/bin/X (xf86BusConfig+0x46) [0x55f50fe682b6] [30.809] (EE) 7: /usr/bin/X (InitOutput+0x961) [0x55f50fe76211] [30.809] (EE) 8: /usr/bin/X (0x55f50fde+0x54866) [0x55f50fe34866] [30.809] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f3262e21541] [30.809] (EE) 10: /usr/bin/X (_start+0x2a) [0x55f50fe1e6ea] [30.809] (EE) [30.809] (EE) Segmentation fault at address 0x0 [30.809] (EE) Fatal server error: [30.809] (EE) Caught signal 11 (Segmentation fault). Server aborting == Looking at dmesg I notice this: == [1.069560] [drm] radeon kernel modesetting enabled. [1.070133] [drm] initializing kernel modesetting (RV730 0x1002:0x9488 0x1028:0x02FE 0x00). [1.070309] resource sanity check: requesting [mem 0x000c-0x000d], which spans more than PCI Bus :00 [mem 0x000d4000-0x000d7fff window] [1.070505] caller pci_map_rom+0x53/0xd0 mapping multiple BARs [1.070655] ATOM BIOS: BR036993 [1.070813] radeon :02:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [1.070995] radeon :02:00.0: GTT: 1024M 0x4000 - 0x7FFF [1.071219] [drm] Detected VRAM RAM=1024M, BAR=256M [1.071352] [drm] RAM width 128bits DDR [1.071773] [TTM] Zone kernel: Available graphics memory: 2012374 kiB [1.071883] [TTM] Initializing pool allocator [1.071990] [TTM] Initializing DMA pool allocator [1.072241] [drm] radeon: 1024M of VRAM memory ready [1.072372] [drm] radeon: 1024M of GTT memory ready. [1.072525] [drm] Loading RV730 Microcode [1.072679] radeon :02:00.0: Direct firmware load for radeon/ RV730_pfp.bin failed with error -2 [1.072859] r600_cp: Failed to load firmware "radeon/RV730_pfp.bin" [1.072974] [drm:rv770_init] *ERROR* Failed to load firmware! [1.073183] radeon :02:00.0: Fatal error during GPU init [1.073294] [drm] radeon: finishing device. [1.084495] ACPI: Battery Slot [BAT0] (battery present) [1.095528] [TTM] Finalizing pool allocator [1.095637] [TTM] Finalizing DMA pool allocator [1.095903] [TTM] Zone kernel: Used memory at exit: 0 kiB [1.096082] [drm] radeon: ttm finalized [1.096832] radeon: probe of :02:00.0 failed with error -2 [1.097301] [drm] Initialized vgem 1.0.0 20120112 for virtual device on minor 0 [1.103389] brd: module loaded [1.105711] loop: module loaded [1.105810] mtip32xx Version 1.3.1 ===== Comparing firmware between kernels 4.12.12 and 4.14.7 I see: $ ls -l /usr/src/linux-4.12.12-gentoo/firmware/radeon/RV730* -rw-r--r-- 1 root root 5440 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ firmware/radeon/RV730_me.bin -rw-r--r-- 1 root root 454 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ firmware/radeon/RV730_me.bin.gen.S -rw-r--r-- 1 root root 6704 Dec 7 09:02 /usr/src/linux-4.12.12-gentoo/ firmware/radeon/RV730_me.bin.gen.o -rw-r--r-- 1 root root 14972 Jul 3 00:07 /usr/src/linux-4.12.12-gentoo/ firmware/radeon/RV730_me.bin
RE: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
> From: michaelkintz...@gmail.com > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel > module) > Date: Tue, 22 Dec 2015 23:02:12 + > > On Tuesday 22 Dec 2015 21:30:48 Alexander Kapshuk wrote: > > On Tue, Dec 22, 2015 at 9:39 PM, Mick wrote: > > > On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > > > > On Sun, Dec 20, 2015 at 9:04 PM, Mick wrote: > > > > > This is not working for me on a Kaveri system. > > > > > > > > > > The wiki page suggests these firmware blobs: > > > > > > > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > > > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > > > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > > > > radeon/kaveri_vce.bin > > > > > > > > > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > > > > > either: > > > > > > > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > > > > /lib/firmware/amdgpu/carrizo_sdma.bin > > > > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > > > > /lib/firmware/amdgpu/fiji_sdma.bin > > > > > /lib/firmware/amdgpu/fiji_sdma1.bin > > > > > /lib/firmware/amdgpu/tonga_sdma.bin > > > > > /lib/firmware/amdgpu/tonga_sdma1.bin > > > > > /lib/firmware/amdgpu/topaz_sdma.bin > > > > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > > > > > > > > > > Building the recommended blobs fails like so: > > > > > > > > > > # make && make modules_install && make firmware_install > > > > > > > > > > CHK include/config/kernel.release > > > > > CHK include/generated/uapi/linux/version.h > > > > > CHK include/generated/utsrelease.h > > > > > CHK include/generated/bounds.h > > > > > CHK include/generated/asm-offsets.h > > > > > CALLscripts/checksyscalls.sh > > > > > CHK include/generated/compile.h > > > > > > > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > > > > make[1]: *** No rule to make target > > > > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > > > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > > > > Makefile:947: recipe for target 'firmware' failed > > > > > make: *** [firmware] Error 2 > > > > > > > > That's interesting. 'kaveri_sdma1.bin' is found in the > > > > 'sys-firmware/amdgpu-ucode' package. See below. > > > > % pwd > > > > radeon_ucode/kaveri > > > > > > I don't seem to have such a directory, or the files therein. Where am I > > > supposed to look? > > > > > > This is what emerge -uaDv sys-firmware/amdgpu-ucode installed on my PC: > > > >>> Installing (1 of 1) sys-firmware/amdgpu-ucode-20150803::gentoo > > > > > > * checking 44 files for package collisions > > > > > > >>> Merging sys-firmware/amdgpu-ucode-20150803 to / > > > > > > --- /lib/ > > > --- /lib/firmware/ > > > --- /lib/firmware/amdgpu/ > > > > > > >>> /lib/firmware/amdgpu/carrizo_ce.bin > > > >>> /lib/firmware/amdgpu/carrizo_me.bin > > > >>> /lib/firmware/amdgpu/carrizo_mec.bin > > > >>> /lib/firmware/amdgpu/carrizo_mec2.bin > > > >>> /lib/firmware/amdgpu/carrizo_pfp.bin > > > >>> /lib/firmware/amdgpu/carrizo_rlc.bin > > > >>> /lib/firmware/amdgpu/carrizo_sdma.bin > > > >>> /lib/firmware/amdgpu/carrizo_sdma1.bin > > > >>> /lib/firmware/amdgpu/carrizo_uvd.bin > > > >>> /lib/firmware/amdgpu/carrizo_vce.bin > > > >>> /lib/firm
Re: [gentoo-user] Loading a Firmware Module By hand?
If you want to build into the kernel again, check ‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set: CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" I must correct myself. I’ve seen that the file ‘firmware-6.bin’ is located in ‘/lib/firmware/ath10k/QCA6174/hw3.0’ and ‘firmware-5.bin’ lives in ‘/lib/firmware/ath10k/QCA6174/hw2.1’, see [1]. That is where your firmware loading error comes from (and my wrong example for the CONFIG_EXTRA_FIRMWARE). So, the correct kernel configuration should be: CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-5.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" or CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw3.0/firmware-6.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" [1] <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ath10k/QCA6174> -- Regards, floyd
Re: [gentoo-user] Weird system freeze?
On 13/6/24 23:57, Dale wrote: Waldo Lemmer wrote: By the way, you should really just use the linux-firmware package if it has the firmware you need. You can plug the name of the firmware into https://portagefilelist.de to check if it does. I agree. For firmware, this is the way to go. I use dracut and I think it even picks up firmware that needs to be loaded early on. So far, I don't recall ever doing anything, it just works. Plus, as pointed out before, it updates as needed. You don't have to remember to do anything or track updates elsewhere, which one may forget to do. Dale :-) :-) P. S. Still waiting on CPU for the build. Sent message to seller requesting them to scream loudly. I'm about sick of that post office hub. :-@ Its in linux-firmware - much easier/safer to install (even temporarily while you grab the files) than asking for a random from the web. BillK bunyip ~ # equery f linux-firmware|grep i915|grep kbl /lib/firmware/i915/kbl_dmc_ver1.bin /lib/firmware/i915/kbl_dmc_ver1_01.bin /lib/firmware/i915/kbl_dmc_ver1_04.bin /lib/firmware/i915/kbl_guc_32.0.3.bin /lib/firmware/i915/kbl_guc_33.0.0.bin /lib/firmware/i915/kbl_guc_49.0.1.bin /lib/firmware/i915/kbl_guc_62.0.0.bin /lib/firmware/i915/kbl_guc_69.0.3.bin /lib/firmware/i915/kbl_guc_70.1.1.bin /lib/firmware/i915/kbl_guc_ver9_14.bin /lib/firmware/i915/kbl_guc_ver9_39.bin /lib/firmware/i915/kbl_huc_4.0.0.bin /lib/firmware/i915/kbl_huc_ver02_00_1810.bin bunyip ~ # ls -al /lib/firmware/i915/kbl_dmc_ver1_04.bin -rw-r--r-- 1 root root 8840 Jun 3 15:06 /lib/firmware/i915/kbl_dmc_ver1_04.bin bunyip ~ #
Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
On Wed, Dec 20, 2017 at 11:51 AM, Mick wrote: > On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote: >> On Wed, Dec 20, 2017 at 9:26 AM, Mick wrote: > >> > You are quite right, there is no firmware_install in the 4.14.7 release. >> > What does this mean? How are we meant to install firmware now? >> >> I believe all firmware has been removed from the kernel sources. >> >> You should install sys-kernel/linux-firmware, or grab just the files >> you need from the git repo. >> >> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > > Thank you all, but I see to have a mental disconnect here: > > I already have sys-kernel/linux-firmware-20170314 installed. > > I have specified in the kernel which blobs I need and /lib/firmware/ as the > path for the kernel to find any firmware it may need. > > I used to run make firmware_install and the kernel was able to load whatever > firmware I had specified so that CPU/GPU can function properly at boot time. > > With 4.14.7 I (can) no longer do this; > > AND > > the newly compiled kernel does not load at boot time any of the needed > firmware. > > What step am I missing to arrive at a bootable kernel with all necessary > firmware? Are you using an initramfs? Does the initramfs contain the necessary firmware blobs?
Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote: > On Wed, Dec 20, 2017 at 9:26 AM, Mick wrote: > > You are quite right, there is no firmware_install in the 4.14.7 release. > > What does this mean? How are we meant to install firmware now? > > I believe all firmware has been removed from the kernel sources. > > You should install sys-kernel/linux-firmware, or grab just the files > you need from the git repo. > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Thank you all, but I see to have a mental disconnect here: I already have sys-kernel/linux-firmware-20170314 installed. I have specified in the kernel which blobs I need and /lib/firmware/ as the path for the kernel to find any firmware it may need. I used to run make firmware_install and the kernel was able to load whatever firmware I had specified so that CPU/GPU can function properly at boot time. With 4.14.7 I (can) no longer do this; AND the newly compiled kernel does not load at boot time any of the needed firmware. What step am I missing to arrive at a bootable kernel with all necessary firmware? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] No wifi
On Tue, Jul 14, 2020 at 12:19:51AM -0400, Walter Dnes wrote: > [thimk][root][~] lspci -k | grep -i -B 1 5100 > Kernel driver in use: i801_smbus > 03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] > Network Connection > Subsystem: Intel Corporation WiFi Link 5100 AGN > > Note that that it's not being "loaded" as a module. I'm building into > the kernel itself. Here's a snippet from .config It doesn't look like it's loading the firmware. Are there any obvious firmware- loading errors in dmesg ? If not, it might be worth installing `sys-apps/lshw` and running `lshw -C network` to see kernel resource information regarding the device. > # > # Firmware loader > # > CONFIG_FW_LOADER=y > CONFIG_EXTRA_FIRMWARE="iwlwifi-5000-ucode-5.4.A.11/iwlwifi-5000-1.ucode" > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" That looks fine, although why are you using such an outdated version of the microcode ? For kernels 2.6.38+, you can use 8.83.5.1-1. > > Did you install the iwlwifi microcode from sys-kernel/linux-firmware > > (linux-firmware.git), or directly from kernel.org ? > > Directly from kernel.org itself. As I mentioned, the feature in > "make menuconfig" pointed there. I basically ran... > > wget [link clipped] Perhaps it would be better to install it from the Gentoo-provided firmware package ? Amend /etc/portage/savedconfig/sys-kernel/linux-firmware to include the appropriate entries (listing at [1]), and emerge `linux-firmware` with the `savedconfig` USE-flag. [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ -- Ashley Dixon suugaku.co.uk 2A9A 4117 DA96 D18A 8A7B B0D2 A30E BF25 F290 A8AA signature.asc Description: PGP signature
Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
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 ---> > > > > Generic Driver Options ---> > > > > -*- Userspace firmware loading support > > [*] Include in-kernel firmware blobs in kernel binary > > > > (amdgpu/.bin radeon/.bin) > > (/lib/firmware) Firmware blobs root directory > > > > Yes I have the firmware includes, I'll try the amdgpu-ucode and report > > back. > > > > > > - > > > > > > Mission successful! Thanks everyone, it appears the missing sdma1.bin > > from linux-firmware is contained in amdgpu-ucode and after switching > > everything is running fine. > > Good to hear. > > Thanks for letting us know. This is not working for me on a Kaveri system. The wiki page suggests these firmware blobs: radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin radeon/kaveri_vce.bin Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there either: find /lib/firmware/amdgpu/ -iname *sdma* /lib/firmware/amdgpu/carrizo_sdma.bin /lib/firmware/amdgpu/carrizo_sdma1.bin /lib/firmware/amdgpu/fiji_sdma.bin /lib/firmware/amdgpu/fiji_sdma1.bin /lib/firmware/amdgpu/tonga_sdma.bin /lib/firmware/amdgpu/tonga_sdma1.bin /lib/firmware/amdgpu/topaz_sdma.bin /lib/firmware/amdgpu/topaz_sdma1.bin Building the recommended blobs fails like so: # make && make modules_install && make firmware_install CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CHK include/generated/bounds.h CHK include/generated/asm-offsets.h CALLscripts/checksyscalls.sh CHK include/generated/compile.h kernel/Makefile:135: *** No X.509 certificates found *** make[1]: *** No rule to make target '/lib/firmware//radeon/kaveri_sdma1.bin', needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. Makefile:947: recipe for target 'firmware' failed make: *** [firmware] Error 2 What now? PS. As VIDEO_CARDS in make.conf I used to have radeon and radeonsi, but have now changed it to amdgpu and radeonsi. Should I revert and forget about radeon/kaveri_sdma1.bin? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] r8169 unable to apply firmware patch
> I remembered that i also had started having a problem with my intel > wireless card, and it looks like both the intel and realtek firmwares > are now in linux-firmware so try emerging that. That fixed it. Thank you very much. I'm a little puzzled because I don't get the "unable to apply firmware patch" messages on my desktop which also uses the r8169 driver and doesn't have linux-firmware installed. I guess linux-firmware is a package released by the kernel folks containing certain firmware blobs? It looks like rt73 is in there but not b43. - Grant
[gentoo-user] AMD Ucode Correction, Fam15h
FYI to all with an interest in AMD Ucode. AMD fixed the 'lwp' instruction(s) in a latter ucode update. -- 2018-05-18 linux-firmware: Update AMD cpu microcode * Add AMD cpu microcode for processor family 17h * Update AMD cpu microcode for processor family 15h * Update the AMD cpu microcode license copyright * Add a Version for both microcode family 15h and 17h https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8 ( sys-kernel/linux-firmware-20180518:0 ) On an AMD FX-9590 , the 'lwp' instruction(s) disappeared. -- 2018-05-25 Update AMD cpu microcode for family 15h * Processor Revision ID 0x00610f01 was accidently not included in the previous submitted microcode container file. * Update the Version for family 15h microcode .bin file https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7518922bd5b98b137af7aaf3c836f5a498e91609 ( sys-kernel/linux-firmware-20180525:0 ) On an AMD FX-9590 , the 'lwp' instruction(s) reappeared. -- Thanks to the person who fixed this little 'oops'.
Re: [gentoo-user] How to tell what the current AMD microcode level is?
On Sat, Dec 7, 2019 at 7:22 PM Adam Carter wrote: > > On Sun, Dec 8, 2019 at 9:39 AM Daniel Frey wrote: >> >> Does anyone know of a list of microcode versions? > > I dont know, so i just use the ~amd64 linux-firmware version. For my 3900X > its currently; > microcode: CPU0: patch_level=0x08701013 > > The last update came through in October; > firmware-md5s-2019-09-09.txt:fef89be989f6a160b340027a24cd0a16 > /lib/firmware/amd-ucode/microcode_amd_fam17h.bin > firmware-md5s-2019-09-25.txt:fef89be989f6a160b340027a24cd0a16 > /lib/firmware/amd-ucode/microcode_amd_fam17h.bin > firmware-md5s-2019-10-23.txt:a30e5f81d37ed38faf039b75bc376197 > /lib/firmware/amd-ucode/microcode_amd_fam17h.bin > firmware-md5s-2019-11-12.txt:a30e5f81d37ed38faf039b75bc376197 > /lib/firmware/amd-ucode/microcode_amd_fam17h.bin > AMD's documentation is pretty terrible on this front. I don't think they actually release the microcode binaries anywhere officially. It seems like they patch them through windows, and these versions end up floating around (probably via enterprise support contracts), and then somebody snags one and sticks it in the linux-firmware package. Oh, and there is basically zero official info as far as a changelog goes. So, if you want to know if some particular version addresses some particular CVE you're just going to have to trust whatever somebody said on lkml or on some random internet forum. These aren't even linux-specific drivers. They're just microcode blobs. Nobody but AMD can create them or work on them. The least AMD could do is stick them on their website along with official hashes and release notes. I'm sure the linux-firmware maintainers know what they're doing and do the necessary detective work to ensure nothing gets missing, but something like this should really have formal vendor support. -- Rich
Re: [gentoo-user] Gentoo installation, network adapter not supported
In linux.gentoo.user, you wrote: > 2013/6/29 Zind >> >>> Can you search with dmesg and find if it's nead a firmware. >> >> Yes. >> At the bottom of the dmesg message, I can see these lines: >> request for firmware file 'iwlwifi-2030-6.ucode' failed. >> request for firmware file 'iwlwifi-2030-5.ucode' failed. >> no suitable firmware found! >> > > You can try to fix this with emerging linux-firmware. I'm not sure if this > firmware is in there, or what else to configure to fit it exactly, but in > default the firmwares ware installed. I can confirm that these firmware files are in the linux-firmware package. -- Regards, Gregory Shearman.
Re: [gentoo-user] Where to put Happauge capture card firmware?
On 16/06/2019 04:34, J. Roeleveld wrote: > There should be a /lib/firmware containing all the firmware files. > See the linux-firmware ebuild for the exact location. Thanks. Installing linux-firmware and adding this file to my initrd in Dracut configuration solved my issue. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
On Tuesday 22 Dec 2015 21:30:48 Alexander Kapshuk wrote: > On Tue, Dec 22, 2015 at 9:39 PM, Mick wrote: > > On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > > > On Sun, Dec 20, 2015 at 9:04 PM, Mick wrote: > > > > This is not working for me on a Kaveri system. > > > > > > > > The wiki page suggests these firmware blobs: > > > > > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > > > radeon/kaveri_vce.bin > > > > > > > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > > > > either: > > > > > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > > > /lib/firmware/amdgpu/carrizo_sdma.bin > > > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > > > /lib/firmware/amdgpu/fiji_sdma.bin > > > > /lib/firmware/amdgpu/fiji_sdma1.bin > > > > /lib/firmware/amdgpu/tonga_sdma.bin > > > > /lib/firmware/amdgpu/tonga_sdma1.bin > > > > /lib/firmware/amdgpu/topaz_sdma.bin > > > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > > > > > > > Building the recommended blobs fails like so: > > > > > > > > # make && make modules_install && make firmware_install > > > > > > > > CHK include/config/kernel.release > > > > CHK include/generated/uapi/linux/version.h > > > > CHK include/generated/utsrelease.h > > > > CHK include/generated/bounds.h > > > > CHK include/generated/asm-offsets.h > > > > CALLscripts/checksyscalls.sh > > > > CHK include/generated/compile.h > > > > > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > > > make[1]: *** No rule to make target > > > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > > > Makefile:947: recipe for target 'firmware' failed > > > > make: *** [firmware] Error 2 > > > > > > That's interesting. 'kaveri_sdma1.bin' is found in the > > > 'sys-firmware/amdgpu-ucode' package. See below. > > > % pwd > > > radeon_ucode/kaveri > > > > I don't seem to have such a directory, or the files therein. Where am I > > supposed to look? > > > > This is what emerge -uaDv sys-firmware/amdgpu-ucode installed on my PC: > > >>> Installing (1 of 1) sys-firmware/amdgpu-ucode-20150803::gentoo > > > > * checking 44 files for package collisions > > > > >>> Merging sys-firmware/amdgpu-ucode-20150803 to / > > > > --- /lib/ > > --- /lib/firmware/ > > --- /lib/firmware/amdgpu/ > > > > >>> /lib/firmware/amdgpu/carrizo_ce.bin > > >>> /lib/firmware/amdgpu/carrizo_me.bin > > >>> /lib/firmware/amdgpu/carrizo_mec.bin > > >>> /lib/firmware/amdgpu/carrizo_mec2.bin > > >>> /lib/firmware/amdgpu/carrizo_pfp.bin > > >>> /lib/firmware/amdgpu/carrizo_rlc.bin > > >>> /lib/firmware/amdgpu/carrizo_sdma.bin > > >>> /lib/firmware/amdgpu/carrizo_sdma1.bin > > >>> /lib/firmware/amdgpu/carrizo_uvd.bin > > >>> /lib/firmware/amdgpu/carrizo_vce.bin > > >>> /lib/firmware/amdgpu/fiji_ce.bin > > >>> /lib/firmware/amdgpu/fiji_mc.bin > > >>> /lib/firmware/amdgpu/fiji_me.bin > > >>> /lib/firmware/amdgpu/fiji_mec.bin > > >>> /lib/firmware/amdgpu/fiji_mec2.bin > > >>> /lib/firmware/amdgpu/fiji_pfp.bin > > >>> /lib/firmware/amdgpu/fiji_rlc.bin > > >>> /lib/firmware/amdgpu/fiji_sdma.bin > > >>> /lib/firmware/amdgpu/fiji_sdma1.bin > > >>> /lib/firmware/amdgpu/fiji_smc.bin > > >>> /lib/firmware/amdgpu/fiji_uvd.bin > > >>> /lib/firmware/amdgpu/fi
Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > On Sun, Dec 20, 2015 at 9:04 PM, Mick wrote: > > This is not working for me on a Kaveri system. > > > > The wiki page suggests these firmware blobs: > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > radeon/kaveri_vce.bin > > > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > > either: > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > /lib/firmware/amdgpu/carrizo_sdma.bin > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > /lib/firmware/amdgpu/fiji_sdma.bin > > /lib/firmware/amdgpu/fiji_sdma1.bin > > /lib/firmware/amdgpu/tonga_sdma.bin > > /lib/firmware/amdgpu/tonga_sdma1.bin > > /lib/firmware/amdgpu/topaz_sdma.bin > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > Building the recommended blobs fails like so: > > > > # make && make modules_install && make firmware_install > > > > CHK include/config/kernel.release > > CHK include/generated/uapi/linux/version.h > > CHK include/generated/utsrelease.h > > CHK include/generated/bounds.h > > CHK include/generated/asm-offsets.h > > CALLscripts/checksyscalls.sh > > CHK include/generated/compile.h > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > make[1]: *** No rule to make target > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > Makefile:947: recipe for target 'firmware' failed > > make: *** [firmware] Error 2 > That's interesting. 'kaveri_sdma1.bin' is found in the > 'sys-firmware/amdgpu-ucode' package. See below. > % pwd > radeon_ucode/kaveri I don't seem to have such a directory, or the files therein. Where am I supposed to look? This is what emerge -uaDv sys-firmware/amdgpu-ucode installed on my PC: >>> Installing (1 of 1) sys-firmware/amdgpu-ucode-20150803::gentoo * checking 44 files for package collisions >>> Merging sys-firmware/amdgpu-ucode-20150803 to / --- /lib/ --- /lib/firmware/ --- /lib/firmware/amdgpu/ >>> /lib/firmware/amdgpu/carrizo_ce.bin >>> /lib/firmware/amdgpu/carrizo_me.bin >>> /lib/firmware/amdgpu/carrizo_mec.bin >>> /lib/firmware/amdgpu/carrizo_mec2.bin >>> /lib/firmware/amdgpu/carrizo_pfp.bin >>> /lib/firmware/amdgpu/carrizo_rlc.bin >>> /lib/firmware/amdgpu/carrizo_sdma.bin >>> /lib/firmware/amdgpu/carrizo_sdma1.bin >>> /lib/firmware/amdgpu/carrizo_uvd.bin >>> /lib/firmware/amdgpu/carrizo_vce.bin >>> /lib/firmware/amdgpu/fiji_ce.bin >>> /lib/firmware/amdgpu/fiji_mc.bin >>> /lib/firmware/amdgpu/fiji_me.bin >>> /lib/firmware/amdgpu/fiji_mec.bin >>> /lib/firmware/amdgpu/fiji_mec2.bin >>> /lib/firmware/amdgpu/fiji_pfp.bin >>> /lib/firmware/amdgpu/fiji_rlc.bin >>> /lib/firmware/amdgpu/fiji_sdma.bin >>> /lib/firmware/amdgpu/fiji_sdma1.bin >>> /lib/firmware/amdgpu/fiji_smc.bin >>> /lib/firmware/amdgpu/fiji_uvd.bin >>> /lib/firmware/amdgpu/fiji_vce.bin >>> /lib/firmware/amdgpu/tonga_ce.bin >>> /lib/firmware/amdgpu/tonga_mc.bin >>> /lib/firmware/amdgpu/tonga_me.bin >>> /lib/firmware/amdgpu/tonga_mec.bin >>> /lib/firmware/amdgpu/tonga_mec2.bin >>> /lib/firmware/amdgpu/tonga_pfp.bin >>> /lib/firmware/amdgpu/tonga_rlc.bin >>> /lib/firmware/amdgpu/tonga_sdma.bin >>> /lib/firmware/amdgpu/tonga_sdma1.bin >>> /lib/firmware/amdgpu/tonga_smc.bin >>> /lib/firmware/amdgpu/tonga_uvd.bin >>> /lib/firmware/amdgpu/tonga_vce.bin >>> /lib/firmware/amdgpu/topaz_ce.bin >>> /lib/firmware/amdgpu/topaz_mc.bin >>> /lib/firmware/amdgpu/topaz_me.bin >>> /lib/firmware/amdgpu/topaz_mec.bin >>> /lib/firmware/amdgpu/topaz_mec2.bin >>> /lib/firmware/amdgpu/topaz_pfp.bin >>> /lib/firmware/amdgpu/topaz_rlc.bin >>> /lib/firmware/amdgpu/topaz_sdma.bin >>> /lib/firmware/amdgpu/topaz_sdma1.bin >>> /lib/firmware/amdgpu/topaz_smc.bin No /kaveri/ in there. > Perhaps the path to the binary blobs specified in your kernel config file > is wrong? You want to double check that. This is what I have: grep /firmware .config CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" Looking at it again the amdgpu wiki page does not list amdgpu firmwares for the KAVERI APU. However, I am confused as to why I can't find radeon/kaveri_sdma1 in my installed firmwares (either from linux-firmware, or from amdgpu-ucode. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
I have "nouveau" build into kernel but it doesn't work: Fom dmesg: nouveau :08:00.0: NVIDIA GP107 (137000a1) nouveau :08:00.0: gr: failed to load firmware "gr/sw_nonctx" nouveau :08:00.0: gr: failed to load gr/sw_nonctx nouveau :08:00.0: DRM: failed to create kernel channel, -22 grep -i nouveau .config CONFIG_DRM_NOUVEAU=y # CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT is not set CONFIG_NOUVEAU_DEBUG=5 CONFIG_NOUVEAU_DEBUG_DEFAULT=3 # CONFIG_NOUVEAU_DEBUG_MMU is not set CONFIG_DRM_NOUVEAU_BACKLIGHT=y I have "linux-firmware" installed but there is a "?" mark beside it eix linux-firmware [?] sys-kernel/linux-firmware Installed versions: 20201022-r3
Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
On Sun, Dec 20, 2015 at 9:04 PM, Mick 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 firmware included in your kernel config file? > > > > > > Device Drivers ---> > > > > > > Generic Driver Options ---> > > > > > > -*- Userspace firmware loading support > > > [*] Include in-kernel firmware blobs in kernel binary > > > > > > (amdgpu/.bin radeon/.bin) > > > (/lib/firmware) Firmware blobs root directory > > > > > > Yes I have the firmware includes, I'll try the amdgpu-ucode and report > > > back. > > > > > > > > > - > > > > > > > > > Mission successful! Thanks everyone, it appears the missing sdma1.bin > > > from linux-firmware is contained in amdgpu-ucode and after switching > > > everything is running fine. > > > > Good to hear. > > > > Thanks for letting us know. > > This is not working for me on a Kaveri system. > > The wiki page suggests these firmware blobs: > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > radeon/kaveri_vce.bin > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > either: > > find /lib/firmware/amdgpu/ -iname *sdma* > /lib/firmware/amdgpu/carrizo_sdma.bin > /lib/firmware/amdgpu/carrizo_sdma1.bin > /lib/firmware/amdgpu/fiji_sdma.bin > /lib/firmware/amdgpu/fiji_sdma1.bin > /lib/firmware/amdgpu/tonga_sdma.bin > /lib/firmware/amdgpu/tonga_sdma1.bin > /lib/firmware/amdgpu/topaz_sdma.bin > /lib/firmware/amdgpu/topaz_sdma1.bin > > > Building the recommended blobs fails like so: > > # make && make modules_install && make firmware_install > CHK include/config/kernel.release > CHK include/generated/uapi/linux/version.h > CHK include/generated/utsrelease.h > CHK include/generated/bounds.h > CHK include/generated/asm-offsets.h > CALLscripts/checksyscalls.sh > CHK include/generated/compile.h > kernel/Makefile:135: *** No X.509 certificates found *** > make[1]: *** No rule to make target > '/lib/firmware//radeon/kaveri_sdma1.bin', > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > Makefile:947: recipe for target 'firmware' failed > make: *** [firmware] Error 2 > > What now? > > PS. As VIDEO_CARDS in make.conf I used to have radeon and radeonsi, but > have > now changed it to amdgpu and radeonsi. Should I revert and forget about > radeon/kaveri_sdma1.bin? > -- > Regards, > Mick > That's interesting. 'kaveri_sdma1.bin' is found in the 'sys-firmware/amdgpu-ucode' package. See below. % pwd radeon_ucode/kaveri % ls -1 *sdma* kaveri_sdma.bin kaveri_sdma1.bin Perhaps the path to the binary blobs specified in your kernel config file is wrong? You want to double check that. Device Drivers ---> Generic Driver Options ---> -*- Userspace firmware loading support [*] Include in-kernel firmware blobs in kernel binary (amdgpu/.bin radeon/.bin) (/lib/firmware) Firmware blobs root directory
Re: [gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
On Sun, 13 Dec 2020 11:52:51 -0700, the...@sys-concept.com wrote: > I have "linux-firmware" installed but there is a "?" mark beside it > > eix linux-firmware > [?] sys-kernel/linux-firmware > Installed versions: 20201022-r3 > It means the version you have installed is no longer in the tree. You should update to the latest. -- Neil Bothwick "RAM DISK is NOT an installation procedure!" pgpG9QDgQDFMj.pgp Description: OpenPGP digital signature
Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
On Wed, 20 Dec 2017 16:51:04 + Mick wrote: On Wednesday, 20 December 2017 16:03:02 GMT Mike Gilbert wrote: On Wed, Dec 20, 2017 at 9:26 AM, Mick wrote: > You are quite right, there is no firmware_install in the 4.14.7 release. > What does this mean? How are we meant to install firmware now? I believe all firmware has been removed from the kernel sources. You should install sys-kernel/linux-firmware, or grab just the files you need from the git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Thank you all, but I see to have a mental disconnect here: I already have sys-kernel/linux-firmware-20170314 installed. I have specified in the kernel which blobs I need and /lib/firmware/ as the path for the kernel to find any firmware it may need. I used to run make firmware_install and the kernel was able to load whatever firmware I had specified so that CPU/GPU can function properly at boot time. With 4.14.7 I (can) no longer do this; Since I fully encrypt my drives and therefore using an EFI-stub kernel with an embedded initramfs, I use genkernel-next and different scripts to build my kernels. It can be tricky and feels like a tool-chain but also works for me. AND the newly compiled kernel does not load at boot time any of the needed firmware. What step am I missing to arrive at a bootable kernel with all necessary firmware? Assuming your specified blobs are all available and required kernel options like CONFIG_MICROCODE and CONFIG_MICROCODE_INTEL [1] are proper set, I’m not sure it makes any difference but the default is: CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" without the appended forward slash. [1] <https://wiki.gentoo.org/wiki/Intel_microcode> -- Regards, floyd
RE: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
> From: michaelkintz...@gmail.com > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel > module) > Date: Sun, 20 Dec 2015 23:25:29 + > > On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > > On Sun, Dec 20, 2015 at 9:04 PM, Mick 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 firmware included in your kernel config file? > > > > > > > > > > Device Drivers ---> > > > > > > > > > > Generic Driver Options ---> > > > > > > > > > > -*- Userspace firmware loading support > > > > > [*] Include in-kernel firmware blobs in kernel binary > > > > > > > > > > (amdgpu/.bin radeon/.bin) > > > > > (/lib/firmware) Firmware blobs root directory > > > > > > > > > > Yes I have the firmware includes, I'll try the amdgpu-ucode and > > > > > report back. > > > > > > > > > > > > > > > - > > > > > > > > > > > > > > > Mission successful! Thanks everyone, it appears the missing > > > > > sdma1.bin from linux-firmware is contained in amdgpu-ucode and after > > > > > switching everything is running fine. > > > > > > > > Good to hear. > > > > > > > > Thanks for letting us know. > > > > > > This is not working for me on a Kaveri system. > > > > > > The wiki page suggests these firmware blobs: > > > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > > radeon/kaveri_vce.bin > > > > > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > > > either: > > > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > > /lib/firmware/amdgpu/carrizo_sdma.bin > > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > > /lib/firmware/amdgpu/fiji_sdma.bin > > > /lib/firmware/amdgpu/fiji_sdma1.bin > > > /lib/firmware/amdgpu/tonga_sdma.bin > > > /lib/firmware/amdgpu/tonga_sdma1.bin > > > /lib/firmware/amdgpu/topaz_sdma.bin > > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > > > > Building the recommended blobs fails like so: > > > > > > # make && make modules_install && make firmware_install > > > > > > CHK include/config/kernel.release > > > CHK include/generated/uapi/linux/version.h > > > CHK include/generated/utsrelease.h > > > CHK include/generated/bounds.h > > > CHK include/generated/asm-offsets.h > > > CALLscripts/checksyscalls.sh > > > CHK include/generated/compile.h > > > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > > make[1]: *** No rule to make target > > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > > Makefile:947: recipe for target 'firmware' failed > > > make: *** [firmware] Error 2 > > > > > > What now? > > > > > > PS. As VIDEO_CARDS in make.conf I used to have radeon and radeonsi, but > > > have > > > now changed it to amdgpu and radeonsi. Should I revert and forget about > > > radeon/kaveri_sdma1.bin? > > > -- > > > Regards, > > > Mick > > > > That's interesting. 'kaveri_sdma1.bin' is found in the > > 'sys-firmware/amdgpu-ucode' package. See below. > > % pwd > > radeon_ucode/kaveri > > % ls -1 *sdma* > > kaveri_sdma.bin > > kaveri_sdma1.bin > > > > Perhaps the path to the binary blobs specified in your kernel config file &g
Re: [gentoo-user] net-misc/r8168 build issue
On Thu, 15 Nov 2018 18:06:26 +0300, Hasan Ç. wrote:
> This is a known problem kernel uses r8169 ethernet firmware for r8168
> chips and causes connectivity issues.Thanks gentoo there is a r8168
> package in net-misc but i encountered a problem.
>
> James Le Cuirot , Sat, 28 Apr 2018 00:09, commit
> ee232457
> <https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ee232457ed7bad1c3d62c4c509419086b6ea3a65>
>
> -CONFIG_CHECK="!R8169"
> -ERROR_R8169="${P} requires Realtek 8169 PCI Gigabit Ethernet adapter
> (CONFIG_R8169) to be DISABLED"
>
> emerge --ask net-misc/r8168
You can't have two r8168 modules installed at the same time. Use either
the in-kernel one or thebinary driver from Realtek, that's what the ebuild
is checking for. For the 8168 firmware, install linux-firmware.
% qlist linux-firmware | grep 8168
/lib/firmware/rtl_nic/rtl8168h-2.fw
/lib/firmware/rtl_nic/rtl8168h-1.fw
/lib/firmware/rtl_nic/rtl8168g-3.fw
/lib/firmware/rtl_nic/rtl8168g-2.fw
/lib/firmware/rtl_nic/rtl8168g-1.fw
/lib/firmware/rtl_nic/rtl8168f-2.fw
/lib/firmware/rtl_nic/rtl8168f-1.fw
/lib/firmware/rtl_nic/rtl8168e-3.fw
/lib/firmware/rtl_nic/rtl8168e-2.fw
/lib/firmware/rtl_nic/rtl8168e-1.fw
/lib/firmware/rtl_nic/rtl8168d-2.fw
/lib/firmware/rtl_nic/rtl8168d-1.fw
--
Neil Bothwick
WORM: (n.) acronym for Write Once, Read Mangled. Used to describe a
normally-functioning computer disk of the very latest design.
pgpD4vG0ANuCS.pgp
Description: OpenPGP digital signature
Re: [gentoo-user] Weird system freeze?
On Thursday, 13 June 2024 04:11:40 BST Walter Dnes wrote: > On Tue, Jun 11, 2024 at 07:45:09PM +0100, Michael wrote > > > The above errors are an indication something is amiss with the > > requisite firmware for your graphics. > > > > Have you specified this in your kernel, or in your initramfs? > > OK, I've downloaded kbl_dmc_ver1_04.bin now, but I'm having problems > implementing it. First I saved it to /lib/firmware, entered the > firmware name in "make menuconfig" (Build named firmware blobs into the > kernel) and recompiled; same error message about no such file. > > Then I created subdirectory /lib/firmware/i915 and moved the bin there. > I changed the entry in "make menuconfig" to "i915/kbl_dmc_ver1_04.bin" > and recompiled. It finds the file now, but still errors out. dmesg says > > = > [0.221960] Loading firmware: i915/kbl_dmc_ver1_04.bin > [0.221962] i915 :00:02.0: [drm] *ERROR* DMC firmware has wrong CSS > header length (1097158924 bytes) [0.221964] i915 :00:02.0: [drm] > Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime > power management. [0.221967] i915 :00:02.0: [drm] DMC firmware > homepage: > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > /tree/i915 > = > > Any ideas what I'm doing wrong? And why is it trying to load the file > even after I (try to) build it into the kernel? For the firmware file(s) code to be built into the kernel *all* necessary firmware files must be present in your filesystem and the path for these defined. The i915 directory contains the attached list of files on my system. You can fetch these individually, or it would make more sense to emerge sys- kernel/linux-firmware. This package will fetch way more than the firmware files you need for your hardware. You can configure it to only fetch the files you actually need and use, thereafter: https://wiki.gentoo.org/wiki/Linux_firmware#Optional:_Savedconfig but it will require to emerge the package twice each time. Using sys-kernel/linux-firmware is a better idea than manually downloading individual files, because the package is updated regularly with any changes released by the OEMs, but either will work as long as all the needed files are present. PS. Your post prompted me to look into an old i915 system, where I discovered a kernel trace hidden undetected in dmesg! Thank you. :-)~ $ ls -la /lib/firmware/i915/*kbl* lrwxrwxrwx 1 root root 19 May 20 12:18 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 8616 May 20 12:18 /lib/firmware/i915/kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 8840 May 20 12:18 /lib/firmware/i915/kbl_dmc_ver1_04.bin -rw-r--r-- 1 root root 176448 May 20 12:18 /lib/firmware/i915/kbl_guc_32.0.3.bin -rw-r--r-- 1 root root 182912 May 20 12:18 /lib/firmware/i915/kbl_guc_33.0.0.bin -rw-r--r-- 1 root root 197184 May 20 12:18 /lib/firmware/i915/kbl_guc_49.0.1.bin -rw-r--r-- 1 root root 200448 May 20 12:18 /lib/firmware/i915/kbl_guc_62.0.0.bin -rw-r--r-- 1 root root 217664 May 20 12:18 /lib/firmware/i915/kbl_guc_69.0.3.bin -rw-r--r-- 1 root root 206976 May 20 12:18 /lib/firmware/i915/kbl_guc_70.1.1.bin -rw-r--r-- 1 root root 142656 May 20 12:18 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 147776 May 20 12:18 /lib/firmware/i915/kbl_guc_ver9_39.bin -rw-r--r-- 1 root root 226048 May 20 12:18 /lib/firmware/i915/kbl_huc_4.0.0.bin -rw-r--r-- 1 root root 218688 May 20 12:18 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: new mobo : Eth0 recovered
On 21/04/12 18:55, Dale wrote: Nikos Chantziaras wrote: [...] Also, make sure to emerge sys-kernel/linux-firmware. Without it, RTL8111/8168B NICs will produce random connectivity hang-ups after a few hours; they need firmware that was previously part of the kernel itself but has now been split to sys-kernel/linux-firmware. Do a: dmesg | grep -i firmware and check for firmware loading errors. So that is what is wrong with my connection. I been having this issue for a while and it is getting on my nerves. Is this fix OK even if you don't build your drivers as modules? I build everything into the kernel. I never did like modules much. The kernel source doesn't have any firmware files in it, so it doesn't matter whether you build the drivers into the kernel or as modules; the firmware isn't there in either case. However, this particular driver (r8169), says in its description that building as a module is recommended. However, it doesn't give you any explanation as to why this recommendation is made. I suppose the driver developer was working for Apple previously :-P Anyway, "dmesg | grep -i firmware" should tell you whether you actually even need the firmware. If you don't get a firmware loading error in dmesg, then you don't need it and your problem is not related. In that case, you belong to the (quite large) group of people for which only the net-misc/r8168 driver works reliably (which unfortunately doesn't always support the latest linux kernel.)
Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > On Sun, Dec 20, 2015 at 9:04 PM, Mick 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 firmware included in your kernel config file? > > > > > > > > Device Drivers ---> > > > > > > > > Generic Driver Options ---> > > > > > > > > -*- Userspace firmware loading support > > > > [*] Include in-kernel firmware blobs in kernel binary > > > > > > > > (amdgpu/.bin radeon/.bin) > > > > (/lib/firmware) Firmware blobs root directory > > > > > > > > Yes I have the firmware includes, I'll try the amdgpu-ucode and > > > > report back. > > > > > > > > > > > > - > > > > > > > > > > > > Mission successful! Thanks everyone, it appears the missing > > > > sdma1.bin from linux-firmware is contained in amdgpu-ucode and after > > > > switching everything is running fine. > > > > > > Good to hear. > > > > > > Thanks for letting us know. > > > > This is not working for me on a Kaveri system. > > > > The wiki page suggests these firmware blobs: > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > radeon/kaveri_vce.bin > > > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > > either: > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > /lib/firmware/amdgpu/carrizo_sdma.bin > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > /lib/firmware/amdgpu/fiji_sdma.bin > > /lib/firmware/amdgpu/fiji_sdma1.bin > > /lib/firmware/amdgpu/tonga_sdma.bin > > /lib/firmware/amdgpu/tonga_sdma1.bin > > /lib/firmware/amdgpu/topaz_sdma.bin > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > Building the recommended blobs fails like so: > > > > # make && make modules_install && make firmware_install > > > > CHK include/config/kernel.release > > CHK include/generated/uapi/linux/version.h > > CHK include/generated/utsrelease.h > > CHK include/generated/bounds.h > > CHK include/generated/asm-offsets.h > > CALLscripts/checksyscalls.sh > > CHK include/generated/compile.h > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > make[1]: *** No rule to make target > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > Makefile:947: recipe for target 'firmware' failed > > make: *** [firmware] Error 2 > > > > What now? > > > > PS. As VIDEO_CARDS in make.conf I used to have radeon and radeonsi, but > > have > > now changed it to amdgpu and radeonsi. Should I revert and forget about > > radeon/kaveri_sdma1.bin? > > -- > > Regards, > > Mick > > That's interesting. 'kaveri_sdma1.bin' is found in the > 'sys-firmware/amdgpu-ucode' package. See below. > % pwd > radeon_ucode/kaveri > % ls -1 *sdma* > kaveri_sdma.bin > kaveri_sdma1.bin > > Perhaps the path to the binary blobs specified in your kernel config file > is wrong? You want to double check that. > Device Drivers ---> > Generic Driver Options ---> > -*- Userspace firmware loading support > [*] Include in-kernel firmware blobs in kernel binary > (amdgpu/.bin radeon/.bin) > (/lib/firmware) Firmware blobs root directory Hmm .. perhaps I've been doing this wrong? Should I fill in: (amdgpu/kaveri.bin radeon/kaveri.bin) instead of: (radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin radeon/kaveri_vce.bin) I've been doing the latter for as long as I can remember. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
On Tue, Dec 22, 2015 at 9:39 PM, Mick wrote: > On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > > On Sun, Dec 20, 2015 at 9:04 PM, Mick wrote: > > > > This is not working for me on a Kaveri system. > > > > > > The wiki page suggests these firmware blobs: > > > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > > radeon/kaveri_vce.bin > > > > > > Unfortunately, radeon/kaveri_sdma1.bin does 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-firmware/amdgpu-ucode, but KAVERI is not found there > > > either: > > > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > > /lib/firmware/amdgpu/carrizo_sdma.bin > > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > > /lib/firmware/amdgpu/fiji_sdma.bin > > > /lib/firmware/amdgpu/fiji_sdma1.bin > > > /lib/firmware/amdgpu/tonga_sdma.bin > > > /lib/firmware/amdgpu/tonga_sdma1.bin > > > /lib/firmware/amdgpu/topaz_sdma.bin > > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > > > > Building the recommended blobs fails like so: > > > > > > # make && make modules_install && make firmware_install > > > > > > CHK include/config/kernel.release > > > CHK include/generated/uapi/linux/version.h > > > CHK include/generated/utsrelease.h > > > CHK include/generated/bounds.h > > > CHK include/generated/asm-offsets.h > > > CALLscripts/checksyscalls.sh > > > CHK include/generated/compile.h > > > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > > make[1]: *** No rule to make target > > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > > Makefile:947: recipe for target 'firmware' failed > > > make: *** [firmware] Error 2 > > > That's interesting. 'kaveri_sdma1.bin' is found in the > > 'sys-firmware/amdgpu-ucode' package. See below. > > % pwd > > radeon_ucode/kaveri > > I don't seem to have such a directory, or the files therein. Where am I > supposed to look? > > This is what emerge -uaDv sys-firmware/amdgpu-ucode installed on my PC: > > >>> Installing (1 of 1) sys-firmware/amdgpu-ucode-20150803::gentoo > * checking 44 files for package collisions > >>> Merging sys-firmware/amdgpu-ucode-20150803 to / > --- /lib/ > --- /lib/firmware/ > --- /lib/firmware/amdgpu/ > >>> /lib/firmware/amdgpu/carrizo_ce.bin > >>> /lib/firmware/amdgpu/carrizo_me.bin > >>> /lib/firmware/amdgpu/carrizo_mec.bin > >>> /lib/firmware/amdgpu/carrizo_mec2.bin > >>> /lib/firmware/amdgpu/carrizo_pfp.bin > >>> /lib/firmware/amdgpu/carrizo_rlc.bin > >>> /lib/firmware/amdgpu/carrizo_sdma.bin > >>> /lib/firmware/amdgpu/carrizo_sdma1.bin > >>> /lib/firmware/amdgpu/carrizo_uvd.bin > >>> /lib/firmware/amdgpu/carrizo_vce.bin > >>> /lib/firmware/amdgpu/fiji_ce.bin > >>> /lib/firmware/amdgpu/fiji_mc.bin > >>> /lib/firmware/amdgpu/fiji_me.bin > >>> /lib/firmware/amdgpu/fiji_mec.bin > >>> /lib/firmware/amdgpu/fiji_mec2.bin > >>> /lib/firmware/amdgpu/fiji_pfp.bin > >>> /lib/firmware/amdgpu/fiji_rlc.bin > >>> /lib/firmware/amdgpu/fiji_sdma.bin > >>> /lib/firmware/amdgpu/fiji_sdma1.bin > >>> /lib/firmware/amdgpu/fiji_smc.bin > >>> /lib/firmware/amdgpu/fiji_uvd.bin > >>> /lib/firmware/amdgpu/fiji_vce.bin > >>> /lib/firmware/amdgpu/tonga_ce.bin > >>> /lib/firmware/amdgpu/tonga_mc.bin > >>> /lib/firmware/amdgpu/tonga_me.bin > >>> /lib/firmware/amdgpu/tonga_mec.bin > >>> /lib/firmware/amdgpu/tonga_mec2.bin > >>> /lib/firmware/amdgpu/tonga_pfp.bin > >>> /lib/firmware/amdgpu/tonga_rlc.bin > >>> /lib/firmware/amdgpu/tonga_sdma.bin > >>> /lib/firmware/amdgpu/tonga_sdma1.bin > >>> /lib/firmware/amdgpu/tonga_smc.bin > >>> /lib/firmware/amdgpu/tonga_uvd.bin > &
[gentoo-user] Re: Do I need firmware for an integrated graphics unit?
On 2024-08-20, Alan Mackenzie wrote: > I've just treated myself to a new machine based on a Ryzen 9 7900 > processor. I chose the second newest generation so as not to get caught > out with not quite debugged systems like I did the last time round. > > Anyhow, I'm up to the stage of configuring the kernel, and I'm stuck at > the bit where I need to specify the firmware to be incorporated into the > kernel for the integrated graphics processor. I'm running a Ryzen 5 3400G with Radeon Vega graphics: $ lspci | grep -i vga 2a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) $ dmesg | grep -i firmware [0.091814] Spectre V2 : Enabling Speculation Barrier for firmware calls [0.244487] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.261256] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [3.021472] Loading firmware: amdgpu/picasso_gpu_info.bin [3.045180] Loading firmware: amdgpu/picasso_sdma.bin [3.046559] Loading firmware: amdgpu/picasso_asd.bin [3.047121] Loading firmware: amdgpu/picasso_ta.bin [3.047408] Loading firmware: amdgpu/raven_dmcu.bin [3.048027] Loading firmware: amdgpu/picasso_pfp.bin [3.048163] Loading firmware: amdgpu/picasso_me.bin [3.048380] Loading firmware: amdgpu/picasso_ce.bin [3.048491] Loading firmware: amdgpu/picasso_rlc_am4.bin [3.048624] Loading firmware: amdgpu/picasso_mec.bin [3.048891] Loading firmware: amdgpu/picasso_mec2.bin [3.049687] Loading firmware: amdgpu/picasso_vcn.bin [3.050007] [drm] Found VCN firmware Version ENC: 1.15 DEC: 3 VEP: 0 Revision: 0 [3.050015] amdgpu :2a:00.0: amdgpu: Will use PSP to load VCN firmware [5.407436] Loading firmware: rtl_nic/rtl8168h-2.fw $ zcat /proc/config.gz | grep -i firmware CONFIG_PREVENT_FIRMWARE_BUILD=y # Firmware loader CONFIG_EXTRA_FIRMWARE="" # end of Firmware loader # Firmware Drivers CONFIG_FIRMWARE_MEMMAP=y # CONFIG_GOOGLE_FIRMWARE is not set # Tegra firmware driver # end of Tegra firmware driver # end of Firmware Drivers # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set # CONFIG_FIRMWARE_EDID is not set # CONFIG_TEST_FIRMWARE is not set CONFIG_GENTOO_PRINT_FIRMWARE_INFO=y $ equery files linux-firmware | egrep 'picasso_|raven_' /lib/firmware/amdgpu/picasso_asd.bin /lib/firmware/amdgpu/picasso_ce.bin /lib/firmware/amdgpu/picasso_gpu_info.bin /lib/firmware/amdgpu/picasso_me.bin /lib/firmware/amdgpu/picasso_mec.bin /lib/firmware/amdgpu/picasso_mec2.bin /lib/firmware/amdgpu/picasso_pfp.bin /lib/firmware/amdgpu/picasso_rlc.bin /lib/firmware/amdgpu/picasso_rlc_am4.bin /lib/firmware/amdgpu/picasso_sdma.bin /lib/firmware/amdgpu/picasso_ta.bin /lib/firmware/amdgpu/picasso_vcn.bin /lib/firmware/amdgpu/raven_asd.bin /lib/firmware/amdgpu/raven_ce.bin /lib/firmware/amdgpu/raven_dmcu.bin /lib/firmware/amdgpu/raven_gpu_info.bin /lib/firmware/amdgpu/raven_kicker_rlc.bin /lib/firmware/amdgpu/raven_me.bin /lib/firmware/amdgpu/raven_mec.bin /lib/firmware/amdgpu/raven_mec2.bin /lib/firmware/amdgpu/raven_pfp.bin /lib/firmware/amdgpu/raven_rlc.bin /lib/firmware/amdgpu/raven_sdma.bin /lib/firmware/amdgpu/raven_ta.bin /lib/firmware/amdgpu/raven_vcn.bin
Re: [gentoo-user] using Wifi in a new machine
On Thursday, 1 June 2023 19:54:08 BST Philip Webb wrote: > 230531 Michael wrote: > > It seems you have the correct module for the mediatek driver installed, > > since lshw on gentoo shows it being used. What is not shown is the > > firmware. Now, to bottom out the firmware issue. > > You need to specify the firmware path in your kernel, as explained here. > > By default this would be under /lib/firmware/ : > > https://wiki.gentoo.org/wiki/Linux_firmware > > /lib/firmware/ is the dir with firmware files. > > > Hopefully, the requisite firmware file blobs will be present > > in the latest stable 'sys-kernel/linux-firmware' package, > > once you install it. > > It is already installed (230404) , presumably as part of Stage 3. > That date shouldn't be too old. The current stable version is: sys-kernel/linux-firmware-20230515 I suggest you run an update to fetch this version - see below. > > dmesg will reveal if these are/not being loaded. > > 'dmesg | grep firmware' shows 10 identical lines : > > Loading firmware : mediatek/WIFI_MT7921_patch_mcu_1_2_hdr.bin : >failed with error-2 . Oops! This is rather ominous and the cause of your problems - see below. > > you could keyword the trunk version hoping it contains what you need: > >** *l^bstd [compress-xz compress-zstd initramfs > > > > +redistributable savedconfig unknown-license] ["initramfs? ( > > redistributable ) ?? ( compress-xz compress-zstd )"] > > I don't understand these lines (smile). This is the bleeding edge version of the package, but you may not need to install it (yet). > > Or, you could compare what firmware files are loaded in Mint/SR ISOs > > and copy these over to your Gentoo system for now > > SR shows no record of loading via 'dmesg' ; > Mint ends with a lot of Bluetooth + mt7921e references. > Mint mentions a firmware " 01 " ( 4 underlines ). Hmm ... Mint seems to be using an older version, which according to this post has since been patched: https://lore.kernel.org/lkml/3198471.FQF0JACdhR@ripper/ > > or you could fish around the Mediatek website for approp firmware files. > > no sign of firmware files. OK. I had a look in the latest stable version sys-kernel/linux-firmware-20230515 for the file you reported an error on: $ find /lib/firmware -iname WIFI_MT7961_patch_mcu_1_2_hdr.bin /lib/firmware/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin $ ls -la /lib/firmware/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin -rw-r--r-- 1 root root 92192 May 18 16:16 /lib/firmware/mediatek/ WIFI_MT7961_patch_mcu_1_2_hdr.bin Do you get the same result? I'd update to the latest linux-firmware version first, just in case. > > Finally, set up a symlink from '/etc.init.d/net.wlp5s0' > > to '/etc/init.d/net.lo' or whatever your card is detected, if not wlp5s0. > > i've created that link, but how is it supposed to help ? This is merely to bring up the interface and establish your wireless network service at boot time, if you add it to the default run level: rc-update add net.wlp5s0 default but until you get it working, you can use this service to start/stop your wireless connection manually. > > https://wiki.gentoo.org/wiki/Handbook:AMD64/Networking/Introduction > > > > and bring up your wireless network service: > > 'rc-service -v net.wlp5s0 start' > > it gives "ERROR : fails to start". Yes, because there is the previous problem with the firmware. > > Besides wpa_supplicant, other packages required like 'net-misc/netifrc', > > 'net-misc/dhcpcd' should be installed, > > if they have not been brought in as dependencies already. > > I've installed 'netifrc' ; 'dhcpcd' was installed long ago. > > > Please post back your dmesg and any terminal output, > > if you are still having problems bringing up this wireless interface. > > PS. This page which may or may not be still relevant > > with the latest stable kernels, but you may want to take a look either > > way: > > https://wiki.gentoo.org/wiki/User:Chess/MT7921e > > So no progress today. I can try copying the firmware files from SR/Mint > -- everything under /lib/firmware/ in SR/Mint & see if it helps. Not yet, let's see if the missing firmware file is available in your /lib/ firmware first. signature.asc Description: This is a digitally signed message part.
[gentoo-user] Broadcom firmware doesn't work with 2.6.32-r4
Hi collective, I just upgraded from linux-2.6.32-tuxonice-r1 to r4 and my network card no longer works. It is "Broadcom Corporation NetXtreme BCM5756ME Gigabit Ethernet PCI Express" and previously I've downloaded firmware from http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware-from-kernel.git;a=tree;f=tigon and put it in /lib/firmware/tigon The config option is tg3, built into the kernel. dmesg shows: $ dmesg | grep -i tg3 tg3.c:v3.102 (September 1, 2009) tg3 :09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 tg3 :09:00.0: setting latency timer to 64 tg3 0000:09:00.0: firmware: requesting tigon/tg3_tso.bin tg3: tg3_load_firmware_cpu: Trying to load TX cpu firmware on eth0 which is 5705. tg3: tg3_load_firmware_cpu: Trying to load TX cpu firmware on eth0 which is 5705. I don't know if the last two lines are normally there or not. The firmware at the above link hasn't changed (according to cksum). Google searches only produce the source code, which is pretty but doesn't help. The error detection around the print message hasn't changed since -r1. Any ideas? I'm stuck using wireless, but that's dropping in and out all the time! thanks, -- Iain Buchanan Experience is that marvelous thing that enables you recognize a mistake when you make it again. -- Franklin P. Jones
Re: [gentoo-user] dracut vs. genkernel
Am 12.06.2013 17:53, schrieb Canek Peláez Valdés:
> I use this script to generate my initramfs:
>
>
> #!/bin/sh
>
> KVER=$(readlink /usr/src/linux | sed "s/^linux-//g")
>
> echo "Creating initrd for kernel version ${KVER}..."
>
> FIRMWARE=""
>
> for i in $(find /lib64/firmware -type f); do
> FIRMWARE+=" ${i}"
> done
>
> /usr/bin/dracut -f -H -I "${FIRMWARE}" /boot/initrd-${KVER} ${KVER}
>
>
> I use this command to generate my GRUB2 config:
>
> grub2-mkconfig -o /boot/grub2/grub.cfg
>
> Everything just works. However, I don't use LVM, and I don't use the
> systemd-love overlay.
Nice script, thanks!
I will have to adapt it a bit to be able to use it with
linux -> /usr/src/linux-git
But for stuff like gentoo-sources it just works, yes!
Stefan
Re: [gentoo-user] AMD microcode error?
On Sunday, 28 January 2024 16:59:52 GMT Mark Knecht wrote: > On Sun, Jan 28, 2024 at 9:49 AM Peter Humphrey > > wrote: > > On Sunday, 28 January 2024 16:39:56 GMT I wrote: > > > Hits on the web suggest downgrading linux-firmware, which I've now done > > and > > > > will await results. The latest upgrade was to version 20240115-r1, four > > days > > > > ago. > > > > s/Hits/Hints/ > > > > -- > > Regards, > > Peter. > > If it is a memory error then there are there possibilities: > > 1) The new linux-firmware has a problem and the error is untrue > > 2) The DRAM was bad but not tested earlier and is true > > 3) The DRAM has gone bad and the error is true > > A reasonable next step is to run some sort of longer term > memory test, memtest 86, memtest64 or something else of your choice. > > Good luck, > Mark I'm not sure a microcode update has been released yet by AMD as a blob, outside what they make available to MoBo OEMs within 'BIOS firmware' updates. To find what's in the box use: dmesg | grep -i 'family:' Then check what CPU family and model microcodes the linux-firmware contains: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ tree/amd-ucode/README If you can't find your family and model in the above, then you could check what firmware updates are available by the MoBo's OEM. These would include microcode made directly available by AMD to the OEM. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] r8169 unable to apply firmware patch
> I'm guessing that radeon-ucode and rt61-firmware and all the others > are being deprecated in favour of linux-firmware, but i don't recall > seeing an elog on it. Does anyone know if this is the case? Doesn't seem very Gentoo-like, although it should minimize package management for the devs which is good. >> but now >> that I look closer I realize that ifconfig doesn't show an eth0 >> interface at all even though lspci -v shows: >> >> Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI >> Express Gigabit Ethernet controller >> ... >> Kernel driver in use: r8169 >> >> Shouldn't the eth0 interface appear in ifconfig once the r8169 driver >> is loaded? dmesg has no mention of eth0 or r8169. > > That's odd. Does that box still have the failed loading firmware > error? Perhaps missing firmware stops eth0 from being created. I'd try > installing linux-fireware and trying again (assuming you havent > already). I didn't have the firmware error on the desktop but I installed linux-firmware and now eth0 is renamed to eth1 and appears under iwconfig (no wireless extensions) but not under ifconfig. My laptop's r8169 eth0 appears under ifconfig even when there's no ethernet cable attached. That's the expected behavior isn't it? - Grant
Re: [gentoo-user] Broadcom firmware doesn't work with 2.6.32-r4
Check out http://bugs.gentoo.org/show_bug.cgi?id=304265 and then update to 2.6.32-r5 Cheers Kad On Wed, Feb 10, 2010 at 11:24 PM, Iain Buchanan wrote: > Hi collective, > > I just upgraded from linux-2.6.32-tuxonice-r1 to r4 and my network card > no longer works. It is "Broadcom Corporation NetXtreme BCM5756ME > Gigabit Ethernet PCI Express" and previously I've downloaded firmware > from > > http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware-from-kernel.git;a=tree;f=tigon > and put it in /lib/firmware/tigon > > The config option is tg3, built into the kernel. > > dmesg shows: > $ dmesg | grep -i tg3 > tg3.c:v3.102 (September 1, 2009) > tg3 :09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > tg3 :09:00.0: setting latency timer to 64 > tg3 :09:00.0: firmware: requesting tigon/tg3_tso.bin > tg3: tg3_load_firmware_cpu: Trying to load TX cpu firmware on eth0 which is > 5705. > tg3: tg3_load_firmware_cpu: Trying to load TX cpu firmware on eth0 which is > 5705. > > I don't know if the last two lines are normally there or not. The > firmware at the above link hasn't changed (according to cksum). > > Google searches only produce the source code, which is pretty but > doesn't help. The error detection around the print message hasn't > changed since -r1. > > Any ideas? I'm stuck using wireless, but that's dropping in and out all > the time! > > thanks, > -- > Iain Buchanan > > Experience is that marvelous thing that enables you recognize a mistake > when you make it again. >-- Franklin P. Jones > > > >
Re: [gentoo-user] How to tell what the current AMD microcode level is?
On Sun, Dec 8, 2019 at 9:39 AM Daniel Frey wrote: > Well, I managed to get my hands on a Ryzen 3950x. > Nice. I figured I should be updating the microcode... so I set up early > updating but it isn't doing anything. > > dmesg is listing what the current microcode level is. The problem is, I > can't find anywhere that lists what the current (or latest) microcode > version is supposed to be in linux-firmware. > > This processor is so new that it's possible that there are no updates > for it but I'd like to make sure. > > I've tried the early microcode update process on my Intel laptop and it > works, so all I can think of is there are no microcode updates. > > Does anyone know of a list of microcode versions? > I dont know, so i just use the ~amd64 linux-firmware version. For my 3900X its currently; microcode: CPU0: patch_level=0x08701013 The last update came through in October; firmware-md5s-2019-09-09.txt:fef89be989f6a160b340027a24cd0a16 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin firmware-md5s-2019-09-25.txt:fef89be989f6a160b340027a24cd0a16 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin firmware-md5s-2019-10-23.txt:a30e5f81d37ed38faf039b75bc376197 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin firmware-md5s-2019-11-12.txt:a30e5f81d37ed38faf039b75bc376197 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin
Re: [gentoo-user] Weird system freeze?
On Tue, Jun 11, 2024 at 07:45:09PM +0100, Michael wrote > > The above errors are an indication something is amiss with the > requisite firmware for your graphics. > Have you specified this in your kernel, or in your initramfs? OK, I've downloaded kbl_dmc_ver1_04.bin now, but I'm having problems implementing it. First I saved it to /lib/firmware, entered the firmware name in "make menuconfig" (Build named firmware blobs into the kernel) and recompiled; same error message about no such file. Then I created subdirectory /lib/firmware/i915 and moved the bin there. I changed the entry in "make menuconfig" to "i915/kbl_dmc_ver1_04.bin" and recompiled. It finds the file now, but still errors out. dmesg says = [0.221960] Loading firmware: i915/kbl_dmc_ver1_04.bin [0.221962] i915 :00:02.0: [drm] *ERROR* DMC firmware has wrong CSS header length (1097158924 bytes) [0.221964] i915 :00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management. [0.221967] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 = Any ideas what I'm doing wrong? And why is it trying to load the file even after I (try to) build it into the kernel? -- Roses are red Roses are blue Depending on their velocity Relative to you
Re: [gentoo-user] ipw2200 dmesg error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marco Calviani wrote: > Hi list, > i'm running gentoo on a laptop with a ipw2200 wireless card. I'm > running the current ipw2200 stable version, that is ipw2200-1.0.8-r1. > It is running well but when used i'm seeing in the kernel messages the > following messages: > > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log captured. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > ipw2200: Firmware error detected. Restarting. > ipw2200: Sysfs 'error' log already exists. > > Is this a known issue of these drivers? > > Thanks in advance, > MC > I haven't seen that. I do use ipw2200 and ipw2200-firmware and at least this driver works and I've not seen such a message like that. I'm using linux-2.6.14-gentoo-r4. Bye, Rafael Fernández López. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDym2q9RRlaicc3IERAvKzAKCKMEjeSaVE8EIEUnYf5Yr7aJVsGQCfRowi nDAfBtVNCTF8TgdpFGPC2oE= =P1Xo -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
On 12/13/2020 04:44 PM, Michael wrote: > On Sunday, 13 December 2020 18:52:51 GMT the...@sys-concept.com wrote: >> I have "nouveau" build into kernel but it doesn't work: >> >> Fom dmesg: >> >> nouveau :08:00.0: NVIDIA GP107 (137000a1) >> nouveau :08:00.0: gr: failed to load firmware "gr/sw_nonctx" >> nouveau :08:00.0: gr: failed to load gr/sw_nonctx >> nouveau :08:00.0: DRM: failed to create kernel channel, -22 >> >> grep -i nouveau .config >> CONFIG_DRM_NOUVEAU=y >> # CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT is not set >> CONFIG_NOUVEAU_DEBUG=5 >> CONFIG_NOUVEAU_DEBUG_DEFAULT=3 >> # CONFIG_NOUVEAU_DEBUG_MMU is not set >> CONFIG_DRM_NOUVEAU_BACKLIGHT=y > > I've never used NVIDIA cards with Gentoo, but in firmware terms you need to > specify in your kernel what firmware you want installed in it. Have a look > at > this guide: > > https://wiki.gentoo.org/wiki/Nouveau/en > > and this: > > https://wiki.gentoo.org/wiki/Linux_firmware > > You'll need to add the firmware the video card asks for here: > > Device Drivers ---> > Generic Driver Options ---> > Firmware loader ---> >-*- Firmware loading facility >() Build named firmware blobs into the kernel binary <== > > In this instance your card NVIDIA GP107 should need '/lib/firmware/nvidia/ > gp107', so the respective entry for it in the kernel config ought to be: > > CONFIG_EXTRA_FIRMWARE="nvidia/gp107" > > Someone more clued up on these cards can correct me or add to it. Thank you, but I've managed to install "nvidia" following: https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers What confused me is the output from two kernels: linux-5.4.80-gentoo-r1 was installed with: genkernel --menuconfig all and "nouveau" was working OK on that kernel: grep CONFIG_EXTRA_FIRMWARE ../linux-5.4.80-gentoo-r1/.config showing: CONFIG_EXTRA_FIRMWARE="" The one below was compiled manually: grep CONFIG_EXTRA_FIRMWARE ../linux-5.4.72-gentoo/.config CONFIG_EXTRA_FIRMWARE="" Both had same output, so why one kernel was working the other didn't?
[gentoo-user] Firmware updates
Greetings, off and on I'm receiving updates of packages "sys-firmware/intel-micro- code" and "sys-kernel/linux-firmware". My kernel has $ grep ^CONFIG_EXTRA_FIRMWARE /usr/src/linux/.config CONFIG_EXTRA_FIRMWARE="intel-ucode/06-5e-03 i915/skl_dmc_ver1_27.bin regulatory.db regulatory.db.p7s iwlwifi-3160-17.ucode" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" $ Is there any need for some postprocessing like booting when either of these packages is updated? Normally my laptop is regularly hibernated but it is rarely booted. Sincerely, Rainer
Re: [gentoo-user] Where are the AMD microcode updates for spectre?
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 juice to do > it? I need fam15h. > > AMD is being annoying and not releasing them to the plebians only OEM > partners - I assume perhaps to encourage people to buy new hardware as > most OEM's won't release BIOS updates for older boards. > > Thanks. . Emerge this package : "sys-kernel/linux-firmware" You can find the blobs in : /lib/firmware/amd-ucode/ If you already have "sys-kernel/linux-firmware" emerged and the blobs aren't showing, un-merge it, and the re-emerge it. . Gentoo does have the newer microcode blobs stashed on a server ( somewhere ). That does pull in the blobs for : Fam10h ( microcode_amd.bin ) Fam15h ( microcode_amd_fam15h.bin ) Fam16h ( microcode_amd_fam16h.bin ) Fam17h ( microcode_amd_fam17h.bin ) . If you have an AMDGPU and use the "amdgpu" driver, firmware will be here : /lib/firmware/amdgpu . Corbin
Re: [gentoo-user] Re: new mobo : Eth0 recovered
On Saturday 21 April 2012 16:21:31 Nikos Chantziaras wrote: > Do a: > >dmesg | grep -i firmware > > and check for firmware loading errors. I have what seems to be the same network hardware, so I did what you said and duly found an error. I hadn't had any obvious network performance problems but I emerged linux-firmware anyway. After the next reboot (without any firmware loading errors) kmail couldn't send any e-mails, complaining each time that it was unable to create an SMTP packet (I think that's what it said). So I removed linux-firmware, rebooted and got kmail back. Go figure. :-) -- Rgds Peter
Re: [gentoo-user] No wifi
On Tue, Jul 14, 2020 at 10:31:21AM -0400, Walter Dnes wrote: > One thing I should've mentioned in the first post is that booting from > the minimal install USB, wlan0 does show up, so the hardware works. That's because the "minimal" install disk actually has quite a lot of stuff installed/enabled, to support all (or, as much as possible) common hardware in a live environment, as this generally runs before the point at which the user can configure their own kernel. > On Tue, Jul 14, 2020 at 05:59:37AM +0100, Ashley Dixon wrote > > It doesn't look like it's loading the firmware. Are there any obvious > > firmware-loading errors in dmesg ? > > What is ASPM and what is error -2? BTW, on my first attempt, when I > accidentally tried a non-existant firmware path, the kernel compile died > early on. Here is what I get in dmesg with ucode 8.83.5.1-1 Error -2 means that it can't find the file: "ENOENT 2 No such file or directory". You should install the firmware through `sys-kernel/linux-firmware`, and then edit your .config accordingly (as Michael mentioned, no subdirectories are added by the Gentoo package): CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" CONFIG_EXTRA_FIRMWARE="iwlwifi-5000-1.ucode iwlwifi-5000-2.ucode iwlwifi-5000-5.ucode" > > That looks fine, although why are you using such an outdated version > > of the microcode ? For kernels 2.6.38+, you can use 8.83.5.1-1. > > The way the items lined up on the webpage, I mis-interpreted it to > mean one driver for 5100AGN, one for 5300AGN, and one for 5350AGN. See > attachment. The table is slightly misleading, but I think that any of the listed firmware packages can work for any of the listed devices, and the only distinction between the files is the supported kernel versions. Thus, you should be able to safely use the latest version. > > Perhaps it would be better to install it from > > the Gentoo-provided firmware package ? Amend > > /etc/portage/savedconfig/sys-kernel/linux-firmware to include the > > appropriate entries (listing at [1]), and emerge `linux-firmware` > > with the `savedconfig` USE-flag. > > I'll do that next if there's nothing obvious here. Yes, that is your next step. Append the appropriate entries to your savedconfig file and emerge `linux-firmware` with `savedconfig`: iwlwifi-5000-1.ucode iwlwifi-5000-2.ucode iwlwifi-5000-5.ucode -- Ashley Dixon suugaku.co.uk 2A9A 4117 DA96 D18A 8A7B B0D2 A30E BF25 F290 A8AA signature.asc Description: PGP signature
Re: [gentoo-user] Loading a Firmware Module By hand?
On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote: > Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version > 9 as well, but that didn't help matters, either. Nor did > compiling the firmware into the kernel; either 4.14 is too old, or it > is too new. I'd think they are both too new? > I tried copying the firmware my live iso was using, but > that didn't help either. If the live iso works, start with using the same kernel release and linux- firmware version, to see if this works as expected on your installation. Then update kernel sources and firmware to the latest stable and see if this works too. >From there on you can move into ~arch to find the version at which things break. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Loading a Firmware Module By hand?
Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version 9 as well, but that didn't help matters, either. Nor did compiling the firmware into the kernel; either 4.14 is too old, or it is too new. I tried copying the firmware my live iso was using, but that didn't help either. On 12/17/17, Andrey Utkin wrote: > On Sun, Dec 17, 2017 at 12:34:14AM -0500, Hunter Jozwiak wrote: >> Hi, >> >> I have an ath10k_pci device that I'm trying to get hooked to the >> Internet, but I'm having some strange issues. It is trying to load the >> 2.1 firmware, but I don't think that is the proper firmware for the >> interface to have; I think it ought to be loading the 3.0 module, but >> am not quite sure on that either, or how I could go about injecting >> that into the modprobe; I wasn't able to pinpoint the firmware blob >> the ISO was using, so that wasn't much of a pointer in the right >> direction either. I see that the 3.0 blob does exist in >> /lib/firmware/ath10k/QCABLEFAGD/HW3.0, but there are many bin files, > > I have little to no idea about your actual case... But could it be that > you have a recent linux-firmware package (which provides /lib/firmware/ > files) and not recent enough kernel? I think kernel is what decides > which firmware file to load. >
Re: [gentoo-user] Where are the AMD microcode updates for spectre?
On 05/20/2018 03:59 AM, Adam Carter wrote: > > > This has indeed been pretty frustrating. > > As far as I can tell there is no official AMD microcode update > page, or any > kind of official release notes. I'm not sure where linux-firmware > actually > gets the microcode files from (I'm sure they wouldn't load if they > weren't > genuine though). I can find no documentation as to what any of these > updates actually do. > > It sounds like AMD intends for the microcode updates to be > distributed via > firmware updates, in which case the fixes would be done before > boot. That > is a good thing of course, but they should still release the microcode > files themselves, and also have release notes for something like this. > > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8 > > > Bulldozer and Zen updates! Thanks for the info. How often does the linux-firmware package update? On a schedule or as needed? Corbin
Re: [gentoo-user] Kernel build error
Dale wrote: > Hi, > > I'm trying to upgrade my kernel but I got this. > > r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # make all && make > modules_install > CHK include/linux/version.h > CHK include/linux/utsrelease.h > CALLscripts/checksyscalls.sh > CHK include/linux/compile.h > make[1]: *** No rule to make target `n/n', needed by > `firmware/n.gen.o'. Stop. > make: *** [firmware] Error 2 > r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # > > I have always used that command but it doesn't usually end like this. I > think that is right. What is target 'n/n'? Am I missing something? > Kernel version is in the prompt up there too. > > Thanks. > > Dale > > :-) :-) > > What firmware drivers had you enabled when you configured the kernel?
Re: [gentoo-user] Weird system freeze?
On Tuesday, 11 June 2024 19:30:28 BST Walter Dnes wrote: > On Tue, Jun 11, 2024 at 11:05:27AM +0100, Michael wrote > > > Can you share the output of your dmesg? > > The only potentially interesting stuff is attempting to load a couple > of firmware blobs that I'm not aware of... > > [0.220521] Loading firmware: i915/kbl_dmc_ver1_04.bin > [0.220530] i915 :00:02.0: Direct firmware load for > i915/kbl_dmc_ver1_04.bin failed with error -2 [0.220533] i915 > :00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. > Disabling runtime power management. [ 0.220535] i915 :00:02.0: [drm] > DMC firmware homepage: > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > /tree/i915 > ***** [ > 57.302978] Loading firmware: rtl_nic/rtl8168h-2.fw > [ 57.302993] r8169 :01:00.0: Direct firmware load for > rtl_nic/rtl8168h-2.fw failed with error -2 [ 57.302997] r8169 > :01:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-2) The above errors are an indication something is amiss with the requisite firmware for your graphics. Have you specified this in your kernel, or in your initramfs? See here: https://wiki.gentoo.org/wiki/Intel The rtl8168h is related to your NIC. Assuming you have configured this, does 'ethtool -i eth0' or whatever you card is detected as show if the firmware has been loaded? > > Next time it happens you can boot straight back into a LiveUSB and > > save dmesg, syslog and Xorg.0.log from your disk, where the errors > > related to the crash should have been captured. > It's too late now. The only potentially interesting stuff is.. > . > [89.701] (EE) Unable to locate/open config file: "xorg.conf" [snip ...] Nothing interesting in that, but dmesg reveals a firmware issue. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] USB sync/async mount
On Monday 27 March 2006 18:11, "b.n." <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-user] USB sync/async mount': > Boyd Stephen Smith Jr. wrote: > > Check out the flash players from iRiver. They play ogg, mp3, and wav, > > and with the proper firmware are accessible as a USB device. > > Thanks! I have a mp3/wmv only flash player I received as a gift but I'd > like to upgrade it with a 1-gb thing ogg-capable, if possible. > I'll look at iRiver. I'm very happy with my iRiver 799-FP (1G). > > Also, files can be deleted and loaded from linux even with the stock > > firmware. > > I'm a bit confused. > Is the flash player recognized as a simple usb flash drive or what? The stock firmware does not show up as a USB block device under either Windows or Linux. There is an official USB firmware that you can download and install that makes it act like a standard USB block device under both operating systems. This has the side effect of rendering the (Windows-only) software they provide for managing the device unusable, but you don't really need it anymore since it's just DnD to load and unload the thing. They don't really publicize the USB firmware; in fact, I had to download it from a non-US site. I think it might has something to do with the draconian US copyright laws or pressure from the RIAA, but I don't really know. Personally, I ended up installing a modified firmware that extends the range of OGG playback and voice recording bitrates. It's a modified version of the USB firmware, so I got access to the device as a USB block device for free. Going back to the stock firmware -- there's a linux utility that provides command-line features roughly equivalent to the (Windows-only) software they provide to manipulate the device. So, you'll be able to load/delete files from Linux and Windows no matter what firmware you are using. -- "If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability." -- Gentoo Developer Ciaran McCreesh pgpotemLZlFZV.pgp Description: PGP signature
Re: [gentoo-user] problem compiling Kernel 6.1.27-gentoo-r1
On Saturday, 20 May 2023 07:59:59 BST Philip Webb wrote: > I'm trying to install Gentoo in my new machine > & have got to the step of compiling a kernel. > I used the config file from my present machine, did 'make oldconfig' > & have then done 'make menuconfig' to include drivers etc. > > The 'make' stage goes on for a long time, then crashes doing > 'UPD drivers/base/firmware_loader/builtin/rtl_nic/rtl8168g-2.fw.gen.S' > with message "make [5] *** No rule to make target > 'lib/firmware/rtl_nic/rtl8168g-2.fw' needed by > 'drivers/base/firmware_loader/ builtin/rtl_nic/rtl8168g-2.fw.gen.o' Stop". > > The relevant line in Menuconfig is 'DeviceDrivers > NetworkDeviceSupport > > EthernetDriverSupport' under 'Realtek devices'. > I've tried it with 'Realtek8169/8168/...' 'Y' or 'M' or 'N' > & also with 'Realtek devices' as 'N'. I also tried a 'make clean'. > The same error goes on happening. > > Since I don't have anything by Realtek for networking > -- sound uses Realtek -- , I can't understand the behaviour above. > > Can anyone offer any advice ? The compilation complains it is missing the firmware required by a realtek NIC, probably a setting inherited from the config settings of the old kernel? You eventually compiled it with "N". I suspect the order in which you configured/compiled it plays a role in this error. Since you do not have this hardware, set it to "N", then run: make clean && make && make install modules_install . Meanwhile, check if you have the firmware file it asks for, which would have been installed as part of 'sys-kernel/linux-firmware': $ ls -la /lib/firmware/rtl_nic/rtl8168g-2.fw -rw-r--r-- 1 root root 4896 May 18 16:15 /lib/firmware/rtl_nic/rtl8168g-2.fw $ qfile /lib/firmware/rtl_nic/rtl8168g-2.fw sys-kernel/linux-firmware: /lib/firmware/rtl_nic/rtl8168g-2.fw When you update world after you have compiled your new kernel, linux-firmware will be installed and the missing file will be available anyway - although no longer needed or used by the kernel. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] (Solved) anyone tried amdgpu (kernel module)
> 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 > [*] Include in-kernel firmware blobs in kernel binary > (amdgpu/.bin radeon/.bin) > (/lib/firmware) Firmware blobs root directory > > > > Yes I have the firmware includes, I'll try the amdgpu-ucode and report back. > > > - > > > Mission successful! Thanks everyone, it appears the missing sdma1.bin from > linux-firmware is contained in amdgpu-ucode and after switching everything is > running fine. > > > > Good to hear. Thanks for letting us know.
Re: [gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
On Monday, 14 December 2020 00:27:03 GMT the...@sys-concept.com wrote: > On 12/13/2020 04:44 PM, Michael wrote: > > On Sunday, 13 December 2020 18:52:51 GMT the...@sys-concept.com wrote: > >> I have "nouveau" build into kernel but it doesn't work: > >> > >> Fom dmesg: > >> > >> nouveau :08:00.0: NVIDIA GP107 (137000a1) > >> nouveau :08:00.0: gr: failed to load firmware "gr/sw_nonctx" > >> nouveau :08:00.0: gr: failed to load gr/sw_nonctx > >> nouveau :08:00.0: DRM: failed to create kernel channel, -22 > >> > >> grep -i nouveau .config > >> CONFIG_DRM_NOUVEAU=y > >> # CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT is not set > >> CONFIG_NOUVEAU_DEBUG=5 > >> CONFIG_NOUVEAU_DEBUG_DEFAULT=3 > >> # CONFIG_NOUVEAU_DEBUG_MMU is not set > >> CONFIG_DRM_NOUVEAU_BACKLIGHT=y > > > > I've never used NVIDIA cards with Gentoo, but in firmware terms you need > > to > > specify in your kernel what firmware you want installed in it. Have a > > look at> > > this guide: > > https://wiki.gentoo.org/wiki/Nouveau/en > > > > and this: > > https://wiki.gentoo.org/wiki/Linux_firmware > > > > You'll need to add the firmware the video card asks for here: > > > > Device Drivers ---> > > > > Generic Driver Options ---> > > > > Firmware loader ---> > > > >-*- Firmware loading facility > >() Build named firmware blobs into the kernel binary <== > > > > In this instance your card NVIDIA GP107 should need '/lib/firmware/nvidia/ > > gp107', so the respective entry for it in the kernel config ought to be: > > > > CONFIG_EXTRA_FIRMWARE="nvidia/gp107" > > > > Someone more clued up on these cards can correct me or add to it. > > Thank you, but I've managed to install "nvidia" following: > https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers > > What confused me is the output from two kernels: > > linux-5.4.80-gentoo-r1 > was installed with: genkernel --menuconfig all > and "nouveau" was working OK on that kernel: > > grep CONFIG_EXTRA_FIRMWARE ../linux-5.4.80-gentoo-r1/.config showing: > CONFIG_EXTRA_FIRMWARE="" > > The one below was compiled manually: > grep CONFIG_EXTRA_FIRMWARE ../linux-5.4.72-gentoo/.config > CONFIG_EXTRA_FIRMWARE="" > > Both had same output, so why one kernel was working the other didn't? Were both of these kernels installed with a corresponding correctly functioning initramfs, which had all the requisite files (including -- firmware) to boot with, or only one of them did? Without an initramfs you will need to specify and build any requisite firmware blobs in the kernel image itself, so they are available to the system as it boots up. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Kernel build error
Saphirus Sage wrote: > Dale wrote: > >> Hi, >> >> I'm trying to upgrade my kernel but I got this. >> >> r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # make all && make >> modules_install >> CHK include/linux/version.h >> CHK include/linux/utsrelease.h >> CALLscripts/checksyscalls.sh >> CHK include/linux/compile.h >> make[1]: *** No rule to make target `n/n', needed by >> `firmware/n.gen.o'. Stop. >> make: *** [firmware] Error 2 >> r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # >> >> I have always used that command but it doesn't usually end like this. I >> think that is right. What is target 'n/n'? Am I missing something? >> Kernel version is in the prompt up there too. >> >> Thanks. >> >> Dale >> >> :-) :-) >> >> >> > What firmware drivers had you enabled when you configured the kernel? > > > Well, I copied .config from my old kernel, ran oldconfig then menuconfig to check on a couple things. Everything looked normal enough for me system. I did say no to the new stuff tho. My old kernel works fine so I am really only updating the kernel. I'm not sure what you mean by "firmware drivers"? I don't use modules but it does have a couple that are default and can't get rid of. Dale :-) :-)
Re: [gentoo-user] Kernel build error
Dale schrieb: > Hi, > > I'm trying to upgrade my kernel but I got this. > > r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # make all && make > modules_install > CHK include/linux/version.h > CHK include/linux/utsrelease.h > CALLscripts/checksyscalls.sh > CHK include/linux/compile.h > make[1]: *** No rule to make target `n/n', needed by > `firmware/n.gen.o'. Stop. > make: *** [firmware] Error 2 > r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # > > I have always used that command but it doesn't usually end like this. I > think that is right. What is target 'n/n'? Am I missing something? > Kernel version is in the prompt up there too. > > Thanks. > > Dale > > :-) :-) > > Hi, you did run oldconfig . Somewhere you said n where a number should be. Search for: External Firmware blobs to build into kernel binary (EXTRA_FIRMWARE) kh
Re: [gentoo-user] ipw2200 dmesg error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rafael Fernández López wrote: > Marco Calviani wrote: > >>>Hi list, >>> i'm running gentoo on a laptop with a ipw2200 wireless card. I'm >>>running the current ipw2200 stable version, that is ipw2200-1.0.8-r1. >>>It is running well but when used i'm seeing in the kernel messages the >>>following messages: >>> >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log captured. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>>ipw2200: Firmware error detected. Restarting. >>>ipw2200: Sysfs 'error' log already exists. >>> >>>Is this a known issue of these drivers? >>> >>>Thanks in advance, >>>MC >>> > > > I haven't seen that. I do use ipw2200 and ipw2200-firmware and at least > this driver works and I've not seen such a message like that. > > I'm using linux-2.6.14-gentoo-r4. > > Bye, > Rafael Fernández López. Sorry I did a dmesg and that message shows for me too... but less times [EMAIL PROTECTED] ~ $ dmesg | grep ipw2200 ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.10 ipw2200: Copyright(c) 2003-2005 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40 ipw2200: Firmware error detected. Restarting. ipw2200: Sysfs 'error' log captured. ipw2200: Firmware error detected. Restarting. ipw2200: Sysfs 'error' log already exists. Bye, Rafael Fernández López. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDym4Z9RRlaicc3IERAgbMAJ9S51jy2vaLEbBQxDMzKGdjt3IW3wCdGsUa wEE2TtbdVgLdzsGODQn8+bc= =zzro -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Eliminating unwanted linux-firmware blobs.
On 6/28/24 6:31 PM, Peter Humphrey wrote:
> On Friday, 28 June 2024 20:32:11 BST Tsukasa Mcp_Reznor wrote:
>
>> Remove the date.so it becomes
>> /etc/portage/savedconfig/sys-kernel/linux-firmware then it applies to all
>> of them and not the specified version.
>>
>> Hope that helps
>
> It certainly does. I wish I'd known that years ago: it would have saved me an
> awful lot of renaming.
The elog message states:
* Your configuration for sys-kernel/linux-firmware-20240610-r1 has been
saved in
* "/etc/portage/savedconfig/sys-kernel/linux-firmware-20240610-r1" for
your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
I admit that this is a bit hard to analyze...
--
Eli Schwartz
OpenPGP_0x84818A6819AF4A9B.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
Re: [gentoo-user] Re: new mobo : Eth0 recovered
Nikos Chantziaras wrote: > On 21/04/12 18:55, Dale wrote: >> Nikos Chantziaras wrote: >>> [...] >>> Also, make sure to emerge sys-kernel/linux-firmware. Without it, >>> RTL8111/8168B NICs will produce random connectivity hang-ups after a few >>> hours; they need firmware that was previously part of the kernel itself >>> but has now been split to sys-kernel/linux-firmware. >>> >>> Do a: >>> >>>dmesg | grep -i firmware >>> >>> and check for firmware loading errors. >> >> So that is what is wrong with my connection. I been having this issue >> for a while and it is getting on my nerves. Is this fix OK even if you >> don't build your drivers as modules? I build everything into the >> kernel. I never did like modules much. > > The kernel source doesn't have any firmware files in it, so it doesn't > matter whether you build the drivers into the kernel or as modules; the > firmware isn't there in either case. > > However, this particular driver (r8169), says in its description that > building as a module is recommended. However, it doesn't give you any > explanation as to why this recommendation is made. I suppose the driver > developer was working for Apple previously :-P > > Anyway, "dmesg | grep -i firmware" should tell you whether you actually > even need the firmware. If you don't get a firmware loading error in > dmesg, then you don't need it and your problem is not related. In that > case, you belong to the (quite large) group of people for which only the > net-misc/r8168 driver works reliably (which unfortunately doesn't always > support the latest linux kernel.) > > > Something like this: root@fireball / # dmesg | grep -i firmware [ 10.138253] r8169 :03:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168d-2.fw (-2) root@fireball / # Looks like I found the fix for this problem. Yeppie !! I don't use modules because a long time ago is was recommended not to. So far, I have seen no reason to change that. Sort of like using the init thingy. I may start using modules, when there is good reason to do so. I'm just a old fart that likes the old ways of doing some things. LOL I still don't like the init thingy although I am using one. :/ Thanks much. I can leave google alone now. Dale :-) :-) P. S. < dale makes note of that command. May come in handy one day. > -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Weird system freeze?
On Thu, Jun 13, 2024 at 09:33:54AM +0100, Michael wrote > For the firmware file(s) code to be built into the kernel *all* > necessary firmware files must be present in your filesystem and the > path for these defined. The i915 directory contains the attached > list of files on my system. At first I didn't understand. It asked for a file, and I gave it that file, but it still errored out. Then things got curiouser and curiouser. Webpage https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 lists kbl_dmc_ver1_04.bin as being 8840 bytes... ***BUT*** the downloaded file on my system is 62768 bytes!!! Houston... we have a problem. I dove into my download with mc, and it's actually a webpage with some binary listing! No wonder it didn't work. I tried different websites and got a 62768 byte file. I switched from Pale Moon (a Firefox fork) to Google Chrome for linux... 62768 bytes. Even wget got me a 62768 byte file. What's going on??? > PS. Your post prompted me to look into an old i915 system, where I > discovered a kernel trace hidden undetected in dmesg! Thank you. :-) > ~ $ ls -la /lib/firmware/i915/*kbl* > lrwxrwxrwx 1 root root 19 May 20 12:18 > /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin > -rw-r--r-- 1 root root 8616 May 20 12:18 > /lib/firmware/i915/kbl_dmc_ver1_01.bin > -rw-r--r-- 1 root root 8840 May 20 12:18 > /lib/firmware/i915/kbl_dmc_ver1_04.bin Is kbl_dmc_ver1_04.bin still on your system? Can you email it to me off-list as an attachment? That 8840 byte size is what I'm looking for. BTW, there is a thread... https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9244 about problems with that firmware. -- Roses are red Roses are blue Depending on their velocity Relative to you
Re: [gentoo-user] AMDGPU: computer won't shut down
On 2020-06-10 00:20, Ashley Dixon wrote: On Tue, Jun 09, 2020 at 11:53:55PM +0200, n952162 wrote: I posted about this problem perhaps a year ago - when running with AMDGPU, my system won't turn off, I have to hold the power button down for a long time, forcing it down. Thanks to all the great help here, I finally got my system properly updated and AMDGPU working, and it finally talks to my HDMI display. But, it still doesn't shut down. I assume you are using the AMDGPU drivers [1], but are you also using AMDGPU-PRO (closed-source accelerator) [2] ? AMDGPU yes AMDGPU-PRO no. Also, are you loading the firmware directly into the kernel, or as kernel modules ? # # Firmware loader # CONFIG_FW_LOADER=y CONFIG_EXTRA_FIRMWARE="amdgpu/stoney_ce.bin amdgpu/stoney_me.bin amdgpu/stoney_mec.bin amdgpu/stoney_pfp.bin amdgpu/stoney_rlc.bin amdgpu/stoney_sdma.bin amdgpu/stoney_uvd.bin amdgpu/stoney_vce.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" # CONFIG_FW_LOADER_USER_HELPER is not set CONFIG_WANT_DEV_COREDUMP=y CONFIG_ALLOW_DEV_COREDUMP=y CONFIG_DEV_COREDUMP=y # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set # CONFIG_TEST_ASYNC_DRIVER_PROBE is not set CONFIG_GENERIC_CPU_AUTOPROBE=y CONFIG_GENERIC_CPU_VULNERABILITIES=y CONFIG_REGMAP=y CONFIG_REGMAP_I2C=m CONFIG_DMA_SHARED_BUFFER=y # CONFIG_DMA_FENCE_TRACE is not set Which GPU series/firmware do you have installed [3] ? -- 00~>lspci | grep -i vga 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] (rev da) -- Volcanic Islands CARRIZO, FIJI, STONEY, TONGA, TOPAZ, WANI GCN3.x R9 285, R9 380, R9 380X, R9 Fury, R9 Nano, R9 Fury X, Pro Duo 4.5 3.2 amdgpu radeonsi -- drwxr-xr-x 2 root root 4096 Dec 15 16:50 /var/db/pkg/sys-kernel/linux-firmware-20191022 -- 00~>equery uses sys-kernel/linux-firmware-20191022 [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for sys-kernel/linux-firmware-20191022: U I - - initramfs : Create and install initramfs for early microcode loading in /boot (only AMD for now) + + redistributable : Install also non-free (but redistributable) firmware files - - savedconfig : Allows individual selection of firmware files -- [1] https://wiki.gentoo.org/wiki/AMDGPU [2] https://wiki.gentoo.org/wiki/AMDGPU-PRO [3] https://wiki.gentoo.org/wiki/AMDGPU#Incorporating_firmware (see the table)
Re: [gentoo-user] TUSB3410 on 3.0.6 kernel
2011/11/6 Érico Porto : > Ok I will try it. > I used: > make && make modules_install && make install > Doesn't the modules get made in the make part? > Érico V. Porto > > > On Sun, Nov 6, 2011 at 8:16 PM, Aljosha Papsch > wrote: >> >> 2011/11/6 Érico Porto : >> > Hello, >> > I would like to ask about the kernel 3.0.6. I can't load >> > the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it >> > makes fine, but when I type make modules_install, I get an error: >> > make[1]: *** No rule to make target `/lib/firmware/./', needed by >> > `/lib/firmware/ti_3410.fw'. Stop. >> > make: *** [_modinst_post] Error 2 >> > Has anyone tried it in the 3.0.6 kernel? My uname -a output is: >> > Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686 >> > Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux >> > My kernel was loaded using emerge. >> > Regards >> > Érico V. Porto >> > >> >> I solved this by not building firmware into kernel. It's somewhere in >> Linux config "General Options". >> > > Yes it's just make. Then I tried compiling the kernel, I got the same error with installing firmware. But I lied in the other message ;) The location of the option is: Symbol: FIRMWARE_IN_KERNEL [=n] | Type : boolean │ Prompt: Include in-kernel firmware blobs in kernel binary │ Defined at drivers/base/Kconfig:80 │ Depends on: FW_LOADER [=y] │ Location: │ -> Device Drivers │ -> Generic Driver Options │ -> Userspace firmware loading support (FW_LOADER [=y])
Re: [gentoo-user] AMD microcode updates - where are they?!
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, to check if I might have missed something relevant. So far, I've just searched the git repository for the package. I suppose I could have kept a copy of the manifest from the initial emerge (without savedconfig) but I didn't think of it at the time. Look under your /lib/firmware/ directory for the file you want to use, or the file dmesg complains is missing. For microcode there will be no complaining, but for other hardware there usually is something along the lines: "failed to load blah-blah.bin, file not found." If linux-firmware is emerged with the savedconfig use flag, then only the firmware not deleted from the config file is left. I did find a few extras based on the "failed to load..." messages after my initial overzealous trimming of that config file. My current concern is indeed with the microcode, about which no complaint. Looking at the link below shows me I am missing the files for my 17h family Ryzen CPU. It will be a bit before I can reboot to see if it does load them once I re-emerge linux-firmware to get them. I'll update again once I've done that. Jack
Re: [gentoo-user] Issues with amdgpu driver: Compositor hangs, sysfs not working
Thank you for your reply. Hello everybody, I installed an AMD Radeon RX 7900 XTX today, switching from Nvidia. But once I enable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y to have a tty once the driver is up, the following happens: 1) My Wayland compositor (Hyprland) takes very long to start. 2) reading from sysfs (e.g. running "cat /sys/class/drm/card0/device/gpu_busy_percent") does not work and causes a hang. Once I disable FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=n, I have no issues with the starting speed of the compositors at all and the mentioned command works. But this leads to a black tty. You'd normally need this enabled to get a fb display on the console, but I don't know if this would be provided by proprietary drivers instead for your card - see below. I made a mistake here, sorry. The issue causing setting is DRM_FBDEV_EMULATION=y, which on itself works with the open source driver, but causes issues as soon as I start Hyprland. It could be both. I don't think there's any Linux firmware released yet for this card - but I don't follow the latest & greatest so I could be wrong. You'd need the AMD amdgpu-pro on top of the amdgpu driver, to bring in the proprietary OpenGL, OpenCL, Vulkan and AMF components: https://wiki.gentoo.org/wiki/AMDGPU-PRO This is what's in portage today: ~ $ eix -l amdgpu-pro * dev-libs/amdgpu-pro-opencl Available versions: ~20.40.1147286 ^fmsd[ABI_X86="32 64"] ["|| ( abi_x86_32 abi_x86_64 )"] Homepage: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-40 Description: Proprietary OpenCL implementation for AMD GPUs * media-libs/amdgpu-pro-vulkan Available versions: ~21.50.2.1384496-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.10.4.1452060-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.20.5.1511376-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~22.40.6.1580631-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~23.10.3.1620044-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] ~23.20.0.1654522-r1 ^md [ABI_X86="32 64" VIDEO_CARDS="amdgpu"] ["video_cards_amdgpu"] Homepage:https://www.amd.com/en/support Description: AMD's closed source vulkan driver, from Radeon Software for Linux * media-video/amdgpu-pro-amf Available versions: ~1.4.24.1452059 ^md ~1.4.26.1511376 ^md ~1.4.29.1580631 ^md ~1.4.30.1620044 ^md ~1.4.31.1654522 (0/31)^md Homepage:https://www.amd.com/en/support Description: AMD's closed source Advanced Media Framework (AMF) driver Found 3 matches The firmare seems good, since it is loaded just fine, "dmesg | grep amdgpu | grep firmware" returns: [ 16.905914] Loading firmware: amdgpu/psp_13_0_0_sos.bin [ 16.905916] Loading firmware: amdgpu/psp_13_0_0_ta.bin [ 16.905917] Loading firmware: amdgpu/smu_13_0_0.bin [ 16.905917] Loading firmware: amdgpu/dcn_3_2_0_dmcub.bin [ 16.905918] Loading firmware: amdgpu/gc_11_0_0_pfp.bin [ 16.905919] Loading firmware: amdgpu/gc_11_0_0_me.bin [ 16.905919] Loading firmware: amdgpu/gc_11_0_0_rlc.bin [ 16.905920] Loading firmware: amdgpu/gc_11_0_0_mec.bin [ 16.905921] Loading firmware: amdgpu/gc_11_0_0_imu.bin [ 16.905922] Loading firmware: amdgpu/sdma_6_0_0.bin [ 16.905923] Loading firmware: amdgpu/vcn_4_0_0.bin [ 16.906095] Loading firmware: amdgpu/gc_11_0_0_mes_2.bin [ 16.906096] Loading firmware: amdgpu/gc_11_0_0_mes1.bin [ 16.906496] amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Also the mesa libraries work just fine, if I disable DRM_FBDEV_EMULATION=n, I just get a black tty, but Hyprland starts and I can play games with the expected performance.
Re: [gentoo-user] Where are the AMD microcode updates for spectre?
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://bugs.gentoo.org/656136 . Thank You, for the info. I noticed something odd about the microcode however ... > amd-ucode/microcode_amd_fam15h.bin 7876 -> 5356 bytes . The size dropped by 2Kb? So is the "fix" actually disabling fixes for other problems? . Reference Link : https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8 . Corbin
Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
On Wed, Dec 20, 2017 at 9:26 AM, Mick wrote: > On Wednesday, 20 December 2017 12:52:16 GMT Floyd Anderson wrote: >> On Wed, 20 Dec 2017 12:22:29 + >> >> Mick wrote: >> >Has something changed in 4.14.7-gentoo sources from its predecessors? >> > >> >I'm getting this on two systems: >> > >> >[snip ...] >> > >> > INSTALL sound/pci/hda/snd-hda-codec-hdmi.ko >> > INSTALL sound/pci/hda/snd-hda-codec.ko >> > INSTALL sound/pci/hda/snd-hda-intel.ko >> > DEPMOD 4.14.7-gentoo >> > >> >make: *** No rule to make target 'firmware_install'. Stop. >> >> Yes, there is a change to drop the target rule ‘firmware_install’ [1]. >> I’ve noticed also [2] but in the end it seems the rule is finally >> dropped: >> >> /usr/src/linux-4.12.12-gentoo/scripts/Makefile.fwinst... exists >> /usr/src/linux-4.14.4-gentoo/scripts/Makefile.fwinst ... no such file >> >> To check it’s there look for ‘Other generic targets’ in kernel dir: >> >> sudo make help >> >> or just grep: >> >> grep -q 'firmware_install' /usr/src/linux/Makefile >> >> >> References: >> - [1] >> - [2] > > You are quite right, there is no firmware_install in the 4.14.7 release. What > does this mean? How are we meant to install firmware now? I believe all firmware has been removed from the kernel sources. You should install sys-kernel/linux-firmware, or grab just the files you need from the git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[gentoo-user] QLogic QLA2xxx driver kernel 2.6.18+
Hi all, Has anyone found a solution to how to load the firmware dirvers on boot in 2.6.18+ kernels. I read something about you need to put the /lib/firmware files into initrd. But I dont know how or where to put it in. My setup is IBM Blade Ceneter with HS20 blades (Intel Xeon cpus) with Qlogic 2412 FC card. I boot from the san so i need the firmware into the kernel. ERROR: QLogic Fibre Channel HBA Driver GSI 19 sharing vector 0xC1 and IRQ 19 ACPI: PCI Interrupt :05:08.0[A] -> GSI 32 (level, low) -> IRQ 193 qla2xxx :05:08.0: Found an ISP2312, irq 193, iobase 0xc2006000 qla2xxx :05:08.0: Configuring PCI space... qla2xxx :05:08.0: Configure NVRAM parameters... qla2xxx :05:08.0: Verifying loaded RISC code... qla2xxx :05:08.0: Firmware image unavailable. qla2xxx :05:08.0: Firmware images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/. qla2xxx :05:08.0: Failed to initialize adapter GSI 20 sharing vector 0xC9 and IRQ 20 ACPI: PCI Interrupt :05:08.1[B] -> GSI 33 (level, low) -> IRQ 201 qla2xxx :05:08.1: Found an ISP2312, irq 201, iobase 0xc2006000 qla2xxx :05:08.1: Configuring PCI space... qla2xxx :05:08.1: Configure NVRAM parameters... qla2xxx :05:08.1: Verifying loaded RISC code... qla2xxx 0000:05:08.1: Firmware image unavailable. qla2xxx 0000:05:08.1: Firmware images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/. qla2xxx :05:08.1: Failed to initialize adapter Kveðja / Regards Ásgeir Halldórsson E.C. Software
Re: [gentoo-user] AMD microcode error?
On Sunday, 28 January 2024 17:39:56 GMT Michael wrote: > I'm not sure a microcode update has been released yet by AMD as a blob, > outside what they make available to MoBo OEMs within 'BIOS firmware' > updates. To find what's in the box use: > > dmesg | grep -i 'family:' > > Then check what CPU family and model microcodes the linux-firmware contains: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ > tree/amd-ucode/README No luck with those. > If you can't find your family and model in the above, then you could check > what firmware updates are available by the MoBo's OEM. These would include > microcode made directly available by AMD to the OEM. That's ASRock X570 Taichi. Their pages suggest that they only acknowledge Windows 10 & 11. I'll keep my eyes open for another glitch. Maybe the microcode isn't to blame at all, in which case I'd better not sleep on the job. Thanks for the pointers. -- Regards, Peter.
Re: [gentoo-user] nouveau: gr: failed to load firmware "gr/sw_nonctx"
On Sun, 13 Dec 2020 17:32:12 -0700, the...@sys-concept.com wrote:
> > It means the version you have installed is no longer in the tree. You
> > should update to the latest.
> >
>
> Something is wrong, I just --sync and reinstall linux-firmware but the
> output is still the same:
>
> eix linux-firmware
> [?] sys-kernel/linux-firmware
> Available versions: 20200316^bsd 20200421^bsd 20200519^bsd
> 20200619^bsd 20200721^bsd 20200817^bsd 20200918^bsd 20201022-r2^bstd
> ***l^bstd {initramfs +redistributable savedconfig
> unknown-license} Installed versions: 20201022-r3^
> 20201022-r3^bst(05:30:05 PM 12/13/2020)(redistributable -initramfs
> -savedconfig -unknown-license)
This shows that you have 20201022-r3 installed but eix says the latest
available is 20201022-r2 so you have a version it thinks is not in the
tree.
Did you run eix-update after syncing?
--
Neil Bothwick
Never ask a geek why, just nod your head and slowly back away
pgpptsPhmNcu6.pgp
Description: OpenPGP digital signature
[gentoo-user] Re: Eliminating unwanted linux-firmware blobs.
On 2024-06-28, Eli Schwartz wrote:
> On 6/28/24 6:31 PM, Peter Humphrey wrote:
>> On Friday, 28 June 2024 20:32:11 BST Tsukasa Mcp_Reznor wrote:
>>
>>> Remove the date.so it becomes
>>> /etc/portage/savedconfig/sys-kernel/linux-firmware then it applies to all
>>> of them and not the specified version.
>>>
>>> Hope that helps
>>
>> It certainly does. I wish I'd known that years ago: it would have saved me
>> an
>> awful lot of renaming.
>
> The elog message states:
>
> * Your configuration for sys-kernel/linux-firmware-20240610-r1 has been
> saved in
> * "/etc/portage/savedconfig/sys-kernel/linux-firmware-20240610-r1" for
> your editing pleasure.
> * You can edit these files by hand and remerge this package with
> * USE=savedconfig to customise the configuration.
> * You can rename this file/directory to one of the following for
> * its configuration to apply to multiple versions:
> * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
> * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
>
> I admit that this is a bit hard to analyze...
Just a bit. :)
Sure would be nice if it was mentioned on whe Wiki page. Mayber later
today...
--
Grant
Re: [gentoo-user] How to Transplant Firmware Blobs -- was: Issue with Wireless Interface
On Tue, 13 May 2014 20:00:55 -0500, Dale wrote: > > Hi all. I found out that I was missing the firmware, not the drivers. > > I have the firmware on a USB stick, so is it possible to transplant it > > in to Gentoo? > It may be in this package: > > sys-kernel/linux-firmware That's the best option, as portage will keep the firmware updated. If your device is not covered and you have the bare firmware file, copy it to /lib/firmware. -- Neil Bothwick Indecision is the key to flexibility. signature.asc Description: PGP signature
Re: [gentoo-user] r8169 unable to apply firmware patch
On Sat, Jul 30, 2011 at 7:05 PM, Grant wrote: >> I remembered that i also had started having a problem with my intel >> wireless card, and it looks like both the intel and realtek firmwares >> are now in linux-firmware so try emerging that. > > That fixed it. Thank you very much. I'm a little puzzled because I > don't get the "unable to apply firmware patch" messages on my desktop > which also uses the r8169 driver and doesn't have linux-firmware > installed. AFAIR the r8169 driver supports multiple chipsets, and they don't all need the firmware file. So perhaps your two systems are not using exactly the same chipset in the ethernet card... On my desktop, I would get that warning, but it would work perfectly fine anyway even without it being present. According to Google results, the general opinion is that r8169 sucks and seems like almost everybody has problems with it. :)
RE: [gentoo-user] QLogic QLA2xxx driver kernel 2.6.18+
Hi all, Should I ask another mailinglist about this problem? From: Ásgeir Halldórsson [mailto:[EMAIL PROTECTED] Sent: 7. febrúar 2007 10:30 To: gentoo-user@gentoo.org Subject: [gentoo-user] QLogic QLA2xxx driver kernel 2.6.18+ Hi all, Has anyone found a solution to how to load the firmware dirvers on boot in 2.6.18+ kernels. I read something about you need to put the /lib/firmware files into initrd. But I dont know how or where to put it in. My setup is IBM Blade Ceneter with HS20 blades (Intel Xeon cpus) with Qlogic 2412 FC card. I boot from the san so i need the firmware into the kernel. ERROR: QLogic Fibre Channel HBA Driver GSI 19 sharing vector 0xC1 and IRQ 19 ACPI: PCI Interrupt :05:08.0[A] -> GSI 32 (level, low) -> IRQ 193 qla2xxx :05:08.0: Found an ISP2312, irq 193, iobase 0xc2006000 qla2xxx :05:08.0: Configuring PCI space... qla2xxx :05:08.0: Configure NVRAM parameters... qla2xxx :05:08.0: Verifying loaded RISC code... qla2xxx :05:08.0: Firmware image unavailable. qla2xxx :05:08.0: Firmware images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/. qla2xxx :05:08.0: Failed to initialize adapter GSI 20 sharing vector 0xC9 and IRQ 20 ACPI: PCI Interrupt :05:08.1[B] -> GSI 33 (level, low) -> IRQ 201 qla2xxx :05:08.1: Found an ISP2312, irq 201, iobase 0xc2006000 qla2xxx :05:08.1: Configuring PCI space... qla2xxx :05:08.1: Configure NVRAM parameters... qla2xxx :05:08.1: Verifying loaded RISC code... qla2xxx 0000:05:08.1: Firmware image unavailable. qla2xxx 0000:05:08.1: Firmware images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/. qla2xxx :05:08.1: Failed to initialize adapter Kveðja / Regards Ásgeir Halldórsson E.C. Software
Re: [gentoo-user] Kernel build error
Dale schrieb: > Saphirus Sage wrote: > >> Dale wrote: >> >> >>> Hi, >>> >>> I'm trying to upgrade my kernel but I got this. >>> >>> r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # make all && make >>> modules_install >>> CHK include/linux/version.h >>> CHK include/linux/utsrelease.h >>> CALLscripts/checksyscalls.sh >>> CHK include/linux/compile.h >>> make[1]: *** No rule to make target `n/n', needed by >>> `firmware/n.gen.o'. Stop. >>> make: *** [firmware] Error 2 >>> r...@smoker /usr/src/linux-2.6.27-gentoo-r8 # >>> >>> I have always used that command but it doesn't usually end like this. I >>> think that is right. What is target 'n/n'? Am I missing something? >>> Kernel version is in the prompt up there too. >>> >>> Thanks. >>> >>> Dale >>> >>> :-) :-) >>> >>> >>> >>> >> What firmware drivers had you enabled when you configured the kernel? >> >> >> >> > > Well, I copied .config from my old kernel, ran oldconfig then menuconfig > to check on a couple things. Everything looked normal enough for me > system. I did say no to the new stuff tho. My old kernel works fine so > I am really only updating the kernel. > > I'm not sure what you mean by "firmware drivers"? I don't use modules > but it does have a couple that are default and can't get rid of. > > Dale > > :-) :-) > > Hi, if you don't want to have this driver atall there should be nothing in there. Best thing ist to run make menuconfig to search for the mentioned line. Sorry for my tiping but I am really sleepy :-) kh
Re: [gentoo-user] Re: AMD microcode updates - where are they?!
On Monday, 15 July 2019 22:18:12 BST Ian Zimmerman wrote:
> UH-OH, Self-followup:
>
> On 2019-07-14 21:30, Ian Zimmerman wrote:
> > I find it odd that there is apparently no central way to track which
> > firmwares are being loaded without a debugging kernel.
> >
> > The relevant messages in linux/drivers/base/firmware_loader/main.c are
> > all dev_dbg(), which as I understand does nothing on a non-debug kernel.
> > Even the message printed when the firmware file is missing is of that
> > type.
> >
> > I guess I could turn on the userspace helper, set it to some script that
> > just logs every request and fails, and then remove the whole
> > /lib/firmware tree, but that is a _really_ round-about way.
>
> Solved with a kernel patch:
>
> --- a/drivers/base/firmware_loader/main.c 2019-07-13 23:01:15.0
> -0700 +++ b/drivers/base/firmware_loader/main.c 2019-07-14
> 23:33:22.348028910 -0700 @@ -336,7 +336,7 @@
>path);
> continue;
> }
> - dev_dbg(device, "direct-loading %s\n", fw_priv-
>fw_name);
> + pr_notice("direct-loading firmware %s\n", fw_priv-
>fw_name);
> fw_priv->size = size;
> fw_state_done(fw_priv);
> break;
Thanks Ian, nothing different with the patch implemented. I am becoming
convinced there is no applicable microcode patch for my fam + model of AMD
CPUs.
$ dmesg | egrep -i "firmware|microcode"
[0.00] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions
Support.
[0.343586] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.351361] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus
00-3f] only partially covers this bridge
[0.627638] [drm] Loading ARUBA Microcode
[0.629254] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[5.753421] [drm] Loading hainan Microcode
[6.643785] microcode: CPU0: patch_level=0x06001119
[6.647663] microcode: CPU1: patch_level=0x06001119
[6.649170] microcode: CPU2: patch_level=0x06001119
[6.650136] microcode: CPU3: patch_level=0x06001119
[6.651110] microcode: Microcode Update Driver: v2.2.
[8.125143] psmouse serio1: elantech: assuming hardware version 3 (with
firmware version 0x450f03)
[9.938954] psmouse serio1: elantech: assuming hardware version 3 (with
firmware version 0x450f03)
[ 30.738249] firmware_class: direct-loading firmware regulatory.db
[ 30.738915] firmware_class: direct-loading firmware regulatory.db.p7s
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Udev 200 : dhcpcd problem + solution
130401 Mick wrote: > On Monday 01 Apr 2013 02:54:08 Philip Webb wrote: >> I've spent a lot of today trying to fix a glitch in starting 'dhcpcd' >> after upgrading to udev-200 ; I outlined it in a msg to gentoo-dev . -- details snipped -- > Thanks for sharing this Philip. > I was surprised to see that firmware for NICs > are meant to be added in this kernel config option. > I thought that this config option was only for the video card firmware. > > # cat /usr/src/linux/.config | grep EXTRA_FIRMWARE > CONFIG_EXTRA_FIRMWARE="radeon/R600_rlc.bin radeon/R700_rlc.bin" > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" > > In my /lib/firmware I have: > > # ls -la /lib/firmware/ > total 1448 > drwxr-xr-x 5 root root4096 Sep 14 2012 . > drwxr-xr-x 14 root root 12288 Mar 31 09:26 .. > drwxr-x--- 2 root root4096 Feb 4 2012 b43 > drwxr-xr-x 2 root root4096 Sep 14 2012 intel-ucode > -rw-r--r-- 1 root root 1451687 Sep 14 2012 microcode.dat > drwxr-xr-x 2 root root4096 Dec 31 09:58 radeon > > and from dmesg I can see that all of these get loaded > *without* being defined in the CONFIG_EXTRA_FIRMWARE= ... > On this box in any case I do not have sys-kernel/linux-firmware installed, > but have installed x11-drivers/radeon-ucode for the video card > and net-wireless/b43-fwcutter for the wireless NIC. > Are you saying that the correct way to go about this > is to uninstall these packages > and instead define the firmware in the kernel in CONFIG_EXTRA_FIRMWARE= ? > PS. I'm currently running kernel-3.7.10-gentoo. No, if your way works, keep doing it. I installed 'linux-firmware' long ago, but may not have used it since. I was faced with the peculiar problem I described, ie after updating to udev-200 & following the news-item advice the 1st attempt at 'dhcpcd' stalled, but a 2nd attempt always worked. Not wanting to face this delay every time I reboot, I investigated with the results described. 'dhcpcd' is now noticeably quicker than with <= udev-197 & the new kernel naming system seems a small general improvement, so my advice wb to update to udev-200 & then solve any other problems. I assume the underlying problem for me was that the kernel took time trying to find the firmware & meanwhile the Dhcpcd process went to sleep or froze. Now that the firmware is compiled into the kernel, there's no delay. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] How to flash an LSI SAS controller from IR to IT mode on linux with sas2flsh
Surprising that you can do that on a VM, clearly they don't provide much security if you can do such powerful things as flashing firmware, pretty easy to write a VM virus that flashes all the flash memory to random, 1, or 0 values that would totally brick a server and add in cards as well as hard drives. it may be hard to reverse engineer most firmware, but that doesn't mean it's hard to corrupt. In any case, sorry for your' problems. thumb drives of 32G and less are really cheap now that the huge ones are available (got a 16GB for <$7). I'm ridiculously poor by american standards (still fighting SS, thank god i got public housing!) and i bought a couple in the last 6 months. manufacturers are starting to make firmware upgrades for linux, and i believe there is a program that can be used to install dos firmware upgrades from linux. I Actually have 2 machines with both windows and linux firmware updates available, but they are servers (13 yr old, not surprisingly they were free!). i've become interested in servers as they depreciate quickly and tend to be built like tanks (though they are equally heavy). mad.scientist.at.large (a good madscientist) -- God bless the rich, the greedy and the corrupt politicians they have put into office. God bless them for helping me do the right thing by giving the rich my little pile of cash. After all, the rich know what to do with money. Regarding uefi, i never believed in it, long before an asian asus manufacturer was kind enough to leave their ftp server open, and someone found the master key there and let the world know. besides which, it's pretty hard to produce an encryption algorithm that will still be hard to break in 5-10 years due to ever increasing processing power, especially if people find some flaws in the algorithm or implementation. I suppose that since it's a card you want to flash you might be able to do it on a friends machine, possibly. Good luck. 20. Mar 2018 13:02 by taii...@gmx.com <mailto:taii...@gmx.com>: > On 03/19/2018 08:02 PM, > mad.scientist.at.la...@tutanota.com > <mailto:mad.scientist.at.la...@tutanota.com>> wrote: >> >> A virtual machine is useful largely because it isolates the VM from >> the real hardware, therefore it's not likely you can update firmware from a >> VM (you really shouldn't be able to).>> > Actually you can update firmware from a VM, I have done it manytimes > on many different PCI-e cards and I already updated the IRmode firmware > to the latest version in a linux VM (but you need DOSto go IR>IT) > > It is part of the reason as to why SR-IOV was created besides the > performance benefits you also get security benefits with restricted > registers and the inability to flash a malicious firmware from aguest if > you attach a VF to the VM instead of the PF. > > I don't have any UEFI machines as I hate UEFI (all my machines run > coreboot with the grub payload) > >> >> The reason they still want us to upgrade with dos is it's a lowest >> common denominator, i.e. every one has it or can get it (freedos). it also >> helps that it's a minimal enviroment.In any case, I suggest you run a REAL >> freedos on a Real machine, so that you can update real not virtual firmware. >> i.e. no Virtual Machine.>> > The issue is not being able to use linux as well and having a bare > metal freedos won't help my disk driver issue there still won't be away > to load the files. >
Re: [gentoo-user] 'firmware_install' won't on 4.14.7-gentoo
On Wednesday, 20 December 2017 15:51:03 GMT Mick wrote: > On Wednesday, 20 December 2017 15:28:03 GMT Peter Humphrey wrote: > > On Wednesday, 20 December 2017 12:22:29 GMT Mick wrote: > > > Has something changed in 4.14.7-gentoo sources from its predecessors? > > [snip ...] > > > What firmware are you trying to install? This box needs firmware for the > > 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. I didn't even know about a firmware_install make target. > > Thanks Peter, > > I am also declaring relevant firmware in the kernel for CPU microcode and > GPU, but they do not get loaded when I build kernel 4.14.7: > > $ grep FIRMWARE /usr/src/linux/.config > CONFIG_PREVENT_FIRMWARE_BUILD=y > CONFIG_FIRMWARE_IN_KERNEL=y > CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1e-05 radeon/R700_rlc.bin radeon/ > RV730_smc.bin radeon/RV710_uvd.bin" > CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" > # CONFIG_CYPRESS_FIRMWARE is not set > # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set > CONFIG_FIRMWARE_EDID=y > CONFIG_FIRMWARE_MEMMAP=y > # CONFIG_GOOGLE_FIRMWARE is not set > # CONFIG_TEST_FIRMWARE is not set Hm. Mine is: # 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_mec2.bin amdgpu/polaris10_mec.bin amdgpu/ polaris10_pfp.bin amdgpu/polaris10_rlc.bin amdgpu/polaris10_sdma1.bin amdgpu/polaris10_sdma.bin amdgpu/polaris10_smc.bin amdgpu/ polaris10_smc_sk.bin amdgpu/polaris10_uvd.bin amdgpu/polaris10_vce.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set CONFIG_FIRMWARE_EDID=y CONFIG_FIRMWARE_MEMMAP=y # CONFIG_GOOGLE_FIRMWARE is not set # CONFIG_TEST_FIRMWARE is not set I don't see that cypress entry (why not? Are you using gentoo-sources?), but otherwise it looks the same. If I didn't have all that polaris stuff I wouldn't have an X display; that's how I started off, and I had to go looking for the right set of amdgpu modules to load. > So I can't load a desktop because xserver will not launch. I also recall > having additional firmware for WiFi/BT cards on this laptop. > > The same problem exists on other systems, some running AMD. We must differ in some other way, I suppose in the way we build our kernels. This is my kernel build script on this UEFI box: # cat /usr/local/bin/kmake #!/bin/bash mount /boot cd /usr/src/linux time (make -j12 && make modules_install && make install &&\ /bin/ls -lh --color=auto /boot && echo &&\ cp -v ./arch/x86/boot/bzImage /boot/EFI/Boot/bootX64.efi ) &&\ echo; echo "Rebuilding modules" && echo &&\ emerge --jobs --load-average=48 @module-rebuild @x11-module-rebuild && echo &&\ echo "Remounting /sys/firmware/efi/efivars read-write" &&\ mount -oremount,rw /sys/firmware/efi/efivars && echo &&\ echo "Don't forget to bootctl-install the new kernel!" && echo HTH, but I wonder... -- Regards, Peter.
Re: [gentoo-user] where is linux-firmware.log?
I have tried a couple different things so linux-firmware and other packages can find the boot location and none of them have worked. I'm going with openrc and efi and gpt. originally I made an efi partition and mounted it mount /dev/sda1 /mnt/gentoo/efi once the efi directory had been created. later I made /mnt/boot/efi and mount /dev/sda1 /mnt/boot/efi I even named /dev/sda1 /boot in parted on existing system. Still linux-firmware continues putting everything in /mnt/gentoo/boot. -- Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Sun, 26 May 2024, Jude DaShiell wrote: > I'm getting a pair of errors when I do emerge linux-firmware: > undefined license group > emerge Assuming no boot partition > > >
Re: [gentoo-user] AMD microcode error?
On Monday, 29 January 2024 16:18:22 GMT Peter Humphrey wrote: > On Sunday, 28 January 2024 17:39:56 GMT Michael wrote: > > I'm not sure a microcode update has been released yet by AMD as a blob, > > outside what they make available to MoBo OEMs within 'BIOS firmware' > > updates. To find what's in the box use: > > > > dmesg | grep -i 'family:' > > > > Then check what CPU family and model microcodes the linux-firmware > > contains: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gi > > t/ tree/amd-ucode/README > > No luck with those. OK, this means there is no microcode to load via the linux-firmware releases (yet). > > If you can't find your family and model in the above, then you could check > > what firmware updates are available by the MoBo's OEM. These would > > include > > microcode made directly available by AMD to the OEM. > > That's ASRock X570 Taichi. Their pages suggest that they only acknowledge > Windows 10 & 11. Check the BIOS version in dmesg and compare it with the with the ASRock's AMD chipset image on the asrock.com website. If the versions/dates are the same you have nothing more to do. If the version on the website is more recent then you may want to flash the MoBo with it. Download the zip archive on offer and unzip it, then store the new image on a USB stick which has been formatted with FAT32. Some OEMs require you rename the firmware image file, it will say so on the website, or in a README within the zip archive. Reboot and press [F2] during POST to get into the BIOS setup menu, then go to the Tools tab to flash it from the USB. You may have to re-apply in the BIOS menu any changes you had previously made after the PC reboots, because restoring the settings from a backup file doesn't always work. > I'll keep my eyes open for another glitch. Maybe the microcode isn't to > blame at all, in which case I'd better not sleep on the job. Well, updating the BIOS firmware with the latest version often contains patches for bugs and microcode patches for CPU vulnerabilities. However, this does not mean it will address the MCE errors you were experiencing. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Loading a Firmware Module By hand?
On 12/18/17, Mick wrote: > On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote: >> Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version >> 9 as well, but that didn't help matters, either. Nor did >> compiling the firmware into the kernel; either 4.14 is too old, or it >> is too new. > > I'd think they are both too new? > >> I tried copying the firmware my live iso was using, but >> that didn't help either. > > If the live iso works, start with using the same kernel release and linux- > firmware version, to see if this works as expected on your installation. > Then > update kernel sources and firmware to the latest stable and see if this > works > too. > > From there on you can move into ~arch to find the version at which things > break. > -- > Regards, > Mick Okay, here are the dmesg messages: https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/ The present kernel configuration, as of yesterday evening: https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/ Make and model of the offending card: Qualcomm 6174 revision 20. Not exactly what the -2 error means, but I will try as Mick suggested and work my way forwards to see what I can get working.
Re: [gentoo-user] Re: Radeon HD 4350 benchmark
On 21 February 2011 04:27, James wrote: > James tampabay.rr.com> writes: > > >> In the kernel, under the Generic section, I first tried: >> CONFIG_FW_LOADER=y >> CONFIG_FIRMWARE_IN_KERNEL=y >> CONFIG_EXTRA_FIRMWARE="radeon" >> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" This should have been: # cat /usr/src/linux/.config | grep -i FIRMWARE CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="radeon/R700_rlc.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/" CONFIG_FIRMWARE_EDID=y # Firmware Drivers CONFIG_FIRMWARE_MEMMAP=y Also, check that you have the R700_rlc.bin in place: ls -la /lib/firmware/radeon/R700_rlc.bin -rw-r--r-- 1 root root 4096 Feb 15 19:40 /lib/firmware/radeon/R700_rlc.bin and emerge x11-drivers/radeon-ucode if it's not already there. -- Regards, Mick
Re: [gentoo-user] Firmware exists but fails to load
On Mon, Aug 15, 2011 at 4:13 AM, Adam Carter wrote: > # dmesg | grep firm > [ 70.453673] r8169 :02:00.0: eth0: unable to load firmware patch > rtl_nic/rtl8168d-2.fw (-2) > # ls -l /lib/firmware/rtl_nic/rtl8168d-2.fw > -rw-r--r-- 1 root root 1324 Aug 12 13:09 /lib/firmware/rtl_nic/rtl8168d-2.fw > > Any ideas why this fails? Filesystem is mounted, file is readable... 1) build the driver as a module (firmware loading from disk does not work otherwise) 2) emerge linux-firmware, if you haven't already. 3) reboot and good luck :)
Re: [gentoo-user] How to tell what the current AMD microcode level is?
On 2019-12-07 16:22, Adam Carter wrote: I dont know, so i just use the ~amd64 linux-firmware version. For my 3900X its currently; microcode: CPU0: patch_level=0x08701013 The last update came through in October; firmware-md5s-2019-09-09.txt:fef89be989f6a160b340027a24cd0a16 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin firmware-md5s-2019-09-25.txt:fef89be989f6a160b340027a24cd0a16 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin firmware-md5s-2019-10-23.txt:a30e5f81d37ed38faf039b75bc376197 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin firmware-md5s-2019-11-12.txt:a30e5f81d37ed38faf039b75bc376197 /lib/firmware/amd-ucode/microcode_amd_fam17h.bin Drat, mine is 0x08701011. That means for some reason it's not doing an early microcode update in the kernel. I'll have to figure out why it's not applying. I followed the same steps for my Intel-based laptop and it works... not sure why it isn't loading. It could be that the 3950x is not defined in the firmware and not applying but I have no way to confirm that. Dan
[gentoo-user] Re: new mobo : Eth0 recovered
On 21/04/12 17:25, Philip Webb wrote: 120421 Dale wrote: Philip Webb wrote: You actually have to remove the offensive file from the dir, not simply rename it to 'xx70xx...' ! That's the same way files in /etc/portage/ works too. I do wish we could put a # on the front to make it ignore files. We can dream I guess. Yes& why did it start doing this only with the new mobo -- was it provoked by seeing an unknown driver ? And whyever did it want to rename the device to 'eth1' ?? So that eth0 still works. It can't know that what you have is a new mobo rather than you having added an additional NIC. Also, make sure to emerge sys-kernel/linux-firmware. Without it, RTL8111/8168B NICs will produce random connectivity hang-ups after a few hours; they need firmware that was previously part of the kernel itself but has now been split to sys-kernel/linux-firmware. Do a: dmesg | grep -i firmware and check for firmware loading errors.
Re: [gentoo-user] r8169 unable to apply firmware patch
>> >> so the question becomes why does eth0 >> >> appear under ifconfig on my laptop with net.eth0 stopped and the cable >> >> unplugged? >> >> >> >> I thought it could be wicd on my laptop but I shut down the daemon >> >> with no change. >> > >> > Try disabling the daemon from starting at boot 'rc-update delete wicd' >> > and reboot, then see if the interface is up. >> >> You nailed it. eth0 was being brought up on my laptop by wicd. >> Thanks a lot. Both systems have functioning NIC's now. > > Glad you got this sorted. > > Is there a conclusion if we should be planning to move away from x11- > drivers/radeon-ucode, net-wireless/b43-fwcutter, et al and use sys- > kernel/linux-firmware instead? > -- > Regards, > Mick I'm not the right guy to make the call but I think the fact that the r8169 firmware exists only in linux-firmware (as far as Portage packages) says something. - Grant
RE: [gentoo-user] How to Transplant Firmware Blobs -- was: Issue with Wireless Interface
-Original Message- From: Neil Bothwick [mailto:n...@digimed.co.uk] Sent: Wednesday, May 14, 2014 4:45 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How to Transplant Firmware Blobs -- was: Issue with Wireless Interface On Tue, 13 May 2014 20:00:55 -0500, Dale wrote: > > Hi all. I found out that I was missing the firmware, not the drivers. > > I have the firmware on a USB stick, so is it possible to transplant > > it in to Gentoo? > It may be in this package: > > sys-kernel/linux-firmware That's the best option, as portage will keep the firmware updated. If your device is not covered and you have the bare firmware file, copy it to /lib/firmware. -- Neil Bothwick Indecision is the key to flexibility. That's what I'll have to do, as my school conviently blocked the Portage tree.
Re: [gentoo-user] TUSB3410 on 3.0.6 kernel
solved, unmark: [ ] Include in-kernel firmware blobs in kernel binary then, type: make && make firmware_install && make modules_install && make install Érico V. Porto On Sun, Nov 6, 2011 at 8:28 PM, Érico Porto wrote: > Ok I will try it. > > I used: > > make && make modules_install && make install > > Doesn't the modules get made in the make part? > > Érico V. Porto > > > > On Sun, Nov 6, 2011 at 8:16 PM, Aljosha Papsch > wrote: > >> 2011/11/6 Érico Porto : >> > Hello, >> > I would like to ask about the kernel 3.0.6. I can't load >> > the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it >> > makes fine, but when I type make modules_install, I get an error: >> > make[1]: *** No rule to make target `/lib/firmware/./', needed by >> > `/lib/firmware/ti_3410.fw'. Stop. >> > make: *** [_modinst_post] Error 2 >> > Has anyone tried it in the 3.0.6 kernel? My uname -a output is: >> > Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686 >> > Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux >> > My kernel was loaded using emerge. >> > Regards >> > Érico V. Porto >> > >> >> I solved this by not building firmware into kernel. It's somewhere in >> Linux config "General Options". >> >> >
RE: [gentoo-user] (Solved) anyone tried amdgpu (kernel module)
From: mcp_rez...@hotmail.com
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] anyone tried amdgpu (kernel module)
Date: Sat, 19 Dec 2015 11:17:40 -0500
From: alexander.kaps...@gmail.com
Date: Sat, 19 Dec 2015 18:13:03 +0200
Subject: Re: [gentoo-user] anyone tried amdgpu (kernel module)
To: gentoo-user@lists.gentoo.org
On Sat, Dec 19, 2015 at 5:43 PM, Tsukasa Mcp_Reznor
wrote:
From: alexander.kaps...@gmail.com
Date: Sat, 19 Dec 2015 09:35:28 +0200
Subject: Re: [gentoo-user] anyone tried amdgpu (kernel module)
To: gentoo-user@lists.gentoo.org
On Fri, Dec 18, 2015 at 11:07 PM, Tsukasa Mcp_Reznor
wrote:
I have a Bonaire gpu, which has legacy support using the amdgpu kernel module.
I currently use the Radeon dri module with radeonsi mesa drivers and am quite
happy. But gentoo being gentoo I thought I'd give the amdgpu a go for the fun
of it.
Tried a few variations and keep coming up with a black screen on boot and it's
hard locked. I'm using the same Firmware includes that the radeon driver
requires, and from reading it looks like that's fine with amdgpu, so I'm not
sure what else could be the issue.
Has anyone here tried and had success with it? I've tried Kernels 4.2 4.2.4
4.3 and 4.3.2. So I believe I'm missing something simple and it's not a kernel
bug.
Did you consult the wiki article shown below when configuring your system to
use admgpu?
https://wiki.gentoo.org/wiki/Amdgpu
Yes I have. The CIK parts kernel option is enabled. the only thing I find a
bit odd, is in the firmware 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 included in your kernel config file?
Device Drivers --->
Generic Driver Options --->
-*- Userspace firmware loading support
[*] Include in-kernel firmware blobs in kernel binary
(amdgpu/.bin radeon/.bin)
(/lib/firmware) Firmware blobs root directory
Yes I have the firmware includes, I'll try the amdgpu-ucode and report back.
-
Mission successful! Thanks everyone, it appears the missing sdma1.bin from
linux-firmware is contained in amdgpu-ucode and after switching everything is
running fine.
Re: [gentoo-user] TUSB3410 on 3.0.6 kernel
2011/11/6 Érico Porto : > Hello, > I would like to ask about the kernel 3.0.6. I can't load > the ti_usb_3410_5052.ko. I mean, when I select it in the kernel menu, it > makes fine, but when I type make modules_install, I get an error: > make[1]: *** No rule to make target `/lib/firmware/./', needed by > `/lib/firmware/ti_3410.fw'. Stop. > make: *** [_modinst_post] Error 2 > Has anyone tried it in the 3.0.6 kernel? My uname -a output is: > Linux localhost 3.0.6-gentoo #13 SMP Wed Nov 2 21:05:47 BRST 2011 i686 > Intel(R) Celeron(R) M processor 900MHz GenuineIntel GNU/Linux > My kernel was loaded using emerge. > Regards > Érico V. Porto > I solved this by not building firmware into kernel. It's somewhere in Linux config "General Options".
