Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
linux-firmware[savedconfig]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 3447

PostPosted: Wed Apr 29, 2020 8:17 am    Post subject: linux-firmware[savedconfig] Reply with quote

The latest linux-firmware update this morning has removed my manually edited config file from /etc/portage/savedconfig/sys-kernel/ and replaced with a fresh linux-firmware-20200421.

Too bad. I had to do it again. So the question is "How can a savedconfig be saved?"

It turns out that savedconfig needs /etc/portage/savedconfig/sys-kernel/linux-firmware without version number.
However USE=savedconfig emerge sys-kernel/linux-firmware installes that file with trailing version number, linux-firmware-20200421.

Bug or feature? (I added a note to the iwlwifi wiki article.)
Back to top
View user's profile Send private message
CaptainBlood
Veteran
Veteran


Joined: 24 Jan 2010
Posts: 1679

PostPosted: Wed Apr 29, 2020 9:22 am    Post subject: Reply with quote

Same deletion here, i.e. /etc/portage/savedconfig/sys-kernel/linux-firmware-[previous-timestamp], with USE=-savedconfig
Only 2 firmware files required here, not too hard to restore.
AFAIR, /etc/portage/savedconfig/sys-kernel/linux-firmware would not be overwritten or removed at install, and prioritized over timestamped version, with USE=savedconfig.
So prior to upgrade, previous /etc/portage/savedconfig/sys-kernel/linux-firmware-[previous-timestamp] should be moved to /etc/portage/savedconfig/sys-kernel/linux-firmware, untested.
Additionnaly a backup copy to /etc/portage/savedconfig/sys-kernel seems not too dirty, as a location that is.
Thks 4 ur attention, interest & support.
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 3447

PostPosted: Wed Apr 29, 2020 9:35 am    Post subject: Reply with quote

IMHO on a new installation and when the savedconfig USE flag is enabled linux-firmware should install /etc/portage/savedconfig/sys-kernel/linux-firmware without trailing version number.
Users should not need to remove the trailing ${PV} manually when they want savedconfig. Am I wrong?
Back to top
View user's profile Send private message
sdauth
Apprentice
Apprentice


Joined: 19 Sep 2018
Posts: 174
Location: Ásgarðr

PostPosted: Wed Apr 29, 2020 10:21 am    Post subject: Reply with quote

charles17 wrote:
IMHO on a new installation and when the savedconfig USE flag is enabled linux-firmware should install /etc/portage/savedconfig/sys-kernel/linux-firmware without trailing version number.
Users should not need to remove the trailing ${PV} manually when they want savedconfig. Am I wrong?


Seems correct to me as well. As I recently switched to a system requiring some firmware, I was surprised to see linux-firmware emerging the whole stuff. (I also use savedconfig to avoid useless firmwares)
Renaming it to linux-firmware fixes it indeed, so thanks for that charles17. It would makes sense to make it the default behaviour if savedconfig is used.
Back to top
View user's profile Send private message
CaptainBlood
Veteran
Veteran


Joined: 24 Jan 2010
Posts: 1679

PostPosted: Wed Apr 29, 2020 10:27 am    Post subject: Reply with quote

With USE=savedconfig, install is expected to take into account the highest prioritized file from etc/portage/savedconfig/sys-kernel/linux-firmware.
In such a case, I don't expect /etc/portage/savedconfig/sys-kernel/linux-firmware to be updated, untested.

On the other hand, a new ebuild may have some former firmware removed, and some new added, which should be reported somewhete, for troubleshooting purposes.

So I'd rather say an ugrade with USE=savedconfig should install its /etc/portage/savedconfig/sys-kernel/linux-firmware-[timestamp] if it doesn't already exist, and take into account the highest prioritized existing /etc/portage/savedconfig/sys-kernel/linux-firmware* for the install itself.

Having faced ths issue a couple of times already, this may be worthing a little testing, assuming forthcoming ebuild beahvior to be stable in this respect:

Tested with only /etc/portage/savedconfig/sys-kernel/linux-firmware installed and USE=-savedconfig:
/etc/portage/savedconfig/sys-kernel/linux-firmware has been deleted and replaced by /etc/portage/savedconfig/sys-kernel/linux-firmware-[timestamp].

which is bad IMHO.

/etc/portage/savedconfig/sys-kernel/linux-firmware should have been keep instead, for a further use with USE=savedconfig once its content has been manually revalidated against the timestamped version.

Would USE=savedconfig be used when upgrading, I would have expected /etc/portage/savedconfig/sys-kernel/linux-firmware to be untouched & taken into account, while replacing former timstamped version with the new one.

Tested with USE=savedconfig and both /etc/portage/savedconfig/sys-kernel/linux-firmware & /etc/portage/savedconfig/sys-kernel/linux-firmware-[new-timestamp] installed:
/etc/portage/savedconfig/sys-kernel/linux-firmware-[new-timestamp] is the one taken into account. Too bad.:cry:

Tested with USE=-savedconfig and only edited /etc/portage/savedconfig/sys-kernel/linux-firmware-[new-timestamp] installed:
/etc/portage/savedconfig/sys-kernel/linux-firmware-[new-timestamp] is overwritten.

The wiki currently doesn"t mention a priority logic, so I must got confused with another subject.
Sorry for the generated noise.

Thks 4 ur attention, interest & support.


Last edited by CaptainBlood on Wed Apr 29, 2020 11:05 am; edited 2 times in total
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 3447

PostPosted: Wed Apr 29, 2020 11:17 am    Post subject: Reply with quote

sdauth wrote:
It would makes sense to make it the default behaviour if savedconfig is used.
bug 720004
Back to top
View user's profile Send private message
kajzer
l33t
l33t


Joined: 27 Nov 2014
Posts: 782

PostPosted: Wed Apr 29, 2020 11:33 pm    Post subject: Reply with quote

I gave up on savedconfig for linux-firmware long time ago, it was always borked for me.
I mean it works fine but after some time there are problems and it goes like that in circles...
I just install everything, seems easier
Back to top
View user's profile Send private message
sigra
Tux's lil' helper
Tux's lil' helper


Joined: 03 Feb 2006
Posts: 75

PostPosted: Sat Jun 27, 2020 1:26 pm    Post subject: Reply with quote

CaptainBlood wrote:
Only 2 firmware files required here, not too hard to restore.

is it allowed to use * as in "brcm/*"? Or is it possible to just have one or a few of the following lines? (lspci says "Network controller: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)")
Code:
brcm/brcmfmac43455-sdio.MINIX-NEO Z83-4.txt
brcm/brcmfmac4350c2-pcie.bin
brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
brcm/brcmfmac43430-sdio.MUR1DX.txt
brcm/brcmfmac4373-sdio.bin
brcm/brcmfmac43430-sdio.bin
brcm/BCM-0bb4-0306.hcd
brcm/brcmfmac43430a0-sdio.bin
brcm/brcmfmac43241b0-sdio.bin
brcm/brcmfmac4366c-pcie.bin
brcm/brcmfmac43569.bin
brcm/brcmfmac43430a0-sdio.ONDA-V80 PLUS.txt
brcm/bcm43xx-0.fw
brcm/brcmfmac4334-sdio.bin
brcm/brcmfmac43455-sdio.bin
brcm/brcmfmac43340-sdio.bin
brcm/brcmfmac43143-sdio.bin
brcm/brcmfmac43602-pcie.bin
brcm/brcmfmac43362-sdio.cubietech,cubietruck.txt
brcm/brcmfmac43241b4-sdio.bin
brcm/brcmfmac43430a0-sdio.jumper-ezpad-mini3.txt
brcm/brcmfmac4354-sdio.bin
brcm/brcmfmac43570-pcie.bin
brcm/brcmfmac43236b.bin
brcm/bcm4329-fullmac-4.bin
brcm/brcmfmac43242a.bin
brcm/brcmfmac4330-sdio.bin
brcm/brcmfmac4356-pcie.gpd-win-pocket.txt
brcm/brcmfmac4356-sdio.bin
brcm/brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt
brcm/brcmfmac43340-sdio.meegopad-t08.txt
brcm/brcmfmac4330-sdio.Prowise-PT301.txt
brcm/brcmfmac43340-sdio.pov-tab-p1006w-data.txt
brcm/brcmfmac4373.bin
brcm/brcmfmac4329-sdio.bin
brcm/brcmfmac4339-sdio.bin
brcm/bcm43xx_hdr-0.fw
brcm/brcmfmac4366b-pcie.bin
brcm/brcmfmac4358-pcie.bin
brcm/brcmfmac4356-pcie.bin
brcm/brcmfmac43430-sdio.AP6212.txt
brcm/brcmfmac4335-sdio.bin
brcm/brcmfmac43602-pcie.ap.bin
brcm/brcmfmac4371-pcie.bin
brcm/brcmfmac43241b5-sdio.bin
brcm/brcmfmac4350-pcie.bin
brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
brcm/brcmfmac43143.bin
brcm/brcmfmac43362-sdio.bin
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2789
Location: Canada

PostPosted: Sat Jun 27, 2020 4:39 pm    Post subject: Reply with quote

With a slight hijacking of the thread. How to find one whether any firmware is used ? I have an oldish desktop (no wifi, no recent kernel firmware), the only suspicious thigs is nvidia.
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 3447

PostPosted: Sat Jun 27, 2020 6:00 pm    Post subject: Reply with quote

Code:
dmesg | grep firmware
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2789
Location: Canada

PostPosted: Sat Jun 27, 2020 11:56 pm    Post subject: Reply with quote

charles17 wrote:
Code:
dmesg | grep firmware


Thanks, I tried that and having zero result did not know if this is a definitive answer :)
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 3447

PostPosted: Sun Jun 28, 2020 4:42 am    Post subject: Reply with quote

Typical candidates are wifi drivers
grep firmware /var/log/dmesg:
[    0.205785] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    3.911566] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
modinfo -F firmware iwlwifi:
iwlwifi-100-5.ucode
iwlwifi-1000-5.ucode
iwlwifi-135-6.ucode
iwlwifi-105-6.ucode
iwlwifi-2030-6.ucode
iwlwifi-2000-6.ucode
iwlwifi-5150-2.ucode
iwlwifi-5000-5.ucode
iwlwifi-6000g2b-6.ucode
iwlwifi-6000g2a-6.ucode
iwlwifi-6050-5.ucode
iwlwifi-6000-6.ucode
tree /lib/firmware:
/lib/firmware/
├── intel-ucode
│   ├── 06-3a-00
│   ├── 06-3a-02
│   ├── 06-3a-04
│   ├── 06-3a-05
│   ├── 06-3a-06
│   ├── 06-3a-08
│   └── 06-3a-09
├── iwlwifi-6000g2a-6.ucode
├── regulatory.db
└── regulatory.db.p7s
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum