• Like 0

    kernel 4.9.6. update: no Internet


    Hi,

    i’ve updated to 4.9.6. but ran into a problem.

    Before systemd 232 start, I’ve got these two warning messages
    0.4964731 platform wdat_wdt failed to claim resource 4
    0.4955987 ACPI wtchdog: failed to create platform device

    Internet connection fails. I have no clue.

  • Like 0

    Please, forget about the above message. I will now roll back to a previous Antergos save so I will be unable to provide dmesgs, logs, whatever may be needed to solve this.

    Cheers

  • Like 0

    Situation is now stabilized.

    I now have only three packages left to update, linux-firmware, linux kernel 4.9.6 and its headers.
    I’ll be waiting some days.
    If my material configuration may be of some help, let me know.

  • Like 0

    Please install linux-lts kernel, just in case (this way you’ll be able to boot into a kernel that allows you have an Internet connection)

    Also, if you eventually update to 4.9 and there’s no Internet, check your journal with journalctl. Also dmesg might be useful.

    Cheers!

  • Like 0

    @karasu

    Thnaks for the advice. I’ll do it.

  • Like 0

    Same problem here. I cant connect to wifi networks.
    Tried to boot into the lts kernel, but then an error showed up, regarding that lightdm failed to start. I just logged in into another tty, and then through the nmtui tried to connect to some wireless networks. But again no luck.
    So for me, both lts kernel, and current kernel cant conect to wifi networks.
    Any ideas as of what to do next?

  • Like 0

    So for me, both lts kernel, and current kernel cant conect to wifi networks.

    That’s really odd if it was working before… you can try to downgrade to 4.8.13

    cd /var/lib/cache/pacman/pkg
    sudo pacman -U linux-4.8.13-1-x86_64.pkg.tar.xz
    sudo mkinitcpio -p linux
    sudo grub-mkconfig -o /boot/grub/grub.cfg
    

    To diagnose your problem, you have to check your logs using
    journalctl -x and dmesg when booting with 4.9

    Cheers!

  • Like 1

    The problem was network manager i guess. Reinstalled it solve the issue.

  • Like 0

    Hi

    It seems this is not the same bug.

    I reproduced it and I can confirm it appears after updating these two packages: kernel 4.9.6. and its headers. I will provide the informations suggested by karasu after reinstall.

  • Like 0

    Hi

    There is a marked improvement with kernel 4.9.7. I get exactly the same warnings on top of systemd 232 like in the first message of this thread but this time, I have an Internet connection.I would be keen to make them disappear.

    The journalctl information I am supposed to transmit is really very verbose. How could reduce this output to something manageable?

  • Like 0

    Well after 15 minutes, the Internet connection failed again. I collected the last journalctl information as well as dmesg
    journalctl
    [spoiler][[email protected] ~]$ journalctl -f -x
    – Logs begin at Tue 2015-04-28 02:52:01 HKT. –
    févr. 07 10:25:39 anterg gvfsd-network[1867]: Couldn’t create directory monitor on smb://x-gnome-default-workgroup/. Error: L’emplacement indiqué n’est pas monté
    févr. 07 10:25:40 anterg gvfsd[477]: mkdir failed on directory /var/cache/samba: Permission non accordée
    févr. 07 10:25:41 anterg gvfsd[477]: mkdir failed on directory /var/cache/samba: Permission non accordée
    févr. 07 10:25:42 anterg gvfsd[477]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): L’obtention de la liste des partages du serveur a échoué : Connexion refusée
    févr. 07 10:25:42 anterg gvfsd-network[1870]: Couldn’t create directory monitor on smb://x-gnome-default-workgroup/. Error: L’emplacement indiqué n’est pas monté
    févr. 07 10:25:55 anterg NetworkManager[364]: <info> [1486434355.9035] connectivity: check for uri ‘http://pkgbuild.com/check_network_status.txt’ failed with 'Erreur de résolution de « pkgbuild.com » : Nom ou service inconnu’
    févr. 07 10:26:05 anterg dbus-daemon[467]: Activating service name='org.gnome.gedit’
    févr. 07 10:26:05 anterg dbus-daemon[467]: Successfully activated service 'org.gnome.gedit’
    févr. 07 10:29:25 anterg expressvpnd[886]: Connection failed with error: network is unreachable, retry in 1.0 secondsFailed to reconnect! Reach max retry limit!xvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:57491->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:49850->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:52766->127.0.0.53:53: read: connection refusedFailed to send disconnect request.Failed to send disconnect request.Failed to send disconnect request.Cannot update client ip. Error: Get https://www.asdjkljfjaowjfq.net/xv-conn-status?include_country_city_isp=1: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:37273->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:48172->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:53548->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:54506->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:44478->127.0.0.53:53: read: connection refusedxvca: error sending event: Post https://www.asdjkljfjaowjfq.net/track: dial tcp: lookup www.asdjkljfjaowjfq.net on 127.0.0.53:53: read udp 127.0.0.1:50121->127.0.0.53:53: read: connection refusedxvca: error sending event: Post ht
    févr. 07 10:30:55 anterg NetworkManager[364]: <info> [1486434655.9039] connectivity: check for uri ‘http://pkgbuild.com/check_network_status.txt’ failed with ‘Erreur de résolution de « pkgbuild.com » : Nom ou service inconnu’
    ^C
    [[email protected] ~]$
    [/spoiler]
    dmesg will be sent using another mean

  • Like 0

    Here is for dmesg which is a 65k file. You can download it from here.

    http://www75.zippyshare.com/v/dwvUJEM7/file.html

    Now I have reinstalled the system using Clonezilla and use again 4.8.13.

  • Like 0

    Sorry, can’t download it.

    Could you paste it to paste2.org and put the link here? (if it’s too long put just the ending part).

    Thanks!

  • Like 0

    @karasu

    Thank you for looking at it

    http://paste2.org/8UfyhE7t

  • Like 0

    Hi,

    But here it is working, right?

    [  665.110846] wlp9s0: associate with 00:23:69:c8:04:e6 (try 1/3)
    [  665.116962] wlp9s0: RX AssocResp from 00:23:69:c8:04:e6 (capab=0x411 status=0 aid=2)
    [  665.117310] wlp9s0: associated
    [ 665.117320] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0: link becomes ready```
  • Like 0

    When I took out this dmesg, Internet connection was broken. It had been working 15 minutes after restart (just the time to send the “improvement” message) and then stopped for good like it did for 4.9.6.

  • Like 0

    @karasu

    I’ll make another try in some days, using 4.9.8. which is reported to have “many network improvements”.

    It’s easy to foresee that something will be wrong when I see the two fateful lines appear before the start of systemd 232

  • Like 0

    Hi

    I tried again today to update from my current 4.8.13-1 kernel to the brand new 4.9.9-1 kernel and I obtained exactly the two same messages before loading systemd232. No Internet connection. I reverted back to the previous 4.8.13-1 kernel.
    If this may be useful, here are my two dmesg reports using these two different kernels in case the differences can tell us something useful.

    this is dmesg with kernel 4.8.13-1
    https://paste2.org/Izj0Akmf
    this is dmesg with kernel 4.9.9-1
    https://paste2.org/6bYLDknX
    At the end there is a mistake regarding sdb3 which is not relevant to this problem.

    Regards

    Roger

internet12 kernel53 4.9.61 Posts 18Views 1053
Log in to reply