Topic: Network card's not recognized

[crusader]

I have two NIC's in my new server system on a ASUS P5K Premium.
The NIC's are:

Marvell 88E8056 PCI-E Gigabit LAN
and the
Realtek RTL8110SC PCI Gigabit LAN

both Nic's won't be recognized from my contribs 7.2 system.
Does someone know how I can activate those nic's?
I've tried it with the R8169 kernel module but it doesn't seem to work.
Any help would be great.

[crazybob]

They may not be on the hardware list.

Check this thread http://forums.contribs.org/index.php?topic=38420.msg173971#msg173971

Bob

[crusader]

I've tried that to get a working driver:

http://forums.contribs.org/index.php?topic=35435.0

but everytime I do the "make clean install" I get this error:

make -C src/ clean
make[1]: Entering directory `/root/r1000_v1.05/src'
rm -rf *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags .tmp_versions
make[1]: Leaving directory `/root/r1000_v1.05/src'
make -C src/ modules
make[1]: Entering directory `/root/r1000_v1.05/src'
make -C /lib/modules/2.6.9-55.0.2.ELsmp/build SUBDIRS=/root/r1000_v1.05/src modules
make: *** /lib/modules/2.6.9-55.0.2.ELsmp/build: No such file or directory.  Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[1]: *** [modules] Error 2
make[1]: Leaving directory `/root/r1000_v1.05/src'
make: *** [modules] Error 2

this is caused by the fact that the script is searching for the sources in /lib/modules/<kernelver>/build but the kernel-devel rpm file does only contain /usr/src/kernel... files
Does someone has an idea how I can solve that problem?

[arne]

Looks like you are missing the proper development environment.
From my notes (and without any guarantee):

1. Go to the server-manager panel and enable the yum function (program installer)
2. yum install kernel-devel Kernel-headers
3. yum install gcc
4. yum install cvs
5. yum install openssl-devel

(I guess the last one is irrelevant, but this were the notes.)

[byte]

Looks like you are missing the proper development environment.

No please don't, if this is your production box you NEVER want to have development tools on your box, either work (with dev tools) on a Centos 4.5 box or go for a supported NIC.

[arne]

byte -> Exuse me. I know that it is considered, among the sme developers, to be "incorrect" or "unsafe" to install a development environment, but the link supplyed bu crusader actually mentioned such an installation of a development environment.

What if the intallation of these packages, after the installation and use of the packackes, for the required tasks, then is removed:

yum remove ..
yum remove ..

Could this be an alternative ?

[cactus]

byte -> Exuse me. I know that it is considered, among the sme developers, to be "incorrect" or "unsafe" to install a development environment, but the link supplyed bu crusader actually mentioned such an installation of a development environment.

What if the intallation of these packages, after the installation and use of the packackes, for the required tasks, then is removed:

yum remove ..
yum remove ..

Could this be an alternative ?

It could be, but it still involves risks and might even render your production server useless and as such is considered very bad practice.

[byte]

byte -> Exuse me. I know that it is considered, among the sme developers, to be "incorrect" or "unsafe" to install a development environment,

Excuse me, but for someone so concerned with apparent security (see firewall threads) you sure don't seem to care all that much about the internal security of your box.

Incorrect its not just the SME developers, it's everyone who runs a production server.

but the link supplyed bu crusader actually mentioned such an installation of a development environment.

Then you should have suggested using Centos 4.5 for their development environment.

[arne]

I know all these argument and different point of views, I have heard them some times during the years. The usual way tha the argumantation regularly use to end is by an advice that the development should be done on a Centos server, and then the result from thit this compilation done on the Centos server should be transfered over to the SME server.

Personally I have no idea how to transfere those things I compiled on the Centos server over to the SME box.

If I (people) just knew the alternative it might be a bit more easy to avoid the "compile on the SME server alternative".

Is there a "how to" or something like that that can be refered to in such a way that users could be adviced to compile the sourecode on a Centos server and then transfere the compiled result to the SME server ? Personally I dont know how to do that. Possibly there exist a guide or something that I do not know about or possibly such a guide can be made ?

I think that if someone has bought in a new server it is not a good alternative just to ask them to throw away their hardware because it is not safe enough to install an development environment to compile the drivers, then to remove this development environment, when the job is done.

If there is an alternative "compile it on the Centos and transfere it to the SME server" guide this might be a even bether solution.
(I will try to read the SME documentation one more time to see if I can find that trick.)

********

I have gone trough the documentation .. again.

The only thing I can fint is in the development manual "how to make or modify a rpm". (Chapter 14).

http://distro.ibiblio.org/pub/linux/distributions/smeserver/contribs/gordonr/devguide/html/devguide.html

For an avarage user this guide will be rather hard to follow.

There should be some way to install a driver, or something like that, from sourcode, in such a way that the avarage user is able to do it.

(And actually there is at least one way - to install the development tools - do the job - then remove the develoment tools.)

[crusader]

Ok, I've found the proper packages for a compilation but now I get this error after trying to modprobe r1000 or insmod r1000.ko

insmod: error inserting 'r1000.ko': -1 Invalid module format

Any idea's why?

[cactus]

Any idea's why?

What does dmesg tell you?

[crusader]

r1000: disagrees about version of symbol struct_module

That's what dmesg says

[byte]

I know [..]

Please keep to original poster's topic. Thanks.

[byte]

Quote
r1000: disagrees about version of symbol struct_module

That's what dmesg says

Which means the version you was trying to load was made for a different kernel than you are actually running on SME Server.

[crusader]

I run a 2.6.9-55.0.12.ELsmp and the kernel-devel package places a /usr/src/kernel/2.6.9-55.0.12.EL and with this I've compiled the r1000.ko file