Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: 8139cp and 8139too

  1. #1
    Join Date
    Oct 2005
    Beans
    28

    8139cp and 8139too

    Version: 8.04

    when i boot i see this error message
    is not an 8139C+ compatible chip
    Try the "8139too" driver instead.
    i looked with lsmod | grep 8139 and i get
    8139too 27776 0
    8139cp 25088 0
    mii 6400 2 8139too,8139cp
    from what i found on google i should blacklist the 8139cp driver, so i added it to /etc/modprobe.d/blacklist at the end of the file i put blacklist 8139cp

    then i rebooted but i still got the same error, and i still get both when i lsmod | grep 8139

  2. #2
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,021
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: 8139cp and 8139too

    Mysterious, isn't it? Does your ethernet card work as expected? If so, I'd ignore it. I, and many people have this, but it doesn't affect my ability to connect or transfer data.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  3. #3
    Join Date
    Oct 2005
    Beans
    28

    Re: 8139cp and 8139too

    i just put this network card in, and i cant ping anything
    ifconfig only gives me localhost ip address
    and when i run
    sudo lshw -C network
    the first line says
    *-network DISABLED

  4. #4
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,021
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: 8139cp and 8139too

    Is the above text in dmesg the only clue? Is the behavior improved if you do:
    Code:
    sudo rmmod -f 8139cp
    Are you dual-booting with Windows?

    http://www.linuxquestions.org/questi...-newer-593495/
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  5. #5
    Join Date
    Oct 2005
    Beans
    28

    Re: 8139cp and 8139too

    no dual boot. it is an old pc that i want to run as a home webserver, it has been running 8.04 before, but i just put this old network card in that i had lying around.

    i ran that command and reboot'ed and i still got the same error message, also it still shows up on lsmod

  6. #6
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,021
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: 8139cp and 8139too

    Who said reboot? Please do:
    Code:
    sudo rmmod-f 8139cp 
    ifconfig
    Do you have an ethernet interface?
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  7. #7
    Join Date
    Oct 2005
    Beans
    28

    Re: 8139cp and 8139too

    whops sorry, im still getting used to how things work

    ok, ran it and here is ifconfig

    Code:
    lo     Link encap:Local Loopback
           inet addr:127.0.0.1 Mask:255.0.0.0
           inet6 addr:  ::1/128 Scope:Host
           UP LOOPBACK RUNNING MTU:16436 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:0
           RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    edit* Uh oh, theres no eth0!
    Last edited by Carus; March 25th, 2010 at 08:29 PM.

  8. #8
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,021
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: 8139cp and 8139too

    Then something else is wrong. Let's have a look at:
    Code:
    dmesg | grep -e 8139 -e eth
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

  9. #9
    Join Date
    Oct 2005
    Beans
    28

    Re: 8139cp and 8139too

    Code:
    [   24.239220] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 2004)
    [   24.      ] ACPI Error (evgpe-0705): No handler or method for GPE[ 5], disabling event [20070126]
    [   25.      ] 8139cp 0000:00:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
    [   25.      ] 8139cp 0000:00:08.0 try the "8139too" driver instead.
    [   25.      ] 8139too Fast Ethernet driver 0.9.28
    [   25.      ] eth0: RealTek RTL8139 at 0xd800, 00:20:18:d7:33:3c, IRQ 11
    [   25.      ] eth0: Indentified 8139 chip type 'RTL-8139C'
    [   26.      ] Driver 'sd' needs updating - please use bus_type methods
    [   26.      ] sda:<4>Driver 'sr' needs updating - please use bus_type methods
    [   37.      ] udev: renamed network interface eth0 to eth1

    thats the output, i kinda skipped typing up all the numbers on the left to save time.

  10. #10
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    25,021
    Distro
    Ubuntu 19.10 Eoan Ermine

    Re: 8139cp and 8139too

    udev: renamed network interface eth0 to eth1
    This is interesting. Did you have another ethernet card in there previously? I am wondering why the interface gets created, renamed and then disappears without a trace. We need, unfortunately, more diagnostics. Please check:
    Code:
    sudo cat /var/log/syslog | grep -e eth -e 00:08
    The file will be long so you can just grab the last ten or so lines, or more if they look suspicious. If it helps, you can copy and paste from the terminal into a text document and transfer the text on a USB key.

    Is it too soon to wonder if the card is defective?
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D., Sc.D.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

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