[OpenWrt-Devel] x86-64: /proc is not being mounted

Carlos Ferreira carlosmf.pt at gmail.com
Sun Sep 13 09:14:36 EDT 2015


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 <carlosmf.pt at gmail.com>
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 <blogic at openwrt.org> 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 - cmf at av.it.pt <mailto:cmf at av.it.pt>
>> > Skype & GTalk -> carlosmf.pt <http://carlosmf.pt>@gmail.com
>> > <http://gmail.com>
>> > LinkedIn -> http://www.linkedin.com/in/carlosmferreira
>> >
>> >
>> > _______________________________________________
>> > openwrt-devel mailing list
>> > openwrt-devel at lists.openwrt.org
>> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>> >
>> _______________________________________________
>> openwrt-devel mailing list
>> openwrt-devel at lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>
>
>
> --
>
> Carlos Miguel Ferreira
> Researcher at Telecommunications Institute
> Aveiro - Portugal
> Work E-mail - cmf at av.it.pt
> Skype & GTalk -> carlosmf.pt at gmail.com
> LinkedIn -> http://www.linkedin.com/in/carlosmferreira
>



-- 

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - cmf at av.it.pt
Skype & GTalk -> carlosmf.pt at gmail.com
LinkedIn -> http://www.linkedin.com/in/carlosmferreira
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20150913/1477486e/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list