Btw, I'm taking this issue quite seriously, because I really wanted to use OpenWRT in My SuperMicro motherboard. For many, using this kind of hardware with OpenWRT might be seen as overkill, but these are my reasons: - This motherboard uses an Atom CPU which does not support VT-d, so PCI passthrough is not available. - I tried to virtualize pfSense using KVM. Although I succeeded, I quickly ran into issues with virtio interfaces. I game up when the pfSense file system got corrupted after 2 hard resets. - Although pfSense is a incredible project and a quite good firewall, it is limited to that. I'm unable to develop my own software to use with it.
Using OpenWRT seens to me, to be the better option. Everything I need is there, hardware support, software, LXC. IMHO, OpenWRT is more than a distribution just for wireless embedded devices, it is also a good option for a high performance home/office Router/Server all-in-one solution. Because of this, I'm inclined to (try) to contribute with a target, specifically for this supermicro motherboard, since it is basically, a big SBC. Can anyone provide me with some insight and directions in how to contribute with a new specific target for OpenWRT? On 13 September 2015 at 14:48, John Crispin <[email protected]> wrote: > good decision let us know if you run into issues. one change at a time > is always best in these cases and tend to cost less time to get the > final result. > > > > On 13/09/2015 15:14, Carlos Ferreira wrote: > > It seems that I'm unable to understand what really happened. > > I decided to start all over again, and instead of adding a lot of > > features to the kernel and test them, I decided to start with a default > > kernel and add features one by one, testing them along the way. > > Since the Chaos Calmer is now out, I will use it instead of using the > trunk. > > > > > > > > On 11 September 2015 at 11:02, Carlos Ferreira <[email protected] > > <mailto:[email protected]>> wrote: > > > > I didn't. I copied the config value so that who read the mail, could > > understand imediatly what I was talking about. > > > > I'm unable to see if the default config works, because after > > booting, I'm unable to use the USB keyboard. I solved it by adding > > usb-pci support and a bunch of keyboard optionn. I was unsure which > > one exactly should be activated, so everything that was related with > > USB + Keyboard, I activated. > > > > The hardware target to where I'm building OpenWRT is a Supermicro > > A1SAi-2750F server board > > < > http://www.supermicro.com/products/motherboard/Atom/X10/A1SAi-2750F.cfm>. > > > > I will send in annex, the configuration files. > > > > > > > > > > On 11 September 2015 at 06:54, John Crispin <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > > > On 11/09/2015 01:53, Carlos Ferreira wrote: > > > I have a custom build for x86_64 where CONFIG_PROC_FS is > active (y) at > > > the kernel configuration. /etc/fstabs has nothing and is > pointing into > > > an empty /tmp directory. > > > > > > Is there any reason that might prevent the /proc from being > mounted? > > > After booting for the first time, /proc is not mounted and > because of > > > that, I'm unable to use 'top' or 'ps' to list the active > processes. > > > > > > I have been banging my head into the wall for the last day, > unable to > > > understand what is going on. > > > > > > procfs is enabled by default. i am not sure why you had to > > enable it by > > hand. does the default configuration work for you ? what other > > changes > > did you make to your tree ? > > > > John > > > > > > > > > > Has anyone had the same issue before? > > > -- > > > > > > Carlos Miguel Ferreira > > > Researcher at Telecommunications Institute > > > Aveiro - Portugal > > > Work E-mail - [email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>> > > > Skype & GTalk -> carlosmf.pt <http://carlosmf.pt> > > <http://carlosmf.pt>@gmail.com <http://gmail.com> > > > <http://gmail.com> > > > LinkedIn -> http://www.linkedin.com/in/carlosmferreira > > > > > > > > > _______________________________________________ > > > openwrt-devel mailing list > > > [email protected] > > <mailto:[email protected]> > > > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > > _______________________________________________ > > openwrt-devel mailing list > > [email protected] > > <mailto:[email protected]> > > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > > > > > > > -- > > > > Carlos Miguel Ferreira > > Researcher at Telecommunications Institute > > Aveiro - Portugal > > Work E-mail - [email protected] <mailto:[email protected]> > > Skype & GTalk -> carlosmf.pt <http://carlosmf.pt>@gmail.com > > <http://gmail.com> > > LinkedIn -> http://www.linkedin.com/in/carlosmferreira > > > > > > > > > > -- > > > > Carlos Miguel Ferreira > > Researcher at Telecommunications Institute > > Aveiro - Portugal > > Work E-mail - [email protected] <mailto:[email protected]> > > Skype & GTalk -> carlosmf.pt <http://carlosmf.pt>@gmail.com > > <http://gmail.com> > > LinkedIn -> http://www.linkedin.com/in/carlosmferreira > -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - [email protected] Skype & GTalk -> [email protected] LinkedIn -> http://www.linkedin.com/in/carlosmferreira
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
