Realtek RTL 8169 no longer able to connect after upgrade - Redhat

This is a discussion on Realtek RTL 8169 no longer able to connect after upgrade - Redhat ; I was running at AS 3.0 Update 2 (2.4.21-9EL) and had my network configured and working. I upgraded to AS 3.0 Update 4 (2.4.21-27EL) and the network device is no longer functioning. When I boot, I get the hardware configuration ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Realtek RTL 8169 no longer able to connect after upgrade

  1. Realtek RTL 8169 no longer able to connect after upgrade

    I was running at AS 3.0 Update 2 (2.4.21-9EL) and had my network
    configured and working.

    I upgraded to AS 3.0 Update 4 (2.4.21-27EL) and the network device is
    no longer functioning. When I boot, I get the hardware configuration
    wizard coming up and telling me that I do not have the device and
    whether I should remove the config.

    I have done that, restarted and was able to remote the network entry
    from the network configuration (using the UI and yes, the entry was
    removed from the /etc/sysconfig/network-scripts directory) and then
    reconfigure the device to no avail.

    I do an modprobe r8169 and it succeeds and I see that there is an entry
    when i do an lsmod (autoclean) with CRC32 being the only module using
    it.

    There is no /dev/eth0 device.

    Clues?


  2. Re: Realtek RTL 8169 no longer able to connect after upgrade

    GadgetKing@gmail.com wrote:
    > I was running at AS 3.0 Update 2 (2.4.21-9EL) and had my network
    > configured and working.
    >
    > I upgraded to AS 3.0 Update 4 (2.4.21-27EL)


    Something funny here. The latest kernels that came with Update 4 to RHEL 3
    are:

    kernel-smp-2.4.21-27.0.1.EL
    kernel-source-2.4.21-27.0.1.EL

    > and the network device is
    > no longer functioning. When I boot, I get the hardware configuration
    > wizard coming up and telling me that I do not have the device and
    > whether I should remove the config.


    I have had a lot of problems with Update 4.

    First of all, the system would not run at run level 5. This was due to the
    fact that they moved file /etc/pango/pango.modules to
    /etc/pango/i386-redhat-linux-gnu/pango.modules and in the process, they
    changed its permissions from 0644 to 0640. So it would not even put up the
    "greeter" screen correctly.

    Second, the little applet that tells about updates, that is normally a
    blue dot with a white checkmark, but is a red dot with a flashing white
    exclamation point when updates are available, checks in with Red Hat every
    minute instead of every once in a long while (4 hours?). This kept my
    demand dialing Internet link from ever shutting down. Fortunately I have a
    tolerant ISP who do not mind my staying up for such long intervals. The
    fix is to change the last few lines in ~/rhn-applet.conf file like this:

    remindTimeStamp[comment]=None
    #remindTimeStamp=1104625865.4 <---<<< YMMV
    remindTimeStamp=NEVERREMIND
    >
    > I have done that, restarted and was able to remote the network entry
    > from the network configuration (using the UI and yes, the entry was
    > removed from the /etc/sysconfig/network-scripts directory) and then
    > reconfigure the device to no avail.
    >
    > I do an modprobe r8169 and it succeeds and I see that there is an entry
    > when i do an lsmod (autoclean) with CRC32 being the only module using
    > it.
    >
    > There is no /dev/eth0 device.
    >
    > Clues?
    >

    I have not had those problems because after reinstalling the whole thing,
    I replaced everything in /etc with what was on a very recent backup tape,
    so my configurations are as before. I have always found configuring
    networking with Red Hats GUI tools to be extremely confusing and lacking
    some of the stuff I needed, so I have been forced to use emacs to make the
    files I needed. At least their current tools are better than the old
    linuxconf.

    --
    .~. Jean-David Beyer Registered Linux User 85642.
    /V\ PGP-Key: 9A2FC99A Registered Machine 241939.
    /( )\ Shrewsbury, New Jersey http://counter.li.org
    ^^-^^ 08:45:00 up 14 days, 22:05, 4 users, load average: 4.18, 4.21, 4.18


  3. Re: Realtek RTL 8169 no longer able to connect after upgrade

    I know what you mean about the UI tools. I have manually inspected the
    network-scripts and the modules.conf and it is as it should be (or
    appears to be).

    What other diagnostics can I try besides a ping to a system in the same
    subnet to see if the network is functioning?
    Should I have a /dev/eth0? I don't recall checking for this before.


  4. Re: Realtek RTL 8169 no longer able to connect after upgrade

    GadgetKing@gmail.com wrote:
    > I know what you mean about the UI tools. I have manually inspected the
    > network-scripts and the modules.conf and it is as it should be (or
    > appears to be).
    >
    > What other diagnostics can I try besides a ping to a system in the same
    > subnet to see if the network is functioning?


    You can try ifconfig to see what your entire network as seen by your
    machine has been doing. I assume the counts start at boot time. N.B.: my
    eth1 does not have anything on it anymore: I gave that machine away.

    > Should I have a /dev/eth0? I don't recall checking for this before.
    >

    If you have an ethernet card (or equivalent on-board), you should have an
    eth? on there, and eth0 makes the most sense.

    $ /sbin/ifconfig
    eth0 Link encap:Ethernet HWaddr 00:30:48:29:1D:5E
    inet addr:192.168.1.251 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:7592125 errors:44 dropped:0 overruns:0 frame:44
    TX packets:1507786 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1948181676 (1857.9 Mb) TX bytes:432556384 (412.5 Mb)
    Base address:0x3000 Memory:fc200000-fc220000

    eth1 Link encap:Ethernet HWaddr 00:30:48:29:1D:5F
    inet addr:192.168.2.251 Bcast:192.168.2.255 Mask:255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Base address:0x3040 Memory:fc220000-fc240000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:87620 errors:0 dropped:0 overruns:0 frame:0
    TX packets:87620 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:40069547 (38.2 Mb) TX bytes:40069547 (38.2 Mb)

    ppp0 Link encap:Point-to-Point Protocol
    inet addr:123.456.789.012 P-t-P:12.35.56.78 Mask:255.255.255.255
    UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
    RX packets:933835 errors:37328 dropped:0 overruns:0 frame:0
    TX packets:831973 errors:0 dropped:2965 overruns:0 carrier:0
    collisions:0 txqueuelen:3
    RX bytes:952114386 (908.0 Mb) TX bytes:121660377 (116.0 Mb)


    --
    .~. Jean-David Beyer Registered Linux User 85642.
    /V\ PGP-Key: 9A2FC99A Registered Machine 241939.
    /( )\ Shrewsbury, New Jersey http://counter.li.org
    ^^-^^ 10:20:00 up 14 days, 23:40, 3 users, load average: 4.27, 4.21, 4.18


+ Reply to Thread