From: pritambankar1988@gmail.com (Pritam Bankar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: building linux kernel 3.0.4
Date: Tue, 08 Nov 2011 00:34:32 +0530 [thread overview]
Message-ID: <4EB82BC0.1080809@gmail.com> (raw)
In-Reply-To: <CAFC7R0cPJx7RP5==3bsy58JfHUhiTcN7_u3rQ1_DqtbjPzhcaw@mail.gmail.com>
On 07-11-2011 23:15, ashish anand wrote:
> Hi ,
> I am using vmware on windows 7 and try to built kernel version 3.0.4 .
> I am following this procedure
>
> make defconfig
> make
> make modules
> make modules_install
> make install
> Every step succeds except make install
> Its throwing me following message
>
> *sh /home/ashu/linux-3.0.4/linux-3.0.4/arch/x86/boot/install.sh 3.0.4
> arch/x86/boot/bzImage \
> System.map "/boot"
> ERROR: modinfo: could not find module fuse
> ERROR: modinfo: could not find module sunrpc
> ERROR: modinfo: could not find module ip6t_REJECT
> ERROR: modinfo: could not find module nf_conntrack_ipv6
> ERROR: modinfo: could not find module ip6table_filter
> ERROR: modinfo: could not find module ip6_tables
> ERROR: modinfo: could not find module ipv6
> ERROR: modinfo: could not find module uinput
> ERROR: modinfo: could not find module snd_ens1371
> ERROR: modinfo: could not find module gameport
> ERROR: modinfo: could not find module snd_rawmidi
> ERROR: modinfo: could not find module snd_ac97_codec
> ERROR: modinfo: could not find module ac97_bus
> ERROR: modinfo: could not find module snd_seq
> ERROR: modinfo: could not find module snd_seq_device
> ERROR: modinfo: could not find module snd_pcm
> ERROR: modinfo: could not find module ppdev
> ERROR: modinfo: could not find module snd_timer
> ERROR: modinfo: could not find module parport_pc
> ERROR: modinfo: could not find module snd
> ERROR: modinfo: could not find module parport
> ERROR: modinfo: could not find module microcode
> ERROR: modinfo: could not find module soundcore
> ERROR: modinfo: could not find module vmware_balloon
> ERROR: modinfo: could not find module snd_page_alloc
> ERROR: modinfo: could not find module pcnet32
> ERROR: modinfo: could not find module mii
> ERROR: modinfo: could not find module i2c_piix4
> ERROR: modinfo: could not find module i2c_core
> ERROR: modinfo: could not find module mptspi
> ERROR: modinfo: could not find module mptscsih
> ERROR: modinfo: could not find module mptbase
> ERROR: modinfo: could not find module scsi_transport_spi
>
> *I wonder if my Vmware workstation is creating a problem?
>
> Or
> If I am using make defconfig why are these modules not bulit.
> Please help I am stuck.
>
> Thanks and Regards
> Ashish Anand
> "Growth Should Not Kill Innovation"
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
make defconfig takes default options present in config file of
particular architecture say x86_64 which is present in source code. Out
of these modules you might not be needing all. So try using make oldconfig.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111108/e9a01394/attachment.html
next prev parent reply other threads:[~2011-11-07 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 17:45 building linux kernel 3.0.4 ashish anand
2011-11-07 19:04 ` Pritam Bankar [this message]
2011-11-08 13:49 ` Pritam Bankar
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=4EB82BC0.1080809@gmail.com \
--to=pritambankar1988@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 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.