void-linux
linux-firmware: update to 20220913
Testing the changes
- I tested the changes in this PR: briefly
Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
Am going to reboot into this soon.
MIght be worth removing linux-firmware-dvb from the repositories.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I've successful tested this PR on 3 different systems.
@ericonr I've created a PR https://github.com/void-linux/void-packages/pull/38683 to get rid of the conflicts between the two packages. Since linux-firmware-dvb has firmware remaining that is not yet in linux-firmware. -> (linux-firmware-dvb: remove conflicts with official linux-firmware)
Hey @absrd,
linux-firmware is now on version 20220815. Could you update the PR?
Hey @classabbyamp,
it seems like @ericonr is currently not available.
I use this firmware version successful on three different physical machines.
I've also create PR https://github.com/void-linux/void-packages/pull/38683 to make sure the conflicts are fixed.
Hey @ericonr,
do we miss something here or can we go forward with merging PR #38683 to remove the conflicts and then merge this PR also?
@absrd and myself are still waiting for further information regarding this PR.
If something does still need work, let @absrd or me know. Since we're still on linux-firmware 20220411.
PR #38683 is created to fix the conflicts with linux-firmware-dvb.
Yesterday was the release of 20221012. Which has several updates and new firmware.
I was also wondering why we're stuck on old firmware. I'm currently running the new firmware you graciously updated and all is well. 3 systems here too.
Rebased on to latest master and updated to 20221109
Hey @absrd, could you force push again please?
Hm wonder what's up with CI, #38683 should've fixed those linux-firmware and linux-firmware-dvb conflicts, maybe another rebase/force-push would fix it?
maybe another rebase/force-push would fix it?
no, the new version of linux-firmware-dvb just hasn't been indexed by xlocate yet.
e.g.:
$ xlocate -S
$ xlocate as102 | grep firmware
linux-firmware-20220411_1 /usr/lib/firmware/as102_data1_st.hex
linux-firmware-20220411_1 /usr/lib/firmware/as102_data2_st.hex
linux-firmware-dvb-20170329_4 /usr/lib/firmware/as102_data1_st.hex
linux-firmware-dvb-20170329_4 /usr/lib/firmware/as102_data2_st.hex
linux-firmware-dvb-20170329_4 /usr/share/licenses/linux-firmware-dvb/README.as102
we can just wait a few hours
Hey @absrd, could you now please force-push again? The indexing seems to be finished.
Also please don't forget to add "fixes #40674" to the body. :+1:
it's there
It does seem like the branch should be rebased with master before a new push?
no, that shouldn't matter. and xlocate hasn't updated yet from what I see
no, that shouldn't matter. and xlocate hasn't updated yet from what I see
Interesting, mine is updated.
[datacobra@sourcerer ~]$ xlocate as102 | grep linux-firmware
linux-firmware-20220411_1 /usr/lib/firmware/as102_data1_st.hex
linux-firmware-20220411_1 /usr/lib/firmware/as102_data2_st.hex
linux-firmware-dvb-20170329_5 /usr/share/licenses/linux-firmware-dvb/README.as102
Do get rid of the no longer needed license files I've created a new PR. :+1: