Announcement

Collapse
No announcement yet.

KDE Network

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

    [SOLVED] KDE Network

    Good Afternoon kubuntu world. I am currently using KDE Neon. I switched from Kubuntu to Sabayon Linux to KDE Neon now. But, IDK what is happening, everything was working fine. I noticed that now the wireless network takes a while to get connected. A message says unable to connect to the wireless network. Another message comes on and it says unable to find network.

    At the same time, I can see the name of the wireless when my card is reading it. Obviously I have tried to disconnect and reconnect to the network. I have also deleted the network from my wireless list and added it back. Still it takes a minimum of 10 to 15 mins to get get connected. Also, I have tried different network for test, and still have the same issue.

    So, my question is: how can I get back to good working order? I am sure it was an update or something. Any help will be greatly appreciated.

    Thanks,

    pookito.
    You can get me Using Threema: B6WSCFVY
    Mastodon: @pookito@latinos.social
    Jabber: pookito@neko.im

    #2
    Need to know what network card driver you are using. See http://ask.xmodulo.com/network-card-...ion-linux.html
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Sure, thank you for waiting and my apologies for taking this long. I know that it has to be with an update, because it was working fine before, but here is what I got when I use the dmesg command and the modinfo:

      dmesg | grep -i ethernet
      [ 1.543034] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
      [12313.308871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

      I guess my driver info is: r8169

      pookito@pookito:~$ modinfo r8169
      filename: /lib/modules/4.10.0-42-generic/kernel/drivers/net/ethernet/realtek/r8169.ko
      firmware: rtl_nic/rtl8107e-2.fw
      firmware: rtl_nic/rtl8107e-1.fw
      firmware: rtl_nic/rtl8168h-2.fw
      firmware: rtl_nic/rtl8168h-1.fw
      firmware: rtl_nic/rtl8168g-3.fw
      firmware: rtl_nic/rtl8168g-2.fw
      firmware: rtl_nic/rtl8106e-2.fw
      firmware: rtl_nic/rtl8106e-1.fw
      firmware: rtl_nic/rtl8411-2.fw
      firmware: rtl_nic/rtl8411-1.fw
      firmware: rtl_nic/rtl8402-1.fw
      firmware: rtl_nic/rtl8168f-2.fw
      firmware: rtl_nic/rtl8168f-1.fw
      firmware: rtl_nic/rtl8105e-1.fw
      firmware: rtl_nic/rtl8168e-3.fw
      firmware: rtl_nic/rtl8168e-2.fw
      firmware: rtl_nic/rtl8168e-1.fw
      firmware: rtl_nic/rtl8168d-2.fw
      firmware: rtl_nic/rtl8168d-1.fw
      version: 2.3LK-NAPI
      license: GPL
      description: RealTek RTL-8169 Gigabit Ethernet driver
      author: Realtek and the Linux r8169 crew <netdev@vger.kernel.org>
      srcversion: EA7EBA99CD518C5B5A01B0F
      alias: pci:v00000001d00008168sv*sd00002410bc*sc*i*
      alias: pci:v00001737d00001032sv*sd00000024bc*sc*i*
      alias: pci:v000016ECd00000116sv*sd*bc*sc*i*
      alias: pci:v00001259d0000C107sv*sd*bc*sc*i*
      alias: pci:v00001186d00004302sv*sd*bc*sc*i*
      alias: pci:v00001186d00004300sv*sd*bc*sc*i*
      alias: pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*
      alias: pci:v000010ECd00008169sv*sd*bc*sc*i*
      alias: pci:v000010ECd00008168sv*sd*bc*sc*i*
      alias: pci:v000010ECd00008167sv*sd*bc*sc*i*
      alias: pci:v000010ECd00008161sv*sd*bc*sc*i*
      alias: pci:v000010ECd00008136sv*sd*bc*sc*i*
      alias: pci:v000010ECd00008129sv*sd*bc*sc*i*
      depends: mii
      intree: Y
      vermagic: 4.10.0-42-generic SMP mod_unload
      parm: use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
      parm: debugebug verbosity level (0=none, ..., 16=all) (int)
      Last edited by Snowhog; Jan 07, 2018, 08:25 PM.
      You can get me Using Threema: B6WSCFVY
      Mastodon: @pookito@latinos.social
      Jabber: pookito@neko.im

      Comment


        #4
        I will assumed that it was an update problem. I waited long enough and a new update fixed the issue. So, I'll close this thread.
        You can get me Using Threema: B6WSCFVY
        Mastodon: @pookito@latinos.social
        Jabber: pookito@neko.im

        Comment

        Working...
        X