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
passthroug
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,
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
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?
> Afte
It seems that preinit is not running after the first boot. I don't know
why...
On 11 September 2015 at 00: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 d
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 bec
