<Wizzup> freemangordon:
<Wizzup> Unpacking leste-config-common (1.88-1+m7.1) over (1.86-1+m7) ...
<Wizzup> Setting up leste-config-common (1.88-1+m7.1) ...
<Wizzup> Removing 'diversion of /etc/profile.d/xdg-runtime.sh to /etc/profile.d/xdg-runtime.sh.leste-orig by leste-config-common'
<Wizzup> Removing obsolete conffile /etc/profile.d/xdg-runtime.sh.leste ...
<Wizzup> seems like it does? or?
uvos__ has quit [Ping timeout: 240 seconds]
uvos__ has joined #maemo-leste
Daanct12 has joined #maemo-leste
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #maemo-leste
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
macros_2ndPC has quit [Ping timeout: 252 seconds]
macros_2ndPC has joined #maemo-leste
ceene has joined #maemo-leste
<freemangordon> Wizzup: yes, that's fine
maemish_ has joined #maemo-leste
mro has joined #maemo-leste
xmn has quit [Ping timeout: 250 seconds]
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
akossh has joined #maemo-leste
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
maemish_ has quit [Quit: Connection closed for inactivity]
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
<Wizzup> freemangordon: what I mean is that it does seem to remove the etc file
<Wizzup> or is the 'obsolete conffile' your echo?
* Wizzup checks
<Wizzup> ah, maintscript? never heard of it before
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
uvos__ has quit [Ping timeout: 248 seconds]
Twig has joined #maemo-leste
<buZz> ooooo, jabber works again \o/
<buZz> thanks!
uvos__ has joined #maemo-leste
norayr has joined #maemo-leste
<buZz> so some people overclocked SPI interfaces to cards here? what improvement in speeds did that give?
<Wizzup> tmlind: I made a ticket for your find fwiw https://github.com/maemo-leste/bugtracker/issues/704
mro has quit [Remote host closed the connection]
<uvos__> buZz: spi???
mro has joined #maemo-leste
<buZz> uvos__: the interface where SD is accessed over
<uvos__> lol
<uvos__> no
<uvos__> i mean you can access sdcards over spi
<uvos__> but no high performance device dose that
<uvos__> that mode is 2.5mb/s max
<uvos__> meanwhile
<uvos__> yes overclocking the bus gets you 40 ish mb/s read and write
<uvos__> on a fast sdcard
<uvos__> this is noticable when lanuching stuff
<buZz> with just plain SPI mode?
<uvos__> no
<uvos__> we dont use spi mode
<uvos__> forget about that
<uvos__> its only used by uc
<uvos__> we use 4bit wide path
mro has quit [Remote host closed the connection]
<buZz> ah alright
<buZz> can we overclock -that- ? :P
<uvos__> yes
<buZz> what speed benefits does it show?
<uvos__> 40ish mb/s
<uvos__> on a good sdcard
<buZz> vs?
<uvos__> 20
<buZz> nice, and you're describing d4?
<uvos__> n900 should be the same
<uvos__> same mmc controller
<buZz> :) nice, how can i enable that OC?
<uvos__> difference isten that great in real usage however, launching sutff ist faster
<uvos__> but no where near 2x
<uvos__> probubly cpu is limit
<uvos__> buZz: you have to hack the dirver atm
<buZz> aw :(
<uvos__> theres no easy way
<uvos__> i have been wanting to add as a sysfs option to force a freqency
<uvos__> but too mutch to do
mro has joined #maemo-leste
<buZz> i guess it improves throughput but not accesstimes?
<Wizzup> probably also improves access time a bit under load
norayr has left #maemo-leste [Disconnected: closed]
Daanct12 has quit [Quit: WeeChat 3.8]
norayr has joined #maemo-leste
ceene has quit [Ping timeout: 265 seconds]
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
uvos__ has quit [Ping timeout: 248 seconds]
uvos__ has joined #maemo-leste
<tmlind> Wizzup: thanks i should have filed the bug myself..
<Wizzup> np, it's good info
<Wizzup> I just don't have an immediate fix right away, but had a note to self not to forget about the find
<Wizzup> I did notice that on wifi the battery does drain a lot faster
<Wizzup> so if this is what causes it...
<Wizzup> oh wait
<Wizzup> I wonder if we can do this with sysctl
<Wizzup> maybe net.ipv4.neigh.default.interval_probe_time_ms
maemish_ has joined #maemo-leste
<Wizzup> (and net.ipv6.neigh.default.interval_probe_time_ms)
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
macros_ has joined #maemo-leste
xmn has joined #maemo-leste
macros_2ndPC has quit [Ping timeout: 252 seconds]
mro has quit [Remote host closed the connection]
norayr has joined #maemo-leste
mro has joined #maemo-leste
mro has quit [Remote host closed the connection]
uvos has joined #maemo-leste
<Wizzup> tmlind: putting this in /etc/sysctl.d/no_neigh.conf:
<Wizzup> net.ipv4.neigh.default.interval_probe_time_ms = -1
<Wizzup> net.ipv6.neigh.default.interval_probe_time_ms = -1
<Wizzup> makes them all -1 (2147483628)
<Wizzup> freemangordon: shall I add this to leste-config ?
<tmlind> Wizzup: no idea if that makes connecting to a network slower or something.. have not seen any issues here
<tmlind> i guess it's like arp related stuff, anybody know?
<bencoh> neigh/default/interval_probe_time_ms - INTEGER
<bencoh> The probe interval for neighbor entries with NTF_MANAGED flag, the min value is 1.
<bencoh> still trying to understand what this actually means
<Wizzup> I think it might be for p2p wifi stuff or something?
<tmlind> no idea if -1 makes any sense, value of 0 did not work via sysfs
<Wizzup> maybe we just increase it to like 300s or something
<bencoh> do we even have managed entries in a normal usecase (ie. without issueing ip neigh replace commands)?
* tmlind on d4 right now and not into browsing into the www currently
<bencoh> (stable's ip command has no support for that thing apparently btw)
<tmlind> maybe neigh is some arp like protocol?
<bencoh> we do have ip neigh (it's the replacement to the arp command indeed, meant to be used with ipv4 arp and ipv6 neigh), just no support for the "managed" flag
<tmlind> ok
<Wizzup> bencoh: ip neighbour did print some stuff on my laptop
<bencoh> Wizzup: with a managed flag?
<Wizzup> let me check
<Wizzup> not sure how to check
<bencoh> (it prints the arp/neighbour tables, basically)
<Wizzup> yeah
<Wizzup> don't know how to see if it is managed
<bencoh> me neither, but I don't think this version knows how to anyway
<tmlind> try arp -a or whatever the command is
<tmlind> and compare to ip neighbour?
<bencoh> afaiu the NTF_MANAGED flag allows the userspace to avoid some entries being evicted
<tmlind> arp -a -n
<tmlind> ip neigh show
<tmlind> i guess it shows the same results?
<bencoh> pretty much yeah
<bencoh> anyway, maybe this interval_probe_time_ms sets a timer independently of the fact that there is no managed entry
<bencoh> which would explain what you saw
<bencoh> my view on this is that it's useless on chimaera (with no compatible userspace to use it), so ... we can just set it to some insanely high value
<Wizzup> bencoh: ok, do we go for -insanely high- or just really high
<Wizzup> like, we can set it to once every 5 or 10 minutes and it won'r really impact pm
<bencoh> heh, I guess just really high would work :)
<Wizzup> or we can set it to many years :)
<bencoh> (between that and the memory pressure worker that woke up every now and then and destroyed idle efforts, it really feels like they hardly care for embedded / battery-powered sometimes ...)
<tmlind> yeah looking at powertop neigh still runs sometimes with -1
<Wizzup> tmlind: hm, with it set for everything?
<Wizzup> bencoh: they probably care but don't give it any thought
<freemangordon> Wizzup: no idea what this is about :)
<freemangordon> I mean - I have no clue what neigh is ;)
<freemangordon> will read about it, bit not now
<Wizzup> probably not too necessary
<Wizzup> tmlind: what is the process name in powertop
<freemangordon> is that some fancy name for ARP?
<bencoh> freemangordon: pretty much (it's more generic and is relevant for ipv6 as well)
<freemangordon> ok
<freemangordon> thanks
maemish_ has quit [Quit: Connection closed for inactivity]
<Wizzup> hm?
<freemangordon> the default values, iiuc
<Wizzup> I still see neigh_periodic_work
<Wizzup> with the time set to 2147483628 for all
<Wizzup> sysctl -a | grep neigh | grep interval_probe
<tmlind> Wizzup: yeah neigh_periodic_work or something in powertop
<Wizzup> there is also net.ipv4.neigh.default.gc_interval
<Wizzup> set to 30
<tmlind> no idea about that stuff
<freemangordon> pro1 is out of stock :(
xmn has quit [Ping timeout: 260 seconds]
k1r1t0_N900 has joined #maemo-leste
<Wizzup> freemangordon: I could try to send mine if you want one
k1r1t0_N900 has left #maemo-leste [#maemo-leste]
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: closed]
<freemangordon> well, I hope they will produce more
<freemangordon> will mail them asking what are the plans
norayr has joined #maemo-leste
arno11 has joined #maemo-leste
arno11 has quit [Quit: Lost terminal]
arno11 has joined #maemo-leste
uvos__ has quit [Ping timeout: 265 seconds]
arno11 has left #maemo-leste [#maemo-leste]
Twig has quit [Ping timeout: 246 seconds]
<uvos> so can i issue beowulf and chimara builds at the same time yet?
<uvos> or is this sill an issue
<Wizzup> I never had issues with it personally, but I recall you or fmg did a while ago
<uvos> both of us
<uvos> we had pacakges form chimeara ending up in beowulf
<uvos> but i gues for the kernel this dosent matter for once xD
<uvos> so maybe i should try it again...
<Wizzup> I'm sure if we need the kernel for beowulf at this point
<Wizzup> I'm not sure*
<uvos> i mean in the kernel case its essentaly free since it cant really cause any beowulf sepcific issues
<uvos> besides ci issues
<Wizzup> sure
<uvos> ok i will see what happens
<uvos> tmlinds idle test patch is included now
<uvos> btw
<Wizzup> ty
akossh has quit [Quit: Leaving.]
ikmaak has quit [Ping timeout: 252 seconds]
ikmaak has joined #maemo-leste
ikmaak has quit [Read error: Connection reset by peer]
ikmaak has joined #maemo-leste
uvos has quit [Ping timeout: 252 seconds]