search

KaOSx / main

Main stable deps, add-ons and drivers
https://kaosx.us/packages/packages.php?sortby=name&sordir=asc&repo=main
17 stars 16 forks source link

error in the connection network #6

Closed mcder3 closed 9 years ago

mcder3 commented 9 years ago

Yesterday install the latest version of KaOS KF5, after upgrading networkmanager disconnects every moment.

The only way I've managed to connect is enabled dhcpcd service.

Screenshot:

http://i.imgur.com/KoJgrha.png

Log Files:

https://drive.google.com/folderview?id=0B7tTd_BxrUN3b3NXM0FLVXpYYU0&usp=sharing

demmm commented 9 years ago

That is the same driver as in use here, both used on kde 4 and kf5 without issue., so not a driver problem. Can you post some more logs? sudo journalctl -b | grep r8169 sudo journalctl -b -p err

mcder3 commented 9 years ago

journalctl -b | grep r8169

dic 28 09:39:16 kaosx kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded dic 28 09:39:16 kaosx kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control dic 28 09:39:16 kaosx kernel: r8169 0000:02:00.0: irq 26 for MSI/MSI-X dic 28 09:39:16 kaosx kernel: r8169 0000:02:00.0 eth0: RTL8168g/8111g at 0xffffc90005132000, b8:97:5a:73:46:75, XID 0c000800 IRQ 26 dic 28 09:39:16 kaosx kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] dic 28 09:39:16 kaosx kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0 dic 28 09:39:21 kaosx NetworkManager[263]: (enp2s0): new Ethernet device (driver: 'r8169' ifindex: 2) dic 28 09:39:21 kaosx kernel: r8169 0000:02:00.0 enp2s0: link down dic 28 09:39:21 kaosx kernel: r8169 0000:02:00.0 enp2s0: link down dic 28 09:39:23 kaosx kernel: r8169 0000:02:00.0 enp2s0: link up

journalctl -b -p err

-- Logs begin at sáb 2014-12-27 21:23:43 CST, end at dom 2014-12-28 09:54:13 CST. -- dic 28 09:39:23 kaosx systemd[363]: Trying to run as user instance, but $XDG_RUNTIME_DIR is n dic 28 09:39:28 kaosx systemd[378]: Trying to run as user instance, but $XDG_RUNTIME_DIR is n dic 28 09:39:41 kaosx pulseaudio[666]: [pulseaudio] pid.c: Daemon already running. dic 28 09:39:41 kaosx pulseaudio[668]: [pulseaudio] pid.c: Daemon already running. dic 28 09:39:41 kaosx pulseaudio[670]: [pulseaudio] pid.c: Daemon already running. dic 28 09:40:01 kaosx ksysguardd[794]: cannot open config file '"/etc/ksysguarddrc"' dic 28 09:41:26 kaosx dhcpcd[1461]: if_addaddress6: Permission denied

demmm commented 9 years ago

sudo journalctl -b | grep dhcpd

mcder3 commented 9 years ago

shows nothing when executing the command

http://i.imgur.com/uuPwUF8.png

mcder3 commented 9 years ago

at this time I have activated the service dhcpcd not know if that affects the logs that I am commanding you?

demmm commented 9 years ago

No, it is fine it doesn't return any.

sudo systemctl status NetworkManager sudo systemctl status dhcpcd

mcder3 commented 9 years ago

systemctl status NetworkManager

● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since dom 2014-12-28 09:39:21 CST; 1h 5min ago Main PID: 263 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─263 /usr/sbin/NetworkManager --no-daemon

dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): Activation: Stage 3 of 5 (I...e. dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): Activation: Stage 5 of 5 (I..... dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): device state change: ip-con...0] dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): Activation: Stage 5 of 5 (I...e. dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): device state change: ip-che...0] dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): device state change: second...0] dic 28 09:41:32 kaosx NetworkManager[263]: NetworkManager state is now CONNECTED...AL dic 28 09:41:32 kaosx NetworkManager[263]: NetworkManager state is now CONNECTED...AL dic 28 09:41:32 kaosx NetworkManager[263]: Policy set 'enp2s0' (enp2s0) as defau...S. dic 28 09:41:32 kaosx NetworkManager[263]: (enp2s0): Activation: successful, dev...d. Hint: Some lines were ellipsized, use -l to show in full.

systemctl status dhcpcd

● dhcpcd.service - dhcpcd on all interfaces Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled) Active: active (running) since dom 2014-12-28 09:41:26 CST; 1h 3min ago Main PID: 1462 (dhcpcd) CGroup: /system.slice/dhcpcd.service └─1462 /sbin/dhcpcd -q -b

dic 28 09:41:26 kaosx dhcpcd[1461]: enp2s0: adding address fe80::e823:135f:add2:bfe1 dic 28 09:41:26 kaosx dhcpcd[1461]: if_addaddress6: Permission denied dic 28 09:41:26 kaosx dhcpcd[1461]: forked to background, child pid 1462 dic 28 09:41:26 kaosx dhcpcd[1462]: DUID 00:01:00:01:1c:32:24:b5:b8:97:5a:73:46:75 dic 28 09:41:26 kaosx dhcpcd[1462]: enp2s0: IAID 5a:73:46:75 dic 28 09:41:26 kaosx dhcpcd[1462]: enp2s0: soliciting an IPv6 router dic 28 09:41:26 kaosx dhcpcd[1462]: enp2s0: rebinding lease of 192.168.1.4 dic 28 09:41:32 kaosx dhcpcd[1462]: enp2s0: leased 192.168.1.4 for 86400 seconds dic 28 09:41:32 kaosx dhcpcd[1462]: enp2s0: adding route to 192.168.1.0/24 dic 28 09:41:32 kaosx dhcpcd[1462]: enp2s0: adding default route via 192.168.1.1

demmm commented 9 years ago

Hmm, so networkmanager was active 2 minutes before dhcpd was activated, still no clue what is going on.......

mcder3 commented 9 years ago

but I am very sure that this problem happened after update.

demmm commented 9 years ago

Can you reboot and run the status commands again, without activating dhcpd? Also run "hwinfo --network" and hwinfo --netcard" then.

demmm commented 9 years ago

"but I am very sure that this problem happened after update." yes, but now need to figure where the issue is, can be the kernel, iproute, networkmanager, dhcpd to name a few.

mcder3 commented 9 years ago

hwinfo --netcard

20: PCI 200.0: 0200 Ethernet controller
[Created at pci.328] Unique ID: c3qJ.5QXFr6qGU37 Parent ID: HnsE.tTRuzdQwFV7 SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "Realtek RTL8111/8168 PCI Express Gigabit Ethernet controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168 PCI Express Gigabit Ethernet controller" SubVendor: pci 0x1565 "Biostar Microtech Int'l Corp" SubDevice: pci 0x2400 Revision: 0x0c Driver: "r8169" Driver Modules: "r8169" Device File: enp2s0 I/O Ports: 0xe000-0xefff (rw) Memory Range: 0xf7c00000-0xf7c00fff (rw,non-prefetchable) Memory Range: 0xf0000000-0xf0003fff (ro,non-prefetchable) IRQ: 27 (1665 events) HW Address: b8:97:5a:73:46:75 Link detected: yes Module Alias: "pci:v000010ECd00008168sv00001565sd00002400bc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (PCI bridge)

hwinfo --network

24: None 00.0: 10701 Ethernet
[Created at net.125] Unique ID: Ij4C.ndpeucax6V1 Parent ID: c3qJ.5QXFr6qGU37 SysFS ID: /class/net/enp2s0 SysFS Device Link: /devices/pci0000:00/0000:00:1c.5/0000:02:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "r8169" Driver Modules: "r8169" Device File: enp2s0 HW Address: b8:97:5a:73:46:75 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #14 (Ethernet controller)

25: None 00.0: 10700 Loopback [Created at net.125] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown

demmm commented 9 years ago

Again, not a single fail or error shown. Still no internet after reboot?

mcder3 commented 9 years ago

the problem is that it connects and disconnects. the connection is not stable until activated dhcpcd

demmm commented 9 years ago

But why no errors anywhere. Best post the full log, sudo journalctl -b > log.txt the file "log.txt will be in your home directory.

mcder3 commented 9 years ago

Log.txt:

http://pastebin.com/YHPt15hB

demmm commented 9 years ago

dhcpd fails on trying an IPv6 connection, can you try to set IPv6 to ignore in the networkmanager plasmoid/settings?

mcder3 commented 9 years ago

I've never used ipv6, ipv4 I've always used

demmm commented 9 years ago

ipv6 is set to "automatic" by default in the network manager settings, please try to set to ignore, see if that changes any.

demmm commented 9 years ago

Anyone else seeing this issue, check "sudo journalctl -b | grep IPv6 If you see a lot of connects/disconnects with that, IPv6 needs to be set to ignored.

If anyone could try with a different kernel. Best try with linux-next: http://kaosx.us/phpBB3/viewtopic.php?f=7&t=69

mcder3 commented 9 years ago

no longer disconnects

ipv6 ignore http://i.imgur.com/5YVK98Z.png

dhcpcd disable http://i.imgur.com/wKzYove.png

mcder3 commented 9 years ago

I have 5 min and the connection network is stable

demmm commented 9 years ago

Now figure which one changed to make the search for IPv6.......

mcder3 commented 9 years ago

not if he was creating a conflict with ipv4. but it works well the connection network.

mcder3 commented 9 years ago

journalctl -b | grep IPv6

dic 28 12:15:41 kaosx kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready dic 28 12:15:43 kaosx kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready dic 28 12:15:48 kaosx kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready dic 28 12:15:48 kaosx kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready dic 28 12:15:49 kaosx dhcpcd[339]: enp2s0: soliciting an IPv6 router dic 28 12:15:50 kaosx kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready

judd1 commented 9 years ago

Hola, he leído y probado todo lo anterior, es más estoy fuera de mi casa, asi me prestan ethernet y hacer pruebas.,. Todo sigue igual con WiFi, imposible conectarse, salvo con dhcpcd o ethernet, por lo demás, gracias por preocuparse ! Mis respetos.-

demmm commented 9 years ago

@judd1 make sure to post the same logs as mcder3 did, so there is info available if your issue is the same.

judd1 commented 9 years ago

demm, no es el mismo problema, funciona perfecto en dhcpcd o ethernet cableada, mi problema es con wifi, y no puedo dar con la solución, lamentablemente, siendo KaOS tan hermosa distro linux. Seguire intentando....por ahora. Gracias demm !

2014-12-28 22:49 GMT-03:00 demmm notifications@github.com:

@judd1 https://github.com/judd1 make sure to post the same logs as mcder3 did, so there is info available if your issue is the same.

— Reply to this email directly or view it on GitHub https://github.com/KaOSx/main/issues/6#issuecomment-68226774.

demmm commented 9 years ago

@judd1 you can open a new issue, post as much info as possible, see the files mcder3 provided in the first post here, and add some logs as asked here, there is always a solution.

judd1 commented 9 years ago

Entiendo demm, ahora bien; ya comente que la única conexión de la cual dispongo es WIFI y se me hace terriblemente engorroso pasar datos con una conexión cableada, que no poseo, pero intentaré. Gracias.-

demmm commented 9 years ago

Closing. Issue resolved for original poster, no further logs or info from subsequent poster.