Kernel Panic when Upgrading to 2.8.0 beta
-
@Spacecase you can try be disabling the wifi card, either in the BIOS or if that is not possible, using a hint, like explained a bit further up in this thread:
https://forum.netgate.com/post/1214869
-
@patient0
Thanks.I've seen what's been posted so far, but reported the event to let developers know there's a bug common to Intel and AMD platforms. For the time being, I need a functioning network. I'll try to find some time to troubleshoot it over the weekend.
-
Yup there's some regression there in at least in the iwlwifi driver. It's failing to load the firmware into the card.
But, yes, disabling that device should allow it to boot normally.
-
@stephenw10
Thanks for looking into the issue. I'm left wondering if it's a corner case or something more widespread. I guess we'll find out soon enough. -
@patient0
I disabled WiFi in the BIOS and am now successfully running 2.8.0. -
N netblues referenced this topic
-
Thought I'd add I had the same (hard lock) kernel panic due to chipset 'iwm3160fw'.
I disabled it using the hint/config file mentioned above. Much appreciate being able to go forward, rather than back-out.I did periodically use the WiFi adapter, so hopefully BSD resolve the issue(s) with those chipsets in a subsequent update...
-
@manicmoose said in Kernel Panic when Upgrading to 2.8.0 beta:
I did periodically use the WiFi adapter, so hopefully BSD resolve the issue(s) with those chipsets in a subsequent update...
Euh ... for the last ... well, since FreeBSD exists, it's Wifi (adapter) driver support is known as quasi non existent.
For drivers to be created, device hardware details need to be 'public'. A driver will exists of course, and it will be for 'Microsoft' based devices. Remember : if you create a driver, you also have to support it.
Just image : reverse engineer NIC wifi driver not knowing the hardware.Your only option : wait until someone creates a driver, and then wait until the FreeBSD author include that driver into FreeBSD, so Netgate can pull it all into pfSense.
Be ware that FreeBSD is known for not importing crap-ware.
The driver's source code should be 'open'.Making a long story short : you need an AP ? Get an AP.
-
I get all that, but you're missing the point.
That same WiFi chip/adapter has been working with pfsense/BSD for over 5 years...the driver probably just needs slight adjustment for a newer kernel, would be my expectation.
-
@manicmoose said in Kernel Panic when Upgrading to 2.8.0 beta:
That same WiFi chip/adapter has been working with pfsense/BSD for over 5 years...the driver probably just needs slight adjustment for a newer kernel, would be my expectation.
I though you were getting the point that pfSense pfSense 2.7.0 uses FreeBSD 14.x
pfSense 2.8.0 uses newer kernel, 15.x.Sure enough, the same (?) driver recompiled for "15" fails - for you.
If it's part of the new "15" kernel set, then it was working for some one, otherwise FreeBSD (and Netgate ?) wouldn't have included the driver.
If you have a chip set version type or any detail that can identify your wifi NIC, check up stream (freebsd driver support) if the issue is known, maybe a more recent driver exists already, compiled for your processor (x86, x64 or arm) and didn't make it into this pfSense build (using kernel 15.x).I agree, making it work could be very easy. It's just a matter of : the guy who has the same hardware as you and can build/test/write/understand FreeBSD kernel drivers, has to to 'his thing'.
edit : remember :
Office 365 for Windows 10 might work Windows 11.
Office is a user land app.
A kernel driver is totally different. For some 'devices' like a NIC for Windows 10 will not work for Windows 11. Is has to be, at least, rebuild.
As system calls, settings etc etc did change, some source modification are needed for every device driver. -
Is it just me, or does it feel weird that pfsense are using freebsd v15, which has not even been officially released yet and won't be until Nov/Dec. this year?
Normally, software like firewalls are built on N-1 version, which have been road-tested and proven to be solid.
Obvs, Netgate are different....or are using CE community as the guinea pigs.edit
Looks like there is active work still going on with these drivers for FreeBSD.They removed the 'iwm' firmware as shipped kernel modules and are just trying to load the raw firmware with version 15 - so I guess there's hope that once all the pre-req's and bugs are ironed out, a subsequent update from pfsense could get the WiFi adapters working again.
-
@manicmoose said in Kernel Panic when Upgrading to 2.8.0 beta:
are using CE community as the guinea pigs.
@manicmoose Plus is has been more current than CE in recent years. So no the reverse has been the case which imo is a problem for the long term viability of a free CE version competing for plus clients without clear benefit for Netgate.
-
Yup Plus has been running 15 for some time.
But also, yes, there appears to be a regression with some drivers that now ship without firmware and load it. It's not just iwm. It should not kernel panic if the driver fails to attach for whatever reason.
-
Hi @stephenw10 quick question...
Having had to use this workaround putting the hint into loader.conf.local....should that be included in the backup xml file? I can't seem to find any reference to the hint in it.
I would have thought it should be in there, in case we have to rescue boot/reinstall off a USB image?! -
Your "loader.conf.local" won't get saved in the config.xml.
Rule of thumb : only GUI settings are saved.Possible solution : Install this package :
and use it to date/annotate/detail (with URLs to the sites /forum /whatever ) and make a Note about what you've put into these system file.
The Notes info will get saved into the config.xml
From now on, you won't need to remember what you've done today, yesterday, or last year.
In case of a re install, read your Notes and do what said in there, you'll be fine. -
No the loader file isn't included in config file.
You could add it using the filer package but you don't have to. You can always set that hint at the loader prompt to allow the system to boot before adding the file again.
