From: bbboson@gmail.com (madper)
To: kernelnewbies@lists.kernelnewbies.org
Subject: compile kernel 3.0.34 errors
Date: Wed, 29 Aug 2012 12:54:09 +0800 [thread overview]
Message-ID: <op.wjsc8jwvwg2gps@localhost.localdomain> (raw)
In-Reply-To: <201208291238400312993@gmail.com>
On Wed, 29 Aug 2012 12:38:43 +0800, wenrongbupt <wenrongbupt@gmail.com>
wrote:
> Hi,
> I am not find initrd in /boot, but has initramfs-3.0.34.img.
> Thank you.
>
Hi, how to creat that img? How about using mkinitcpio?
>wenrongbupt
>From: Mulyadi Santosa
> Date: 2012-08-29 11:17
> To: wenrongbupt
> CC: Anuz Pratap Singh Tomar; kernelnewbies
> Subject: Re: Re: compile kernel 3.0.34 errors
> Hi....
>On Wed, Aug 29, 2012 at 8:55 AM, wenrongbupt <wenrongbupt@gmail.com>
> wrote:
>> I follow a full steps as following:
>> make mrproper
>> make menuconfig
>> make bzImage
>> make modules
>> make modules_install
>> make install
>> It still has following errors:
>> ERROR: modinfo: could not find module twofish
>> ERROR: modinfo: could not find module i2c
>>
>> Please help me! Thank you.
>ANyway, do you see newly built initrd in /boot? I guess it should be
> like /boot/initrd-3.0.34 ...
>--regards,
>Mulyadi Santosa
> Freelance Linux trainer and consultant
>blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120829/24a14d6a/attachment-0001.html
next prev parent reply other threads:[~2012-08-29 4:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 8:08 compile kernel 3.0.34 errors wenrongbupt
2012-08-28 8:19 ` Mulyadi Santosa
2012-08-28 8:39 ` Vivek Panwar
2012-08-28 12:00 ` wenrongbupt
2012-08-28 16:47 ` Mulyadi Santosa
2012-08-29 0:48 ` wenrongbupt
2012-08-28 12:08 ` wenrongbupt
2012-08-28 16:03 ` Anuz Pratap Singh Tomar
2012-08-29 1:55 ` wenrongbupt
2012-08-29 3:17 ` Mulyadi Santosa
2012-08-29 4:38 ` wenrongbupt
2012-08-29 4:54 ` madper [this message]
2012-08-29 4:58 ` wenrongbupt
2012-09-14 10:45 ` zhaoqiao
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=op.wjsc8jwvwg2gps@localhost.localdomain \
--to=bbboson@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).