| 01:13.38 | *** join/#maemo infobot (ibot@rikers.org) |
| 01:13.38 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 02:28.27 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 03:26.10 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 03:28.00 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 03:41.19 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 03:43.01 | *** join/#maemo MetalGearSolid (~MetalGear@unaffiliated/metalgearsolid) |
| 04:11.49 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:32.09 | Zungo | thanks maemo talk bot for emailing me a happy birthday |
| 04:32.10 | Zungo | :D |
| 04:32.19 | Zungo | hmm |
| 04:32.21 | Zungo | yesterday? |
| 04:32.24 | Zungo | oh nvm |
| 04:36.34 | *** join/#maemo jon_y (~enforcer@2001:e68:4075:41ab:f64d:30ff:fe63:5a5a) |
| 04:40.10 | *** join/#maemo APic (apic@apic.name) |
| 05:47.39 | *** join/#maemo pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
| 05:56.24 | *** join/#maemo pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
| 05:56.35 | *** join/#maemo hubutm20 (~hubutm20@109.166.137.90) |
| 06:26.22 | *** join/#maemo pigeon (~pigeon@150.101.116.163) |
| 07:06.40 | *** join/#maemo Kabouik (~kabouik@32.232.202.84.customer.cdi.no) |
| 07:39.37 | *** join/#maemo sfa (~sfa@108.89.35.42) |
| 07:55.48 | *** join/#maemo MetalGearSolid (~MetalGear@110.159.13.175) |
| 07:55.57 | *** join/#maemo MetalGearSolid (~MetalGear@unaffiliated/metalgearsolid) |
| 08:11.33 | *** join/#maemo xy2_ (~xy2_@2.245.16.93.rev.sfr.net) |
| 08:31.55 | *** join/#maemo florian (~fuchs@77.9.67.151) |
| 08:33.51 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 08:44.51 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 09:32.51 | *** join/#maemo florian (~fuchs@77.9.67.151) |
| 09:35.50 | *** join/#maemo xy2_ (~xy2_@2.245.16.93.rev.sfr.net) |
| 10:23.56 | *** join/#maemo shentey (~shentey@x4e340c3e.dyn.telefonica.de) |
| 10:30.36 | *** join/#maemo xy2_ (~xy2_@2.245.16.93.rev.sfr.net) |
| 10:45.07 | *** join/#maemo zGrr (~quassel@095160127104.warszawa.vectranet.pl) |
| 10:45.47 | zGrr | moin ;) |
| 10:57.40 | *** join/#maemo zGrr (~quassel@095160127104.warszawa.vectranet.pl) |
| 11:03.03 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 11:45.16 | *** join/#maemo zGrrr (~quassel@user-94-254-144-13.play-internet.pl) |
| 12:09.41 | *** join/#maemo shentey (~shentey@x55b15753.dyn.telefonica.de) |
| 12:16.19 | *** join/#maemo sunshavi (~user@181.64.192.207) |
| 12:24.32 | *** join/#maemo zGrr (~quassel@095160127104.warszawa.vectranet.pl) |
| 12:38.51 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 12:54.35 | *** join/#maemo shentey_ (~shentey@x55b155a3.dyn.telefonica.de) |
| 13:02.30 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 13:03.02 | *** join/#maemo shentey_ (~shentey@x55b155a3.dyn.telefonica.de) |
| 13:12.12 | *** join/#maemo mp107 (~mp107___@PC-109-125-232-42.wegrow.domtel.com.pl) |
| 13:26.12 | *** join/#maemo shentey (~shentey@x4e35021c.dyn.telefonica.de) |
| 15:42.02 | *** part/#maemo mp107 (~mp107___@PC-109-125-232-42.wegrow.domtel.com.pl) |
| 16:08.14 | *** join/#maemo florian_ (~fuchs@217.190.134.68) |
| 16:25.00 | *** join/#maemo capitanocrunch (~capitanoc@unaffiliated/capitanocrunch) |
| 16:28.03 | *** part/#maemo capitanocrunch (~capitanoc@unaffiliated/capitanocrunch) |
| 17:01.15 | dreamer | meuh, lost my n900 this weekend (still no clue how .. ) |
| 17:01.22 | dreamer | sad day :( |
| 17:03.44 | KotCzarny | ['] |
| 17:04.56 | Sicelo | didn't have smscon on it? |
| 17:07.27 | *** join/#maemo Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 17:10.19 | bencoh | :/ |
| 17:10.36 | *** join/#maemo mp107 (~mp107___@PC-109-125-232-42.wegrow.domtel.com.pl) |
| 17:11.37 | bencoh | meanwhile I'm glad to announce I have A2DP working between maemo5 and a bluez-alsa (bluez5/alsa plugin) device |
| 17:11.45 | bencoh | (with a slightly patched version of bluez-alsa) |
| 17:17.02 | *** join/#maemo drawkula (~username@p4FDDAC5F.dip0.t-ipconnect.de) |
| 17:19.34 | *** join/#maemo zGrr (~quassel@095160127104.warszawa.vectranet.pl) |
| 17:23.17 | *** join/#maemo M4rtinK (~M4rtinK@77.48.149.46) |
| 17:23.38 | Sicelo009N | n900 is source or sink |
| 17:25.03 | bencoh | source in that case |
| 17:27.10 | KotCzarny | i think inz was interested in such setup |
| 17:27.56 | bencoh | KotCzarny: being able to receive audio from n900 to linux box? |
| 17:27.57 | *** join/#maemo nincs__ (~ViBE@unaffiliated/vibe) |
| 17:28.32 | KotCzarny | hum |
| 17:28.45 | bencoh | or the other way around? |
| 17:31.37 | totalizator | I had it few years ago working almost ootb in Ubuntu, just a matter of config |
| 17:32.08 | totalizator | with pulse audio ofc |
| 17:33.00 | KotCzarny | evilaudio |
| 17:33.04 | bencoh | the good thing here is that it doesn't need PA on sink :) |
| 17:33.33 | KotCzarny | ahm, he needed n8x0 as a bt receiver |
| 17:33.45 | KotCzarny | so completely different. nvm |
| 17:42.22 | totalizator | troubleshooting time - my n900 battery is dying surprisingly fast and syslog is full of: "3422.782367 wlan0: driver reports beacon loss from AP cfuu87c - sending probe request" |
| 17:42.26 | totalizator | could this be the case? |
| 17:43.23 | KotCzarny | wifi noise? |
| 17:43.37 | totalizator | no idea |
| 17:43.46 | totalizator | and what you mean by that? |
| 17:43.50 | KotCzarny | nothing in top/powertop? |
| 17:44.02 | totalizator | nothing |
| 17:44.37 | KotCzarny | wifi noise == lots of activity on interface not directed to you, but disrupting/waking up the chip |
| 17:44.58 | KotCzarny | disable wifi? |
| 17:45.04 | KotCzarny | change channel? |
| 17:45.16 | totalizator | but originating from my network or not necessarily? |
| 17:45.31 | KotCzarny | not necessarily |
| 17:45.39 | totalizator | yep, when I disable wifi it's better (I guess) |
| 17:45.45 | bencoh | in your case it might very well be what's logged |
| 17:45.47 | KotCzarny | run kismet and see what's happening on your channel |
| 17:45.47 | totalizator | hence I'm asking what it means |
| 17:46.26 | bencoh | ie wl keeps reprobing AP and waking you up at the same time |
| 17:46.27 | totalizator | and I'm not using any IM on n900 |
| 17:46.39 | KotCzarny | im? |
| 17:47.06 | totalizator | instant messaging |
| 17:47.15 | KotCzarny | doesnt matter |
| 17:47.40 | KotCzarny | its not about your traffic |
| 17:48.08 | KotCzarny | its about your device waking up because losing sight of your ap due of interference on your wifi channel |
| 17:48.10 | totalizator | there is almost no other traffic on *my* network most of the day |
| 17:48.24 | KotCzarny | not your network, again |
| 17:48.50 | totalizator | sure, there is lots of other networks around |
| 17:49.10 | totalizator | and I believe the channel is set to non-overlapping one |
| 17:49.37 | totalizator | but it doesn't matter as there is so many other networks around utilizing almost every channels |
| 17:50.09 | KotCzarny | might be someone using illegal antennas with too much gain |
| 17:50.51 | totalizator | and all my other wifi devices are behaving quite ordinary |
| 17:51.25 | totalizator | then I have to test it some other place |
| 17:52.13 | totalizator | it's what I loved about my n900 - that it could stay idle for a few days without charging with wifi on |
| 17:52.21 | Sicelo009N | iirc, there's also a bug report somewhere for that, bugs.maemo.org |
| 17:52.58 | totalizator | yes, I saw that |
| 17:53.12 | totalizator | but there is no conclusion |
| 17:53.22 | Sicelo009N | if you think the problem is on N900 itself, have you tried rebooting? or unload/reload the driver? |
| 17:53.48 | totalizator | https://bugs.maemo.org/show_bug.cgi?id=6615 |
| 17:53.50 | povbot | 04Bug 6615: Battery Dies Under 6 Hours with Very Moderate Use (Static IP?) |
| 17:54.18 | totalizator | yes, I have rebooted it many times |
| 17:55.29 | totalizator | well, I guess I have to backup my sms db and reflash |
| 17:55.43 | totalizator | once/10 years won't hurt, huh? |
| 17:55.44 | KotCzarny | or just reboot? |
| 17:56.06 | totalizator | I did - it's the same spam in syslog |
| 17:56.11 | KotCzarny | hmm |
| 17:56.18 | KotCzarny | change wifi channel? |
| 17:57.17 | totalizator | I would rather not as my AP is tweaked hard to get maximum bandwidth |
| 17:57.37 | totalizator | but what I might actually try is to find my old Linksys router |
| 17:58.16 | totalizator | which I remember the 900 has been paired with most of the past years |
| 17:58.40 | Sicelo009N | if your N900 behaves fine in other networks, then of course you'll need to revisit your AP settings :) |
| 17:59.07 | Sicelo009N | just recently had to adjust DTIM on mine for example, and i see better results since |
| 18:02.23 | Sicelo009N | and can't you save the existing config on your ap before making adjustments such as suggested by KotCzarny? ;) |
| 18:03.07 | *** join/#maemo WeDeker (4e34667a@gateway/web/freenode/ip.78.52.102.122) |
| 18:05.15 | totalizator | I'll try but wifi in the city is like jungle survival ;) endless fighting for a non occupied channels |
| 18:06.49 | KotCzarny | it wouldnt be if all obeyed the law/regulations |
| 18:07.03 | KotCzarny | and not set wifi tx to the max by default |
| 18:07.41 | TheKit | does someone have newer glibc deb for Maemo? |
| 18:07.44 | KotCzarny | but hey, 'i have to have max bWwWWwww! no matter if i use it once a week, and otherwise it would spam overpowered beacons' |
| 18:07.56 | KotCzarny | thekit: need newer kernel first |
| 18:08.33 | TheKit | I don't have N900, so that's no the biggest issue :) |
| 18:08.36 | TheKit | *not |
| 18:09.11 | TheKit | I just found https://talk.maemo.org/showpost.php?p=1354484&postcount=29 this topic, but the links are dead |
| 18:09.20 | totalizator | well, the real issue is that at 2,4GHz you are unable to use max speed anyway if you are following the regulatory reqs |
| 18:10.14 | totalizator | 5GHz is a good solution as almost nobody is using it (around me) |
| 18:10.25 | KotCzarny | yeah. yet. |
| 18:11.05 | totalizator | even in the crowded places imho |
| 18:12.18 | KotCzarny | we are baking ourselves with e-m |
| 18:15.26 | totalizator | I don't want to start with that :D |
| 18:15.33 | KotCzarny | :) |
| 18:16.06 | KotCzarny | i have 1 or 2 neighbours with stronger signal than my tp-link router 2m away ;) |
| 18:16.38 | KotCzarny | so you know, if your wifi doesnt work as expected, it's.. people |
| 18:16.39 | totalizator | nevertheless I stopped carrying my phone in a pocket some time ago |
| 18:16.39 | KotCzarny | ;) |
| 18:16.57 | Sicelo | what do you do instead? |
| 18:17.24 | KotCzarny | me? ethernet cable |
| 18:17.27 | totalizator | in my backpack or ...outer pockets |
| 18:17.28 | KotCzarny | or usb |
| 18:18.03 | totalizator | yep, I could live without wifi - totally |
| 18:19.36 | totalizator | but I don't believe that any wireless device could be harmful when not with a direct contact to the body |
| 18:20.07 | totalizator | like ultra low signal phone sticked to your butt |
| 18:20.07 | KotCzarny | um, power is inversely proportional to distance^2 |
| 18:20.25 | KotCzarny | so the further away it is, the better, but still, if its strong to begin with.. ;) |
| 18:21.07 | KotCzarny | offtopic: internet radio browser addition in oscp is the best feature since make-rescursive-list |
| 18:21.21 | totalizator | hyhy :3 |
| 18:21.42 | totalizator | I agree! |
| 18:24.06 | totalizator | but mostly by the inclusion of the "top voted" category |
| 18:24.23 | KotCzarny | top click isnt bad too |
| 18:24.31 | KotCzarny | for something new |
| 18:27.19 | totalizator | well adding a few hard coded wouldn't hurt as well, huh? |
| 18:27.41 | KotCzarny | um, thats what ~/.fav-1.m3u etc are for |
| 18:27.54 | KotCzarny | and favX= in config too |
| 18:38.53 | *** join/#maemo nincs__ (~ViBE@unaffiliated/vibe) |
| 18:42.04 | DocScrutinizer05 | totalizator: ((and all my other wifi devices are behaving quite ordinary)) well, do your other devices use power saving mode aka PSM on wifi? or are they simply shutting down wifi completely as soon as you 'lock' them, or even are PCs or similar that have no issues with keeping wifi using a few watts of power? |
| 18:42.56 | DocScrutinizer05 | first of all make sure your PSM is set to a mode that works with your APN |
| 18:44.47 | DocScrutinizer05 | see >><Sicelo009N> just recently had to adjust DTIM on mine for example<< |
| 18:47.15 | totalizator | DocScrutinizer05: oh, I get it now |
| 18:47.23 | totalizator | thanks |
| 18:50.42 | DocScrutinizer05 | totalizator: WiFi sleeps 99% of time, and wakes e.f. once per second (DTIM time) to watch AP's beacon and a possible "wake up! I got data for you!" bit in that. When AP doesn't keep exact timing or somebody spams the beacons into illegibility, N900 needs to stay RX active 100% of time, which eats **huge** amounts of battery (simplified picture but gives you the basics) |
| 18:51.01 | totalizator | the only question is what and where would be "a mode that works with my AP" |
| 18:52.16 | DocScrutinizer05 | advanced in WiFi settings: "power savings mode" iirc |
| 18:52.17 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 18:52.32 | DocScrutinizer05 | none|min|max |
| 18:52.55 | *** part/#maemo WeDeker (4e34667a@gateway/web/freenode/ip.78.52.102.122) |
| 18:53.31 | totalizator | I will try |
| 18:53.35 | DocScrutinizer05 | and I suggest to keep TX at 100mW, it doesn't make a huge difference. The purpose of this setting is just for poor frenchmen who mustn't >10mW outdoors |
| 18:53.53 | totalizator | haha, ok |
| 18:54.52 | *** join/#maemo WeDeker (4e34667a@gateway/web/freenode/ip.78.52.102.122) |
| 18:56.04 | DocScrutinizer05 | I mean, 90mW (100 - 10) is sucking empty a full battery in sth like 50h, if your WLAN would send all the time, which it doesn't for sure |
| 18:57.14 | DocScrutinizer05 | it's WLAN RX that's known to be extremely power greedy |
| 18:58.16 | DocScrutinizer05 | and it's poorly working PSM in APs that causes exactly that |
| 18:59.19 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 18:59.23 | DocScrutinizer05 | plus you even got an indication: syslog is full of: "3422.782367 wlan0: driver reports beacon loss from AP cfuu87c - sending probe request" |
| 19:00.37 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 19:01.12 | DocScrutinizer05 | btw zzztop of course shows something: number of IRQ from WLAN |
| 19:01.17 | *** join/#maemo spiiroin (~spiiroin@87-93-126-159.bb.dnainternet.fi) |
| 19:02.07 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 19:03.37 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 19:05.07 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 19:05.09 | DocScrutinizer05 | and cmdline: wl12xx |
| 19:05.18 | DocScrutinizer05 | err |
| 19:05.22 | DocScrutinizer05 | and cmdline: <wl12xx> |
| 19:06.37 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 19:08.07 | *** join/#maemo pagurus (~user@p4FDC3E55.dip0.t-ipconnect.de) |
| 19:08.18 | DocScrutinizer05 | http://paste.opensuse.org/50263550 |
| 19:08.37 | totalizator | I will definitely try to solve and debug the issue as I see a great future ahead of my n900 ;) |
| 19:10.22 | DocScrutinizer05 | niote the "Average Current: 20 mA" from bq27200.sj which is the actual power consumption of my N900 while it's logged in to IRC and I'm logged in to it via ssh, all over WLAN |
| 19:12.04 | DocScrutinizer05 | TTE: 2083 minutes |
| 19:12.23 | DocScrutinizer05 | ~2083/60 |
| 19:12.23 | infobot | 34.716666666667 |
| 19:12.45 | DocScrutinizer05 | hours, with a 67% remaining charge |
| 19:12.56 | DocScrutinizer05 | 57%, sorry |
| 19:13.50 | DocScrutinizer05 | without IRC, it should do a week of standby while ssh over WLAN session established but idle |
| 19:16.38 | enyc | =) |
| 19:24.54 | totalizator | yup, that's what I want it to be |
| 19:36.12 | *** join/#maemo Sicelo009N (~sicelo@169.239.28.253) |
| 19:36.40 | *** join/#maemo Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 19:56.59 | *** join/#maemo WeDeKer (4e34667a@gateway/web/freenode/ip.78.52.102.122) |
| 20:14.18 | Sicelo | DocScrutinizer05: what is the meaning of the vol'try/non-vol fields in zzztop output, context switch section |
| 20:14.41 | KotCzarny | voluntary context switches? |
| 20:15.15 | KotCzarny | ie. how many times app given up the cpu control? |
| 20:15.26 | DocScrutinizer05 | preemtive/forced (by scheduler, due to e.g. timeslice expiry) versus voluntary task switching |
| 20:15.26 | KotCzarny | vs. forced taking control away |
| 20:15.44 | Sicelo | thanks. cool |
| 20:15.44 | DocScrutinizer05 | O'd guess |
| 20:15.49 | DocScrutinizer05 | I* |
| 20:16.30 | KotCzarny | if its high, there is probably lots of happening in the system |
| 20:16.50 | KotCzarny | which could result in high 'load' even with low cpu usage |
| 20:18.16 | DocScrutinizer05 | basically the voluntary context switches are same number as the events waking up a process |
| 20:20.12 | DocScrutinizer05 | forced aka non-voluntary context switches just mean the task is running longer than the scheduler's time slices, so they don't really count for how often the task got woken up, it stays "status: R-unning" when non-vol context switch happens to it |
| 20:21.51 | DocScrutinizer05 | a voluntary context switch otoh should mean the process/task left R status for going waiting for something, be it timer, completion of a poll() or wait() or whatever |
| 20:54.43 | *** join/#maemo Sicelo_ (~sicelo@unaffiliated/sicelo) |
| 20:55.03 | *** join/#maemo erstazi_ (~erstazi@unaffiliated/erstazi) |
| 20:56.12 | *** join/#maemo geaaru (~geaaru@host32-47-dynamic.45-213-r.retail.telecomitalia.it) |
| 21:23.39 | *** join/#maemo mp107 (~mp107@PC-109-125-232-42.wegrow.domtel.com.pl) |
| 22:18.37 | *** join/#maemo Zungo (~Arre@unaffiliated/juest) |
| 23:25.01 | *** join/#maemo auenfx4 (David@120.155.29.160) |