| 00:27.15 | *** join/#maemo infobot (~infobot@rikers.org) |
| 00:27.15 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | DONT FORGET TO VOTE FOR COUNCIL! https://maemo.org/vote/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog |
| 00:27.23 | *** join/#maemo spiiroin (~spiiroin@87-93-92-210.bb.dnainternet.fi) |
| 01:02.09 | *** join/#maemo wnd (~wnd@katei.fi) |
| 01:20.33 | *** join/#maemo g3kk3r (~torrkull@far.torrkulla.net) |
| 02:35.13 | *** join/#maemo g3kk3r (~torrkull@far.torrkulla.net) |
| 03:18.19 | *** join/#maemo pagurus (~user@p4FDC34B8.dip0.t-ipconnect.de) |
| 03:48.16 | *** join/#maemo Vajb (~Vajb@85-76-41-197-nat.elisa-mobile.fi) |
| 04:21.28 | *** join/#maemo sleepee (~sleepee@24.55.74.192) |
| 04:25.37 | timeless | Maxdamantus: so, in redhat, the version of a package could be incredibly patched to the point that the "version" isn't remotely accurate |
| 04:30.36 | Maxdamantus | timeless: you mean the minor version? Sure, so the minor version should change, which means the minor version of the OS that includes it also needs to change (since a user in that OS might compile some software that won't work correctly against the previous minor version) |
| 04:31.10 | timeless | Maxdamantus: in redhat, the x.y.z tends to be fixed |
| 04:31.22 | timeless | and the patch version which is x.y.z-patch is what's updated |
| 04:31.29 | timeless | and it isn't really related to anything |
| 04:32.21 | Maxdamantus | Is x.y.z a version for a RH distribution, a RH package or a piece of software that is packaged by RH? |
| 04:32.36 | timeless | the latter |
| 04:32.48 | timeless | err, the last one |
| 04:36.27 | timeless | frowns |
| 04:47.57 | timeless | grr. one system had /proc/sys/net/ipv4/ip_forward enabled via /etc/sysctl.conf -- the other didn't |
| 05:51.11 | DocScrutinizer05 | doesn't get it how there's not a single script that would easily port a system to a new iron, or compare two systems (same distro/version, to start with) |
| 05:52.36 | DocScrutinizer05 | seems like the distro upgrade scripts should basically be capable to do the job, but they're not made for that |
| 05:53.43 | DocScrutinizer05 | plus fragmented across a million pre/postinstall scripts in packages |
| 05:58.59 | *** join/#maemo dafox (~dafox@92.69.236.143) |
| 06:24.54 | *** join/#maemo dmth|intevation (~dmth|inte@46.189.67.21) |
| 07:04.47 | *** join/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 07:15.34 | *** join/#maemo err0r3o3 (~err0r3o3@178-191-16-220.adsl.highway.telekom.at) |
| 07:29.18 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 07:48.21 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 07:58.20 | *** join/#maemo Maxdamantus (~Maxdamant@unaffiliated/maxdamantus) |
| 08:02.58 | Maxdamantus | Mm .. seems that the gas fitter damaged the lines to two of our phone jacks. |
| 08:03.25 | Maxdamantus | was going to say that he wasn't very familiar with RH when it cut out. |
| 08:08.14 | Wizzup | DocScrutinizer05: it can't cost me anything, but I will let him know |
| 08:08.30 | Wizzup | I got it 22 more times since my last msg |
| 08:10.30 | *** join/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 08:22.37 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-gtmpoekhgcvuubmz) |
| 08:22.37 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:26.47 | xes | DocScrutinizer05: what would do you suggest? an rsync to one new VM on .maemo.org? |
| 08:34.05 | *** part/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 08:36.16 | *** join/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 08:40.47 | *** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net) |
| 08:47.05 | *** join/#maemo merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 08:47.05 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 08:52.50 | rm_work | oh hey timeless ;) |
| 08:52.54 | rm_work | waves |
| 08:57.48 | *** join/#maemo Konsieur (~kabouik@129.242.224.21) |
| 09:49.45 | *** join/#maemo N-Mi (~nicolas@office.ibrowse.com) |
| 09:49.45 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 10:15.50 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 10:27.30 | *** join/#maemo TheKit (~nekit@85-95-189-40.saransk.ru) |
| 10:54.40 | *** join/#maemo qwazix (~qwazix@46-198-128-218.static.cyta.gr) |
| 10:54.40 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 11:07.28 | *** join/#maemo qwazix (~qwazix@46-198-128-218.static.cyta.gr) |
| 11:07.28 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 11:36.31 | *** join/#maemo xy2_ (~xy2_@93.245.16.93.rev.sfr.net) |
| 12:05.22 | *** join/#maemo hurrian (~textual@unaffiliated/rikanee) |
| 12:34.20 | DocScrutinizer05 | xes: I don't know if it needs an own VM or just an own vserver |
| 12:34.57 | DocScrutinizer05 | it does some heavy indexing every once in a while |
| 12:35.15 | DocScrutinizer05 | so maybe a container of sorts is in order |
| 12:55.30 | *** join/#maemo spiiroin (~spiiroin@87-93-92-210.bb.dnainternet.fi) |
| 12:59.26 | *** join/#maemo ravelo__ (ravelo@85.93.4.75) |
| 12:59.43 | timeless | hi rm_work |
| 13:00.14 | timeless | DocScrutinizer05: yeah... |
| 13:00.52 | timeless | ok, for my next trick, i need to convince mariadb (on devuan) to `start` |
| 13:00.57 | timeless | anyone know how to debug it? |
| 13:07.39 | timeless | grumble |
| 13:07.45 | timeless | `mysqld --verbose` works fine |
| 13:07.54 | timeless | wonders why `service start mysql` wouldn't work |
| 13:09.25 | inz | is there anything relephant in /var/log/daemon.log? |
| 13:10.08 | timeless | these files were presumably created by the `mysqld` that worked https://www.irccloud.com/pastebin/kaoWEsXQ/ |
| 13:10.23 | timeless | there's no sign of anything else |
| 13:11.22 | timeless | oh, interesting |
| 13:11.33 | *** join/#maemo jrayhawk (~jrayhawk@unaffiliated/jrayhawk) |
| 13:12.17 | timeless | when i try `service mysql status` and i'm using `mysqld --verbose` the latter says: https://www.irccloud.com/pastebin/A6EXMbAB/ |
| 13:12.26 | timeless | (the former for some reason says it twice...) |
| 13:14.54 | timeless | i don't think debian (devuan really) managed to properly set up the mariadb system https://www.irccloud.com/pastebin/2enwAdvx/ |
| 13:15.12 | timeless | (which is true, the postinstall script failed, and my attempts to coax it forward failed miserably) |
| 13:17.44 | timeless | Use of uninitialized value $action in string eq at /usr/share/debconf/frontend line 27. |
| 13:26.04 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 13:26.31 | timeless | oh. brother |
| 13:26.39 | timeless | mariadb requires systemd? |
| 13:29.28 | DocScrutinizer05 | DAMN! now Poettering answered (not even totally moot) https://github.com/systemd/systemd/issues/6309#issuecomment-314392132 and I can't reply, to point out that syntax check should be limited to the cases where the user= value is NOT in the password database already |
| 13:30.14 | DocScrutinizer05 | rationale: systemd MUST allow to use existing usernames no matter how garbled they look "syntactically" |
| 13:30.20 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 13:33.49 | DocScrutinizer05 | fix: swap sequence of chacks, first getpwnam() or whatever, only THEN and in case getpwnam threw error NONEXIST do syntax check |
| 13:36.05 | DocScrutinizer05 | or even defer syntax check to the moment when systemd actually creates a user. (and even then it's arguable if systemd should use existing policy definitions like in `man useradd|less -j6 +'/On Debian, the only constraints are.*$' ` instead of introducing/enforcing own ones |
| 13:37.56 | DocScrutinizer05 | a decent design would do execve("useradd"...) instead of doing own syntax check |
| 13:39.43 | DocScrutinizer05 | one of the few cases where execve($some-unixtool) is the only correct way to implement stuff, since the system's policy is defined in that tool and no other way to find out about the policy |
| 13:40.43 | DocScrutinizer05 | after all sysadmin might have replaced useradd by a proprietary version that implements however complex individual policy |
| 13:41.50 | DocScrutinizer05 | and systemd sysuser.d MY ASS!!! |
| 13:43.20 | DocScrutinizer05 | I already start puking when I read about DynamicUser=1 |
| 13:49.25 | *** part/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 14:07.49 | sicelo | my N900 still rebooting randomly :-( |
| 14:15.47 | DocScrutinizer05 | damn |
| 14:15.56 | sicelo | not a kernel oops, at least because sp-oops-extract only has older oopses |
| 14:16.47 | DocScrutinizer05 | reflash stock to rule out hw issues |
| 14:18.56 | DocScrutinizer05 | did you try my suggestion to run htop via WLAN ssh? |
| 14:20.26 | DocScrutinizer05 | and maybe even configure N900 rsyslog to log via WLAN as well |
| 14:21.02 | DocScrutinizer05 | alternatively run dmesg in a loop, every second |
| 14:21.41 | sicelo | it happens at realy odd moments, when not in use. unfortunately no access to wifi at all times |
| 14:22.02 | sicelo | i really doubt it's a case of something hogging cpu |
| 14:22.24 | DocScrutinizer05 | you won't find out with guessing |
| 14:23.36 | DocScrutinizer05 | your only chance is to get some useful diagnostic prints |
| 14:24.21 | DocScrutinizer05 | or strip down system to bare bones stock, then add functions until it sarts failing again |
| 14:24.23 | sicelo | yes, that what i'd like to ask .. what's a conclusive way to figure this out? |
| 14:24.49 | sixwheeledbeast^ | have you checked boot_reason? |
| 14:24.50 | DocScrutinizer05 | see above |
| 14:25.00 | DocScrutinizer05 | wd32 |
| 14:25.05 | DocScrutinizer05 | iirc |
| 14:25.07 | sixwheeledbeast^ | ah k |
| 14:25.38 | sicelo | yes still wd32_to |
| 14:25.54 | *** join/#maemo xy2_ (~xy2_@93.245.16.93.rev.sfr.net) |
| 14:26.01 | sixwheeledbeast^ | crawls back under the rock |
| 14:26.31 | sicelo | lifeguard restarts unchanged from saturday (had at least 4 restarts since) |
| 14:26.57 | sicelo | reflashing not an option for a while |
| 14:27.01 | KotCzarny | run rescueos and see if it reboots too? |
| 14:27.05 | KotCzarny | ;) |
| 14:27.06 | DocScrutinizer05 | no clear idea what *exactly* is wd32 watchdog, but I am pretty sure when it times out, something is blocking the kernel |
| 14:28.20 | DocScrutinizer05 | indeed when reflashing is no option and you can't do any decent persistent logging like suggested above, then rescueOS is a sane test |
| 14:29.12 | sicelo | it's not, because reboot doesn't happen in 'reasonable' time. so i'd not have a phone for long times |
| 14:29.21 | sicelo | will log to a file |
| 14:30.01 | KotCzarny | also, check swapfile for badblocks if you use it |
| 14:30.05 | DocScrutinizer05 | the problem with logging is: when kernel gets blocked/frozen by whatever task then any logging on system is highly prone to not getting flushed to storage, so you NEED off system logging, via WLAN, or via USB or console |
| 14:30.28 | sicelo | :-) |
| 14:30.40 | sicelo | looks i have to live with the reboots then |
| 14:31.16 | KotCzarny | nah, if it's dying hw it will get worse :/ |
| 14:31.34 | DocScrutinizer05 | you may try to reduce commit time to maybe 1 second (is 30s now iirc) |
| 14:32.29 | DocScrutinizer05 | redoing swap is a very good suggestion |
| 14:32.56 | DocScrutinizer05 | or... :-D swap swap to uSD :-D |
| 14:33.41 | DocScrutinizer05 | any defects or oddities in swap may cause unsolicited reboots easily |
| 14:34.19 | DocScrutinizer05 | since kernel actually freezes as long as kswapd is busy |
| 14:34.41 | sixwheeledbeast^ | I had wd32 with stupid things like tracker taking an age to index stuff. |
| 14:34.54 | DocScrutinizer05 | yes, same here |
| 14:35.14 | DocScrutinizer05 | at least I guess it was wd32 |
| 14:35.38 | sicelo | uGod forbid that it should be dying hardware ... i don't have replacment |
| 14:35.43 | DocScrutinizer05 | or browser opening a terrible website that ate all memory incl swap |
| 14:36.00 | DocScrutinizer05 | device getting unresponsive for an hour or two, then finally rebooting |
| 14:36.38 | KotCzarny | sicelo: check both emmc and usd for badblocks, readonly test should be enough for now |
| 14:36.38 | DocScrutinizer05 | apropos... what's with vote? |
| 14:37.21 | DocScrutinizer05 | could somebody with credentials finally hit the "calculate and publish" button on https://maemo.org/vote/results.php?election_id=48 |
| 14:37.26 | DocScrutinizer05 | PLEASE! |
| 14:37.35 | sixwheeledbeast^ | :nod: Modrana downloading tiles or running a tracklog on default settings a few other weird wd32's. |
| 14:38.16 | DocScrutinizer05 | where's juiceme? |
| 14:39.02 | DocScrutinizer05 | xes_: warfare: could you maybe log in to the election machine and hit the final button to calculate and publish stuff? |
| 14:40.01 | DocScrutinizer05 | I know there's such button and it works/worked, since I've hit it at least 3 times |
| 14:41.18 | *** join/#maemo xy2_ (~xy2_@93.245.16.93.rev.sfr.net) |
| 14:42.23 | DocScrutinizer05 | can't be true maemo takes longer to evaluate/count an election than the USA ;-P |
| 14:43.16 | DocScrutinizer05 | particularly since it's literally just a button to press |
| 14:44.44 | DocScrutinizer05 | http://maemo.org/vote/admin.php |
| 14:46.21 | DocScrutinizer05 | warfare: I don't know who except juiceme has valid credentials, mine are gone |
| 14:46.42 | warfare | DocScrutinizer05: I don't. |
| 14:47.06 | DocScrutinizer05 | create a set for you in mysql? |
| 14:47.50 | sixwheeledbeast^ | Well CC meeting tonight anyway |
| 14:48.44 | DocScrutinizer05 | do we need a meeting of old vanishing CC to decide to press a button to evaluate and then publish election results? |
| 14:49.49 | DocScrutinizer05 | back when we pondered to make that automatically when election period expires. We decided against it to have a checkpoint where manual interference is possible when something went haywire |
| 14:50.34 | DocScrutinizer05 | didn't think the thing to go haywire is that checkpoint itself and the human interaction needed to continue the automated process |
| 14:55.05 | DocScrutinizer05 | warfare: you should have credentials anyway, to recover the whole system when all credentials but yours are lost |
| 14:55.20 | DocScrutinizer05 | the whole voting system |
| 14:55.42 | sicelo | installed crash-reporter. hope it will help narrow down the issue |
| 14:55.48 | sicelo | bug 6334 |
| 14:55.50 | povbot | 04Bug https://bugs.maemo.org/6334 random but frequent HW watchdog reboots (/proc/bootreason contains "32wd_to") when returning from off_mode |
| 14:56.08 | DocScrutinizer05 | hmm, sounds to the point, yes |
| 14:57.41 | DocScrutinizer05 | WTF?!?? bazillion comments |
| 14:59.05 | sicelo | unfortuantely |
| 15:02.08 | DocScrutinizer05 | >> Ext3 is journaled, but it's not as robust as UBIFS. If you have really bad luck and/or huge number of unclean reboots (32wd_to reboot or sw_rst caused by oops; sw_rst from SW watchdog are fine, file systems are then synched) and/or remove the battery while there's uncommited data (commit interval = 1s), it may get corrupted.<< https://bugs.maemo.org/show_bug.cgi?id=6334#c415 |
| 15:02.10 | povbot | 04Bug 6334: random but frequent HW watchdog reboots (/proc/bootreason contains "32wd_to") when returning from off_mode |
| 15:03.16 | DocScrutinizer05 | it's controversial if journaling makes *any* sense on flash storage |
| 15:05.21 | DocScrutinizer05 | sicelo: try swapping your swap, to start with! |
| 15:07.04 | *** join/#maemo ff_ (~ff_@aafi131.neoplus.adsl.tpnet.pl) |
| 15:07.38 | ff_ | sicelo: I've had the same randomly reboot issue every one, two days. This was changed: in KP53, governor to conservative, SmartReflex off vdd1=0 vdd2=0, +5 to all voltage vals, 360MHz for DSP. |
| 15:08.50 | DocScrutinizer05 | >> They were the same - after connecting charger and turning on the device startup took slightly longer than usually and animation (Nokia logo, sound, connecting hands) was not displayed. Then crash reporter started telling that it has report about 32wd_to reboot. Situation does not occur when I turn off the phone using power button, nor after reboot.<< sounds like fsck acting up, not unheard of |
| 15:09.04 | ff_ | Now it's 38days uptime and everythink is hunky-dory. Maybe in future I'll check greater DSP freq but for now it's work. |
| 15:09.10 | DocScrutinizer05 | smartreflex is known to be unstable |
| 15:09.44 | DocScrutinizer05 | that's why it's disabled in stock, until somebody proves otherwise for the reason |
| 15:11.31 | DocScrutinizer05 | Nokia didn't throttle the N900 on purpose, just to make it slower than it could be. All tuning at clocks and smartreflex is considered to have negative impact on system stability |
| 15:12.35 | DocScrutinizer05 | possibly *reducing* clock below stock settings can help on devices that suffer wear out |
| 15:13.18 | DocScrutinizer05 | so much for the often claimed "not a single device ever suffered harm from overclocking so far" |
| 15:14.04 | DocScrutinizer05 | those who claim that simply never would accept overclocking as a reason for hardware wear and resulting system instability |
| 15:14.34 | ff_ | dealing with performace needs some adjust |
| 15:14.45 | DocScrutinizer05 | though I seem to recall sicelo never OCed |
| 15:15.26 | sicelo | how can i check status on mine? never needed a fast n900 and therefore never looked at those things |
| 15:16.07 | DocScrutinizer05 | hmm, to start with, look a zzztop for the frequencies used. and then there's that KP-tuning tool |
| 15:16.46 | DocScrutinizer05 | though when you never touched that stuff, you should not have any OC |
| 15:16.53 | sicelo | err, isn't it accessible in /sys or something? |
| 15:17.23 | DocScrutinizer05 | it is, but I wouldn't know the /sys or /proc files off top of my head |
| 15:17.39 | sicelo | ok |
| 15:18.04 | ff_ | give here output of kernel-config show |
| 15:19.41 | DocScrutinizer05 | sicelo: install reswap or similar tool and transfer your swap to uSD |
| 15:20.19 | DocScrutinizer05 | or would you like to do it manually? |
| 15:20.23 | ff_ | should be sth like http://paste.debian.net/plain/975920 |
| 15:21.13 | DocScrutinizer05 | min frequency 600? really now? |
| 15:22.07 | DocScrutinizer05 | aside form my system not even having kernel-config command, I doubt this is a recommended setting I see there |
| 15:23.25 | ff_ | I don't know but it's work flawlessly for 38days and it has nice performace |
| 15:23.36 | DocScrutinizer05 | ~oc |
| 15:23.37 | infobot | i heard oc is an Optical Carrier, An OC1 has 672 channels or 44.736 Mbit/s |
| 15:23.46 | DocScrutinizer05 | ~maemo-oc |
| 15:23.53 | DocScrutinizer05 | whatever |
| 15:25.05 | ff_ | what is optical carrier in maemo? |
| 15:25.34 | DocScrutinizer05 | ~overclocking |
| 15:25.34 | infobot | "OK, listen up. This is your CPU." apt drops the CPU into a hot frying pan. "This is your CPU on overclocking. Any questions?" |
| 15:26.08 | sicelo | yes i can do it manually (relocating swap) |
| 15:26.34 | sicelo | anyway for now will see what crash reporter catches first |
| 15:27.12 | DocScrutinizer05 | won't catch anything I'm pretty sure |
| 15:27.14 | ff_ | ah, ok |
| 15:30.09 | ff_ | I'm watching out to not beyond over 40C |
| 15:30.48 | DocScrutinizer05 | pointless |
| 15:31.07 | ff_ | but that temp is from battery sensor I think, not CPU? |
| 15:33.31 | DocScrutinizer05 | aaah |
| 15:33.43 | DocScrutinizer05 | ~omap-oc |
| 15:33.43 | infobot | omap-oc is probably http://mg.pov.lt/maemo-irclog/%23maemo.2010-08-01.log.html#t2010-08-01T22:16:05 read that!, or and this http://mg.pov.lt/maemo-irclog/%23maemo.2011-03-11.log.html#t2011-03-11T03:04:11, or http://electronics.stackexchange.com/a/156130 |
| 15:34.40 | DocScrutinizer05 | damn, poor bot suffering DDoS |
| 15:34.40 | *** join/#maemo Konsieur (~kabouik@129.242.224.21) |
| 15:38.47 | DocScrutinizer05 | ff_: how could we know which temperature you're looking at. There's three tenps: battery charging chip die temperature and NTC sensor battery temperature, and CPU die temperature though CPU may have hotspots that are not detectable from the generic die temperature sensor |
| 15:40.04 | ff_ | temp from bq27200.sh |
| 15:40.08 | DocScrutinizer05 | that's basically useless, die temp of bq27200 charging chip |
| 15:40.39 | DocScrutinizer05 | not that any other temperature was really more useful regarding OC |
| 15:41.02 | DocScrutinizer05 | see third link the bot provided above |
| 15:41.55 | ff_ | ok |
| 15:43.02 | bencoh | shit, this kernel doesn't have /sys/class/thermal |
| 15:43.04 | bencoh | *meh* |
| 15:43.19 | DocScrutinizer05 | forget it sicelo |
| 15:44.15 | DocScrutinizer05 | oh bencoh, sorry |
| 15:44.15 | timeless | DocScrutinizer05: so... i'm back to my main problem: i have a `pydio` in a `devuan`. |
| 15:44.15 | timeless | i have mariadb installed (in case there's a use for it) |
| 15:44.23 | timeless | pydio in theory is configured to use sqlite3, and there is a database file |
| 15:44.34 | ff_ | previously reboots occurs even all phone was cold 27degC |
| 15:44.36 | sicelo | see you all later |
| 15:45.09 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:48.18 | DocScrutinizer05 | bencoh: what for would you need thermal? |
| 15:49.04 | DocScrutinizer05 | btw the OMAP die temp sensor is broken, SiErr :-/ |
| 15:49.14 | DocScrutinizer05 | sporadic |
| 15:50.25 | DocScrutinizer05 | eventually it freezes the value |
| 15:50.58 | DocScrutinizer05 | iirc |
| 15:51.14 | DocScrutinizer05 | recover via power cycle |
| 16:10.40 | ff_ | this /sys/devices/platform/omap34xx_temp/temp1_input & /sys/devices/platform/omap34xx_temp/temp1_input_raw ? |
| 16:11.27 | DocScrutinizer05 | yes, prolly |
| 16:20.29 | ff_ | strange, first N900 shows temp1_input -40 & raw 0 and sec 30 & 53 |
| 16:21.19 | *** join/#maemo dafox (~dafox@92.69.238.213) |
| 16:26.13 | ff_ | and as you said, frozen |
| 16:45.13 | *** join/#maemo infobot (~infobot@rikers.org) |
| 16:45.13 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | DONT FORGET TO VOTE FOR COUNCIL! https://maemo.org/vote/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog |
| 16:53.48 | *** join/#maemo xy2_ (~xy2_@93.245.16.93.rev.sfr.net) |
| 16:56.24 | *** join/#maemo florian (~fuchs@x4d094ad3.dyn.telefonica.de) |
| 16:56.24 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 17:15.06 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 17:36.05 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 17:48.26 | *** join/#maemo enyc (~enyc@muddle.enyc.org.uk) |
| 17:49.39 | *** join/#maemo louisdk (~louisdk@static-5-103-138-205.fibianet.dk) |
| 18:02.07 | *** join/#maemo L29Ah (~L29Ah@31.173.81.18) |
| 18:12.28 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 18:23.37 | Vajb | how long it should take for "flash it all" script to do it's magic? |
| 18:25.05 | Vajb | it's been like 15minutes in state "kernel:[1311239.551502] Disabling IRQ #18 |
| 18:25.48 | Vajb | device itself shows just a steady yellow light |
| 18:32.59 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 18:33.20 | freemangordon | TheKit: yes, there are semi-REed Nokia PA modules: https://notabug.org/freemangordon/pulseaudio-nokia/src/fremantle |
| 18:33.46 | freemangordon | TheKit: actually, everything but voice module is REed |
| 18:34.18 | TheKit | would they be needed on different device? |
| 18:34.44 | freemangordon | most probably, for VOIP |
| 18:35.00 | freemangordon | though... |
| 18:35.02 | *** join/#maemo florian (~fuchs@x4d094ad3.dyn.telefonica.de) |
| 18:35.31 | freemangordon | maybe not as most if not all voip clients supports their own agc, aec, etc |
| 18:35.42 | *** join/#maemo err0r3o3 (~err0r3o3@178-191-16-220.adsl.highway.telekom.at) |
| 18:36.09 | freemangordon | but, it still will be perfect if we have Nokia audio processing algos on our side :) |
| 18:41.53 | DocScrutinizer05 | OT (mlockall() for noswap) http://paste.ubuntu.com/25069876 |
| 18:43.25 | DocScrutinizer05 | Vajb: flash-it-all.sh takes less than 2 minutes. Never seen anything like >>kernel:[1311239.551502] Disabling IRQ #18<< |
| 18:44.05 | DocScrutinizer05 | ((less than 2 minutes unless you need to download stuff via an ultraslow internet link) |
| 18:44.12 | TheKit | is dialer provided by rtcom-call-ui? |
| 18:45.29 | DocScrutinizer05 | freemangordon: ((maybe not)) that's why I suggested replacing that stuff by a feed-trhough dummy |
| 18:46.51 | DocScrutinizer05 | limiting the impact to reduced audio quality, worst case |
| 18:53.44 | *** join/#maemo Vajb (~Vajb@85-76-41-197-nat.elisa-mobile.fi) |
| 19:03.09 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 19:14.13 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 19:15.58 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 19:19.43 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 19:22.50 | *** join/#maemo spiiroin (~spiiroin@87-93-120-189.bb.dnainternet.fi) |
| 19:34.26 | freemangordon | ok, finally I hit libhildon-plugins-notify-sv :(. Going to RE it |
| 20:15.19 | *** join/#maemo Guest8809 (~juice@Maemo/community/council/juiceme) |
| 20:22.54 | *** join/#maemo louisdk (~louisdk@static-5-103-138-205.fibianet.dk) |
| 20:30.47 | *** join/#maemo louisdk (~louisdk@static-5-103-138-205.fibianet.dk) |
| 20:32.14 | DocScrutinizer05 | that bugger |
| 20:32.31 | DocScrutinizer05 | about time it gets REed |
| 20:34.20 | freemangordon | yeah. will take time though, it is not small one (60k binary) |
| 20:36.20 | *** join/#maemo MikaT (~mtapoja@projects.sse.fi) |
| 20:58.31 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 21:15.52 | DocScrutinizer05 | pretty sure. Does a couple of things |
| 21:16.54 | DocScrutinizer05 | prolly from yellow ribbons to requesters to LED patterns (via dbus to mce) to audio jungles, right? |
| 21:17.17 | *** join/#maemo louisdk (~louisdk@static-5-103-138-205.fibianet.dk) |
| 21:18.29 | DocScrutinizer05 | jingles even |
| 21:19.01 | DocScrutinizer05 | I might be wrong though |
| 22:47.11 | *** join/#maemo infobot (~infobot@rikers.org) |
| 22:47.11 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | DONT FORGET TO VOTE FOR COUNCIL! https://maemo.org/vote/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf ~tabletsdev ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog |
| 22:51.54 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |