| 00:23.52 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
| 00:38.55 | DocScrutinizer05 | ack |
| 00:47.15 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 00:55.03 | *** join/#maemo kiswe (~frochosk@50.28.130.186) |
| 00:55.03 | *** part/#maemo kiswe (~frochosk@50.28.130.186) |
| 01:27.02 | *** join/#maemo hurrian_ (~textual@112.210.151.206) |
| 01:58.29 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 02:34.25 | *** join/#maemo Kabouik- (~kabouik@236.34.200.37.customer.cdi.no) |
| 03:24.08 | jonwil | great, the site I am upliading CSSU-devel bits to has just gone down :( |
| 03:25.55 | *** join/#maemo merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 03:26.03 | jonwil | now its back :) |
| 03:52.16 | *** join/#maemo auenfx8 (~David@CPE-143-238-162-244.lns11.woo.bigpond.net.au) |
| 03:55.46 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 03:56.18 | *** join/#maemo auenf (~David@CPE-143-238-162-244.lns11.woo.bigpond.net.au) |
| 04:05.19 | *** join/#maemo deepy (deepy@wrongplanet/deepa) |
| 04:18.42 | *** join/#maemo deepy (deepy@wrongplanet/deepa) |
| 04:19.01 | sicelo | fmg is already doing some RE work around connui |
| 04:59.56 | jonwil | Yeah I am aware |
| 05:00.10 | jonwil | but that doesn't necessarily include the wlan bits |
| 05:28.04 | jonwil | ok, that's done everything I can for cssu-devel updating |
| 05:29.04 | jonwil | Some packages wouldn't compile properly and a couple wouldn't upload (need to find out from the right people how to get them to compile or upload properly) but all the ones that worked are in cssu-devel now |
| 05:30.23 | jonwil | http://talk.maemo.org/showthread.php?p=1537037#post1537037 |
| 05:38.14 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 05:41.39 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 05:42.48 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 06:36.16 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 07:04.52 | *** join/#maemo jon_y (~enforcer@2001:e68:4075:5ca0:f64d:30ff:fe63:5a5a) |
| 07:17.43 | sicelo | jonwil: what's new in microb-engine |
| 07:18.20 | jonwil | https://github.com/community-ssu/microb-engine/commit/ac5fdce5bc231334ca616461377daa7b8e2cfa63 |
| 07:18.24 | jonwil | That's the relavent commit |
| 07:18.33 | sicelo | thanks. |
| 07:19.05 | jonwil | Its a workaround for an issue with Google that Google knows about but hasn't fixed |
| 07:22.23 | jonwil | But yeah I have put everything into cssu-devel that I can (a couple things that I want to put there but cant compile or cant properly upload) |
| 07:30.08 | *** join/#maemo freemangordon_ (~ivo@195.128.225.2) |
| 07:31.42 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 08:18.54 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:20.24 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 08:27.49 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 08:38.41 | *** join/#maemo rhombus (~rhombus@remote.rl-institut.de) |
| 08:39.51 | rhombus | DocScrutinizer05: I have an update. Sorry I wasn't around last night, I had a long workday |
| 08:40.16 | rhombus | The battery is fine. I tested the phone with a standard USB charging device. It was fully charged in three hours :) |
| 08:40.21 | rhombus | But there are some issues |
| 08:40.58 | rhombus | One is that, when I disconnected the phone, I got the prompt asking me which USB mode I want to use, mass storage mode or pc-suite mode |
| 08:41.07 | rhombus | note: this was *after* disconnecting |
| 08:41.40 | rhombus | After this, the phone thought it was connected to USB in mass storage mode and there seemed to be no way to turn this off |
| 08:41.49 | rhombus | This meant I had no access to stored files |
| 08:42.09 | rhombus | The other issue I've noticed has to do with the FM radio function |
| 08:42.49 | rhombus | I installed the "C FM radio" app. I couldn't find the "FM radio" app, it must be in a repo I haven't added |
| 08:43.04 | rhombus | when I turn it on, it works -- but it also turns on Bluetooth |
| 08:43.51 | rhombus | If I turn Bluetooth off, the radio stops working. The app runs, but I don't hear anything. Turning Bluetooth on again has no effect. Nor does restarting the app. The only solution is to reboot the phone. |
| 08:44.18 | rhombus | Is this normal behaviour? Are the Bluetooth and FM receivers linked somehow? |
| 08:44.50 | rhombus | So -- in both cases, the only solution was to reboot the phone. Doesn't sound right to me. |
| 08:44.53 | rhombus | End of update :) |
| 08:45.35 | bencoh | bluetooth/fm sit on the same chip |
| 08:45.59 | rhombus | bencoh: so they both have to be on for FM to work? |
| 08:46.10 | bencoh | regarding usb you have to select "pc-suite" if you want to access user data with usb plugged in |
| 08:46.34 | bencoh | but the fact that it prompted you after disconnecting is strange |
| 08:46.38 | rhombus | bencoh: ok, that makes sense, but the primary issue is that I am only presented this prompt when I disconnect the phone from the charger |
| 08:46.46 | rhombus | bencoh: yes, strange :) |
| 08:46.56 | bencoh | well, unless ... |
| 08:47.06 | rhombus | bencoh: it's possible it was in the background when I plugged in the phone |
| 08:47.16 | rhombus | and then jumped to foreground when I disconnected |
| 08:47.21 | rhombus | I would have to experiment with it |
| 08:53.24 | rhombus | bencoh: well, unless? |
| 08:54.39 | *** join/#maemo jkepler1 (~Thunderbi@2a01:e35:2f37:400:224:d7ff:feaa:82a8) |
| 08:54.50 | *** join/#maemo Kabouik (~kabouik@158.38.1.70) |
| 08:55.43 | rhombus | What I also find strange is that it says "charging only" -- which implies that nothing is mounted. And yet I can't access storage. This was a dumb charger anyway, there's nothing (at least, that I know of! Hello NSA) in the charger that could mount the storage. I just want the juice... |
| 09:09.02 | KotCzarny | is that behaviour repeatable? |
| 09:09.28 | KotCzarny | maybe the charger you use simulates (or has) computer inside? |
| 09:09.53 | *** join/#maemo eMHa (~mh@2a02:788:113:142:d6be:d9ff:fe2b:f21b) |
| 09:09.58 | KotCzarny | also, your ac-2e seems fake, because it is barrel plug, not microusb |
| 09:10.08 | KotCzarny | so someone either modified or refurbished it |
| 09:15.50 | Vajb | i have same issue sometimes. I think it matters of the angle in which u insert charger |
| 09:16.08 | KotCzarny | uh, oh, sounds like a recipe for broken usb port |
| 09:16.12 | Vajb | solution is to plug charger to phone and then to mains |
| 09:17.03 | *** join/#maemo ecc3g (~eccerr0r@2602:46:3913:b400:5054:ff:fe37:7e04) |
| 09:17.17 | Vajb | also if ur phone thinks it is connected to charger or usb host. U can use usb-host-mode to reset the state |
| 09:17.29 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 09:17.55 | Vajb | but in my case i've had that prompt only when inserting charger |
| 09:22.07 | rhombus | KotCzarny: Have you seen my AC-2E? |
| 09:22.21 | KotCzarny | nope, but every ac-2e in google has barrel plug |
| 09:23.02 | rhombus | KotCzarny: I don't quite understand how it follows from that that it is a fake :) |
| 09:23.06 | rhombus | KotCzarny: It is probably just old |
| 09:23.14 | Vajb | one of my n900 came with barrel to micro-usb adapter |
| 09:23.27 | KotCzarny | fake as in 'somone had a charger and replaced the cable' |
| 09:23.37 | rhombus | Remember, the legislation to require USB charging was only introduced in 2011 |
| 09:23.44 | rhombus | KotCzarny: No. |
| 09:24.04 | rhombus | KotCzarny: The design is totally consistent with prior Nokia charger designs |
| 09:24.12 | KotCzarny | would be interesting to see what is resistance between data pins on it |
| 09:24.30 | rhombus | Yes, I need to start equipping my toolbox, starting with a good multimeter |
| 09:24.50 | Vajb | maybe Nokia just had left over stock of those charger bodies and just used them with new cables? |
| 09:25.44 | rhombus | Vajb: new cables? It's just a Nokia standard barrel plug. It goes into a Nokia branded adapter block, which has a micro USB connector on the end |
| 09:26.22 | KotCzarny | sure, but when n900 was released standard was there already, and i'm almost 100% none of n900 were shipped with anything weaker than 900-1000mA |
| 09:26.35 | rhombus | There's nothing unusual about this, the manufacturers were legally required (in Europe) beginning in 2011 to provide standardized USB charging capability. You're not just going to throw out all of your old stock. |
| 09:27.31 | rhombus | KotCzarny: I have a complete original box with all the parts including the operating manual, warranty card, etc. When I get home tonight, I'll look and see if there is a packing list. |
| 09:27.58 | KotCzarny | and there is a chance that charger is noncomformant to it, hence, with updated bme-replacement in cssu it set max charging to 100mA |
| 09:28.33 | rhombus | KotCzarny: That is very possible. It was indeed strange that it coincidentally stopped working after the update. |
| 09:29.01 | KotCzarny | did you try your wife's charger? |
| 09:29.02 | rhombus | I have to admit it struck me as peculiar that the charger was so small for such an obviously power hungry phone |
| 09:29.35 | rhombus | KotCzarny: Yes, she has a generic white USB charger that she uses for charging her iPhone and iPad |
| 09:29.57 | KotCzarny | so at least you can use it as a fallback |
| 09:30.01 | KotCzarny | :) |
| 09:30.01 | rhombus | It worked wonderfully, the phone was charged in three hours. Apart from the issue with the USB mode locking my storage, of course :) |
| 09:30.12 | rhombus | KotCzarny: Yes, I'm going to purchase a similar charger |
| 09:30.23 | Vajb | didn't ianything have it's own istandard... |
| 09:30.49 | sixwheeledbeast | I have seen two N900 with the Nokia barrel to uUSB adaptor, I don't know of a Nokia barrel charger that outputs 1A. |
| 09:30.50 | rhombus | Vajb: it's not an Apple charger |
| 09:31.01 | Vajb | ah |
| 09:31.03 | rhombus | Vajb: also, standards compliance for chargers is required by law |
| 09:31.09 | sixwheeledbeast | Standards only work if companies adhere to them. |
| 09:31.11 | Vajb | charger with many plugs? |
| 09:31.22 | rhombus | Vajb: charger with one USB port :) |
| 09:31.29 | KotCzarny | swb: ac-4e (or ac-4u) for example |
| 09:31.41 | KotCzarny | 890mA with barrel plug |
| 09:31.41 | Vajb | ah of course |
| 09:31.42 | rhombus | sixwheeledbeast: yes, the charger is small and lightweight. It did strike me as strange. |
| 09:32.01 | KotCzarny | (from my n800) |
| 09:32.14 | rhombus | sixwheeledbeast: standards compliance mandated by law is different :) |
| 09:32.32 | rhombus | in any event, the charger works both for her iPhone and my N900 :) |
| 09:32.44 | rhombus | (afk) |
| 09:33.00 | KotCzarny | i suspect that barrel-to-usb adapter might have something on data pins |
| 09:33.31 | Vajb | i can try and measure |
| 09:33.45 | Vajb | i have multimeter plus said adapter |
| 09:34.56 | KotCzarny | you might try to open it too if you arent attached to it |
| 09:36.04 | Vajb | oh yes, wonderfull way to split my fingers too =) |
| 09:37.04 | KotCzarny | for science! |
| 09:37.06 | KotCzarny | ;) |
| 09:37.12 | Vajb | i'll go by measure first |
| 09:37.31 | Vajb | i just need to search for schematics for the plug |
| 09:38.06 | Vajb | i vaguely recall that furthest were data + and -,but... |
| 09:38.50 | KotCzarny | http://pinouts.ru/PortableDevices/micro_usb_pinout.shtml |
| 09:38.59 | KotCzarny | or just http://pinouts.ru/visual/micro_usb.jpg |
| 10:05.13 | rhombus | Vajb: how do I reset usb mode from the console? In case I have this hangup business again. Or do I just use mount? |
| 10:05.16 | rhombus | (afk) |
| 10:36.49 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 10:42.22 | *** join/#maemo Vajb (~Vajb@85-76-75-125-nat.elisa-mobile.fi) |
| 10:53.42 | DocScrutinizer05 | USB host detected when UNplugging happens sometimes. It's a race. Just plug+znplug again |
| 10:58.59 | DocScrutinizer05 | rhombus: you should have mentioned the barrel->usb adapter earlier :-P Yes they came with N900, and they are deprecated since they can't do the needed 900mA and _may_ catch fire X-P |
| 10:59.34 | KotCzarny | oh, so he has barrel adapter? |
| 10:59.35 | KotCzarny | o.O |
| 11:00.03 | *** join/#maemo saponga (~saponga@179-197-136-242.user.veloxzone.com.br) |
| 11:00.04 | KotCzarny | where did he mention that? |
| 11:00.46 | DocScrutinizer05 | but I can see how KotCzarny gave you no chance to mention the edapter, being too busy to suggest nonsense to you |
| 11:01.32 | KotCzarny | it was vajb mentioning it |
| 11:01.46 | sicelo | heh you two |
| 11:02.58 | rhombus | I mentioned yesterday that I have an AC-2E |
| 11:03.05 | rhombus | which I believe came only with a barrel connector |
| 11:05.16 | DocScrutinizer05 | [2017-10-17 Tue 11:25:44] <rhombus> Vajb: new cables? It's just a Nokia standard barrel plug. It goes into a Nokia branded adapter block, which has a micro USB connector on the end |
| 11:06.01 | KotCzarny | must have been flooded by output from other channels, oh well |
| 11:06.06 | KotCzarny | still, one mystery less |
| 11:06.19 | DocScrutinizer05 | for FM: you need wired headset plugged in to have an antenna |
| 11:06.49 | DocScrutinizer05 | KotCzarny: or flooded by own posts |
| 11:10.36 | DocScrutinizer05 | and I can only hiess how miuch noise came from users that are on ignore here |
| 11:10.41 | DocScrutinizer05 | guess* |
| 11:10.55 | rhombus | DocScrutinizer05: I had a wired headset plugged in :) |
| 11:11.15 | DocScrutinizer05 | then please re-iterate the problem |
| 11:11.24 | DocScrutinizer05 | I failed to get it |
| 11:11.47 | KotCzarny | rhombus: http://maemo.org/packages/view/fmradio/ |
| 11:11.52 | KotCzarny | it's in extras |
| 11:12.15 | rhombus | DocScrutinizer05: I installed C FM radio. When I start the app, it turns Bluetooth on |
| 11:12.28 | DocScrutinizer05 | normal |
| 11:12.29 | rhombus | I can hear radio |
| 11:12.37 | DocScrutinizer05 | fine |
| 11:12.38 | rhombus | If I turn Bluetooth off, then the radio goes silent |
| 11:12.44 | DocScrutinizer05 | normal |
| 11:12.53 | rhombus | If I turn Bluetooth back on... no effect. Radio is still silent. |
| 11:13.00 | DocScrutinizer05 | normal |
| 11:13.05 | rhombus | Closing and reopening the app does not help |
| 11:13.14 | rhombus | the only thing that makes radio audible again is rebooting the phone |
| 11:13.34 | rhombus | Ok, so you are saying that the FM receiver only works if Bluetooth is on. |
| 11:13.34 | DocScrutinizer05 | yeah, not exactly normal but somewhat expected |
| 11:13.54 | DocScrutinizer05 | you're not supposed to shut down BT when FM |
| 11:13.59 | rhombus | That's unfortunate. Bluetooth consumes power |
| 11:14.01 | DocScrutinizer05 | they share one chip |
| 11:14.10 | DocScrutinizer05 | no, not realy |
| 11:14.27 | rhombus | Ok, well, if I know that, then I will leave it on next time |
| 11:14.44 | rhombus | But it shouldn't require a reboot of the phone to restore normal operation :) |
| 11:15.07 | DocScrutinizer05 | the audio routing is a tad fragile |
| 11:15.23 | rhombus | Was this always the case, or does it have to do with CSSU? |
| 11:15.48 | DocScrutinizer05 | when you reboot with wired headset, or plug in wired headset while BT headset enabled, you may see weird results |
| 11:16.11 | DocScrutinizer05 | same for shutting down BT while wired headset plugged in |
| 11:16.38 | DocScrutinizer05 | it's a sw flaw |
| 11:16.59 | DocScrutinizer05 | always was like that |
| 11:18.23 | rhombus | Ah. (Just fyi, I was not using a BT headset :) ) |
| 11:18.30 | rhombus | (afk) |
| 11:19.04 | DocScrutinizer05 | but usually that's no problem. The real flaw is that it shows "BT enabled" when you only start radio, since what it does is power up the chip but not exactly enable BT afaik |
| 11:21.37 | sicelo | bt is enabled in the real sense :-) |
| 11:21.49 | DocScrutinizer05 | possible |
| 11:22.02 | DocScrutinizer05 | I never *really* inverstigated |
| 11:22.11 | sicelo | it is |
| 11:22.26 | sicelo | pycage evidently also got inside info (from nokia) |
| 11:22.38 | KotCzarny | not good in the light of recent bt exploits |
| 11:23.41 | sicelo | you turn off the radio is you want to be safe :-) |
| 11:23.42 | DocScrutinizer05 | what's pycage? |
| 11:24.16 | DocScrutinizer05 | and how is it related? |
| 11:24.26 | sicelo | Martin Grimme, iirc |
| 11:24.35 | DocScrutinizer05 | hm? |
| 11:25.38 | sicelo | i believe he was the first to develop fm radio application for N900 |
| 11:27.12 | sicelo | tl;dr .. the radio & bt are on same chip. hence the need for bt to be on when fm radio on |
| 11:27.52 | DocScrutinizer05 | that's what I said, yes |
| 11:31.09 | DocScrutinizer05 | rhombus: you seem to have a very early device given you got that adapter. You should find out about your hw version (2010, 2101...) in case you need it |
| 11:35.19 | DocScrutinizer05 | rhombus: flasher can tell you, and did tell you |
| 11:35.40 | DocScrutinizer05 | though I bet there are other ways to find out about hw rev |
| 11:41.21 | DocScrutinizer05 | anyway Neo900 has FM RX on FM TX chip |
| 11:43.28 | DocScrutinizer05 | which seems more natural as well |
| 11:45.49 | rhombus | DocScrutinizer05: makes sense |
| 11:46.51 | rhombus | I didn't save flasher's output, unfortunately |
| 11:47.58 | rhombus | I have to stay focused, so I'm going to sign off for now, but perhaps I will be on in the evening. Thanks for the help thus far. |
| 11:48.36 | DocScrutinizer05 | http://paste.opensuse.org/98288505 |
| 11:59.21 | *** join/#maemo louisdk (~louisdk@5.103.138.205) |
| 12:20.06 | *** join/#maemo xy2_ (~xy2_@217.109.44.189) |
| 12:52.57 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 13:30.15 | *** join/#maemo eMHa (~mh@p200300738E0CE800267703FFFE6CC360.dip0.t-ipconnect.de) |
| 13:47.57 | *** join/#maemo NotKit (~nekit@85-95-189-164.saransk.ru) |
| 14:30.57 | timeless | hey DocScrutinizer05 |
| 14:31.01 | timeless | has an unfortunate problem |
| 14:31.14 | timeless | i made the mistake of using a non low numbered uid for a system service |
| 14:31.29 | timeless | it turns out that systemd gives special protection to lower numbered uids |
| 14:31.40 | KotCzarny | remove systemd, problem solved |
| 14:31.46 | timeless | yeah, thanks |
| 14:32.04 | timeless | so, i'd like to transition from the non lower numbered uid to a low numbered uid |
| 14:32.17 | timeless | but i don't want the system to have much downtime if i can avoid it |
| 14:32.51 | timeless | assuming that task has a distinct uid+gid pair that's only used for itself, and that all files are 066x |
| 14:33.32 | timeless | can i cheat by changing the uid to the new low number, leaving the service as a member of the old high number gid, and then chown all files to the low numbered gid? |
| 14:33.45 | timeless | (restarting before the chown) |
| 14:34.16 | KotCzarny | on a normal system it could work, but who knows what systemd would do.. |
| 14:34.36 | timeless | and then similarly change the service to default to the corresponding low numbered gid (but still being a member of the high numbered group), restart, and then chgrp ... ? |
| 14:34.54 | timeless | does that seem like the "simplest" approach? |
| 14:35.16 | timeless | perhaps not "simplest" but a way that's easy to understand and should limit downtime for my system |
| 14:51.19 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 14:52.01 | *** join/#maemo Kabouik- (~kabouik@236.34.200.37.customer.cdi.no) |
| 15:06.07 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 15:15.33 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:30.42 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 16:15.52 | *** join/#maemo badcloud- (~halav@77.139.255.186) |
| 16:24.50 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 17:19.06 | *** join/#maemo sunshavi (~user@190.234.106.7) |
| 17:19.51 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 17:21.43 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 17:35.13 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 17:41.24 | *** join/#maemo Kabouik_ (~kabouik@ks3100825.kimsufi.com) |
| 17:47.52 | *** join/#maemo jkepler (~Thunderbi@gateway/vpn/privateinternetaccess/jkepler) |
| 18:09.35 | Pali | hello, has somebody checked if n900 is affected by current security problem found in wpa implementation handling? |
| 18:10.27 | Pali | Maemo on N900 does not use wpa_supplicant, but instead use two daemons, wlancond and eapd, first implements wpa part and is open source, second implements eap part and is closed |
| 18:10.54 | KotCzarny | word is, if they kept to specs, it's vulnerable |
| 18:11.14 | Pali | fix is backward compatible with spec |
| 18:11.30 | Pali | just to refuse reusing same nonce |
| 18:11.41 | Pali | here is source of wlancond: https://github.com/community-ssu/osso-wlan |
| 18:13.53 | Pali | basically wifi on Maemo is handled differently as in whole Linux world, Nokia wrote own software for it... |
| 18:14.24 | KotCzarny | as did cisco. and they are vulnerable |
| 18:14.40 | KotCzarny | same with *bsd folks |
| 18:30.20 | *** join/#maemo badcloud- (~halav@77.139.255.186) |
| 18:35.52 | DocScrutinizer05 | Pali: we discussed it yesterday. It wasn't clear where WPA gets handled, yesterday conculsion was it must be in eapd or osso-wlan-security |
| 18:37.29 | Pali | eapd = osso-wlan-security |
| 18:37.54 | Pali | wlancond = osso-wlan |
| 18:40.26 | DocScrutinizer05 | see what jonwil said |
| 18:40.47 | DocScrutinizer05 | maybe replace that stuff by wpa-supplicant et al then? |
| 18:42.09 | DocScrutinizer05 | my personal take on it: should be easy enough to just replace osso-wlan-security by wpa-supplicant |
| 18:43.23 | DocScrutinizer05 | probably now (after 7(?) years?) wpa-supplicant is better and more versatile than osso-wlan-security, unlike back when Nokia made osso-wlan-security |
| 18:44.34 | DocScrutinizer05 | I seem to recall wpa-supplicant was just a pile of segfaulting Sh* back when |
| 18:45.42 | DocScrutinizer05 | which is most likely _one_ of the reasons why Nokia cooked their own |
| 18:47.02 | DocScrutinizer05 | also WOW @ https://github.com/community-ssu/osso-wlan - I thought that was a blob too |
| 18:48.33 | DocScrutinizer05 | HMMMM https://github.com/community-ssu/osso-wlan/blob/master/wpa.c |
| 18:50.34 | DocScrutinizer05 | gosh!!! I *HATE* how github (in konqueror) eats one i5 core for 6s to render any scrolling |
| 18:50.49 | DocScrutinizer05 | JS crap |
| 18:57.50 | DocScrutinizer05 | you know I also hate stuff like value = key_mgmt != 0 || (encryption & WLANCOND_ENCRYPT_METHOD_MASK) == WLANCOND_WEP; |
| 19:01.22 | DocScrutinizer05 | immediately fllowed by the other extreme: http://paste.opensuse.org/68253426 |
| 19:06.25 | *** join/#maemo NeKit (~nekit@85-95-189-164.saransk.ru) |
| 19:09.10 | DocScrutinizer05 | hmm, no real crypto stuff in https://github.com/community-ssu/osso-wlan/blob/master/wpa.c |
| 19:11.21 | DocScrutinizer05 | neither protocol stuff |
| 19:11.32 | DocScrutinizer05 | aiui |
| 19:36.33 | Pali | crypto is done in kernel/hardware |
| 19:36.47 | Pali | you should just provide aes or wep keys to kernel |
| 19:37.02 | Pali | just protocol is in userspace |
| 19:45.15 | sicelo | good to have you on board Pali :) |
| 19:45.52 | sicelo | i have been trying to see if the tools for testing are released yet .. doesn't seem to be the case. or i missed something? |
| 19:47.33 | sicelo | https://www.krackattacks.com/#tools |
| 19:53.35 | *** join/#maemo TheKit (~nekit@87-119-253-147.saransk.ru) |
| 20:07.03 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 20:10.38 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 20:12.03 | Pali | so easiest would be to wait until check tool is released |
| 20:12.24 | Pali | and then decide if some steps are needed or not |
| 20:12.36 | Pali | or locale which part is responsible for wpa |
| 20:12.58 | Pali | I would bet it is this file: https://github.com/community-ssu/osso-wlan/blob/master/dbus-handler.c |
| 20:13.38 | Pali | there is a function named clear_wpa_keys() |
| 20:37.10 | *** join/#maemo rhombus (~rhombus@ip5b41109b.dynamic.kabel-deutschland.de) |
| 20:37.21 | rhombus | Greetings |
| 20:38.35 | rhombus | DocScrutinizer05: Question-Machine is back |
| 20:42.06 | DocScrutinizer05 | ohhai |
| 20:42.37 | DocScrutinizer05 | just in time :-) a 5 minutes back I wasn't on kbd |
| 20:43.10 | DocScrutinizer05 | ((<Pali> just protocol is in userspace(( where exactly? |
| 20:43.21 | DocScrutinizer05 | s/((/))/ |
| 20:43.37 | DocScrutinizer05 | or somesuch |
| 20:44.19 | DocScrutinizer05 | ~+uptime |
| 20:44.26 | DocScrutinizer05 | WOW |
| 20:45.44 | rhombus | DocScrutinizer05: what is that? |
| 20:46.07 | DocScrutinizer05 | nevermind, unrelated |
| 20:46.15 | DocScrutinizer05 | ~botsnack |
| 20:46.15 | infobot | :), DocScrutinizer05 |
| 20:46.37 | rhombus | ~botsnack |
| 20:46.37 | infobot | aw, gee, rhombus |
| 20:46.54 | DocScrutinizer05 | ~poettering |
| 20:46.54 | infobot | 'sth is poettering' means it acts invasive, possessive, destructive, and generally in an egocentric exacerbating negative way. ``this cancer is extremely poettering'', or you look here for Linus' notion on what's poettering: http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01331.html, or http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01488.html, or see ~systemd cabal |
| 20:47.27 | rhombus | Probably something Swedish. |
| 20:47.40 | rhombus | So... trying to decide where to start here |
| 20:47.41 | DocScrutinizer05 | ~infobot |
| 20:47.41 | infobot | infobot is, like, A program on the IRC that helps users, ask it to do something by putting a ~ and then say a command! |
| 20:47.50 | rhombus | ~fish |
| 20:47.50 | infobot | fish is, like, FISHFISHFISH! DO THE FISH DANCE! "Give a man a fish and you'll feed him a day. Teach him how to fish and he'll feed himself for the rest of his life." This is so appropriate, instead of asking us to tell you exactly what to do, why not read some docs, then come back and ask specific questions which aren't covered?, or http://www.p-nand-q.com/maldives/rbr/fish/sf25.jpg |
| 20:48.10 | rhombus | wow, good guess. |
| 20:48.56 | rhombus | So... is there any hope that there will be a patch for the WPA2 vulnerability on maemo? |
| 20:49.09 | DocScrutinizer05 | :-D |
| 20:49.44 | DocScrutinizer05 | <DocScrutinizer05> ((<Pali> just protocol is in userspace)) where exactly? |
| 20:50.36 | DocScrutinizer05 | http://mg.pov.lt/maemo-irclog/latest.log.html#t2017-10-17T02:44:49 |
| 20:50.38 | Pali | wlancond and eapd are only wlan related daemons |
| 20:51.22 | DocScrutinizer05 | Pali: lemme rephrase - where in kernel is WPA encryption? |
| 20:51.28 | Pali | eapd seems do TLS+PEAP related crypto |
| 20:52.20 | Pali | net/wireless/lib80211_crypt_*.c |
| 20:52.32 | Pali | lib80211_crypt_ccmp.c, lib80211_crypt_tkip.c, lib80211_crypt_wep.c |
| 20:52.42 | Pali | so seems in kernel is aes + wep |
| 20:52.49 | freemangordon | isn;t that done in HW? |
| 20:52.55 | Pali | and IIRC hw itself support aes |
| 20:53.38 | Pali | at least I remember parameters of some wifi drivers to enable HW accel of aes |
| 20:54.20 | DocScrutinizer05 | Pali: sounded wierd, but indeed https://github.com/community-ssu/osso-wlan/blob/master/dbus-handler.c#L2067 |
| 20:55.27 | DocScrutinizer05 | ((and IIRC hw itself support aes)) that's exactly what I seem to recall too |
| 20:55.39 | DocScrutinizer05 | didn't find a hint though, last 2 days |
| 20:55.54 | DocScrutinizer05 | anyway what we need is protocol |
| 20:56.45 | Pali | yes, need to figure out where is implemented that 4 way handshake |
| 20:57.10 | DocScrutinizer05 | https://github.com/community-ssu/osso-wlan/blob/master/dbus-handler.c#L2067 for (i=0;i<4;i++) { |
| 20:57.25 | DocScrutinizer05 | looks sort if interesting |
| 20:58.00 | DocScrutinizer05 | though there are 4 keys in WEP |
| 20:58.02 | DocScrutinizer05 | iirc |
| 20:58.17 | DocScrutinizer05 | tbh I got 0 clue about WPA |
| 20:58.54 | DocScrutinizer05 | I just know "nunce" from SIP challenge/response |
| 21:00.23 | DocScrutinizer05 | I didn't look into complete set of sec patches as e.g. found in UBNT updates either |
| 21:01.02 | DocScrutinizer05 | it's not just wpa-supplicant response#3 0 key. There are more CVE to fix |
| 21:01.21 | DocScrutinizer05 | just ^^^ is the worst one |
| 21:02.58 | DocScrutinizer05 | posting old shite, but one out of 200 may have missed it: https://www.krackattacks.com/ https://papers.mathyvanhoef.com/ccs2017.pdf |
| 21:07.14 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 21:10.12 | *** join/#maemo pkill9 (~pkill9@unaffiliated/pkill9) |
| 21:10.41 | DocScrutinizer05 | rhombus: a few notes on another topic: USB charger voltage between 4.75V and 6V is fine. Often chargers use ~5.3V to compensate for voltage drop on cable |
| 21:10.56 | pkill9 | has anyone installed slackware ARM onto nokia n900 and/or anyone know of a guide to do so? |
| 21:11.04 | DocScrutinizer05 | rhombus: charger should be capable of at least 800mA |
| 21:11.05 | rhombus | DocScrutinizer05: Ah, thanks |
| 21:11.41 | DocScrutinizer05 | rhombus: the Nokia barrel->usb adapter is *deprecated*, it's dangerous, starts a fire sometimes |
| 21:11.46 | pkill9 | specifically, booted it from SD card via U boot |
| 21:12.25 | DocScrutinizer05 | regardless I got one of them in use since 5 years 24/7/365 |
| 21:12.28 | pkill9 | also does anyone know of a way to pause the u-boot text when launching a kernel? like sendign a pause break key? |
| 21:13.22 | DocScrutinizer05 | pkill9: no, and no |
| 21:13.59 | DocScrutinizer05 | first possible just never heard of, 2nd not possible afaik |
| 21:14.08 | pkill9 | kk |
| 21:14.41 | DocScrutinizer05 | closest thing I could think of: gentoo on N900 |
| 21:14.58 | pkill9 | hmm yeah i might try that first |
| 21:15.16 | pkill9 | then work out how to get slack working |
| 21:15.38 | DocScrutinizer05 | afaik slackware is ultra-conservative so I doubt it has any support for special stuff on N900 hw platform |
| 21:15.52 | rhombus | DocScrutinizer05: I'm a fan of gentoo :) |
| 21:16.15 | rhombus | I tried to start ssh server on my N900, but it fails because it can't load the host keys |
| 21:16.20 | DocScrutinizer05 | afaik gentoo was the first non-maemo distro on N900 |
| 21:16.41 | DocScrutinizer05 | ugh! |
| 21:16.57 | rhombus | DocScrutinizer05: are all the phone functions supported on gentoo? |
| 21:17.06 | DocScrutinizer05 | no |
| 21:17.21 | rhombus | damn |
| 21:17.25 | pkill9 | DocScrutinizer05: could slack be configured to support extra hw stuff? |
| 21:17.30 | rhombus | Ok -- so to my ssh problem |
| 21:17.35 | DocScrutinizer05 | only maemo has complete phone support |
| 21:17.47 | pkill9 | I'm not fussed about the phone stuff really |
| 21:17.55 | pkill9 | I wanna use it as a tablet |
| 21:18.00 | DocScrutinizer05 | SHR has poor audio, otherwise sorta works |
| 21:18.08 | pkill9 | I'm kinda sick of smartphones tbh lol |
| 21:18.23 | DocScrutinizer05 | I feel with you |
| 21:18.46 | DocScrutinizer05 | I opt for renaming then to "fartphone" |
| 21:18.47 | rhombus | I just figured something out |
| 21:18.58 | rhombus | Or buttphone |
| 21:19.11 | DocScrutinizer05 | spyphone |
| 21:19.38 | DocScrutinizer05 | re sshd I can't recall any problems with hostkeys |
| 21:19.51 | rhombus | DocScrutinizer05: It helps if one does it as root |
| 21:19.53 | rhombus | :D |
| 21:19.53 | DocScrutinizer05 | should get auto-generated on installation, I'd assume |
| 21:20.07 | DocScrutinizer05 | ooh yeah |
| 21:20.16 | DocScrutinizer05 | definitely ;-P |
| 21:21.21 | DocScrutinizer05 | pkill9: ((could slack be configured to support extra hw stuff?)) for sure |
| 21:21.45 | pkill9 | kk cool :) |
| 21:22.05 | rhombus | I can't seem to ping the phone. Is ICMP turned off by default? |
| 21:22.19 | DocScrutinizer05 | possibly, yes |
| 21:22.23 | rhombus | I can ping my laptop *from* the phone |
| 21:22.52 | DocScrutinizer05 | though: |
| 21:23.00 | DocScrutinizer05 | 23:22:33 jr@saturn:~>ping IroN900 |
| 21:23.02 | DocScrutinizer05 | PING IroN900 (192.168.4.41) 56(84) bytes of data. |
| 21:23.04 | DocScrutinizer05 | 64 bytes from IroN900 (192.168.4.41): icmp_seq=1 ttl=64 time=78.1 ms |
| 21:23.15 | rhombus | "The password for user cannot be changed." |
| 21:23.30 | DocScrutinizer05 | there's no password for user |
| 21:23.43 | rhombus | How do I log into the phone via ssh, then? Only root logins? |
| 21:24.01 | DocScrutinizer05 | I'm not sure how to log in via user account - I always go straight to root |
| 21:25.02 | DocScrutinizer05 | I bet it *can* get done. Anyway you're supposed to use ssh keys and no passowrds ;-P |
| 21:25.04 | *** join/#maemo drathir (~kamiljk8@unaffiliated/drathir) |
| 21:25.28 | rhombus | DocScrutinizer05: I haven't used ssh much the past few years, so I'm out of practice |
| 21:25.58 | DocScrutinizer05 | man ssh-copy-id |
| 21:26.30 | *** join/#maemo GoNeL (~GoNeL@unaffiliated/gonel) |
| 21:28.35 | DocScrutinizer05 | 23:28:07 jr@saturn:~>cat `which iron900` |
| 21:28.36 | DocScrutinizer05 | ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l root IroN900 $@ |
| 21:30.00 | DocScrutinizer05 | 23:28:19 jr@saturn:~>grep -i iron900 /etc/hosts |
| 21:30.02 | DocScrutinizer05 | 192.168.4.41 IroN900 iron900 |
| 21:32.13 | *** join/#maemo drathir (~kamiljk8@unaffiliated/drathir) |
| 21:32.35 | DocScrutinizer05 | http://paste.opensuse.org/51594250 |
| 21:34.48 | DocScrutinizer05 | rhombus: the dir and file permissions and owner mist be exactly like this, otherwise login fails with pretty unhelpful error message |
| 21:35.27 | DocScrutinizer05 | afaik ssh-copy-id takes care about all this |
| 21:36.11 | DocScrutinizer05 | also see ssh-keygen |
| 21:37.07 | DocScrutinizer05 | though I'm sure you got a keypair already. do you? |
| 21:37.34 | DocScrutinizer05 | on your PC |
| 21:37.53 | rhombus | DocScrutinizer05: I am just discovering that |
| 21:38.15 | rhombus | Warning: Permanently added '192.168.3.24' (RSA) to the list of known hosts. |
| 21:38.15 | rhombus | Authentication failed. |
| 21:39.16 | DocScrutinizer05 | see ^^^ |
| 21:39.28 | DocScrutinizer05 | https://www.startpage.com/do/metasearch.pl?query=ssh+essentials |
| 21:40.21 | rhombus | DocScrutinizer05: yes and no |
| 21:40.23 | DocScrutinizer05 | pick the one you like most, they all are useful and correct |
| 21:40.51 | rhombus | DocScrutinizer05: I can generate this on my laptop, yes? |
| 21:41.15 | DocScrutinizer05 | ooh, and of course you need the password you gave on installing sshd. for user "root" |
| 21:41.21 | DocScrutinizer05 | yes, sure |
| 21:43.02 | DocScrutinizer05 | you may ommit "passphrase" on ssh-keygen. Some think that's no good idea, others thing passphrase to unlock local ssh private key is BS |
| 21:43.05 | rhombus | DocScrutinizer05: what do I need a password for if I'm using keys? |
| 21:43.20 | DocScrutinizer05 | to install the keys :-) |
| 21:44.07 | DocScrutinizer05 | on PC run ssh-keygen and ssh-copy-id |
| 21:44.26 | rhombus | Ok, i have generated a key pair with ssh-keygen |
| 21:44.58 | rhombus | but I have to change the permissions on the N900 first before this will work at all, right? |
| 21:45.28 | DocScrutinizer05 | no, you just run ssh-copy-id <N900> <root> or somesuch |
| 21:45.51 | rhombus | on my laptop |
| 21:46.12 | DocScrutinizer05 | Usage: /usr/bin/ssh-copy-id [-h|-?|-n] [-i [identity_file]] [-p port] [[-o <ssh -o options>] ...] [user@]hostname |
| 21:46.22 | rhombus | how can ssh-copy-id work if normal ssh logins don't? |
| 21:46.36 | DocScrutinizer05 | it uses your password |
| 21:46.48 | DocScrutinizer05 | normal login using password needs to work for that |
| 21:46.59 | rhombus | DocScrutinizer05: well, it doesn't |
| 21:47.09 | rhombus | I get an error message |
| 21:47.12 | DocScrutinizer05 | ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l root IroN900 $@ |
| 21:47.37 | rhombus | DocScrutinizer05: on the N900 |
| 21:47.41 | rhombus | so i have to restart ssh |
| 21:47.53 | DocScrutinizer05 | in your case: ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l root 192.168.3.24' |
| 21:48.47 | DocScrutinizer05 | do on phone: `root; passwd` |
| 21:49.15 | DocScrutinizer05 | then |
| 21:49.17 | DocScrutinizer05 | in your case: ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l root 192.168.3.24' |
| 21:50.00 | DocScrutinizer05 | on PC |
| 21:50.23 | DocScrutinizer05 | then ssh-copy-id |
| 21:50.26 | DocScrutinizer05 | on PC |
| 21:50.44 | rhombus | but the ssh server has to be running on the phone first for this to work |
| 21:50.47 | rhombus | :) |
| 21:50.50 | DocScrutinizer05 | yes |
| 21:51.04 | rhombus | do I have to fix any permissions on the phone? |
| 21:51.49 | DocScrutinizer05 | /etc/init.d/ssh start |
| 21:51.54 | DocScrutinizer05 | no |
| 21:52.59 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
| 21:54.06 | DocScrutinizer05 | you're in a xterm and root on phone? |
| 21:54.32 | rhombus | yes |
| 21:54.38 | rhombus | just changed the password |
| 21:55.03 | DocScrutinizer05 | then run /etc/init.d/ssh start |
| 21:55.18 | DocScrutinizer05 | (should have been done during boot, but...) |
| 21:55.54 | *** join/#maemo sunshavi (~user@190.234.106.7) |
| 21:55.56 | DocScrutinizer05 | then on PC, run: ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l root 192.168.3.24 |
| 21:57.09 | DocScrutinizer05 | you may omit the "-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" part if your phone's IP never changes |
| 21:57.46 | DocScrutinizer05 | you're already past the "Warning: Permanently added '192.168.3.24' (RSA) to the list of known hosts." |
| 22:00.54 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 22:01.04 | DocScrutinizer05 | so what does a ssh -l root 192.168.3.24 give you now? |
| 22:01.11 | rhombus | DocScrutinizer05: ok, what was the ssh -q command for? |
| 22:01.26 | DocScrutinizer05 | invokes ssh --help |
| 22:01.56 | DocScrutinizer05 | -q Quiet mode. Causes most warning and diagnostic messages to be suppressed. Only fatal errors are displayed. |
| 22:02.39 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 22:03.04 | DocScrutinizer05 | so it suppresses the "Warning: Permanently added '192.168.3.24' (RSA) to the list of known hosts. |
| 22:04.01 | rhombus | ok, well, nothing happen |
| 22:04.04 | DocScrutinizer05 | and "-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" suppress the quedtion "do you want to add...?" and avoid filling your known_hists file with litter |
| 22:04.06 | rhombus | happened |
| 22:04.23 | rhombus | it waited for ages and then died and gave me my local prompt again |
| 22:04.24 | DocScrutinizer05 | how, nothing? |
| 22:04.38 | DocScrutinizer05 | hmm, which command? |
| 22:04.47 | rhombus | ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l root 192.168.3.24 |
| 22:05.04 | DocScrutinizer05 | try `ssh -l root 192.168.3.24` |
| 22:05.52 | rhombus | nothing is happening |
| 22:05.57 | DocScrutinizer05 | o.O |
| 22:05.59 | rhombus | it's like it's timing out |
| 22:06.08 | DocScrutinizer05 | weeeiiird |
| 22:06.35 | DocScrutinizer05 | try `ssh -l root 192.168.3.24 date` |
| 22:06.59 | rhombus | I just got a password prompt |
| 22:07.03 | DocScrutinizer05 | try `ssh -vv -l root 192.168.3.24 date` and paste the diagnostic output |
| 22:07.09 | rhombus | after I pinged my laptop from the phone |
| 22:07.19 | DocScrutinizer05 | yes, that's exactly what shall happen |
| 22:07.39 | DocScrutinizer05 | not after pinhing though |
| 22:07.40 | rhombus | I just entered the password, it's taking forever |
| 22:07.47 | rhombus | ok, I'm in the phone |
| 22:08.00 | rhombus | Is that the reverse lookup timeout causing that? |
| 22:08.08 | DocScrutinizer05 | you WLAN might be... hmmm, there are often issues with lag |
| 22:08.16 | DocScrutinizer05 | yes, prolly |
| 22:08.39 | DocScrutinizer05 | even likely |
| 22:08.44 | rhombus | my WLAN has probably been compromised by hackers |
| 22:09.02 | DocScrutinizer05 | ohnoes! no kidding |
| 22:09.22 | rhombus | Ok, so I am in the phone. That means I can run ssh-copy-id from the laptop now and expect it to work, if slowly |
| 22:09.33 | DocScrutinizer05 | yes |
| 22:09.53 | DocScrutinizer05 | once you're in the phone, is it still slow? |
| 22:10.58 | rhombus | DocScrutinizer05: yes, pretty slow |
| 22:11.07 | rhombus | I mean, it works, but there's significant lag |
| 22:11.14 | DocScrutinizer05 | then it's not rDNS, it's wlan lag |
| 22:11.40 | DocScrutinizer05 | change PSM in phone's WLAN settings to 'none' |
| 22:11.55 | DocScrutinizer05 | what's your AP brand/make? |
| 22:12.18 | sixwheeledbeast | large amount of dropped packets on ping? |
| 22:12.26 | rhombus | I need to update my router. I'm running OpenBSD 6.0 It has no 802.11N support. N support was added in 6.1. Besides, I have to upgrade to 6.2 with the new WPA2 hole anyway |
| 22:12.52 | sixwheeledbeast | Even G wouldn't be that slow |
| 22:12.53 | rhombus | no packet loss on the ping from the phone |
| 22:13.02 | DocScrutinizer05 | yeah, you need to fix router settings to make PSM work |
| 22:13.15 | rhombus | average round trip 29 ms |
| 22:13.25 | rhombus | max 1035 ms |
| 22:13.42 | rhombus | What's PSM? |
| 22:13.44 | rhombus | :) |
| 22:14.24 | DocScrutinizer05 | phone's WLAN goes to sleep for a second or more, in PSM, and just wakes up for a few milliseconds to losten to next router beacon that has a flah telling "please stay awake" which may be 1 or 0 |
| 22:14.46 | DocScrutinizer05 | to listen to* |
| 22:14.57 | jonwil | yay, I figured out how to get hildon-status-menu into GDB. You need to stop hildon-status-menu with dsmetool then you need to start it again using maemo-summoner |
| 22:15.25 | rhombus | DocScrutinizer05: where do I set that? |
| 22:15.27 | DocScrutinizer05 | so there are two parameters you want to fix on router;: beacon freqiency and another TTdunnowhat that must be 1 |
| 22:15.44 | rhombus | PSM, I mean |
| 22:16.19 | DocScrutinizer05 | on phone you - for now - go to WLAN connections, edit, clik OK until on last requester there's "advanced..." |
| 22:16.31 | DocScrutinizer05 | and there you set PSM to "none" |
| 22:17.26 | sixwheeledbeast | power saving mode |
| 22:17.49 | rhombus | it says it will eat my children and steal all my money |
| 22:18.14 | DocScrutinizer05 | settings, internet connections, <your connection>, edit, ok, ok, ok... |
| 22:18.38 | rhombus | damn, I accidentally disconnected the WLAN and now my ssh connection is frozen |
| 22:19.35 | DocScrutinizer05 | " ~. |
| 22:19.44 | rhombus | I've turned psm off |
| 22:19.58 | rhombus | I'm trying to log in again |
| 22:20.49 | sixwheeledbeast | \n ~. |
| 22:21.05 | DocScrutinizer05 | better |
| 22:21.08 | sixwheeledbeast | I didn't know that. |
| 22:22.20 | rhombus | still highly variable |
| 22:22.30 | rhombus | It is probably the router |
| 22:22.31 | DocScrutinizer05 | AP problem |
| 22:22.53 | rhombus | beacon frequency and TTwhat? |
| 22:23.04 | DocScrutinizer05 | ywell, tbh it's "variable" even for me |
| 22:23.11 | DocScrutinizer05 | yes |
| 22:23.28 | DocScrutinizer05 | and correct implementation of PSM in AP |
| 22:23.32 | rhombus | I'll have to revisit this another day, I can't be staying up until all hours again |
| 22:23.39 | rhombus | I have PSM off on the AP |
| 22:23.47 | DocScrutinizer05 | oooh |
| 22:23.58 | DocScrutinizer05 | wait, that's probably another PSM |
| 22:24.44 | rhombus | ok, the minute I stop pinging my laptop from the phone, the connection becomes excruciatingly slow |
| 22:25.01 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 22:25.07 | DocScrutinizer05 | yes, typical problem with PSM and AP |
| 22:25.29 | DocScrutinizer05 | not much that can be done on phone except disabling PSM for the connection |
| 22:25.33 | rhombus | I don't have power save mode on on the AP |
| 22:25.54 | rhombus | It's an OpenBSD router that I put together myself, there's none of that nonesense configured |
| 22:25.58 | rhombus | nonsense |
| 22:26.15 | DocScrutinizer05 | on AP the meaning of "power save mode" will probably be quite different |
| 22:26.43 | DocScrutinizer05 | you need a beacon timing of 10 per second |
| 22:26.47 | rhombus | ok |
| 22:26.48 | DocScrutinizer05 | to startz with |
| 22:26.53 | rhombus | ok |
| 22:27.05 | DocScrutinizer05 | the other parameter is "1" by default |
| 22:27.31 | DocScrutinizer05 | it tells "send stay-awake-flag with N-th eakon only" |
| 22:28.29 | DocScrutinizer05 | also a reboot on phone *might* help to reset WLAN, the PSM setting is a tad ... special on that thing |
| 22:29.08 | DocScrutinizer05 | ~psm |
| 22:29.08 | infobot | psm is, like, Personal Security Manager for Mozilla, at http://docs.iplanet.com/docs/manuals/psm/psm-mozilla/index.html. You don't need to restart mozilla as noted on that URL. It also consumes 100% CPU unfortunately... lame piece of software. no longer works as of mozilla 0.7, or needed for viewing of some login sites, i.e. yahoo. install by apt-get install mozilla-psm |
| 22:29.13 | DocScrutinizer05 | meh |
| 22:30.48 | DocScrutinizer05 | you should probably get an update for your AP/router |
| 22:31.29 | DocScrutinizer05 | but first make sure to have beacon timing at 10Hz or more |
| 22:31.57 | DocScrutinizer05 | some routers have it at 1HZ or lower per default |
| 22:32.38 | rhombus | DocScrutinizer05: I'll have to see where that is set, as I said, it's a homespun OpenBSD box |
| 22:33.10 | DocScrutinizer05 | yeah, for now your pest option is to run a ping from a second terminal to phone |
| 22:33.22 | DocScrutinizer05 | that will keep connection responsive |
| 22:33.29 | DocScrutinizer05 | best* |
| 22:34.15 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 22:34.27 | rhombus | Interesting. I'm logged in via sftp now, and it's much faster. |
| 22:34.34 | DocScrutinizer05 | or maybe really reboot the phone. your sshd also wasn't started despite it should, right? |
| 22:35.44 | DocScrutinizer05 | did you find a working solution for your charging? |
| 22:37.02 | DocScrutinizer05 | ((when requester "assrage, PCsuite, charge?" pops up on unplugging USB, just plug and unplug again)) |
| 22:37.16 | rhombus | sorry, scratch that, I'm putting a file and it's excruciatingly slow |
| 22:37.25 | rhombus | ok, getting better |
| 22:37.28 | DocScrutinizer05 | that's weird |
| 22:37.33 | rhombus | 1.4 MB/s now |
| 22:37.48 | DocScrutinizer05 | connection should stay alive during data transfer |
| 22:38.00 | rhombus | yes |
| 22:38.11 | DocScrutinizer05 | well, that's _almost_ max speed via sftp |
| 22:38.20 | rhombus | Oh, and I don't have a specific charger yet, but I am going to get one that's similar to my wife's |
| 22:38.44 | DocScrutinizer05 | mind you, it needs to decrypt on a CPU that's like a 300MHz P-II |
| 22:39.05 | rhombus | ok, then I can live with that :) |
| 22:40.15 | rhombus | DocScrutinizer05: the problem yesterday was that by the time I noticed the USB problem, I was nowhere near a charger or cable |
| 22:40.36 | DocScrutinizer05 | yeah |
| 22:41.12 | rhombus | the phone fell asleep and the sftp transfer stalled |
| 22:41.15 | rhombus | I had to wake it up |
| 22:41.19 | rhombus | it was slow waking up |
| 22:41.21 | DocScrutinizer05 | o.O |
| 22:41.54 | DocScrutinizer05 | I'm doing ssh and sftp all the time while device is next room sleeping on charger |
| 22:42.17 | rhombus | Well, I'm sure that there's lots I have to configure on the phone |
| 22:42.35 | DocScrutinizer05 | not really |
| 22:42.46 | DocScrutinizer05 | most thinks should "just work" |
| 22:43.16 | DocScrutinizer05 | but phone getting irresponsive on large amounts of data to write to flash is a known annoying nasty effect |
| 22:43.39 | DocScrutinizer05 | you're easily entering swap hell with copy of large files |
| 22:43.43 | rhombus | DocScrutinizer05: ok, then that is the explanation, I'm uploading 85 MB podcast files to the phone |
| 22:44.54 | DocScrutinizer05 | should work, just take a while |
| 22:46.44 | DocScrutinizer05 | never forget about partitions/volumes: you only got a 2GN minus X on your ~user dir, root has no homedir at all where you could store large files, since it's on rootfs. and the true mass storage is ~user/MyDocs |
| 22:46.55 | DocScrutinizer05 | 2GB |
| 22:47.14 | rhombus | That's where I was pushing the files to |
| 22:47.29 | rhombus | ~user/MyDocs |
| 22:47.31 | DocScrutinizer05 | I hope you don't store those 85MB to root's home? |
| 22:47.35 | rhombus | no |
| 22:47.36 | rhombus | :) |
| 22:47.40 | DocScrutinizer05 | aah ok :-) |
| 22:47.42 | rhombus | ~user/MyDocs |
| 22:47.46 | DocScrutinizer05 | good |
| 22:48.00 | rhombus | is that on the microSD? |
| 22:49.23 | rhombus | ok man, I gotta go to bed. That's a bit of progress for today. I'm starting to really enjoy the phone |
| 22:49.34 | rhombus | listened to the radio on the train today... some podcasts |
| 22:49.42 | rhombus | it's working nicely |
| 22:50.04 | rhombus | I'll get a new charger shortly, fix my WLAN, etc. |
| 22:50.10 | rhombus | Chat soon |
| 22:59.00 | jonwil | Looks like we have another person who doesn't heed the warnings and has just installed all the stuff I uploaded to cssu-devel and is now wondering why his device bootloops... |
| 23:13.13 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 23:19.56 | sixwheeledbeast | I am not surprised. Won't be the first or the last |
| 23:20.42 | jonwil | My guess is one of the recent clones by Freemangordon is what's causing the boot loop (either his cloning or my compile/build) |
| 23:21.04 | jonwil | I need my N900 too much to try installing any of that stuff to narrow down the culprit |
| 23:36.20 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 23:36.53 | *** join/#maemo Kilroo (~Kilroo@cpe-71-71-97-50.triad.res.rr.com) |
| 23:43.23 | *** join/#maemo r00t^home (~r00t@port-92-196-60-16.dynamic.qsc.de) |
| 23:52.53 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
