On 09/21/2016 12:07 AM, J. Roeleveld wrote:
>
> All those effects depend on your 3D GPU.
>
> The nouveau drivers don't fully support 3D (please correct me if I am wrong)
> due to Nvidia not being able (legally) to provide all the necessary specs.
> (This is Nvidias claim, I am not interested
On September 21, 2016 6:03:23 AM GMT+02:00, Daniel Frey
wrote:
>On 09/20/2016 08:26 PM, Kai Krakow wrote:
>>>
>>> I've noticed a couple more things. One is after resume from standby
>>> the plasma taskbar hangs at 100% cpu for 2-3 minutes, during which
>>> time you can't open
Am Tue, 20 Sep 2016 21:03:23 -0700
schrieb Daniel Frey :
> On 09/20/2016 08:26 PM, Kai Krakow wrote:
> >>
> >> I've noticed a couple more things. One is after resume from standby
> >> the plasma taskbar hangs at 100% cpu for 2-3 minutes, during which
> >> time you can't open
Hello!
I upgraded xorg to 1.18 and during that process also enabled
USE=wayland. However, I don't run a wayland session (this actually
doesn't seem to work with nvidia). I use sddm as the login manager, and
I'm running latest plasma 5.7. The system is booted with systemd.
I just came accross the
On 09/20/2016 08:26 PM, Kai Krakow wrote:
>>
>> I've noticed a couple more things. One is after resume from standby
>> the plasma taskbar hangs at 100% cpu for 2-3 minutes, during which
>> time you can't open the K menu, click on open programs in the task
>> bar or start any apps. The tray icons
Am Tue, 20 Sep 2016 06:08:31 -0700
schrieb Grant :
> [...]
> [...]
> >>
> >>
> >> It looks like the TCP Queuing spike itself was due to imapproxy
> >> which I've now disabled. I'll post more info as I gather it.
> >
> >
> > imapproxy was clearly affecting the TCP
Hi,
You should install plasma-desktop and use startkde in your ~/.xinitrc if
you do not use session manager.
Regards,
Alon
On 21 September 2016 at 06:46, Philip Webb wrote:
> I've got Gwenview to behave by installing Plasma-meta :
> Systemsettings shows up with adequate
Am Tue, 20 Sep 2016 05:42:01 -0700
schrieb Grant :
> >> A while back I was having networking issues. I eventually tried
> >> drastically lowering the MTU of all the systems onsite and the
> >> issues disappeared. I always thought the issue was due to the MTU
> >> on our
I've got Gwenview to behave by installing Plasma-meta :
Systemsettings shows up with adequate options & single-click is back,
as are the previews of pix on the folder icons.
I've been a happy user of Fluxbox for many years,
but am willing to see how well KDE 5 works in 2016 .
>From a raw command
Am Tue, 20 Sep 2016 08:13:49 -0700
schrieb Daniel Frey :
> On 09/19/2016 11:36 PM, Kai Krakow wrote:
> > Am Mon, 19 Sep 2016 20:05:19 -0700
> > schrieb Daniel Frey :
> >
> >> So, I have a week off and have time to mess around trying to
> >> upgrade to
On Tue Sep 20 07:52:58 2016, Todd Goodman wrote:
> MTU is per network interface but you really don't want to end up having
> your router fragment every IP packet because systems on your subnet are
> using a larger MTU.
>
> Todd
You will not fragment every packet, the PMTUd will do his job and
On Tue Sep 20 12:52:57 2016, Grant wrote:
> The spikes are taking place on my remote server but they seem to
> roughly coincide with user activity within my own network. My
> technical knowledge of networking internals is weak. Does anyone know
> which tool will tell me more about the
On Tuesday 20 Sep 2016 12:57:00 Grant wrote:
> > Leaving your MTU at the default ethernet size of 1500 on your PC/server
> > should not cause a problem for most day to day operations, because modern
> > end-point OS and network devices use Path MTU Detection. Problems will
> > arise when you come
> Leaving your MTU at the default ethernet size of 1500 on your PC/server should
> not cause a problem for most day to day operations, because modern end-point
> OS and network devices use Path MTU Detection. Problems will arise when you
> come across a misconfigured router/firewall/server
>>> My web server's response time for http requests skyrockets every
>>> weekday between about 9am and 5pm. I've gone over my munin
>>graphs
and
>>> the only one that really correlates well with the slowdown is
>>"TCP
>>> Queuing". It looks like I normally have about 400
On Tuesday 20 Sep 2016 19:38:02 David Haller wrote:
> Hello,
>
> On Tue, 20 Sep 2016, Grant wrote:
> >>>Strangely, I'm able to ping with that command even with a very high -s
> >>>value:
> >>>
> >>>$ ping -c 4 -M dont -s www.dslreports.com
> >>>PING www.dslreports.com (64.91.255.98)
On September 20, 2016 4:53:41 PM GMT+02:00, Grant wrote:
>> My web server's response time for http requests skyrockets every
>> weekday between about 9am and 5pm. I've gone over my munin
>graphs
>>>and
>> the only one that really correlates well with the
Hello,
On Tue, 20 Sep 2016, Grant wrote:
>>>Strangely, I'm able to ping with that command even with a very high -s value:
>>>
>>>$ ping -c 4 -M dont -s www.dslreports.com
>>>PING www.dslreports.com (64.91.255.98) (10027) bytes of data.
>>>10007 bytes from www.dslreports.com
On Tue, 20 Sep 2016 08:36:24 +0200
Kai Krakow wrote:
> There's kmix and there's the systray integrated mixer. Disable either
> one of them. With modern versions of plasma I prefer the plasma
> integrated mixer and uninstalled kmix.
>
> You can disable the other mixer in
>>Strangely, I'm able to ping with that command even with a very high -s value:
>>
>>$ ping -c 4 -M dont -s www.dslreports.com
>>PING www.dslreports.com (64.91.255.98) (10027) bytes of data.
>>10007 bytes from www.dslreports.com (64.91.255.98): icmp_seq=1 ttl=54
>>time=331 ms
>>10007
Hello,
On Tue, 20 Sep 2016, Grant wrote:
[..]
>> $ ping -n -c 1 -M dont -s 1465 www.dslreports.com
>> PING www.dslreports.com (64.91.255.98) 1465(1493) bytes of data.
>> 1473 bytes from 64.91.255.98: icmp_seq=1 ttl=51 time=137 ms
>>
>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>>> MTU is per network interface but you really don't want to end up having
>>> your router fragment every IP packet because systems on your subnet are
>>> using a larger MTU.
>>>
>>> Todd
>>
>>That makes sense. So in my case, I'm thinking 1492 MTU on every
>>interface in the network.
>>
>>So I'm
On 09/19/2016 11:36 PM, Kai Krakow wrote:
> Am Mon, 19 Sep 2016 20:05:19 -0700
> schrieb Daniel Frey :
>
>> So, I have a week off and have time to mess around trying to upgrade
>> to Plasma once again.
>>
>> I have got it mostly-somewhat upgraded, but I have two bizarre
>>
> My web server's response time for http requests skyrockets every
> weekday between about 9am and 5pm. I've gone over my munin graphs
>>and
> the only one that really correlates well with the slowdown is "TCP
> Queuing". It looks like I normally have about 400 packets per
Hello,
On Tue, 20 Sep 2016, Grant wrote:
>> MTU is per network interface but you really don't want to end up having
>> your router fragment every IP packet because systems on your subnet are
>> using a larger MTU.
>>
>> Todd
>
>That makes sense. So in my case, I'm thinking 1492 MTU on every
On September 20, 2016 2:38:03 AM GMT+02:00, Grant wrote:
My web server's response time for http requests skyrockets every
weekday between about 9am and 5pm. I've gone over my munin graphs
>and
the only one that really correlates well with the slowdown is "TCP
* Grant [160920 08:53]:
> >> > A while back I was having networking issues. I eventually tried
> >> > drastically lowering the MTU of all the systems onsite and the issues
> >> > disappeared. I always thought the issue was due to the MTU on our
> >> > modem/router. Today
My web server's response time for http requests skyrockets every
weekday between about 9am and 5pm. I've gone over my munin graphs and
the only one that really correlates well with the slowdown is "TCP
Queuing". It looks like I normally have about 400 packets per second
>> > A while back I was having networking issues. I eventually tried
>> > drastically lowering the MTU of all the systems onsite and the issues
>> > disappeared. I always thought the issue was due to the MTU on our
>> > modem/router. Today I read that AT DSL requires a 1492 MTU so I
>> >
>> A while back I was having networking issues. I eventually tried
>> drastically lowering the MTU of all the systems onsite and the issues
>> disappeared. I always thought the issue was due to the MTU on our
>> modem/router. Today I read that AT DSL requires a 1492 MTU so I
>> increased the
>> Rather than guess and take random values read on the net - measure it.
>>
>> Google calculate mtu - netgear and others show ways to test upstream to
>> get the ideal size using ping
>>
>> You are looking for the largest MTU value before fragmentation starts to
>> occur.
>
> See
* wabe [160919 20:50]:
> Grant wrote:
>
> > A while back I was having networking issues. I eventually tried
> > drastically lowering the MTU of all the systems onsite and the issues
> > disappeared. I always thought the issue was due to the MTU on our
On Monday 19 Sep 2016 21:28:25 Mick wrote:
> On Monday 19 Sep 2016 13:08:29 Mike Gilbert wrote:
--->8
> > The manpage seems to be incorrect; -B/--delete-bootnum does not take
> > any argument. Instead, you must specify the entry number using the -b
> > option.
Or you could say, with hindsight,
On Tue, 20 Sep 2016 08:41:56 +0200, Kai Krakow wrote:
> > What makes you think I didn't use -p? I have a cron job that runs
> > emerge -pXXX @world after syncing and mails me the output, and I
> > always use -a when running emerge in a shell.
>
> You could also try porticron... ;-)
I could but
On 09/19/2016 10:54 AM, Raymond Jennings wrote:
> Just curious, but how are gentoo's infra assets organized?
>
> Do you guys use VMs on top of hardware machines and whatnot?
>
> Reasons for asking:
>
> * general curiosity
> * wondering how a migration to use anongit.gentoo.org
>
Am Mon, 19 Sep 2016 21:17:36 +0100
schrieb Neil Bothwick :
> On Mon, 19 Sep 2016 13:01:39 -0400, Philip Webb wrote:
>
> > > I'm surprised you needed to jump through such hoops.
> > > I updated 2 stable systems to perl 5.22 last week
> > > and emerge @world took care of all
Am Mon, 19 Sep 2016 14:56:59 -0700
schrieb Grant :
> A while back I was having networking issues. I eventually tried
> drastically lowering the MTU of all the systems onsite and the issues
> disappeared. I always thought the issue was due to the MTU on our
> modem/router.
Am Mon, 19 Sep 2016 20:05:19 -0700
schrieb Daniel Frey :
> So, I have a week off and have time to mess around trying to upgrade
> to Plasma once again.
>
> I have got it mostly-somewhat upgraded, but I have two bizarre
> problems.
>
> The first one is I have two volume
38 matches
Mail list logo