The compile finished with no apparent errors.
When I ran 'make xconfig' I selected 'm' for ne2000 support so that it would
create a module.
I used the find command to search in /home/cs/redhat for ne.ko and it was not
found.
I greped the .config file for the relevant lines:
The command I used and the output are as follows:
grep ISA /home/cs/redhat/SOURCES/kernel-2.6.18-`uname -m`.config | grep -v
HISAX | grep -yv disable
CONFIG_GENERIC_ISA_DMA=y
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_ISAPNP is not set
CONFIG_NET_ISA=y
# Wireless 802.11b ISA/PCI cards support
# CONFIG_ISDN_DRV_AVMB1_B1ISA is not set
# CONFIG_ISDN_DRV_AVMB1_T1ISA is not set
# ISA-based Watchdog Cards
CONFIG_I2C_ISA=m
# CONFIG_I2C_PCA_ISA is not set
# ISA devices
I also greped for NE2000 in the same file:
CONFIG_NE2000=m
I am 99% sure that I entered 'y' for ISAPNP and ISA support and 'm' for
ne2000.
The above shows that ISAPNP is not set. In my research I read that it should
be selected. Does it need to be?
I am more than willing to recompile again and double check the settings after
I have run 'make xconfig'.
But before doing that, is there a way to limit which kernels in the i686
group are compiled? If it can be limited to one (ie. exclude xen, PAE etc.),
then the compile will not take nearly as long.
Thanks,
David
On Monday 21 May 2007 1:42 pm, Akemi Yagi wrote:
> On 5/21/07, Akemi Yagi <amyagi@xxxxxxxxx> wrote:
> > On 5/21/07, dcw <dwoody1@xxxxxxxxxxx> wrote:
> > > When I use the i386 the compile continues.
> > > However, I had to edit the SOURCE config file after running make
> > > xconfig. That command altered the first line of the config file.
> >
> > Yes, I was about to say the same thing. In fact, the arch name (i386)
> > gets deleted twice. First, when rpmbuild -bp is run. But this is not
> > a problem by itself, because in the next step .config is copied from
> > SOURCE which has the correct first line. Then the second time is when
> > make menuconfig (or xconfig) is run as you noted. This is the
> > problem. At this point, arch needs to be added back manually to
> > .config as just you did.
> >
> > I really want to why menuconfig does not do it right.
>
> I have done a bit of a search regarding this issue. Turns out the
> same problem was reported as early as Feb 2005 on a Fedora list. So
> this is not something new, nor CentOS specific. Bad news is that I
> have yet to find an answer for this. The only thing I saw in the
> search was the same manual editing of .config as we already did as a
> temporary solution.
>
> http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-05/0405.html
>
> I am still trying to figure out why rpmbuild -bp messes up the first
> line of .config. And of course this problem never surfaces if you run
> rpmbuild -ba in the beginning because the incorrect version of .config
> is created but *not* used in this operation.
>
> Akemi
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
--
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
