Emancipate Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Litt komplisert, men jeg hadde altså to PCer som, etter det jeg visste, fungerte perfekt. Men i det siste har jeg bare brukt PC 1. Inntil nylig, da jeg byttet kabinett på PC 2 og begynte å bruke den. Etter det har jeg fått noen problemer med korte til lange ( flere minutter) perioder med skyhøy ping, se under: 64 bytes from 192.168.1.1: icmp_seq=336 ttl=64 time=1.20 ms 64 bytes from 192.168.1.1: icmp_seq=337 ttl=64 time=1.39 ms 64 bytes from 192.168.1.1: icmp_seq=338 ttl=64 time=1.42 ms 64 bytes from 192.168.1.1: icmp_seq=339 ttl=64 time=1.40 ms 64 bytes from 192.168.1.1: icmp_seq=340 ttl=64 time=1.43 ms 64 bytes from 192.168.1.1: icmp_seq=341 ttl=64 time=1.41 ms 64 bytes from 192.168.1.1: icmp_seq=342 ttl=64 time=1.40 ms 64 bytes from 192.168.1.1: icmp_seq=343 ttl=64 time=1.17 ms 64 bytes from 192.168.1.1: icmp_seq=344 ttl=64 time=1.47 ms 64 bytes from 192.168.1.1: icmp_seq=345 ttl=64 time=1.39 ms 64 bytes from 192.168.1.1: icmp_seq=346 ttl=64 time=1.13 ms 64 bytes from 192.168.1.1: icmp_seq=348 ttl=64 time=2185 ms 64 bytes from 192.168.1.1: icmp_seq=349 ttl=64 time=1739 ms 64 bytes from 192.168.1.1: icmp_seq=350 ttl=64 time=926 ms 64 bytes from 192.168.1.1: icmp_seq=351 ttl=64 time=76.5 ms 64 bytes from 192.168.1.1: icmp_seq=352 ttl=64 time=5.87 ms 64 bytes from 192.168.1.1: icmp_seq=353 ttl=64 time=1.48 ms 64 bytes from 192.168.1.1: icmp_seq=354 ttl=64 time=1.42 ms 64 bytes from 192.168.1.1: icmp_seq=355 ttl=64 time=1.42 ms 64 bytes from 192.168.1.1: icmp_seq=356 ttl=64 time=1.17 ms 64 bytes from 192.168.1.1: icmp_seq=357 ttl=64 time=1.41 ms 64 bytes from 192.168.1.1: icmp_seq=358 ttl=64 time=1.42 ms 64 bytes from 192.168.1.1: icmp_seq=359 ttl=64 time=1.48 ms cat /etc/issueUbuntu 14.04.1 LTS \n \l uname -a Linux ubuntu-studio 3.13.0-40-lowlatency #69-Ubuntu SMP PREEMPT Thu Nov 13 18:11:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Jeg har prøvd å restarte ruter. Noen idéer? Jeg er rimelig sikker på at det ikke er ruteren, ettersom den fungerte perfekt til jeg byttet PC. Lenke til kommentar
Lycantrophe Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Står det noe morsomt i dmesg? Lenke til kommentar
Emancipate Skrevet 12. februar 2015 Forfatter Del Skrevet 12. februar 2015 Dette er noe av det siste som står: [ 7.556224] Bluetooth: RFCOMM TTY layer initialized [ 7.556243] Bluetooth: RFCOMM socket layer initialized [ 7.556246] Bluetooth: RFCOMM ver 1.11 [ 7.562795] init: cups main process (848) killed by HUP signal [ 7.562800] init: cups main process ended, respawning [ 7.653955] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7.653957] Bluetooth: BNEP filters: protocol multicast [ 7.653964] Bluetooth: BNEP socket layer initialized [ 7.926512] init: Failed to spawn atd main process: unable to execute: No such file or directory [ 8.179820] r8169 0000:02:00.0 eth0: link down [ 8.179864] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8.180054] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8.181277] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S [ 8.181482] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S [ 8.192759] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 8.192946] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 8.346543] init: samba-ad-dc main process (1147) terminated with status 1 [ 8.895790] init: plymouth-upstart-bridge main process ended, respawning [ 9.258862] init: plymouth-stop pre-start process (1500) terminated with status 1 [ 15.498743] wlan0: authenticate with 00:14:78:ec:e4:3e [ 15.500759] wlan0: send auth to 00:14:78:ec:e4:3e (try 1/3) [ 15.502650] wlan0: authenticated [ 15.502763] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [ 15.502765] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [ 15.503560] wlan0: associate with 00:14:78:ec:e4:3e (try 1/3) [ 15.507125] wlan0: RX AssocResp from 00:14:78:ec:e4:3e (capab=0x431 status=0 aid=1) [ 15.507869] wlan0: associated [ 15.507895] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 15.507937] cfg80211: Calling CRDA for country: NO [ 15.510313] cfg80211: Regulatory domain changed to country: NO [ 15.510315] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 15.510316] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 15.510317] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 15.510318] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 15.510318] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 15.510319] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) [ 16.243757] wlan0: deauthenticating from 00:14:78:ec:e4:3e by local choice (reason=2) [ 16.245604] wlan0: authenticate with 00:14:78:ec:e4:3e [ 16.247554] wlan0: send auth to 00:14:78:ec:e4:3e (try 1/3) [ 16.248076] cfg80211: Calling CRDA to update world regulatory domain [ 16.249239] wlan0: authenticated [ 16.249327] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [ 16.249329] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [ 16.249697] cfg80211: World regulatory domain updated: [ 16.249699] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 16.249700] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 16.249701] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 16.249701] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 16.249702] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 16.249703] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 16.250592] wlan0: associate with 00:14:78:ec:e4:3e (try 1/3) [ 16.253169] wlan0: RX AssocResp from 00:14:78:ec:e4:3e (capab=0x431 status=0 aid=1) [ 16.255716] wlan0: associated [ 16.255759] cfg80211: Calling CRDA for country: NO [ 16.257249] cfg80211: Regulatory domain changed to country: NO [ 16.257251] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 16.257252] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 16.257253] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 16.257254] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 16.257255] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 16.257255] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) [ 37.375766] audit_printk_skb: 87 callbacks suppressed [ 37.375768] type=1400 audit(1423741907.736:53): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2209 comm="apparmor_parser" [ 37.375772] type=1400 audit(1423741907.736:54): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2209 comm="apparmor_parser" [ 37.375990] type=1400 audit(1423741907.736:55): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2209 comm="apparmor_parser" [ 2469.956959] wlan0: deauthenticated from 00:14:78:ec:e4:3e (Reason: 1) [ 2469.979004] cfg80211: Calling CRDA to update world regulatory domain [ 2469.984698] cfg80211: World regulatory domain updated: [ 2469.984703] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 2469.984707] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2469.984710] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2469.984712] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 2469.984714] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2469.984716] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2473.733622] wlan0: authenticate with 00:14:78:ec:e4:3e [ 2473.735614] wlan0: send auth to 00:14:78:ec:e4:3e (try 1/3) [ 2473.737899] wlan0: authenticated [ 2473.738043] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [ 2473.738048] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [ 2473.738593] wlan0: associate with 00:14:78:ec:e4:3e (try 1/3) [ 2473.741178] wlan0: RX AssocResp from 00:14:78:ec:e4:3e (capab=0x431 status=0 aid=1) [ 2473.741871] wlan0: associated [ 2473.741925] cfg80211: Calling CRDA for country: NO [ 2473.744894] cfg80211: Regulatory domain changed to country: NO [ 2473.744896] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 2473.744897] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 2473.744897] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 2473.744898] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 2473.744899] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 2473.744900] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) [ 2768.153234] cfg80211: Calling CRDA to update world regulatory domain [ 2768.155099] cfg80211: World regulatory domain updated: [ 2768.155100] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 2768.155101] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2768.155102] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2768.155103] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 2768.155104] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2768.155104] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 2783.411155] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2787.069853] wlan0: authenticate with 00:14:78:ec:e4:3e [ 2787.071446] wlan0: send auth to 00:14:78:ec:e4:3e (try 1/3) [ 2787.073190] wlan0: authenticated [ 2787.073290] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [ 2787.073292] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [ 2787.073378] wlan0: associate with 00:14:78:ec:e4:3e (try 1/3) [ 2787.075906] wlan0: RX AssocResp from 00:14:78:ec:e4:3e (capab=0x431 status=0 aid=1) [ 2787.084151] wlan0: associated [ 2787.084186] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2787.084243] cfg80211: Calling CRDA for country: NO [ 2787.086955] cfg80211: Regulatory domain changed to country: NO [ 2787.086958] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 2787.086960] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 2787.086962] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 2787.086963] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 2787.086964] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 2787.086965] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) [20753.791519] perf samples too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 [21392.848985] type=1400 audit(1423763269.491:56): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/etc/xfce4/defaults.list" pid=5740 comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [36084.474339] wlan0: deauthenticated from 00:14:78:ec:e4:3e (Reason: 1) [36084.493355] cfg80211: Calling CRDA to update world regulatory domain [36084.506796] cfg80211: World regulatory domain updated: [36084.506798] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [36084.506800] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [36084.506801] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [36084.506803] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [36084.506804] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [36084.506805] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [36088.250074] wlan0: authenticate with 00:14:78:ec:e4:3e [36088.251631] wlan0: send auth to 00:14:78:ec:e4:3e (try 1/3) [36088.253451] wlan0: authenticated [36088.253534] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [36088.253536] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [36088.254198] wlan0: associate with 00:14:78:ec:e4:3e (try 1/3) [36088.256956] wlan0: RX AssocResp from 00:14:78:ec:e4:3e (capab=0x431 status=0 aid=1) [36088.257682] wlan0: associated [36088.257721] cfg80211: Calling CRDA for country: NO [36088.260065] cfg80211: Regulatory domain changed to country: NO [36088.260072] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [36088.260076] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [36088.260079] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [36088.260082] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [36088.260084] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [36088.260087] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) Lenke til kommentar
Lycantrophe Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Tipper ping-spikes kommer av at du deauthenticates sporadisk. Lenke til kommentar
Emancipate Skrevet 12. februar 2015 Forfatter Del Skrevet 12. februar 2015 Det er nok værre enn som så. 64 bytes from 192.168.1.1: icmp_seq=384 ttl=64 time=214 ms 64 bytes from 192.168.1.1: icmp_seq=385 ttl=64 time=434 ms 64 bytes from 192.168.1.1: icmp_seq=386 ttl=64 time=1185 ms 64 bytes from 192.168.1.1: icmp_seq=388 ttl=64 time=2047 ms 64 bytes from 192.168.1.1: icmp_seq=389 ttl=64 time=1718 ms 64 bytes from 192.168.1.1: icmp_seq=390 ttl=64 time=1318 ms 64 bytes from 192.168.1.1: icmp_seq=391 ttl=64 time=1241 ms 64 bytes from 192.168.1.1: icmp_seq=392 ttl=64 time=674 ms 64 bytes from 192.168.1.1: icmp_seq=393 ttl=64 time=1016 ms 64 bytes from 192.168.1.1: icmp_seq=394 ttl=64 time=200 ms 64 bytes from 192.168.1.1: icmp_seq=396 ttl=64 time=1834 ms 64 bytes from 192.168.1.1: icmp_seq=397 ttl=64 time=1438 ms 64 bytes from 192.168.1.1: icmp_seq=398 ttl=64 time=1728 ms 64 bytes from 192.168.1.1: icmp_seq=399 ttl=64 time=992 ms 64 bytes from 192.168.1.1: icmp_seq=400 ttl=64 time=1.95 ms 64 bytes from 192.168.1.1: icmp_seq=402 ttl=64 time=661 ms 64 bytes from 192.168.1.1: icmp_seq=403 ttl=64 time=790 ms 64 bytes from 192.168.1.1: icmp_seq=404 ttl=64 time=243 ms 64 bytes from 192.168.1.1: icmp_seq=405 ttl=64 time=250 ms 64 bytes from 192.168.1.1: icmp_seq=406 ttl=64 time=40.9 ms 64 bytes from 192.168.1.1: icmp_seq=407 ttl=64 time=1.54 ms 64 bytes from 192.168.1.1: icmp_seq=408 ttl=64 time=192 ms 64 bytes from 192.168.1.1: icmp_seq=409 ttl=64 time=18.8 ms 64 bytes from 192.168.1.1: icmp_seq=410 ttl=64 time=125 ms 64 bytes from 192.168.1.1: icmp_seq=411 ttl=64 time=27.3 ms 64 bytes from 192.168.1.1: icmp_seq=412 ttl=64 time=19.3 ms 64 bytes from 192.168.1.1: icmp_seq=413 ttl=64 time=5.31 ms 64 bytes from 192.168.1.1: icmp_seq=414 ttl=64 time=8.93 ms 64 bytes from 192.168.1.1: icmp_seq=415 ttl=64 time=3.40 ms 64 bytes from 192.168.1.1: icmp_seq=416 ttl=64 time=1.60 ms 64 bytes from 192.168.1.1: icmp_seq=417 ttl=64 time=122 ms 64 bytes from 192.168.1.1: icmp_seq=418 ttl=64 time=93.3 ms 64 bytes from 192.168.1.1: icmp_seq=419 ttl=64 time=74.7 ms 64 bytes from 192.168.1.1: icmp_seq=420 ttl=64 time=140 ms 64 bytes from 192.168.1.1: icmp_seq=421 ttl=64 time=296 ms 64 bytes from 192.168.1.1: icmp_seq=422 ttl=64 time=141 ms 64 bytes from 192.168.1.1: icmp_seq=423 ttl=64 time=856 ms 64 bytes from 192.168.1.1: icmp_seq=424 ttl=64 time=20.2 ms 64 bytes from 192.168.1.1: icmp_seq=425 ttl=64 time=36.7 ms 64 bytes from 192.168.1.1: icmp_seq=426 ttl=64 time=241 ms 64 bytes from 192.168.1.1: icmp_seq=427 ttl=64 time=1.91 ms 64 bytes from 192.168.1.1: icmp_seq=429 ttl=64 time=603 ms Den blå streken skal holde seg konstant på 1, men den svinger ned når ping går opp, over en periode på 1 minutt. Sånn er det selvsagt ikke hele tiden. Lenke til kommentar
Lycantrophe Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Hvilket nettverkskort (eller hovedkort) står i den? Lenke til kommentar
Emancipate Skrevet 12. februar 2015 Forfatter Del Skrevet 12. februar 2015 MSI H87I AC. Jeg tror faktisk at jeg skal teste med den andre PCen i morgen. Lenke til kommentar
Lycantrophe Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Hva sier lsmod? Du har en realtek-chip. Ikke rart du har problemer. Lenke til kommentar
Emancipate Skrevet 12. februar 2015 Forfatter Del Skrevet 12. februar 2015 (endret) Nei, jeg har intel. ~$ lsmod Module Size Used by ctr 13049 3 ccm 17773 3 cuse 13445 3 bnep 19624 2 rfcomm 69160 12 binfmt_misc 17468 1 nls_iso8859_1 12713 1 arc4 12608 2 snd_hda_codec_realtek 65580 1 snd_hda_codec_hdmi 46368 1 joydev 17332 0 hid_generic 12548 0 usbhid 48514 0 hid 106148 2 hid_generic,usbhid iwlmvm 189768 0 mac80211 638933 1 iwlmvm snd_hda_intel 52306 5 snd_hda_codec 192906 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel mxm_wmi 13021 0 snd_hwdep 13602 1 snd_hda_codec snd_pcm 102040 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel snd_page_alloc 18710 2 snd_pcm,snd_hda_intel x86_pkg_temp_thermal 14205 0 intel_powerclamp 14705 0 coretemp 13435 0 kvm_intel 143192 0 kvm 455718 1 kvm_intel snd_seq_midi 13324 0 snd_seq_midi_event 14899 1 snd_seq_midi snd_rawmidi 30095 1 snd_seq_midi snd_seq 61560 2 snd_seq_midi_event,snd_seq_midi crct10dif_pclmul 14250 0 crc32_pclmul 13113 0 ghash_clmulni_intel 13216 0 aesni_intel 55624 6 aes_x86_64 17131 1 aesni_intel snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi lrw 13286 1 aesni_intel gf128mul 14951 1 lrw glue_helper 13990 1 aesni_intel snd_timer 29433 2 snd_pcm,snd_seq ablk_helper 13597 1 aesni_intel cryptd 20359 3 ghash_clmulni_intel,aesni_intel,ablk_helper snd 69273 21 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_seq_midi iwlwifi 174028 1 iwlmvm cfg80211 496328 3 iwlwifi,mac80211,iwlmvm serio_raw 13413 0 lpc_ich 21080 0 i915 788204 5 btusb 28267 0 drm_kms_helper 55071 1 i915 bluetooth 395387 22 bnep,btusb,rfcomm drm 303102 4 i915,drm_kms_helper i2c_algo_bit 13413 1 i915 mei_me 18627 0 soundcore 12680 1 snd mei 82276 1 mei_me parport_pc 32701 0 ppdev 17671 0 nct6775 55222 0 hwmon_vid 12783 1 nct6775 lp 17759 0 parport 42299 3 lp,ppdev,parport_pc video 19476 1 i915 wmi 19177 1 mxm_wmi intel_smartconnect 12619 0 mac_hid 13205 0 psmouse 102569 0 ahci 25819 4 r8169 67581 0 libahci 32716 1 ahci mii 13934 1 r8169 Endret 12. februar 2015 av Emancipate Lenke til kommentar
Lycantrophe Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Right, det er wlan-kortet du bruker. Det er ikke en av disse der du må slå av n for å ikke få horribel ytelse? Lenke til kommentar
Lycantrophe Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1354975Ser ut til at du ikke er alene. Lenke til kommentar
007CD Skrevet 12. februar 2015 Del Skrevet 12. februar 2015 Det er ett Intel WiFi kort i allefall, siden det er en Intel driver som benyttes, iwlwifi. Men noe gjør at kortet deauthes i allefall, det er ikke en vanlig tilkoblings dropp som jeg ville tolket det. Enten er det kortet som har ett problem, ellers så er det routeren som er problemet. Bare for å ta noen generelle spørsmål bare for å få litt bakgrunnsinfo, hva er bosituasjonen din? Altså bor du i enebolig? Rekkehus? Bystrøk? ute på landet? Har du noen andre enheter som kommuniserer trådløst (Trådløse telefoner, babycalls etc) i nærheten? Mange nære naboer? Lenke til kommentar
Emancipate Skrevet 13. februar 2015 Forfatter Del Skrevet 13. februar 2015 Det er noen andre i nærheten, men ikke så nære. Men jeg har "mistet" 4GB ram også, så jeg tror jeg skal åpne PCen og se om det hjelper å trykke ting litt på plass. Lenke til kommentar
Emancipate Skrevet 14. februar 2015 Forfatter Del Skrevet 14. februar 2015 Jeg så problemet litt på en annen pc også, så jeg tror det er ruteren som er gåen. Jeg har bestilt ny. Lenke til kommentar
Emancipate Skrevet 25. februar 2015 Forfatter Del Skrevet 25. februar 2015 Salige kvakksalver, jeg har fortsatt problemer! Ingenting i dmesg. ~$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. ^C --- 192.168.1.1 ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 27001ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2914 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1919 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=931 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=3.72 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.44 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.96 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.97 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.34 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.46 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.46 ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.44 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.46 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.46 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.47 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.46 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.45 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.46 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.44 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.47 ms Lenke til kommentar
eriktar76 Skrevet 3. mars 2015 Del Skrevet 3. mars 2015 Har du faktiske problemer, eller måler du oppførsel med ping? Moderne wlan kort og aksesspunkt går gjerne i "power save" mode. Kan finne på å aggregere pakker før de sendes ut for å spare strøm. Dvs om nettet er tomt for trafikk annet enn din ping så kan det ta lang tid før den kommer ut på lufta. Kjører du trafikk samtidig så vil nettverkskortet ikke rekke å komme inn i power save og dermed har du god ping. Dvs har du gammel 11.b kort så vil du ha mer javn latency fordi det vil aldri gå i power save. Moderne 11ac og 11n vi så ofte som mulig gå i power save og dermed se dårligere ut. Test å sette opp iperf eller annet med en lav hastighet mellom pc1 og pc1 (UDP mode og 500kbit). Tipper at så lenge den strømmen går vil du aldri få dårlig ping. Lenke til kommentar
Emancipate Skrevet 3. mars 2015 Forfatter Del Skrevet 3. mars 2015 Har du faktiske problemer, eller måler du oppførsel med ping?Jeg har selvsagt problemer. Sider laster ikke inn, etc. Ta en titt på den blå linja i skjermskuddet over. Den måler ned-hastighet. Lenke til kommentar
eriktar76 Skrevet 3. mars 2015 Del Skrevet 3. mars 2015 Har du faktiske problemer, eller måler du oppførsel med ping?Jeg har selvsagt problemer. Sider laster ikke inn, etc. Ta en titt på den blå linja i skjermskuddet over. Den måler ned-hastighet. Der røyk teorien min. jaja. Lenke til kommentar
Emancipate Skrevet 3. mars 2015 Forfatter Del Skrevet 3. mars 2015 Men stort sett er det bedre. Lenke til kommentar
Emancipate Skrevet 15. mars 2015 Forfatter Del Skrevet 15. mars 2015 Kvaliteten hopper opp og ned raskt. Kjørt ca. med 1 sekunds mellomrom: ~$ iwconfig wlan0 | grep -i --color quality Link Quality=60/70 Signal level=-50 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=62/70 Signal level=-48 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=13/70 Signal level=-97 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=12/70 Signal level=-98 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=13/70 Signal level=-97 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=15/70 Signal level=-95 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=62/70 Signal level=-48 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=64/70 Signal level=-46 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=62/70 Signal level=-48 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=65/70 Signal level=-45 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=11/70 Signal level=-99 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=15/70 Signal level=-95 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=65/70 Signal level=-45 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=64/70 Signal level=-46 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=15/70 Signal level=-95 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=60/70 Signal level=-50 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=16/70 Signal level=-94 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=64/70 Signal level=-46 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=59/70 Signal level=-51 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=62/70 Signal level=-48 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=13/70 Signal level=-97 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=60/70 Signal level=-50 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=63/70 Signal level=-47 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=60/70 Signal level=-50 dBm ~$ iwconfig wlan0 | grep -i --color quality Link Quality=14/70 Signal level=-96 dBm ~$ Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå