Solved Very Slow Legacy Boot w/10.2 and UEFI

jasonvp

jasonvp

Hey folks -

If I put this in the wrong part of the forum, I apologize; please feel free to move it. I've been trying to get 10.2 installed on my new Gigabyte GA-H170N motherboard that has AMI's UEFI on it. The 10.2 EFI memstick installer page faults as the kernel boots, every single time, in the same spot. It's a bug in the code. I tried the latest 11.0 snapshot and it boots (and installs) just fine. But 11.0 leaves me with no package repositories, etc, so I'm not going to use it. This is for a router, BTW, so bleeding edge is no bueno.

Anyway, I've also managed to successfully boot and install 10.2 on the machine using the non-EFI memstick image. The problem: the boot time. It literally takes more than 5 minutes to load the kernel. The little twirly stick turns so slow it looks like it's pausing between each tick. This happens both with the installer image and once FreeBSD is installed on the disk.

While I don't intend to reboot my router often, I can't have it take 5-10 minuted to reboot. That's highly unacceptable. Any ideas of what I can do to either A)speed up the non-EFI image, or B)fix the EFI image so that it boots without page faulting?

Thanks.
 
jasonvp said:
This is for a router, BTW, so bleeding edge is no bueno.
Click to expand...
The FreeBSD cluster machines mostly run -CURRENT. I'd have no problems using it for a router. A router will not have much installed, so either build from ports or set up your own package repository with poudriere.
 
jasonvp said:
This is for a router, BTW, so bleeding edge is no bueno.
Click to expand...

Just be aware that while 10-STABLE is more "stable" than -CURRENT, it's still rolling-release by nature. Any time you perform a security or bug-fix update by updating the source tree you'll be getting the security/bug patches, plus all the changes that have been committed to the -STABLE source branch since your last update, and code gets committed every day. I ran 10-STABLE between 10.1 and 10.2 with only one minor setback, so you'll probably be fine, but just know that there's a slightly higher maintenance burden involved. You'll want to pay some attention to freebsd-announce@freebsd.org, freebsd-stable@freebsd.org and svn-src-stable-10@freebsd.org, and if you don't want all the updates involved you'll need to manually apply the patches sent out with security/bug announcements to your local source tree.
 
You must log in or register to reply here.
Back
Top