console no longer working after upgrade to 2.4.4

Napsterbater

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=1

to /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?

jimp

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.

maarten

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=1

Booting 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

jimp

@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=1
Booting 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

The 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.

bole5

@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=sc

There was another suggestion that also seem to have worked:

hw.vga.acpi_ignore_no_vga=1

Hope this fixes your problem.

Napsterbater

@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=sc

That 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.

bole5

@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.

jimp

@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=sc yesterday.

breakaway

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”?

stephenw10

Using the kern.vty=sc loader line should work instead.

Steve