Find the answer to your Linux question:
Results 1 to 6 of 6
I get an odd error message when trying to bring up my network/eth :- Code: # service network restart Shutting down loopback interface: [ OK ] Bringing up loopback interface: ...
  1. #1
    Just Joined!
    Join Date
    Jun 2009
    Posts
    23

    [SOLVED] ifup "[blank] does not seem to be present, delaying initialization"

    I get an odd error message when trying to bring up my network/eth :-
    Code:
    # service network restart
    Shutting down loopback interface:  [  OK  ]
    Bringing up loopback interface:  [  OK  ]
     does not seem to be present, delaying initialization.
    [FAILED]
     does not seem to be present, delaying initialization.
    [FAILED]
    Code:
    # dmesg | grep eth
    eth0: (PCI Express:2.5GB/s:Width x4) 00:00:de:50:04:18
    eth0: Intel(R) PRO/1000 Network Connection
    eth0: MAC: 0, PHY: 4, PBA No: c83246-002
    eth1: (PCI Express:2.5GB/s:Width x4) 00:00:de:50:04:19
    eth1: Intel(R) PRO/1000 Network Connection
    eth1: MAC: 0, PHY: 4, PBA No: c83246-002
    Code:
    # dmesg | grep e1000
    e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k4
    e1000e: Copyright (c) 1999-2008 Intel Corporation.
    Code:
    # cat /etc/sysconfig/network-scripts/ifcfg-eth0
    # Intel Corporation 82571EB Gigabit Ethernet Controller
    DEVICE=eth0
    BOOTPROTO=none
    BROADCAST=192.168.0.255
    HWADDR=00:00:DE:50:04:18
    IPADDR=192.168.0.10
    NETMASK=255.255.255.0
    NETWORK=192.168.0.0
    ONBOOT=yes
    TYPE=Ethernet
    Anyone got any ideas?

  2. #2
    Trusted Penguin Roxoff's Avatar
    Join Date
    Aug 2005
    Location
    Nottingham, England
    Posts
    3,392
    This could be caused if you have an old network configuration, perhaps your system was upgraded from an earlier version of your distribution, or maybe you've changed or removed some other network card in the past.

    Whatever the cause, you can probably solve this by running 'system-config-network' (or, in text mode from the command line 'system-config-network-tui') and deleting any spurious/old/out of date interfaces it lists.
    Linux user #126863 - see http://linuxcounter.net/

  3. #3
    Just Joined!
    Join Date
    Jun 2009
    Posts
    23
    Quote Originally Posted by Roxoff View Post
    This could be caused if you have an old network configuration, perhaps your system was upgraded from an earlier version of your distribution, or maybe you've changed or removed some other network card in the past.

    Whatever the cause, you can probably solve this by running 'system-config-network' (or, in text mode from the command line 'system-config-network-tui') and deleting any spurious/old/out of date interfaces it lists.
    I do only get this error after a scripted kickstart of which I copy (overwrite) some system files, including ifcfg-eth0 & 1.
    (HWADDR was wrong once, then left blank for next try, then set correctly, wouldnt of thought that would have anything to do with this?)
    The date/time are all messed up due to no clock, couldnt be this?

    Other files I copy are nothing to do with networking (as far as I belive!)
    grub/smb/rc.init

    Thanks for your help, I will look into this more when at work tomos.

  4. #4

  5. #5
    Just Joined!
    Join Date
    Jun 2009
    Posts
    23
    Thats very intresting, thanks.

    As I am setting up many computers, all with the same networking info (private/closed systems).
    So I setup the ifcfg-eth0/1 and commented out the HWADDR, and saved this to copy once the new system is installed.
    When I got this error, I put the correct HWADDR in, and it still occured? Which was odd. But now we belive it is related to this, I will ensure this is correct before trying to engage the network.

    Many thanks.

  6. #6
    Just Joined!
    Join Date
    Jun 2009
    Posts
    23
    It was the HWADDR field missing (I have 2 nics on this board)!

    Once inplace it worked just great!

    Many thanks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...