Author Topic: broadcom-wl 6.30.223.271-16pclos2019 [SOLVED]  (Read 454 times)

Offline dockmackie

  • Full Member
  • ****
  • Posts: 163
broadcom-wl 6.30.223.271-16pclos2019 [SOLVED]
« on: January 04, 2020, 07:04:02 PM »
Driver fails to build under kernel 5.4.8
Logged

Offline Tex

  • Administrator
  • Super Villain
  • **********
  • Posts: 21970
  • Space City, Tx
Re: broadcom-wl 6.30.223.271-16pclos2019
« Reply #1 on: January 04, 2020, 07:31:55 PM »
Driver fails to build under kernel 5.4.8

You need to continue booting the 5.4.7 kernel until the broadcom-wl driver catches up to the 5.4.8 kernel released 8 hours ago. Thanks for your report.

Logged

Offline dockmackie

  • Full Member
  • ****
  • Posts: 163
Re: broadcom-wl 6.30.223.271-16pclos2019
« Reply #2 on: January 04, 2020, 08:42:35 PM »
Thank you, good sir. That's what I figured. Was too quick on the draw. 5.4.7 it is, and remains until such time as.
Logged

Offline Tex

  • Administrator
  • Super Villain
  • **********
  • Posts: 21970
  • Space City, Tx
Re: broadcom-wl 6.30.223.271-16pclos2019
« Reply #3 on: January 05, 2020, 06:35:46 AM »
Thank you, good sir. That's what I figured. Was too quick on the draw. 5.4.7 it is, and remains until such time as.

These updates are on the way to the repo and will fix building the dkms kernel drivers for kernel 5.3.8 and prior kernels. This is the second time this package has stung me. No more updates for file and lib64magic1.

file-5.38-2pclos2020.x86_64.rpm
lib64magic1-5.38-2pclos2020.x86_64.rpm

Logged

Offline dockmackie

  • Full Member
  • ****
  • Posts: 163
Re: broadcom-wl 6.30.223.271-16pclos2019 [SOLVED]
« Reply #4 on: January 05, 2020, 11:46:41 AM »
OK, that worked, and thank you.

I noticed that during the boot with the second install of 5.4.8, it appeared nothing was being built. The OS came up minus connection. I manually started eth0 and it came up OK, though wlan0 fibrillated a bit before getting a normal heartbeat after ~6 seconds. So I rebooted, and all was back to usual, no noticeable anomalies - the manual start had persistence. Do I assume what needed building actually succeeded, but could not be attached to the new kernel because of the beloved 'magic', and that once that was repaired all was (relatively) well? Just curious.

I can stream music. I can stream effluent from the news. I can get on with other, and way less interesting, forms of heartburn. I mark this solved.

Thank you again, Tex.


Logged