**** BEGIN LOGGING AT Thu Mar 22 02:59:58 2012 Mar 22 04:01:26 hi Mar 22 04:02:22 Is anyone know about mono&moonlight? Mar 22 06:00:45 anyone happen to know the package name that contains the GNU version of ps? not ps as in postscript but ps as in that process viewer tool. I'm trying to find the offending process that is deliberately shutting off wlan0 interface Mar 22 06:14:41 hmm.. psycho_oreos, i don't remember too well now, but check out Mar 22 06:14:46 ~jrtools Mar 22 06:14:47 [jrtools] http://wiki.maemo.org/User:Joerg_rw/tools Mar 22 06:16:00 Sicelo, thanks, going to have a quick glance. I'm just really pissed off that there's a process that is deliberately turning wlan0 down, its evident in both dmesg and in ip but I can't find the bloody culprit Mar 22 06:16:23 either coreutils-gnu or procps :/ Mar 22 06:16:52 procps? Mar 22 06:18:06 its definitely not coreutils-gnu, I already have that installed, checked the contents of that package and there's no gnu ps tool Mar 22 06:18:07 though I'm not all that sure how it will help to find a process that shuts down wkan Mar 22 06:18:18 thanks, going to use procps Mar 22 06:18:21 procps!! Mar 22 06:19:06 I always thought htop is indispensable Mar 22 06:19:16 yeah its not a definitive way, but airmon-ng usually lists offending process, though I have yet to see how that really works. I bet its not for embedded setups Mar 22 06:19:25 hmm Mar 22 06:19:36 but admittedly sometimes there's nothing that competes to ps Mar 22 06:21:02 to a real ps, not that messybox BS Mar 22 06:21:25 its annoying that so far I've tried a few tools to pinpoint the culprit but so far I have not gotten anywhere closer Mar 22 06:22:11 what's the *exact* problem? Mar 22 06:23:22 running kp50 with the latest CSSU (testing), I ran airodump-ng on wlan0 with lxp's drivers. airodump-ng keeps reporting interface wlan0 is down and after awhile the process aborts leaving a mess in the terminal Mar 22 06:23:39 dmesg is littered with firmware booted, up and down repeatedly Mar 22 06:23:52 ouch Mar 22 06:24:37 I've also even wrote a nasty while script (purely for the sake of testing) to constantly turn the interface up regardless of the state but it doesn't really help airodump-ng Mar 22 06:25:02 two possibilities come to mind: either wlan itself "segfaults" and gets reloaded, or ICD2 and peers does that Mar 22 06:25:08 * psycho_oreos is certain that once the N900 is associated properly to a normal network (via managed mode) it will not disassociate itself Mar 22 06:25:12 hmm Mar 22 06:26:15 heh I tried killing wlancond, but admittedly if I tried to kill it at least twice the device would automatically reboot Mar 22 06:26:44 * psycho_oreos tries the managed mode just for the sake of narrowing down the problem Mar 22 06:27:04 yes, there's been that "bug" that wlan xucks battery like mad while not associated. Nokia implemented a "fix" into (IIRC) ICD2 so it gets modprobe-r'd for long periods between scans for APs Mar 22 06:28:01 hey, when you kill processes started via dsme, you sure will get a reboot sometimes Mar 22 06:28:14 try "stop " Mar 22 06:28:27 rather than "killall " Mar 22 06:29:29 interestingly enough the fix nokia did, does not affect the current status of interface constantly going up and down. I'm certain its somewhere along CSSU testing/kp is somehow causing the issue. I remember awhile back lxp released osso-wlan fix which may also be the culprit Mar 22 06:30:29 yeah I did pkill, which would be similar to killall :) I'm going to try using the method you said after I try associating to wlan through normal way and seeing if that is not the issue Mar 22 06:30:31 if that's realy related to CSSU &/| KP, we definitely need a ticket and further joint effort investigations Mar 22 06:31:04 not until I pinpoint the actual problem :) this is where I'm going to dive deeper myself first as the problem is quite complex actually Mar 22 06:31:50 yep. thanks a lot for that attitude and for taking care Mar 22 06:32:48 o.O *is a little puzzled at that remark* Mar 22 06:33:03 you *may* try entering airplane mode, then cranking up wlan "manually" Mar 22 06:33:36 psycho_oreos: why? that remark was a honest thanks and a bit of a compliment Mar 22 06:33:40 ahh Mar 22 06:34:12 I dunno, my caffeine dosage right now is on its `worn' state so I get a little skeptic :/ Mar 22 06:34:40 * psycho_oreos thinks the need for more coffee is soon to be required Mar 22 06:34:40 hehe, I'm just about to refiill after wake from suspend Mar 22 06:35:36 heh sometimes caffeine doesn't stack for me, but I might be able to stack it today.. who knows :D if not I'll just end up literally hitting the sack early Mar 22 06:36:26 airmon-ng reports avahi as being a potential culprit. I'm sure that's a pretty standard process and mind you I hardly use airmon-ng at all, I never use it anywhere else Mar 22 06:36:52 I should run to get to daywork early, so I might leave a bit more early as well Mar 22 06:37:14 AVAHI!!! GRRRR >:-( Mar 22 06:38:19 that's a good idea actually :) if you can do that lol. I'm not a morning bird but to get work done first thing in the morning and out of the way is something that I highly value. Mar 22 06:38:24 * DocScrutinizer runs ps|grep avahi Mar 22 06:39:36 hehe now now I don't think avahi is really really that bad, I'm sure it exist in literally all default maemo setups but yeah I'm sure there's some other offending process somewhere... *leans slightly to strongly towards ICD2, mutters about stopping wlancond thinking that would probably be the cure* Mar 22 06:39:48 no avahi on my machines ;-) Mar 22 06:40:11 esp not on maemo Mar 22 06:40:35 well avahi-daemon is the actual process name. You don't have it? did you remove it or you never had it? :| Mar 22 06:40:56 t900:~# ps aux|grep ava Mar 22 06:40:58 8138 root 2088 S grep ava Mar 22 06:41:06 sounds like you never had it Mar 22 06:41:10 yep Mar 22 06:41:24 >:( *forces removal of avahi immediately* Mar 22 06:41:26 hotspot? Mar 22 06:43:06 yeah that could a potential possibility but I hardly use that program anyway.. should it remove hotspot I wouldn't really care to be frank lol Mar 22 06:43:56 apt-cache search avahi Mar 22 06:44:19 wtf.. http://pastebin.com/eEbZ97rA Mar 22 06:44:29 it seems like there's a whole lot of deps Mar 22 06:46:47 none of which I know who's depending on them Mar 22 06:47:25 maemo-pc-connectivity is a but :-S though, in that list Mar 22 06:47:30 it seems like when trying to remove avahi-daemon, the packages to be removed was a whole bunch Mar 22 06:48:02 a bit* Mar 22 06:48:48 anyhow I've aborted the idea of removing avahi-daemon, I was really close to removing it. I've instead stopped wlancond and retried airodump-ng again.. initally I stopped avahi-daemon now its wlancond Mar 22 06:49:11 it seems like wlancond was the culprit, I've had no messages about wlan0 is turned off Mar 22 06:49:48 hmmhmmmhmmm Mar 22 06:50:20 * psycho_oreos stops airodump-ng and starts avahi-daemon again Mar 22 06:51:44 1 minute into airodump-ng with avahi-daemon and no messages about interface is down. Usually it was around 30 seconds or so mark Mar 22 06:51:56 * psycho_oreos runs airodump-ng for a little longer just to make sure Mar 22 06:52:08 ~ # ls -l /usr/sbin/wlancond Mar 22 06:52:10 -rwxr-xr-x 1 root root 58292 Jan 17 22:47 /usr/sbin/wlancond Mar 22 06:52:31 IIRC I was guinea pig for that thing to test Mar 22 06:52:49 new CSSU might bring it per default Mar 22 06:52:49 you also used airodump-ng to test? Mar 22 06:52:57 nope, not yet Mar 22 06:53:19 ahh ok Mar 22 06:53:32 -rwxr-xr-x 1 root root 58292 2012-01-18 07:47 /usr/sbin/wlancond Mar 22 06:53:54 anyway that's my t900 (very old KP, no CSSU): Mar 22 06:53:57 t900:~# ls -l /usr/sbin/wlancond Mar 22 06:53:59 -rwxr-xr-x 1 root root 60764 Jan 18 2010 /usr/sbin/wlancond Mar 22 06:54:48 :nod: Mar 22 06:54:57 3 minutes in, its definitely wlancond, by now with that wlancond on, airodump-ng would just quit and osso-xterm would just hang (but you can still close the window) Mar 22 06:55:00 so yu got the "fixed" version of CSSU Mar 22 06:55:15 yeah, well its the latest one iinm I can check right now Mar 22 06:56:16 21.2011.38-1Tmaemo2.1 <--- CSSU version Mar 22 06:56:18 pester merlin1991 about it ;-D Mar 22 06:56:41 that's a bug with CSSU then? o.O *is surprised* Mar 22 06:56:52 not a "bug" Mar 22 06:57:08 we got that lxp bugFIX in wlancond Mar 22 06:57:18 or whatever feature they added and now is causing this headache lol Mar 22 06:57:19 ahh Mar 22 06:58:04 I only tested it for normal operation of device Mar 22 06:58:27 probably my notion of "normal" wasn't comprehensive Mar 22 06:58:37 should have tested airodump as well Mar 22 06:58:42 yeah nothing wrong with normal operation in my case as well, I mean having it associated to an AP through managed mode Mar 22 06:59:10 *nods* though its just a little weird how all of the sudden having it in monitor mode would be an issue Mar 22 06:59:54 anyway, /join #maemo-SSU, pester merlin1991 Mar 22 07:00:01 * psycho_oreos goes and files info on bugzilla Mar 22 07:00:04 heh I'm there :D Mar 22 07:01:10 I've not the time nor the background to dig into that right now, but it definitely needs close and immediate and in-depth investigation Mar 22 07:01:41 *nods*, well I'll file it as something other than bug under cssu bugzilla :D Mar 22 07:10:41 I am on the new CSSU, what's exactly with wlancond - monitor mode - airodump? Mar 22 07:10:56 I could do some test too ;) Mar 22 07:13:09 monitor mode = RFMON mode, there's a good wikipedia article about it. airodump-ng (not airodump) is a tool part of aircrack-ng suite Mar 22 07:14:58 I don't need the info about aircrack-ng and rfmon mode, but I want to know if I can reproduce your bug ;) Mar 22 07:18:09 do you get that bug with airmon only? Mar 22 07:19:06 not airmon-ng, moreso with airodump-ng and aireplay-ng. Mind you I hardly use airmon-ng myself, almost never Mar 22 07:19:18 it used to bwe borked Mar 22 07:19:42 so setting up down, monitor, up was the way Mar 22 07:19:48 not sure if it works now Mar 22 07:19:53 MrPingu, ahh well its easy, latest testing CSSU + aircrack-ng suite = issue Mar 22 07:20:02 I think it did at kp48 at least Mar 22 07:20:36 heh I always use wlan0 interface, I never bothered with airmon-ng but if one uses airmon-ng, it would create a vif named mon0 Mar 22 07:20:37 but dump/replay always worked fine Mar 22 07:20:48 yeah Mar 22 07:20:53 useful in some cases Mar 22 07:21:18 yeah it works fine with older kernels and what not.. It wasn't an issue with kp50 or so I thought but yeah its wlancond in CSSU-T Mar 22 07:21:35 hmmm strange estel didn't notice that Mar 22 07:21:37 well if you're a wifi pentester, it's almost an absolute necessity Mar 22 07:22:09 he did complain about cleven/faircrack when they were not working with pre50 Mar 22 07:22:20 I always use airmon-ng but sometimes mon0 will hang on the same channel as wlan0 if you connect through maemo Mar 22 07:22:29 so definitely was using monitor mode on 50 :/ Mar 22 07:22:55 none of those use airmon though Mar 22 07:22:56 let me test... brb Mar 22 07:24:14 ahh yeah that thread, I skimmed through that as I was trying to look for ways to solve my own problem at the time. Mar 22 07:25:22 mon0 shouldn't hang in theory but you cannot change the channel of mon0 as it would affect wlan0 as well Mar 22 07:25:44 saturn also mentions no problems if .ko's are copied but .sh's left, so another person with no such prob Mar 22 07:26:02 though whether they are in latest testing... probably Mar 22 07:26:41 there was no .sh file with the latest lxp binary tarball. Plus I used that wlan switcher tool by ossipena (hopefully I got his handle right) Mar 22 07:27:19 .sh were used by cleven Mar 22 07:27:24 are* Mar 22 07:27:43 saturn mentions they need to be left there and it supposedly works Mar 22 07:27:44 ahh yes hence I would somewhat see the dependency Mar 22 07:28:13 but the fix for not seeing networks sounds much more likely culprit Mar 22 07:28:52 it does something like restarting wlan interface if I'm not mistaken Mar 22 07:29:02 maybe it misbehaves with latest Mar 22 07:29:32 yeah I'm not sure, I never used cleven personally. I just like the idea of tapping away with me two thumbs :) Mar 22 07:29:57 useful for war-walking Mar 22 07:30:09 [ CH 12 ][ Elapsed: 3 mins ][ 2012-03-22 08:29 Mar 22 07:30:15 seems to work? Mar 22 07:30:46 you'll have to wait around 30 seconds Mar 22 07:30:50 MrPingu: do you use the fix for missing wlans? Mar 22 07:30:51 hmm Mar 22 07:31:05 well war-anything almost :) Mar 22 07:31:09 3min<- Mar 22 07:31:15 yeah I noticed that Mar 22 07:31:25 Uhm I only use cssu + new compiled modules Mar 22 07:32:00 never installed the ossowlan.deb that came with the drivers from the old package Mar 22 07:32:02 cssu testing right? which version? Mar 22 07:32:18 testing 2.1 + kp50 Mar 22 07:33:23 interesting Mar 22 07:33:48 then it sounds like something is making wlancond in my case turning wlan0 down Mar 22 07:34:04 s/something/something else/ Mar 22 07:34:05 psycho_oreos meant: then it sounds like something else is making wlancond in my case turning wlan0 down Mar 22 07:35:16 try uninstalling the 'fix'? Mar 22 07:35:37 lxp's fix? Mar 22 07:35:40 yeah Mar 22 07:35:53 unless you have a widget that does this Mar 22 07:36:10 not that many things left that could be interfering Mar 22 07:37:27 well in #maemo-ssu DocScrutinizer and I discussed about this issue and he provided me the original wlancond (that's not modified by CSSU) and told me to try and run it. Well I did (after backing up the necessary file, copied it across, made it executable and rebooted), the problem still persist with the old wlancond Mar 22 07:37:57 old wlancond as in the one DocScrutinizer provided, so yeah Mar 22 07:38:12 lxp's fix only touches that? Mar 22 07:39:15 * psycho_oreos is not aware if lxp has made other fixes Mar 22 07:41:00 I used this monitor on wlan0 FYI Mar 22 07:41:40 normally I use on Mon0 but as you said you always used on wlan0, I did that this time ;) Mar 22 07:41:50 Didn't test injection tho Mar 22 07:42:01 not that using wlan0 or mon0 would actually matter, mon0 is just a vif Mar 22 07:42:18 injection won't be affected if airodump-ng in your case wasn't affected Mar 22 07:42:55 It's all a long time ago I played with wifipentesting Mar 22 07:43:14 I try to learn metasploit nowadays :P Mar 22 07:43:27 jr@halley:~/Documents/OpenMoko> ls -l /scratchbox/users/jr/targets/FREMANTLE_ARMEL/usr/sbin/wlancond Mar 22 07:43:29 -rwxr-xr-x 1 jr sbox 56412 2. Mär 2010 /scratchbox/users/jr/targets/FREMANTLE_ARMEL/usr/sbin/wlancond Mar 22 07:44:37 DocScrutinizer, your original wlancond (the one with .bak extension, obviously renamed when I tried it out on mine) didn't fix the issue, I'm guessing its somewhere else that is causing wlancond to shut off wlan0 interface Mar 22 07:45:11 try .old, same location Mar 22 07:45:14 see ^^^ Mar 22 07:45:42 my .bak also is from last december Mar 22 07:45:53 yeah I toyed with aircrack-ng tool because of kp50 and I wanted to make sure that monitor/injection still works Mar 22 07:45:54 not all sure about it Mar 22 07:45:55 hmm Mar 22 07:47:49 -rwxr-xr-x 1 root root 57692 Jul 5 2010 wlancond Mar 22 07:47:58 Ah, well I still have to do that test :P monitor is working fine =) Mar 22 07:52:49 heh I almost dug myself in, I did the test with the stock driver and that intercepted by wlancond, So after stopping wlancond and ran airodump-ng again on wlan0 (still with stock drivers) the problem disappeared. Now told to run the .old version I just realised I wasn't using bleeding edge drivers, so I repeated the test with bleeding edge drivers and yeah same result. So its definitely nothing to do with the drivers itself at all Mar 22 07:52:59 now rebooting with wlancond (from wlancond.old) Mar 22 07:54:57 have to go to school Mar 22 07:55:05 see ya! Bye! Mar 22 07:55:20 cya and thanks for testing! Mar 22 07:55:59 NP, I like to test simple things. Slowly building my knowledge... Mar 22 07:56:12 cya Mar 22 07:56:30 indeed, a good way somewhat to start somewhere Mar 22 07:57:54 DocScrutinizer, nope still no dice with .old Mar 22 07:58:23 its definitely pointing to some other process that is making wlancond shut off wlan0... hmpf Mar 22 07:59:24 <_freemangordon> psycho_oreos, do you have any of those "auto-disconnect","auto-switch" or whatever widgets installed? Mar 22 07:59:42 _freemangordon, yeah autodisconnect, I disabled that functionality Mar 22 08:00:04 <_freemangordon> and you're sure it behaves correctly? Mar 22 08:00:39 <_freemangordon> psycho_oreos ^^^ Mar 22 08:00:42 well I could instantly remove that autodisconnect tool :) though I've never ran into this issue before Mar 22 08:00:49 remove/purge/nuke from orbit just to be sure? Mar 22 08:01:04 <_freemangordon> well, I just guessing what could be the reason ;) Mar 22 08:01:19 <_freemangordon> *I am Mar 22 08:01:29 O Mar 22 08:01:35 <_freemangordon> is low on caffeine Mar 22 08:01:45 I'm curious to see if I can solve it without having to kill wlancond everytime as well :) Mar 22 08:02:29 <_freemangordon> psycho_oreos, you can start dbus-monitor, to check who is calling wlancond through d-bus Mar 22 08:02:50 there's some process that is trying to access network/internet, every so often I get that usual ICD dialogue box coming up when I'm not connected to network/internet. I disabled modest functionality in autochecking so I'm guessing it could be some program that is trying to phone home or some crap Mar 22 08:03:07 _freemangordon, good idea, I'll try that Mar 22 08:14:04 _freemangordon, according to dbus-monitor --system, it's reporting mostly icd and icd2 is causing the issue Mar 22 08:15:25 every four to five times dbus-monitor reports icd && icd2 activity, there seems to be a new entry into dmesg in regards to wl1251 unloaded, and loaded Mar 22 08:15:50 and about 5 or so minutes I get the select connection dialog box Mar 22 08:16:50 install wireshark, connect, check where it is connecting, what it is sending/pulling Mar 22 08:23:07 yeah I did something similar to that with little success Mar 22 08:23:21 no packets caught? Mar 22 08:24:11 the question was exactly which interface to capture on, I initially tried wlan0 and there was nothing, not even on phonet Mar 22 08:24:27 unlikely Mar 22 08:24:46 maybe constant up/down interferes Mar 22 08:24:50 try mitm Mar 22 08:24:57 well, of course there won't be anything until you actually up the IF ;) Mar 22 08:25:01 catch all inbetween N900 and router Mar 22 08:25:09 no probs with interface this way Mar 22 08:25:54 I meant when I did that before, I used tcpdump and I did not have any default gw set nor was icd hooked on any connection Mar 22 08:26:46 psycho_oreos: a simple change in your user internet config settings may help. Just don't allow to connect on request, not even with asking Mar 22 08:26:50 though needless to say as soon as I connected up ppp0 (3/3.5G mode) lots of stuff were going in and out Mar 22 08:27:40 DocScrutinizer, yeah I did set that to always ask :) I even checked that not long ago because I thought somehow either I turned it to scan automatically or somewhere it was re-enabled. Though that wasn't the case Mar 22 08:28:00 I can't really find the option to not ask, if I could that would be nice :D Mar 22 08:28:05 not even asking <- Mar 22 08:28:09 yeah Mar 22 08:28:10 disable "connect to wlan when available" Mar 22 08:28:28 its on "always ask" but the dialog box still appears :) Mar 22 08:28:55 ooh, you cut out the hole and there's still a hole? Mar 22 08:28:57 ;-D Mar 22 08:29:26 there is no option Don't ask Mar 22 08:29:36 meh Mar 22 08:29:49 I meant under connect automatically heh Mar 22 08:29:50 my bad Mar 22 08:30:07 use wlan and never Mar 22 08:30:08 connect automatically: always ask <-- the rest of the options are greyed out evidently Mar 22 08:30:14 hmm ok Mar 22 08:30:28 as search interval and don't check that box Mar 22 08:31:07 but still, would be nice to dump what is going on after connect Mar 22 08:31:08 well if search interval is never, the option to check that box is also inherently greyed out Mar 22 08:31:23 yeah :) Mar 22 08:31:30 makes sense Mar 22 08:32:23 "search" means ICD2 is cranking up wlan to do a scan Mar 22 08:32:31 every N minutes Mar 22 08:33:10 automatic connect means it's trying to connect when sth asking for internet Mar 22 08:33:47 ah ha.. and here comes the answer to the clue being the user is the error lol Mar 22 08:34:42 still I see dbus activities with icd and icd2 fiddling with various interfaces even though it already has a connection Mar 22 08:34:54 it's always PEBKAC ;-) Mar 22 08:35:54 nope there's still wl1251 being booted and unloaded in dmesg Mar 22 08:36:09 hmm what if I set to say Any connection but never scan? Mar 22 08:36:32 you NEED "never scan" Mar 22 08:36:55 you also need unchecked "use wlan if available" Mar 22 08:37:14 though that'S prolly greyed out when "never scan" Mar 22 08:37:42 that was done, even on WLAN it still has dmesg showing booting and unloaded. I did that as well (momentarily set search interval to 5 minutes and unchecked that box, and set search interval to never) Mar 22 08:37:45 yeah Mar 22 08:38:09 "automatic connect:" GPRS only Mar 22 08:38:38 do NOT use "any" or "always ask" Mar 22 08:39:06 uncheck "connect to WLAN if available" too Mar 22 08:39:13 I just set it to my usual 3G/3.5G connection, pretty sure there will still be new messages in dmesg in regards to wl1251 Mar 22 08:39:24 "search interval:" never Mar 22 08:39:27 yup all that is done Mar 22 08:40:04 now just make sure no friggin auto-disconnect app is bypassing those settings Mar 22 08:40:07 and... there's still new messages in dmesg stating wl1251 being booted and unloaded Mar 22 08:40:29 * psycho_oreos thinks of just removing auto-disconnect just for the sake of testing Mar 22 08:41:05 auto-disconnect is messing up system so terribly and thoroughly, I dunno if you ever can uninstall it Mar 22 08:41:37 ugh Mar 22 08:41:56 I never looked into it, but there've been several user reports that the system was in bogus state with auto-disconnect, and only a reflash recovered Mar 22 08:42:47 * DocScrutinizer waves Mar 22 10:00:30 MohammadAG: does open media player support replaygain tags, more specifically for vorbis files ? Mar 22 10:01:05 I grepped the sources for REPLAY, but did not find any occurence Mar 22 10:02:26 I wondered if it has support for it through gstreamer or not at all Mar 22 10:03:48 peetah: OMP uses mafw as a backend Mar 22 10:04:00 And I'm not sure that even supports replaingain Mar 22 10:04:07 Replaygain Mar 22 10:04:32 If its possible with gatreamer patching mafw to include the changes should be possible Mar 22 10:06:07 ok thanks Mar 22 11:30:37 Ouch just discover that there are good fake n900 : http://www.youtube.com/watch?v=1Xd7IVCV3Jg&feature=related Mar 22 11:53:01 Khertan: i wonna see the firmware on it! Mar 22 11:54:09 http://www.youtube.com/watch?v=d5BdyIGtYcg Mar 22 12:15:45 hi I upgraded recently to the new release of power kernel 2.6.28.10-power50 and now cleven is telling me that the kernel is not compatible I've checked for a new update for cleven but there wasn't any ..... any idea what i should do Mar 22 12:18:22 it only says it might not work properly Mar 22 12:18:41 as far as i can see Mar 22 12:18:42 works for me Mar 22 12:20:46 dhbiker let mecheck on this one Mar 22 12:21:20 dhbiker, but why would it say it might not work properly while it is Mar 22 12:22:30 it only says that it did not find a known compatible kernel... Mar 22 12:22:42 dhbiker, are you able to enable monitor mode Mar 22 12:22:47 yes Mar 22 12:22:57 dhbiker, i can't Mar 22 12:23:06 download the newer drivers Mar 22 12:23:52 what drivers I already checked twice for updates and none is found Mar 22 12:24:47 http://talk.maemo.org/showthread.php?s=057f7ba199a3bca52c2c69c31c08c5ae&t=83118 Mar 22 12:24:53 read this thread carfully Mar 22 12:24:58 carefully Mar 22 12:25:12 there is a link to injection drivers Mar 22 12:25:24 dhbiker, ok i will Mar 22 12:31:43 Pali: ping Mar 22 12:38:38 dhbiker, that's one big file Mar 22 12:43:48 Pali: ping Mar 22 12:44:01 int_ua: pong Mar 22 12:44:21 Pali: Looks like there is a limit of 2 Mb for uImage on N900. Is that true? Mar 22 12:44:31 yes Mar 22 12:44:44 oh, it is smaller Mar 22 12:44:52 2MB is nand kernel parition Mar 22 12:45:20 so u-boot + kernel must be smaller then 2MB Mar 22 12:45:25 Pali: But isn't U-Boot loading kernels from RAM? Mar 22 12:45:47 yes, U-Boot is starting kernel from RAM Mar 22 12:45:56 but kernel must be loaded to RAM first :D Mar 22 12:46:20 so kernel is stored after u-boot in kernel nand parition Mar 22 12:46:25 Pali: I'm talking about kernel on mmc, not combined with U-Boot Mar 22 12:46:53 about kernel on mmc, I do not know if there is limit Mar 22 12:46:59 it depens on u-boot Mar 22 12:47:09 but it is not good idea to have big kernel image Mar 22 12:47:46 Pali: Ubuntu stock kernel is 3.6Mb, it doesn't look like very big :) Mar 22 12:47:54 now I see that rx51 board code thinks that uImage will not be bigger 2MB Mar 22 12:47:55 Pali: Is it? Mar 22 12:48:19 so if uImage will be bigger it can rewrite something in RAM (e.g u-boot itself Mar 22 12:48:41 Pali: So theoretically it can be changed for loading bigger kernels? Mar 22 12:48:53 yes Mar 22 12:49:18 via env :-) Mar 22 12:49:32 * dhbiker bows to Pali Mar 22 12:49:33 in env kernaddr is stored address where will be kernel loaded Mar 22 12:49:43 Pali: wow, even without patching? Mar 22 12:49:56 same for env initrdaddr and scriptaddr Mar 22 12:49:57 Pali: isn't it the start of image? Mar 22 12:50:49 if you use "run kernload" it will load kernel image to address specified in kernaddr Mar 22 12:51:48 Pali: Do you mean that initrdaddr=kernaddr+2Mb? Mar 22 12:52:16 default values: kernaddr=0x82008000 initrdaddr=0x84008000 scriptaddr=0x86008000 Mar 22 12:52:38 so if you have both kernel and initfs, kernel must not be bigger then 2MB Mar 22 12:54:16 int_ua, so yes Mar 22 12:54:53 scriptaddr is address where will be loaded u-boot script (e.g. boot.src) if is used Mar 22 13:05:54 Pali: I'm a little bit puzzled. 2Mb is 0x200000, right? And the difference between kernaddr and initrdaddr is 0x2000000, on one zero more, 32Mb, is it? Mar 22 13:06:32 wait, I will check zeros in configs :D Mar 22 13:09:10 int_ua, you are right, there is really one more zero Mar 22 13:09:24 so memory limit 32MB (instead 2MB) Mar 22 13:23:52 Hi, how i can contact the repository admin of extras devel ? some file has incorrect size/md5/sha1/sha256 in the Packages file . Mar 22 13:24:05 ping X-Fade Mar 22 13:27:07 ping X-Fade Mar 22 13:27:13 ~seen X-Fade Mar 22 13:27:24 x-fade is currently on #maemo #harmattan #meego, last said: 'qronic: just tap star twice'. Mar 22 13:55:15 hi, back from school =) Mar 22 15:38:10 any idea why login on maemo.org seems not to be working? Mar 22 15:40:04 nevermind Mar 22 19:24:00 FYI: size of fremantle extras (arm+i386+source): 6.7gb, testing 8.7gb, devel 25gb ; ONLY coping the last version of each package Mar 22 21:22:10 hmm Mar 22 21:23:01 every time i take off the battery in my N900, the clock resets.. I suppose this is because of the backup battery has drained, no? Mar 22 21:23:12 DocScrutinizer: infobot joined! Mar 22 21:24:16 FIQ, DocScrutinizer once said those backup batteries only last for about a year... Mar 22 21:24:25 if that's the cause, I'll have to use my calculator as a portable source for checking the time I guess Mar 22 21:24:31 Yes, and I have no plans on buying a new Mar 22 21:24:33 ntpd Mar 22 21:24:38 oh Mar 22 21:24:40 ntpd works Mar 22 21:25:02 Assuming you have some net, of course. Mar 22 21:25:06 yeah Mar 22 21:25:10 hm Mar 22 21:25:47 my USB port is broken, and as N900 product line has ended far ago, and that problem is (pretty much?) impossible to fix, I'll stick to an external battery Mar 22 21:26:00 too bad if i end myself in a "you need to reflash" situation.. :p Mar 22 21:26:28 You can reflash - if you install a bootloader, and do it from meego Mar 22 21:26:43 Hm, that works I suppose Mar 22 21:26:44 Or something else booted from SD Mar 22 21:26:50 yes Mar 22 21:27:34 I once had a fully working archlinux setup (just for fun), and still think I have.. but the problem is the bootloader Mar 22 21:27:39 uboot works fine, but.. Mar 22 21:27:57 I don't really want to compile it from source to get it to work with powerkernel Mar 22 21:28:48 especially since the one time I tried to install Maemo SDK, i got a load of interesting bugs here and there... Mar 22 21:29:22 i need to install rtcom-accounts-voip-support Mar 22 21:29:36 i think i broke something and now i cant find it... Mar 22 23:50:52 hmmm Mar 22 23:51:13 forcing newer qemu got ubuntu in a strange state Mar 22 23:51:45 -f install wants to remove 942mb Mar 22 23:52:24 --force is rarely the right thing to do Mar 22 23:52:30 yeah Mar 22 23:53:09 update manager offer partial update and just hangs for a couple of hours Mar 22 23:53:56 and what does apt-get dist-upgrade offer you? Mar 22 23:53:57 wish reflash of ubuntu took minutes like maemo Mar 22 23:54:06 heh Mar 22 23:55:06 try using -f Mar 22 23:55:28 all this just from a new qemu? Mar 22 23:55:54 couple of debs of newer versions Mar 22 23:56:20 but got tired after 5th or so Mar 22 23:56:33 was hoping it would be a couple Mar 22 23:57:03 qemucommon, kvm, libgnutls, libpulse, libtinfo Mar 22 23:57:41 guess installing proper versions of those might fix it Mar 22 23:57:52 ought to Mar 22 23:57:56 still all versions were oneiric Mar 22 23:58:09 didn't expect that much of a prob Mar 22 23:58:18 and the base distro is what? Mar 22 23:58:24 11.1p Mar 22 23:58:27 0* Mar 22 23:58:38 or maybe I need to enable devel of some kind Mar 22 23:58:49 are you saying you force-installed oneiric packages onto an oneiric system and that broke everything?? Mar 22 23:59:01 seems like it Mar 22 23:59:13 might be just missing devel(ish) repo Mar 22 23:59:25 so cries not found for latest versions Mar 22 23:59:35 not sure how buntu handles that Mar 23 00:01:03 natty* Mar 23 00:07:39 ok libpulse0 and libgnutls reinstall fixed it Mar 23 00:14:06 Hi, is there some tool for sending sms on schedual? Mar 23 00:21:44 cron + smssend? Mar 23 00:27:18 szopeen: could you provide an example please? Mar 23 00:27:48 google man crontab Mar 23 00:28:01 say I want to send a msg "Hello" to 13913900999 on 2012/03/24 08:00 Mar 23 00:28:10 ok, will do it Mar 23 00:28:12 this will let you schedule running of smssend - command line sms sender Mar 23 00:32:29 oh, I can't access to http://maemo.org/packages/view/smssend/ ... Mar 23 00:33:02 me neither atm Mar 23 00:33:13 seems not only talk.maemo... got problems Mar 23 00:33:46 ok... will wait for its working, thank you for your help, szopeen :) Mar 23 00:34:02 repo might be up, so apt-get install smssend could work Mar 23 00:34:27 oh, forgot it ;p Mar 23 00:34:29 thread about it is also working Mar 23 00:34:55 so you could possibly tinker, not sure though Mar 23 00:35:41 I'm reading the thread, yes, sounds it's what I'm looking for Mar 23 00:37:51 does clockd is a cron like app on maemo? Mar 23 00:38:23 crontab should be stock-installed Mar 23 00:38:32 not sure what clockd offers Mar 23 00:40:34 both give me output (though clockd error of some kind), maybe busybox power only got crontab??? usyBox v1.19.3 (Debian 1.19.3power5) multi-call binary. this one definitely has it Mar 23 00:41:25 oh, maemo.org is back! Mar 23 00:41:57 you could always keep watch -n (seconds till send) xterm window open, but that is hardly useful Mar 23 00:51:49 szopeen: yes. and I find cron or crontab doesn't exist on stable repo, maybe I have to get them from testing or unstable repo Mar 23 00:52:23 what happens when you type crontab in xterm? Mar 23 00:54:06 szopeen: -sh: crontab: not found Mar 23 00:54:16 install busybox-power Mar 23 00:55:46 szopeen: thanks, it sounds interesting, will do it later, my N900 can't access network currently :( Mar 23 00:56:18 got it with latest it seems, so might need devel or testing, not sure Mar 23 00:56:59 but if you can use clockd for the same effect might be worth exploring (no idea what clockd is) Mar 23 00:57:36 if you get it running report back :) Mar 23 00:57:43 gotta run Mar 23 00:57:53 gn all Mar 23 01:01:37 oh, what's the font name in screenshot of busybox-power at http://oi54.tinypic.com/14v7dzm.jpg? looks beautifully Mar 23 01:01:51 szop|afk: thank you! Mar 23 01:05:26 oh, it's not called clockd, it's named alarmd ;p **** ENDING LOGGING AT Fri Mar 23 02:59:58 2012