From: Stefan Feilmeier <stefan@deeproot.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] hardware detection
Date: Wed, 14 Mar 2007 08:34:59 +0530 [thread overview]
Message-ID: <1173841499.5844.11.camel@stefan-nb.feilmeier> (raw)
Hello.
First of all buildroot is a really useful tool and we use it to build
the initial system for our install cd. The only problem is that I am
stuck on hardware detection. I am trying to store my kernel modules on
the cd and mount it during boot process to keep my initrd small. Modules
for the cdrom drive are compiled into the kernel. This is what I do
currently:
1. Boot initrd
2. /etc/init.d/S10udev starts udev and populates /dev
3. Mount cdrom(s) on /mnt/cdrom/
4. Mount --bind /lib/modules
Till here everything works just fine and the modules are accessible
in /lib/modules. Now I try to run `udevtrigger` but it doesn't detect my
network card. Loading the module manually with `modprobe pcnet32` works
fine. I am trying this in a VMware virtual machine.
Does anybody have a hint for me?
Regards,
Stefan
DeepRoot Linux
next reply other threads:[~2007-03-14 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 3:04 Stefan Feilmeier [this message]
2007-03-14 10:08 ` [Buildroot] hardware detection Bernhard Fischer
2007-03-14 10:25 ` Stefan Feilmeier
2007-03-14 10:35 ` Bernhard Fischer
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=1173841499.5844.11.camel@stefan-nb.feilmeier \
--to=stefan@deeproot.co.in \
--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