Re: Terrible F25 WiFi Performance

Damn strange. The computer is in a static location for all tests. This is still using iperf in all cases, but abbreviated since I'm copying by hand. Each test is about five seconds apart. Fedora 25 live 58 Mbit/sec 61 41 Fedora 24 live 54 Mbit/sec 46 38 65 Fedora 25 installed 29 42 38 38 There

Confusing mockbuild error

Hi, I am trying to build the RPMs from the following repo: http://copr-dist-git.fedorainfracloud.org/cgit/jsouthworth/racket/racket.git I cloned it down, ran `spectool -g *.spec`, and then `fedpkg --release f24 mockbuild`. This last command gives the following output: Wrote: /rpms/racket/racket-

Re: avahi mdns configuration question.

On 11/01/17 11:54, Rick Stevens wrote: On 01/10/2017 09:58 PM, Robin Laing wrote: Hello, I am trying to get mdns to work on my local network. I want all the different computers to broadcast or at least allow their mdns host names to be found by the router. As more devices are appearing, I am

Re: Terrible F25 WiFi Performance

On 01/11/2017 07:12 PM, Chris Murphy wrote: I retested Fedora 25 to match the same kernel used by Rawhide, and I get: [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 49.9 MBytes 41.6 Mbits/sec Is that consistent on retries? I get really variable results on WiFi. I'd run th

Re: Terrible F25 WiFi Performance

OK so this is bat guano... Boot off Fedora-Workstation-Live-x86_64-Rawhide-20170110.n.0.iso USB stick and retest: [root@localhost liveuser]# iperf -c 10.0.0.3 Client connecting to 10.0.0.3, TCP port 5001 TCP window size: 85.0 KByte (de

Re: Terrible F25 WiFi Performance

On 01/11/2017 07:27 PM, Christopher wrote: On Wed, Jan 11, 2017 at 9:01 PM Gordon Messmer mailto:gordon.mess...@gmail.com>> wrote: Try enabling TX aggregation. This setting boosted my iperf results from 21M/s to 78M/s: # cat /etc/modprobe.d/iwlwifi.conf options iwlwifi 11n_d

Re: Terrible F25 WiFi Performance

On Wed, Jan 11, 2017 at 9:01 PM Gordon Messmer wrote: > Try enabling TX aggregation. This setting boosted my iperf results > from 21M/s to 78M/s: > > # cat /etc/modprobe.d/iwlwifi.conf > options iwlwifi 11n_disable=8 > > This had a negligible effect when I tried it. -- Christopher

Re: Terrible F25 WiFi Performance

Try enabling TX aggregation. This setting boosted my iperf results from 21M/s to 78M/s: # cat /etc/modprobe.d/iwlwifi.conf options iwlwifi 11n_disable=8 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@

Re: Terrible F25 WiFi Performance

$ ethtool -i wlo1 driver: iwlwifi version: 4.8.17-200.fc24.x86_64 firmware-version: 22.361476.0 expansion-rom-version: bus-info: :6c:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no $ lspci 6c:00.0 Network controller

Re: Terrible F25 WiFi Performance

the line starting with "A misconfigured firewall" lit up a red flash in my mind. Not only is my box just slow slow slow but I am now unable to connect to a secure server (one that requires a CA certificate) whereas with fedora 13 this was possible. How would I test for a firewall problem (have

Re: Terrible F25 WiFi Performance

On 01/11/2017 11:40 AM, Chris Murphy wrote: > On Wed, Jan 11, 2017 at 11:00 AM, Rick Stevens wrote: >> On 01/10/2017 07:30 PM, Chris Murphy wrote: >>> [chris@f25h Downloads]$ iperf -c 10.0.0.3 >>> >>> Client connecting to 10.0.0.3, TCP p

Re: powertop

On 01/11/2017 11:36 AM, Chris Murphy wrote: > On Wed, Jan 11, 2017 at 11:11 AM, Rick Stevens wrote: > > >> Try running with "--debug" set? > > Did that. No additional information. Also the audit log doesn't report > anything, no AVC denial either. The time stamp of the /var/cache files > change

Re: Terrible F25 WiFi Performance

On 01/11/2017 11:35 AM, Christopher wrote: > On Wed, Jan 11, 2017 at 1:01 PM Rick Stevens > wrote: > > On 01/10/2017 07:30 PM, Chris Murphy wrote: > > [chris@f25h Downloads]$ iperf -c 10.0.0.3 > > ---

Re: Terrible F25 WiFi Performance

On Wed, Jan 11, 2017 at 11:00 AM, Rick Stevens wrote: > On 01/10/2017 07:30 PM, Chris Murphy wrote: >> [chris@f25h Downloads]$ iperf -c 10.0.0.3 >> >> Client connecting to 10.0.0.3, TCP port 5001 >> TCP window size: 85.0 KByte (default)

Re: powertop

On Wed, Jan 11, 2017 at 11:11 AM, Rick Stevens wrote: > Try running with "--debug" set? Did that. No additional information. Also the audit log doesn't report anything, no AVC denial either. The time stamp of the /var/cache files changes to coincide with the powertop run, but still it's a zero

Re: Terrible F25 WiFi Performance

On Wed, Jan 11, 2017 at 1:01 PM Rick Stevens wrote: > On 01/10/2017 07:30 PM, Chris Murphy wrote: > > [chris@f25h Downloads]$ iperf -c 10.0.0.3 > > > > Client connecting to 10.0.0.3, TCP port 5001 > > TCP window size: 85.0 KByte (defaul

Re: powertop

On Wed, Jan 11, 2017 at 11:11 AM, Rick Stevens wrote: > On 01/11/2017 09:35 AM, Rami Rosen wrote: >> Hi Chris, >> I tried now first installing the powertop rpm and than running it, on >> a Fedora 25 x86_64 platform, and I get exactly the same results: >> ... >> ls /var/cache/power* -l >> total 0 >

Re: avahi mdns configuration question.

On 01/10/2017 09:58 PM, Robin Laing wrote: > Hello, > > I am trying to get mdns to work on my local network. I want all the > different computers to broadcast or at least allow their mdns host names > to be found by the router. > > As more devices are appearing, I am seeing them in the router li

Re: powertop

On 01/11/2017 09:35 AM, Rami Rosen wrote: > Hi Chris, > I tried now first installing the powertop rpm and than running it, on > a Fedora 25 x86_64 platform, and I get exactly the same results: > ... > ls /var/cache/power* -l > total 0 > -rw-r--r--. 1 root root 0 Jan 11 19:30 saved_parameters.powert

Re: Terrible F25 WiFi Performance

On 01/10/2017 07:30 PM, Chris Murphy wrote: > [chris@f25h Downloads]$ iperf -c 10.0.0.3 > > Client connecting to 10.0.0.3, TCP port 5001 > TCP window size: 85.0 KByte (default) > ---

Re: powertop

Hi Chris, I tried now first installing the powertop rpm and than running it, on a Fedora 25 x86_64 platform, and I get exactly the same results: ... ls /var/cache/power* -l total 0 -rw-r--r--. 1 root root 0 Jan 11 19:30 saved_parameters.powertop -rw-r--r--. 1 root root 0 Jan 11 19:30 saved_results.

powertop

[root at f25h ~]# ls -l /var/cache/powertop/ total 0 -rw-r--r--. 1 root root 0 Dec 29 14:49 saved_parameters.powertop -rw-r--r--. 1 root root 0 Dec 29 14:49 saved_results.powertop These files are always 0 length files. I'm not finding that any of the calibration runs I've done are actually getting