I am installing the 3.0 bf2.4 on a Dell GX260 which has the Pro/1000 MT NIC.

The e1000 driver ( for the Pro/1000 family) is not part of the bf2.4 kernel, so I have downloaded from Intel and want to compile. Next step is to get gcc.

This is the part I need some input on:

I downloaded the following debs from stable:

binutils_2.12.90.0.1-4_i386.deb
cpp-3.0_3.0.4-7_i386.deb
gcc-3.0_3.0.4-7_i386.deb
gcc-3.0-base_3.0.4-7_i386.deb
libgcc1_3.0.4-7_i386.deb

and installed them with

dpkg --install ( all installed fine )

Could some body help me get this right, basically doing what apt does manually.

I got some errors like missing crt10.o in compiling a simple helloworld program.

I have got a system with basedebs.tar installed. If I can get my NIC working with a e1000.o and some config, I can move towards a more usable system.

Thanks!

Biren

Hi,
I am not at all sure that this is correct,but I think you would have better luck with the 2.95 version compilers. I believe this would include:
cpp
cpp-2.95
gcc
gcc-2.95
g++
g++-2.95
libstdc++2.10

I am sure that you have reasons for choosing the bf2.4 flavor to install, but I think one of the others might include built-in support for your card. This might make installation easier.

>> .. reasons for choosing the bf2.4 flavor to install

Yes -- basically Intel is supporting the 2.4 kernel more than 2.2 ( my impression ) and past this NIC I will have similar struggles with an Intel 82845G/GL Graphics Controller.

By the way, after what I installed, there was a gcc-3.0 compiler in /usr/bin which compiled the driver OK:

gcc-3.0 -DLINUX -D__KERNEL__ -DMODULE -O2 -pipe -Wall -I/usr/src/kernel-headers-2.4.18-bf2.4/include -I. -DMODVERSIONS -DEXPORT_SYMTAB -include /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/modversions.h -c -o e1000_main.o e1000_main.c
gcc-3.0 -DLINUX -D__KERNEL__ -DMODULE -O2 -pipe -Wall -I/usr/src/kernel-headers-2.4.18-bf2.4/include -I. -DMODVERSIONS -DEXPORT_SYMTAB -include /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/modversions.h -c -o e1000_hw.o e1000_hw.c
gcc-3.0 -DLINUX -D__KERNEL__ -DMODULE -O2 -pipe -Wall -I/usr/src/kernel-headers-2.4.18-bf2.4/include -I. -DMODVERSIONS -DEXPORT_SYMTAB -include /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/modversions.h -c -o e1000_param.o e1000_param.c
gcc-3.0 -DLINUX -D__KERNEL__ -DMODULE -O2 -pipe -Wall -I/usr/src/kernel-headers-2.4.18-bf2.4/include -I. -DMODVERSIONS -DEXPORT_SYMTAB -include /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/modversions.h -c -o e1000_ethtool.o e1000_ethtool.c
gcc-3.0 -DLINUX -D__KERNEL__ -DMODULE -O2 -pipe -Wall -I/usr/src/kernel-headers-2.4.18-bf2.4/include -I. -DMODVERSIONS -DEXPORT_SYMTAB -include /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/modversions.h -c -o kcompat.o kcompat.c


**************************************************
** e1000.o built for 2.4.18-bf2.4
** SMP Disabled
**************************************************

gzip -c ../e1000.7 > e1000.7.gz
# remove all old versions of the driver
find /lib/modules/2.4.18-bf2.4 -name e1000.o -exec rm {} \; \
|| true
install -D -m 644 e1000.o /lib/modules/2.4.18-bf2.4/kernel/drivers/net/e1000.o
/sbin/depmod -a || true
install -D -m 644 e1000.7.gz /usr/share/man/man7/e1000.7.gz
man -c -P'cat > /dev/null' e1000 || true

Then

insmod e1000

worked fine but, next step

ifconfig eth0 144.25.166.4 netmask 255.255.252.0 up

gave a segmentation fault. Pursuing with Intel support, but do look forward to any comments or other experience.

Thanks again for your help.

I was no help at all.
Will go stick my tongue in a light socket now.

Hi dowmun,

Actually your analysis and suggestion was spot on! I guess I was thinking that gcc-3.0 should be better than gcc-2.95.4 -- but this is not right.

I received also a communication from Matt Domsch who is with Dell ( my PC brand ) that I need to compile the module and the kernel with the same version of the compiler. The reason for this turns out to be the need to maintain the same ABI -- Applications Binary Interface. I don't know much about the details of this other than conventions in laying out the module image etc. I imagine.

Anyway, when I followed your and Matts suggestion, not only did the module compile, it also configured just fine with ifconfig!

Thank you very much!