Topic: Onboard NIC Problem:

[ansentry]

Setting up new machine:
Motherboard ASUS P5GZ-MX
Onboard NIC: Marvell Yukon 88E8001 Gigabit Ethernet Controller.
On the installation CD there is a driver "install-8_36.tar.bz2"
I copied it to a directory on my machine and tar xfvj /install-8_36.tar.bz2.
Then I cd to DriverInstall and ran ./Install.sh
Up to this point all appeared to fine. Then the instructions I got of the web said to do the following:
#modprobe sk98lin
next
#netconfig
-bash: netconfig: command not found.

I would appreciate if someone can point me in the right direction.

[Stefano]

Setting up new machine:
Motherboard ASUS P5GZ-MX
Onboard NIC: Marvell Yukon 88E8001 Gigabit Ethernet Controller.
On the installation CD there is a driver "install-8_36.tar.bz2"
I copied it to a directory on my machine and tar xfvj /install-8_36.tar.bz2.
Then I cd to DriverInstall and ran ./Install.sh
Up to this point all appeared to fine. Then the instructions I got of the web said to do the following:
#modprobe sk98lin
next
#netconfig
-bash: netconfig: command not found.

I would appreciate if someone can point me in the right direction.

Hi

AFAIK you don't need that driver..

Code: [Select]


[root@fileserver ~]# cd /lib/modules/2.6.9-42.0.10.ELsmp/kernel/drivers/net
[root@fileserver net]# ls sk*
skge.ko  sky2.ko

sk98lin:
sk98lin.ko


so, what are you doing?

ciao

Stefano

[ansentry]

Stefano,

Thank you for you quick reply.


In .../Modules I only have:

2.6.9-42.0.3.ELsmp

not

2.6.9-42.0.10.ELsmp

Is this my problem, I can't do any yum update as my nic not working.
Any further help would be appreciated. It is 12:56PM here and I am of the bed.

[Stefano]

Stefano,

Thank you for you quick reply.


In .../Modules I only have:

2.6.9-42.0.3.ELsmp

not

2.6.9-42.0.10.ELsmp

Is this my problem, I can't do any yum update as my nic not working.
Any further help would be appreciated. It is 12:56PM here and I am of the bed.

Hi..

no problem for kernel version..

on a sme 7.1.3 I see:

Code: [Select]


[root@fileserver ~]# cd /lib/modules
[root@fileserver modules]# ls
2.6.9-34.EL     2.6.9-42.0.10.EL     2.6.9-42.0.10.plus.c4     2.6.9-42.0.2.EL     2.6.9-42.0.[b]3[/b].EL     2.6.9-42.0.8.EL     kabi-4.0-0
2.6.9-34.ELsmp  2.6.9-42.0.10.ELsmp  2.6.9-42.0.10.plus.c4smp  2.6.9-42.0.2.ELsmp  2.6.9-42.0.3.ELsmp  2.6.9-42.0.8.ELsmp  kabi-4.0-0smp
[root@fileserver modules]# cd 2.6.9-42.0.[b]3[/b].ELsmp/kernel/drivers/net/sk98lin/
[root@fileserver sk98lin]# ls
sk98lin.ko


so, it seems that you already have the right driver..

try

Code: [Select]


modprobe sk98lin


HTH

Ciao

Stefano

p.s. maybe you'll give a try tomorrow

[ansentry]

Stefano,

Yes you are right I do have the driver .

I tried:

#modprobe sk98lin

Nothing appears to happen it just takes me back to the #

No light on my NIC  and my switch (hub) does not indicate a connection.

Thanks again (I did not make it to bed) I will go and have a coffee then bed.

Thanks again.


PS I just noticed when I tried to shut it down, shutdown is halting on:

Shutting down interface eth0: eth0: network connection down.

[Stefano]

Stefano,

Yes you are right I do have the driver .

I tried:

#modprobe sk98lin

Nothing appears to happen it just takes me back to the #

No light on my NIC  and my switch (hub) does not indicate a connection.

Thanks again (I did not make it to bed) I will go and have a coffee then bed.

Thanks again.


PS I just noticed when I tried to shut it down, shutdown is halting on:

Shutting down interface eth0: eth0: network connection down.

ok..

try this:

Code: [Select]



config setprop InternalInterface Driver sk98lin Configuration static IPAddress your_ip Netmask your_netmask Network your_network Name eth0

signal-event post-upgrade; signal-event reboot


for example,

your_ip=192.168.0.1
your_netmask=255.255.255.0
your_network=192.168.0.0

be carefull: first command is on one line

let me know

Ciao

Stefano

[bpivk]

No light on my NIC and my switch (hub) does not indicate a connection.

Check the cable. Some of your lights should be turned on even if SME doesn't work (they should be on as soon as you boot your server).
I have never seen a switch that doesn't light up as soon as you connect a cable so this could be a hardware problem.

[ansentry]

bpivk,

I have changed switches (hub) and cables but still not light.

As the motherboard is brand new, you could be right "hardware problem"

I have re-installed SME and the problem still the same.

Stefano,

your_ip=192.168.0.1
your_netmask=255.255.255.0
your_network=192.168.0.0

Your_ip =192.168.4.41 - (this is the static ip of my machine)
your_netmask = 255.255.255.0 (this is my netmask)
your_network = what is this??

I tried 192.168.4.0 for your_network.
After I issue the command

signal-event post-upgrade; signal-event reboot

the system starts to shutdown and then stops at:

Shutting down interface eth0: eth0: network connection down.

I am using the same model motherboard on a winxp machine and it is fine. I may try and install xp on this machine to see if the onboard NIC is faulty.

Thank you both for you help and advise.

[Stefano]

bpivk,

I have changed switches (hub) and cables but still not light.

As the motherboard is brand new, you could be right "hardware problem"

yes, it makes sense..

Your_ip =192.168.4.41 - (this is the static ip of my machine)
your_netmask = 255.255.255.0 (this is my netmask)
your_network = what is this??

I tried 192.168.4.0 for your_network.

yes, you are right

After I issue the command

signal-event post-upgrade; signal-event reboot

the system starts to shutdown and then stops at:

Shutting down interface eth0: eth0: network connection down.

no problem..

at that point you can shut down the server via power button then reboot..

ciao

Stefano

[byte]

Why don't you save yourself the hassle and buy a cheap PCI NIC    and disable the onboard NIC

[ansentry]

Byte,

Yes that would be 1 easy way.

=============================================

I have another new machine (that I had put XP Pro on) that has an intel motherboard and Realtek onboard NIC so I install SME 7.1 on that and it worked fine.

I then put XP Pro onto the ASUS motherboard machine and the OP picked up the onboard NIC and it now works fine.

==============================================

bpivk,

You are right as I was installing SME onto the intel machine the NIC light came on before the installation was completed.

================================================
Stefano,

Thank you for your help.