Hello
community,
I have problems with the compilation of the kernel if compiling Xen from the
current tarballs / even if I trz to download http://bits.xensource.com/oss-xen/release/3.4.2/xen-3.4.2.tar.gz
which then takes the sources of the kernel from mercurial repositorz or I
download directly http://bits.xensource.com/oss-xen/release/3.4.2/linux-2.6.18-xen-3.4.2.tar.gz
and compile it, everything goes in a good way, butit never compiles and links
the file
drivers/net/tg3.c
All other
drivers in the same directory are compiled normally, but even if I select in
make menuconfig the given driver to be compiled into the kernel or not, it
never gets compiled, the file tg3.ko is never created. It creates the tg3.o
file, but nothing more.
I made
following steps:
1.
downlaoded the tarball http://bits.xensource.com/oss-xen/release/3.4.2/linux-2.6.18-xen-3.4.2.tar.gz
and unpacked to the directory /root/Work/XenLinux
2. I
created new empty directory /root/Work/XenLinux/kernelout and switched to the
directory /root/Work/XenLinux/linux-2.6.18-xen-3.4.2
3. I
started
make
O=/root/Work/XenLinux/kernelout/ menuconfig
and
selected the Tigon3 to be installed into the kernel (under devices –
network – ethernet 1000), saved the config
4. I
started
make
O=/root/Work/XenLinux/kernelout/
and the
kernel files have been compiled, but in the result is no tg3.ko file on the
expected place, only the tg3.o is created in
/root/Work/XenLinux/kernelout/drivers/net, but nothing else. Also no tg3.mod.o
or tg3.mod.c what would be analogous and is generated to all other *.o files in
the same directory have been generated.
If I then
prepare (install) the kernel and ramdisk etc. Xen boots, everything runs well,
only the network does not work, lsmod naturally reports there is no tg3 module
loaded, etc...
I make it
on Debian Lenny, HW is the standard HP G5 ML 110 Server with the on-board
integrated Broadcom NIC, driven in the Non-Xen kernel by the tg3 driver, NIC
reported in dmesg as
Tigon3
[PartNo(N/A) rev a200 (5722/5756)] (PCI Express) 10/100/1000Base-T Ethernet
What do I
wrong? Or is it a bug? I have found there has been fixed in the last version
some issue with the tg3 driver, so cannot it be this is somehow connected to
this problem?
Any helps or
pointers are appreciated.
Thanx in
advance, Artur
P.S. I also performed the step 4 with the –d switch
and there was generated following make-log, related to tg3:
...
Considering target file
`drivers/net/tg3.o'.
File `drivers/net/tg3.o' does not
exist.
Looking for an implicit rule for
`drivers/net/tg3.o'.
Trying pattern rule with stem
`tg3.o'.
Trying implicit prerequisite
`drivers/net/tg3.o_shipped'.
Trying pattern rule with stem
`tg3'.
Trying implicit prerequisite `drivers/net/tg3-xen.c'.
Trying pattern rule with stem
`tg3'.
Trying implicit prerequisite
`drivers/net/tg3-xen.S'.
Trying pattern rule with stem
`tg3'.
Trying implicit prerequisite
`drivers/net/tg3.c'.
Found prerequisite `drivers/net/tg3.c'
as VPATH `/root/Work/XenLinux/linux-2.6.18-xen-3.4.2/drivers/net/tg3.c'
Trying rule prerequisite `FORCE'.
Found an implicit rule for
`drivers/net/tg3.o'.
Considering target file
`drivers/net/tg3.c'.
Looking for an implicit
rule for `drivers/net/tg3.c'.
Trying pattern rule
with stem `tg3.c'.
Trying implicit
prerequisite `drivers/net/tg3.c_shipped'.
No implicit rule found
for `drivers/net/tg3.c'.
Finished prerequisites
of target file `drivers/net/tg3.c'.
No need to remake target
`drivers/net/tg3.c'; using VPATH name
`/root/Work/XenLinux/linux-2.6.18-xen-3.4.2/drivers/net/tg3.c'.
Considering target file
`FORCE'.
File `FORCE' does not
exist.
Finished prerequisites of
target file `FORCE'.
Must remake target `FORCE'.
Successfully remade target
file `FORCE'.
Finished prerequisites of target
file `drivers/net/tg3.o'.
Must remake target `drivers/net/tg3.o'.
Putting child 0x02331660 (drivers/net/tg3.o) PID 9144 on the
chain.
Live child 0x02331660 (drivers/net/tg3.o) PID 9144
CC drivers/net/tg3.o
Reaping winning child 0x02331660 PID 9144
Removing child 0x02331660 PID 9144 from chain.
Successfully remade target file
`drivers/net/tg3.o'.
...
That’s all nothing more found in the log related to
tg3
