Topic: NIC Problem After Update

[Bud]

Please help

After Updating from 7.2 to 7.3 from Server Manager Softare Update I cannot get my Onboard NIC to work. I am running in " SERVER Only " mode.

When I type in " ifconfig eth0 " all I get is -: [root@serve]# eth0: error fetching interface informtion: Device not found

I have users Shouting, Please HELP 

[cactus]

Please help

After Updating from 7.2 to 7.3 from Server Manager Softare Update I cannot get my Onboard NIC to work. I am running in " SERVER Only " mode.

When I type in " ifconfig eth0 " all I get is -: [root@serve]# eth0: error fetching interface informtion: Device not found

I have users Shouting, Please HELP 

Is this a NIC that worked out of the box on the 7.2 system or is this a network card that needed it's own driver?

[Bud]

Thanks for the Quick Response

Yes it worked out of the Box after I installed 7.2. I did not need to install a Driver for it.

But if I wanted to load a Driver what is the Procedure?? Sorry I'm still new at Linux 

[CharlieBrady]

Please help

As it says in bright red when you post messages here - "Don't report problems here". Report all problems via the bug tracker.

[Bud]

Hey Guys Please what do I do. Please give me a Link to help me to Bind an Intel Lan Controller to this Server with an IP Address. How do I do This??? 

[Bud]

What is the Secret to setting up a NIC Manually on the SME Server and how do I do this? Please Help 

[Bud]

Yea Ok I understand. I'll just have to figure it out by myself I guess.   

[byte]

Yea Ok I understand. I'll just have to figure it out by myself I guess.   

Or do what Charlie said.

[Bud]

Thanks I got it Sorted out. Works Ok now. Just a few Questions on SME 7.3

1. How in Console mode of SME 7.3 can I find out what Drivers for What Hardware is Loaded at any Time?
2. If I want to load a Driver Manually what is the Procedure?
3. How do I backup my Server Settings and if I want to How do I restore them (for Future Reference)

Thanks for the Help 

[CharlieBrady]

Thanks I got it Sorted out. Works Ok now.

How did you get it sorted out?

1. How in Console mode of SME 7.3 can I find out what Drivers for What Hardware is Loaded at any Time?

Code: [Select]

config show EthernetDriver1
config show EthernetDriver2

will show you what the configured drivers are for eth0 and eth1.

2. If I want to load a Driver Manually what is the Procedure?

There is no procedure, and trying to use any NIC which isn't fully supported by the OS is (IMO) more trouble than it is worth.

3. How do I backup my Server Settings and if I want to How do I restore them (for Future Reference)

Backup and restore are fully covered in the Users Guide.  There is no option for selectively restoring only configuration.

If you've somehow screwed up your ethernet driver settings, you don't need to restore from backup - just choose option 2 "Configure this server" from the console menu.

[cactus]

If you've somehow screwed up your ethernet driver settings, you don't need to restore from backup - just choose option 2 "Configure this server" from the console menu.

Which can be found by login in as admin and not as root user (just to be sure)

[Bud]

Thanks again for you Input and Help

Well what I discovered is this:

I edited and changed my " grub.conf " (in boot/grub folder) file about two weeks ago to just Cosmetically show what Boot Options are Available eg:

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

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/main/root
#          initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=5
splashimage=(hd0,0)/grub/tux.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title MySME Server (2.6.9-55.0.12.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.12.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.12.ELsmp.img
title MySME Server (2.6.9-55.0.12.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.12.EL ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.12.EL.img
title MySME Server (2.6.9-55.0.9.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.9.ELsmp.img
title MySME Server (2.6.9-55.0.9.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.9.EL ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.9.EL.img
title MySME Server (2.6.9-55.0.2.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.2.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.2.ELsmp.img

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

Notice that the First Boot Img file is " 2.6.9-55.0.12.ELsmp "

Then I did the Software Updates.

BANG The Server Boots but it does not Bind the Server IP Address to the Onboard Lan Controller

WHY?

Because when I lloked at my " grub.conf " File I noticed some changes:

Changed grub.conf File
============================================ 

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/main/root
#          initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title SME Server (2.6.9-67.0.1.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-67.0.1.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-67.0.1.ELsmp.img
title SME Server (2.6.9-67.0.1.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-67.0.1.EL ro root=/dev/main/root
   initrd /initrd-2.6.9-67.0.1.EL.img
title MySME Server (2.6.9-55.0.12.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.12.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.12.ELsmp.img
title MySME Server (2.6.9-55.0.12.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.12.EL ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.12.EL.img
title MySME Server (2.6.9-55.0.9.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.9.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.9.ELsmp.img
title MySME Server (2.6.9-55.0.9.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.9.EL ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.9.EL.img
title MySME Server (2.6.9-55.0.2.ELsmp)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.2.ELsmp ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.2.ELsmp.img
title SME Server-up (2.6.9-55.0.2.EL)
   root (hd0,0)
   kernel /vmlinuz-2.6.9-55.0.2.EL ro root=/dev/main/root
   initrd /initrd-2.6.9-55.0.2.EL.img

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

Notice now that the First Boot Img that it uses is " 2.6.9-67.0.1.ELsmp " amd not the Original " 2.6.9-55.0.12.ELsmp " boot img File.

That is what caused the Server not Load the Correct Lan Driver.

What can I do to make the Default boot String to be " 2.6.9-55.0.12.ELsmp " all the Time even if I do Software updates?

Hope this Helps 

[thomasch]

turning off SME Server kernel updates from smeserver os repository can help to retain kernel that works with your NIC

server-manager::Software Installer::Change Software Installer Settings

[raem]

Bud

The real issue (as I see it) is that you are making custom changes that rely upon a certain kernel.
As sme will continuously be upgraded, and kernel changes are usually part of that upgrade process, then you have locked yourself into an old kernel (which is not a good idea).

This will continue to be a problem for future upgrades (eg security related fixes which you will definitely want), which may depend on a new kernel being installed & running.

Your better approach is to use fully supported NICs, ie plug in a supported NIC card rather than use unsupported onboad NICs or NICs requiring extra drivers/kernel dependencies. They only cost a few dollars these days so the insistance to use on board NICs does not really save you much, and in fact causes you further support costs.

[byte]

As sme will continuously be upgraded, and kernel changes are usually part of that upgrade process, then you have locked yourself into an old kernel (which is not a good idea).

And you would not be able to use VPN if selecting an older kernel.