From: Heiko Helmle <helman@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Problems with udev buildroot
Date: Mon, 08 Aug 2011 21:15:21 +0200 [thread overview]
Message-ID: <20110808191521.304570@gmx.net> (raw)
Hello List,
I'm a bit new and I'm trying to build a small x86 buildroot with udev.
So far I just enabled building a pretty default .config (just enabled a kernel with i386 defconfig and set udev for /dev management).
Unfortunately on 2011.8rc1 and the latest git this doesn't work right:
---
unable to access '/sys//devices/platform/i8042/serio1/input/input2
/sbin/modprobe: invalid option -- b
--
then comes the busybox help for modprobe
--
unable to access 'sys//devices/platform/i8042/serio1/input/input2/mouse0
unable to access 'sys//devices/platform/i8042/serio1/input/input2/event2
can't open /dev/tty1: No such file or directory
can't open /dev/tty1: No such file or directory
next reply other threads:[~2011-08-08 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 19:15 Heiko Helmle [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-08 19:18 [Buildroot] Problems with udev buildroot Heiko Helmle
2011-08-08 19:43 ` Peter Korsgaard
2011-08-08 20:07 Heiko Helmle
2011-08-08 20:56 ` Heiko Helmle
2011-08-09 6:31 ` Peter Korsgaard
2011-08-09 20:52 ` Heiko Helmle
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=20110808191521.304570@gmx.net \
--to=helman@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox