Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
On Wed, May 30, 2018 at 03:50:39PM +, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). Tested memstick.img in both UEFI and legacy mode on : Lenovo ThinkPad T430s MSI Cubi 3 Silent Both work for me. > Thanks, > > Glen Kevin ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
>https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD >-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img Works fine on a Lenovo ThinkPad x201 Fails on a Dell PowerEdge 2950 - The USB stick doen't show up in the boot menu - After fixing the partition table entries, the USB stick does show up - And then fails with 'Missing operating system' Note that after fixing the partition table entries, it still works on the ThinkPad. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 --- Comment #5 from Ka Ho Ng --- Below is one of the suspected change that causes KBI breakage, as vm_map_min/max/pmap are inline helpers before being made non-inline by https://svnweb.freebsd.org/base?view=revision&revision=332091 : https://svnweb.freebsd.org/base?view=revision&revision=328469 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
Hi. Booted as expected on ThinkPad T420. Fixed with descrete (nvidia) GPU, CPU internal GPU is disabled. Both UEFI and Legacy (CSM) boot are enabled. UEFI first : Boot on UEFI mode. [Confirmed efifb is used.] Legecy first: Boot on CSM mode. [Confirmed vt(vga) is used.] UEFI boot is much faster than legacy (CSM) boot. Is firmware version needed? On Wed, 30 May 2018 15:50:39 + Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > -- Tomoaki AOKI ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 Rodney W. Grimes changed: What|Removed |Added CC||rgri...@freebsd.org --- Comment #6 from Rodney W. Grimes --- virtual box's module is a "well known" problem with respect to ABI issues, the best way to fix this is to compile the kmod on the specific release you are running Virtual box on. This module just knows way to much about the insides of the kernel to easily maintain. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 --- Comment #7 from Eric van Gyzen --- At the very least, this needs special mention in the release notes. Maybe the release notes could suggest that users change their configuration to avoid loading these modules until their packages have been updated. Otherwise, the system could get into a panic-on-boot loop, which is...shall we say...unfriendly. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 rkober...@gmail.com changed: What|Removed |Added CC||rkober...@gmail.com --- Comment #8 from rkober...@gmail.com --- This is not something new. While I have seen the assertion that the KBI/KPI are supposed to be stable between major releases as the system ABI/API are, I am not sure that this is official policy and, even it is, it seems to be frequently ignored. In any case, it is because of this that the PORTS_MODULES variable and the support for it in makekernel came into being. If you build your own kernel, that takes care of it. If you use freebsd-update it would be a good thing if the script printed a reminder to re-build ports after an upgrade operation. It probably could use pkg to find all kmod ports installed and offer to re-build them. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 11.2-RC1 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first RC build of the 11.2-RELEASE release cycle is now available. Installation images are available for: o 11.2-RC1 amd64 GENERIC o 11.2-RC1 i386 GENERIC o 11.2-RC1 powerpc GENERIC o 11.2-RC1 powerpc64 GENERIC64 o 11.2-RC1 sparc64 GENERIC o 11.2-RC1 arm GUMSTIX o 11.2-RC1 armv6 BANANAPI o 11.2-RC1 armv6 BEAGLEBONE o 11.2-RC1 armv6 CUBIEBOARD o 11.2-RC1 armv6 CUBIEBOARD2 o 11.2-RC1 armv6 CUBOX-HUMMINGBOARD o 11.2-RC1 armv6 RPI-B o 11.2-RC1 armv6 RPI2 o 11.2-RC1 armv6 PANDABOARD o 11.2-RC1 armv6 WANDBOARD o 11.2-RC1 aarch64 GENERIC Important note: due to an issue reported and confirmed regarding the amd64 ISOs failing to boot on non-UEFI systems (legacy, CMS, BIOS), it is encouraged that the equivalent memstick installation media be used instead, while we continue to investigate the issue. UEFI-capable systems should be able to boot the ISOs, however, but please report any issues of either memstick images in both UEFI and legacy/BIOS failing to boot, or ISO images failing to boot under UEFI. Note regarding arm/armv6 images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/ftp/releases/ISO-IMAGES/11.2/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "stable/11" branch. A summary of changes since 11.2-BETA3 includes: o A fix to flush caches are before initiating a microcode update on Intel CPUs. o Wake On LAN features for Ice Lake and Cannon Lake devices has been activated. o The amd64 memstick installers have been updated to use MBR instead of GPT for better compatibility with hardware that can handle both, but do not boot in BIOS-mode (legacy mode) with a GPT partitioning scheme. Note, this does not affect the installed system, only the install media itself. o The disc1.iso has been stripped down to reduce the "Live CD" userland, allowing the media to fit onto a 700MB CD-ROM. o libxo(3) has been updated to upstream version 0.9.0. o Miscellaneous bug fixes. A list of changes since 11.1-RELEASE is available in the stable/11 release notes: https://www.freebsd.org/releases/11.2R/relnotes.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 11.2-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/11.2-RC1/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are not available for this build, and the cause is being investigated. === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-11.2-RC1 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 11.2-RC1 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdow
