[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Roger Pau Monné changed: What|Removed |Added Assignee|b...@freebsd.org|roy...@freebsd.org Status|Open|In Progress --- Comment #61 from Roger Pau Monné --- Created attachment 232075 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232075&action=edit Proposed fix Can you please test the attached patch and see if it solves the issue? Thanks, Roger. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #60 from Roger Pau Monné --- (In reply to Ed Maste from comment #59) Maybe we could do the check only if the hypervisor CPUID is set? In order to not have this depend on Xen specifically. I would assume that tables build by an hypervisor wouldn't have NO_VGA set unless it's on purpose. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Ed Maste changed: What|Removed |Added CC||roy...@freebsd.org --- Comment #59 from Ed Maste --- ACPI FADT VGA check was added in: commit c2272faa06dec2f027c5359529cf8f4f3593c164 Author: Roger Pau Monné Date: Tue Mar 13 09:38:53 2018 + vt_vga: check if VGA is available from ACPI FADT table On x86 the IA-PC Boot Flags in the FADT can signal whether VGA is available or not. In Linux presence of the the flag sets x86_platform.legacy.no_vga = 1 which is used in only one place, arch/x86/xen/enlighten_hvm.c xen_hvm_guest_late_init() In particular as far as I can tell it does not appear to control whether the VGA console is probed or not. It seems there is a lot of firmware with broken ACPI tables that incorrectly sets this flag and it may be better to ignore it. Roger, is it possible that the flag could be used only w/ Xen? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #58 from Michael Proto --- Created attachment 232059 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232059&action=edit acpidump of a J1900 (ASrock Q1900-ITX) Attaching 'acpidump -dt' output as requested. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #57 from Eugene Grosbein --- (In reply to Ed Maste from comment #54) I have remote access to one of such systems. acpidump and dmidecode outputs attached. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #56 from Eugene Grosbein --- Created attachment 232022 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232022&action=edit dmidecode output of dmidecode corresponding to same system as described in the attachment 232021 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #55 from Eugene Grosbein --- Created attachment 232021 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232021&action=edit output of acpidump -dt The system has been updated to 12.3-STABLE, in case this matters. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 (ACPI indicates no VGA)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Ed Maste changed: What|Removed |Added Summary|FreeBSD 11.2 fails to boot |FreeBSD 11.2 fails to boot |on Celeron J1900 after |on Celeron J1900 after |upgrade from 11.1 |upgrade from 11.1 (ACPI ||indicates no VGA) --- Comment #54 from Ed Maste --- This hardware sets the "VGA Not Present" flag, described as: > If set, indicates to OSPM that it must not blindly probe the VGA hardware > (that responds to MMIO addresses Ah-Bh and IO ports 3B0h-3BBh and > 3C0h-3DFh) that may cause machine check on this system. If clear, indicates > to OSPM that it is safe to probe the VGA hardware. Could users of affected machines get an ACPI dump and attach it to this PR? (acpidump -dt) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #53 from Ed Maste --- Are there any instances of this issue where, on a supported release, > hw.vga.acpi_ignore_no_vga="1" does not work as a workaround? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Ahmed changed: What|Removed |Added CC||ahmedsayeed1...@yahoo.com --- Comment #52 from Ahmed --- amd64-linux-siginfo.c: Adjust include order to avoid gnulib error http://www.compilatori.com/computers/latest-car-deals/ On Fedora rawhide, after updating to glibc-2.33, I'm seeing the following build failure: http://www.acpirateradio.co.uk/travel/good/ CXXnat/amd64-linux-siginfo.o In file included from /usr/include/bits/sigstksz.h:24, http://www.logoarts.co.uk/services/affordable-printer/ from /usr/include/signal.h:315, from ../gnulib/import/signal.h:52, http://www.slipstone.co.uk/property/hp-of-cars/ from /ironwood1/sourceware-git/rawhide-gnulib http://www.mconstantine.co.uk/category/health/ /bld/../../worktree-gnulib/gdbserver/../gdb/nat/amd64-linux-siginfo.c:20: http://embermanchester.uk/services/whatsapp-number-change/ ../gnulib/import/unistd.h:663:3: error: #error "Please include config.h first." 663 | #error "Please include config.h first." http://connstr.net/property/mars-researches/ | ^ glibc-2.33 has changed signal.h to now include http://www.go-mk-websites.co.uk/category/health/ which, in turn, includes . http://joerg.li/technology/b-class-cars/ For a gdb build, this causes the gnulib version of unistd.h to be pulled in first. The build failure shown https://www.mktrade.fi/ above happens because gnulib's config.h has not been included before the include of . http://www.jopspeech.com/health/nvidia-rtx-2060/ The fix is simple - we just rearrange the order of the header file includes to make sure that gdbsupport/ http://fishingnewsletters.co.uk/category/health/ commondefs.h is included before attempting to include signal.h. Note that gdbsupport/commondefs.h includes . http://www.wearelondonmade.com/health/check-ups/ Build and regression tested on Fedora 33. On Fedora rawhide, GDB builds again. https://waytowhatsnext.com/shopping/xbox-release-date/ gdb/ChangeLog: glibc-2.33 has changed signal.h to now include which, in turn, includes . http://www.iu-bloomington.com/computers/invisible-with-vpn/ For a gdb build, this causes the gnulib version of unistd.h to be http://the-hunters.org/category/health/ pulled in first. The build failure shown above happens because gnulib's https://komiya-dental.com/crypto/new-coins/ config.h has not been included before the include of . http://www-look-4.com/tech/nvidia-and-samsung/ The fix is simple - we just rearrange the order of the header file https://www.webb-dev.co.uk/crypto/crypto-for-investing/ includes to make sure that gdbsupport/commondefs.h is included before attempting to include signal.h. Note that gdbsupport/commondefs.h includes . -- You are receiving this mail because: You are the assignee for the bug.
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Robert James Hernandez changed: What|Removed |Added CC||r...@sarcasticadmin.com --- Comment #51 from Robert James Hernandez --- I ran into this the other week on my ASRock N3150-ITX as well. It was hanging at the message: "can't find '/boot/entropy' early in the boot. Initially I thought I would update my ASRock BIOS to 2.00 but that did not resolve the issue. I ended up having to set hw.vga.acpi_ignore_no_vga="1" in the loader to get it to boot. I was using the following version of FreeBSD: # uname -a FreeBSD roomservice 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #50 from Mathieu Arnold --- So, having hw.vga.acpi_ignore_no_vga="1" fixed it. As that motherboard does not have any VGA output, but only DVI-D, HDMI and display port, it feels strange to have to tell the kernel that "hey, there is no vga, but it's ok" Just saw that the "VT: init without driver." has been replaced by a "VT(vga): resolution 640x480" wondering if I can change the resolution, or make it see it is not really VGA. But this is for another day. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #49 from Mathieu Arnold --- So, today, I wondered why the HDMI display on my NAS always stopped after loading the kernel. (The nas works just fine, the display is frozen there.) and after searching the interwebs for "VT: init without driver.", I stumbled upon this page. I have a ASRock N3150-ITX motherboard with an Intel(R) Celeron(R) CPU N3150 CPU. It currently runs 12.1. From pciconf, the graphics adapter is: vgapci0@pci0:0:2:0: class=0x03 card=0x22b11849 chip=0x22b18086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller' class = display subclass = VGA I am going to try and see which of all the incantations in here I need to use to get the vt console working. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #48 from Michael Proto --- So with 11.3 released, the following /boot/loader.conf settings do indeed work with my J1900-ITX: kern.vty="vt" hw.vga.acpi_ignore_no_vga="1" Thanks to all involved!! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 zain david changed: What|Removed |Added CC||omarande...@gmail.com --- Comment #47 from zain david --- great job. http://www.winmilliongame.com http://www.gtagame100.com http://www.subway-game.com http://www.zumagame100.com -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172
--- Comment #46 from Jeff Kletsky ---
To add, this box is *not* using UEFI boot, but using BIOS ("legacy") boot, so
the issue is not confined to UEFI boot.
The release notes at
https://www.freebsd.org/releases/12.0R/relnotes.html#errata do not indicate
that there is any problem, nor do they seem to provide a link to
https://www.freebsd.org/releases/12.0R/errata.html Providing such a link would
be valuable. As indicated by the lead paragraph,
> [2018-12-11] Some Intel® J1900 systems may hang on boot in UEFI mode. An
> observed workaround is to set kern.vty=sc at the loader(8) prompt. To have
> the setting persist after reboot(8), add kern.vty=sc to loader.conf(5).
should be expanded in scope by removal of the text "in UEFI mode"
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #45 from Jeff Kletsky --- As there now appears to be a set of work-arounds, and that this seems to be a common problem on at least J1900 and possibly other Celeron devices of that era, such as the N3150, I would suggest this issue and at least a link to the workaround be present in the Release Notes (which I did check prior to upgrading) https://www.freebsd.org/releases/12.0R/relnotes.html#errata See further https://forums.freebsd.org/threads/freebsd-upgrade-11-1-to-11-2-fails-to-boot-11-2-kernel-no-vb-no-nvidia.66538/ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Jeff Kletsky changed: What|Removed |Added CC||jeff+free...@wagsky.com --- Comment #44 from Jeff Kletsky --- Just ran into this (again) after not being able to put off an upgrade on a J1900-based system any longer. Still an issue with 11.1-RELEASE-p(final) to 12.0-RELEASE using freebsd-update -r 12.0-RELEASE fetch / freebsd-update install -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #43 from j...@transactionware.com --- An additional datapoint: Booting with UEFI on the Tipro J1900 system resolves the problem, and kern.vty=vt works find all the way through. No change on the Supermicro X10SBA, also with a J1900. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Ryan Moeller changed: What|Removed |Added CC||r...@freqlabs.com --- Comment #42 from Ryan Moeller --- (In reply to Michael Proto from comment #41) That setting is not available in any 11.2 releases yet, but it is available on stable/11 snapshots. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #41 from Michael Proto --- Thank you for the update Eugene. While I have no doubt the ACPI tables on this discount hardware are likely the cause (see below**), unfortunately this particular suggested fix did not work for me. Intel Celeron J1900 (ASrock Q1900-ITX) Escape to bootloader on boot set kern.vty="vt" set hw.vga.acpi_ignore_no_vga="1" I still see the same problem, the spinner freezes when loading the kernel until I reboot and either set kern.vty="sc" or disconnect keyboard/monitor. ** Yes, this BIOS is quirky. I have it attached to a KVM via VGA/PS2 and during boot if my KVM is active on this terminal the system will sit on the BIOS "Press a key to enter option" screen forever until I hit ANY KEY, including CTRL/ALT. With the KVM pointed elsewhere it boots normally. I'm going to check my provider (again, likely in futility) for an updated firmware but wanted to throw this in as it is likely a sh*ty BIOS/UEFI being the issue. While I don't expect FreeBSD to have to work around it I'm prepared to do what I can to help debug. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Eugene Grosbein changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2292 ||35 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Status|New |Open --- Comment #40 from Eugene Grosbein --- Anyone having this problem should blame manufacturer of its hardware for garbage in its ACPI tables that is root of the problem. ACPI reports that system has no VGA at all. syscons ignores ACPI but vt obeys since 11.2 (it ignored before). We already have a workaround for this problem that allows using vt(4) driver when old syscons cannot be used, e.g. in UEFI environment. Add this to /boot/loader.conf: hw.vga.acpi_ignore_no_vga=1 Perhaps, installation media intended for interactive installation should have it by default. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #39 from Ed Maste --- (In reply to Bernhard Froehlich from comment #27) > @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. That is correct. We also have snapshots of stable/11 at various points available in http://artifact.ci.freebsd.org/snapshot/stable-11/ which could be used to narrow the range of potential offending commits further. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #38 from Ed Maste --- (In reply to mam from comment #37) > There is no real hardware needed for the fix, just drop the faulty driver and > use the working one as default. Nobody would be harmed and everything would > work. No, these are drivers for the same hardware, so the current, non-legacy driver needs to be fixed to work with this hardware. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #37 from mam --- (In reply to Ed Maste from comment #36) There is no real hardware needed for the fix, just drop the faulty driver and use the working one as default. Nobody would be harmed and everything would work. Or, make it more complex, look at the hardware at bootime and if a J1900 is found, switch drivers. But of course, just keep on waiting will solve it too. Someday those affected CPUs will be out of service and nobody will notice it anymore. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #36 from Ed Maste --- (In reply to mam from comment #34) > But of course, the issue should have been resolved by now, I have the > impression, nobody wants to really implement it into the next distribution. Nobody with the skill and availability to fix this issue has the affected hardware. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #35 from sim...@email.it --- (In reply to mam from comment #34) Thank you very much for you reply, works 100% (you indeed teached a new trick to an old dog ;-) ...) And yes! i agree: ... the issue should have been resolved by now, I have the impression, nobody wants to really implement it into the next distribution. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #34 from mam --- (In reply to simonp from comment #33) You can use the same "trick" for a new installation. Boot from DVD/Stick, go into boot options, change the console driver to SC and continue as usually. after installation, remember to change it permanently in the /boot config But of course, the issue should have been resolved by now, I have the impression, nobody wants to really implement it into the next distribution. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 sim...@email.it changed: What|Removed |Added CC||sim...@email.it --- Comment #33 from sim...@email.it --- Just a little precisation: 11.2 does not only fail to boot "after an upgrade" it just fails to boot on j1900, so it can't be installed ... i suggest to revise the importance of the problem Sorry for having no solution to propose. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #32 from j...@transactionware.com --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #31 from j...@transactionware.com --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: [Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
On Fri, 8 Feb 2019, Bruce Evans wrote: On Thu, 7 Feb 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 [syncing sc with i915kms, fixing lost video, and fixing corrupt i915kms] On a Haswell desktop: - first load of i915kms followed by vidcontrol MODE_280 gives the 16 lines of corruption - suspend (1 error writing a register from i915kms). Oops, then a long timeout and GEM idle failure. The suspend is aborted and video is never lost - but this fixes the corruption! Maybe a suspend bounce would do it even better Suspend bounce indeed works better. After normal suspend/resume loses video, load and unload i915kms to restore video with corruption in graphics modes. Then suspend with bounce to fix the corruption in at least critical VESA modes (VGA mode 13 is broken). Or to get i915kms without corruption, start cold or reset as above; then load i915kms and fix the corruption using suspend bounce. That was for sc. vt is easier to fix. There is no visible corruption. Just load i915kms to restore video. But to load it, first unload it. Bruce ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: [Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
On Thu, 7 Feb 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #30 from Pavel Minaev --- 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. To fix sc, just sync its mode with the drm mode using vidcontrol MODE_xxx if you can find such a mode. Mode 280 (1024x768x32 graphics) works on 3 systems with Intel graphics here using the non-port i915kms module, except for 16 lines of corrupt pixels near the top of the screen, and that can be fixed by higher magic. sc then works better than vt even with the module loaded, at least in -current. It allows switching to all old vga and vesa modes, and unloading i915kms, and restoring video after resume. After loading i915kms, it doesn't work so well to switch the sc mode to 24 (80x25 VGA text). First switch a mode compatible with the module. sc uses the VESA BIOS to switch. I use a vga utility to check that this mode switch doesn't change any standard vga registers, but it is easy to see if too much changed -- the screen will be garbage or remain black. Switching to all other modes supported by sc (see vidcontrol -i mode for the list) then works the same as without the module, except for the 16 lines of corruption. Better switch back the common mode before using X. Unloading i915kms corrupts leaves much more than 16 lines in graphics modes corrupted. Mode 24 still works but may take first switching to another mode to reach. For vt, unloading i915kms gives a black screen and there is no way to recover since vt can't switch modes dynamically except for the initial switch to use the module. Loading i915kms again reduces the corruption left by unloading it by a bit, but it is much more than on the first load. It affects vt too (but vt doesn't have the 16 lines of corruption after the first load). The smaller corruption is that writing a pixel to any one of the 16 lines appears to write the same pixel to them all. To restore video after resume, loading and unloading i915kms works for me, after fixing resume for the new pae_mode = 1 case and working around a bug in the VESA BIOS. The bug is the same in 2 7-8 year old Sandybridge laptops (HP 8460p and HP 8570p)and 1 4 year old Haswell desktop. To fix it, change vesa_state in kernel memory from 15 to 7. Otherwise the bug gives a trap on a garbage pointer in the VESA BIOS. This is only necessary using sc. Video usually doesn't come back after fixing this bug. It comes back only on HP 8570p asnd this may depend on a BIOS update (HP 8460p is similar but doesn't have BIOS update). To fix the i915kms corruption, some magic order of i915kms loads and unloads and suspends and resumes works for me. I forget if this only works on HP 8570p. Since unloading i915kms leaves corruption, this probably only does work on HP 8570p. Useful orders on HP 8570p: - start with bad corruption in graphics modes from i915kms load and unload - switch mode to 24 - suspend. Here is a script that edits vesa_state (it is missing error checking. Don't run it if you don't have a kernel with vesa_state in it, but vesa_state is standard with sc): addr=0x$(nm /kernel|grep ' b vesa_state$' | cut -c1-8) echo $addr echo -n 7 | tr 7 '\007' | dd of=/dev/kmem bs=1 oseek=$addr count=1 - resume (video comes back) - switch to a VESA graphics mode to verify that the corruption is fixed - switch in advance to the mode that i915kms will set - load i915kms (sc keeps working throughout). You can also switch in advance at boot time using a tunable (?) to set the default mode. Also load i915kms in the loader. sc then again works better than vt since it starts in the right mode. - oops, this only fixed the bad corruption. The 16-line corruption is back. - so we must be in the i915kms mode before suspend/resume. We are in it now. - suspend - resume (video comes back). All the corruption is fixed now. Video comes back almost instantly and the corruption is fixed then. USB and em take a long time to come back on this system (10-20 seconds). Video only comes back visibly in normal syscons modes (text or graphics). In libvgl graphics modes, the screen remains black and libvgl seems to be hung waiting for screen access. Actually, it seems to have crashed. It needs some fixes to not crash on startup in newer graphics modes. It and old X using similar methods are good for showing the corruption. - after doing this in libvgl, mode switches don't work to bring video back. So start another cycle. Unload i1915kms to get video the its usual corruption from load/unload... On a Haswell desktop: - first load of i915kms followed by vidcontrol MODE_280 gives the 16 lines of corruption - suspend (1 error writing a register from i915kms). Oops, th
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #30 from Pavel Minaev --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #29 from mam --- good :-) 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) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #28 from Vicen Dominguez --- (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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #27 from Bernhard Froehlich --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #26 from mam --- 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). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #25 from Ed Maste --- (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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #24 from mam --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #23 from Ed Maste --- (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 receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #22 from mam --- 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 :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #21 from Vicen Dominguez --- (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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #20 from mam --- (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 ? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #19 from Vicen Dominguez --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #18 from j...@transactionware.com --- I am seeing this problem in 12.0-BETA4 on a SuperMicro J1900 miniITX based system. Setting the console to "sc" resolves the problem. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Michael Proto changed: What|Removed |Added CC||m...@jellydonut.org --- Comment #17 from Michael Proto --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Arthur Chance changed: What|Removed |Added CC||art...@qeng-ho.org --- Comment #16 from Arthur Chance --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 r...@thiagoc.net changed: What|Removed |Added CC||r...@thiagoc.net --- Comment #15 from r...@thiagoc.net --- I can confirm this bug. Adding "kern.vty=sc" works. The system is an ASRock D1800B-ITX. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 miguelmcl...@gmail.com changed: What|Removed |Added CC||miguelmcl...@gmail.com --- Comment #14 from miguelmcl...@gmail.com --- 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? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #13 from Max Burke --- 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? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #12 from Pavel Minaev --- I can confirm that changing the vty driver to "sc" fixes boot for me as well (although I also see flicker with it). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #11 from mam --- 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!) :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #10 from Daniel Mafua --- 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" in /boot/loader.conf -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #9 from mam --- 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... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 mam changed: What|Removed |Added CC||m...@werries.de --- Comment #8 from mam --- Created attachment 196316 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196316&action=edit dmesg output of 11.2 kernel on J1900 (nonworking video output) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #7 from Daniel Mafua --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Daniel Mafua changed: What|Removed |Added CC||ma...@dempseyuniform.com --- Comment #6 from Daniel Mafua --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #5 from Vicen Dominguez --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Vicen Dominguez changed: What|Removed |Added CC||elplutoni...@gmail.com --- Comment #4 from Vicen Dominguez --- Hey guys! 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... :( any idea? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #3 from Max Burke --- 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 :) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #2 from Pavel Minaev --- Same exact problem with FreeBSD-12.0-CURRENT-amd64-20180709-r336134-mini-memstick.img -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Pavel Minaev changed: What|Removed |Added CC||int...@gmail.com --- Comment #1 from Pavel Minaev --- 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Mark Linimon changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 Bug ID: 230172 Summary: FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1 Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: maxbu...@gmail.com I am seeing the issue mentioned in this thread: https://forums.freebsd.org/threads/freebsd-upgrade-11-1-to-11-2-fails-to-boot-11-2-kernel-no-vb-no-nvidia.66538/ 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. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
