From: Andreas Ziegler <br015@umbiko.net>
To: buildroot@busybox.net
Subject: [Buildroot] enc28j60 ethernet module doesn't work on rpi0
Date: Fri, 27 Apr 2018 09:59:01 +0200 [thread overview]
Message-ID: <0fa76360ff8efd2158cac7f627b5406f@umbiko.net> (raw)
In-Reply-To: <mailman.21.1524657611.10868.buildroot@busybox.net>
Hi Jacek,
> Date: Tue, 24 Apr 2018 19:19:41 +0000
> From: Jacek Drewniak <yahuza.pl@gmail.com>
> To: buildroot at busybox.net
> Subject: Re: [Buildroot] enc28j60 ethernet module doesn't work on rpi0
> It seems that problem is with loading modules at all. Now after
> `Starting
> mdev...` I can see that others modules loaded: gpiomem, watchdog.
This may be related to your init system. Probably mdev was not started
previously or did not pick up kernel events. Check if mdev is
initialized somewhere during system initialization. For example, if you
use busybox, there should be a /etc/init.d/S10mdev script. Also mdev
needs a line for modprobe in /etc/mdev.conf. This config item is present
in the current buildroot configuration, but was missing before 2016.
>> - I can modprobe enc28j60.ko and it appears in lsmod but nothing else
>> happens (no eth0 in ifconfig)
If you start the interface manually after loading the driver using 'ifup
eth0', it should be visible.
Kind regards,
Andreas
next parent reply other threads:[~2018-04-27 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.21.1524657611.10868.buildroot@busybox.net>
2018-04-27 7:59 ` Andreas Ziegler [this message]
2018-04-24 12:31 [Buildroot] enc28j60 ethernet module doesn't work on rpi0 Jacek Drewniak
2018-04-24 19:19 ` Jacek Drewniak
2018-04-26 18:38 ` Jacek Drewniak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fa76360ff8efd2158cac7f627b5406f@umbiko.net \
--to=br015@umbiko.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.