| 00:19.15 | *** join/#maemo infobot (ibot@rikers.org) |
| 00:19.15 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | 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 | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 01:30.01 | *** join/#maemo ginggs (~quassel@2a05:d018:c1e:8d00:c473:4128:ae2d:2c36) |
| 01:58.58 | *** join/#maemo pagurus (~user@p50837152.dip0.t-ipconnect.de) |
| 02:28.59 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 02:44.45 | *** join/#maemo pagurus (~user@p50837330.dip0.t-ipconnect.de) |
| 02:57.49 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 02:59.38 | *** join/#maemo vahe (~vahe@130.193.124.163) |
| 03:20.20 | *** join/#maemo Maxdaman1us (~Maxdamant@unaffiliated/maxdamantus) |
| 04:01.31 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 04:08.07 | *** join/#maemo platicus (~matrixirc@fanzine.igalia.com) |
| 04:44.00 | *** join/#maemo Funnyface (~user5330@56.92-220-152.customer.lyse.net) |
| 05:14.05 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:cdac:addf:8e32:cea1) |
| 05:21.05 | *** join/#maemo Funnyface (~user5330@56.92-220-152.customer.lyse.net) |
| 05:44.00 | *** join/#maemo arcean (~arcean@131.228.32.166) |
| 06:03.27 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 06:25.48 | *** join/#maemo dmth|intevation (~dmth|inte@2001:470:747a:2a:6af7:28ff:fe64:1ded) |
| 06:39.06 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 06:44.59 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 06:45.02 | *** join/#maemo platicus (~matrixirc@fanzine.igalia.com) |
| 06:51.01 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 07:34.46 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-kzfbzghexwqvagto) |
| 07:34.46 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 07:47.32 | *** join/#maemo platicus (~matrixirc@fanzine.igalia.com) |
| 08:15.58 | *** join/#maemo eMHa__ (~mh@HSI-KBW-46-237-200-175.hsi.kabel-badenwuerttemberg.de) |
| 08:25.29 | *** join/#maemo xorly (~xorly@147.32.218.143) |
| 08:26.01 | *** join/#maemo N-Mi (~nicolas@37.160.79.233) |
| 08:26.01 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 08:35.10 | Wizzup | is openmediaplayer not yet in the normal repos? |
| 08:36.53 | sixwheeledbeast | #define normal |
| 09:01.30 | *** join/#maemo drawkula (~username@p4FDDA325.dip0.t-ipconnect.de) |
| 09:22.17 | *** join/#maemo Kabouik (~kabouik@158.38.1.70) |
| 09:33.47 | Wizzup | Something I can install from the normal package manager |
| 09:33.52 | Wizzup | e.g. stuck in dev repo |
| 09:35.29 | DocScrutinizer05 | http://maemo.org/packages/view/openmediaplayer/ nobody promoting it |
| 09:35.42 | sixwheeledbeast | it should be in extras-devel |
| 09:36.01 | sixwheeledbeast | oh hi |
| 09:36.38 | KotCzarny | might be because they got fed up with -devel/-testing/extras cycle? |
| 09:37.09 | KotCzarny | or dont know how to do it |
| 09:38.31 | KotCzarny | Random Question |
| 09:38.35 | KotCzarny | What is the last Maemo release's name? |
| 09:38.38 | KotCzarny | i dont know?! |
| 09:38.39 | DocScrutinizer05 | Wizzup: pester the developer to promote package |
| 09:38.46 | KotCzarny | is it fremantle? or harmattan? |
| 09:39.06 | KotCzarny | those anti bots questions are actually anti users too ;) |
| 09:39.49 | sixwheeledbeast | it has never been promoted as it was never finished. I don't know if gidzzz has finished working on it to a stable state yet |
| 09:39.51 | KotCzarny | definitely t.m.o didnt accept 'fremantle' as an answer |
| 09:40.27 | sixwheeledbeast | Diablo? |
| 09:40.37 | sixwheeledbeast | maybe it's old question |
| 09:40.37 | DocScrutinizer05 | huh? |
| 09:41.18 | KotCzarny | but at least i got 'answer to the universe and everything' right |
| 09:41.46 | KotCzarny | definitely requires some inside knowledge when trying to do t.m.o search ;) |
| 09:42.24 | sixwheeledbeast | maybe just login to avoid the question |
| 09:42.24 | KotCzarny | Last Activity: 2016-11-13 16:48 |
| 09:42.36 | KotCzarny | uh, gidzzz seems has left the building |
| 09:43.44 | KotCzarny | Latest commit 4d51170 on Nov 13, 2016 |
| 09:44.08 | sixwheeledbeast | oh and the answer is Harmattan |
| 09:44.29 | sixwheeledbeast | well it thinks the answer is anyway |
| 09:44.53 | KotCzarny | it's debatable if harmattan is maemo |
| 09:45.00 | sixwheeledbeast | exactly |
| 09:52.29 | KotCzarny | yup, you will have to wait for thebug, he has that board and is the only one that can confirm |
| 09:52.44 | KotCzarny | he lives in different time zone |
| 09:54.45 | KotCzarny | oops. wrong chan |
| 10:05.52 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 10:08.46 | *** join/#maemo vahe (~vahe@130.193.124.163) |
| 10:14.32 | *** join/#maemo cyphase (~cyphase@unaffiliated/cyphase) |
| 10:21.27 | *** join/#maemo Maxdaman1us (~Maxdamant@unaffiliated/maxdamantus) |
| 10:57.49 | sicelo | at least getting packages to -testing is easy . . . i don't see why anyone would be fed up with that |
| 11:02.27 | KotCzarny | because it breaks development trance? |
| 11:02.49 | KotCzarny | ie. you have to switch from cozy text to browser and click things |
| 11:10.33 | DocScrutinizer05 | sicelo: nobody is fed up with promoting. It's devels simply giving a flying F* about which repo their package is in. Or basically about packaging at all, generally |
| 11:11.34 | DocScrutinizer05 | seems most devels and users don't even understand the idea of maemo-testing, mistaking it as a sympathy contest |
| 11:12.47 | DocScrutinizer05 | it's maemo.testing, NOT maemo-most-popular |
| 11:13.33 | DocScrutinizer05 | testinf comments like "I love it, 1 thunb up from me" should get their account closed |
| 11:13.33 | sixwheeledbeast | It doesn't help the amount of package testers tho and the time it takes to test a package |
| 11:14.08 | DocScrutinizer05 | sixwheeledbeast: indeed |
| 11:14.27 | DocScrutinizer05 | testers are a rare species, and that's a real problem |
| 11:14.45 | KotCzarny | and killing users is not gonna help neither |
| 11:15.06 | KotCzarny | some people like the idea of dead repos being dead. but tidy as hell |
| 11:15.53 | DocScrutinizer05 | I still have that pet project idea to wrap ALL apps in maemo-testing into a runtime test wrapper that opens a "nag screen" on closing the app. That nag screen collects mem usage etc values automatically and appends a comment form user to make an automated email to the testing infra |
| 11:16.20 | sixwheeledbeast | I dont have the time I had to spend testing various packages like i did. |
| 11:17.06 | sixwheeledbeast | automatic testing of root and opt memory would reduce the testing time greatly |
| 11:17.20 | DocScrutinizer05 | I occasionally do testing, but very raely and not many packages are new in testing. The ones still lingering there are not the ones I feel like giving them a test |
| 11:17.33 | sixwheeledbeast | :nod: |
| 11:17.50 | DocScrutinizer05 | yep, that's the idea: automate the usual leak and hog test |
| 11:18.47 | DocScrutinizer05 | should be rather simple to do to wrap such thing around $arbitrary-testing-app-pkg |
| 11:19.26 | sixwheeledbeast | a large number of new users will be unaware of the QA procedure anyway. #speedpatch |
| 11:19.37 | DocScrutinizer05 | ROTFL |
| 11:19.43 | DocScrutinizer05 | ~jrtools |
| 11:19.43 | infobot | methinks jrtools is http://wiki.maemo.org/User:Joerg_rw/tools |
| 11:20.24 | DocScrutinizer05 | http://wiki.maemo.org/User:Joerg_rw/tools#AFTER_FLASHING |
| 11:21.50 | DocScrutinizer05 | needs a "maemo fremantle for newcomers, 2017 edition" |
| 11:23.03 | DocScrutinizer05 | starting with the very basics like "maemo is very much _like_ debian, but it IS NOT debian. For example the packaging (and thus proecedures you're possibly used to, like apt-get dist-upgrade) fail epically on maemo" |
| 11:26.25 | sixwheeledbeast | "WAS" very much like Debian? |
| 11:26.27 | DocScrutinizer05 | just throwing a new sources.list at noobs doesn't help them to understanf how repos *really* work, regarding maemo-devel|testing|extras, tools, whatnot |
| 11:26.36 | DocScrutinizer05 | indeed LOL |
| 11:26.59 | DocScrutinizer05 | nice place to have a short exursion to Devuan |
| 11:27.10 | DocScrutinizer05 | and how maemo debian and devuan relate |
| 11:27.25 | Wizzup | welp, I guess I can't ask a question without a non-constructive debate following |
| 11:28.09 | DocScrutinizer05 | when you think this debate is non-constructive then readjust your filters and attitude |
| 11:28.17 | sixwheeledbeast | sudo givemeworkingmaemopackages |
| 11:30.24 | DocScrutinizer05 | one thing's for sure: calling this discussion non-constructive for sure doesn'T qualify as a constructive contribution |
| 11:35.03 | *** join/#maemo cyteen (~cyteen@cpc83573-brig19-2-0-cust508.3-3.cable.virginm.net) |
| 11:35.46 | DocScrutinizer05 | hmmmm, zzztop lacks a feature: should have `zzztop -t=0` which collects data infinitely until zzztop gets a ^C or other signal that stops it, then dumps the results |
| 11:36.35 | DocScrutinizer05 | as you might have guessed, that would be useful for the above mentioned testing wrapper |
| 11:37.45 | *** join/#maemo tx-tmp (~tx@public.ams0.true.nl) |
| 11:38.43 | tx-tmp | I'm having an odd issue where my N900 refuses to boot after reflashing. When I boot it the white LED fades on yet it doesn't "vibrate" and show anything on screen. From there on nothing happens and I have to remove the battery to boot again. |
| 11:38.53 | tx-tmp | Anyone that might have a clue on what to try next? |
| 11:39.16 | tx-tmp | I reflashed eMMC/FIASCO. |
| 11:39.22 | tx-tmp | To no avail. ;_; |
| 11:39.29 | DocScrutinizer05 | did you use lazyflashing? |
| 11:40.17 | DocScrutinizer05 | sounds like an issue with bootloader |
| 11:41.21 | DocScrutinizer05 | if youlike, I can talk you through a series of tests |
| 11:41.43 | DocScrutinizer05 | prerequisites: you're using a linux PC |
| 11:41.55 | tx-tmp | Lazyflashing? You mean the .sh from the Wiki? I assumed bootloader issues as well, but cold flashing does not seem to be needed (I tried it anyhow; didn't help). |
| 11:41.59 | tx-tmp | Yes, I'm on Linux. |
| 11:42.07 | tx-tmp | Would be very much appreciated. |
| 11:42.10 | DocScrutinizer05 | ~lazyflashing |
| 11:42.10 | infobot | from memory, lazyflashing is http://wiki.maemo.org/Updating_the_tablet_firmware#The_Lazy_Approach |
| 11:42.16 | tx-tmp | Didn't try. |
| 11:42.28 | tx-tmp | Just used the .deb flasher by hand. |
| 11:42.40 | DocScrutinizer05 | please try this first, it's the most siple and secure way to do flashing right |
| 11:42.55 | tx-tmp | I will! Thank you. |
| 11:43.08 | DocScrutinizer05 | yw :-) please report back here |
| 11:44.05 | DocScrutinizer05 | should try to move lazyflashing to maemo infra, just in case his server goes south some time |
| 11:46.06 | DocScrutinizer05 | ouch >>cold flashing does not seem to be needed (I tried it anyhow<< this _might_ have had an opposite effect |
| 11:47.30 | sixwheeledbeast | you can zzztop -t=999999999 it? |
| 11:47.48 | DocScrutinizer05 | tx-tmp: first thing to do: check your linux PC /var/log/syslog or /var/log/messages (or dmesg, worst case) for logs of powered down N900 getting connected to PC via USB |
| 11:48.16 | DocScrutinizer05 | sixwheeledbeast: yes, but I guess it won't dump statistics when you abort it, right? |
| 11:48.47 | sixwheeledbeast | oic |
| 11:50.09 | sixwheeledbeast | powertop is the same? I suppose it needs to calculate values over a set period of time |
| 11:51.02 | DocScrutinizer05 | http://paste.ubuntu.com/24560254 |
| 11:51.06 | DocScrutinizer05 | yep, same |
| 11:51.22 | tx-tmp | It does show up in the systemlog, yes, and I didn't overwrite the bootloader (no worries there)! |
| 11:51.25 | tx-tmp | Anyhow, I tried lazyflashing |
| 11:51.27 | *** join/#maemo Sigyn (sigyn@freenode/utility-bot/sigyn) |
| 11:51.41 | tx-tmp | Final step is "please remove battery, unplug USB, then reinsert battery and let device boot and init system which may take a while" - after which it still boots in the same way as before. :( |
| 11:51.57 | DocScrutinizer05 | damn, zzztop is perl |
| 11:52.01 | tx-tmp | It worked yesterday, by the way. Left it to charge overnight and it died. |
| 11:52.13 | tx-tmp | Might be relevant, or might not be, but I tried to save a video file which corrupted yesterday. |
| 11:52.52 | DocScrutinizer05 | ~flatbatrecover |
| 11:52.53 | infobot | Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber shut off -> start over again with ~flatbatrecover while already searching for a new battery. CAVEAT! Only works when ~rootfs OK (no ~bootloop) |
| 11:52.53 | tx-tmp | The weird thing is that the battery is full, and booting it in "charge mode" still seems to charge. |
| 11:53.01 | DocScrutinizer05 | ~bootloop |
| 11:53.01 | infobot | rumour has it, bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device. |
| 11:53.47 | DocScrutinizer05 | ((final step)) please provide full session log pastebin |
| 11:53.51 | *** join/#maemo arcean (~arcean@131.228.32.166) |
| 11:53.55 | tx-tmp | @flatbat: Battery light is steady green. After leaving it on for a bit it does turn into a flashing amber light. (Odd sidenote: it turned into a green flashing light for a bit, too.) |
| 11:54.11 | DocScrutinizer05 | lazyflashing shouldn't make "device boot as usualy" |
| 11:54.16 | sixwheeledbeast | I thought you knew it was perl? |
| 11:54.23 | sixwheeledbeast | ~zzztop |
| 11:54.23 | infobot | zzztop is, like, - the better and even FOSS powertop - http://wiki.maemo.org/Zzztop |
| 11:54.44 | DocScrutinizer05 | yes |
| 11:54.46 | sixwheeledbeast | fatphil is the one to ask |
| 11:54.48 | tx-tmp | And it doesn't bootloop. Looks more like a freeze/panic. I have to pull the battery out before it can attempt to boot again (white LED fading on). |
| 11:55.03 | DocScrutinizer05 | I thought it was perl, but I realized I have no idea how to patch perl ;-) |
| 11:55.10 | DocScrutinizer05 | to get a trap in |
| 11:55.54 | DocScrutinizer05 | (fatphil) I know :-) |
| 11:56.19 | DocScrutinizer05 | but I guess I can learn as much perl as needed for such simple patch |
| 11:58.00 | DocScrutinizer05 | tx-tmp: please compare http://wiki.maemo.org/User:Joerg_rw/PC_syslog_of_USB_enum |
| 12:01.10 | DocScrutinizer05 | if those 3 stages are OK for your device, your bootloader should be OK and a lazyflashing should fix your issue |
| 12:02.06 | DocScrutinizer05 | if 3rd stage (maemo, idProduct=01c7) doesn't show, your bootloader still is OK and same as above applies |
| 12:02.57 | DocScrutinizer05 | if stage 2 (idProduct=0105) doesn't show, you need coldflashing |
| 12:04.30 | DocScrutinizer05 | next test: hold 'u' key while plugging in powered-down device to USB, check if NOKIA screen with USB icon comes up |
| 12:04.46 | DocScrutinizer05 | if not, your battery is probably empty |
| 12:06.28 | DocScrutinizer05 | green idicator light however is quite "strange" since it is a feature of maemo system already booted iirc. Shouldn't get set by NOLO nor hardware |
| 12:06.49 | DocScrutinizer05 | please allow 60s for booting |
| 12:06.54 | DocScrutinizer05 | minimum |
| 12:07.21 | DocScrutinizer05 | after flashing, a few minutes with black screen are ok until system firstboot finished |
| 12:07.46 | DocScrutinizer05 | it's all in comments printed by lazyflashing ;-) |
| 12:09.33 | DocScrutinizer05 | on low battery NOLO tries to directly boot into maemo system to charge battery, which is a very braindamaged thing to do when system is defect and needs reflash |
| 12:09.37 | DocScrutinizer05 | see |
| 12:09.40 | DocScrutinizer05 | ~bootloop |
| 12:09.40 | infobot | methinks bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device. |
| 12:10.41 | DocScrutinizer05 | bbl, busy |
| 12:16.08 | tx-tmp | https://ybin.me/p/a7ae44c55bfeb1d6#+ByyYq+Tg5YURtuAkgfb62VB5+4BlLWfHEyrYssgm6s= Looks fine to me. Reaches stage 3. |
| 12:18.29 | DocScrutinizer05 | sixwheeledbeast: first googlehit: http://perltricks.com/article/37/2013/8/18/Catch-and-Handle-Signals-in-Perl/ |
| 12:18.47 | DocScrutinizer05 | tx-tmp: yes |
| 12:19.06 | DocScrutinizer05 | try lazyflashing, follow the instructions verbatim |
| 12:19.32 | DocScrutinizer05 | don't assume, don't connect device without being istructed to do so |
| 12:24.22 | DocScrutinizer05 | here's a browsable version of the script: http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir_v2/flash-it-all.sh |
| 12:29.01 | DocScrutinizer05 | (([2017-05-12 Fri 13:51:40] <tx-tmp> Final step is "please remove battery, unplug USB, then reinsert battery and let device boot and init system which may take a while" - after which it still boots in the same way as before. )) "A while" here means several minutes |
| 12:29.55 | DocScrutinizer05 | did you answer "YES" (three chars UpperCase) to the question? |
| 12:30.39 | APic | lol |
| 12:36.12 | DocScrutinizer05 | tx-tmp: ooh, and for good measure, remove SIM and uSD |
| 12:37.05 | tx-tmp | Sorry, incomplete response, got a phone call from work so I was afk for a bit. |
| 12:37.17 | DocScrutinizer05 | uSD might have filesystems that impair the boot process when they are e.g. unknown or need fsck. SIM known to make boot process block in very rare cases |
| 12:37.40 | tx-tmp | I did lazyflash exactly according to instructions, sadly, the problem remains the same (as before flashing). |
| 12:37.47 | tx-tmp | I did answer YES and SIM/SD are removed. |
| 12:38.21 | KotCzarny | maybe you should log whole flashing session and pastebin it? |
| 12:39.01 | tx-tmp | It's just a normal flashing session, output is exactly as one would expect when looking at the .sh and assuming a non-faulty device. :) |
| 12:39.23 | tx-tmp | The odd thing is that the screen doesn't turn on and it doesn't give the classical vibration/jolt upon boot. |
| 12:39.30 | tx-tmp | It's as if it gets stuck before that part... |
| 12:39.38 | KotCzarny | do you have spare battery? |
| 12:39.47 | *** join/#maemo sunshavi (~user@190.234.106.64) |
| 12:39.53 | tx-tmp | I will try a different battery, I think I have a spare one at home. |
| 12:40.15 | tx-tmp | Wouldn't be surprised if it's a battery issue. It's been showing up as being 0% full in the OS even when it was actually charged... |
| 12:40.20 | tx-tmp | Ancient little battery. |
| 12:40.57 | tx-tmp | Also, thanks for all the help Doc, very much appreciate it. |
| 12:41.05 | KotCzarny | mine is 8 years old, still using it ;) |
| 12:41.23 | *** join/#maemo sledges (~sleleiva@unaffiliated/sledgeas) |
| 12:42.44 | *** join/#maemo mavhc (~mavhc@cpc77319-basf12-2-0-cust433.12-3.cable.virginm.net) |
| 12:42.53 | tx-tmp | Same! |
| 12:43.22 | KotCzarny | but it's charged, ie taken from working device? |
| 12:43.23 | DocScrutinizer05 | tx-tmp: please test the hold-Ukey thing |
| 12:43.43 | tx-tmp | Yeah, this battery works the N900 of a friend. |
| 12:43.44 | tx-tmp | Will do. |
| 12:44.41 | DocScrutinizer05 | if your NOLO doesn't show the NOKIA screen (without, then with backlight on), yur display is defect |
| 12:44.51 | DocScrutinizer05 | of NOLO is defect |
| 12:44.54 | DocScrutinizer05 | or* |
| 12:44.55 | *** join/#maemo spiiroin (~spiiroin@188-67-78-173.bb.dnainternet.fi) |
| 12:45.06 | *** join/#maemo oniongarlic (~milang@195.16.220.82) |
| 12:45.21 | tx-tmp | No screen is shown whatsoever. |
| 12:45.33 | tx-tmp | I would accept the screen being broken, but it bugs me that the boot-vibration is also missing. |
| 12:45.38 | tx-tmp | Which is a different piece of HW. |
| 12:45.38 | KotCzarny | broken display shouldnt affect lack of vibra on powerup |
| 12:46.26 | DocScrutinizer05 | NOLO behaves strange when display not connected |
| 12:47.03 | DocScrutinizer05 | when NOLO can't initialize the display controller, it will not kick vibra afaik |
| 12:47.16 | tx-tmp | Mhm, interesting. Might actually be that the display died in that case. |
| 12:47.34 | DocScrutinizer05 | usually cable |
| 12:47.37 | KotCzarny | swapping display part is 5 minutes of work |
| 12:47.38 | DocScrutinizer05 | ~flexcable |
| 12:47.42 | DocScrutinizer05 | ~flex |
| 12:47.42 | infobot | i guess flex is a sucky nick used by freaks, or flex is also the Fast Lexical analyzer generator. A Lex compatible scanner generator. |
| 12:47.55 | DocScrutinizer05 | ~uselss |
| 12:48.22 | DocScrutinizer05 | ~listvalues flex*cable |
| 12:48.32 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 12:48.40 | KotCzarny | ~fract-o-rama |
| 12:48.40 | infobot | Qt-based, flexible fractal generation program. URL: http://locutus.kingwoodcable.com/jfd/fractal/ |
| 12:48.45 | DocScrutinizer05 | ~listvalues flat*cable |
| 12:48.48 | KotCzarny | cute |
| 12:49.47 | DocScrutinizer05 | ~fpc |
| 12:51.29 | DocScrutinizer05 | ~listvalues maemo*cable |
| 12:51.47 | DocScrutinizer05 | ~listvalues cale*maemo |
| 12:51.52 | DocScrutinizer05 | ~listvalues cable*maemo |
| 12:51.58 | DocScrutinizer05 | no idea |
| 12:52.06 | DocScrutinizer05 | seach in tmo |
| 12:53.02 | DocScrutinizer05 | usually the flat plastic connector cable from display slide to mainboard, particularly the B2B conn 'plug' at end, which breaks |
| 12:54.14 | tx-tmp | I'll try fixing that one, yeah. |
| 12:54.21 | tx-tmp | It was about time to buy a spare N900 anyway... |
| 12:56.36 | DocScrutinizer05 | https://www.aliexpress.com/item/BRAND-NEW-CAMERA-FLAT-MAIN-FLEX-CABLE-RIBBON-FOR-NOKIA-N900-C57R/32262531025.html?spm=2114.40010208.4.56.xrEOVs |
| 13:08.59 | sixwheeledbeast | ~fixribbon |
| 13:08.59 | infobot | [fixribbon] http://talk.maemo.org/showthread.php?p=1324171#post1324171 |
| 13:09.03 | sixwheeledbeast | ? |
| 13:09.25 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 13:09.30 | *** join/#maemo N-Mi (~nicolas@adsl.n-mi.com) |
| 13:09.30 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 13:12.06 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 13:19.23 | tx-tmp | Thanks. :) |
| 13:33.47 | *** join/#maemo sunshavi (~user@190.234.106.64) |
| 13:56.39 | kerio | my mobile operator now has free national roaming for data ;o |
| 13:56.44 | kerio | all the 2G irc |
| 13:58.49 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 13:59.37 | kerio | i have like barely any reason not to leave xchat open in perpetuity i guess |
| 14:01.21 | KotCzarny | two words: battery drain ? |
| 14:03.42 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 14:03.49 | *** join/#maemo xy2_ (~xy2_@172.245.16.93.rev.sfr.net) |
| 14:03.51 | kerio | it's gprs tho |
| 14:04.20 | KotCzarny | see? battery drain |
| 14:05.14 | deepy | KotCzarny: compared to what? |
| 14:05.55 | KotCzarny | 3g |
| 14:05.59 | KotCzarny | and up |
| 14:06.16 | deepy | Are you saying the battery drain on gprs is greater than on 3g? |
| 14:06.27 | KotCzarny | yup, 2g time slots are big |
| 14:06.28 | Wizzup | with a passive conn? |
| 14:06.38 | Wizzup | or if you're using it actively |
| 14:07.27 | deepy | Actually, I can't argue this becuase I don't remember if I'm remembering the drain with or without HSPA :E |
| 14:09.03 | KotCzarny | also, being slower, it requires long transmit events |
| 14:10.32 | KotCzarny | https://android.stackexchange.com/questions/44628/2g-versus-3g-does-it-really-save-battery |
| 14:10.37 | bencoh | KotCzarny: actually, no, definitely not (regarding gprs vs umts) |
| 14:10.44 | KotCzarny | funny numbers in 'data only' scenario |
| 14:11.58 | KotCzarny | and remember that with tcp there is much less idling when there is some connection going on |
| 14:12.07 | KotCzarny | as every packet requires answer |
| 14:12.29 | ShadowJK | The "lots of very small but frequent data transfers" category is missing from that link :) |
| 14:12.39 | KotCzarny | and i assume kerio sits on many channels |
| 14:46.07 | *** join/#maemo stryngs (~stryngs@unaffiliated/stryngs) |
| 15:21.37 | *** join/#maemo RzR (~RzR@unaffiliated/rzr) |
| 15:28.51 | *** join/#maemo vahe (~vahe@130.193.124.163) |
| 15:57.47 | *** join/#maemo TheKit (~nekit@178.45.144.138) |
| 16:00.23 | *** join/#maemo eMHa__ (~mh@p200300738E174F00267703FFFE6CC360.dip0.t-ipconnect.de) |
| 16:27.09 | *** join/#maemo Kabouik_ (~kabouik@158.38.1.70) |
| 16:58.40 | DocScrutinizer05 | ~#maemo flexcable is <reply>see fixribbon |
| 16:58.40 | infobot | DocScrutinizer05: okay |
| 16:58.46 | DocScrutinizer05 | ~flexcable |
| 16:58.46 | infobot | well, fixribbon is http://talk.maemo.org/showthread.php?p=1324171#post1324171 |
| 17:00.01 | DocScrutinizer05 | kerio: national roaming?? |
| 17:00.12 | kerio | my operator is 3G-only |
| 17:00.16 | kerio | well, with some 4G |
| 17:00.31 | kerio | so it offered roaming on the 2G operator for a while |
| 17:00.39 | kerio | but data was not included |
| 17:00.40 | DocScrutinizer05 | we got that since... A-band here, and I have xchat open 25/7/365 |
| 17:01.53 | DocScrutinizer05 | we had like 4 primary operators, recently O2 bought out E-plus |
| 17:02.11 | DocScrutinizer05 | so now O2, Vodafone, Telekom |
| 17:02.28 | DocScrutinizer05 | everything else are minute resellers |
| 17:03.29 | DocScrutinizer05 | in the early days O2 (E1 band) used roaming on Telekom's D1 band in areas where they had no own coverage |
| 17:03.37 | DocScrutinizer05 | via Swisscom ;-P |
| 17:04.07 | DocScrutinizer05 | now all three providers are nationwide coverage |
| 17:04.36 | DocScrutinizer05 | some minute resellers offer roaming between 2 or 3 of the providers |
| 17:05.22 | DocScrutinizer05 | all 3 providers now use D and E bands as well as other (harmonized, so far) bands for UMTS |
| 17:06.37 | DocScrutinizer05 | compare that to 3rd world telecom nations like USA where you need roaming to go from east LA to west LA |
| 17:08.41 | DocScrutinizer05 | and in 4 weeks an EU-wide regulation forbids roaming primium charge in whole EU |
| 17:09.42 | DocScrutinizer05 | so we have free roaming from Norway(?) to Ceuta (Spain, on Afrika) |
| 17:10.17 | DocScrutinizer05 | byebye "Great" Britain |
| 17:18.14 | *** join/#maemo APic (apic@apic.name) |
| 17:21.20 | DocScrutinizer05 | ooh, and all 3 providers provide all RATs from 2G to LTE |
| 17:21.46 | *** join/#maemo xy2_ (~xy2_@172.245.16.93.rev.sfr.net) |
| 17:21.47 | DocScrutinizer05 | they differ slightly in LTE max speed |
| 17:26.15 | Enrico_Menotti | Hello. I'd like to ask a few general things about Maemo architecture, and operating systems in general. Although I have Devuan booting on the N900, and now also X and gtk+ on top of it, I'm not sure I refer to all the OS components with their (strictly) correct names. Up to now I decided to follow a quite heuristic approach to OS's, in order to grab immediately a practical flavour of theoretical concepts. Now I got |
| 17:26.15 | Enrico_Menotti | <PROTECTED> |
| 17:29.03 | KotCzarny | ~ask |
| 17:29.03 | 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. |
| 17:29.56 | Enrico_Menotti | So first, a general question about OS architecture, in general. As I have been learning in the last few weeks, an OS is composed fundamentally by a kernel and a file system (possibly with an initial ram disk), and on top of that one may have a stack for running a desktop environment. Right? |
| 17:30.09 | Enrico_Menotti | KotCzarny (A minute, I'm asking.) |
| 17:33.11 | Enrico_Menotti | Now in common language I'm used to hear talking about "Linux" as an OS, with all its possible flavours (such as Debian, Devuan, Ubuntu, etc.). But if I got it right, strictly speaking the name "Linux" only defines the kernel, while the OS includes the file system as well. So this is the first point I'd like to be sure of. |
| 17:35.04 | Enrico_Menotti | The second is about the term "Operating System": if I got it right, as stated above, it comprises *both* kernel and file system, but what about the desktop environment? Should it be considered part of the OS? |
| 17:37.33 | Enrico_Menotti | And now about Maemo specifically: the kernel is Linux (patched?), the file system is derived from Debian's, and the desktop environment runs on top of gtk+ (modded for Maemo). Is this right? |
| 17:37.54 | DocScrutinizer05 | the correct name is usually GNU/Linux which is kernel, filesystem and userland basic system services |
| 17:39.08 | DocScrutinizer05 | usually you consider the OS being kernel, filesystem drivers, and all the basic userland tools and processes/daemons/services |
| 17:39.52 | DocScrutinizer05 | OS (and several, but not all, available filesystems) are linux, while the userland stuff is GNU |
| 17:40.19 | DocScrutinizer05 | unless it isn't, e.g upstart or systemd prolly isn't GNU |
| 17:40.51 | DocScrutinizer05 | ~gnu |
| 17:40.52 | infobot | gnu is, like, an animal having a drooping beard. And it's also an antelope. |
| 17:40.59 | DocScrutinizer05 | MEH! |
| 17:41.04 | Enrico_Menotti | :D |
| 17:41.08 | DocScrutinizer05 | ~wiki GNU |
| 17:44.08 | DocScrutinizer05 | and no, a desktop isn't usually considered a tightly OS-related component |
| 17:44.56 | DocScrutinizer05 | though some DEs only run on a particular OS, many are pretty OS-agnostic, I think KDE even runs on windows ;-D |
| 17:46.03 | DocScrutinizer05 | Apple's OS is not linux (and even less GNU), but it's still a unix of sorts, and stuff like KDE and GNU tools work on OS-X |
| 17:47.33 | Enrico_Menotti | Ok, so fundamentally OS = kernel + filesystem management + services, right? |
| 17:48.13 | DocScrutinizer05 | there's one common denominator nowadays and that's POSIX which defines systemcalls that are identical on all POSIX compliant systems, no matter if GNU/linux or GNU/hurd or *BSD or OS-X or windows |
| 17:48.26 | DocScrutinizer05 | yes, that's quite right |
| 17:49.02 | DocScrutinizer05 | https://en.wikipedia.org/wiki/Operating_system |
| 17:52.46 | DocScrutinizer05 | *usually* you get a OS bundled with a wealth of userland applications made to run on that OS |
| 17:53.33 | Enrico_Menotti | Ok, now about "Linux". Is it just the kernel? Or also the filesystem management? And services are excluded from the "Linux" definition, being referred to as "GNU"? |
| 17:53.42 | DocScrutinizer05 | so many people refer to both the OS and the apps when they talk about their (operating) System |
| 17:53.58 | *** join/#maemo at1as (~at1as@24-231-230-53.static.trcy.mi.charter.com) |
| 17:54.11 | DocScrutinizer05 | that's a tough question, see above |
| 17:54.44 | DocScrutinizer05 | also see https://en.wikipedia.org/wiki/GNU/Linux_naming_controversy |
| 17:55.41 | Enrico_Menotti | Ah so that's not well defined, right? (I read both things here and there over the web.) |
| 17:57.45 | Enrico_Menotti | In the last link you posted, e.g., they talk about "Linux kernel". |
| 17:57.45 | DocScrutinizer05 | yes |
| 17:58.11 | DocScrutinizer05 | for shits & giggles, read about https://en.wikipedia.org/wiki/GNU_Hurd |
| 17:58.59 | DocScrutinizer05 | running gag: is Hurd already released? |
| 18:00.39 | Enrico_Menotti | Ok so it's not just me having no clear ideas. Nice to hear. :) |
| 18:01.51 | Enrico_Menotti | About Maemo: the kernel is Linux (patched?), the file system is derived from Debian's, and the desktop environment runs on top of gtk+ (modded for Maemo). Is this right? |
| 18:03.19 | DocScrutinizer05 | the kernel of maemo is pretty much a plain upstream linux kernel, though Nokia added a few device drivers that were not (initially) upstreamed and thus considered Nokia-specific (though thery are FOSS) by some |
| 18:03.37 | DocScrutinizer05 | the file systems are plain upstream |
| 18:03.50 | DocScrutinizer05 | the file system drivers that is |
| 18:04.08 | DocScrutinizer05 | often people call a disk image a "filesystem" |
| 18:05.16 | DocScrutinizer05 | the desktop environment is Hildon which is based on a X11 flavor called matchbox iirc, with a window manager/desktop manager developed by Nokia on top |
| 18:05.59 | *** join/#maemo Kabouik (~quassel@32.232.202.84.customer.cdi.no) |
| 18:06.03 | DocScrutinizer05 | (the latter would be hildon-desktop, hildon-home, etc) |
| 18:06.14 | DocScrutinizer05 | matchbox is upstream |
| 18:07.20 | DocScrutinizer05 | and yes, hildon uses gtk2+ modified for the usecase |
| 18:09.27 | DocScrutinizer05 | the major problem with the kernel is: Maemo has some userland libs that are basically closed source replacement for proper lernel drivers. Particularly for the OMAP3 Graphics engine PowerVR |
| 18:09.57 | DocScrutinizer05 | s/lernel/kernel/ |
| 18:10.49 | DocScrutinizer05 | another huge part is the stack of libs and daemons that talks to the modem |
| 18:11.26 | DocScrutinizer05 | a thitd is the stuff related to the OMAP DSP |
| 18:11.32 | DocScrutinizer05 | third* |
| 18:11.49 | Enrico_Menotti | Digital Signal Processor? |
| 18:11.52 | DocScrutinizer05 | yep |
| 18:11.57 | Enrico_Menotti | Ok. |
| 18:12.19 | Enrico_Menotti | The part for the modem, is that open source or not? |
| 18:12.26 | DocScrutinizer05 | nope, closed |
| 18:12.31 | Enrico_Menotti | :( |
| 18:12.34 | DocScrutinizer05 | yes |
| 18:13.05 | Enrico_Menotti | So up to now the only OS which is able to use the N900 as a cell phone is Maemo? |
| 18:13.18 | DocScrutinizer05 | there are replacements like ofono but they are not plug-in replacement for the existing stuff, they have different concept and API |
| 18:13.23 | Wizzup | Enrico_Menotti: no |
| 18:13.31 | Wizzup | some people have been able to make calls |
| 18:13.34 | Wizzup | albeit crappy quality |
| 18:15.29 | DocScrutinizer05 | useful: http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/System_Software http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Top_Level_Architecture |
| 18:16.35 | Enrico_Menotti | Ok, thank you for the *very* useful info. Nice talk. Now I have to go - I will ask some more in the next few days, although I will be a bit busy with Special Relativity :) . |
| 18:16.41 | DocScrutinizer05 | http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Multimedia_Domain |
| 18:17.59 | Enrico_Menotti | Great diagrams, btw. I had already seen something, but did not read carefully, I admit. |
| 18:26.44 | DocScrutinizer05 | Special Relativity is simpler than maemo ;-P |
| 18:36.00 | *** join/#maemo eMHa__ (~mh@p54B0F309.dip0.t-ipconnect.de) |
| 18:37.01 | *** join/#maemo shentey (~shentey@x55b23000.dyn.telefonica.de) |
| 19:12.58 | *** join/#maemo Vajb (~Vajb@85-76-115-58-nat.elisa-mobile.fi) |
| 19:33.43 | *** join/#maemo ecloud (quassel@nat/qt/x-jgwpwtuhblmbflkw) |
| 19:36.55 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 19:57.47 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 20:28.37 | *** join/#maemo eMHa__ (~mh@p200300738E289000267703FFFE6CC360.dip0.t-ipconnect.de) |
| 20:31.34 | *** join/#maemo florian (~fuchs@x4d094c76.dyn.telefonica.de) |
| 20:32.59 | *** join/#maemo xy2_ (~xy2_@mlv95-h01-176-134-46-233.dsl.sta.abo.bbox.fr) |
| 20:59.25 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 21:21.07 | *** join/#maemo eMHa__ (~mh@p200300738E289000267703FFFE6CC360.dip0.t-ipconnect.de) |
| 22:32.21 | *** join/#maemo geaaru (~geaaru@host88-154-dynamic.54-82-r.retail.telecomitalia.it) |