| 02:56.47 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 03:14.04 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 03:45.36 | *** join/#maemo-ssu amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 05:22.12 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-50-29.residential.rdsnet.ro) |
| 05:58.49 | *** join/#maemo-ssu dhbiker (~dhbiker@APN-123-152-227-gprs.simobil.net) |
| 06:52.45 | *** join/#maemo-ssu LauRoman|Laptop (~LauRoman@5-14-50-29.residential.rdsnet.ro) |
| 07:07.58 | *** join/#maemo-ssu arcean (~arcean@aacz71.neoplus.adsl.tpnet.pl) |
| 07:09.39 | *** join/#maemo-ssu luf (~luf@80.188.29.62) |
| 07:26.44 | *** join/#maemo-ssu radekp (~radek@82.113.39.213) |
| 07:42.07 | *** join/#maemo-ssu kolp (~quassel@55d45acc.access.ecotel.net) |
| 09:01.28 | *** join/#maemo-ssu arcean_ (~arcean@aadb251.neoplus.adsl.tpnet.pl) |
| 10:11.29 | *** join/#maemo-ssu M13 (~MirandaLS@83.149.35.215) |
| 10:12.27 | *** join/#maemo-ssu M13 (~MirandaLS@83.149.35.215) |
| 11:52.54 | *** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 12:15.30 | *** join/#maemo-ssu NishanthMenon (~nmenon@nat/ti/x-llcancolbtnzigsj) |
| 12:59.13 | *** join/#maemo-ssu psycho_oreos (~tuxsavvy@unaffiliated/tuxsavvy) |
| 13:27.58 | *** join/#maemo-ssu psycho_oreos (~tuxsavvy@unaffiliated/tuxsavvy) |
| 14:13.44 | Pali | [16:07:43] <Pali> info about specific maemo kernel files: https://wiki.maemo.org/Porting/Kernel |
| 14:13.51 | Pali | this could be fixed in cssu userspace |
| 14:27.05 | *** join/#maemo-ssu psycho_oreos (~tuxsavvy@unaffiliated/tuxsavvy) |
| 15:57.15 | *** join/#maemo-ssu kolp (~quassel@55d45acc.access.ecotel.net) |
| 16:33.33 | freemangordon | Pali: give up on that patch already, lets simply fix osso-system-info and make all others use it :) |
| 16:43.39 | Pali | freemangordon: ok, but first I need to know what is correct place |
| 16:43.46 | Pali | where is stored board info |
| 17:08.55 | freemangordon | Pali: sure. I'll try to find time tomorrow to hack osso-system-info to not use hardcoded paths but a config file |
| 17:09.20 | Pali | anyway, there are more libs which using cpuinfo |
| 17:09.34 | Pali | look at that wiki page ^^^^^ |
| 17:11.03 | freemangordon | yep, and all of them should be fixed to use osso-system-info |
| 17:11.27 | freemangordon | now we have the same code spread all over the place |
| 17:13.05 | Pali | ok, good point |
| 17:15.09 | freemangordon | do we have a list? |
| 17:15.17 | freemangordon | I know about mce and ke-recv |
| 17:31.46 | Pali | do not know |
| 17:55.52 | *** join/#maemo-ssu sixwheeledbeast (~paul@host-78-150-232-16.as13285.net) |
| 18:02.39 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
| 18:11.30 | *** join/#maemo-ssu RedM (~redw@89-73-179-171.dynamic.chello.pl) |
| 18:27.07 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 18:57.44 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 19:03.08 | *** join/#maemo-ssu NishanthMenon (~nmenon@nat/ti/x-tixrrogcqibwgdkj) |
| 19:04.15 | *** join/#maemo-ssu cbeau (~cbeau@ebichu.roadcake.org) |
| 19:04.51 | cbeau | Anyone here using CSSU-testing? |
| 19:06.18 | cbeau | the N900 is my only phone right now so I can't have it go "weird". But I also would like to get CSSU-testing because changes are too slow to trickle into CSSU-stable (which I currently have)... any thoughts? |
| 19:16.46 | kerio | runs cssu-thumb+devel |
| 19:20.44 | Sicelo | cbeau: i do |
| 19:21.02 | Sicelo | zero complaints |
| 19:23.37 | cbeau | ah, nice to know. And since I've already got CSSU-stable, can I just install CSSU-testing or would I need to flash the device to switch to testing? |
| 19:24.09 | kerio | first, you make a full backup with backupmenu |
| 19:24.24 | kerio | then you just enable the cssu-testing repos and upgrade |
| 19:24.44 | cbeau | upgrade via HAM or apt-get upgrade ? |
| 19:25.36 | Sicelo | HAM is recommended .. (although i used apt) |
| 19:26.26 | cbeau | ah, alright. Thanks a lot! I'll maybe give it a try. I'm scared because this is my only phone and I really don't have time to spend fixing it if this goes badly |
| 19:26.36 | kerio | well |
| 19:26.47 | kerio | do you have COMBINED? |
| 19:27.05 | kerio | if you do, then if anything goes wrong it's just a matter of flashing combined, installing backupmenu and restoring the previously-made backup |
| 19:27.12 | cbeau | oh, not sure what COMBINED is so... i think not |
| 19:27.21 | kerio | the thing you flash |
| 19:27.39 | kerio | ~pr131 |
| 19:27.39 | infobot | methinks combined is the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin, or http://galif.eu/nokia/ |
| 19:28.20 | *** join/#maemo-ssu amizraa4 (~amizraa@gateway/tor-sasl/amizraa) |
| 19:28.39 | cbeau | oh dear... getting scary... has anyone done the stable to testing switch flawlessly through HAM with no need to fix anything (e..g. flash)? |
| 19:29.51 | Sicelo | cbeau: i did it via apt.. no fix needed. so HAM will be magnitudes safer |
| 19:30.09 | cbeau | ah, feeling a little better. thanks! |
| 19:30.42 | cbeau | my main motivation is that as soon as "wireless networking" gets "fixed" in testing (if ever) I'd wanna make sure I get that right away |
| 19:30.54 | Sicelo | what? |
| 19:30.55 | cbeau | I haven't had wireless working at my office since ages ago... |
| 19:31.23 | cbeau | It's not wireless altogether that I've got troubles with, just the MSCHAPv2 auth at my workplace that's not working. everything else is fine |
| 19:31.54 | Sicelo | not fixed. eapd is closed |
| 19:32.10 | cbeau | I can hack together manually using wpa-supplicant and get it to work, but the whole doig it manually business sucks |
| 19:32.27 | cbeau | what does "eapd is closed" mean? |
| 19:32.32 | Sicelo | yes, and not battery-friendly |
| 19:33.31 | Sicelo | closed-source, i meant... so no one can fix it .. it is the supplicant in maemo |
| 19:34.53 | Sicelo | cbeau:do you set the 'manual username' field for the wifi settings? |
| 19:35.35 | cbeau | oh, that's heart broken... no way it will ever get fixed then? :( |
| 19:36.07 | cbeau | yes, I do set the manual username, and with and without the domain attached, with @ or with \, i've tried all possible combinations of all the tricks ever reported to have worked for someone.. |
| 19:36.29 | Sicelo | ok. i'm in the same boat |
| 19:36.38 | cbeau | what's sad is that it used to work, and then it didn't anymore, and I have no idea why (i.e. is it some package I installed that did this?) |
| 19:36.57 | cbeau | yeah, it's a very sad boat to be on. stupid authentication protocol |
| 19:37.05 | Sicelo | your admins broke it |
| 19:37.53 | cbeau | well, they insist it's not them. And in fact they showed me the logs of the handshake and it's my phone that's messing up. that's clear. and the fact that it works with wpa-supplicant does suggest the problem's really at my end :( |
| 19:38.23 | Sicelo | tbh, N900 is 'right' to not connect (as sad as it is). it won't connect when something is wrong with their certificate |
| 19:39.04 | Sicelo | your admins are at fault (same issue at my organization) |
| 19:39.16 | cbeau | ah, really... because the IT people at my uni are pretty nice so if I could figure out what's wrong with what they do, Im sure they'd be happy to fix it... but that's a lot of work for me... not really time to do that |
| 19:39.41 | Sicelo | wpa_supplicant connects because it can skip cert verification. eapd will not do that |
| 19:40.16 | cbeau | but the certificate situation on N900 is a little weird: many can't be taken out, it's not always trivial to get new ones in manually... |
| 19:40.37 | cbeau | i keep wondering if my trouble is with the certificates or with the wireless protocol... |
| 19:40.41 | Sicelo | the problem cert is in the server :p |
| 19:41.31 | cbeau | in what sense... you mean that they've incorrectly setup their server cert for the wireless network or they've incorrectly set how the handshake and certificate exchange works? |
| 19:42.08 | Sicelo | just the certificate only that is problematic .. either it is missing some fields, or some other issue |
| 19:42.56 | Sicelo | if you have time, setup a FreeRadius server of your own, and configure it for MSCHAPv2 .. it will connect just fine |
| 19:43.24 | cbeau | "it will connect" meaning the n900? |
| 19:43.29 | Sicelo | yes |
| 19:44.03 | cbeau | ah, so here's a question: if I get my hands on their certificate, is there some way for me to know what is "wrong" with it so I could communicate that back to them? |
| 19:44.23 | Sicelo | my N900 doesn't conect on my organization's mschapv2 wifi, but on my freeradius can connect |
| 19:44.35 | Sicelo | unfortunately i can't help much there.. |
| 19:44.55 | cbeau | ah but you did, you suggested another avenue for me to look into. Tha's progress |
| 19:45.02 | cbeau | thanks! |
| 19:46.35 | cbeau | i love my n900 but there are two things bothering me now: the wireless situation and the fact that its cpu is getting on the old side... it'd like a bit more juice. But still there are absolutely no good replacement for it on the market. that's why I've got 2 and the second will be my backup when this one dies |
| 19:47.15 | Sicelo | http://lists.maemo.org/pipermail/maemo-users/2014-February/017369.html << might give you an idea what to look for in connection with the certificate |
| 19:48.35 | cbeau | tnx |
| 19:49.36 | Sicelo | for cpu, try thumb on your 2nd device and see if it performs better :) |
| 19:50.26 | Sicelo | others overclock, but there are differing views about the pros and cons |
| 19:50.44 | Sicelo | btw, maybe this convo should have moved to #maemo |
| 19:53.28 | kerio | holy shit you're worried about the cpu but not the nonexistance of ram? |
| 19:55.18 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-50-29.residential.rdsnet.ro) |
| 19:58.22 | freemangordon | Pali: I'm going to try to RE sscd, any hints? is there any x86 binary you're aware of, even not from Maemo |
| 19:59.21 | Pali | freemangordon: I do not know about any x86 sscd binary |
| 20:01.13 | Pali | freemangordon: anyway, see list what to RE: http://mg.pov.lt/maemo-irclog/#maemo.2014-08-23.log.html#t2014-08-23T15:49:43 |
| 20:02.38 | freemangordon | Pali: hmm, usb status plugin should be easy, what is the .so name? |
| 20:03.24 | Pali | freemangordon: /usr/lib/hildon-desktop/usb_plugin.so |
| 20:03.35 | Pali | package: hildon-status-bar-usb_2.1.99-25-12+0m5_armel.deb |
| 20:03.39 | freemangordon | thanks |
| 20:04.07 | Pali | it is armel only |
| 20:04.21 | freemangordon | yeah |
| 20:04.24 | Pali | second rtcom packages have also i386 binaries |
| 20:05.04 | Pali | and header C files are available in nokia-binaries repo |
| 20:05.32 | freemangordon | hmm, usb plugin is 22k, should be doable in a wek or so |
| 20:06.49 | Pali | and that two rtcom libraries? |
| 20:06.58 | Pali | how hard it is? |
| 20:07.34 | freemangordon | lemme check |
| 20:08.38 | freemangordon | libgtalk-plugin is 12k x86 binary, a piece of cake |
| 20:08.45 | freemangordon | I'll start with it |
| 20:09.31 | freemangordon | jabber plugin is 18k |
| 20:14.23 | *** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro) |
| 20:18.30 | *** join/#maemo-ssu LauRoman|Laptop (~LauRoman@5-14-50-29.residential.rdsnet.ro) |
| 20:21.24 | *** join/#maemo-ssu LauRoman|Laptop (~LauRoman@5-14-50-29.residential.rdsnet.ro) |
| 21:00.55 | sixwheeledbeast | jabber is annoying on maemo. no priority settings for a start |
| 21:13.45 | Pali | sixwheeledbeast: this is reason for RE |
| 21:13.53 | sixwheeledbeast | \o/ |
| 21:14.03 | kerio | freemangordon: did you get the leaked hex-rays for arm |
| 21:14.05 | Pali | see: http://mg.pov.lt/maemo-irclog/#maemo.2014-08-23.log.html#t2014-08-23T15:49:43 |
| 21:16.17 | freemangordon | kerio: no :( |
| 21:16.36 | freemangordon | is there leaked hexrays for ARM? |
| 21:16.55 | kerio | apparently! |
| 21:17.03 | kerio | can't remember who said so |
| 21:17.07 | kerio | here or in #maemo |
| 21:18.45 | freemangordon | kerio: please remember |
| 21:20.22 | *** join/#maemo-ssu merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 21:20.27 | kerio | just look for it on the internet gawd |
| 21:23.25 | kerio | it's on what.cd at the very least |
| 21:54.54 | sixwheeledbeast | while we are on about jabber did anyone find any more information about my availability not working issue? |
| 21:56.41 | Pali | sixwheeledbeast: what? |
| 21:58.15 | sixwheeledbeast | http://talk.maemo.org/showthread.php?t=93553 basically "my availability" doesn't work any more |
| 21:58.38 | sixwheeledbeast | so status message in jabber is blank. |
| 22:03.12 | Pali | I never used that function |
| 22:03.22 | Pali | maybe again some problem with certman/certificates? |
| 22:32.01 | sixwheeledbeast | Hmm, actually I found one that expired 24 october 2013 in certman. The thing is you can't change the time and date to test if it is the cert. |
| 22:33.19 | sixwheeledbeast | oh there's a valid duplicate self signed one with the same name |
| 22:38.30 | freemangordon | sixwheeledbeast: you can try to remove the expired one |
| 22:38.47 | freemangordon | with certman or whatever the binary name was |
| 22:39.07 | sixwheeledbeast | freemangordon: will that help? the certman app in settings? |
| 22:39.34 | freemangordon | hmm, I don;t think you can remove certificates from settings |
| 22:39.42 | freemangordon | certman is a CLI tool |
| 22:40.04 | freemangordon | hmm, wrong name, lemme try to find the correct one |
| 22:40.18 | freemangordon | sixwheeledbeast: cmcli |
| 22:40.33 | sixwheeledbeast | ah ok I can try it. |
| 22:41.07 | freemangordon | it should be in common-ca |
| 23:15.12 | sixwheeledbeast | it only shows one cert, the cmcli help file isn't great but I guess "cmcli -T common-ca -L" should show my two certs? |
| 23:17.24 | freemangordon | I think so |
| 23:18.03 | freemangordon | kerio: yep, there is leaked arm decompiler |
| 23:33.42 | *** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 23:34.44 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 23:41.28 | sixwheeledbeast | hmm, I can't seem to remove it. "cmcli -c common-ca -r <key number>" maybe I'll play about in the morning while awake. |
| 23:47.27 | freemangordon | YAY!!! ARM hexrays works :D |