Pfsense 1.2.1-RC2 and vge driver problem.
-
Hi,
I have an epia en12000eg fanless itx that I want to turn into to a pfsense box. It only has 1 RJ45 port onboard so my second nic is a box standard 10/100/1000 PCI card purchased from a local electronics shop. Unfortunately i seem to have encountered a problem with the onboard device. Its a VIA Networking Gigabit Ethernet device and the O/S does not seem to want to play ball with this at all. I get the following information from dmesg about the card.
vge0: <via networking="" gigabit="" ethernet="">vge0: MII read timed out
vge0: failed to start MII autopoll
vge0: MII without any phy!
device_attach: vge0 attach returned 6I've googled around trying to find resolutions to this but its all VERY vague and the only pfsense reference says its a FreeBSD issue. Some sites suggest changing the rc.conf file for ifconfig_vge0 but I'm unsure as to if this is a valid solution as they a seem more geared to FreeBSD as a desktop environment and not a pfsense environment.
I could really do with some help here, is the vge driver supported fully? Does anyone know if a previous version of pfsense works with it ok?
Thanks in advance.</via>
-
I would try pfSense 2.0 if it still doesn't work. Then install FreeBSD so you can report the error to them.
-
I would try pfSense 2.0 if it still doesn't work. Then install FreeBSD so you can report the error to them.
Thanks for the reply.
I'd already tried upgrading rc2 to the latest alpha alpha of 2.0 and that made no difference. I'm unsure if the alpha upgrades actually change the kernel etc as I think the problem comes from the driver which I believe is compiled into the kernel as it doesn't look like its a loaded module.
Thankfully I already have a fully working PF that lives in a virtual but I really want to move away from that and onto the hardware directly. Unforutnately I'd say i've installed pfsense to hardware 1 out of 3 times. FreeBSD just doesn't seem to like my EPIA kit :(.
-
Send an email with the output you pasted here and the output of a pciconf -lv and send it to freebsd-net@freebsd.org plus freebsd-stable@freebsd.org so the driver author can give you a propper answer.
Usually it is an id issue which is a simple adding the id to the driver and recompile but better confirm with the driver author.