| *** louisdk has joined #maemo | 01:47 | |
| *** clopez has quit IRC | 02:02 | |
| *** clopez has joined #maemo | 02:06 | |
| *** dafox has joined #maemo | 02:07 | |
| *** louisdk has quit IRC | 02:18 | |
| *** dafox has quit IRC | 02:27 | |
| *** florian has quit IRC | 02:53 | |
| *** Pali has quit IRC | 03:15 | |
| *** SpeedEvil has quit IRC | 03:24 | |
| *** SpeedEvil has joined #maemo | 03:27 | |
| *** BitEvil__ has joined #maemo | 03:38 | |
| *** SpeedEvil has quit IRC | 03:38 | |
| *** Michael_a380 has joined #maemo | 04:23 | |
| *** lxp has joined #maemo | 06:02 | |
| *** lxp1 has quit IRC | 06:03 | |
| *** spinal84 has joined #maemo | 06:27 | |
| *** DocScrutinizer05 has quit IRC | 07:07 | |
| *** DocScrutinizer06 has joined #maemo | 07:07 | |
| *** DocScrutinizer06 is now known as DocScrutinizer05 | 07:07 | |
| *** Oksanaa has joined #maemo | 07:11 | |
| Oksanaa | What's wrong with the device? http://www.ebay.com.au/itm/291998141306 | 07:18 |
|---|---|---|
| hurrian | no USB door/SIM holder? | 07:36 |
| Oksanaa | Huh, the SIM holder should be easy to insert, question is how to add USB door, since it should be rotating on a hinge? | 07:37 |
| hurrian | if you buy one brand new off eBay, you can just push it in - I don't have the service manual on me right now but it's easy to install | 07:38 |
| hurrian | don't need to take off the screen etc - just push it in. takes a bit more force to pull it out though | 07:39 |
| Oksanaa | Do the WiFi/Bluetooth/Camera on the device work, otherwise? If USB door is easy to install, and the case itself is not bent/damaged, then a repair should be straightforward... | 07:40 |
| Michael_a380 | Is anyone bidding? I was going to bid, it's 2 miles / 3 km from me. | 07:40 |
| Oksanaa | Not going to bid. I am NSW, shipping would add up. | 07:40 |
| Oksanaa | I already have a cyan N9, into which I inserted a SIM tray; it had no problems with USB door, though. | 07:41 |
| Oksanaa | Michael_a380 : Good luck, you will be able to pick it up locally, and that's very nice. | 07:42 |
| Michael_a380 | Thanks. I'm still a little skeptical about unremovable battery. I found 'doors' here http://www.easyphix.com.au/?rf=kw&kw=Nokia+n9. Seems pricey for a bit of plastic. | 07:44 |
| Michael_a380 | Reflash sounds like a nightmare, compared to n900. | 07:47 |
| hurrian | Michael_a380: first thing you'd need to do is check software version - if it's on an old release, flash to PR1.3 region 001 and call it a day :) | 07:48 |
| Michael_a380 | are you sure you don't want it, even as spare? | 07:49 |
| Michael_a380 | You would probably have better use of it. | 07:50 |
| Michael_a380 | It's sad that the bad guys are winning: Trustworthy Nokia N9 vs spying Android http://www.abc.net.au/technology/articles/2011/12/06/3384952.htm | 07:54 |
| Oksanaa | Michael_a380 : Not that simple, the charging port cover is. http://thumbs.ebaystatic.com/images/g/RPcAAOSwnH1WZlmq/s-l225.jpg | 07:55 |
| Michael_a380 | wow, thanks | 07:55 |
| Oksanaa | Yes, we have no Android here, so far. Or WinPhone. Or iPhone. Or even Blackberry. Just some Firefox OS, some Symbian, some Maemo, some Harmattan, some Nemo. In various states of usability. | 07:57 |
| Michael_a380 | First thought the 'black part' was missing from the 'charger door' ad. Did you notice the charger door ad? http://www.easyphix.com.au/nokia-n9-charging-port-cover-red | 08:01 |
| Oksanaa | Feel free to find Nokia N9 service manual | 08:01 |
| Oksanaa | The small triangle of black plastic looks like a shadow. | 08:05 |
| Michael_a380 | Not sure what you're refering to? Would the plastic 'dents' indicate the screen was removed (phone was opened)? | 08:09 |
| Oksanaa | Nay. Just, whatever accident caused removal of SIM tray and USB door, might have caused some bends. In my case, the corner of the device is slightly bent, so it's difficult for SIM tray to stay in here; it prefers to jump out. | 08:11 |
| Oksanaa | Slightly, like, 1mm or less. | 08:11 |
| Oksanaa | Feel free to register with NickServ, and/or https://maemo.org | 08:17 |
| *** Oksanaa has quit IRC | 09:03 | |
| *** Oksanaa has joined #maemo | 09:22 | |
| Oksanaa | N900 frightened me for a minute. After changing battery, it looked like LCD was cracked; 3+ parts of display, working or black or white; when touching, the parts changing their states (their shapes, too ; have seen a pentagon once). 1st clue: in list of apps, text was fine, icons weren't here. 2nd clue: LCD cracks don't disappear or change that quickly. Display driver glitch. Reboot fixed it. | 09:25 |
| sicelo- | :-) | 09:41 |
| Michael_a380 | N900: "It's just a prank, bro". | 09:44 |
| *** Michael_a380 has quit IRC | 09:47 | |
| *** Oksanaa has quit IRC | 10:14 | |
| *** Oksanaa has joined #maemo | 10:18 | |
| KotCzarny | :> | 10:26 |
| *** Oksanaa has quit IRC | 10:33 | |
| *** Oksanaa has joined #maemo | 10:33 | |
| *** Maxdamantus has joined #maemo | 10:49 | |
| *** florian has joined #maemo | 11:02 | |
| *** krnlyng has quit IRC | 11:19 | |
| *** louisdk has joined #maemo | 11:24 | |
| Oksanaa | My hardware keyboard had no backlight. Why could it be? | 11:29 |
| *** krnlyng has joined #maemo | 11:31 | |
| sicelo- | there's a script somewhere (wiki perhaps) which can cycle them .. | 11:32 |
| sicelo- | lots of possibilities .. faulty ribbon being one of them | 11:33 |
| sicelo- | s/ribbon/flex cable/ | 11:33 |
| infobot | sicelo- meant: lots of possibilities .. faulty flex cable being one of them | 11:33 |
| Oksanaa | Keyboard LEDs app : not lighting up | 11:35 |
| Oksanaa | cannot create /sys/class/i2c-adapter/i2c-2/2-0032/engine3_mode: nonexistent directory | 11:38 |
| sicelo- | uh oh | 11:38 |
| *** dafox has joined #maemo | 11:38 | |
| Oksanaa | Does it mean "flex cable damaged" or "driver not loaded"? | 11:39 |
| Oksanaa | Because it used to work recently, like, within last 24h, or I would have found typing difficult earlier | 11:40 |
| Oksanaa | In fact, /sys/class/leds/ has only twl4030:vibrator . Is it the RGB LED near the display? Or is my RGB LED also not working? | 11:45 |
| sicelo- | i might be wrong .. maybe wait for more knowledgeable people to chime in | 11:48 |
| Maxdamantus | It looks like all the other LEDs use the lp5523 controller. | 11:48 |
| Maxdamantus | (keyboard backlight and status LEDs) | 11:48 |
| Maxdamantus | for me they appear as /sys/class/leds/lp5523:{r,g,b,kb{1..6}} | 11:49 |
| Oksanaa | kb ones are not here, definitely. Neither are RGB ones. | 11:50 |
| Maxdamantus | So presumably your status LEDs don't work at all? | 11:50 |
| Maxdamantus | ie, charge/notification indications | 11:51 |
| Oksanaa | Yes, I think so. /Blanks the screen, waits for notification/ | 11:51 |
| Maxdamantus | I imagine a faulty cable wouldn't lead to that, but I'm not entirely sure. | 11:51 |
| Oksanaa | These leds use different cables, right? | 11:52 |
| Oksanaa | /me considers reinstalling mce... In c | 11:52 |
| Maxdamantus | Reinstalling mce won't help. | 11:52 |
| Maxdamantus | I'm not sure what defines all the LEDs as existing. I think in newer kernels it would be defined by device tree. | 11:52 |
| sicelo- | faulty flex definitely does cause non-working (or erratic) status LED .. my 2nd N900 has that | 11:53 |
| Maxdamantus | Yes, of course it can prevent the LEDs from ultimately not working, but I don't think it would cause the LEDs not to show up in sysfs. | 11:53 |
| sicelo- | let me recheck on that N900 | 11:54 |
| *** jon_y has quit IRC | 11:54 | |
| *** jon_y has joined #maemo | 11:55 | |
| sicelo- | yes, i have them in /sys | 11:55 |
| Maxdamantus | I suspect the actual controller is on the motherboard, not the front part. | 11:57 |
| Maxdamantus | and I suspect there'll just be a wire on the ribbon cable for each of the status LEDs. | 11:58 |
| sicelo- | makes sense .... /me would make bad EE | 11:59 |
| Maxdamantus | so with the ribbon cable disconnected, nothing really looks any different. The only way it could notice a difference is if it measured the resistance across the presumed LEDs. | 11:59 |
| Maxdamantus | Oksanaa: I guess the obvious thing to do would be to look through dmesg for something relating to lp5523 | 12:00 |
| Oksanaa | Dmesg : where? /Yes, haven't done it for a very long time/ | 12:01 |
| Maxdamantus | maybe compare it to a normal dmesg .. my phone has been on too long to have the messages from boot atm | 12:01 |
| Maxdamantus | You just run `dmesg`, and capture/analyse the output. | 12:01 |
| *** Oksanaa has quit IRC | 12:10 | |
| *** Oksanaa has joined #maemo | 12:10 | |
| *** Pali has joined #maemo | 12:11 | |
| freemangordon | Pali: hi! As you know I am trying to bring fremantle on jessie. now I am to the point of upstart scripts. How do you think - shall I keep sysvinit compatibility? | 12:15 |
| Pali | hi | 12:15 |
| Pali | this depends on which init daemons we should support | 12:15 |
| Pali | if all --> then upstart scripts needs to be rewritten to init.d scripts | 12:16 |
| freemangordon | well, who is to define that? | 12:16 |
| *** Oksanaa has quit IRC | 12:16 | |
| *** Oksanaa has joined #maemo | 12:16 | |
| Pali | if defaul debian init daemon (systemd) --> then upstart scripts needs to be rewritten to init.d script or systemd services | 12:16 |
| freemangordon | what about upstart only? are there any drawbacks? | 12:16 |
| freemangordon | I mean - /etc/init, not /etc/init.d | 12:17 |
| Pali | if debian version of upstart --> then maemo upstart scripts needs to be moved to /etc/init/ | 12:17 |
| freemangordon | exactly | 12:17 |
| Pali | and if you are going to patch debian version of upstart --> then no change is needed | 12:17 |
| freemangordon | also, I am using devuan, not debian ;) | 12:17 |
| freemangordon | why patch? | 12:17 |
| Pali | because new upstart (in debian) does not scan /etc/event.d anymore | 12:18 |
| freemangordon | ahh, sure | 12:18 |
| freemangordon | but it is packages that should be fixed, not upstart :) | 12:18 |
| Pali | for me solutions are: | 12:18 |
| freemangordon | Pali: see https://github.com/fremantle-gtk2/ke-recv-extra/commit/fd7b7d80de45dfc07c36171e4c2d2a7a8b5672d4 | 12:19 |
| Oksanaa | mce.ini has Modules=display;keypad;vibrator;led;battery;filter-brightness-als;inactivity;alarm;accelerometer;callstate;camera;homekey;audiorouting , correct? Not seeing anything in dmesg, even when I restart mce, or ask ledpatterneditor to test a pattern | 12:19 |
| Pali | 1. rewrite everything to init.d scripts --> this is supported by any init system (daemon which should be restarted on crash could use dsme) | 12:19 |
| Maxdamantus | Oksanaa: it wouldn't be an issue with mce. The kernel is responsible for populating things in /sys | 12:20 |
| Pali | 2. rewrite everything to use Debian's upstart --> renaming /etc/event.d to /etc/init.d and rewrite all Maemo init.d scripts to upstart | 12:20 |
| Pali | 3. path Debian's upstart to support also /etc/event.d and no change in init.d and upstart scripts is needed | 12:20 |
| freemangordon | Pali: I think I like (2) more then the others, at least for start. but why should we rewrite /etc/init.d scripts for upstart? see what ke-recv-extra startup scripts are doing | 12:21 |
| freemangordon | *than | 12:22 |
| Pali | if we want support for Maemo daemons/applications in other distributions too, I would go with (1) | 12:22 |
| Pali | (2) is basicaly compatible only with distros which have upstart | 12:22 |
| freemangordon | Pali: I see. but that would mean no dependencies between services, right? | 12:22 |
| freemangordon | or rather - hardcoded boot order | 12:23 |
| Pali | in init.d scripts you can specify some dependency | 12:23 |
| Pali | see LSB header | 12:23 |
| freemangordon | even with sysvinit? | 12:23 |
| Pali | based on headers is generated fixed order | 12:24 |
| Pali | what I do not like is that two different applications are responsible for restarting daemons (upstart and also dsme) | 12:24 |
| freemangordon | Pali: what about - I will go with (2) for now, as I have all the dependencies in place, sort of. as soon as we have something more or less complete, then go for (1)? | 12:25 |
| freemangordon | well, dsme does more things afaik | 12:26 |
| Pali | ok | 12:26 |
| Pali | (1) is harder as (2) | 12:26 |
| Pali | so (1) takes also much more time | 12:26 |
| freemangordon | yes | 12:26 |
| freemangordon | this is why (2), to not lose focus :) | 12:27 |
| freemangordon | Pali: so far I have gtk2 maemo auto-booting to h-d with hildon-status-menu in x86-64 VM :) | 12:27 |
| *** sicelo- has quit IRC | 12:27 | |
| *** spinal84 has quit IRC | 12:28 | |
| freemangordon | ah, and it is gtk2+clutter1.x | 12:28 |
| Pali | what is state of gtk3 version of hildon? | 12:29 |
| Oksanaa | How much would I need to disassemble to have a visual inspection of the led engine on the motherboard? In case, say, a tiny piece of foil made its way inside the device to short-circuit it, or whatever? | 12:29 |
| freemangordon | Pali: well, seems android808 has suspened the work on libhildon, so no much progress in the last 2 weeks | 12:29 |
| Oksanaa | And how is hildon-home?.. | 12:29 |
| freemangordon | Oksanaa: didn't try it so far, but it shoudl work OOB | 12:30 |
| Oksanaa | What else could I reinstall, besides mce, in case the leds not working is a software problem? | 12:31 |
| freemangordon | Pali: but I am really getting reluctant about that gtk3 affair - I don;t really see what are the pros | 12:32 |
| Maxdamantus | (for context: his lp5523 LEDs don't appear in /sys/class/leds) | 12:32 |
| freemangordon | at least in short term | 12:32 |
| Pali | posibility to appear hildon in linux distributions | 12:32 |
| Pali | e.g. in upstart debian | 12:32 |
| freemangordon | how is xfce4 there then? | 12:33 |
| freemangordon | it is gtk2 | 12:33 |
| Pali | but hildon depends on maemo's gtk2 | 12:33 |
| freemangordon | oh, no,no :) | 12:33 |
| Pali | not upstream gtk2 | 12:33 |
| freemangordon | I am using "stock" gtk2 | 12:33 |
| freemangordon | not maemo one | 12:33 |
| freemangordon | ;) | 12:33 |
| Pali | ok | 12:33 |
| Oksanaa | The only thing appearing in /sys/class/leds is twl4030:vibrator | 12:34 |
| freemangordon | Pali: see https://github.com/fremantle-gtk2/hildon/blob/master/hildon/hildon-gtk-module.c | 12:34 |
| Pali | in debian is gtk2 at version 2.24.31 | 12:34 |
| Pali | if there are "no new gtk2 apps" policy, then we could probably ask for inclusion | 12:35 |
| Oksanaa | Because it's not really new, it's old, but recently ported | 12:35 |
| freemangordon | Pali: 2.24.25-3+deb8u1 here | 12:35 |
| freemangordon | but this is devuan jessie | 12:36 |
| Pali | that is in sid ^^^ | 12:36 |
| Pali | jessie is frozen for a long time | 12:36 |
| freemangordon | "Devuan GNU/Linux 1", whatever it is :D | 12:36 |
| freemangordon | but shouldn't make any difference | 12:36 |
| Pali | so... if you think that your new hildon and apps are working fine on stock gtk2, I can try to prepare Debian packaging and ask for inclusion into Debian (sid) | 12:37 |
| Pali | stretch is already frozen for new packages, so it would appear in stretch+1 release... | 12:37 |
| freemangordon | I am using gtk module to "inject" whatever maemo-specific functionality is needed, not complete so far, but I think this is the right way to go | 12:37 |
| freemangordon | also, maybe not all stuff can be implemented, but... | 12:38 |
| freemangordon | still not working fine, I was playing with startup scripts recently | 12:38 |
| freemangordon | Pali: and what about mce, dsme and the other maemo-specific stuff? | 12:39 |
| Pali | good question... | 12:39 |
| Pali | for whole Hildon desktop on Maemo/N900 it is needed | 12:40 |
| freemangordon | what are we aiming for? rebased fremantle, as distro, or hildon-desktop in debian? | 12:40 |
| freemangordon | and this is distro | 12:40 |
| freemangordon | afaik | 12:40 |
| *** pagurus has joined #maemo | 12:40 | |
| Pali | I think rebased fremantle on top of new debian/devuan | 12:40 |
| freemangordon | I think the goal should be mobile distribution | 12:40 |
| Pali | it is right now, yes? | 12:41 |
| freemangordon | which one? | 12:41 |
| Pali | and once it is ok, we can clean code/packages and try to talk with upstart debian | 12:41 |
| freemangordon | ok, but will it still be debian? I simply have no idea how stuff works re distribution wise | 12:42 |
| Pali | I think it should work with both debian and devuan, but we can develop on devuan as it is systemd free and upstart there could be easier without systemd dependences | 12:42 |
| freemangordon | sure | 12:42 |
| freemangordon | that is why I use devuan | 12:42 |
| Pali | yes | 12:42 |
| Pali | but if we want same new package it should go via upstart debian --> and then appear in devuan | 12:43 |
| freemangordon | the point is - so far I have something booting - is it a new distro? | 12:43 |
| Pali | probably yes | 12:43 |
| freemangordon | ok, why not put it on maemo servers then? | 12:43 |
| freemangordon | with mirror of the needed debian packages | 12:44 |
| freemangordon | as I don't think we'll be able to make hildon-desktop compatible with gnome or xfce etc | 12:45 |
| freemangordon | or at least I don;t know how to do it :D | 12:47 |
| *** xkr47 has quit IRC | 12:47 | |
| Wizzup | What do you mean compatible? | 12:48 |
| freemangordon | h-d is single user | 12:49 |
| Pali | ok, I do not see problem with it | 12:49 |
| *** xkr47 has joined #maemo | 12:54 | |
| freemangordon | Pali: problem with what? | 12:55 |
| *** florian has quit IRC | 12:56 | |
| Pali | putting new dist on maemo servers... | 12:56 |
| *** BitEvil__ has quit IRC | 13:04 | |
| *** SpeedEvil has joined #maemo | 13:04 | |
| freemangordon | Wizzup: anny progress with autobuilder? | 13:13 |
| freemangordon | *any | 13:13 |
| *** Michael_a380 has joined #maemo | 13:14 | |
| Oksanaa | /me cheers | 13:15 |
| Wizzup | freemangordon: not since two days ago, however, I think I'll have some initial things working this weekend. | 13:17 |
| freemangordon | Pali: dsme in fremantle upstart job depends on rcS. Any idea what should it depend on upstream? | 13:20 |
| Wizzup | freemangordon: as I understood, I need a git.devuan.org account, upload code there (not sure if that means full source of what is on gh) and then have the pkg built by the CI | 13:20 |
| freemangordon | filesystem? | 13:20 |
| Wizzup | then I can make a branch and trigger builds for it | 13:20 |
| Wizzup | the next step will then be getting a (.deb) repo on their site with the packages | 13:21 |
| Pali | needs to understand what rcS is doing | 13:21 |
| Pali | and then depends on services started by rcS | 13:21 |
| freemangordon | some maemo specific stuff (loading .ko files | 13:21 |
| *** RedW has quit IRC | 13:21 | |
| freemangordon | etc | 13:21 |
| Pali | maybe it needs to depends on dbus? | 13:21 |
| freemangordon | I think no, as there is dsme-dbus job, which waits for dbus | 13:22 |
| freemangordon | rcS depends on startup | 13:22 |
| freemangordon | depending on dbus is safe bet though, but I don;t think it should wait that much | 13:23 |
| freemangordon | I'll make it depend on filesystem | 13:24 |
| enyc | freemangordon: is there any useful process startup type log (or debugging) that can be put in place to see whats slowing down boot getting to the point of mounting extra filesystems (MyDocs/mmc1)? [already sorted fs//fsck part of issue] | 13:30 |
| freemangordon | enyc: /var/log/syslog | 13:35 |
| NeKit | got cogl-x11-tfp demo and clutter toys rendering on Android device through libhybris and some hacks to connect to SurfaceFlinger | 13:36 |
| NeKit | what repos should I try for building hildon-desktop? | 13:37 |
| freemangordon | NeKit: do you have gtk there? | 13:41 |
| NeKit | yes, full Linux chroot | 13:42 |
| freemangordon | which gtk? 2 or 3? | 13:42 |
| freemangordon | anyway, gtk2 port is more functional, try the stuff on https://github.com/fremantle-gtk2 | 13:43 |
| NeKit | currently 2 due to LXDE installed | 13:43 |
| freemangordon | good, ^^^ then | 13:43 |
| freemangordon | most of the needed build dependencies are in place on that repo | 13:44 |
| freemangordon | ping me when there is something missing | 13:44 |
| NeKit | thanks | 13:44 |
| freemangordon | Pali: do you have any idea why hildon-desktop is started from both /etc/X11/Xsessio.pos atn as an upstart service? | 13:46 |
| freemangordon | */etc/X11/Xsession.post and | 13:46 |
| Pali | yes | 13:47 |
| freemangordon | cool | 13:47 |
| Pali | because it is started for user | 13:47 |
| Pali | and not system-wide root service | 13:47 |
| freemangordon | but why upstart service then? | 13:47 |
| Pali | ah, it is also from upstart then | 13:48 |
| Pali | so upstart scripts can depends on "started hildon-desktop"? | 13:48 |
| freemangordon | ah, thanks | 13:48 |
| freemangordon | yeah, makes sense | 13:48 |
| Pali | anyway, it should be started only from X11 | 13:48 |
| Pali | and send event to upstart | 13:49 |
| Pali | hildon-desktop should not be upstart service... but no idea how hard would be to fix this | 13:49 |
| *** pagurus has quit IRC | 13:50 | |
| freemangordon | Pali: ah, there is also hildon-desktop in /etc/init.d :( | 13:50 |
| freemangordon | WTF? | 13:50 |
| Oksanaa | Is it possible that hildon-desktop checks to make sure there is only one instance of itself? | 13:51 |
| Wizzup | Or perhaps the init scripts are not called | 13:51 |
| freemangordon | Wizzup: is that possible? | 13:51 |
| freemangordon | so you think this is some remnant? | 13:51 |
| Wizzup | At least with openrc, I have many scripts that are there, but are never started | 13:51 |
| freemangordon | Pali: what do you think? ^^^ | 13:52 |
| Pali | think about what? | 13:52 |
| freemangordon | could it be that on maemo the stuff in /etc/rcN.d is not called? | 13:53 |
| freemangordon | so /etc/init.d scripts are ignored? | 13:53 |
| *** Kabouik has joined #maemo | 13:53 | |
| Pali | yes, /etc/init.d/ is ignored on maemo's upstart | 13:53 |
| Pali | so /etc/rcN.d is not called | 13:53 |
| freemangordon | ok, that makes sense then | 13:54 |
| freemangordon | so, h-d is only started from Xsession.post | 13:54 |
| Pali | to start /etc/rcN.d in Ubuntu's upstart is /etc/init/rc.conf which do that | 13:54 |
| freemangordon | Pali: but it seems we *do not* want hildon-desktop started from /etc/init.d | 13:55 |
| freemangordon | so I guess I'll have to remove that script | 13:55 |
| Pali | yes | 13:55 |
| freemangordon | ok, thanks | 13:55 |
| Oksanaa | What is /etc/init.d for, then? | 13:58 |
| freemangordon | Oksanaa: remnant from sysvinit | 13:58 |
| *** spinal84 has joined #maemo | 14:06 | |
| *** florian has joined #maemo | 14:08 | |
| freemangordon | Pali: who is supposed to get bootstate? | 14:11 |
| freemangordon | mce? | 14:11 |
| Pali | dsme | 14:12 |
| Pali | but from some file | 14:12 |
| Pali | getbootstate | 14:12 |
| Pali | is there for determinating boot state and it write it to some file | 14:12 |
| *** pagurus has joined #maemo | 14:12 | |
| Oksanaa | Is it safe to upgrade kernel-power on a device with broken charging port? | 14:13 |
| Oksanaa | And, how to reload a kernel module (except for reboot) ? | 14:16 |
| Wizzup | rmmod | 14:16 |
| Wizzup | en then modprobe | 14:16 |
| freemangordon | Pali: oh, it is in package getbootstate which contains /sbin/preinit as well :D | 14:17 |
| freemangordon | that one will be tough, I guess it will wait as the last one on the queue | 14:18 |
| Pali | anyway, all CSSU packages should now work without /proc/bootreaons | 14:18 |
| Pali | and /proc/component_version | 14:19 |
| freemangordon | Pali: sure, but dsme expects something in /tmp/STATE, otherwise it enters MALF and powers-down the machine in a minute | 14:19 |
| Pali | then we should patch it | 14:19 |
| Pali | so that some default state is used | 14:20 |
| freemangordon | or rather check if state is empty in https://github.com/fremantle-gtk2/dsme/blob/master/debian/dsme.upstart#L10 and set it to USER if yes | 14:21 |
| freemangordon | I am not sure we'll have to do that for CSSU though | 14:21 |
| Oksanaa | Anyway, reinstall kernel*modules, and rmmod leds-lp5523; modprobe leds-lp5523; stop mce; start mce; didn't help with getting leds to work | 14:22 |
| freemangordon | Oksanaa: is there anything in dmesg? | 14:22 |
| Oksanaa | Freemangordon: kb_lock, slide, wlan0, onenand_wait: correctable ECC error, wl1251: firmware booted (Rev 4.0.4.3.7) | 14:25 |
| freemangordon | Oksanaa: I meant - after you modprobed leds ko | 14:26 |
| Pali | onenand_wait: correctable ECC error --> looks like nand is going to die... | 14:26 |
| freemangordon | mhm | 14:27 |
| Oksanaa | Right after modprobe, yes. dmesg | grep -v kb_lock | grep -v slide | grep -v wlan0 gives relatively short output | 14:28 |
| freemangordon | NeKit: just pushed some more things to gtk2 h-d please pull again | 14:30 |
| *** RedW has joined #maemo | 14:32 | |
| Pali | freemangordon: or you can use getbootstate binary from getbootstate package | 14:37 |
| Pali | in cssu is version compatible with upstream kernel | 14:37 |
| freemangordon | Pali: I know, the point is that the package that contains getbootstate contains other stuff as well | 14:38 |
| Pali | so you can run getboostate (maybe via upstart job?) before dsme | 14:38 |
| freemangordon | like /sbin/preinit and whatnot | 14:38 |
| freemangordon | so it should be repackaged for upstream maemo | 14:38 |
| Pali | ok | 14:38 |
| freemangordon | but this is low-priority job as of now | 14:39 |
| Pali | ok | 14:40 |
| Pali | freemangordon: can you take these two patches? https://github.com/community-ssu/libmatchbox2/pull/1 https://github.com/community-ssu/hildon-desktop/pull/2 | 14:49 |
| freemangordon | Pali: I guess yes, but won;t happen soon | 14:52 |
| Pali | ok | 14:52 |
| *** Michael_a380 has quit IRC | 14:59 | |
| Vajb | adding smileys to pidgin theme works! | 15:25 |
| Vajb | pidgin smiley theme* | 15:26 |
| *** msava has joined #maemo | 15:59 | |
| *** msava has quit IRC | 16:03 | |
| *** pagurus has quit IRC | 16:15 | |
| *** pagurus has joined #maemo | 16:22 | |
| *** pagurus has quit IRC | 16:52 | |
| *** Birchy has quit IRC | 16:53 | |
| *** pagurus has joined #maemo | 16:54 | |
| *** sicelo- has joined #maemo | 16:54 | |
| freemangordon | Pali: any clue who is supposed to start system dbus on debian? | 16:56 |
| Pali | systemd :-) | 16:57 |
| freemangordon | comeon :( | 16:57 |
| Pali | basically init daemon is starting it when booting | 16:57 |
| freemangordon | wello, no systemd here | 16:57 |
| freemangordon | and I don;t see system dbus, only session | 16:57 |
| Pali | so either sysvinit via /etc/init.d | 16:57 |
| *** pagurus has quit IRC | 16:58 | |
| Wizzup | openrc has an init script for it. so I assume it's the same for upstart | 16:58 |
| Wizzup | Doesn't need systemd | 16:58 |
| Pali | or systemd service (when using systemd init daemon) | 16:58 |
| freemangordon | there is /etc/init.d/dbus | 16:58 |
| freemangordon | but it starts session bus | 16:58 |
| Pali | init daemon is responsible to start system's dbus-daemon | 16:59 |
| freemangordon | omg, in runlevel 2 dbus is not started | 17:00 |
| freemangordon | Pali: shall I start it by "hand" from an upstart script? | 17:01 |
| Pali | https://en.wikipedia.org/wiki/Runlevel#Linux_Standard_Base_specification | 17:02 |
| Pali | 2Multi-user modeDoes not configure network interfaces and does not export networks services.[c] | 17:02 |
| Pali | so it is correct to not start dbus-daemon as it operates on network | 17:02 |
| Pali | 3Multi-user mode with networkingStarts the system normally.[1] | 17:02 |
| freemangordon | hmm | 17:03 |
| Pali | why is not used runlevel 3? | 17:03 |
| freemangordon | but maemo runs on 2 | 17:03 |
| freemangordon | I changed it to 2 | 17:03 |
| freemangordon | but can;t remember what was before that | 17:03 |
| freemangordon | :D | 17:03 |
| *** pagurus has joined #maemo | 17:04 | |
| Pali | anyway, my ubuntu is also running in runlevel 2 | 17:04 |
| freemangordon | on ubuntu there is no inittab | 17:04 |
| Pali | probably something was changed... | 17:05 |
| freemangordon | same here - 2 | 17:05 |
| freemangordon | anyway, I am going to write upstart script that starts dbus no matter the runlevel | 17:05 |
| Pali | and my debian is running in runlevel 5 | 17:06 |
| *** pcfe has quit IRC | 17:06 | |
| freemangordon | Pali: is there inittab in etc? | 17:06 |
| Pali | no, IIRC inittab is not used for a long time... | 17:06 |
| Pali | but this debian is systemd based | 17:07 |
| freemangordon | Pali: and how is default runlevel setup then? | 17:07 |
| Pali | somehow by systemd | 17:07 |
| Pali | no idea | 17:07 |
| *** florian has quit IRC | 17:08 | |
| Pali | in my debian runlevel(8) manpage is writtten: runlevel 5 is systemd target graphical.target | 17:08 |
| freemangordon | cool | 17:09 |
| Pali | upstart cookbook: http://upstart.ubuntu.com/cookbook/#runlevels | 17:10 |
| Pali | 2 : Graphical multi-user plus networking (DEFAULT) | 17:10 |
| Pali | it is big mess! | 17:10 |
| freemangordon | seems so | 17:10 |
| Pali | so if you have LSB init.d script it probably needs to be "modified" for specific linux distribution | 17:11 |
| Pali | as systemd has different numbers for runlevels as upstart and as LSB init.d | 17:11 |
| Pali | or your init.d script should assume that 2 == 3 == 3 == 5 | 17:12 |
| Pali | also == 4 | 17:12 |
| *** Birchy has joined #maemo | 17:24 | |
| *** spinal84 has quit IRC | 17:52 | |
| *** dafox has quit IRC | 17:53 | |
| ceene | Pali: when i first used redhat/mandrake circa 2000, it used 2 by default, and changed to 5 whenever i installed xfree86 | 18:13 |
| ceene | my understanding now is that runlevel became totally obsolete in modern distros | 18:13 |
| KotCzarny | on slackware 3 was default no-x and 4 with x | 18:13 |
| ceene | yeah... distro maintainers just forgot about it | 18:14 |
| ceene | it would make sense to have named customizable runlevels, however only a set of numbered runlevels with restricted functionality doesn't provide enough flexibility, so it just ceased to exist in practice | 18:16 |
| KotCzarny | only 3 runlevels are used nowadays, system start, started, shutting down/poweroff | 18:16 |
| KotCzarny | runlevels are a remnant from server roots of linux | 18:18 |
| KotCzarny | well, unix, but linux was based on their idea | 18:19 |
| sicelo- | ceene: in connection with yappari, would it have been possible to just use Signal only (not to integrate with WA) | 18:22 |
| ceene | if there is a signal library available, it could be done i guess | 18:23 |
| sicelo- | okay | 18:24 |
| *** xkr47 has quit IRC | 18:46 | |
| *** louisdk has quit IRC | 18:50 | |
| *** xkr47 has joined #maemo | 18:58 | |
| *** louisdk has joined #maemo | 19:06 | |
| *** pcfe has joined #maemo | 19:28 | |
| *** pcfe has quit IRC | 19:28 | |
| *** pcfe has joined #maemo | 19:28 | |
| *** florian has joined #maemo | 19:56 | |
| *** Oksanaa has quit IRC | 20:06 | |
| *** florian has quit IRC | 20:08 | |
| *** fuz_ has quit IRC | 20:11 | |
| *** pagurus has quit IRC | 20:17 | |
| *** pagurus has joined #maemo | 20:21 | |
| *** pagurus has quit IRC | 20:26 | |
| *** fuz_ has joined #maemo | 20:35 | |
| *** xkr47 has quit IRC | 20:35 | |
| *** xkr47 has joined #maemo | 20:38 | |
| *** pagurus has joined #maemo | 21:07 | |
| *** Michael_a380 has joined #maemo | 21:08 | |
| *** pagurus has quit IRC | 21:15 | |
| *** florian has joined #maemo | 21:17 | |
| *** pagurus has joined #maemo | 21:20 | |
| *** florian has quit IRC | 21:25 | |
| *** pagurus has quit IRC | 21:28 | |
| *** pagurus has joined #maemo | 21:30 | |
| *** florian has joined #maemo | 21:32 | |
| *** florian has quit IRC | 21:37 | |
| *** spinal84 has joined #maemo | 21:40 | |
| *** pagurus has quit IRC | 21:43 | |
| NeKit | how should be the hildon-desktop from fremantle-gtk2 started? | 21:53 |
| Maxdamantus | ln -s `which hildon-desktop` ~/.xinitrc | 22:16 |
| Maxdamantus | (just my opinion, feel free to ignore it) | 22:16 |
| *** florian has joined #maemo | 22:23 | |
| *** florian has quit IRC | 22:30 | |
| *** jonwil has joined #maemo | 22:55 | |
| jonwil | hi | 23:03 |
| freemangordon | NeKit: did you build it with maemo-launcher support? | 23:04 |
| NeKit | Currently without. Is it needed? | 23:05 |
| freemangordon | NeKit: currently no :) | 23:06 |
| freemangordon | NeKit: you should start it as DISPLAY=:0 hildon-desktop | 23:06 |
| freemangordon | nothing special | 23:06 |
| freemangordon | assuming you have X running | 23:06 |
| freemangordon | NeKit: though, I have no idea how you should start it on wayland or whatever you're using under android | 23:08 |
| NeKit | means I'm missing something, since it gives few GLib-CRITICAL and freezes ( | 23:08 |
| freemangordon | what are those criticals? | 23:08 |
| NeKit | http://pastebin.com/vHUvLiNg | 23:08 |
| NeKit | no Wayland, just Xorg | 23:09 |
| freemangordon | are you sure you build it for gtk2? | 23:09 |
| freemangordon | hmm, the problem might be in clutter 1.0, it has gtk3 backend enabled by default | 23:10 |
| freemangordon | maybe you should rebuild clutter without gdk3 backend | 23:10 |
| freemangordon | NeKit: do ldd on hildon-desktop and make sure there is no libgtk3 involved | 23:11 |
| freemangordon | NeKit: ? | 23:14 |
| NeKit | libgdk-3 is involved | 23:14 |
| NeKit | I will try rebuilding clutter then | 23:14 |
| freemangordon | NeKit: is that chroot some distro-based? | 23:15 |
| NeKit | yes, Arch Linux ARM | 23:15 |
| freemangordon | NeKit: is libgdk3 directly loaded by hildon-desktop or libhildon, or only by libclutter? | 23:16 |
| freemangordon | hmm, weird, I have libgdk3 here as well, but it starts ok | 23:17 |
| NeKit | if I check with ldd, I see at least hildon-desktop and libclutter-1.0.so linked to it | 23:17 |
| freemangordon | same here | 23:18 |
| freemangordon | but, my clutter-dev package is from the modified clutter I rebuild because of the same problem | 23:19 |
| freemangordon | NeKit: maybe first rty with CLUTTER_BACKEND=x11 DISPLAY=:0 hildon-desktop | 23:21 |
| freemangordon | if that doesn't help, I am afraid you'll have to rebuild clutter | 23:22 |
| NeKit | it did the trick | 23:26 |
| freemangordon | really? | 23:26 |
| freemangordon | cool | 23:26 |
| freemangordon | NeKit: I want a video :) | 23:27 |
| freemangordon | NeKit: don't forget to install theme and to copy the backgrounds | 23:28 |
| freemangordon | NeKit: also, you have to symlink /usr/hildon/theme to /usr/shares/theme/default and symlink /usr/shares/theme/default to /usr/shares/theme/alpha (if you install alpha theme). dunno how you're supposed to install debian package on arch linux, but I guess you know | 23:30 |
| NeKit | looks way better with theme and wallpaper :) | 23:38 |
| freemangordon | yes, I know :) | 23:39 |
| freemangordon | NeKit: but, I am afraid that was the easy part. Bringing hildon-status-menu etc needs more stuff, like sapwood and whatnot | 23:41 |
| freemangordon | and maybe working upstart | 23:41 |
| freemangordon | oh, and working dbus | 23:43 |
| NeKit | dbus is probably the least of worries, compared to upstart or sapwood(?) | 23:46 |
| freemangordon | NeKit: sapwood is easy, I have it build for upstream, but it is still not on github | 23:50 |
| freemangordon | NeKit: I can give you debian source package | 23:51 |
| freemangordon | if you want | 23:51 |
| freemangordon | Pali: where was gitorious maemo backup? | 23:53 |
| Pali | which? | 23:53 |
| Pali | gitorious is now in read-only mode | 23:53 |
| Pali | with all git repos | 23:53 |
| freemangordon | oh, ok | 23:54 |
| *** florian has joined #maemo | 23:56 | |
| freemangordon | hmm, FF hung on it | 23:56 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!
