| 00:36.33 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@14.151.30.77) |
| 02:50.47 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 03:46.08 | *** join/#maemo-ssu lartza_ (~lartza@IP-62-216-127-116.telemail.fi) |
| 03:47.29 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 04:51.49 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 04:52.32 | *** join/#maemo-ssu M13 (~Miranda@83.149.38.193) |
| 05:09.18 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 05:19.33 | *** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:185a:93da:b21b:928) |
| 05:24.18 | *** join/#maemo-ssu b-r-a-i-n (~admin@188.168.202.135) |
| 06:15.14 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 06:18.12 | *** join/#maemo-ssu futpib (~futpib@89.106.197.36) |
| 07:20.07 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-235.residential.rdsnet.ro) |
| 07:36.06 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 08:02.33 | *** join/#maemo-ssu hardo (~sacko@p549AC83E.dip0.t-ipconnect.de) |
| 08:02.44 | hardo | hi |
| 08:02.50 | hardo | somebody here |
| 08:04.21 | freemangordon | ~ask |
| 08:04.21 | infobot | Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. |
| 08:07.25 | *** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:185a:93da:b21b:928) |
| 08:13.37 | hardo | are the problems with cssu testing fixed ? |
| 08:14.17 | hardo | because yesterday I tried to install cssu testing and it didn't work |
| 08:14.31 | freemangordon | hardo: refresh in HAM |
| 08:15.24 | hardo | thanks |
| 08:40.35 | hardo | hey I got problems with the cssu |
| 08:40.37 | hardo | testing |
| 08:41.03 | hardo | after installing the update I won't turn on |
| 09:06.00 | *** join/#maemo-ssu retard (~tom@zak.radionova.no) |
| 09:06.27 | Drathir | freemangordon: loop sloved? |
| 09:06.30 | Drathir | mornin |
| 09:07.00 | hardo | some people report positive |
| 09:07.05 | hardo | I have problems |
| 09:12.37 | Drathir | DocScrutinizer05: maybe is possibility include something that in php ? |
| 09:13.27 | *** join/#maemo-ssu piscodig (~discopig@2001:5c0:1400:a::49) |
| 09:13.27 | *** join/#maemo-ssu piscodig (~discopig@unaffiliated/discopig) |
| 09:46.17 | *** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm) |
| 09:55.40 | *** join/#maemo-ssu jon_y (~enforcer@2002:af91:e842::af91:e842) |
| 10:03.12 | *** join/#maemo-ssu jon_y (~enforcer@2002:af91:e842::af91:e842) |
| 10:08.56 | freemangordon | Drathir: it should be |
| 10:10.26 | hardo | yes everthing is fine |
| 10:10.39 | hardo | i solved the problem ^ |
| 10:10.58 | hardo | but i have the next problem |
| 10:11.09 | hardo | i want to update the kernel power |
| 10:11.15 | hardo | to 52 |
| 10:11.44 | hardo | does that mean I have to activate the cssu (devel) repositorie) |
| 10:22.08 | Drathir | hardo: how sloved? |
| 10:22.38 | Drathir | botsnack |
| 10:22.43 | hardo | @drathir |
| 10:22.53 | hardo | I flashed my n900 |
| 10:23.04 | hardo | then take out the sd card |
| 10:23.13 | Drathir | oh i seee |
| 10:23.25 | hardo | and go an webpage and install cssu testing from there |
| 10:24.12 | Drathir | any errors show when try to update KP 52? |
| 10:24.30 | hardo | i don t know how to update |
| 10:24.36 | hardo | i found in ham |
| 10:24.51 | hardo | linux kernel for cssu |
| 10:24.55 | hardo | and |
| 10:25.05 | hardo | linux kernel for power user |
| 10:25.17 | hardo | i don t know which one i need |
| 10:26.22 | hardo | i even don t know if i have to activate the repositories from community (devel) |
| 10:26.47 | Drathir | i have "harder" config because i have also u-boot on board... |
| 10:27.33 | hardo | i see... |
| 10:27.37 | Drathir | menu settings about cssu |
| 10:27.54 | hardo | what is there ? |
| 10:28.25 | Drathir | what flavor you have there? |
| 10:28.43 | hardo | 21.2011.38-1Tmaemo8.1 |
| 10:28.52 | hardo | testing |
| 10:28.58 | Drathir | there only information about cssu installed |
| 10:29.32 | hardo | my cssu went fine |
| 10:29.33 | Drathir | Version: 21.2011.38-1Tmaemo7.2 |
| 10:29.48 | Drathir | looks like updated sucessfull |
| 10:29.53 | hardo | yes |
| 10:30.39 | hardo | uname -r shows |
| 10:30.52 | hardo | 2.6.28-omap1 |
| 10:31.04 | hardo | that means the kernel is not up to date |
| 10:31.21 | hardo | i got to find a way to update the kernel to 52 |
| 10:31.39 | Drathir | Linux Nokia-N900 2.6.28.10-power52 #1 PREEMPT Sat Apr 6 11:59:23 UTC 2013 armv7l GNU/Linux |
| 10:32.24 | hardo | so |
| 10:32.33 | Drathir | idk if this is possible without u-boot... |
| 10:32.38 | hardo | linux kernel for power user should be right ? |
| 10:32.47 | hardo | in ham |
| 10:33.35 | Drathir | DocScrutinizer05 maybe can help more hardo... |
| 10:35.24 | Drathir | i dont really want to say you something cause boot loop and reflash again a phone... |
| 10:40.23 | Drathir | but looks like dependencies works http://pastebin.com/Z5maHz9t |
| 10:43.27 | *** join/#maemo-ssu kolp (~quassel@212.255.229.223) |
| 11:20.07 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-235.residential.rdsnet.ro) |
| 12:09.08 | merlin1991 | hardo: when you don't have u-boot then you should enable extras-deve and install kernel-power-flasher |
| 12:26.15 | peetah | merlin1991: are there more users experiencing bootloop even with T8.1 or am I still the only one ? |
| 12:27.27 | merlin1991 | so far only hardo had it but for him it went fine when he reflashed and then installed T8.1 |
| 12:29.29 | hardo | peetah my fault was that I forgot about the sd card |
| 12:31.08 | merlin1991 | hardo: well you can put it in now, it shouldn't affect it anymore |
| 12:31.58 | peetah | ok so odds are high that my problem could come from whatever change I could have made in critical files in the past... now which one , I don't know and I really don't want to reflash, so I'll have to postpone this upgrade and dig a little more in my /etc |
| 12:32.08 | peetah | hardo: what about the sd card ? |
| 12:32.35 | hardo | nothing special |
| 12:32.42 | hardo | today i flashed my n900 |
| 12:33.05 | hardo | and after installing cssu my n900 didn't reboot |
| 12:33.22 | hardo | i think for obvios reseon ^ |
| 12:33.34 | hardo | reason |
| 13:06.14 | Drathir | hmm now /me thinkink about apply of cssu update ^^ |
| 13:10.22 | DocScrutinizer05 | peetah: check rcs-late, preinit, etc |
| 13:10.41 | DocScrutinizer05 | peetah: particularly those that might have changed in T8 |
| 13:12.19 | DocScrutinizer05 | alas it seems CSSU doesn't (try to) apply patches to those files, but rather ruthlessly replaces them no matter if they are original or customized |
| 13:13.06 | *** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be) |
| 13:18.22 | peetah | after upgrade, and bootloop, I have a new /var/log/fsck_home.log that says fsck has been cancelled: is this normal ? |
| 13:24.42 | DocScrutinizer05 | well, the T8 fstab hack also touched the already botched fsck mechanism |
| 13:24.47 | DocScrutinizer05 | aiui |
| 13:24.51 | peetah | dmesg does not give any useful info |
| 13:25.28 | peetah | I installed sysklogd before upgrading, but it doesn't seems to fill in the /var/log/syslog during the bootloop |
| 13:25.50 | DocScrutinizer05 | and caused fsck to check the wrong MMC since the name of eMMC changes depending on whether or not a uSD been inserted during boot |
| 13:26.13 | peetah | any other place where I could gather information about the boot process ? |
| 13:26.39 | DocScrutinizer05 | debugging boot process is really hard |
| 13:27.04 | peetah | but checking the wrong MMC should simply send a warning, not preventing boot no ? |
| 13:28.38 | DocScrutinizer05 | I think the schema been: do fsck to /home, if it succeeds continue booting; if it had to fix errors try to reboot after fsck exited, to make home remount cleanly |
| 13:28.48 | DocScrutinizer05 | or sth along that line |
| 13:30.27 | DocScrutinizer05 | merlin1991 claimed he kicked out resp disabled fsck completely as a stopgap measure in T8.1 |
| 13:31.25 | DocScrutinizer05 | it's quite unfortunate that this whole fstab patch made it into CSSU at all, without proper testing and perr review |
| 13:31.31 | DocScrutinizer05 | peer even |
| 13:40.06 | merlin1991 | peetah: check /etc/default/mount-opts |
| 13:40.42 | merlin1991 | and make sure the various _fsck options have a "0" settings |
| 13:45.14 | peetah | merlin1991: no _fsck options in mount-opts, only home_opts and fat_opts |
| 13:45.53 | merlin1991 | then check if you have any /etc/default/mount-opts.* file |
| 13:46.13 | peetah | yep dpkg-dist |
| 13:46.42 | merlin1991 | cp yours into a backup mv that into place and merge changes |
| 13:46.51 | peetah | wow much more options there :) |
| 13:46.54 | merlin1991 | also bitchslap ham for not overwriting it and thus ruining your day |
| 13:49.27 | peetah | what about my own options which do not seem to appear in .dpkg-dist file ? do I copy them there or are they now not used by any scripts ? |
| 13:49.45 | merlin1991 | what are your own options? |
| 13:50.30 | peetah | home_opts="rw,noatime,errors=continue,commit=1,data=writeback" |
| 13:51.20 | DocScrutinizer05 | [2013-06-10 15:46:41] <merlin1991> [...] merge changes |
| 13:51.25 | peetah | fat_opts="noauto, nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir" |
| 13:52.33 | peetah | ok it seems that they are overwritten by rcS-late |
| 13:52.37 | DocScrutinizer05 | bitchslap CSSU for overwriting config files instead of applying diff patches |
| 13:52.52 | merlin1991 | eval home_opts=$common_opts,$root_opts,\$${home_type}_opts |
| 13:52.57 | peetah | at least for home_opts |
| 13:53.02 | peetah | merlin1991: exactly |
| 13:53.10 | peetah | but fat_opts is not used anywhere |
| 13:53.19 | peetah | at least in event.d directory |
| 13:53.23 | merlin1991 | I think it's vfat_opts now |
| 13:53.44 | merlin1991 | hm not used either |
| 13:54.13 | peetah | so so I have to put them in mount-opts-overwrite |
| 13:54.14 | peetah | ? |
| 13:54.17 | *** join/#maemo-ssu hardo (~sacko@p549AC83E.dip0.t-ipconnect.de) |
| 13:54.40 | peetah | or just ignore them, they do not seem to be very exotic |
| 13:54.42 | merlin1991 | there is $mydocs_opts now though |
| 13:55.11 | merlin1991 | and yes using mount-opts-overwrite is probably a better choice |
| 13:55.57 | DocScrutinizer05 | md5sum original "obsolete" files, compare md5sums to the master list that comes with "the update", warn if any of the original files been changed wrt what patch developer expected to see, the apply / not apply diff-patches to user's system |
| 13:56.41 | DocScrutinizer05 | it's pretty silly to simply overwrite any existing files |
| 13:57.05 | merlin1991 | well it doesn#t overwrite them at all |
| 13:57.16 | merlin1991 | it places a new file $file.dpkg-dist |
| 13:57.17 | DocScrutinizer05 | that's almost as silly |
| 13:57.35 | DocScrutinizer05 | at least without a FAT WARNING |
| 13:58.03 | DocScrutinizer05 | idealy a diff-patch should get applied |
| 13:58.15 | DocScrutinizer05 | which would do the merges you suggested above |
| 13:58.30 | DocScrutinizer05 | user still should check if the merge went ok |
| 13:59.02 | DocScrutinizer05 | when the original file been different to what devel expected his patch gets applied to |
| 13:59.27 | DocScrutinizer05 | also a backup of original file must get kept |
| 14:00.03 | peetah | still looping |
| 14:00.49 | merlin1991 | hm check if you have any other .dpkg-dist files on the system |
| 14:01.19 | peetah | already did, but nothing except for openvpn which should not influence the boot process |
| 14:01.58 | DocScrutinizer05 | maybe disabling watchdogs could help? |
| 14:02.15 | merlin1991 | then there's nothing left but to add various echo "got past section x" >> /var/log/rcs.log lines into /etc/event.d/rcS-late and see where it stops |
| 14:03.04 | peetah | that's what I start to do |
| 14:03.55 | DocScrutinizer05 | tbh those diagnostic prints should be in every boot related script. Maybe even set -vx |
| 14:05.26 | DocScrutinizer05 | exec >>/var/log/rcs.log |
| 14:05.44 | DocScrutinizer05 | err |
| 14:05.52 | DocScrutinizer05 | exec 2>>/var/log/rcs.log ? |
| 14:09.58 | DocScrutinizer05 | the orthodox boot debug procedure is to attach a serial console, btw |
| 14:10.29 | DocScrutinizer05 | that's what the UART-3(?) testpoints under battery are for |
| 14:11.05 | merlin1991 | I bet the kernel config doesn't have the serial console bootline on the shipped devices |
| 14:11.25 | DocScrutinizer05 | on Freerunner, you got a debug board for that |
| 14:11.55 | DocScrutinizer05 | flasher allows defining new boot kernel cmdline |
| 14:12.05 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 14:12.09 | DocScrutinizer05 | so does uBoot |
| 14:12.30 | DocScrutinizer05 | and setting boot options via flasher enables serial console too |
| 14:13.41 | DocScrutinizer05 | http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Development_Environment/Maemo_Flasher-3.5 |
| 14:14.57 | DocScrutinizer05 | --set-rd-flags=serial-console |
| 14:15.11 | DocScrutinizer05 | obvious, uh? |
| 14:15.53 | DocScrutinizer05 | nfc zhough what's sti-console |
| 14:32.03 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 14:43.28 | peetah | ok, so it seems line "initctl emit MOUNTS_OK" of rcS-late is not in love with my n900... does it ring a bell ? |
| 14:45.50 | peetah | clock_daemon, hildon-control-panel-personalisation, rc-clean-fail-thumbnail ans xsession start on MOUNTS_OK |
| 14:46.35 | peetah | which disable order would make more sense ? |
| 15:02.09 | DocScrutinizer05 | diable order? |
| 15:02.41 | DocScrutinizer05 | also, what means "is not in love with my n900" |
| 15:03.02 | peetah | it does not do anything past this line |
| 15:03.48 | DocScrutinizer05 | does it execute that line? does it return from that line? |
| 15:04.38 | Drathir | i good understand that is possible install KP without u-boot? |
| 15:04.50 | DocScrutinizer05 | sure |
| 15:05.11 | Drathir | in that case oryginal is only exchanged with KP one? |
| 15:05.16 | DocScrutinizer05 | that's the usual way to do it |
| 15:05.22 | peetah | it does not print anything after that line |
| 15:05.22 | DocScrutinizer05 | yes |
| 15:06.37 | Drathir | ok thanks now i'll be know that if someone ask about that... |
| 15:06.52 | DocScrutinizer05 | peetah: initctl emit MOUNTS_OK sends a signal to initctl/upstart, which in turn makes upstart start all scripts that are defined as waiting for that signal. any of the jobs/services started could cause reboot |
| 15:07.32 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 15:08.16 | DocScrutinizer05 | peetah: check /etc/events.d for files with "start (on|after) MOUNTS_OK" |
| 15:08.53 | peetah | that's why I asked which disable order of the started services cited above would make more sense in order to point the culprit |
| 15:10.15 | DocScrutinizer05 | cd /etc/event.d/; grep MOUNTS_OK * |
| 15:10.50 | DocScrutinizer05 | you won't gain anything by disabling those services |
| 15:11.04 | DocScrutinizer05 | you need to check which one fails on getting started |
| 15:12.25 | DocScrutinizer05 | a cascaded "sleep N" at beginning in any of the services, plus a few echo lines (or logger lines) should help to serialize the jobs and see which one gets started but never finishes |
| 15:12.52 | Drathir | but anyway i little scary to helping ppl with kernel questions is too important and critical thing in the system... and too responsible to my knowledge... |
| 15:13.12 | DocScrutinizer05 | I also found >> hildon-control-panel-personalisation.dpkg-new:start on MOUNTS_OK<< |
| 15:13.33 | DocScrutinizer05 | but that's on *my* (obsolete) system, not related to T8 |
| 15:19.38 | DocScrutinizer05 | peetah: I'd figure e.g. xsession or hildon-control-panel-personalisation or rc-clean-fail-thumbnail might have startjobs that use dsmetool to monitor the process and when the service fails and segfaults for some reason (not unseen for e.g. H-D-widgets when config got messed up) the dsme reboots system after 3 failed respawns in 60s |
| 15:21.47 | peetah | DocScrutinizer05: pfiouuuuu spent too much time on it already ...restoring backup and will look at this sometimes later in the week. thanks for all advices and help ! |
| 15:22.07 | DocScrutinizer05 | yw |
| 15:27.35 | *** join/#maemo-ssu arcean (~arcean@apn-77-114-14-171.dynamic.gprs.plus.pl) |
| 15:32.18 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 15:40.22 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28C9A.dip0.t-ipconnect.de) |
| 15:49.11 | DocScrutinizer05 | Pali: freemangordon: Jun 10 17:47:14 IroN900 kernel: [85239.571258] OMAP3 ROM RNG: HW init failed: 1 |
| 15:49.28 | DocScrutinizer05 | on cat /dev/hwrng |
| 15:49.34 | DocScrutinizer05 | :-S |
| 15:49.56 | Pali | bad |
| 15:50.34 | DocScrutinizer05 | is hwrng a feature of PK? |
| 15:50.38 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 16:10.10 | Drathir | i have the same [26386.323333] OMAP3 ROM RNG: HW init failed: 1 |
| 16:11.03 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 16:14.44 | *** join/#maemo-ssu xmlich02 (~imlich@2001:67c:1220:80c:21c:c0ff:fe18:9398) |
| 16:40.06 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 16:45.03 | DocScrutinizer05 | I consider this a possible security threat |
| 16:45.55 | freemangordon | DocScrutinizer05: which kernel? |
| 16:46.13 | DocScrutinizer05 | IroN900:~# uname -a |
| 16:46.14 | DocScrutinizer05 | Linux IroN900 2.6.28-omap1 #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 armv7l GNU/Linux |
| 16:47.36 | DocScrutinizer05 | grep PRNG -A6 /etc/event.d/rcS-late |
| 16:49.06 | freemangordon | no such error here |
| 16:49.16 | freemangordon | oh, wait |
| 16:49.30 | DocScrutinizer05 | cat /dev/hwrng |
| 16:49.32 | freemangordon | DocScrutinizer05: do I need to cat /dev/? |
| 16:49.33 | freemangordon | ok |
| 16:49.52 | freemangordon | [17999.453399] OMAP3 ROM RNG: HW init failed: 1 |
| 16:49.57 | freemangordon | hmm, wtf? |
| 16:50.04 | DocScrutinizer05 | and worse: no output of cat /dev/hwrng |
| 16:50.20 | freemangordon | cat: read error: Input/output error |
| 16:50.39 | DocScrutinizer05 | that stderr |
| 16:50.45 | DocScrutinizer05 | ;-P |
| 16:51.05 | freemangordon | DocScrutinizer05: though cat /dev/random works |
| 16:51.23 | DocScrutinizer05 | that doesn't matter |
| 16:51.27 | DocScrutinizer05 | <PROTECTED> |
| 16:51.28 | DocScrutinizer05 | <PROTECTED> |
| 16:51.30 | freemangordon | not sure if cat /dev/hwrng is the correct thing to be done |
| 16:51.35 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 16:52.02 | DocScrutinizer05 | grep PRNG -A6 /etc/event.d/rcS-late |
| 16:52.10 | freemangordon | yep, saw it |
| 16:52.24 | DocScrutinizer05 | wonders if that's genuine |
| 16:52.29 | DocScrutinizer05 | or CSSU |
| 16:52.44 | freemangordon | checks on gitorious |
| 16:53.01 | DocScrutinizer05 | anyway it seeds entropy with ever-same null stuff |
| 16:53.09 | DocScrutinizer05 | or not at all |
| 16:53.50 | DocScrutinizer05 | which could result in all devices worldwide use same random sequences for tcp stack and whatnot |
| 16:54.22 | DocScrutinizer05 | --> huge security vulnerability |
| 16:55.48 | freemangordon | DocScrutinizer05: nokia: |
| 16:55.49 | freemangordon | https://gitorious.org/community-ssu/upstart/blobs/14e703ee87703880d80bd14b574cbbc96bfe02fe/debian/event.d/system-services/rcS-late#line133 |
| 16:56.33 | DocScrutinizer05 | thought as much |
| 16:56.41 | freemangordon | DocScrutinizer05: though... |
| 16:57.05 | freemangordon | if the line in rcS-late fails, the device wotn boot |
| 16:57.12 | freemangordon | lemme try with dd |
| 16:58.13 | freemangordon | DocScrutinizer05: dd gives the same error |
| 16:58.21 | freemangordon | i'll assume that a false alarm |
| 16:58.49 | freemangordon | if we get the same error in rcS-late, we're in bootloop |
| 17:05.42 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 17:06.10 | kerio | DocScrutinizer05: bitchslap HAM for not presenting the standard "config file changed, overwrite or keep?" dialog on package update |
| 17:06.52 | kerio | diff patches are kinda hard with the way we're doing config files throughout the whole of maemo |
| 17:06.57 | DocScrutinizer05 | well, not everything is a config file |
| 17:07.15 | kerio | if it's not a config file, it's the user's fault for modifying it under dpkg's nose |
| 17:07.26 | DocScrutinizer05 | meh |
| 17:07.44 | kerio | (or the package maintainer's fault for not marking it as a config file) |
| 17:08.17 | DocScrutinizer05 | check who's maintainer and what's package of rcs-late |
| 17:08.34 | DocScrutinizer05 | or of mount-opts |
| 17:09.01 | DocScrutinizer05 | that's exactly why CSSU got _invented_ |
| 17:09.20 | DocScrutinizer05 | so we can't say we're CSSU and not our fault |
| 17:09.32 | kerio | anyway, before pali had finalized the latest system-services, i reported a bootloop that i couldn't properly investigate due to lack of time |
| 17:09.51 | kerio | but my config is way too nonstandard to be of much use :< |
| 17:10.04 | *** join/#maemo-ssu sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net) |
| 17:11.38 | DocScrutinizer05 | actually CSSU should try to cope with as many config variations as reasonably feasible |
| 17:12.20 | DocScrutinizer05 | and for sure we MUST NOT assume a completely standard system as granted |
| 17:13.08 | DocScrutinizer05 | rather we MUST check if the system actually _is_ compatible with whatever we try to propagate to all users |
| 17:13.56 | kerio | this change, if it worked properly, kinda needed some user intervention, in case of a nonstandard config |
| 17:14.07 | kerio | but that's to be expected, a nonstandard config must modify rcS-late |
| 17:14.07 | DocScrutinizer05 | so indiscriminately replacing whatever rcs-late we find on user's system for sure is a extremely silly and stupid thing, not in line with best practice |
| 17:14.28 | kerio | mmh, you can't quite do it differently though |
| 17:14.34 | kerio | not with the current HAM at least |
| 17:14.43 | freemangordon | DocScrutinizer05: and what do you propose to do instead? |
| 17:14.59 | kerio | freemangordon: postinst scripts! :D |
| 17:15.14 | DocScrutinizer05 | you can a) do a md5sum to check if system has unaltered files like rcs-late, and b) apply diffs rather than replace complete files |
| 17:15.29 | kerio | a diff here would still be catastrophical |
| 17:15.45 | kerio | it's quite a substantial change |
| 17:16.06 | kerio | the correct thing to do is to ask the user |
| 17:16.11 | freemangordon | and what if diff cannot be applied? |
| 17:16.13 | kerio | which is what dpkg does |
| 17:16.21 | freemangordon | well, but HAM does not |
| 17:16.35 | freemangordon | so file a bug against HAM |
| 17:16.43 | kerio | is it a bug, though? |
| 17:16.58 | kerio | feature request |
| 17:17.28 | freemangordon | still, I doubt it will be implementd |
| 17:19.51 | DocScrutinizer05 | kerio: see what I suggested before: check md5sum, ifequ: (apply patch, exit), warn user, create backup, apply patch, present to user and ask him if that's OK, exit to editor |
| 17:20.45 | kerio | wait, apply patch? at that point you can just replace the file |
| 17:21.16 | DocScrutinizer05 | so you want to ship a diff AND a full replacement file? why? |
| 17:21.18 | kerio | and yeah, that's pretty much what dpkg does, except that there's no diff between old and new so your choices are to replace, keep or view a diff between current and new |
| 17:21.36 | kerio | current as in the current config file |
| 17:22.32 | DocScrutinizer05 | yes, dpkg should use diffmerge istead of diff |
| 17:23.18 | freemangordon | BTW is rcS-late really a config file? |
| 17:23.23 | kerio | it's in /etc |
| 17:23.25 | DocScrutinizer05 | no |
| 17:23.35 | DocScrutinizer05 | that's why it is no HAM bug |
| 17:23.37 | freemangordon | kerio: I don;t care where it is |
| 17:24.15 | DocScrutinizer05 | ham and dpkg/apt work correctly |
| 17:24.35 | DocScrutinizer05 | it's CSSU maintainers that *handle* it incorrectly |
| 17:24.49 | freemangordon | so, it is Nokia to blame for not doing it in the correct way initially |
| 17:25.00 | freemangordon | and we can fix it |
| 17:25.06 | DocScrutinizer05 | we should make HAM/apt *think/ rcs-late was a config file |
| 17:25.47 | kerio | marking it as not a config file would allow it to be properly dpkg-diverted |
| 17:25.51 | DocScrutinizer05 | (or any other of those scripts, for that topic) |
| 17:25.59 | freemangordon | DocScrutinizer05: wouldn't a correct fix be to move that script to /sbin and to replace rcS-late with a wrapper to it? |
| 17:26.03 | kerio | so user modifications will stay, and the user will be responsible for it |
| 17:26.18 | kerio | otherwise dpkg will make rcS-late.dpkg-new in that directory, which fucks up the boot process |
| 17:27.14 | DocScrutinizer05 | kerio: valid point. Yes we probably shouldn't use dpkg/apt at all for it, rather postinst scripts and handle that stuff manually |
| 17:27.22 | kerio | +1 for anything that removes responsibilities from upstart |
| 17:28.00 | DocScrutinizer05 | freemangordon: ummm - I need to ponder your suggestion |
| 17:29.00 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 17:30.17 | DocScrutinizer05 | we basically need sth similar to quilt/bitbake |
| 17:30.32 | DocScrutinizer05 | by structure |
| 17:31.11 | DocScrutinizer05 | the .deb dpkg is fubar on root, by Nokia abusing stuff with their mp-fremantle-pr |
| 17:32.30 | DocScrutinizer05 | and since everybody has mp-fremantle-pr, we can't assume everybody did any modifications s/he needed in e.g. initscripts in a way that's compatible with .deb/dpkg |
| 17:33.39 | DocScrutinizer05 | so all we could do via HAM/apt/dpkg is to deliver "empty" packages that apply a diff patch to system |
| 17:35.19 | DocScrutinizer05 | since basically *any* user modification to any part included in mp-fremantle-pr is messing up the whole dpkg concept |
| 17:35.45 | DocScrutinizer05 | or rather, CSSU would mess up user's system by installing a new mp-fremantle-pr |
| 17:36.18 | DocScrutinizer05 | that's why I always said CSSU shall leave mp-*-pr behind |
| 17:36.59 | DocScrutinizer05 | unpack it into as many independent pkgs as possible |
| 17:38.29 | *** join/#maemo-ssu Pali_ (~pali@Maemo/community/contributor/Pali) |
| 17:40.05 | *** join/#maemo-ssu b-r-a-i-n (~admin@188.168.202.135) |
| 17:41.20 | *** join/#maemo-ssu kerio_ (~kerio@Maemo/community/contributor/kerio) |
| 17:44.16 | sixwheeledbeast | I have no issues with upstart, why the hate? |
| 17:45.30 | kerio | it's not sysv |
| 17:48.37 | sixwheeledbeast | get with the times :) |
| 17:49.07 | sixwheeledbeast | upstart was made as a better replacement for sysV |
| 17:49.12 | DocScrutinizer05 | upstart as well as systemd have abysmal "UI" |
| 17:49.28 | kerio | yeah, so it can boot faster by using all the multiple cores the n900 has |
| 17:49.31 | kerio | OH WAIT |
| 17:51.18 | DocScrutinizer05 | while sysV has a clear "API" by ls /etc/init.d/*, upstart and particularly systemd offer no clean API/UI to find out what's going on and what are the sysop's options to do now |
| 17:52.28 | DocScrutinizer05 | sysV: for service in /etc/init.d/*; do $service status; done |
| 17:52.38 | DocScrutinizer05 | upstart: ????? |
| 17:53.25 | DocScrutinizer05 | and systemd even abandons runlevels |
| 17:53.57 | kerio | but runlevels are so unix, DocScrutinizer |
| 17:54.14 | kerio | people don't use anything but desktops or tablets |
| 17:54.15 | kerio | you should know that |
| 17:54.22 | DocScrutinizer05 | yeah, so let's see if we find some concept that's more windozy |
| 17:55.17 | DocScrutinizer05 | like systemd needing dbus(!!!) to even start up a system, and having his own shell to communicate with it |
| 17:55.50 | DocScrutinizer05 | clearly an ideal proces#0 |
| 17:56.13 | DocScrutinizer05 | both by system architecture as well as by resource requirements |
| 17:57.15 | DocScrutinizer05 | and here comes my killer argument why both upstart and systemd are hell spawn: upstart is canonical, systemd is poettering |
| 17:57.44 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 17:58.20 | DocScrutinizer05 | both entities are notorious for evil attitude to take unix hostage and turn it into sth that meets their very own design goals and _nothing_ else |
| 18:00.06 | DocScrutinizer05 | generations of linux devels invested eternities of their worktime to make linux a unix-compatible system. Poettering considers this a major *flaw* of linux |
| 18:00.54 | DocScrutinizer05 | plain hybris |
| 18:03.06 | DocScrutinizer05 | "we don't need (easy porting of) *any* of the tools or libs or toolkits or filesystems or drivers of any of the UNIX systems. We are linux, we have everything we need and staying compatible with UNIX blocks our oh-so-devine creativity to have networked audio during user login" |
| 18:22.29 | *** join/#maemo-ssu amiconn (amiconn@rockbox/developer/amiconn) |
| 18:38.29 | DocScrutinizer05 | freemangordon: I don't think the line "" dd if=/dev/hwrng of=/dev/urandom bs=$URANDOM_POOLSZ count=1 "" throwing error would cause a bootloop |
| 18:39.52 | DocScrutinizer05 | after all rcs-late is a upstart script, and there's not much essential after that line in the script section of /etc/event.d/rcS-late |
| 18:42.33 | DocScrutinizer05 | anyway I got 3 lines with RNG in my syslog: |
| 18:42.35 | DocScrutinizer05 | May 31 15:39:58 IroN900 kernel: [ 2.623168] OMAP3 ROM RNG: initializing |
| 18:42.44 | DocScrutinizer05 | during regular boot |
| 18:43.07 | DocScrutinizer05 | and then |
| 18:43.09 | DocScrutinizer05 | Jun 10 17:47:14 IroN900 kernel: [85239.571258] OMAP3 ROM RNG: HW init failed: 1 |
| 18:43.10 | DocScrutinizer05 | Jun 10 17:48:17 IroN900 kernel: [85302.464813] OMAP3 ROM RNG: HW init failed: 1 |
| 18:43.18 | DocScrutinizer05 | during my former tests |
| 18:44.55 | DocScrutinizer05 | freemangordon: Pali_: could you spot the line in kernel printing that error msg? |
| 18:47.06 | DocScrutinizer05 | o.O https://lkml.org/lkml/2013/3/28/536 |
| 18:48.20 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 18:48.43 | *** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net) |
| 18:49.21 | DocScrutinizer05 | I wonder if that's a coincidence that Pali is looking into it recently. I stay with L.J.Gibbs: "I don't believe in coincidences" |
| 18:57.43 | Pali_ | DocScrutinizer05: I ported that driver to 3.9 kernel |
| 19:01.32 | Pali | DocScrutinizer05: http://mxr.maemo.org/fremantle/source/kernel/drivers/char/hw_random/omap3-rom-drv.c#81 |
| 19:02.49 | Pali | it failing call_sec_rom function which is wrapper around smc instruction: http://mxr.maemo.org/fremantle/source/kernel/drivers/char/hw_random/omap3-rom-asm.S |
| 19:03.16 | Pali | it looks like your omap board is broken |
| 19:04.00 | Pali | DocScrutinizer05: try to turn device off and on. NOLO has some code which doing something with M-Shield, so maybe it can reset it |
| 19:04.55 | DocScrutinizer05 | my omap board broken?? duh! |
| 19:05.33 | Pali | secure side of omap cpu returned error |
| 19:05.38 | DocScrutinizer05 | maybe I used a cmd that "broke2 it |
| 19:06.12 | DocScrutinizer05 | this could've been softupd only, for all I can tell |
| 19:07.08 | DocScrutinizer05 | well, ok. I'll give my daily phone another reboot - way too early since it has an uptime of only 10 days |
| 19:10.53 | *** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 19:45.07 | Drathir | hrhr updates knoking to me ^^ |
| 19:45.20 | Drathir | knocking* |
| 19:55.04 | merlin1991 | DocScrutinizer05: upstart has a status check |
| 19:55.07 | merlin1991 | service $service status |
| 19:56.17 | DocScrutinizer05 | uhu, and who tells me about content of $status? |
| 19:56.24 | DocScrutinizer05 | err $service |
| 19:57.25 | merlin1991 | <PROTECTED> |
| 19:58.12 | merlin1991 | but since the upstart on maemo os more than old its not even service ... but "status $service" |
| 20:02.32 | DocScrutinizer05 | hmm I wonder if files like ke-recv.dpkg-new and icd2.dpkg-new in /etc/event.d do any good |
| 20:06.54 | DocScrutinizer05 | http://privatepaste.com/efeb0ad74f |
| 20:11.57 | DocScrutinizer05 | http://privatepaste.com/a46c5d990c |
| 20:12.42 | DocScrutinizer05 | http://privatepaste.com/910207db60 |
| 20:24.10 | freemangordon | Pali: it could be that hwrng cannot be initialized/called more than once |
| 20:25.38 | Pali | DocScrutinizer05: XYZ.dpkg-new files replacing XYZ after successfull installation/upgrade |
| 20:25.50 | freemangordon | if it is broken this https://gitorious.org/community-ssu/upstart/blobs/master/debian/event.d/system-services/rcS-late#line223 would fail on boot |
| 20:26.12 | Pali | if you edited XYZ file, then apt-get will ask you if you really want to update that files |
| 20:26.21 | freemangordon | Pali: so I'd assume we have NFC how it works |
| 20:26.55 | Pali | freemangordon: original nokia code was "dd if=/dev/hwrng of=/dev/urandom bs=$URANDOM_POOLSZ count=1" |
| 20:27.06 | Pali | (or /dev/hw_random) I do not know now |
| 20:27.25 | Pali | one is in vanilla kernel and one in maemo patched udev |
| 20:27.30 | freemangordon | Pali: i looked into it, there is no difference |
| 20:27.43 | freemangordon | it is somewhere in the backscroll |
| 20:27.59 | Pali | you can try to add "|| true" so it skip hwrand error |
| 20:28.16 | freemangordon | Pali: there is no error |
| 20:28.18 | freemangordon | https://gitorious.org/community-ssu/upstart/blobs/14e703ee87703880d80bd14b574cbbc96bfe02fe/debian/event.d/system-services/rcS-late#line133 |
| 20:28.36 | Pali | ok |
| 20:28.42 | freemangordon | Pali: if there was error (during bootup) the device will enter reboot loop |
| 20:28.56 | Pali | right |
| 20:29.06 | freemangordon | DocScrutinizer05 got this error while doing cat /dev/hwrng |
| 20:29.41 | freemangordon | and I am not sure adding || true is a good idea |
| 20:29.58 | freemangordon | as that would mean we'll continue to boot on a faulty HW |
| 20:35.18 | *** join/#maemo-ssu texed (~user@ip-94-113-121-14.net.upcbroadband.cz) |
| 20:58.43 | *** join/#maemo-ssu chem|st (~chemist@svn.unix-ag.uni-kl.de) |
| 21:01.38 | *** join/#maemo-ssu DaRoDi (~DaRoDi@109.88.64.137) |
| 21:29.38 | DocScrutinizer05 | rebooting on a faulty hw for sure is no alternative X-P |
| 21:31.49 | DocScrutinizer05 | if that HWRNG can get initialized only once, then kernel shouldn't de-initialize it after usage, *OR* should immediately close and cleanout/remove /dev/hwrng after it got used |
| 21:32.12 | DocScrutinizer05 | + unload the kernel module |
| 21:35.26 | *** join/#maemo-ssu RoDi (~DaRoDi@109.88.64.137) |
| 21:37.36 | *** join/#maemo-ssu macmaN (~chezburge@138.167.190.90.dyn.estpak.ee) |
| 21:47.13 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 22:10.42 | Pali | DocScrutinizer05: if some application needs random data, then it will use hw random data instead pseudo random |
| 22:11.54 | Pali | in rcS-late maemo setting initial state of pseudo random generator from random data provided by hw |
| 22:12.33 | kerio | how fast is the hwrng? |
| 22:13.04 | kerio | also, *.dpkg-new in /etc/event.d will screw things up, i think |
| 22:19.51 | Pali | kerio: it is slow, but looks like it is faster than /dev/random |
| 22:25.36 | DocScrutinizer05 | kerio: that's what I think as well |
| 22:25.49 | *** join/#maemo-ssu peterpark (543e5811@gateway/web/freenode/ip.84.62.88.17) |
| 22:25.50 | DocScrutinizer05 | a terribly bad idea to place those files there |
| 22:27.59 | Pali | dpkg-new, dpkg-old files are only temporary when dpkg running |
| 22:28.21 | Pali | after successfull upgrade those files are moved/removed |
| 22:28.45 | Pali | it looks like HAM broke something... |
| 22:29.06 | Pali | who created that HAM???? |
| 22:30.56 | kerio | Pali: apt-get does that too |
| 22:31.18 | Pali | ah... |
| 22:31.39 | kerio | that's why /etc/event.replace.d exists i think |
| 22:32.07 | kerio | put the file there, copy it and remove any extra cruft in postinst |
| 22:34.17 | DocScrutinizer05 | anyway my dpkg is NOT running |
| 22:38.17 | DocScrutinizer05 | I think event.replace.d is for recovering from terribly fuxored setup |
| 22:53.43 | peterpark | is the cssu/testing release still stuck in reboot loop? |
| 22:53.57 | tadzik | nope |
| 22:56.55 | peterpark | thanks for the info! Keep up the good work! |
| 22:56.59 | peterpark | double thumbs up!! |
| 22:57.09 | tadzik | at least it works for me :) |
| 22:57.57 | peterpark | I will have a try then :) |
| 23:11.26 | peterpark | great! my nokia is alive again! |
| 23:49.36 | *** join/#maemo-ssu acab (~acab@80.94.231.67) |
| 23:49.57 | acab | hello, i have last cssu, but i havent rtcom-messaging-ui-portait conversations in portrait |