I cannot seem to get WOL working with FreeBSD on my server based on a ASRock B250M Pro4 board. In the UEFI Chip Set Configuration of the board, I enabled PCIe/PCI Devices Power On.
Actually, when I start the system into the UEFI settings, and then by using the power button directly switch it...
Freshly installed FreeBSD 11 Release on my Lenovo W520 with UEFI and VT. When I boot from FreeBSD ISO DVD, UEFI only and VT, everything looks normal, after installation completed and reboot the system here what the output looks like (please look at the attached file).
Just a quick test; I booted FreeBSD 11.1-RC3 (amd64) off a usb memory stick on this machine. After the kernel loads, console output is corrupted (graphics corruption), Ctrl-Alt-Del works, so presumably the keyboard works. To work around the console problem, escape to the boot loader prompt and...
I've been using FreeBSD 9 on a fairly old computer based on Intel® DG45FC motherboard, with a Celeron 64bit CPU. After 3 years lying there gathering dust, I've decided to repurpose it and run the latest release.
So far, I've been unsuccessful at booting FreeBSD 10.3/11.0-RELEASE (AMD64)...
I have exactly the same problem, which is also described in this thread.
However, the solution does not work for me.
Before the beastie menu, the boot loader asks for the password.
No matter what I enter there, the boot process continues.
Later, when the root system is to be mounted...
I have read about a Apple Mac EFI rootkit by a certain government agency.
I always knew in my heart that EFI was evil.
Does your computer boot faster with EFI?
What features from the EFI list above do you need and use?
As my kernel messages were scrolling through I suddenly get this scrolling through endlessly:
vm_fault: pager read error, pid 1 (init)
If I look quick enough, it seems to happen at the very end of the boot-up.
For what its worth, I am doing this very odd remote dual-boot setup where I change...
I've been trying to put FreeBSD on my laptop (Dell XPS15, l502x). Previously, the memory stick worked (10.1 works), but on FreeBSD 10.3 and 11.0 (I haven't tried 10.2), boot fails with an "Operating system not found" message on screen. My laptop uses the traditional BIOS and UEFI
I have a...
Hello FreeBSD community
I am having problems booting from USB after writing the FreeBSD 11.0 image to a USB drive, although I have had the same issue when trying the UEFI-memstick image of FreeBSD 10.3. I used the command from the install guide with the filename changed to reflect the new...
I am trying to install FreeBSD 11.0-RELEASE on the GELI encrypted ZFS pool without /boot on a separate unencrypted partition.
I tried this on real hardware (ThinkPad T420s laptop) and under VirtualBox (both with UEFI) without luck.
These are the steps which I tried:
# boot FreeBSD...
Ever since I upgraded from 10.2 to 10.3, sometimes the boot process gets stuck after beastie menu, and sometimes not. I didn't have any problems before. If it's in any way relevant, I had originally installed 10.1 (the 1st one to support UEFI boot) on this machine, which then I upgraded to 10.2...
I've done following:
Changed BIOS settings to boot UEFI. Installed 10.3-RELEASE UEFI (no customization). Set up sshd, verified, logged in from my laptop (over LAN). Restarted to see if all works fine. It did. Until I put my monitor back in the closet.
I don't have any idea what has...
I can not get the UEFI freebsd loader to finish loading the kernel -- on my other systems (macbook pro, Z87 Desktop) the install goes perfect. But on my Z77 desktop it gets to the framebuffer section and stalls (it appears it cannot switch to the proper mode)
how do I get around this ?
I am in the process of migrating to UEFI on my laptop. I would like /boot to be on a separate partition in order to have / on GELI, but I cannot get the UEFI bootloader to play along.
It finds both my mirrored /boot UFS partitions just fine, but refuses to continue because /boot/loader.efi does...
Do we have a tool / tools to read (U)EFI variables under FreeBSD?
So far, the only thing I can find is that uefi says that
which is ok. Still, it would be nice to at least be able to read those variables without having to boot into another operating system.