Date: Sun, 6 Jan 2013 09:29:12 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Matthew Seaman <matthew@FreeBSD.org> Cc: jb <jb.1234abcd@gmail.com>, freebsd-questions@freebsd.org Subject: Re: FB 9.1 boot loader problem in VirtualBox Message-ID: <alpine.BSF.2.00.1301060924190.22269@wonkity.com> In-Reply-To: <50E963CD.3030709@FreeBSD.org> References: <loom.20130106T005723-617@post.gmane.org> <loom.20130106T121300-657@post.gmane.org> <50E963CD.3030709@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Jan 2013, Matthew Seaman wrote: > On 06/01/2013 11:19, jb wrote: >> Next problem: >> the installation's dmesg shows net driver em0, which is Intel PRO/1000 - and >> this is how install offers to configure the network; >> but my host has Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI >> Express, which is bge0 driver in FB. >> How to force it to discover the right net device during install, and/or after >> install ? > > This is normal for VirtualBox -- it doesn't matter what NIC the host > has, VB always presents it as an em(4) interface to the guest. Under Network/Adapter1/Advanced, there are other choices for the emulated adapter type. Intel PRO/1000 MT Desktop (82540EM) is the default, and usually a good choice. The first choice is PCnet-PCI II (Am79C970A), and that one works with FreeBSD also. That first one is capable of PXE-booting in bridged mode, where the emulated Intel cards are not.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301060924190.22269>