00:13.01 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
01:39.39 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@222.190.112.229) |
02:29.31 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
03:42.04 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
04:24.25 | *** join/#maemo-ssu SpacedOut (david@SubSpace.fries.net) |
05:10.12 | *** join/#maemo-ssu luf (luf@nat/ibm/x-gmcfjlcssyhcbcbm) |
06:00.02 | freemangordon | peetah: you need libqtm12 |
06:16.07 | *** join/#maemo-ssu fw190 (a47e83c0@gateway/web/freenode/ip.164.126.131.192) |
06:16.22 | fw190 | morning all |
06:16.49 | kerio | moin |
06:16.50 | fw190 | freemangordon: when I try to install bootimage with cssu kernel HAM doesn't allow to do that |
06:16.58 | fw190 | any hints how to solve this? |
06:18.05 | kerio | fw190: install a fake package that provides kernel-feature-errata-430973-workaround |
06:18.19 | kerio | and make sure you never ever ever ever ever boot with a kernel that's not thumb-enabled |
06:18.25 | fw190 | I could only use bootimage for uboot with kp 50 |
06:18.38 | kerio | (i assume you're on cssu-thumb) |
06:18.42 | fw190 | well I did it twice ;) |
06:19.01 | kerio | you shouldn't, it's undefined behaviour |
06:19.14 | fw190 | I'm on thumb but from time to time I like to test what Nemomobile looks like |
06:19.14 | kerio | programs may behave strangely before they crash |
06:19.26 | kerio | what does it look like? |
06:19.33 | fw190 | well with thumb and stock kernel it doesn't boot even |
06:19.42 | fw190 | well no wit looks much better |
06:19.46 | fw190 | with the new ui |
06:20.02 | kerio | fw190: anyway, it's a dependency problem |
06:20.14 | kerio | all the thumb packages depend on kernel-feature-errata-430973-workaround |
06:20.15 | fw190 | ah ok |
06:20.24 | kerio | which is provided by kernel-power-flasher or kernel-cssu-flasher |
06:20.30 | fw190 | so where from shoul I get this errata |
06:20.35 | fw190 | and how to install it |
06:20.39 | kerio | it's not a "thing" |
06:20.41 | fw190 | so I can have palis uboot |
06:21.13 | kerio | make a fake package |
06:21.36 | fw190 | uhhhh now you are demanding huge things from a end user ;) |
06:22.40 | DocScrutinizer05 | the problem is uBoot comes with kernel. AIUI this isn't a thumb kernel, so uBoot isn't compatible with thumb userland |
06:22.58 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
06:23.31 | kerio | DocScrutinizer05: the problem is that there's no way to tell apt "i'm only ever going to boot this OS with a thumb-enable kernel, so act as if the dependency is met" |
06:23.38 | kerio | you know, without making an actual package |
06:24.13 | DocScrutinizer05 | how would you guarantee you never boot with uBoot standard kernel? |
06:24.15 | fw190 | I remeber that a few kp ago I compiled a power kernel with uboot on the device itself and had Kp wit uboot all in one |
06:24.24 | fw190 | there was a tutorial somewhere on tmo for this |
06:24.34 | fw190 | ? |
06:24.35 | fw190 | would it be possible with the lates thing |
06:24.43 | kerio | DocScrutinizer05: by... never booting with it? |
06:24.44 | kerio | idk |
06:24.52 | kerio | fw190: you're using uboot, you're not an end user anymore |
06:24.53 | DocScrutinizer05 | fw190: probably |
06:25.16 | kerio | ~pali |
06:25.16 | infobot | i guess pali is http://atrey.karlin.mff.cuni.cz/~pali/ |
06:25.22 | fw190 | kerio: pali wrote what to do when I like an moron booted stock one ;) |
06:25.40 | kerio | there were some prebuilt .debs outside of the repos |
06:25.51 | fw190 | he wrote what to do to always have booting the kp not the stock one |
06:25.51 | freemangordon | fw190: I missed what is your problem with installing -bootimg |
06:25.59 | kerio | freemangordon: the usual, unmet deps |
06:26.08 | fw190 | freemangorson: it doesnt instal froom HAM |
06:26.10 | freemangordon | kerio: should not be |
06:26.14 | kerio | fw190: can you open a terminal and type sudo apt-get install kernel-cssu? |
06:26.16 | kerio | freemangordon: he's using uboot |
06:26.18 | freemangordon | fw190: but why? |
06:26.19 | kerio | or something |
06:26.23 | kerio | fw190: er, sorry |
06:26.26 | fw190 | doesn't say |
06:26.27 | kerio | sudo apt-get install kernel-cssu-bootimg |
06:26.37 | freemangordon | fw190: what is in the problems tab? |
06:26.45 | freemangordon | kerio: wait a minute |
06:26.57 | fw190 | it's written in Polsih: something like it can not be installed |
06:27.03 | fw190 | Polsih |
06:27.06 | kerio | freemangordon: he wants to use uboot with cssu-thumb |
06:27.07 | fw190 | damn |
06:27.09 | fw190 | Polish |
06:27.21 | freemangordon | kerio: yes, i understand that |
06:27.39 | freemangordon | fw190: and what is the reason it cannot be installed |
06:27.48 | tadzik | hello |
06:28.09 | freemangordon | tadzik: hi |
06:28.20 | kerio | fw190: can you pastebin the output of "apt-get install kernel-cssu-bootimg"? don't confirm anything if it asks for a confirmation |
06:28.54 | fw190 | hmmm My N900 is now a modem with qt hotspot so I don't know if I can apt-get someting |
06:29.04 | fw190 | will try and report |
06:29.07 | fw190 | aaaa |
06:29.08 | fw190 | one more thing |
06:29.11 | kerio | you don't need internet for it |
06:29.17 | kerio | apt already knows how the dependencies wor |
06:29.18 | kerio | k |
06:29.26 | fw190 | I don't have palis uboot now installed |
06:29.38 | fw190 | should I have it to test or it is not recomended |
06:30.16 | freemangordon | fw190: you need pali's uboot for all of the KP flavours, most probably that is why you cannot install -bootimg |
06:30.43 | kerio | yeah, the -bootimg depends on multiboot-kernel-power |
06:30.55 | freemangordon | conficts? |
06:30.59 | fw190 | freemangordon: when I last tried it I had palis uboot |
06:31.11 | fw190 | funny thing |
06:31.13 | kerio | and that pulls in multiboot |
06:31.16 | kerio | which is awful |
06:31.17 | fw190 | without ubbot it installed |
06:31.24 | fw190 | without problems |
06:31.41 | kerio | fw190: ask Pali where's the uboot+kp51 build he ha |
06:31.42 | kerio | d |
06:31.42 | kerio | i know he has one |
06:31.42 | freemangordon | fw190: well, you have some dependency problem, run the command kerio posted and we'll see it |
06:32.02 | fw190 | freemangordon: I just did and it installed without uboot on board |
06:32.07 | fw190 | without problems |
06:33.39 | kerio | hmm... free space on the rootfs? |
06:33.52 | kerio | also, do you have multiboot installed? |
06:33.54 | fw190 | 70mb |
06:33.56 | fw190 | no |
06:34.00 | fw190 | I do not use multiboot |
06:34.06 | kerio | hm |
06:34.07 | kerio | oh well |
06:34.07 | fw190 | jus have backupmenu |
06:35.12 | fw190 | ok |
06:35.19 | fw190 | now I have the uboot image |
06:35.24 | fw190 | and uboot on board |
06:35.44 | fw190 | but how to check it on reboot I will have the option for kernel power? |
06:35.58 | Skry | fw190: can you install/have you installed uboot from http://talk.maemo.org/showthread.php?t=81613 ? |
06:36.02 | fw190 | so I don't end up like an idiot with brick for the third time ;) |
06:36.22 | fw190 | I have the latest uboot from op from Pali |
06:37.20 | freemangordon | fw190: you'd better read u-boot thread or ask Pali, it was too long aglo I was playing with u-boot |
06:38.08 | Skry | fw190: I can send you the combined uboot+cssu kernel image if I find it on my hdd so you can flash it, if you want |
06:38.51 | Skry | or you can do it by yourself from whatever kernel you want |
06:39.10 | Skry | http://talk.maemo.org/showpost.php?p=1150859&postcount=6 |
06:39.14 | fw190 | wait |
06:39.20 | fw190 | it installed ok. |
06:39.28 | fw190 | I will post the output |
06:39.33 | fw190 | there are some errors |
06:45.33 | *** join/#maemo-ssu fw190 (6df33f5e@gateway/web/freenode/ip.109.243.63.94) |
06:45.39 | fw190 | I'back |
06:45.50 | fw190 | here is the output whle instaling boot image |
06:46.43 | fw190 | http://pastebin.com/7BMCJ3F2 |
06:48.32 | Skry | it's just complaining about missing kernel for bootmenu entry |
06:52.42 | *** join/#maemo-ssu fw190_ (6df33f5e@gateway/web/freenode/ip.109.243.63.94) |
06:52.53 | fw190_ | skry: thanks |
06:53.00 | fw190_ | I removed the entry for kp50 |
06:53.17 | fw190_ | and just did a reboot |
06:53.23 | fw190_ | and everything works ok |
06:53.28 | Skry | congrats :) |
06:53.31 | fw190_ | ;) |
06:54.35 | fw190_ | but the funny thing is that even after reflash and on CSSU T I was unable to install uboot bootimage on latest kp from devel or for cssu kernel using HAM |
06:54.44 | fw190_ | from command line it went well |
06:54.50 | fw190_ | without problem |
06:54.58 | fw190_ | except informatinal complaines |
06:57.24 | Skry | problems like that are quite common |
06:59.33 | Skry | I never liked debian package management, add HAM to that and things happen or not. |
07:01.26 | *** join/#maemo-ssu andre__ (~andre@ip-89-176-24-140.net.upcbroadband.cz) |
07:01.26 | *** join/#maemo-ssu andre__ (~andre@Maemo/community/bugmaster/andre) |
07:03.35 | fw190_ | skry: thanks for the info |
07:03.52 | fw190_ | and thanks to all for helping me out ;) |
07:04.14 | Skry | np |
07:06.20 | Skry | time get some sleep |
07:47.16 | kerio | Skry: the debian package management isn't meant to do stuff like that |
07:47.20 | kerio | for a reason :) |
07:47.56 | kerio | packages for bootloaders mostly only install the utilities to install the bootloader |
07:48.39 | *** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm) |
07:54.22 | *** join/#maemo-ssu FireFly (~firefly@oftn/member/FireFly) |
07:58.51 | peetah | freemangordon: ok thanks I'll install it later in the day and let you know how it feels compared to FF14 |
08:01.37 | kerio | =D |
08:03.37 | *** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com) |
08:21.24 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
08:30.55 | *** join/#maemo-ssu arcean (~Arcean@aacu210.neoplus.adsl.tpnet.pl) |
08:37.48 | peetah | freemangordon: libqtm12 package is already installed on my n900 |
08:46.12 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
09:19.20 | *** join/#maemo-ssu marcdeop (~marc@176.red-80-28-121.adsl.static.ccgg.telefonica.net) |
09:24.53 | *** join/#maemo-ssu ivgalvez_ (~ivgalvez@89.140.113.138.static.user.ono.com) |
09:25.32 | *** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com) |
09:25.55 | *** join/#maemo-ssu arcean_ (~Arcean@aaen138.neoplus.adsl.tpnet.pl) |
09:31.00 | *** join/#maemo-ssu ivgalvez (~ivgalvez@89.140.113.138.static.user.ono.com) |
09:41.04 | *** join/#maemo-ssu fw190 (6df33f5e@gateway/web/freenode/ip.109.243.63.94) |
09:41.37 | fw190 | freemangordon: with the latest thum and transitions set to 10 the N900 is fast as lightning |
09:41.52 | fw190 | just like I would have a new phone A.D. 2012 |
09:43.31 | tadzik | what are "transitions set to 10?" |
09:43.54 | fw190 | tadzik: there is an app |
09:44.00 | fw190 | to set the transitions |
09:44.09 | fw190 | i changed every value to 10 |
09:44.28 | fw190 | so now it doesn't take that much to do things |
09:44.31 | fw190 | and it feels faster |
09:45.05 | tadzik | I installed some "OMG Fastest transitions for N900" from tmo, and it is actually a lot faster |
09:45.20 | tadzik | it just removes all the eye-candy for the sake of responsiveness |
09:45.32 | fw190 | there is an app in the repo so you can tweak it as you wish |
09:46.01 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
09:55.02 | Lava_Croft | tadzik: the 'Smooth' transitions? |
09:55.27 | Lava_Croft | The 'smooth' transitions you can find on TMO are actually the best I have come across over the years |
09:56.29 | Lava_Croft | tadzik: http://talk.maemo.org/showthread.php?t=83000 |
09:57.58 | tadzik | I use those from http://talk.maemo.org/showthread.php?t=78591 |
09:58.13 | Lava_Croft | I used those before, but i really love the animations |
09:58.22 | Lava_Croft | those Smooth ones really are smooth :) |
09:58.34 | tadzik | but are they equally fast? |
09:58.51 | tadzik | I don't care much for the jumping icons :) |
10:00.12 | marcdeop | thanks for the link, I'm gonna try it |
10:02.09 | Lava_Croft | tadzik: no, they are slower |
10:02.21 | Lava_Croft | But thats what i mean, i dont like the istant transitions:) |
10:02.27 | Lava_Croft | If you want speed, stick to what you are using now |
10:04.34 | marcdeop | the transitions are indeed smooth |
10:04.38 | marcdeop | good :) |
10:04.40 | Lava_Croft | yeah, it amazed me |
10:15.38 | Skry | okay that video got me interested |
10:15.54 | Skry | that looks.. smooth. |
10:57.41 | *** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl) |
12:00.53 | tadzik | ~seen freemangordon |
12:00.57 | infobot | freemangordon <~freemango@130-204-50-168.2074221835.ddns.cablebg.net> was last seen on IRC in channel #maemo, 4h 23m 50s ago, saying: 'cityLights: what is written in th "problems" tab in application mamanger?'. |
12:00.57 | tadzik | infobot: help |
12:01.03 | tadzik | ah, ok |
14:52.25 | *** join/#maemo-ssu Pali (~pali@unaffiliated/pali) |
15:07.38 | *** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
15:12.58 | *** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se) |
15:18.37 | freemangordon | tadzik: are you ready with opera-thumb.deb? :P |
15:18.45 | tadzik | freemangordon: not yet :) |
15:18.55 | tadzik | mind if I PM you? |
15:19.06 | freemangordon | but,but.. you had almost 18 hours |
15:19.09 | freemangordon | :D:D:D |
15:19.13 | freemangordon | tadzik: no |
15:24.28 | marcdeop | hey guys, I've been out of touch from maemo for a few months |
15:24.41 | marcdeop | do you know if there's been any work in idle imap support? |
15:41.53 | *** join/#maemo-ssu NIN101 (~NIN@p5DD2881D.dip0.t-ipconnect.de) |
16:15.55 | *** join/#maemo-ssu lizardo (lizardo@nat/indt/x-xquclnhalwcikndz) |
16:49.02 | *** join/#maemo-ssu Pali (~pali@unaffiliated/pali) |
17:03.14 | freemangordon | merlin1991: http://talk.maemo.org/showpost.php?p=1268398&postcount=737 |
17:03.22 | freemangordon | is it the same in -testing? |
17:12.45 | *** join/#maemo-ssu fredrinLap (~fn@cm-84.208.108.15.getinternet.no) |
17:30.34 | *** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz) |
17:37.27 | freemangordon | luf: did you manage to fix bluex build? |
17:46.01 | luf | Not yet and I see the BT name bug since last phone reboot :( |
17:46.26 | freemangordon | :( |
17:46.27 | *** join/#maemo-ssu kerio (kerio@unaffiliated/kerio) |
17:57.49 | luf | Strange it survived 3 or 4 reboots. After that I installed backupmenu and after reboot I get the weird BT name. |
18:01.12 | freemangordon | hmm |
18:01.26 | freemangordon | could be something related to boot order? |
18:01.56 | luf | No idea. |
18:02.55 | luf | freemangordon: Didn't you write that you're able to compile bluez? |
18:03.21 | freemangordon | only with gcc 4.2.1 if I don;t do reconfigure |
18:03.45 | freemangordon | hmm, and anly the one in the repos (iirc) |
18:03.48 | freemangordon | not yours |
18:20.02 | *** join/#maemo-ssu _ade_ (~arno@52481E0B.cm-4-1a.dynamic.ziggo.nl) |
18:21.04 | luf | I can reproduce the strange name behavior :D And I can survive with right name ... |
18:21.22 | freemangordon | luf: you're my hero |
18:21.35 | freemangordon | now you only need to fix the packaging :P :D:D:D |
18:21.47 | freemangordon | luf: what happens? |
18:22.13 | luf | No I'm not. And I think I'm unable to fix autoconf mess :( |
18:22.36 | _ade_ | freemangordon: how about a wiki page for gcc 4.7 / thumb2 in scratchbox? |
18:22.40 | *** join/#maemo-ssu Woody14619 (~Woody@66-162-186-66.static.twtelecom.net) |
18:22.40 | *** join/#maemo-ssu Woody14619 (~Woody@Maemo/Community/council/Woody14619) |
18:22.41 | _ade_ | my last attempt resulted in some strange compiler warning for a simple test program |
18:22.53 | _ade_ | and the resulting (thumb2) was bigger then the 4.2 compiled version.. |
18:23.43 | freemangordon | _ade_: it is a very good idea, unfortunately I was short of spare time |
18:24.03 | _ade_ | who isn't ;-) |
18:24.13 | freemangordon | _ade_: btw I don't know how to start a wiki page :D |
18:24.35 | _ade_ | I just made one for the replacement clock. |
18:24.44 | luf | freemangordon: you're bad guy :D |
18:24.46 | freemangordon | luf: I was joking about autoconf, I will look at it when I have some spare time |
18:25.14 | luf | freemangordon: Yes you don |
18:25.24 | luf | don't have spare time :D |
18:26.30 | luf | So when I enable BT and reboot the BT name persist. When I never enable BT during uptime and reboot the BT name was lost (empty) and it leads to strange name when enable BT. |
18:26.48 | luf | I have to try what about enable BT, disable BT, reboot |
18:26.52 | luf | Ugh. |
18:28.58 | freemangordon | _ade_: could you make an empty page, I will fill it's contents |
18:29.35 | _ade_ | freemangordon: sure |
18:29.47 | freemangordon | thanks. |
18:30.05 | _ade_ | what would be the best title? |
18:30.17 | freemangordon | hmm, |
18:30.18 | luf | freemangordon: just empty page? I hope _ade_ can help more ... |
18:30.36 | freemangordon | luf: don't think so |
18:30.41 | luf | ok. |
18:30.56 | _ade_ | I will to the spellingcheck :-) |
18:31.08 | freemangordon | _ade_: "CSSU-thumb toolchain setup"? |
18:31.22 | freemangordon | luf: ^^^ ? |
18:31.23 | _ade_ | sound good to me |
18:32.00 | freemangordon | can wiki page title be edited? |
18:32.03 | luf | _ade_: every help is good |
18:32.18 | luf | freemangordon: what are you asking me for? |
18:32.25 | freemangordon | the name |
18:32.32 | _ade_ | freemangordon: never tried, but I suppose it can be changed |
18:32.33 | freemangordon | any better idea? |
18:32.43 | freemangordon | luf: ^^^ |
18:32.45 | luf | freemangordon: You can remove the page and copy to another in worst case ;) |
18:33.05 | luf | I'm sorry I'm one of the worst in naming ... |
18:33.38 | _ade_ | I will post the wiki link over here later |
18:34.00 | freemangordon | _ade_: "CSSU-thumb toolchain setup(gcc4.7.2-linaro)" |
18:34.16 | freemangordon | _ade_: ok |
18:34.28 | freemangordon | I will try to do it tomorrow |
18:34.33 | luf | freemangordon: have you read what I wrote about BT name? It's funny. |
18:34.38 | freemangordon | luf: yes |
18:35.07 | _ade_ | freemangordon: ok |
18:36.38 | freemangordon | luf: it seems you're missing some initialization |
18:36.54 | DocScrutinizer05 | huh? make ampty wiki page??? WUT? |
18:37.06 | freemangordon | DocScrutinizer05: not funny |
18:37.07 | kerio | MAKE AMPTY WIKI PAGE |
18:37.19 | kerio | luf: does the bug appear if you keep bt on? |
18:37.44 | freemangordon | DocScrutinizer05: I have NFC where to even start |
18:38.00 | DocScrutinizer05 | http://wiki.maemo.org/N900_Hardware_Power_management/lkdsökjdshkjdskjfeHglihg |
18:38.13 | _ade_ | freemangordon: http://wiki.maemo.org/CSSU-thumb_toolchain_setup_%28gcc4.7.2-linaro%29 |
18:38.21 | freemangordon | _ade_: thanks |
18:38.32 | DocScrutinizer05 | http://wiki.maemo.org/N900_Hardware_Power_management/lkdsökjdshkjdskjfeHglihg |
18:38.41 | DocScrutinizer05 | DAMN |
18:38.47 | DocScrutinizer05 | http://wiki.maemo.org/LkdsökjdshkjdskjfeHglihg |
18:38.57 | kerio | my xchat doesn't want to open that D: |
18:39.15 | Lava_Croft | links like that only work in proper irc clients |
18:39.20 | kerio | Lava_Croft: fu |
18:39.45 | DocScrutinizer05 | freemangordon: see the "There is currently no text in this page, you can search for this page title in other pages or edit this page." ? |
18:39.56 | DocScrutinizer05 | see it's actually links under it? |
18:41.04 | luf | freemangordon: I didn't write the code :) |
18:48.58 | luf | kerio: I don't understand you question (I'm sorry my wife come back so we have to discuss a lot of things). |
18:49.08 | kerio | the BT name bug |
18:49.18 | luf | boot + enable BT + reboot = ok BT name |
18:49.22 | kerio | does it appear if you always keep bluetooth on? |
18:49.25 | kerio | alright |
18:49.30 | luf | boot + reboot = empty BT name |
18:49.51 | luf | I'm trying boot + enable BT + disable BT + reboot |
18:50.38 | luf | kerio: I have disabled BT by default after boot. |
18:51.18 | kerio | huh, why? :c |
18:51.19 | luf | kerio: the bug is for bluze-4.99 (while maemo bluez is 4.60 ;) ) |
18:51.51 | luf | kerio: because of battery and I use BT rarely when I'm driving ... |
18:52.11 | kerio | luf: no carkit? D: |
18:52.19 | kerio | but aren't you the dude of the carkit? |
18:52.37 | luf | Yes I'm ;) |
18:53.44 | luf | Shit. So if BT is disabled when firing reboot the BT name after reboot is empty. WTF where is the name stored? It doesn't get it from /etc/bluetooth/main.conf or /var/lib/bluetooth/<BT id>/config :( |
18:55.07 | kerio | i bet it's something silly |
18:55.08 | kerio | like cal |
18:55.24 | luf | what is cal? |
18:56.35 | kerio | it's a land of happiness and magic |
18:56.40 | kerio | also /dev/mtd1 |
18:57.33 | luf | Great so it's easy. Just to find the way into the mirror :D |
19:01.16 | DocScrutinizer05 | BS, BT name isn't in CAL |
19:01.51 | luf | DocS: WTF is CAL? |
19:02.05 | kerio | i said "i bet" |
19:02.13 | DocScrutinizer05 | if there's no separate BT names et (NFC if there's even such thing), then it uses /etc/hostname afaik |
19:02.20 | DocScrutinizer05 | ~CAL |
19:02.20 | infobot | cal is, like, a calendar. try $(cal 1752) |
19:02.30 | kerio | no, it doesn't use /etc/hostname |
19:02.35 | DocScrutinizer05 | ~whatiscal |
19:02.47 | DocScrutinizer05 | MEH! |
19:03.03 | DocScrutinizer05 | luf: /dev/mtd1 aka "config" |
19:04.53 | luf | DocS: thanks. |
19:05.10 | luf | Shit the magic is more dark than I think ... |
19:06.41 | luf | It's enough to change /var/lib/bluetooth/<BT id>/config: mode on and the name appears ... So it depends if the BT device is on during kernel module or something like that. |
19:06.54 | luf | (appears after reboot) |
19:07.09 | luf | * during loading kernel module ... |
19:07.22 | luf | It's big bull .... |
19:09.06 | DocScrutinizer05 | luf: here you are: |
19:09.08 | DocScrutinizer05 | t900:~# grep -r IroN999 /etc /var /home/user/ 2>/dev/null |
19:09.10 | DocScrutinizer05 | /var/lib/bluetooth/A8:7E:33:CD:E5:2B/config:name IroN999 |
19:11.28 | luf | I know but it's ignored if you have mode off (in same file) when you fire reboot. |
19:11.45 | luf | I'm working with bluez-4.99 on N900 ;) |
19:12.00 | DocScrutinizer05 | if BT is off, so how would BT name matter... And to whom even? |
19:12.31 | luf | You want to specify BT name each time you reboot? Don't be silly. |
19:13.30 | luf | Please DocS read the history (last hour or so) at first. |
19:14.57 | luf | I appreciate you want help me but this doesn't help me. |
19:17.05 | DocScrutinizer05 | well, sorry I won't study last hour of backscroll |
19:18.43 | *** join/#maemo-ssu ekze-nyan (~nyan@bakaekze.ru) |
19:19.06 | DocScrutinizer05 | I just tell you there's three locations for device name: cat var/lib/bluetooth/*/config; cat /etc/hostname; gconftool -g /apps/modest/device_name |
19:19.16 | DocScrutinizer05 | that's it, do with it whatever you like |
19:20.13 | luf | ok, thanks |
19:21.27 | DocScrutinizer05 | of course also in /home/user/.modest/local_folders/*/*/*/*/*/* |
19:22.28 | *** join/#maemo-ssu ekze_nyan (~nyan@bakaekze.ru) |
19:22.38 | luf | What is modest for? |
19:22.51 | DocScrutinizer05 | hmm? |
19:22.57 | *** join/#maemo-ssu BCMM (~ben@unaffiliated/bcmm) |
19:22.58 | DocScrutinizer05 | mail? |
19:24.12 | luf | Why it contains BT name in gconf? |
19:24.24 | DocScrutinizer05 | I said device name |
19:25.04 | DocScrutinizer05 | waitwaitwait |
19:25.37 | DocScrutinizer05 | no, don't wait ;-D |
19:25.40 | luf | For sure it's BT name. My device (hostname) is another. |
19:29.06 | DocScrutinizer05 | [2012-09-19 20:53:45] <luf> Shit. So if BT is disabled when firing reboot the BT name after reboot is empty. WTF where is the name stored? It doesn't get it from /etc/bluetooth/main.conf or /var/lib/bluetooth/<BT id>/config :(<< honestly, doesn't make sense to me. The BT name is stored in var/lib/bluetooth/*/config, only there and nowhere else |
19:30.47 | DocScrutinizer05 | And I'm really sorry I dared to ask how there can be a BT name when BT is off, since - again sorry - I'm too simple to see where from I would get BT name value when BT is off |
19:31.36 | DocScrutinizer05 | of course BT name is empty when BT is off (unless you talk about /var/lib/bluetooth/<BT id>/config) |
19:32.15 | luf | BT device not bluetoothd daemon. And when I activate BT device the BT is empty => get it from driver not from config. |
19:32.29 | DocScrutinizer05 | (btw I actually *did* read backscroll, before I first answered) |
19:32.47 | luf | bluze-4.60 takes value from config all the time. It doesn't matter if BT device is on or off. |
19:33.47 | DocScrutinizer05 | so where's the problem? |
19:34.32 | DocScrutinizer05 | you got a bug in some of your BT stack when it doesn't manage to set up BT name according to /var/lib/bluetooth/<BT id>/config |
19:34.52 | DocScrutinizer05 | I never seen that though |
19:35.22 | luf | bluez-4.99 when BT mode off during boot - there is empty value in BT name (in settings). When I enable BT device it put some mess into BT name (chip name) from driver. That's the problem. |
19:35.45 | luf | DocScrutinizer05: there are even reports on TMO or bugzilla with bluez-4.60. |
19:36.09 | DocScrutinizer05 | :shrug:, IO've never experienced that |
19:36.38 | freemangordon | luf: so forward-port the patch that reads the name from gconf and you should be ok |
19:37.25 | luf | freemangordon: the name is in config too but it doesn't take it into account :( |
19:38.35 | freemangordon | luf: iirc you can get the name of the device by a dbus call |
19:38.43 | freemangordon | lemme try to find that code for you |
19:39.01 | luf | Never mind. I'll try debug the bluetoothd (I know how to "fix it") do I can compare these two situation. |
19:39.29 | luf | freemangordon: Yes, it's empty when no dbus call due to no device activation during boot. |
19:39.58 | luf | I remember I tried go deeper into the problem 3 month ago. |
19:40.26 | DocScrutinizer05 | freemangordon: name from gconf??? |
19:40.33 | DocScrutinizer05 | which one? |
19:40.36 | luf | Today I can reproduce wrong and right result so I'm one step further :) |
19:40.49 | kerio | i thought there was just *one* device name, and you set it in the bluetooth settings panel |
19:42.07 | DocScrutinizer05 | kerio: until you set /etc/hostname, or device name in modest |
19:42.19 | kerio | /etc/hostname is unrelated i think |
19:42.28 | kerio | i didn't know modest also knew how to set the device name |
19:42.35 | luf | kerio: you're right. |
19:42.39 | DocScrutinizer05 | *sigh* |
19:42.54 | DocScrutinizer05 | kerio: modest has *his own* device name |
19:42.59 | kerio | oic |
19:43.04 | DocScrutinizer05 | just like system has /etc/hostname |
19:43.49 | DocScrutinizer05 | kerio: probably you could even argue xchat has another instance of device name, though it's called server name there iirc |
19:43.56 | kerio | hahahahaha |
19:44.58 | DocScrutinizer05 | kerio: and yes, the name in var/lib/bluetooth/*/config will be set via the settings/BT dialog only |
19:45.37 | DocScrutinizer05 | (modulo niche cases like reflashing or reste-to-factory) |
19:46.21 | luf | Good the problem is in initialization for sure :D |
19:46.22 | luf | BT disabled + boot + BT name empty + enable BT + BT name like RCM2048XY Initial configuration + reboot + BT name back to the correct value :) |
19:46.47 | DocScrutinizer05 | luf: how T F so you "enable BT"? |
19:47.41 | luf | Click on time or icons -> enable BT (or you can use System -> Settings -> Bluetooth -> (un)check Enabled) |
19:48.11 | DocScrutinizer05 | since I guess the hildon settings dialog will read out the name from var/lib/bluetooth/*/config, fill it in as initial text to the textedit box, and on "save" initializes BT stack with whatever is in that textbox (besides writing it also back to var/lib/bluetooth/*/config) |
19:48.44 | luf | You're wrong. |
19:48.57 | luf | The dialog settings get it from DBUS call :D |
19:49.04 | DocScrutinizer05 | mhm |
19:49.05 | freemangordon | :nod: |
19:49.23 | freemangordon | string Name [readwrite] |
19:49.32 | DocScrutinizer05 | so where from does DBUS get it then? IOW whom is settings->BT *asking* for the name? |
19:49.55 | freemangordon | DocScrutinizer05: what I see in the code: |
19:50.00 | DocScrutinizer05 | yaknow, each dbus msg has a destination |
19:50.01 | luf | bluez. |
19:50.16 | freemangordon | ir tries "read_pretty_host_name" |
19:50.27 | luf | bluetoothd to be precise |
19:50.36 | freemangordon | and after that (af the above fails) "read_local_name" |
19:50.51 | DocScrutinizer05 | LOL |
19:50.58 | DocScrutinizer05 | makes sense |
19:51.00 | luf | freemangordon: it doesn't work neither to set pretty_host_name in bluez. |
19:51.02 | freemangordon | read_local_name gets it from /var/lib.../config |
19:51.27 | freemangordon | luf: gimme some time to see who calls that |
19:51.40 | luf | freemangordon: No it doesn't in case of "initialization problem" |
19:51.42 | freemangordon | adaptername_probe() is that |
19:51.53 | DocScrutinizer05 | still my question: what's dbus destination when settings->BT is the sender? |
19:52.09 | freemangordon | luf: maybe it waits for a kernel event |
19:52.21 | freemangordon | (which never comes as we use an old kernel) |
19:52.38 | DocScrutinizer05 | good shot |
19:52.50 | freemangordon | luf: handle_inotify_cb :P |
19:53.06 | freemangordon | guess who :D |
19:53.08 | DocScrutinizer05 | freemangordon: realy now? |
19:53.13 | luf | freemangordon: I think about it ... but why it works then when the BT is enabled during boot. |
19:53.20 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
19:53.55 | luf | freemangordon: ? kp50 is too old? Does KP51 implement it? |
19:54.04 | luf | I think about some BT changes in kernel ... |
19:54.14 | freemangordon | I can bet it registers inotify_cb, and enumerates already enabled devices |
19:54.31 | freemangordon | at least I will do it that way :D |
19:54.35 | luf | freemangordon: this sound reasonable ... |
19:54.51 | freemangordon | luf: lets find how the old bluez does it |
19:55.00 | luf | Does KP51 implement inotify_cb ? |
19:55.11 | freemangordon | luf: does not matter |
19:55.14 | luf | old one is dead. |
19:55.27 | luf | It works even with the name very different way. |
19:55.40 | luf | freemangordon: why it doesn't matter? |
19:55.49 | freemangordon | luf: come on, gimme 5 more minutes :P |
19:56.01 | luf | 4:48 ... |
19:56.11 | luf | 4:34 ... |
19:56.40 | luf | We're very good here. We can even take 60 minutes in 40 minutes :D |
19:57.10 | freemangordon | like my new watch? he is "rocket" :P |
19:57.16 | freemangordon | s/he/it/ |
19:57.37 | luf | :D So 5 minutes left ... |
20:00.12 | DocScrutinizer05 | no, he said "5 *more*..." |
20:00.24 | luf | Docs: He had -10 mintues ;) |
20:00.54 | DocScrutinizer05 | actually he had 5 now |
20:02.11 | DocScrutinizer05 | luf, my abstract virual debugging shows it's obviously the kernel driver or some daemon that gets loaded only when BT gets enabled |
20:02.27 | freemangordon | DocScrutinizer05: no |
20:02.55 | freemangordon | bluetooth enables (loads, whatever) the adapter in question and waiths a callback event |
20:03.07 | DocScrutinizer05 | :nod: |
20:03.18 | freemangordon | that event never comes as the kernel does not support inotify |
20:03.30 | DocScrutinizer05 | still :nod: |
20:03.34 | freemangordon | (in bt driver at least) |
20:03.57 | DocScrutinizer05 | while during boot it does udev-events-playback-late or whatever the script is named |
20:04.00 | freemangordon | adapter named ir read from configuration file on "adapter up" event |
20:04.15 | freemangordon | DocScrutinizer05: could be, NFC |
20:04.35 | DocScrutinizer05 | meh |
20:04.56 | freemangordon | DocScrutinizer05: but I believe that on bootup already enabled adapters are enumerated and initialized |
20:05.42 | freemangordon | AIUI old bluez sets device properties on "adapter enable" dbus call |
20:05.53 | freemangordon | luf: ^^^ |
20:06.07 | DocScrutinizer05 | here you are: (4 lines spam!) |
20:06.10 | DocScrutinizer05 | Sep 19 22:16:24 t900 kernel: [29803.526702] hci_h4p hci_h4p: firmware: requesting bcmfw.bin |
20:06.12 | DocScrutinizer05 | Sep 19 22:16:24 t900 bluetoothd[909]: HCI dev 0 up |
20:06.13 | DocScrutinizer05 | Sep 19 22:16:24 t900 bluetoothd[909]: Starting security manager 0 |
20:06.15 | DocScrutinizer05 | Sep 19 22:16:24 t900 bluetoothd[909]: Adapter /org/bluez/909/hci0 has been enabled |
20:06.33 | DocScrutinizer05 | (this device is 10 min ahead of time) |
20:06.51 | luf | Shit it isn't so easy ... |
20:06.56 | DocScrutinizer05 | but those are the 4 lines in syslog, when you enable BT |
20:06.58 | freemangordon | 4.99 waits for "/org/bluez/909/hci0 has been enabled" inotify |
20:07.12 | freemangordon | luf: what is not easy? |
20:08.14 | luf | When I debugged it (shit I removed the syslog one week ago). It tried to initialize correct name and after that it gets the wrong one. I was unable to find the source. |
20:08.35 | luf | But it sounds very good what you're saying free. |
20:09.01 | DocScrutinizer05 | and that's dbus (systembus): |
20:09.03 | DocScrutinizer05 | signal sender=org.freedesktop.DBus -> dest=(null destination) serial=84 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged |
20:09.05 | DocScrutinizer05 | <PROTECTED> |
20:09.06 | DocScrutinizer05 | <PROTECTED> |
20:09.08 | DocScrutinizer05 | <PROTECTED> |
20:09.08 | luf | I'm sorry I'm upgrading VIO so I'm not so responsible as I want. |
20:09.09 | DocScrutinizer05 | method call sender=:1.541 -> dest=org.freedesktop.DBus serial=426 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=ReleaseName |
20:09.11 | DocScrutinizer05 | <PROTECTED> |
20:09.17 | DocScrutinizer05 | oops, more lines than it looked like |
20:10.06 | freemangordon | WTF? |
20:10.08 | freemangordon | inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask) |
20:10.18 | freemangordon | #define MACHINE_INFO_DIR "/etc/" |
20:10.18 | freemangordon | #define MACHINE_INFO_FILE "machine-info" |
20:10.38 | luf | It's the pretty name ... |
20:10.53 | luf | If I remember it right. But it doesn't work neither. |
20:10.56 | DocScrutinizer05 | no fsckng such file here, I *bet* |
20:11.01 | freemangordon | luf: try echo luf > /etc/machine-info |
20:11.10 | freemangordon | while BT enabled without name |
20:11.18 | luf | freemangordon: ^^^ |
20:11.24 | freemangordon | luf: I know |
20:11.51 | freemangordon | please try it, to see if the name will appear |
20:12.00 | freemangordon | "luf" name I mean |
20:12.13 | DocScrutinizer05 | nah froblshnarz |
20:12.59 | luf | You don't trust me ... :)D |
20:13.43 | freemangordon | luf: elaborate please |
20:13.57 | DocScrutinizer05 | dafaq, inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask) -- now I realize what they're doing |
20:14.06 | luf | In progress ... N900 doesn't boot in one sec ... |
20:14.20 | luf | But you don't trust me. It hurts :D :D |
20:14.27 | freemangordon | DocScrutinizer05: and what did you realize? |
20:14.43 | DocScrutinizer05 | >><freemangordon> while BT enabled without name<< |
20:15.04 | freemangordon | luf: you're a big boy, you can stand a little pain :P |
20:15.19 | DocScrutinizer05 | those donkeyballsuckers use /etc/ for a dynamic file |
20:15.28 | freemangordon | yeah |
20:15.39 | freemangordon | called machine-info :P |
20:15.46 | freemangordon | or not? |
20:15.54 | DocScrutinizer05 | looks like |
20:16.08 | freemangordon | luf: could you just touch /etc/fmg? |
20:16.28 | freemangordon | instead of machine-info |
20:16.52 | freemangordon | (not sure it will work though, didn;t read the whole code) |
20:17.34 | DocScrutinizer05 | lazybone |
20:17.51 | freemangordon | but, but.. then we miss some daemon. |
20:18.03 | freemangordon | ur it is udev to do that? |
20:18.06 | freemangordon | *or |
20:18.13 | DocScrutinizer05 | NFC |
20:18.20 | luf | You're right that you don't trust me. |
20:18.20 | DocScrutinizer05 | you ate the code |
20:18.30 | freemangordon | luf: I know |
20:18.40 | DocScrutinizer05 | without sharing more than 3 small lines |
20:18.40 | freemangordon | :P |
20:19.09 | freemangordon | DocScrutinizer05: someone should touch a file in /etc on BT adapter up |
20:19.31 | freemangordon | it is not a part of bluez aiui |
20:19.37 | freemangordon | luf: what happened? |
20:20.21 | luf | freemangordon: but do you dive into 4.99 code to take a look how they initialize it (not machine-info - it's ugly workaround). |
20:20.43 | luf | freemangordon: what you expected. |
20:20.44 | freemangordon | initialize what? |
20:20.49 | freemangordon | adapter name? |
20:20.59 | freemangordon | yes |
20:21.01 | luf | BT when the BT device is off during boot. |
20:21.12 | DocScrutinizer05 | someone should s§inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask) §dbus-wait-signal("path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged", 'string "com.nokia.connui_bluetooh_status_menu_item-cp_plugin-conbtui"') § |
20:21.23 | freemangordon | i looked into the code, that is why I posted inotify_cb here |
20:21.37 | freemangordon | DocScrutinizer05: no |
20:21.44 | freemangordon | gimme 5 more minutes :D:D:D |
20:22.00 | luf | freemangordon: 4.99 or 4.60 ? |
20:22.07 | freemangordon | 4.99 |
20:22.26 | freemangordon | it is totally different in 4.53 (that is wht I have here) |
20:23.23 | luf | Where do you have 4.53? There is no bluez for win XP ... :D |
20:23.45 | DocScrutinizer05 | waaait |
20:23.46 | freemangordon | from repository.maemo.org |
20:24.04 | DocScrutinizer05 | Sep 19 22:16:24 t900 kernel: [29803.526702] hci_h4p hci_h4p: firmware: requesting bcmfw.bin |
20:24.13 | luf | I'm going to switch to another machine ... There is 4.60 in maemo ... |
20:24.16 | DocScrutinizer05 | set inotify on bcmfw.bin |
20:24.28 | luf | I'll be offline for few minutes ... |
20:24.58 | DocScrutinizer05 | I'm afk for a few beers |
20:25.01 | freemangordon | DocScrutinizer05: waaaait, lets see how is that supposed to work with newer kernels :) |
20:25.09 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz) |
20:25.49 | DocScrutinizer05 | should I guess? udev writing there |
20:26.23 | DocScrutinizer05 | I'm guessing all the time |
20:26.40 | freemangordon | still NFC |
20:26.43 | *** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz) |
20:26.43 | freemangordon | http://www.spinics.net/lists/linux-bluetooth/msg13459.html |
20:26.44 | DocScrutinizer05 | since evil freemangordon eats all the code all alone |
20:27.00 | freemangordon | this is the commit that does the shit |
20:27.45 | DocScrutinizer05 | ohfsck, that's too nasty |
20:27.45 | freemangordon | doc will like that one: |
20:27.48 | freemangordon | "This file is part of systemd's hostnamed functionality:" |
20:27.56 | DocScrutinizer05 | WAAAAAHHHH!!! |
20:28.09 | DocScrutinizer05 | see? I said "udev" |
20:28.23 | freemangordon | noo, it is systemd :P |
20:28.23 | DocScrutinizer05 | udev sufered poettering treatment |
20:29.00 | freemangordon | but it still makes no sense to me |
20:29.03 | DocScrutinizer05 | "embrace and suffocate" |
20:29.32 | freemangordon | what will happen (on desktop) when I pull my usb BT adapter? |
20:29.40 | freemangordon | what in /etc will chage? |
20:29.46 | freemangordon | DocScrutinizer05: ^^^? |
20:29.58 | DocScrutinizer05 | oooh makes perfect sense to me, it's poettering. Only poettering can think of "let's write to /etc/ to signal an event to $random_process" |
20:30.17 | freemangordon | ~poettering |
20:30.17 | infobot | 'sth is poettering' means it acts invasive, possessive, destructive, and generally in an egocentric exacerbating negative way. ``this cancer is extremely poettering'' |
20:30.50 | freemangordon | DocScrutinizer05: anyway, who the hell writes in /etc? |
20:30.57 | DocScrutinizer05 | nfc |
20:31.03 | freemangordon | kernel? i doubt |
20:31.08 | DocScrutinizer05 | inotify-monitor |
20:31.18 | freemangordon | WT is that? |
20:31.52 | luf | freemangordon: inotifi is only for the file ... |
20:31.57 | freemangordon | luf: hmm, did you check if bluez provides some udev/systemd rules? |
20:32.12 | freemangordon | luf: inotify if for the whole /etc |
20:32.29 | DocScrutinizer05 | inotify-watch and inotify-monitor are commands |
20:33.01 | luf | Shit. As I expected it's not reboot persistent. If the file exists it ignores the file :D That's what I tested few month ago. |
20:33.23 | DocScrutinizer05 | luf: you understand inotify? |
20:33.44 | DocScrutinizer05 | [2012-09-19 22:13:56] <DocScrutinizer05> dafaq, inotify_add_watch(inot_fd, MACHINE_INFO_DIR, mask) -- now I realize what they're doing |
20:33.47 | freemangordon | luf: yes, you need someone to touch a file in /etc after bluetoothd is started |
20:33.53 | luf | I know. |
20:34.02 | luf | I just want a proof. |
20:34.13 | luf | BTW maybe I see my problem ... |
20:34.27 | freemangordon | touch /etc/fmg_proof |
20:34.33 | luf | No. |
20:34.40 | freemangordon | yes |
20:34.42 | DocScrutinizer05 | lol |
20:34.44 | luf | The problem in code ... |
20:34.52 | freemangordon | we don't want machine-info in /etc |
20:35.20 | freemangordon | luf: what is the problem? |
20:35.32 | DocScrutinizer05 | figue /me going mad ;-P |
20:35.42 | luf | I'm trying to search if I'm not wrong ... |
20:36.02 | luf | Do you see: |
20:36.02 | luf | /* And disable the name change now */ |
20:36.02 | luf | adapter_set_allow_name_changes(adapter, FALSE); |
20:36.37 | DocScrutinizer05 | halebop:~ # ls -l /etc/machine-id |
20:36.38 | DocScrutinizer05 | -r--r--r-- 1 root root 33 Nov 10 2011 /etc/machine-id |
20:36.39 | freemangordon | luf: that happens in case you have /etc/machine-info |
20:36.51 | DocScrutinizer05 | well, seems old enough? |
20:36.56 | freemangordon | luf: and that disables name updates using dbus call |
20:37.26 | freemangordon | luf: remove your /etc/machine-info and touch /etc/fmg_proof |
20:37.29 | luf | Yes. And it enable name updates otherwise. And that is the problem. |
20:38.09 | DocScrutinizer05 | http://linux.die.net/man/1/inotifywatch |
20:38.36 | freemangordon | luf: there is this udev rule: |
20:38.38 | freemangordon | ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/local/sbin/bluetoothd --udev" |
20:39.54 | DocScrutinizer05 | http://linux.die.net/man/1/inotifywait |
20:40.03 | DocScrutinizer05 | not *monitor |
20:41.15 | luf | What does the action mean? |
20:41.30 | luf | BTW it was enough to remove the machine-info file ... |
20:43.39 | freemangordon | luf: yes |
20:43.58 | freemangordon | any change in /etc will lead to name re-read |
20:44.14 | freemangordon | even touch /etc should do it |
20:44.46 | freemangordon | dafaq |
20:45.11 | freemangordon | reading /var/lib/... is a backup |
20:45.33 | freemangordon | this is intended to work with exising /etc/machine-info |
20:46.00 | DocScrutinizer05 | freemangordon: hey, with inotifywatch we could easily find out about all commands and libs used in early boot, before /opt available :-D |
20:47.40 | luf | freemangordon: but backup where another name change is allowed. |
20:48.10 | freemangordon | luf: yes yes. and we should not have /etc/machine-info anyway |
20:48.33 | freemangordon | the question remains - who TF touches /etc |
20:49.29 | freemangordon | anyway, I will have to wakeup really early tomorrow |
20:49.30 | freemangordon | so I am kleaving |
20:49.30 | freemangordon | *leaving |
20:51.15 | freemangordon | night, wish you luck with finding how exactly udev touches /etc :D |
20:51.17 | DocScrutinizer05 | on desktop? |
20:51.17 | freemangordon | yes |
20:51.17 | DocScrutinizer05 | hmmm |
20:51.18 | DocScrutinizer05 | ponders mkfifo |
20:51.20 | freemangordon | I mean - when a BT adapter is enableds |
20:51.48 | luf | It uses another way for sure. |
20:51.49 | DocScrutinizer05 | or even a stale nfs-link ;-P |
20:51.55 | luf | good nigth. |
20:51.57 | freemangordon | luf: though I thing we can safely revert http://www.spinics.net/lists/linux-bluetooth/msg13459.html |
20:52.14 | freemangordon | (or the patch in bluez tree) |
20:52.17 | freemangordon | night |
20:54.40 | luf | freemangordon: not true. There are more changes ... It's not so simple/ |
20:55.37 | freemangordon | well, the simple task was for me (to find what/how happens) :P |
20:55.48 | freemangordon | night, really |
21:02.56 | freemangordon | luf: an idea - call stupid callback function manually from dbus "adapter_enable" handler |
21:19.16 | luf | freemangordon: Were not you going sleep? :D |
21:20.00 | luf | freemangordon: I'm looking into it. I don't understand why during boot it can't set adaptername when it can set it in the callback. |
21:20.17 | luf | And for sure it's called using register_driver ... |
21:21.25 | luf | And the create/delete/write operation has to be on /etc/machine-info there is a if in the callback. |
21:31.00 | DocScrutinizer51 | maybe during boot some idiot writes to /etc? |
21:31.29 | luf | I don't think so. |
21:37.48 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz) |
21:39.47 | DocScrutinizer51 | the fsck knows what's mask set to on this buggy line |
21:40.14 | DocScrutinizer51 | maybe is's already sufficient to read the /etc |
21:48.18 | luf | DocScrutinizer51: come on ... |
21:48.35 | luf | +if (pevent->len && + pevent->name != NULL && + strcmp(pevent->name, MACHINE_INFO_FILE) == 0) { +changed = TRUE; |
21:48.58 | luf | I know you don't trust me. But I wrote that the machine-info is checked in the callback. |
22:01.46 | DocScrutinizer05 | I toldya freemangordon ate all that code without sharing a single char |
22:03.18 | DocScrutinizer05 | the one who decides it would be a good idea to have a semaphore gile in /etc(!!!) might also fsckup mask and forget to check return values |
22:03.33 | DocScrutinizer05 | ~lart lennart |
22:03.33 | infobot | tries to shut lennart up |
22:03.44 | DocScrutinizer05 | ~uselss |
22:03.49 | DocScrutinizer05 | ~useless |
22:03.49 | infobot | ACTION starts crying and hides from docscrutinizer05 in the darkest corner of the room. :( |
22:04.04 | DocScrutinizer05 | ~kill lennart |
22:04.04 | infobot | ACTION shoots a charged pseudoneutrino gun at lennart |
22:05.52 | DocScrutinizer05 | torturing poor NAND for such utter bullshit concept (completely ignoring it's not at all safe from arbitrary "race" conditions when other processes mess with the /etc) |
22:06.56 | DocScrutinizer05 | ooh, he actually did share |
22:07.14 | DocScrutinizer05 | switches to that rotting browser window |
22:08.30 | DocScrutinizer05 | God! is that just me or is c source text indigestible in those patches, with that leading "+" |
22:13.42 | DocScrutinizer05 | if (changed != FALSE) { |
22:13.50 | DocScrutinizer05 | OOOOUUUUUUUUUUUUUUUUCCHH!!! |
22:14.40 | DocScrutinizer05 | if (((changed != FALSE) == TRUE ) != FALSE) { |
22:15.29 | DocScrutinizer05 | if ((((changed != FALSE) == TRUE ) != FALSE) && (changed == changed) == TRUE)){ |
22:16.34 | *** join/#maemo-ssu _rd (~rd@p57B49547.dip0.t-ipconnect.de) |
22:16.43 | DocScrutinizer05 | just to be sure X-P |
22:18.39 | *** join/#maemo-ssu myuu__ (~miku@pool-108-27-201-196.nycmny.fios.verizon.net) |
22:18.58 | luf | You're sure sure sure of sure :D |
22:20.43 | DocScrutinizer05 | luf: dafaq am I getting senile or is the while friggin function static gboolean handle_inotify_cb() not returning any meaningful return-value or triggering any meaningful event besides DBG(MACHINE_INFO_DIR MACHINE_INFO_FILE ?? |
22:20.58 | DocScrutinizer05 | s/while/whole/ |
22:21.43 | DocScrutinizer05 | ooh, it indeed triggers manager_foreach_adapter((adapter_cb) adaptername_probe, NULL); |
22:22.07 | luf | Yeah in time when there is no adapter ;) |
22:23.10 | luf | Ahh sorry, it triggers what you said. |
22:23.41 | luf | There is aslo register_driver which trigger the same foreach (in time when no adapter is loaded) :D |
22:42.14 | merlin1991 | did I miss anything today? |
22:42.50 | luf | I think nothing urgent. Just DocS as usual want to be sure sure sure of sure :D |
22:54.23 | DocScrutinizer05 | merlin1991: how's about >> if ((((changed != FALSE) == TRUE ) != FALSE) && (changed == changed) == TRUE)){ |
22:56.14 | RST38h | while(0==0) *(void *)0=0; |
22:56.24 | DocScrutinizer05 | or maybe >> if ((changed != FALSE) && (TRUE == changed)) |
22:58.13 | merlin1991 | ETOOMANYPARENTHESIS |
22:58.51 | DocScrutinizer05 | ENFCBOOLALGEBRA |
22:59.23 | DocScrutinizer05 | +if (changed != FALSE) { |
22:59.24 | DocScrutinizer05 | +DBG(MACHINE_INFO_DIR MACHINE_INFO_FILE |
22:59.26 | DocScrutinizer05 | +" changed, changing names for adapters"); |
22:59.28 | DocScrutinizer05 | OUUUUUUCH! |
23:00.05 | merlin1991 | where does all that come from? |
23:00.08 | DocScrutinizer05 | if (!changed == FALSE) |
23:00.14 | DocScrutinizer05 | http://www.spinics.net/lists/linux-bluetooth/msg13459.html |
23:00.39 | DocScrutinizer05 | From: Bastien Nocera <hadess@xxxxxxxxxx> |
23:01.18 | DocScrutinizer05 | oops |
23:01.25 | DocScrutinizer05 | if (~changed == FALSE) |
23:03.14 | DocScrutinizer05 | if !(changed == FALSE) |
23:04.52 | merlin1991 | DocScrutinizer05: you should combinbe them with ^ aswell |
23:05.11 | DocScrutinizer05 | lol |
23:05.37 | DocScrutinizer05 | actually comparing something against TRUE is a terrible idea, in C |
23:05.51 | DocScrutinizer05 | comparing against FALSE is just silly |
23:06.56 | merlin1991 | is currently lost, 0 is true and everything else false, or how did it go? |
23:07.13 | DocScrutinizer05 | I think so |
23:07.18 | DocScrutinizer05 | nah |
23:07.22 | DocScrutinizer05 | other way round |
23:07.48 | merlin1991 | yep |
23:08.02 | merlin1991 | makes sense |
23:08.13 | merlin1991 | otherwise if(fp) { ... code would be stupid :D |
23:08.15 | DocScrutinizer05 | there's one FALSE, and a zillion differnts truthes |
23:08.42 | merlin1991 | sounds like politics |
23:08.47 | DocScrutinizer05 | which is quite interesting, philosophically |
23:09.02 | merlin1991 | you just don't tell them they make more money than they do, everything else is just a shade of the truth ;) |
23:27.25 | *** join/#maemo-ssu arcean (~Arcean@aaen138.neoplus.adsl.tpnet.pl) |