IRC log for #maemo-ssu on 20130827

00:43.44*** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1)
01:04.39*** join/#maemo-ssu povbot_ (~supybot@office.pov.lt)
01:04.39*** mode/#maemo-ssu [+v povbot_] by ChanServ
01:28.37*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@113.73.161.151)
02:25.33*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:07.22*** join/#maemo-ssu FlameReaper (~assassin@203.106.67.128)
04:57.01*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
05:04.11*** join/#maemo-ssu M13 (~Miranda@217.118.91.101)
05:48.10*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@113.73.161.151)
06:22.14*** join/#maemo-ssu dafox (~dafox@88.128.80.6)
06:23.36*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@113.73.161.151)
06:26.36*** join/#maemo-ssu dhbiker (~dhbiker@APN-123-191-205-gprs.simobil.net)
06:47.54*** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net)
06:57.24*** join/#maemo-ssu FlameReaper (~assassin@183.171.172.206)
07:13.36*** join/#maemo-ssu FlameReaper (~assassin@183.171.175.153)
07:56.30*** join/#maemo-ssu kolp (~quassel@212.255.246.235)
08:06.08*** join/#maemo-ssu LauRoman (~LauRoman@5-14-93-219.residential.rdsnet.ro)
08:32.56*** join/#maemo-ssu psycho_oreos (~no@unaffiliated/tuxsavvy)
09:14.30*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
09:19.43*** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net)
09:42.01*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-125-57.net.upcbroadband.cz)
11:13.39*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
11:28.05*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
11:32.10*** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1)
11:47.27*** join/#maemo-ssu arcean (~arcean@aafr254.neoplus.adsl.tpnet.pl)
13:40.33*** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net)
13:55.56*** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net)
14:05.05*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
15:00.13*** join/#maemo-ssu NIN101 (~NIN@p5DD28BFA.dip0.t-ipconnect.de)
15:08.17*** join/#maemo-ssu drathir (~kamiljk8@s51.linuxpl.com)
16:00.57*** join/#maemo-ssu FatPhil (~pcarmody@87-119-183-129.tll.elisa.ee)
16:10.36FatPhilDoes the CSSU pay any attention to the ARM errata for the OMAP?
16:11.26FatPhilFor example, enabling Thumb2 can cause heisenbugs
16:17.23*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
16:17.38kerioFatPhil: cssu-thumb ships a kernel (which is a rebranding of kernel-power) with the errata workaround
16:17.57keriothere's some sort of plan to update the kernel for cssu proper
16:20.01FatPhilwhat's the giturl for the kernel, I'll grab a copy when I get home
16:20.21keriomh, poke freemangordon or Pali
16:20.24kerioPali: *poke*
16:20.28FatPhilAnd do you have a commit id for the fix (it might not be the same bug that I'm thinking of)
16:20.47kerioit's the same bug i think
16:21.05kerioerrata 430973 and errata 657417
16:21.09PaliFatPhil: gitorious.org/community-ssu
16:21.36FatPhilhmm, is there a problem with static.maemo.org ? wiki pages are taking for ever to load
16:22.17*** join/#maemo-ssu dafox (~dafox@88.128.80.6)
16:25.48FatPhilOK, found git@gitorious.org:community-ssu/kernel-cssu.git ...
16:26.13FatPhiltime to go home, methinks...
16:50.29DocScrutinizer05?o/
16:50.38DocScrutinizer05\o/ even
16:51.19DocScrutinizer05FatPhil: freemangordon did an awesome work (rather fight) to fix the thumb heissenbug
16:51.26*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
16:51.32DocScrutinizer05and he finally succeeded I'd say
16:51.36DocScrutinizer05:-D
16:59.30DocScrutinizer05static.m.o maybe had a temporary hickup. I can't detect any problems right now
17:01.14DocScrutinizer05FatPhil: if any such problems like slow static.maemo.org arise, please do: *) check http://monitor.maemo.org/ganglia/  *) ping me or warfare or freemangordon or merlin1991 on IRC  *) send a mail to techstaff@maemo.org
17:01.50FatPhilThe thunmb one (something to do with a cache boundary, but I forget what) was never hit in practice, but TI and ARM didn't have a work around, so we just disabled thumb, not wanting to risk it in the released product.
17:02.22DocScrutinizer05mhm, interesting new facts
17:02.25FatPhilSomething that happens only once a year for an engineer happens several times a day to 100000 customers.
17:02.36DocScrutinizer05yep, sure
17:02.41FatPhilIs anyone (still) in Nokia?
17:02.48DocScrutinizer05not afaik
17:03.10DocScrutinizer05well, we have one contact, or we had several months ago at least
17:03.34FatPhilThe channel's logged, though, so I shouldn't say anything too revealing.
17:03.43DocScrutinizer05hehe
17:05.55DocScrutinizer05SiErr in TI and what needed to be done to cpe with them are not really highly secret (anymore)
17:06.09DocScrutinizer05cope even
17:07.03DocScrutinizer05particularly when they are published in TI's own SiErr list - which not all of them are, see the nasty one in OMAP4 I mentioned in #maemo
17:07.24*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
17:09.05DocScrutinizer05We're currently wondering about some SiErr in twl4030, do you happen to know why e.g Nokia didn't use the audio of GAIA?
17:09.56DocScrutinizer05I gather the whole USB disaster been due to a SiErr in twl4030 PHY which failed to detect fastchargers
17:10.21DocScrutinizer05but why is nobody (Nokia, Pandora) using the audio of twl4030?
17:13.50FatPhilI see from linux-arm-kernel that freemangordon is in dialog with both Tony and Nishanth, so if they've seen his patches they're probably good.
17:15.22FatPhilOK, that git repo is diffs relative to some baseline - but what baseline?
17:24.50DocScrutinizer05probably stock
17:26.10DocScrutinizer05that's a big nasty in all maemo kernel I've been told by those who actually touched that stuff. Originally there been no git for kernel, so aiui everything got applied by a huge diff patchset
17:26.20FatPhilpullable from where? I have no idea how you outsiders get your kernels! ;-)
17:26.36DocScrutinizer05that's the crux
17:26.47DocScrutinizer05there's probably no "root" for that
17:26.58DocScrutinizer05(git noob here)
17:33.05*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-85-160-62-19.eurotel.cz)
17:43.47FatPhilDamn, I've forgotten everything
17:45.09FatPhilanyone know what version 21.2011.38-1 corresponds to?
17:45.27FatPhilThis new n900 has been quite pimped, I really have no idea what's on iyt
17:46.24*** join/#maemo-ssu MohammadAG_ (~MohammadA@Maemo/community/contributor/MohammadAG)
17:51.37*** join/#maemo-ssu discopig (~discopig@unaffiliated/discopig)
17:52.46ShadowJKMy guess is Probably 1.3
17:52.54ShadowJKunless I'm confusing with Diablo
17:53.59FatPhilI don't have a FIASCO that corresponds to that, alas
17:54.35FatPhilIt would be nice to know I could just restore it to the state before I start experimenting
17:54.46ShadowJK1.3.1 then? Minor update that never received an image
17:54.53keriothere's even pr131
17:55.00kerioShadowJK: there's an image
17:55.52ShadowJKok so 38-1 is pr 1.3.1
17:55.57FatPhilfrom t.m.o, "21.2011.38-1 PR is the version that is installed in my N900 which is pr1.3.1"
17:59.20*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
18:01.10DocScrutinizer05~pr131
18:01.10infobotmethinks combined is the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://maemo.cloud-7.de/maemo5/fiasco+co/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin  or  http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin
18:01.57DocScrutinizer05last "official" one been PR1.3 aka 2010.36-2 iirc
18:02.27FatPhilI have 36-2 PR and RD images, but nothing newer :-|
18:02.55DocScrutinizer0538.1 is just with some SSL cert patches
18:03.01DocScrutinizer05see
18:03.03DocScrutinizer05~cssu
18:03.03infobot[cssu] http://wiki.maemo.org/Community_SSU
18:03.43DocScrutinizer05also see
18:03.45DocScrutinizer05~bm
18:03.46infobotsomebody said backupmenu was http://talk.maemo.org/showthread.php?t=63975
18:04.03DocScrutinizer05(for "restore what been there")
18:04.24FatPhilI only just got the device, there's none of my data on it.
18:04.35DocScrutinizer05caveat: it does NOT backup7restore kernels
18:04.47FatPhilRestore for me just means a fresh OS
18:05.01DocScrutinizer05BM does a full rootfs image
18:05.26DocScrutinizer05it however does NOT backup/restore kernel NAND partition
18:05.43FatPhilI was thinking it would be nice to take a device, and create a FIASCO that would regenerate that device.
18:06.04DocScrutinizer05~bm
18:06.04infobothmm... backupmenu is http://talk.maemo.org/showthread.php?t=63975
18:06.31DocScrutinizer05>>Can I restore my BackupMenu images through the Nokia Flasher?<<
18:06.57DocScrutinizer05>>It -is- possible to convert a BackupMenu image to a Nokia Flasher rootfs image, but it requires a Linux PC with mtd-utils.<<
18:10.14FatPhilwhat's a COMBINED fiasco?
18:11.55FatPhilWhat MMC image goes with the 131 rootfs?
18:12.10DocScrutinizer05there are two image types, COMBINED aka rootfs, and VANILLA aka eMMC
18:12.51DocScrutinizer05there are just 2 eMMC images, the newer one is unchanges since... errr PR1.1?
18:14.38DocScrutinizer05I *guess* /home/jr/n900/RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin is newest one
18:16.06DocScrutinizer05~flashing
18:16.07infobothmm... maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware
18:16.17FatPhilcool, I already have that fiasco
18:23.38FatPhilSo is CSSU just a series of package upgrades relative to 131? There's no "can't downgrade" NOLO security bullshit implications?
18:24.17FatPhildamn, root password isn't rootme...
18:28.28ShadowJKinstall rootsh
18:29.08ShadowJK"rootme" needs RD mode enabled via flasher, iirc, and comes with side-effects
18:30.02FatPhilit has sudo gainroot enabled, and I stuck it in rd mode
18:30.13FatPhilso my console's now active, yay
18:31.49FatPhilare there any tell-tale packages I can look for to see if I've got cssu already installed (and in which case, what version)?
18:32.44ShadowJKSettings - "About Community SSU",
18:33.05ShadowJKdpkg -l | grep cssu
18:33.06ShadowJKI guess
18:33.47FatPhilthat's what I tried first - nothing, and settings shows nothing
18:34.16FatPhilso previous owner just stuck 100s of packages on it (including gui tweaks that confuse me!)
18:44.53*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
18:47.54*** join/#maemo-ssu discopig (~discopig@unaffiliated/discopig)
18:51.22FatPhilyeah, I think ARM errata 430973 was the Thumb issue I remember (or should I say, clearing the BTB could solve the issue that I remember)
18:53.02DocScrutinizer05yep
18:53.57FatPhiloooh, uname says "Linux Nokia-N900 2.6.28.10-power50 #1 PREEMPT Sun Mar 18 20:10:56 EET 2012 armv7l unknown
18:54.07DocScrutinizer05and it supposedly "can't be done" on N900 due to NOLO locking the HS or whatever. Fremangordon found some call to ROM-monitor to toggle the relevant bit nevertheless
18:54.27DocScrutinizer05KernelPower50
18:54.59DocScrutinizer05you should probably upgrade to 52
18:55.49DocScrutinizer05wishes Pali and/or FMG were aroundd
18:55.52*** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net)
18:56.10DocScrutinizer05~botsnack
18:56.10infobotaw, gee, DocScrutinizer05
18:57.11kerioFatPhil: just reflash it
18:58.57FatPhilpackage manager is offering me updates, I see a 52 in apt-cache search
18:59.48keriowhat's this n900? bought used?
18:59.55kerioor just forgotten in a drawer?
19:01.17*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
19:02.24FatPhilbought used
19:03.02FatPhilBought 2 used in the last month.
19:03.17kerioso... why aren't you reflashing it?
19:04.10FatPhilI'll probably reflash the other one.
19:04.18keriothey're used
19:04.31kerioyou can't know which rootkit the previous owner has installed on it
19:05.02FatPhilI worked with the previous owner at nokia, and work with him in my current job too. No rootkits
19:05.32FatPhilHe's put loads of toys on it, it might be nice to play with a few to see if I want to keep them
19:05.47FatPhilbugger, package conflicts
19:06.12FatPhilHas anyone got aptitude to work? (the command line works, but not the GUI, IIRC)
19:12.05DocScrutinizer05go for BM! really!
19:12.38DocScrutinizer05BM is your only chance to restore all those awesome toys
19:14.36DocScrutinizer05install backupmenu, make a backup of rootfs and /opt (actually /home) to MyDocs (or even better a uSD), backup the MyDocs content via mass storage mode. Then do a uname -a and label the backup with the kernel version to not mess up when you restore
19:15.19DocScrutinizer05restoring rootfs (incl modules) to a non-matching kernel causes bootloops
19:16.45DocScrutinizer05thus: label your backup with the kernel version and copy the backup and MyDocs to your PC. You're done for any disaster recovery
19:17.26DocScrutinizer05power users and devels say, resoring a BM backup is easier than reflashing
19:17.28FatPhilyeah, gonna install BM. BUt gonna use aptitude to install it, as I can't grok the bloody gui
19:18.34DocScrutinizer05as long as you don't do apr-get upgrade or apt-get dist-upgrade or apt-get autoremove, you're fine
19:19.43DocScrutinizer05mind you, maemo is NOT debian ;-)
19:20.00DocScrutinizer05though it almost looks alike
19:22.54FatPhilhmmm, root's PATH was bogus, that's odd
19:23.03DocScrutinizer05my KP install procedure: cd ~MyDocs; wget kernelpower kernelpower-flasher kernelpower-modules; while ! dpkg -i kernel*.dpk; do :; done
19:24.15DocScrutinizer05after the max 3rd dpkg invocation, all three pkgs should be installed properly
19:24.19FatPhilI'm confused by the optified nature of this device
19:24.28DocScrutinizer05hehehe
19:24.35DocScrutinizer05~optification
19:24.35infobotoptification is a inventive duct tape workaround to reclaim space in fs root, done due to the fact the systeminit *and* partitioning is FUBAR,  http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing/Installing_under_opt_and_MyDocs, or ""OMG - I wish they looked into FHS and moved /usr to eMMC"", http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE2 bullet1,2 and fhs-2.3.html#PURPOSE16 dot3"
19:24.59FatPhillooks like my daily device is 1.3 and is not optified
19:25.08DocScrutinizer05WUT?
19:25.24DocScrutinizer05df -h /opt
19:26.03DocScrutinizer05hardly feasible
19:26.17DocScrutinizer05there's not enough space on NAND /
19:26.29*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
19:26.29DocScrutinizer05that's why Nokia invented optification
19:26.59DocScrutinizer05since PR1.2 a device won't run without proper 7opt
19:27.03DocScrutinizer05/opt even
19:27.11FatPhil/dev/mmcblk0p2   2.0G   448.4M    1.4G   23%  /home
19:27.20DocScrutinizer05excellent
19:27.29FatPhilI kinda optified it myself about a year before nokia invented optification
19:27.42FatPhilI think
19:27.47FatPhilI have no idea wat device this is
19:28.08FatPhilI've had about 10 in my time, and did different things to each of them
19:28.29DocScrutinizer05don't tell me, I know that with another device ;-)
19:28.51DocScrutinizer05tries to count the Neo Freerunner he has or had
19:28.54FatPhilall I know is that it says 20.2010.36-2, and it doesn't have all the bloody bind mounts
19:29.11DocScrutinizer05o.O
19:29.41DocScrutinizer05http://paste.opensuse.org/24388439
19:29.53DocScrutinizer05for your reference
19:30.37FatPhilyeah, I have no /opt/py*
19:30.45DocScrutinizer05frowns at paste.opensuse
19:31.22DocScrutinizer05missing python upgrades
19:31.39DocScrutinizer05not fremantle core
19:31.39FatPhilI did my optification just using symlinks, assuming this is the one I did it to
19:32.05DocScrutinizer05symlinks is the way optification works
19:32.18DocScrutinizer05python is a special critter
19:33.17DocScrutinizer05pymaemo-optify - PyMaemo optification package
19:33.41DocScrutinizer05came with PR1.2 iirc
19:33.48DocScrutinizer05or shortly after
19:34.43FatPhilyeah, my old device is clear of that pymaemo-optify crap
19:35.13FatPhilI've never liked bind mounts anyway, but this is total abuse of them.
19:35.20DocScrutinizer05won't hurt until you want to runa any python based app
19:36.12DocScrutinizer05agrees in "abuse" notion
19:36.30DocScrutinizer05nfc why they didn't use symlinks
19:38.00DocScrutinizer05one possible explanation would be: a reduced set of python support crap is needed in early boot, so there actually is sth in /opt/pymaemo/*
19:38.15DocScrutinizer05later on they bindmount the true stuff over that
19:38.26FatPhil'cos I wasn't in the packaging team, that's why!
19:38.33DocScrutinizer05hehe
19:39.05FatPhilThen again, I'd have just got the partition sizes (and distribution across devices) right in the first place
19:39.25DocScrutinizer05indeed
19:39.51DocScrutinizer05againn (sorry)
19:39.53FatPhilSwap was bouncing between OneNAND and eMMC several times, they couldn't make their mind up. And when they finally decided on a layout, they got it wrong!
19:39.55DocScrutinizer05~optification
19:39.56infobotoptification is a inventive duct tape workaround to reclaim space in fs root, done due to the fact the systeminit *and* partitioning is FUBAR,  http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing/Installing_under_opt_and_MyDocs, or ""OMG - I wish they looked into FHS and moved /usr to eMMC"", http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE2 bullet1,2 and fhs-2.3.html#PURPOSE16 dot3"
19:40.15*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
19:40.17DocScrutinizer05~factinfo optification
19:40.17infobotoptification -- created by DocScrutinizer <~jr@openmoko/engineers/joerg> at Mon Mar 15 10:29:39 2010 (1261 days); last modified at Wed Nov 30 04:17:02 2011 by DocScrutinizer!~halley@openmoko/engineers/joerg; it has been requested 121 times, last by DocScrutinizer05, 22s ago; it has been locked by DocScrutinizer.
19:42.57FatPhilhmmm, I do have a single opt bind mount, just not the pymaemo ones. No idea how I managed to avoid those
19:43.17FatPhilSo clearly this wasn't the device I self-optified
19:43.26DocScrutinizer05never installed pymaemo-optify package?
19:43.42FatPhilif it's not essential generally I don't install anything
19:44.14FatPhilmy n900 is used for calls, smses, browsing, and ssh-ing to my home machine
19:44.14DocScrutinizer05it's not essential until you want to run apps that are based on python
19:44.40DocScrutinizer05all that works without python pretty much ;-)
19:45.14DocScrutinizer05I do the other way around usually, my home machine ssh into N900
19:45.21FatPhil14 python packages installed
19:45.34ShadowJKRe root's path, "sudo gainroot" is equivalent to "su", which retains user environment. "root" when you've got rootsh installed is equivalent to "su -", which gives root env and path
19:45.35DocScrutinizer05prolly none of them wirll work
19:45.55DocScrutinizer05ShadowJK: \o/
19:45.56DocScrutinizer05ack
19:46.06FatPhilshadowjk: this was root login from the serial console
19:46.15DocScrutinizer05has to leave for dinner
19:46.27ShadowJKI, for one, like having rootfs on nand, as ubifs is much more competent than ext3 on emmc
19:46.31DocScrutinizer05check your shell init scripts
19:47.24DocScrutinizer05oooh, dunno if you find anything useful in it (just occurs to me when I say "check shell init"):
19:47.28DocScrutinizer05~jrtools
19:47.28infobotfrom memory, jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
19:49.00FatPhilmy device has a sensible ~root/.profile, the new device has none. I guess previous owner may have blatted some dirs
19:51.04DocScrutinizer05grins at >>All these hacks are tested on PR1.2(!!), but the cmdlines here are just off top of my head, so maybe typos or sth can be found. Lots of it will work on PR1.3 as well, but I haven't tested anything for PR1.3 yet<< proving he refused for quite some time to upgrade to PR1.3
19:51.57ShadowJKIf I had tons of spare time, and someone made a modern kernel work, I'd probably convert my device to use f2fs for /home and MyDocs :)
19:52.20DocScrutinizer05f2fs? o.O
19:52.36ShadowJKflash friendly filesystem
19:52.44DocScrutinizer05obsoletes ubi?
19:53.26DocScrutinizer05sounds intriguing
19:53.34ShadowJKNo, it's for emmc/sd
19:53.41DocScrutinizer05aah
19:53.45ShadowJKnot for raw nand
19:54.24DocScrutinizer05I bet Pali will love to implement it into KP
19:59.49FatPhilshadowjk 3.10: boots on n900
20:00.08ShadowJKiirc there were modem issues?
20:00.43FatPhilwhether it works with hildon userspace is another matter. but you can boot to a minimal shell.
20:01.44FatPhilthere's a guy who tests every kernel release on his n810, his n900, his n950 and his n9
20:02.13FatPhilbut being a kernel dev, he doesn't care about userspace - a shell's all he needs
20:03.13FatPhilHe might well be interested in contributing to Neo900
20:07.13DocScrutinizer05coool
20:07.44DocScrutinizer05our problem with fremantle port is: it depends on a certain look&feel of kernel API
20:08.05DocScrutinizer05actually our problem with all kernels
20:08.21DocScrutinizer05KP as well as Neo900
20:08.57DocScrutinizer05basically KP is all about keeping 2.6.28 API/ABI while backporting all the new good stuff
20:09.41DocScrutinizer05if we only could implement a compatibility layer between recent API (read: sysfs etc) and fremantle userland...
20:10.23DocScrutinizer05and the very few direct kernel function calls that may have changed
20:10.43FatPhilYou're not saying that kernel devs have broken userspace are you??!?!?!
20:10.53DocScrutinizer05LOL
20:10.54FatPhilBut teh Linus says that never happens!
20:11.35DocScrutinizer05no, it been evidently Nokia that created broken crappy closed userland apps
20:11.47DocScrutinizer05that are too silly to learn new sysfs paths etc
20:12.11DocScrutinizer05even worse: libs
20:12.28ShadowJKBesides sysfs, there was a bug in the kernel, I forget the details, which some of the closed source packages depend on
20:12.41DocScrutinizer05o.O
20:12.51DocScrutinizer05pthread?
20:12.52ShadowJKiirc
20:12.58DocScrutinizer05or what it's called?
20:13.04ShadowJKNo I donmt remember what area
20:13.10DocScrutinizer05aah no, poll
20:13.33DocScrutinizer05hardly the right one
20:13.42DocScrutinizer05since nothing can depend on it
20:13.48DocScrutinizer05it's simply broken
20:14.04FatPhilno syscalls have been removed, we'd never do that
20:14.12DocScrutinizer05yep
20:14.19DocScrutinizer05nobody claimed that
20:14.54DocScrutinizer05but aiui some libs (powervr?) are linked against a certain kernel ABI
20:15.24DocScrutinizer05and as long as you can't recompile them... dooom
20:15.53FatPhilThere was a change in the POLL_IN behaviour in poll on virtual files
20:16.29DocScrutinizer05some *poll* been emuated in libc, but not for ARM
20:16.39DocScrutinizer05emulated
20:17.05FatPhilAfter 2.6.29 you had to use POLL_PRI, otherwise you'd spin
20:17.08DocScrutinizer05ask the CSSU dudes, we're getting a new libc for that
20:17.53FatPhilsh: =: unknown operand
20:18.04FatPhilsh: 0: unknown operand
20:18.43DocScrutinizer05https://bugs.launchpad.net/ubuntu/+source/linux/+bug/319729
20:18.53DocScrutinizer05here you are
20:19.02FatPhilIf you want to stay sane - never look at the console...
20:19.08DocScrutinizer05dang, that took long
20:19.48DocScrutinizer05<PROTECTED>
20:20.28*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
20:21.37DocScrutinizer05FMG fixed it
20:21.56DocScrutinizer05afaik
20:22.21DocScrutinizer05now I hope we hooked you as kernel maintainer ;-)
20:22.46DocScrutinizer05since, if that's not your fav stuff, I dunno what else is
20:23.26ShadowJKThat must be some nightmare scenario, to get thrown back to a world of 2.6.28
20:23.35DocScrutinizer05ROTFL
20:24.56DocScrutinizer05well, come up with a nice compatibility layer (some symlinks?) and we happily migrate to kernel5.756, as long as our lib blobs still work
20:25.40ShadowJKI wonder if that can be fudged in userspace with LD_PRELOAD tricks
20:25.44FatPhil2.6.28's a bit outdated, yeah. Doesn't have some must-have features
20:26.47ShadowJKvaguely recalls trying to convince microb in Diablo to not focus-steal, via LD_PRELOAD tricks
20:26.57DocScrutinizer05tbh we lack true kernel hackers
20:27.33DocScrutinizer05even pali and FMG are not the natural born kernel hackers
20:27.51DocScrutinizer05they do an awesome job, sure
20:27.53ShadowJKTurns out there are 97 different ways for an app to bring itself to front and steal focus, and mozilla/gecko/microb called everyone of them 7 times just to be sure.. so I gave up :)
20:28.11DocScrutinizer05lol
20:28.12FatPhilI wouldn't claim to be one myself, it just so happens I ended up having to work on it
20:28.40FatPhilShadowJK: I remember bugs being filed about that.
20:29.50FatPhilprocess 1356: arguments to dbus_connection_unregister_object_path() were incorrect, assertion "path != NULL" failed in file dbus-connection.c line 5567.
20:29.54FatPhilThis is normally a bug in some application using the D-Bus library.
20:30.09DocScrutinizer05anyway, i have to take care about my dinner now. For real. Please give FatPhil a cosy feeling and a heartly welcome
20:30.48DocScrutinizer05bbl
20:31.00FatPhilI need to get some food myself too
20:31.10ShadowJKYou'll saturate serial console with dbus and gtk warnings...
20:31.53FatPhilshadowjk: I was behind the great console spam cleanup operation. Must have filed hundreds of bugs against userspace.
20:33.17FatPhilYOu wouldn't believe some of the crap excuses they gave. Actually, you probably would, as you've probably seen their source code.
20:34.33*** join/#maemo-ssu arcean (~arcean@aafr254.neoplus.adsl.tpnet.pl)
20:35.57ShadowJKI once tried to submit a bugreport+patch to gypsy. Though it was said in different words, the reply was basically "yes it's broken for real life, but it passes all our tests and the spec", bug closed :-)
20:36.56*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
20:39.02FatPhilSeen many a response like that
20:39.35FatPhilClearly sometimes tests don't include things like "must not emit any GTK assertion failures"
20:39.45*** join/#maemo-ssu LauRoman (~LauRoman@5-14-93-219.residential.rdsnet.ro)
20:40.12ShadowJKso you redirect stderr to /dev/null on start?
20:40.16ShadowJK;D
20:40.17FatPhilI tried to persuade them to turn assertion failures into fatals, and their response was "but nothing would run!"
20:41.07FatPhilshadowjk: the bodgers in HArmattan time did exactly that - except they used "console none" in their upstart script
20:42.20ShadowJKlol
20:45.27*** join/#maemo-ssu _rd (~rd@p57B495D6.dip0.t-ipconnect.de)
20:48.00DocScrutinizer05just for some idea you can chew on while I'm off for diner: how about a FMRX replaced by a SDR, like http://sdr.osmocom.org/trac/wiki/rtl-sdr, but hooked up directly to some shared RAM that can get processed by DSP?
20:49.41FatPhilShadowJK: do you know what kernel tree/tag the kernel-cssu is based on?
20:51.01ShadowJKMy guess would be that it's based on nokia's kernel as it is in the source deb?
20:51.08DocScrutinizer05prolly a terrible power hog (the E4000 is rated ~500mW iirc), but definitely a cool set op option you get
20:51.50DocScrutinizer05RX from 20 to 2000MHz, SDR
20:52.09DocScrutinizer05means you even could do DVB-T
20:52.30DocScrutinizer05and maybe GPS as well
20:52.32ShadowJKBut could you do police radar warner?
20:52.33DocScrutinizer05;-D
20:52.39DocScrutinizer05sure
20:52.46ShadowJKWith infinite amounts of code..
20:52.48DocScrutinizer05for those <2Ghz
20:53.57*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
20:53.59DocScrutinizer05well the rtl2832 would do DVB-T decoding for you
20:54.14DocScrutinizer05but is has USB interface :-/
20:54.26FatPhilwhere's the bleedin nokia deb-src url?
20:54.51ShadowJKAn SDR module would be cool idea implemented in Jolla's "other half" style though
20:54.54DocScrutinizer05ok, on GTA04 we at least have full featured hostmode that *maybe* can do highspeed
20:55.26DocScrutinizer05forget that jolla isdea, you won't see the highspeed interface to OH
20:55.50DocScrutinizer05I still wonder if their interface is BT or NFC
20:55.53ShadowJKyeah they're probably doing NFC
20:56.17DocScrutinizer05screw dat
20:56.22DocScrutinizer05boring
20:56.32FatPhilIceweasel can't find the server at maemo.research.nokia.com
20:56.50DocScrutinizer05prolly scrapped
20:57.14DocScrutinizer05n.c tore down a lot of URLs
20:57.19DocScrutinizer05aka servers
20:57.30FatPhilindeed
20:58.15DocScrutinizer05even worse: some of them gone down without any prior notice
20:58.24DocScrutinizer05~skeiron
20:58.24infobotrumour has it, skeiron is the semi-official backup and emergency standin for all internet borne maemo resources: http://skeiron.org/tablets-dev/   http://talk.maemo.org/showthread.php?p=1315143#post1315143, or see: ~tabletsdev
20:59.17ShadowJKdeb-src http://repository.maemo.org/ fremantle/sdk free
20:59.30DocScrutinizer05seems I'm already too late for dinner. Might become a beer then
21:01.04DocScrutinizer05actually I wonder why skeiron factoid still mentions tablets-dev
21:01.27DocScrutinizer05this should be one of the few n.c URLs that still work
21:01.38DocScrutinizer05;-)
21:01.46ShadowJKwasnt working earlier when I tried
21:02.02DocScrutinizer05please holler immediately when it doesn't
21:02.20DocScrutinizer05we need to fix that before somebody complains at Nokia care about it
21:02.39ShadowJKic
21:02.53DocScrutinizer05~tabletsdev
21:02.53infobotwell, tabletsdev is http://tabletsdev.maemo.org, or http://wiki.maemo.org/Tabletsdev
21:03.02DocScrutinizer05damn
21:03.37ShadowJKthat works
21:04.21DocScrutinizer05infobot: no, tabletsdev is http://tablets-dev.nokia.com/
21:04.21infobotokay, DocScrutinizer05
21:04.47DocScrutinizer05~tabletsdev is also http://wiki.maemo.org/Tabletsdev
21:04.47infobotokay, DocScrutinizer05
21:05.40DocScrutinizer05~tabletsdev is also http://skeiron.org/tablets-dev/ or http://tabletsdev.maemo.org
21:05.40infobotDocScrutinizer05: okay
21:06.05DocScrutinizer05~tabletsdev
21:06.05infoboti guess tabletsdev is http://skeiron.org/tablets-dev/http://tabletsdev.maemo.org
21:06.13DocScrutinizer05wtf?!
21:06.39DocScrutinizer05~forget tabletsdev
21:06.40infobotDocScrutinizer05: i forgot tabletsdev
21:06.53DocScrutinizer05+listkeys tabletsdev
21:06.57DocScrutinizer05~listkeys tabletsdev
21:07.53DocScrutinizer05~tabletsdev is <reply>http://tablets-dev.nokia.com/  http://wiki.maemo.org/Tabletsdev ,  http://skeiron.org/tablets-dev/ or http://tabletsdev.maemo.org
21:07.53infobotDocScrutinizer05: okay
21:07.59DocScrutinizer05~tabletsdev
21:07.59infobothttp://tablets-dev.nokia.com/  http://wiki.maemo.org/Tabletsdev ,  http://skeiron.org/tablets-dev/ or http://tabletsdev.maemo.org
21:08.43DocScrutinizer05weird bug in bot
21:08.48FatPhilhere's the pselect patch, indeed not in the nokia kernel:
21:08.49FatPhilcommit 369842658a36bcea28ecb643ba4bdb53919330dd
21:08.49FatPhilAuthor: Mikael Pettersson <mikpe@it.uu.se>
21:08.49FatPhilDate:   Sat Aug 15 12:58:11 2009 +0100
21:09.06DocScrutinizer05but in CSSU/KP
21:10.42DocScrutinizer05ran childspin on my N900 to prove we got that problem. It's indeed not on Nokia kernel
21:11.18DocScrutinizer05you need to give system some decent load so eventually it will preempt the childspin process
21:12.26DocScrutinizer05nice -15 while true; do x=$((55555/333)); done
21:12.46DocScrutinizer05in a second shell. does the trick
21:13.25FatPhilhmmm, I've got way too many repos here. just discovered a copy of git://gitorious.org/nokia-n900-kernel/nokia-n900-kernel.git
21:13.54DocScrutinizer05mhm
21:15.28FatPhilThat was probably Ameya's tree, I thikn he rebased to 2.6.35
21:17.03FatPhilhow's maemo.org being financed and managed?
21:19.42DocScrutinizer05financed by free colocation, managed by stupid volunteers like me
21:20.12kerioso stupid
21:20.25kerioliterally the stupidest tech staff coordinator we have
21:20.28DocScrutinizer05http://talk.maemo.org/showthread.php?p=1369830#post1369830  awesome
21:20.47DocScrutinizer05kerio: absolutely
21:28.16ShadowJK7 months ago the hosting was expensive, and the decisionmaking was stalled by everyone except the filibustering lawyer resigning in protest, or something like that. I might remember wrong though :)
21:28.39ShadowJK(especially as I had and still havent got much time to follow stuff)
21:45.33FatPhilhmmm, backupmenu's a no-go as it depends on mtd-tools, which depends on liblzo2-2 which isn't available.
21:46.58kerioD:
21:47.05keriobut seriously tho
21:47.33kerioflash dat shit
21:48.09FatPhilI'll flash my other spare one, I'll probably pick it up at the weekend, or have my g/f bring it over
21:48.46ShadowJKit's in fremantle tools
21:59.14FatPhilyou're not implying I need an SDK are you?
22:02.56keriono, but you might need to install the package from the fremantle/tools repo
22:08.14FatPhilcan't find a link for that repo
22:08.16DocScrutinizer05http://maemo.org/packages/view/liblzo2-2/
22:08.55DocScrutinizer05http://maemo.org/packages/view/backupmenu/
22:09.29keriowhy is there a package in -testing that can't be installed?
22:09.55DocScrutinizer05lik to tools repo on ~jrtools
22:10.14DocScrutinizer05because somebody thought we might promote it?
22:10.46DocScrutinizer05robbiethefirst been aware that it's facing depedency problems in extras(-testing)
22:11.07DocScrutinizer05I simply might fix that, promoting liblzo2-2 to extras ;-P
22:12.14DocScrutinizer05iirc it been me who told him "promote it! we'll deal with any problems in that later"
22:12.42DocScrutinizer05now we know the problems, now we can deal with them, eh? ;-D
22:13.22DocScrutinizer05though I thought it been i2c-tools that were not available in extras
22:13.47DocScrutinizer05actually I#m a bit puzzled about liblzo
22:13.56FatPhilliblzo2-dev - data compression library (development files)
22:13.56FatPhilliblzo2-2-dbg - Debug symbols for liblzo2-2
22:14.02FatPhilboth known to apt-cache
22:14.29DocScrutinizer05possibly a side effect of epoch fix?
22:15.06DocScrutinizer05I wouldn't even know why BM needs liblzo at all
22:15.24DocScrutinizer05ooohshit, depends from mtdtools
22:15.27DocScrutinizer05I see
22:15.43DocScrutinizer05weird
22:17.14DocScrutinizer05merlin1991: could you please have a look into that mess and fix it? simply move any package needed to the place where it's needed, if there's no more arcane reason like "can't install from Nokia repos" or sth
22:18.29DocScrutinizer05http://maemo.org/packages/package_instance/view/fremantle_nokia-applications_explicit_armel/liblzo2-2/2.03-1maemo3/
22:18.34DocScrutinizer05o.O
22:20.47DocScrutinizer05feels like never having heard of this repo
22:22.02DocScrutinizer05this whole repo management is a major PITA
22:22.54DocScrutinizer05seems this is no repo at all
22:23.16DocScrutinizer05rather the lib should ship with fiasco aiui
22:23.52DocScrutinizer05ohmy
22:24.23kerioi could check my n900
22:24.30keriobut my wifi isn't working, so i'd have to *walk* to it
22:24.41keriono wait i have bluetooth PAN working
22:25.26FatPhilmy old device has liblzo2-2 installed, weird
22:25.47DocScrutinizer05http://privatepaste.com/6d5426d171
22:26.40kerioit's in both dmnc repos
22:26.43kerioand in fremantle/tools
22:27.11DocScrutinizer05and dmnc has exoired-key issue?
22:27.20kerioirrelevant, for HAM
22:27.33DocScrutinizer05is it
22:27.35DocScrutinizer05?
22:27.40kerioit is
22:27.41kerioi think
22:27.41DocScrutinizer05also, no HAM used
22:27.43kerioi dunno
22:27.50kerioit's definetely not relevant for apt-get
22:27.54kerioand if it's not installed
22:27.56keriowait
22:27.59keriomh
22:28.02kerioi dunno lol
22:28.18DocScrutinizer05FFS
22:28.19kerioit might be considered a system package
22:28.23DocScrutinizer05yep
22:28.36kerioanyway, let's just get a more recent liblzo2-2 in extras
22:28.42keriostop depending on nokia
22:28.47DocScrutinizer05sure, hotfix
22:29.07DocScrutinizer05kill Nokia, with fire!
22:29.32DocScrutinizer05how stupid can you be letting your single pubkey expire?
22:29.45kerioeven worse
22:29.55kerionot using your current, working pubkey to resign a repo
22:29.59keriobecause of "reasons"
22:30.04DocScrutinizer05yeah
22:30.17kerioit's literally just two openssl commands
22:30.20DocScrutinizer05"reasons" is they don't find it
22:30.21kerioor possibly even just one
22:30.23jon_yso ballmer retiring soon, what would Nokia do?
22:30.31keriothat dude said that they did have it
22:30.38FatPhilship them an Elop
22:30.49jon_y:)
22:30.49DocScrutinizer05\o/
22:30.53FatPhilMS deserves an elop on top
22:30.56nox-hehe
22:31.16DocScrutinizer05uncle fester retires, gasoline pisser moves to redmond
22:31.24jon_yis it illegal to have the same CEO run 2 companies at the same time?
22:32.00DocScrutinizer05no
22:32.22DocScrutinizer05while they are no more two companies anyway
22:32.48DocScrutinizer05would just straighten things
22:33.03DocScrutinizer05MS-Nokia
22:33.10jon_yah, so dynastic personal unions are still possible in this modern age
22:33.58jon_ytotally will try to merge as MS-Nokia
22:34.03DocScrutinizer05FatPhil: get liblzo2 stuff via dpkg
22:34.09jon_ymore like absorbed
22:36.54DocScrutinizer05headdesks a little about http://talk.maemo.org/showthread.php?p=1369885#post1369885 and wanders off getting some old pizza and a decent drink
23:01.00*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
23:23.23FatPhilOK, now starting to apply patches to the nokia kernel from the community-ssu repo
23:23.33FatPhilwhy are there no commit messages?
23:37.54*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
23:41.43FatPhilOh noes! Joikusploit!
23:42.06freemangordonhmm?
23:42.39FatPhilI'm just applying the kernel-cssu patches to the nokia kernel
23:42.52keriowhy not the kernel-power ones?
23:42.57kerioalso, why not just use kernel-power?
23:43.31FatPhilbecause I was told to use the kernel-cssu ones!
23:43.41keriobut it's the exact same thing
23:43.45keriobut kernel-power has teh power
23:43.58freemangordonFatPhil: hold on, elaborate on what you're trying to do
23:44.25freemangordonFatPhil: also, what is kernel-cssu?
23:47.21FatPhilurl = git@gitorious.org:community-ssu/kernel-cssu.git
23:48.29freemangordonFatPhil: this is the kernel in cssu-thumb. I am the maintainer of cssu-thumb, just in case you're not aware. Now, what you're trying to do?
23:51.29FatPhiljust trying to get up to date. I've just got a couple of 2nd hand n900s, one of which will become my new daily device, the other of which will become a development device.
23:52.51FatPhilgrrr, the current kernel-power isn't a ffwd of the old http://atrey.karlin.mff.cuni.cz/~pali/kernel-power.git
23:52.54freemangordonFatPhil: oh, sorry
23:53.09freemangordonI just forgot that http://talk.maemo.org/showpost.php?p=1369526&postcount=75
23:53.26freemangordonFatPhil: welcome :)
23:53.58freemangordonFatPhil: well, kcssu as of now is KP
23:53.59FatPhilhowdy, looks like you've been working hard
23:54.12freemangordonI guess so :P
23:54.18freemangordonhowever
23:54.43FatPhilthough I don't understand the inclusion of some of those diffs in the kernel-cssu repo
23:54.54freemangordonI am also one of the KP maintainers
23:54.57FatPhilIn part because they don't have commit messages!
23:55.18freemangordonwell, some of them was done bask in 2011 for example
23:55.23freemangordonback*
23:55.48freemangordonthe guys are not a part of the community since then
23:56.11freemangordonFatPhil: check http://wiki.maemo.org/CSSU_kernel_assess
23:56.40freemangordonwe plan t include a krenel in the next CSSU based on that table
23:56.45freemangordon*to
23:57.40freemangordonsthe so-called kernel-cssu is what I use for a kernel in cssu-thumb, it is just KP51r1
23:58.26freemangordonther real kernel-cssu will be based in the above table. we want to have it because of the long-standing ppoll/pselect bug in kernel/glibc
23:58.47freemangordonif you are aware of it
23:59.21FatPhilI'm doing everything in git, so I can just create a new branch and add the kernel-power patches to that branch instead.
23:59.40freemangordonFatPhil: wait
23:59.50FatPhilI'm no fan of quilt, presuming these packages are for quilt
23:59.51freemangordonwhat are you trying to do?

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.