FedoraForum.org - Fedora Support Forums and Community
Results 1 to 2 of 2
  1. #1
    hood Guest

    Red face (Solved) Can't get IP, Realtek 8139, dual boot XP Linux, WakeOnLan causes the problem

    I think this is not a fedora specific problem, since I can't get an IP with Ubuntu, Damnsmalllinux and Slax, all livecd versions. It would be great if someone can help me out.
    Many thanks in advance.

    Tried:
    - I added a 2nd network card, still no IP.
    - Tried different cables.
    - Tried Half 10 mode
    Code:
    mii-tool eth0 --force=10baseT-HD

    Hardware involves:
    - D-link 624 router with DHCP
    - Realtek 8139


    Error messages:
    Code:
    [fedora@localhost ~]$ dmesg |less
     ... 
    eth3: link up, 100Mbps, full-duplex, lpa 0x45E1
    eth2: link down
    ADDRCONF(NETDEV_UP): eth2: link is not ready
    eth3: no IPv6 routers present
    NETDEV WATCHDOG: eth3: transmit timed out
    eth3: Transmit timeout, status 0d 0000 c07f media 10.
    eth3: Tx queue start entry 4  dirty entry 0.
    eth3:  Tx descriptor 0 is 0008205a. (queue head)
    eth3:  Tx descriptor 1 is 0008204e.
    eth3:  Tx descriptor 2 is 00082156.
    eth3:  Tx descriptor 3 is 00082046.
    eth3: link up, 100Mbps, full-duplex, lpa 0x45E1
    NETDEV WATCHDOG: eth3: transmit timed out
    eth3: Transmit timeout, status 0d 0000 c07f media 10.
    eth3: Tx queue start entry 4  dirty entry 0.
    eth3:  Tx descriptor 0 is 00082156. (queue head)
    eth3:  Tx descriptor 1 is 00082046.
    eth3:  Tx descriptor 2 is 0008205a.
    eth3:  Tx descriptor 3 is 00082046.
    eth3: link up, 100Mbps, full-duplex, lpa 0x45E1
    NETDEV WATCHDOG: eth3: transmit timed out
    eth3: Transmit timeout, status 0d 0000 c07f media 10.
    eth3: Tx queue start entry 4  dirty entry 0.
    eth3:  Tx descriptor 0 is 00082156. (queue head)
    eth3:  Tx descriptor 1 is 00082156.
    eth3:  Tx descriptor 2 is 00082156.
    eth3:  Tx descriptor 3 is 00082156.
    ...
    Code:
    [root@localhost ~]# ethtool eth3
    Settings for eth3:
    	Supported ports: [ TP MII ]
    	Supported link modes:   10baseT/Half 10baseT/Full 
    	                        100baseT/Half 100baseT/Full 
    	Supports auto-negotiation: Yes
    	Advertised link modes:  10baseT/Half 10baseT/Full 
    	                        100baseT/Half 100baseT/Full 
    	Advertised auto-negotiation: No
    	Speed: 10Mb/s
    	Duplex: Half
    	Port: MII
    	PHYAD: 32
    	Transceiver: internal
    	Auto-negotiation: off
    	Supports Wake-on: pumbg
    	Wake-on: d
    	Current message level: 0x00000007 (7)
    	Link detected: yes
    Last edited by hood; 20th May 2008 at 01:07 PM.

  2. #2
    hood Guest
    Solved, quote from:
    http://www.linuxquestions.org/questi...-newer-593495/

    The issue
    Something got broken in kernel 2.6.21.3. The problem, according to the Gentoo Wiki and the Ubuntu Forums, is that:

    Quote:

    As of 27 May 2007, in kernel 2.6.21.3, you may experience the issues with the r8169 driver if you dual boot Windows on some systems. Windows by defaults disables the NIC at Windows shutdown time in order to disable Wake-On-Lan, and this NIC will remain disabled until the next time Windows turns it on. The r8169 driver in the kernel does not know how to turn the NIC on from this disabled state; therefore, the device will not respond, even if the driver loads and reports that the device is up. To work around this problem, simply enable the feature "Wake-on-lan after shutdown." You can set this options through Windows' device manager.
    The solution
    - Boot up Windows
    - Right click on My Computer
    - Click on Properties -> Hardware -> Device Manager
    - Expand your network card section and double click on your Realtek network card
    - Set "Wake-on-lan after shutdown" to enabled

Tags for this Thread

Posting Permissions

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