Re: Lack of /dev/vtvga0?
On Fri, 22 Jun 2018 23:31:58 -0500 "Mahmoud Al-Qudsi" said Hello list, As I've mentioned in a previous message, I've been working on trying to get a proper graphics subsystem/desktop up and running under 12-CURRENT without any X components; something that was once possible a long time ago by using libvgl probably via SDL1.2 — an option that's been deprecated in SDL2 and isn't viable in all cases since libvgl doesn't support newcons/vt. I'm not clear if you're already possibly referring to this. But have you tried sc(4) ( SysCons ). If you haven't tried already; adding the following to your loader.conf(5) should give it to you: kern.vty=sc You can also include it in your custom kernel by adding this to your KERNCONF devicesc options SC_PIXEL_MODE # adds support for the raster text mode Hope this helps. --Chris I understand the limitations of the basic VGA driver (lack of hardware acceleration, current hard-coded 640x480x16 resolution) but I'm not clear on why the vt_vga driver does not make a framebuffer device available (vtvga0 is initialized, but there is no corresponding /dev/vtvga0). Isn't it possible to use vt_vga in pixel mode and directly write to the kernel console framebuffer? Any insight would be appreciated! Mahmoud Al-Qudsi NeoSmart Technologies ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Boot freezing after kernel load - root on zfs
There were some issues with legacy geely booting recently. What version? UEFI or legacy BIOS booting? Warner On Fri, Jun 22, 2018, 10:26 PM Ben Woods wrote: > On 23 June 2018 at 12:08, Allan Jude wrote: > > > If you just press shift a bunch of times, does it print the Mount root > > prompt? > > -- > > Allan Jude > > > > > No, unfortunately not. But please keep any troubleshooting suggestions > coming! > > I have tried booting with the KVM monitor and USB disconnected, with the > same result. > > It is also worth noting I can successfully boot from a USB stick running > the latest 12-current snapshot > FreeBSD-12.0-CURRENT-amd64-20180618-r335317-memstick.img. From there I can > import both of my zpools (zroot and zstore), and then export them again > before rebooting - still can't boot from disk. > > -- > From: Benjamin Woods > woods...@gmail.com > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Lack of /dev/vtvga0?
Hello list, As I've mentioned in a previous message, I've been working on trying to get a proper graphics subsystem/desktop up and running under 12-CURRENT without any X components; something that was once possible a long time ago by using libvgl probably via SDL1.2 — an option that's been deprecated in SDL2 and isn't viable in all cases since libvgl doesn't support newcons/vt. I understand the limitations of the basic VGA driver (lack of hardware acceleration, current hard-coded 640x480x16 resolution) but I'm not clear on why the vt_vga driver does not make a framebuffer device available (vtvga0 is initialized, but there is no corresponding /dev/vtvga0). Isn't it possible to use vt_vga in pixel mode and directly write to the kernel console framebuffer? Any insight would be appreciated! Mahmoud Al-Qudsi NeoSmart Technologies ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Boot freezing after kernel load - root on zfs
On 23 June 2018 at 12:08, Allan Jude wrote: > If you just press shift a bunch of times, does it print the Mount root > prompt? > -- > Allan Jude > No, unfortunately not. But please keep any troubleshooting suggestions coming! I have tried booting with the KVM monitor and USB disconnected, with the same result. It is also worth noting I can successfully boot from a USB stick running the latest 12-current snapshot FreeBSD-12.0-CURRENT-amd64-20180618-r335317-memstick.img. From there I can import both of my zpools (zroot and zstore), and then export them again before rebooting - still can't boot from disk. -- From: Benjamin Woods woods...@gmail.com ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Boot freezing after kernel load - root on zfs
On June 22, 2018 10:13:31 PM EDT, Ben Woods wrote: >Hi everyone, > >After shutting down to connect a new IP KVM switch (VGA and USB), my >FreeNAS mini hardware is no longer booting FreeBSD with root in zfs (no >encryption) - it is getting stuck after the kernel finishes loading and >it >tries to mount root and start_init. It just stops printing any more >output >to the screen, but I know the keyboard is working as ctrl+alt+delete >works. > >I wonder if this could be due to hard drives names being re-ordered >(e.g. >what was ada0 is now ada1). I have 2 SATA3 SSDs in a zfs mirror for >root >(showing as ada4 and ada5 during boot), and 4 SATA3 HDDs in a raidz2 >with >geli for further storage (showing as ada0-3, but these are only mounted >during rc init - after the point the boot process is getting stuck). I >have >no USB storage, although the IP KVM may present a virtual disk for >loading >media remotely. > >I am running 12-CURRENT, but know the recent upgrade is not the issue >because I can’t load from the previous boot environment either. > >Is anyone able to recommend a fix or a way to troubleshoot further? >Please >see below a link with screenshots at the end of the boot where it gets >stuck. > >https://imgur.com/gallery/vhn7ScC > >Thanks in advance for any help! > >Regards, >Ben > >-- >From: Benjamin Woods >woods...@gmail.com >___ >freebsd-current@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscr...@freebsd.org" If you just press shift a bunch of times, does it print the Mount root prompt? -- Allan Jude ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Boot freezing after kernel load - root on zfs
Hi everyone, After shutting down to connect a new IP KVM switch (VGA and USB), my FreeNAS mini hardware is no longer booting FreeBSD with root in zfs (no encryption) - it is getting stuck after the kernel finishes loading and it tries to mount root and start_init. It just stops printing any more output to the screen, but I know the keyboard is working as ctrl+alt+delete works. I wonder if this could be due to hard drives names being re-ordered (e.g. what was ada0 is now ada1). I have 2 SATA3 SSDs in a zfs mirror for root (showing as ada4 and ada5 during boot), and 4 SATA3 HDDs in a raidz2 with geli for further storage (showing as ada0-3, but these are only mounted during rc init - after the point the boot process is getting stuck). I have no USB storage, although the IP KVM may present a virtual disk for loading media remotely. I am running 12-CURRENT, but know the recent upgrade is not the issue because I can’t load from the previous boot environment either. Is anyone able to recommend a fix or a way to troubleshoot further? Please see below a link with screenshots at the end of the boot where it gets stuck. https://imgur.com/gallery/vhn7ScC Thanks in advance for any help! Regards, Ben -- From: Benjamin Woods woods...@gmail.com ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: head -r335568 breaks the ci.freebsd.org builds of the various FreeBSD-head-*-build
Mark Millard wrote: >from the likes of: > >https://ci.freebsd.org/job/FreeBSD-head-sparc64-build/8346/consoleText > >--- nfs_commonkrpc.o --- >/usr/src/sys/fs/nfs/nfs_commonkrpc.c: In function 'newnfs_request': >/usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: 'ND_HASSLOTID' undeclared >(first >use in this function) >/usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: (Each undeclared identifier >is >reported only once >/usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: for each function it appears >in.) >*** [nfs_commonkrpc.o] Error code 1 As you might have guessed, I missed part of the commit. Should be fixed by r335571. Pointy hat goes on me. Thanks for reporting it, rick ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
head -r335568 breaks the ci.freebsd.org builds of the various FreeBSD-head-*-build
from the likes of: https://ci.freebsd.org/job/FreeBSD-head-sparc64-build/8346/consoleText --- nfs_commonkrpc.o --- /usr/src/sys/fs/nfs/nfs_commonkrpc.c: In function 'newnfs_request': /usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: 'ND_HASSLOTID' undeclared (first use in this function) /usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: (Each undeclared identifier is reported only once /usr/src/sys/fs/nfs/nfs_commonkrpc.c:813: error: for each function it appears in.) *** [nfs_commonkrpc.o] Error code 1 (a gcc 4.2.1 context). Similarly for clang-based: --- all_subdir_nfscommon --- /usr/src/sys/fs/nfs/nfs_commonkrpc.c:814:20: error: use of undeclared identifier 'ND_HASSLOTID' (ND_NFSV41 | ND_HASSLOTID) && nmp != NULL && === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel broken on if_ixl when EVDEV is enabled
On 06/22/18 10:38, Navdeep Parhar wrote: > On 06/22/18 10:25, Pete Wright wrote: >> >> >> On 06/21/2018 20:47, Danilo Egêa Gondolfo wrote: >>> Hi, >>> >>> check if you have 'options IXL_IW' in your kernel conf. It's removed >>> from GENERIC. I had the same problem here with my customized conf. >> >> ah - that was totally it i think. i was lazy and just copied GENERIC to >> GENERIC-EVDEV so it got of sync. i've now re-created my EVDEV config to >> just include GENERIC. > > You can avoid your kernconf going out of sync by including GENERIC in it > and then adding just your customizations. oops I missed the last sentence in your email. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel broken on if_ixl when EVDEV is enabled
On 06/22/2018 10:38, Navdeep Parhar wrote: On 06/22/18 10:25, Pete Wright wrote: On 06/21/2018 20:47, Danilo Egêa Gondolfo wrote: Hi, check if you have 'options IXL_IW' in your kernel conf. It's removed from GENERIC. I had the same problem here with my customized conf. ah - that was totally it i think. i was lazy and just copied GENERIC to GENERIC-EVDEV so it got of sync. i've now re-created my EVDEV config to just include GENERIC. You can avoid your kernconf going out of sync by including GENERIC in it and then adding just your customizations. include GENERIC ident GENERIC-EVDEV options EVDEV_SUPPORT device evdev yep, that's exactly what i did - don't think my hasty response phrased things too well :) -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel broken on if_ixl when EVDEV is enabled
On 06/22/18 10:25, Pete Wright wrote: > > > On 06/21/2018 20:47, Danilo Egêa Gondolfo wrote: >> Hi, >> >> check if you have 'options IXL_IW' in your kernel conf. It's removed >> from GENERIC. I had the same problem here with my customized conf. > > ah - that was totally it i think. i was lazy and just copied GENERIC to > GENERIC-EVDEV so it got of sync. i've now re-created my EVDEV config to > just include GENERIC. You can avoid your kernconf going out of sync by including GENERIC in it and then adding just your customizations. include GENERIC ident GENERIC-EVDEV options EVDEV_SUPPORT device evdev Regards, Navdeep ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel broken on if_ixl when EVDEV is enabled
On 06/21/2018 20:47, Danilo Egêa Gondolfo wrote: Hi, check if you have 'options IXL_IW' in your kernel conf. It's removed from GENERIC. I had the same problem here with my customized conf. ah - that was totally it i think. i was lazy and just copied GENERIC to GENERIC-EVDEV so it got of sync. i've now re-created my EVDEV config to just include GENERIC. thanks for the heads up! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
clang on 12-CURRENT traps on its internal assertion when build kernel under nanobsd.sh control
I tripped over very strange, but repeateable (in my conditions) bug in clang on 12-CURRENT. This message will be rather long, as I need to describe all details. I have VBox-based (Windows 10 is host) virtual machine with very fresh 12-CURRENT FreeBSD guest (r335478 now). I'm using this VM to build NanoBSD "firmware" for my router and I'm updating this VM via "buildworld buildkernel" ~weekly. This VM has 4 core CPU, 8GiB of "physical" RAM and 16GiB of swap. I *never* have problem when I make "make -j4 buidlworld buildkernel" to update VM itself. It works rock-solid. But when I try to build NanoBSD image from SAME SOURCES (exactly the same!) with SAME compiler (I'm using system compiler as cross-compiler to decrease time of build) clang fails every second time. Other problem is, that "nanobsd.sh" with "make -j1", but it is NOT out-of-memory, as swap isn't used at all! Message is always the same, and file is the same (asterisks are by me, to highlight assert): /usr/bin/cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/nanobsd/data/src/amd64.amd64/tmp -B/usr/obj/nanobsd/data/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/data/src/sys/netgraph/bluetooth/include -I/data/src/sys/netgraph/bluetooth/drivers/ubtbcmfw -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/nanobsd/data/src/amd64.amd64/sys/D2500CC/opt_global.h -I. -I/data/src/sys -I/data/src/sys/contrib/ck/include -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/obj/nanobsd/data/src/amd64.amd64/sys/D2500CC -MD -MF.depend.ubtbcmfw.o -MTubtbcmfw.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c /data/src/sys/netgraph/bluetooth/drivers/ubtbcmfw/ubtbcmfw.c -o ubtbcmfw.o * Assertion failed: ((!RequiresNullTerminator || BufEnd[0] == 0) && "Buffer is not null terminated!"), function init, file /data/src/contrib/llvm/lib/Support/MemoryBuffer.cpp, line 48. * cc: error: unable to execute command: Abort trap (core dumped) cc: error: clang frontend command failed due to signal (use -v to see invocation) FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) Target: x86_64-unknown-freebsd12.0 Thread model: posix InstalledDir: /usr/bin cc: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed source, and associated run script. -- // Lev Serebryakov signature.asc Description: OpenPGP digital signature
