Announcement

Collapse
No announcement yet.

Ksysguard does not show eth3 in the graph.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Ksysguard does not show eth3 in the graph.

    I posted a bug report on this issue, 357906 at https://bugs.kde.org/show_bug.cgi?id=357906
    So far there has been no activity since I first reported it on January 12 and I am perplexed why no one is concerned that Ksysguard does not show eth3 on the graph.
    Perhaps someone here can enlighten me as to why this bug is being ignored?
    I am using Kubuntu 14.04 LTS at this time, while considering upgrading to 16.04 LTS.
    Can anyone confirm that it is fixed in 16.04 or, ignored!
    Thank you!

    #2
    Being "unconfirmed", and no one else is reporting it, it is probably not a bug but a misconfiguration.
    Your post lacks information:
    computer make and model
    type of network chip or card and the driver it is using
    (use lshw to get this info)
    Mine looks like this:
    Code:
     *-network
                    description: Ethernet interface
                    product: [B]AR8151 [/B]v2.0 Gigabit Ethernet
                    vendor: Qualcomm Atheros
                    physical id: 0
                    bus info: pci@0000:0e:00.0
                    logical name: enp14s0
                    version: c0
                    serial: 4c:72:b9:2d:8d:99
                    size: 100Mbit/s
                    capacity: 1Gbit/s
                    width: 64 bits
                    clock: 33MHz
                    capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
                    configuration: autonegotiation=on broadcast=yes [B]driver=atl1c[/B] driverversion=1.0.1.1-NAPI duplex=full ip=192.168.1.101 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
    the output of ifconfig
    the output of iwconfig (because mislabled networks can be caused by the second device)
    The content of the /etc/network/interfaces file.

    Meanwhile, here is some light reading on networking: https://help.ubuntu.com/lts/servergu...iguration.html
    Last edited by GreyGeek; Nov 05, 2016, 06:01 AM.
    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
    – John F. Kennedy, February 26, 1962.

    Comment


      #3
      Output of sudo lshw | egrep -nA 23 kubuntu
      1:kubuntu
      2- description: Desktop Computer
      3- product: To Be Filled By O.E.M. (To Be Filled By O.E.M.)
      4- vendor: To Be Filled By O.E.M.
      5- version: To Be Filled By O.E.M.
      6- serial: To Be Filled By O.E.M.
      7- width: 64 bits
      8- capabilities: smbios-2.7 dmi-2.7 vsyscall32
      9- configuration: boot=normal chassis=desktop family=To Be Filled By O.E.M. sku=To Be Filled By O.E.M. uuid=00020003-0004-0005-0006-000700080009
      10- *-core
      11- description: Motherboard
      12- product: 990FX Killer
      13- vendor: ASRock
      14- physical id: 0
      15- serial: M80-51010900321
      16- *-firmware
      17- description: BIOS
      18- vendor: American Megatrends Inc.
      19- physical id: 0
      20- version: P1.30
      21- date: 10/14/2014
      22- size: 64KiB
      23- capacity: 4032KiB
      24- capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi


      Output of lshw | egrep -nA 14 network:
      169: *-network
      170- description: Ethernet interface
      171- product: Killer E220x Gigabit Ethernet Controller
      172- vendor: Qualcomm Atheros
      173- physical id: 0
      174- bus info: pci@0000:03:00.0
      175- logical name: eth3
      176- version: 10
      177- serial: d0:50:99:63:4a:8e
      178- size: 100Mbit/s
      179- capacity: 1Gbit/s
      180- width: 64 bits
      181- clock: 33MHz
      182- capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
      183- configuration: autonegotiation=on broadcast=yes driver=alx duplex=full ip=192.168.1.105 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s

      Output of /etc/network/interfaces file:
      interfaces(5) file used by ifup(8) and ifdown(8)
      auto lo
      iface lo inet loopback

      Output of ifconfig:
      eth3 Link encap:Ethernet HWaddr d0:50:99:63:4a:8e
      inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
      inet6 addr: fe80::d250:99ff:fe63:4a8e/64 Scope:Link
      UP BROADCAST RUNNING 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)
      Interrupt:47

      eth4 Link encap:Ethernet HWaddr 1c:ba:8c:a2:b5:d5
      inet addr:192.168.7.1 Bcast:192.168.7.3 Mask:255.255.255.252
      inet6 addr: fe80::1eba:8cff:fea2:b5d5/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:38 errors:0 dropped:0 overruns:0 frame:0
      TX packets:21630 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:5090 (5.0 KB) TX bytes:5268992 (5.2 MB)

      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:65536 Metric:1
      RX packets:116808 errors:0 dropped:0 overruns:0 frame:0
      TX packets:116808 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:12802079 (12.8 MB) TX bytes:12802079 (12.8 MB)

      Output of iwconfig:
      eth3 no wireless extensions.

      eth4 no wireless extensions.

      lo no wireless extensions.

      Comment


        #4
        The description of Ethernet interface logical names is described here. And, assuming your Ethernet cat5 cable is not miswired or defective, you've got one card and two logical configurations, apparently without bridging.

        The logical names are changeable, so you can configure eth3 to be eth0:
        Ethernet Interface Logical Names

        Interface logical names are configured in the file /etc/udev/rules.d/70-persistent-net.rules. If you would like control which interface receives a particular logical name, find the line matching the interfaces physical MAC address and modify the value of NAME=ethX to the desired logical name. Reboot the system to commit your changes.



        Ksysmonitor is configurable. You can add a tab and configure it to report any logical name you wish.
        "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
        – John F. Kennedy, February 26, 1962.

        Comment


          #5
          Thank you!
          You have no idea how many hours I have spent trying to find that information online.
          At any rate it did work changing the logical name. Then, I ran a upload/download speed test and it registered nothing, flatline. The ethernet card is part of the motherboard, so that cannot be changed.
          I guess I will have to put up without using ksysguard for checking the internet connection.
          Thank you, again!

          Comment


            #6
            I don't run 16.04 but you might check the widgets and see if a network monitor is among them.

            There are a couple of script utilities in the repository: ethstats and ethstatus. In the upper left hand corner of EVERY main window of any app in Linux is an icon. Left click on it and choose "More Actions". On that submenu is "Keep above others". You could resize the app so that just the info you want to watch is visible and move it to a corner or the top, and continue using other apps.
            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
            – John F. Kennedy, February 26, 1962.

            Comment

            Working...
            X