I am seeing the issue mentioned in this thread:
I upgraded from FreeBSD 11.1 to 11.2 via freebsd-update but the system fails to boot. As mentioned in the thread, after the "Booting message", but before the screen clears and prints the copyright message, the boot process stops.
The system is an ASRock Q1900-ITX; there is no discrete video adapter.
I'm also seeing this problem on Thinkpad 11E:
- Celeron N2940
- Intel HD Graphics (Bay Trail)
It's definitely not something with installed packages, custom kernels etc, because I can also reproduce it with install media - USB stick with image for 11.1 boots fine, and the one with 11.2 fails in the same exact way.
Same exact problem with FreeBSD-12.0-CURRENT-amd64-20180709-r336134-mini-memstick.img
I have tried enabling the verbose boot option with the out-of-the-box 11.2 kernel but this has provided no extra diagnostic information.
(Unless I'm doing it wrong, which may be the case :)
Just confirm it from Spain. Same system (ASRock Q1900-ITX) and indeed... freezed at boot time.
I don't have any nvidea inside so I smell no relation to this driver.
The hang is in kernel time, just after the libalias.ko in my case.
And, indeed again, i am coming from 11.1 without problem so, sadly, it seems a regression... :(
In a new and a crazy try, I disabled all modules (including zfs) from the loader.conf with the same result: hung.
I have to add that I have a mirror (geom) as boot disk, and ufs. Nothing else.
Impossible to get some extra information with "verbose" boot enabled.
I've noticed many experiencing this issue (myself included) seem to have Intel Celeron/Atom processors. I do however have a few such boxes I successfully upgraded to 11.2, however noticed a line in the logs "VT: init without driver"
I had a box with an Intel Atom E3845 which would not boot a 11.2 kernel, but on a hunch unplugged the monitor then it would work (but with the message seen above). Notably the boxes I upgraded successfully from 11.1 to 11.2 didn't have monitors hooked up to them.
I did more testing on my Intel Atom PC. I waited for the machine to fully boot, then logged in via ssh and everything seemes fine, however if I plug in a monitor I see it's still stuck at the "booting..." screen before the copyright message.
Created attachment 196316 [details]
dmesg output of 11.2 kernel on J1900 (nonworking video output)
I can second that, altough the console is totally frozen (after the boot menu), the machine (also Asustec J1900-ITX) boots up and is available via SSH later on.
I have attached the dmesg output that contains a few warnings, maybe it can help to fix the problem because although this is mainly a router, a "last resort console" should be available too if everything fails...
In my case I also noticed ttyv* devices are missing in /dev. This probably leads a person to believe the system is frozen, as it does not reboot with ctrl+alt+del since the system can't accept user input.
I've been able to work around this problem by setting kern.vty="sc"
great idea! it works!
(lol, it even now is in colour but in B&W like before :-) )
(the video output is not really great, there are often disturbing stripes and flicker on the screen, but who cares, at least a working console!)
I can confirm that changing the vty driver to "sc" fixes boot for me as well (although I also see flicker with it).
Adding kern.vty=sc to my /boot/loader.conf worked! My system now boots with 11.2! :-)
(I had tried the monitor trick but the system never came up.)
Is there something that we can do to get a fix imported into the base system now?
Just found the same issue today, after updating to 11.2 on a Intel "Braswell" cpu.
using "vc" works around the issue, but I actually update so I could test a newer DRM code...
Any idea of a possible fix?
I can confirm this bug. Adding "kern.vty=sc" works. The system is an ASRock D1800B-ITX.
Just to add another data point. Gigabyte Brix box with Celeron N3000. Booting with kern.vty=vt appears to hang before the graphics mode switch, kern.vty=sc works fine.
Adding a me-too here, just upgraded my Celeron J1900 (ASrock Q1900-ITX) from FreeBSD 10.4 to 11.2 via freebsd-update and ran into this exact issue. Setting kern.vty=sc at the loader prompt allows the machine to complete the boot sequence and adding it to /boot/loader.conf allows a reboot to work without issue.
I am seeing this problem in 12.0-BETA4 on a SuperMicro J1900 miniITX based system. Setting the console to "sc" resolves the problem.
I know this is from 11.1 to 11.2 upgrading process. But, just for your information, same as FreeBSD 12.0-RELEASE upgraded from FreeBSD 11.1
The system is completely stuck in the boot process, without ssh access.
(In reply to Vicen Dominguez from comment #19)
this is not really surprising, the faulty driver has not been repaired/exchanged. You should have switched the device before update as suggested in this thread.
but usually, the machine, although looking irresponsly, is accessable from the network... maybe your problem is a bit different / deeper ?
(In reply to mam from comment #20)
Indeed mam! changing the driver to "sc" worked for me. As you said, perhaps my problem is a little different because I never could connect to the server via ssh (waiting for 2 hours).
I am lost... no ideas. Anyway, thank you to everybody.
but now with the "sc" driver the network works again too???
that would be strange, but maybe now you can find a log entry that shines a light on you problem.
Anyway, if it works again, all is fine :-)
(In reply to mam from comment #22)
Well, if vt used to work and now doesn't there's a regression we need to find. It seems there are several different reports in here - can someone confirm that the problem occurs under one (or both) of these cases:
11.1 to 11.2 upgrade with no monitor attached
11.1 to 11.2 upgrade with monitor attached
Also please include the motherboard model, firmware version, and for the second case the monitor interface (VGA/HDMI/etc.)
you are funny :-)
How could somebody notice that the console does not work, if there is no monitor attached ???
As far as it looks for now, its always that AsRock Q1900-ITM Mobo, the connection to the monitor does not matter, there is nothing on either VGA, DVI or HDMI.
It looks like the Intel GPU onboard is not supported in this particular processor.
(In reply to mam from comment #24)
> How could somebody notice that the console does not work, if there is no
> monitor attached ???
If they're using a serial console.
then they would not notice it either.
Its only the monitor that blocks.
Not sure about the keyboard, because you cant see anything, typing is not really responsive too.
Thank god, everything else works, the machine boots up and you can login over the network.
At the beginning everybody (including me) thought, it was a total crash, because Bios is ok, then the booloader shows the cute Demon and lets you change config and so on. But as soon as you try to boot the kernel, the rotating / | \ ... animations stops and from then on, nothing appears on screen anymore (but the current contents stays there visible until the cows come home).
I can confirm the issue on an Supermicro X10SBA (FW 1.3a) with FreeBSD 12.0. That board also uses an Intel Celeron J1900.
@ed: If I understand you correctly you want to check if this is a regression between 11.1 and 11.2 so it should be enough to verify by booting those with a usb stick. I should be able to provide that data.
(In reply to mam from comment #22)
sorry mam, I wasn't very clear. yes yes... in a nutshell, with "sc" everything worked again.
I have a little "flicker" in the screen but it doesn't disturb me and I didn't try Xwindows, but it's a home server so the workaround works for me.
I have the "flicker" too. Its a bit annoying but much better than no pic at all :-)
(No idea about X stuff too, this is a router, not a desktop)
To use X, you'll need to kldload drm_next_kmod. If you do that with sc driver in effect, your screen will go blank the moment you do it. But the system is still alive, and if you then run X, it'll work. I just made a little script that does both.
Some notes when 'vt' is used (some of this also in comments above):
* Console output stops when the kernel starts booting.
* If the boot is allowed to complete it is available via ssh.
* /dev/ttyv* device entries are not present.
* Loading /boot/modules/i915kms.ko makes the device entries appear and console output resumes. In my case this is on FreeBSD 12-p3 with port graphics/drm-fbsd12-kmod.
* "kill -HUP 1" restarts getty processes and the console becomes usable.
* If /boot/modules/i915kms.ko is loaded via kld_list in /etc/rc.conf, console output will resume once the module is loaded and the ttyv* getty processes will start correctly.
My comments above were on a Tipro J1900 based touch screen system.
I have also tested on a SuperMicro X10SBA; there the system hangs when loading i915kms.ko, and requires a power cycle.