What files need to be edited and how to enable regular console on nanoBSD?
-
The subject says it all: I have a CF card with the nanoBSD image on it. Now I want to alter the configuration such that it uses a regular instead of a serial console, such that I can set up the device…
Also, do the configuration files in question allow for commenting lines out?
-
It can't be done on a stock NanoBSD install. It doesn't have VGA or keyboard support in the kernel.
There are some builds with VGA enabled floating around, but it isn't something you can convert manually without a new image.
-
It can't be done on a stock NanoBSD install. It doesn't have VGA or keyboard support in the kernel.
There are some builds with VGA enabled floating around, but it isn't something you can convert manually without a new image.
Bummer. I wish that were something that were at least in the kernel and settable by options.
Seeing that's not in the cards, how do I enable the em-type Ethernet drivers and get a WAN interface set up, such that I can get in with ssh and/or the web interface?
I can probably figure it out by looking at my regular install, once I know where to look for these things.
-
You'd have to edit the config.xml that's on the card from another BSD machine (pfSense install, freebsd install, etc)
Or see if anyone has a VGA-enabled 1.2.3 nanobsd image out there (I think there are some on the Hacom site)
-
You'd have to edit the config.xml that's on the card from another BSD machine (pfSense install, freebsd install, etc)
Or see if anyone has a VGA-enabled 1.2.3 nanobsd image out there (I think there are some on the Hacom site)
I'll have to check out the config.xml, because I'm going with the 2.0 version of pfSense anyway…
-
So, I edited the config.xml on the file system with the restored nano image on it.
This should indicate that the image restore worked (heck, I can mount the file system).
But then the unit is supposed to boot from that CF card, it never shows up on the LAN/WAN.In essence, what I did was take the config.xml from a working installation, removed the installed packages (because there are none installed on the nano system), and saved the file to /conf/config.xml on the nano file system.
Is there some magic file I need to touch such that it knows that it's supposed to be configured, and doesn't try to wait for me to configure the system from the serial port?
Or is/are there some additional file(s) I need to edit/create, e.g. to make sure the drivers for the em NIC are loaded? -
Try these guys.
Cheers.
-
Try these guys.
Cheers.
Thanks for the pointer. I assume you suggest to use these images, and then, after successful configuration, upgrading to pfSense 2.0 ?
Also, you suggest these images because they have built-in VGA support, yes?
Thanks!
-
Also, you suggest these images because they have built-in VGA support, yes?
Yes.
They have modified 2.0rc1 images also. Here:
http://support.hacom.net/pub/index.php?dir=pfsense%2FSteve
-
Wonderful!
Not that it really matters, because once the system is set up, I won't be able to use the VGA anymore anyway, but is that a function that then is retained after an on-line OS update, or does it revert to the standard behavior after an update?
In any case, these images sound like they'll be the ticket. I'll try them when I'm back on that project!
-
I'm not sure. I haven't tried any of these images myself. I don't know how much they have changed.
Given that they have their own upgrade files I would think that you need to use those if you want to retain VGA console.
Let us know how it goes. :)
Steve
