console no longer working after upgrade to 2.4.4
-
Supermicro board with Celeron J1900
kern.cam.boot_delay=10000
kern.ipc.nmbclusters="1000000"vm.kmem_size="435544320"
vm.kmem_size_max="535544320"
autoboot_delay="3"
hw.usb.no_pf="1"
-
You're hitting this: https://forum.netgate.com/post/790647
Either of the solutions there will correct that.
Steve
-
-
I have added a note for that console issue to the Upgrade Guide: https://www.netgate.com/docs/pfsense/install/upgrade-guide.html#upgrading-from-versions-older-than-pfsense-2-4-4
-
I am having this issues as well, the system only has Legacy boot and UEFI Win 7 and UEFI Win 8 options, only legacy works to boot at all.
System is a "ZOTAC ZBOX CI323" with Intel N3150 with Interggrated gfx
I Added
i915kms_load="YES" drm.i915.enable_unsupported=1to /boot/loader.conf.local
Yet while there is a few more lines added on the screen it still does not get past "Booting...", which im going to guess is because it is not a "i915" family GFX.
Any idea what I would need to add for the Intel N3150 GFX?
-
I'm not familiar with that hardware, but you might try changing to one of the UEFI boot options and then boot from a memstick and reinstall, see if the console works then. It may be that your BIOS doesn't get along too well with the current combination of kernel/boot scheme/paritions/etc.
-
I have the same problem with a Celeron J1900, adding the following to /boot/loader.conf.local does not help.
i915kms_load="YES" drm.i915.enable_unsupported=1Booting with kernel.old does allow the system to boot, Safemode does not help.
the system locks up it's not just the console the system does not even respond to ping messages on any internal interface -
@maarten said in console no longer working after upgrade to 2.4.4:
I have the same problem with a Celeron J1900, adding the following to /boot/loader.conf.local does not help.
i915kms_load="YES" drm.i915.enable_unsupported=1Booting with kernel.old does allow the system to boot, Safemode does not help.
the system locks up it's not just the console the system does not even respond to ping messages on any internal interfaceThe OP in this thread has a system that booted, but without the console. Your issue is different. If the system does not boot, then it is not this issue. Please start your own thread with additional details.
-
@Napsterbater
I was researching on this very problem. I too have a ZBOX CI323 and am waiting with upgrading to 2.4.4 after I read about this problem.
On freebsd pages there is a bug with N3150 that looks exactly like the problem we are experiencing. You can read more here. The reporter did a great job of finding the actual commit which caused this error. As far I can read there are two workarounds.The original poster added following to /boot/loader.conf as a workaround:
# Load SysCons driver kern.vty=scThere was another suggestion that also seem to have worked:
hw.vga.acpi_ignore_no_vga=1Hope this fixes your problem.
-
@bole5 said in console no longer working after upgrade to 2.4.4:
The original poster added following to /boot/loader.conf as a workaround:
Load SysCons driver
kern.vty=scThat worked for me, and for another poster in a diffrent thread (https://forum.netgate.com/topic/135874/console-fails-to-boot-after-2-4-4-upgrade/9)
Thanks.
-
@napsterbater said in console no longer working after upgrade to 2.4.4:
https://forum.netgate.com/topic/135874/console-fails-to-boot-after-2-4-4-upgrade/9
Great. Glad you solved your problem.
@jimp Would you mind updating Upgrade Guide? This issue could be specific to N3150.
-
@bole5 said in console no longer working after upgrade to 2.4.4:
@jimp Would you mind updating Upgrade Guide? This issue could be specific to N3150.
It's already there. I added a note about
kern.vty=scyesterday. -
How to work around the fact that some systems do not have UEFI boot but you still want to install pfSense. The installer does not show anything after “booting”?
-
Using the
kern.vty=scloader line should work instead.Steve
