kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: wenrongbupt@gmail.com (wenrongbupt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: compile kernel 3.0.34 errors
Date: Wed, 29 Aug 2012 08:48:56 +0800	[thread overview]
Message-ID: <201208290848515008330@gmail.com> (raw)
In-Reply-To: CAGdaadbgFtKArpYRvgx9Tf2uOFCDv5FerZbo7dwWwVk+K=i-DA@mail.gmail.com

I follow your steps,but it still has errors.

ERROR: modinfo: could not find module bluetooth
ERROR: modinfo: could not find module rfkill
ERROR: modinfo: could not find module authenc
ERROR: modinfo: could not find module esp4
ERROR: modinfo: could not find module xfrm4_mode_tunnel
ERROR: modinfo: could not find module deflate
ERROR: modinfo: could not find module zlib_deflate
ERROR: modinfo: could not find module ctr
ERROR: modinfo: could not find module twofish
ERROR: modinfo: could not find module twofish_common
ERROR: modinfo: could not find module camellia
ERROR: modinfo: could not find module serpent
ERROR: modinfo: could not find module blowfish
ERROR: modinfo: could not find module cast5
ERROR: modinfo: could not find module des_generic
ERROR: modinfo: could not find module cbc
ERROR: modinfo: could not find module aes_i586
ERROR: modinfo: could not find module aes_generic
ERROR: modinfo: could not find module xcbc
ERROR: modinfo: could not find module rmd160
ERROR: modinfo: could not find module sha512_generic
ERROR: modinfo: could not find module sha256_generic
ERROR: modinfo: could not find module crypto_null
ERROR: modinfo: could not find module af_key
ERROR: modinfo: could not find module ppdev
ERROR: modinfo: could not find module parport_pc
ERROR: modinfo: could not find module lp
ERROR: modinfo: could not find module parport
ERROR: modinfo: could not find module nfsd
ERROR: modinfo: could not find module lockd
ERROR: modinfo: could not find module nfs_acl
ERROR: modinfo: could not find module auth_rpcgss
ERROR: modinfo: could not find module exportfs
ERROR: modinfo: could not find module fuse
ERROR: modinfo: could not find module sunrpc
ERROR: modinfo: could not find module ipv6
ERROR: modinfo: could not find module uinput
ERROR: modinfo: could not find module snd_hda_codec_realtek
ERROR: modinfo: could not find module snd_hda_intel
ERROR: modinfo: could not find module iTCO_wdt
ERROR: modinfo: could not find module snd_hda_codec
ERROR: modinfo: could not find module iTCO_vendor_support
ERROR: modinfo: could not find module snd_hwdep
ERROR: modinfo: could not find module broadcom
ERROR: modinfo: could not find module snd_seq
ERROR: modinfo: could not find module i2c_i801
ERROR: modinfo: could not find module r8169
ERROR: modinfo: could not find module snd_seq_device
ERROR: modinfo: could not find module mii
ERROR: modinfo: could not find module snd_pcm
ERROR: modinfo: could not find module snd_timer
ERROR: modinfo: could not find module snd
ERROR: modinfo: could not find module soundcore
ERROR: modinfo: could not find module snd_page_alloc
ERROR: modinfo: could not find module serio_raw
ERROR: modinfo: could not find module tg3
ERROR: modinfo: could not find module microcode
ERROR: modinfo: could not find module dcdbas
ERROR: modinfo: could not find module i915
ERROR: modinfo: could not find module drm_kms_helper
ERROR: modinfo: could not find module drm
ERROR: modinfo: could not find module i2c_algo_bit
ERROR: modinfo: could not find module i2c_core
ERROR: modinfo: could not find module video
ERROR: modinfo: could not find module output



wenrongbupt

From: Mulyadi Santosa
Date: 2012-08-29 00:47
To: wenrongbupt
CC: Vivek Panwar; kernelnewbies
Subject: Re: Re: compile kernel 3.0.34 errors
On Tue, Aug 28, 2012 at 7:00 PM, wenrongbupt <wenrongbupt@gmail.com> wrote:
> I follow your procedure,the build result as following:
> It seems there are more modules could not find now.
>
> ERROR: modinfo: could not find module bluetooth
> ERROR: modinfo: could not find module rfkill
> ERROR: modinfo: could not find module authenc
> ERROR: modinfo: could not find module esp4
> ERROR: modinfo: could not find module xfrm4_mode_tunnel
> ERROR: modinfo: could not find module deflate

I have a good guess that somehow you accidentally or inaccidentally
use your distro default kernel config.

So, what you might need to do before make mrproper is probably
temporarily move every config file in /boot to somewhere else, say
/tmp:
mv /boot/config-* /tmp

then use casual mantra....

let's see if that helps...




-- 
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/d14b959c/attachment.html 

  reply	other threads:[~2012-08-29  0:48 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 [this message]
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
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=201208290848515008330@gmail.com \
    --to=wenrongbupt@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).