| 00:41.14 | *** join/#maemo fortytwo (~thomas@who.let.this.bloody.dropbear.in) |
| 01:03.14 | *** join/#maemo eMHa (~mh@p54B0FE7F.dip0.t-ipconnect.de) |
| 01:03.45 | *** join/#maemo Humpelstilzchen (erik@x4e366ad6.dyn.telefonica.de) |
| 01:18.18 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 02:03.49 | Linkandzelda | DocScrutinizer05: was able to fix the issue with /bin/dd vs the gnu path version with ssh login to user and root as well as xterm login. i added "source ~/.bashrc" into .profile for /home/user and /root/ now it executes a source on loading of each shell and the paths are set to use gnu before the others, no more busybox binaries or root; bash; |
| 02:44.27 | Vajb | Sicelo: LMD = 3221mAh ;) |
| 03:31.23 | *** join/#maemo AndrewX192 (~andrew@unaffiliated/andrewx192) |
| 04:00.51 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 04:15.16 | *** join/#maemo pagurus (~user@p4FD6DD07.dip0.t-ipconnect.de) |
| 04:16.27 | *** join/#maemo pagurus (~user@p4FD6DD07.dip0.t-ipconnect.de) |
| 04:19.52 | *** join/#maemo pagurus (~user@p4FD6DD07.dip0.t-ipconnect.de) |
| 05:13.03 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 05:31.06 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 05:31.15 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 05:41.01 | KotCzarny | vajb: poser :P |
| 06:50.09 | *** join/#maemo eijk_ (~eijk@x4db3acc7.dyn.telefonica.de) |
| 06:52.51 | *** join/#maemo Dynamit (~Mohamed@2a02:c200:1:10:2:3:6999:150) |
| 07:23.06 | frals | DocScrutinizer05: cheers. yeah didnt see any question there either :) |
| 08:01.25 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 08:01.32 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 08:52.44 | *** join/#maemo lxp (~lxp@unaffiliated/lxp) |
| 09:51.33 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 09:56.54 | *** join/#maemo shentey (~shentey@x4e34c7be.dyn.telefonica.de) |
| 10:30.35 | *** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net) |
| 10:41.10 | *** join/#maemo xorly (~xorly@ip-89-176-117-132.net.upcbroadband.cz) |
| 10:56.50 | Sicelo | Vajb: i'd love to have that one, lol |
| 10:57.23 | DocScrutinizer05 | pretty easy, speedswap batteries |
| 10:58.38 | Sicelo | i've done that a couple of times, yes |
| 10:59.39 | DocScrutinizer05 | LMD means nothing, not even when CI=0 |
| 11:00.06 | Sicelo | it's not very convenient tbh .. esp. the need for wall charger. most times when you need that extra power, it's because you do not have access to 'charging' |
| 11:00.28 | DocScrutinizer05 | aah that sort of howswap, yeah |
| 11:00.37 | DocScrutinizer05 | hotswap even |
| 11:02.17 | DocScrutinizer05 | re "access to charging": there are pretty small (~1.5 .. 2 BL-5J volume sizes) USB power banks |
| 11:02.44 | DocScrutinizer05 | even with photovoltaic cell |
| 11:03.55 | Sicelo | :) |
| 11:07.58 | DocScrutinizer05 | https://www.amazon.com/Dual-USB-Waterproof-Solar-Battery-Charger/dp/B01EZ91C76/ref=sr_1_11?ie=UTF8&qid=1468062437&sr=8-11&keywords=usb+power+bank+solar |
| 11:08.49 | DocScrutinizer05 | https://www.amazon.com/dp/B01H3CFFF2?psc=1 |
| 11:09.25 | DocScrutinizer05 | the latter actually looks like a nifty smart critter |
| 11:12.05 | kerio | 1200mAh tho |
| 11:12.22 | kerio | well i mean, the first one claims 5Ah |
| 11:12.26 | kerio | for 10 monies |
| 11:12.31 | kerio | there's no way that's true |
| 11:15.18 | DocScrutinizer05 | https://www.amazon.com/Mini-Portable-Retractable-Motorola-Blackberry/dp/B01EJ69VF0/ref=sr_1_28?s=wireless&ie=UTF8&qid=1468062883&sr=1-28&keywords=usb+mini+power+bank |
| 11:30.54 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:0:decf:5ea9:e960:80dc) |
| 11:38.48 | DocScrutinizer05 | burn in stress test for N900 CPU: rsync a full eMMC via ssh |
| 11:39.19 | DocScrutinizer05 | temperature 52 C |
| 11:40.57 | L29Ah | how do you tell the temperature? |
| 11:41.36 | DocScrutinizer05 | http://wstaw.org/m/2016/07/09/plasma-desktopEA2277.png |
| 11:41.49 | DocScrutinizer05 | temp? simple: bq27200.sh |
| 11:42.09 | DocScrutinizer05 | chip temp of bat gauge (_not_ battery temp!) |
| 11:50.43 | kerio | i hope you're using a recent enough sshd |
| 11:50.54 | kerio | (and ssh, but that's easier) |
| 11:55.20 | kerio | chacha20 is measurably faster than other ciphers |
| 11:58.52 | DocScrutinizer05 | sshd on N900 is as recent as it gets, I guess |
| 11:59.09 | DocScrutinizer05 | IOW ancient |
| 12:00.16 | KotCzarny | faster would be just inserting microsd, rsync to it and rsync again to target |
| 12:00.44 | DocScrutinizer05 | that's not the purpose of the setup though |
| 12:00.48 | KotCzarny | order of magnitude at least faster |
| 12:02.12 | DocScrutinizer05 | my cron on PC doesn't control a robot |
| 12:02.38 | kerio | my server without AES-NI does 195MB/s of aes128gcm, 178MB/s of aes128cbc and 580MB/s of chacha20 |
| 12:02.47 | *** join/#maemo Gryllida (~svetlana@fsf/member/svetlana) |
| 12:03.00 | kerio | almost 3x speedup just by updating openssh |
| 12:03.17 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 12:03.24 | DocScrutinizer05 | kerio: that's very useful info, but I dunno what to make of it in context of rsync to N900 |
| 12:03.33 | kerio | rsync goes over ssh |
| 12:04.02 | kerio | unless you set up rsyncd |
| 12:04.05 | DocScrutinizer05 | so, you say there's a openssh version for N900 I did miss to notice? |
| 12:04.34 | kerio | i don't think it got packaged by anyone actually |
| 12:04.40 | DocScrutinizer05 | see? |
| 12:05.00 | kerio | i just asked fmg to compile it for me |
| 12:05.04 | DocScrutinizer05 | I dunno what to make of it in context of rsync to N900 |
| 12:05.08 | kerio | and i untarred it in /usr/local |
| 12:05.25 | kerio | ok whatever forget i said anything |
| 12:07.58 | DocScrutinizer05 | transfer rate is pretty constant at a pathetic 500kB/s |
| 12:08.01 | Gryllida | (Question from Oksana) Installed update from kernel power 51 to kernel power 53, phone does not boot, gives "Can not flash kernel, required files not found #00000025.62017712". Alas I have non-working USB port, so can not look at files and fix them by hand... |
| 12:08.38 | DocScrutinizer05 | ouch |
| 12:09.18 | KotCzarny | o.o |
| 12:10.57 | KotCzarny | did you have multiboot installed? |
| 12:14.18 | DocScrutinizer05 | I guess when device refuses to boot (how the heck you get the diagnostic output then?) then your only chance is USB, by whatever means. If jack is broken, there's still the 2 testpads under battery |
| 12:16.09 | Gryllida | (From Oksana) I am trying to fix USB port (googling videos), the phone is in a boot loop, it shows this Guru Meditation message and shuts down and then boots again. |
| 12:16.21 | DocScrutinizer05 | however since the diagnostic output has to have a source, the device actually boots, just maybe not entering normal interactive GUI state. bootmenu/backupmenu shell is your best bet |
| 12:18.36 | DocScrutinizer05 | iirc kernel installation hooks in a script to do the actual kernel flashing during next boot. BM should kick in before that, so you could remove that kernel flashing hooked-in script |
| 12:19.37 | DocScrutinizer05 | hi svetlana! |
| 12:19.58 | DocScrutinizer05 | best wishes and good luck to oksana |
| 12:22.11 | *** join/#maemo Dynamit (~Mohamed@2a02:c200:1:10:2:3:6999:150) |
| 12:24.01 | DocScrutinizer05 | http://paste.opensuse.org/49384982 |
| 12:24.29 | DocScrutinizer05 | # Scheduled updates are to be collected from here: |
| 12:24.30 | DocScrutinizer05 | STAGING_DIR=/var/lib/softupd/staging |
| 12:25.53 | *** join/#maemo shentey (~shentey@x55b230b4.dyn.telefonica.de) |
| 12:26.19 | DocScrutinizer05 | sbin/preinit: http://paste.opensuse.org/39905617 |
| 12:26.56 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 12:27.39 | DocScrutinizer05 | I'm not 100% sure this is the right location to look at |
| 12:27.52 | DocScrutinizer05 | but odds are it is |
| 12:31.42 | DocScrutinizer05 | ~usbfix |
| 12:31.42 | infobot | from memory, usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater), or https://www.youtube.com/watch?v=fYz5nIHH0iY#t=1866, you will basically need two irons: a small good one (or better hot-air reflow) and a 60+ Watt |
| 12:33.59 | DocScrutinizer05 | desparate measure: solder the two data wires (green, yellow?) of a USB cable to the pair of USB testpoints under battery, solder GND (black) to ground testpad nearby (do NOT use battery minus which isn't a GND pin!) |
| 12:35.04 | DocScrutinizer05 | http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports |
| 12:35.23 | DocScrutinizer05 | J5300/01 |
| 12:35.26 | DocScrutinizer05 | data |
| 12:35.55 | DocScrutinizer05 | J2000 |
| 12:35.57 | DocScrutinizer05 | pin 1 :: GND (MIDDLE upper point, right to J2062 !) |
| 12:36.50 | DocScrutinizer05 | you probably also want to solder red wire of cable to pin 3 :: USB VBUS 5V |
| 12:38.12 | DocScrutinizer05 | unless charging via USB jack still works, which means the VBUS pin still has contact and so you can provide 5V via the normal way |
| 12:39.17 | DocScrutinizer05 | test: when device power up when connecting it to a charger, then VBUS still works |
| 12:42.32 | Gryllida | How to enter the backup menu? Multiboot is installed |
| 12:48.30 | *** join/#maemo Juest (~Zilla@unaffiliated/juest) |
| 12:50.23 | KotCzarny | gryllida: just google your error code |
| 12:50.31 | KotCzarny | there is tmo thread that could help you |
| 12:50.51 | KotCzarny | and most likely multiboot is the culprit of failed update |
| 12:51.07 | DocScrutinizer05 | ~maemo-multiboot |
| 12:51.08 | infobot | hmm... maemo-multiboot is deprecated, and a horrible hack. PROBLEMS WITH NITDROID/MULTIBOOT? reflash rootfs&kernel aka COMBINED |
| 12:53.13 | DocScrutinizer05 | this factoid been defined after literally dozens of failed efforts to recover from a broken multiboot (multiboot is NOT uBoot!) |
| 12:54.03 | DocScrutinizer05 | multiboot basically reflashes kernel on *every* boot, which is.. well what the factoid says: a *horrible* hack |
| 12:54.44 | Juest | no wonder its broken, it similar to the /system/etc/install-recovery.sh annoyance on Android. |
| 12:55.07 | Juest | aka no surprise |
| 12:55.12 | Juest | waves |
| 12:57.03 | DocScrutinizer05 | and obviously when you flash a new kernel, next multiboot will fail epically since it has no idea that kernel (and matching modules!!) changed, and so multiboot will flash something inappropriate or will throw random crappy errors |
| 13:01.26 | Juest | it is a recoverable brick at least? |
| 13:01.32 | Juest | wonders |
| 13:02.03 | DocScrutinizer05 | >>Plzzz tel cz my n900 is screeveedd << OHMY!! |
| 13:02.20 | Juest | o.o |
| 13:02.20 | DocScrutinizer05 | https://talk.maemo.org/showthread.php?t=72879&page=2 |
| 13:03.43 | DocScrutinizer05 | Juest: multiboot? -->reflash |
| 13:03.54 | KotCzarny | juest, with working usb port you cannot brick n900 |
| 13:04.04 | KotCzarny | the only way is to nuke nolo |
| 13:04.10 | DocScrutinizer05 | no |
| 13:04.13 | KotCzarny | but that requires some skill |
| 13:04.15 | DocScrutinizer05 | not even that |
| 13:04.29 | Juest | Well, apparently wikiwide didnt armor the usb port |
| 13:04.42 | Juest | nolo? wat |
| 13:04.47 | DocScrutinizer05 | nevermind |
| 13:04.51 | DocScrutinizer05 | ~nolo |
| 13:04.55 | DocScrutinizer05 | o.O |
| 13:05.10 | DocScrutinizer05 | NOkia bootLOader |
| 13:05.18 | Juest | Right |
| 13:05.26 | DocScrutinizer05 | ~coldflashing |
| 13:05.31 | Juest | weird its not in infobot, would expected it |
| 13:05.35 | DocScrutinizer05 | ~coldflas |
| 13:05.37 | DocScrutinizer05 | ~coldflash |
| 13:05.37 | infobot | [coldflash] http://mg.pov.lt/maemo-irclog/%23maemo.2010-10-31.log.html#t2010-10-31T23:34:01 (jacekowski's instructions), or http://wiki.maemo.org/Updating_the_firmware/Cold_Flashing |
| 13:05.49 | Juest | Thank you. |
| 13:10.08 | DocScrutinizer05 | yw |
| 13:11.26 | DocScrutinizer05 | ~nolo is NOkia bootLOader, Nokia's version of uboot-alike first (actually 2nd) stage bootloader for NIT like N900 |
| 13:11.26 | infobot | DocScrutinizer05: okay |
| 13:12.00 | Juest | ~nit |
| 13:12.00 | infobot | somebody said nit was Nokia Internet Tablet |
| 13:12.10 | Juest | hehe |
| 13:12.30 | Juest | nice addition btw |
| 13:13.43 | DocScrutinizer05 | ~nolo is also somebody said it was a nasty character in Norwegian languange |
| 13:13.43 | infobot | okay, DocScrutinizer05 |
| 13:14.08 | DocScrutinizer05 | ~nolo |
| 13:14.08 | infobot | rumour has it, nolo is NOkia bootLOader, Nokia's version of uboot-alike first (actually 2nd) stage bootloader for NIT like N900, or somebody said it was a nasty character in Norwegian languange |
| 13:14.10 | Juest | wonders is there a way to properly execute maemo shortcuts on xepyhr since shift+control is used to grab and release mouse/keyboard control |
| 13:14.34 | DocScrutinizer05 | reconfigure xephyr shortcuts |
| 13:14.51 | Juest | either bypassing xephyr and using X directly or yeah that, i dont know where the config is located |
| 13:15.02 | DocScrutinizer05 | nfc |
| 13:15.33 | Juest | its sort of "fragile" the launcher only seems to work properly when using the shortcut on the desktop, it didnt work with a terminal directly |
| 13:15.54 | DocScrutinizer05 | launcher? |
| 13:16.01 | Juest | .desktop |
| 13:16.03 | DocScrutinizer05 | with a terminal? |
| 13:16.17 | Juest | .desktop's commandline |
| 13:16.26 | *** join/#maemo shentey (~shentey@x55b230b4.dyn.telefonica.de) |
| 13:16.31 | DocScrutinizer05 | .desktop are intricate |
| 13:16.32 | Juest | sdk is a ubuntu lucid vm.... |
| 13:17.01 | DocScrutinizer05 | often a run-standalone <app> helps |
| 13:17.15 | Juest | what you mean? hmm |
| 13:17.25 | DocScrutinizer05 | run-standalone <app> |
| 13:17.35 | Juest | adventures into /etc about xephyr |
| 13:17.50 | DocScrutinizer05 | run-standalone.sh |
| 13:17.57 | Juest | path? |
| 13:18.01 | DocScrutinizer05 | err |
| 13:18.14 | DocScrutinizer05 | <PROTECTED> |
| 13:18.22 | Juest | ah ok |
| 13:22.10 | DocScrutinizer05 | anyway you can't run e.g /usr/share/applications/hildon/camera-ui.desktop as a cmdline binary or script |
| 13:23.39 | DocScrutinizer05 | you got some dbus related info in those .desktop: |
| 13:23.43 | DocScrutinizer05 | X-Osso-Service=com.nokia.cameraui |
| 13:23.44 | DocScrutinizer05 | X-Osso-Type=application/x-executable |
| 13:24.09 | DocScrutinizer05 | and some supposedly cmdline path: Exec=/usr/bin/camera-ui |
| 13:24.45 | Juest | ... i've tried running /usr/bin/start_xephyr.sh and it didnt work properly from a terminal |
| 13:24.46 | DocScrutinizer05 | often the latter is sinmply a symlink to maemo-launcher |
| 13:25.28 | DocScrutinizer05 | starting xephyr is tricky |
| 13:25.32 | DocScrutinizer05 | s/starting // |
| 13:26.24 | Gryllida | where are you running it ? |
| 13:26.54 | Juest | Apparently only it works properly by using the desktop launcher |
| 13:27.01 | Juest | solely on a terminal doesnt work |
| 13:27.18 | Juest | And i am still trying to find Xephyr's config files |
| 13:29.35 | Juest | Okay, it works from a oot terminal |
| 13:29.45 | Juest | s/oot/root |
| 13:29.57 | Juest | no screen :( |
| 13:30.05 | Juest | ah, not allowed |
| 13:30.54 | Juest | Weird, now i simply do not have a display :/ |
| 13:32.38 | Juest | Great... now i dont have a screen |
| 13:34.49 | Juest | I am unable to run it from a standard terminal |
| 13:35.07 | Juest | root terminal works but the sdk is not designed to be ran as root |
| 13:35.21 | Juest | now maemo is there but in some sort of limbo |
| 13:35.34 | Juest | it broke for the session |
| 13:37.10 | Juest | feel free to join at juesto.pw:6000 pw: maemosdk |
| 13:37.22 | Juest | (vnc) |
| 13:38.08 | Juest | it also has few glitches.... |
| 13:38.15 | Juest | like changing themes breaks ui |
| 13:39.22 | DocScrutinizer05 | sorry, last time I used maemo-sdk + xephyr must be like 6 years ago, maybe longer |
| 13:40.44 | Juest | damnit, it makes me feel tired Gryllida |
| 13:41.59 | Juest | i cant find anything about tweaking xephyr |
| 13:42.48 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 13:43.58 | Gryllida | is xephyr an an emulator ? |
| 13:44.29 | Juest | man xephyr its not a emulator but a Nested X |
| 13:44.38 | Juest | in this case its some sort of emulator Gryllida |
| 13:44.48 | Juest | fremantle sdk emulator |
| 13:44.52 | Gryllida | one does not maemo until they are soldering |
| 13:45.02 | Juest | o_O? |
| 13:45.18 | Juest | meep pm Gryllida |
| 13:48.34 | Gryllida | our solder is too big, and no flux, this tiny thing. feynman's radio life was more fun, at least the items were large enough for the soldering iron to stick its end nto them freely |
| 13:48.57 | Juest | :( |
| 13:51.15 | Juest | Lol, i cant delete in maemo configuration editor |
| 13:52.42 | Juest | scrollwheel doesnt even work |
| 13:52.45 | Juest | neither hold :/ |
| 13:53.08 | Juest | at least not in that app |
| 13:53.58 | Juest | and theres no camera on the sdk |
| 13:54.47 | Juest | Hello? |
| 13:56.50 | Juest | well idk |
| 13:56.57 | Juest | apparently its the app itself |
| 13:59.00 | Juest | wtf, upgrade ability is broken somewhat |
| 14:03.52 | Juest | lol |
| 14:03.56 | Juest | now anything fials to install |
| 14:05.37 | DocScrutinizer05 | Juest: you're talking random? |
| 14:06.00 | Juest | perhaps, i am still upset with this half-working thing |
| 14:10.31 | Juest | great, i managed to freeze fremantle sdk |
| 14:10.33 | Juest | ffs |
| 14:23.57 | *** part/#maemo Juest (~Zilla@unaffiliated/juest) |
| 14:45.17 | *** join/#maemo xkr47 (xkr47@2001:14b8:141:5926:5358:9793:2384:6264) |
| 15:14.32 | kerio | do we have a report of someone restoring bluetooth functionality after clearing CAL? |
| 15:14.59 | DocScrutinizer05 | Gryllida: don't even think of soldering SMT unless you got a proper noclean flux |
| 15:15.24 | DocScrutinizer05 | kerio: not afaik, but why whouldn't it work? |
| 15:16.00 | kerio | istr that guy who did nandtest on everything didn't have a working bluetooth afterwards |
| 15:16.07 | kerio | the bluetooth MAC is stored in CAL |
| 15:16.07 | DocScrutinizer05 | you're not supposed to clear CAL, restore it to arbitrary proper content |
| 15:16.30 | kerio | what if critical failure happens |
| 15:17.37 | DocScrutinizer05 | ^^^ |
| 15:17.47 | *** join/#maemo APic (apic@apic.name) |
| 15:17.53 | Gryllida | we're soldering to the testing pads |
| 15:18.25 | kerio | hold on weren't there some mtdblk devices |
| 15:18.35 | kerio | that behaved like shitty block devices |
| 15:18.43 | DocScrutinizer05 | hm? |
| 15:19.01 | kerio | hold on what's log |
| 15:19.19 | DocScrutinizer05 | http://maemo.cloud-7.de/dd_if%3dmtd1ro.bin |
| 15:19.36 | DocScrutinizer05 | log = mtdoops |
| 15:20.04 | kerio | oh right |
| 15:20.07 | kerio | how do i read that again? |
| 15:20.19 | kerio | DocScrutinizer05: are you sure that dd is enough? |
| 15:20.34 | kerio | like, have you tried a restore? |
| 15:20.54 | kerio | nanddump has a bunch of options regarding OOB data and bad blocks ._. |
| 15:21.28 | *** join/#maemo APic (apic@apic.name) |
| 15:21.36 | DocScrutinizer05 | sp-oops-extract |
| 15:22.36 | DocScrutinizer05 | http://maemo.cloud-7.de/mtd_debug_read_mtd1_0_0x60000.bin |
| 15:23.32 | kerio | why isn't cal-tool able to dump and restore CAL from a higher level, though? |
| 15:23.46 | *** join/#maemo APic (apic@apic.name) |
| 15:24.03 | DocScrutinizer05 | no idea |
| 15:25.13 | DocScrutinizer05 | maybe because cal-tool isn't meant for that, there's another more generic cal thing made by iirc pali |
| 15:25.56 | Pali | because there is no backup/restore tool for cal |
| 15:27.05 | DocScrutinizer05 | https://dev.openwrt.org/browser/packages/utils/calvaria |
| 15:30.46 | DocScrutinizer05 | http://maemo.cloud-7.de/_hidden/cncmods-net/www.cncmods.net/files/calvaria |
| 15:35.29 | DocScrutinizer05 | http://paste.opensuse.org/85827438 |
| 15:39.22 | DocScrutinizer05 | http://paste.opensuse.org/95893210 |
| 15:44.12 | DocScrutinizer05 | seems calvaria lacks write capabilities, however that should be trivial |
| 15:44.57 | DocScrutinizer05 | and anyway you could check if a raw data write to NAND CAL partition (nandwrite et al) would result in a CAL content that looks OK |
| 15:45.51 | DocScrutinizer05 | you even could edit the image file before to your liking, and check that file with calvaria to look OK before you flash it |
| 15:46.23 | DocScrutinizer05 | edit manually that is |
| 15:47.18 | DocScrutinizer05 | I dunno if openwrt has improved the calvaria tool |
| 15:49.40 | *** join/#maemo krnlyng (~liar@77.117.87.74.wireless.dyn.drei.com) |
| 15:52.13 | DocScrutinizer05 | noteworthy that niokia's phenix service tool knows to write e.g. ALS calib data to CAL, so I guess that must be a generic way Nokia uses to calibrate their phones - phenix is universal for all Nokia devices |
| 15:53.14 | DocScrutinizer05 | Phoenix |
| 15:53.33 | DocScrutinizer05 | http://www.allmobiletools.net/2014/12/nokia-phoenix-service-software-201415.html |
| 15:57.18 | DocScrutinizer05 | note that this particular site looks like scam |
| 15:57.41 | DocScrutinizer05 | I explicitly don't recommend to download anything there |
| 15:59.32 | DocScrutinizer05 | anyway here's more info http://nokiarevolution.com/how-to-flash-your-nokia-device-via-phoenix-usb-dead-flashing/ |
| 16:07.17 | DocScrutinizer05 | kerio: nope, I actually didn't try to restore yet. Anyway what could possibly go wrong that's worse than an already borked CAL when you try to restore it? |
| 16:07.36 | kerio | the point is that we should figure out a way to not have a borked CAL |
| 16:07.50 | kerio | but i don't think a block-by-block copy is the answer |
| 16:08.14 | kerio | is CAL used somewhere else? |
| 16:08.25 | kerio | because i don't understand how you could come up with something like that |
| 16:08.28 | DocScrutinizer05 | I *guess* when you write the dump to CAL and dd dump the CAL content after that and compare to original image, and they don't differ, I'd dare to say you won |
| 16:08.30 | kerio | versus just a file on jffs2 |
| 16:08.59 | DocScrutinizer05 | again, it's legacy |
| 16:09.13 | DocScrutinizer05 | prolly used on all Nokia phones |
| 16:09.13 | kerio | yeah but is it used on some dumber nokia phone? |
| 16:09.15 | kerio | k |
| 16:11.07 | DocScrutinizer05 | we already discused and verified that a simple bindmount or the like should suffice to use a image file instead of a mtd partition for cal* in maemo |
| 16:11.37 | DocScrutinizer05 | except for flasher of course |
| 16:11.49 | DocScrutinizer05 | since that's not 'in maemo' |
| 16:12.05 | Gryllida | (From Oksana) With such huge soldering iron and no flux, it is hopeless to do anything even with such large test pads.. |
| 16:12.24 | kerio | oh, you can change the lock code and it'll get "appended" to your bindmounted file? |
| 16:12.32 | kerio | and when you remove the bindmount the lock code is still the old one? |
| 16:12.37 | kerio | neato |
| 16:12.46 | DocScrutinizer05 | yes, please don't ruin device by trying to solder on it with cheap tools and lack of decent flux |
| 16:12.50 | DocScrutinizer05 | it never will work |
| 16:13.35 | DocScrutinizer05 | kerio: yes |
| 16:14.07 | kerio | DocScrutinizer05 would probably like louis rossmann |
| 16:14.12 | Gryllida | Oksana says she can only hope the camera is still okay. (I say we would maybe try to get access to proper tools at uni, or at a local store; the lack of flux immediately disappointed me in the beginning) |
| 16:14.30 | DocScrutinizer05 | I don't know that guy |
| 16:14.58 | kerio | makes videos on youtube where he repairs mostly macbook motherboards |
| 16:15.03 | kerio | yells at apple |
| 16:15.07 | DocScrutinizer05 | get *decent* flux, NO acid flux! |
| 16:15.08 | kerio | yells at stupid repair shops |
| 16:15.39 | Gryllida | cheers |
| 16:15.59 | DocScrutinizer05 | ~usbfix |
| 16:15.59 | infobot | i guess usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater), or https://www.youtube.com/watch?v=fYz5nIHH0iY#t=1866, you will basically need two irons: a small good one (or better hot-air reflow) and a 60+ Watt |
| 16:16.04 | DocScrutinizer05 | see the video |
| 16:16.32 | kerio | became famous after yelling at another (very popular) youtuber for making a video where a video card was "fixed" by putting it in an oven |
| 16:21.32 | DocScrutinizer05 | Gryllida: https://youtu.be/b9FC9fAlfQE?t=939 |
| 16:28.26 | Gryllida | good video, shows how it works and the picture is not blurry, and has useful info. thank you |
| 16:33.53 | DocScrutinizer05 | https://youtu.be/b9FC9fAlfQE?t=1560 |
| 16:34.02 | DocScrutinizer05 | Gryllida: yw |
| 16:34.14 | *** join/#maemo xray256_ (~xray256@host86-166-174-128.range86-166.btcentralplus.com) |
| 16:34.15 | DocScrutinizer05 | no learning without competent info source |
| 16:36.41 | Gryllida | (From Oksana) Curious, what this problem is caused by, a lot of people must be using kernel power 53, and many of them have probably upgraded from kernel power 51. So what exactly was the problem with upgrding to kernel power 53? |
| 16:38.34 | KotCzarny | you have multiboot installed |
| 16:40.25 | DocScrutinizer05 | https://youtu.be/b9FC9fAlfQE?t=1850 |
| 16:40.46 | DocScrutinizer05 | Gryllida: what KotCzarny said# |
| 16:40.54 | DocScrutinizer05 | ~maemo-multiboot |
| 16:40.54 | infobot | i guess maemo-multiboot is deprecated, and a horrible hack. PROBLEMS WITH NITDROID/MULTIBOOT? reflash rootfs&kernel aka COMBINED |
| 16:41.42 | DocScrutinizer05 | [2016-07-09 Sat 14:53:13] <DocScrutinizer05> this factoid been defined after literally dozens of failed efforts to recover from a broken multiboot (multiboot is NOT uBoot!) |
| 16:41.43 | DocScrutinizer05 | [2016-07-09 Sat 14:54:03] <DocScrutinizer05> multiboot basically reflashes kernel on *every* boot, which is.. well what the factoid says: a *horrible* hack |
| 16:43.25 | Gryllida | ok |
| 16:50.10 | DocScrutinizer05 | https://youtu.be/b9FC9fAlfQE?t=2211 |
| 16:50.31 | DocScrutinizer05 | take care! you NEED a decent regulated soldering iron |
| 16:52.09 | Vajb | soldering has its times |
| 16:52.15 | Vajb | just not today |
| 16:52.42 | Vajb | tried to made bridging over two pairs of pads |
| 16:53.06 | Vajb | problem was that area was like 1mm x 2mm at max |
| 16:53.26 | Vajb | needless to say i failed miserably |
| 16:53.46 | Vajb | should have sticked to graphite instead... |
| 16:54.52 | Vajb | and what i was doing? Tried to fix Nokia 5130 "no sound from headset" problem |
| 16:56.11 | DocScrutinizer05 | Gryllida: https://youtu.be/J5Sb21qbpEQ?t=91 |
| 16:57.20 | Gryllida | thank you most kindly; I was expecting this to be easy, but the soldering material isn't sticky enough, and I should definitely know better |
| 16:57.59 | Gryllida | I will watch all this when I'm a bit more awake, with Oksana, and plan from there |
| 17:00.18 | DocScrutinizer05 | Gryllida: good plan :-) you're welcome |
| 17:01.02 | DocScrutinizer05 | honestly no expert can do a decent job with cheesy tools. You need a certain minimum that's listed in last URL |
| 17:01.45 | DocScrutinizer05 | regulated soldering iron, FLUX!!!, solder wick. Then you're already almost there |
| 17:02.22 | DocScrutinizer05 | hot air comes in very handy when you also got solder paste etc |
| 17:04.02 | DocScrutinizer05 | and decent solder wire of course |
| 17:05.07 | Gryllida | I think in another few years we will be able to open a phone fix company |
| 17:05.13 | DocScrutinizer05 | https://youtu.be/J5Sb21qbpEQ?t=686 |
| 17:05.28 | Gryllida | already have a lot of screwdrivers, internet to buy replacement parts, now soldering iron and related tools, ... what else? :) |
| 17:06.12 | Gryllida | a pretty logo and a pretty site + some time for flying a cheaper beta program to gain experience |
| 17:06.14 | Gryllida | or something |
| 17:06.34 | Gryllida | (or some course... whatever these guys usually begin from) |
| 17:09.16 | Pali | DocScrutinizer05: Phoenix boots N900 into TEST mode and uses softupd daemon and it just update cal keys, but do not support dump/restore |
| 17:10.21 | DocScrutinizer05 | I didn't think it supports dump/restore |
| 17:10.48 | DocScrutinizer05 | dump/restore is a basically alien concept to CAL |
| 17:26.31 | DocScrutinizer05 | however I wonder how Phoenix does e.g. ALS CAL calibration via softupd, when maemo has no tool to write CAL records |
| 17:27.03 | DocScrutinizer05 | must be raw NAND partition access then, no? |
| 17:28.04 | DocScrutinizer05 | unless flasher has some secrete function to update CAL records |
| 17:28.12 | *** join/#maemo shentey (~shentey@x55b230b4.dyn.telefonica.de) |
| 17:29.03 | DocScrutinizer05 | or Phoenix uploads a executable to RAM and runs it |
| 17:31.01 | DocScrutinizer05 | flasher indeed also updates CAL records, it notes the software version there |
| 17:31.30 | DocScrutinizer05 | so I wonder how flasher and phoenix do this magic |
| 17:32.21 | DocScrutinizer05 | BME also seems to write to CAL |
| 17:32.55 | KotCzarny | RE the softupd? |
| 17:37.32 | DocScrutinizer05 | what for? |
| 17:38.05 | DocScrutinizer05 | it's way easier to augment calvaria to learn to write records |
| 17:38.56 | DocScrutinizer05 | the only unclear (unspecified) behavior in CAL is when it's getting full |
| 17:39.55 | DocScrutinizer05 | until then new records are simply appended and supersede any prior records for same key |
| 17:40.19 | DocScrutinizer05 | iirc |
| 17:41.30 | DocScrutinizer05 | iirc that's also how bad NAND blocks get handled. Simply read back the record you just wrote, and when that fails simply write it once more |
| 17:43.17 | DocScrutinizer05 | note that writing to erased NAND is simple. Just erasing NAND is not as simple |
| 17:45.40 | DocScrutinizer05 | you only can erase complete erase pages (set all bits to e.g. zero) and then you can set each individual bit to one at arbotrary times |
| 17:47.06 | DocScrutinizer05 | that's btw what TRIM is all about |
| 17:47.27 | DocScrutinizer05 | Pali: does powerkernel know TRIM/discrad? |
| 17:48.01 | DocScrutinizer05 | I noticed all our flash storage isn't mounted with -o discard |
| 17:48.37 | DocScrutinizer05 | this would make for a *huge* improvement, also and particularly for swap |
| 17:50.01 | Pali | IIRC ext3 does not support discard |
| 17:50.25 | DocScrutinizer05 | it does |
| 17:50.48 | DocScrutinizer05 | https://wiki.ubuntuusers.de/SSD/TRIM/ |
| 17:51.32 | DocScrutinizer05 | <PROTECTED> |
| 17:52.09 | Pali | but that is batched mode |
| 17:52.11 | Pali | not "discard" |
| 17:52.13 | DocScrutinizer05 | aah yes |
| 17:52.21 | DocScrutinizer05 | just noticed that |
| 17:52.47 | Pali | fstrim is using that batched mode |
| 17:53.05 | DocScrutinizer05 | I didn't find fstrim for maemo |
| 17:53.06 | Pali | but anyway, everything needs new kernel |
| 17:53.13 | Pali | nothing for 2.6.28 |
| 17:53.19 | DocScrutinizer05 | yep |
| 17:53.33 | DocScrutinizer05 | that's why I asked about powerkernel |
| 17:53.42 | Pali | nothing |
| 17:53.44 | *** join/#maemo andril (~andril@97.68.237.19) |
| 17:54.11 | Pali | only battery modules were backported and all is same as upstream kernel |
| 17:55.15 | DocScrutinizer05 | worthwhile to ponder how to get TRIM support |
| 17:57.14 | DocScrutinizer05 | for swap it's important to make swap page size == flash erase page size |
| 17:57.18 | DocScrutinizer05 | and align |
| 18:00.38 | *** join/#maemo ashneo76 (~ashneo76@204.14.154.168) |
| 18:15.57 | DocScrutinizer05 | for the interested audience: http://www.thessdreview.com/daily-news/latest-buzz/garbage-collection-and-trim-in-ssds-explained-an-ssd-primer/ |
| 18:18.30 | buZz | cute, ty |
| 18:18.41 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 18:19.04 | buZz | DocScrutinizer05: also checkout fstrim |
| 18:19.12 | buZz | <PROTECTED> |
| 18:19.13 | buZz | <PROTECTED> |
| 18:19.13 | buZz | <PROTECTED> |
| 18:23.19 | DocScrutinizer05 | I know :-9 |
| 18:23.24 | DocScrutinizer05 | :-) even |
| 18:24.14 | DocScrutinizer05 | the key statement: >>When the OS deletes the file, it simply marks the space used for that data as free in its logical data table. With HDDs, the OS does not need to tell the storage device anything about the deletion because it would simply write something new into that same physical location in the future. In the case of an SSD, it only becomes aware that the data is deleted (or invalid) when the OS tries to write to that location |
| 18:24.15 | DocScrutinizer05 | again<< |
| 18:26.29 | DocScrutinizer05 | and >>The advantage of the TRIM command is that it enables the SSDâs GC to skip the invalid data rather than moving it, thus saving time not rewriting the invalid data. This results in a reduction of the number of erase cycles on the flash memory and enables higher performance during writes<< |
| 18:38.24 | DocScrutinizer05 | https://www.youtube.com/watch?v=x6lqYU4j7no |
| 18:43.55 | DocScrutinizer05 | wonders how hard it could be to implement fstrim-alike brute force TRIM to a range of eMMC (read: swap) without any kernel support |
| 18:45.07 | DocScrutinizer05 | reswap only makes true sense with TRIM of the deactivated and depleted swap partition |
| 18:46.23 | DocScrutinizer05 | this whole TRIM issue also suggests an explanation why devices slow down when you have much data on eMMC |
| 18:46.37 | DocScrutinizer05 | the eMMC lacks overprovisioning then |
| 18:46.58 | DocScrutinizer05 | which significantly burdens the GC |
| 18:52.01 | DocScrutinizer05 | hmmm, re implementing batched TRIM, it would need a way to talk directly to the storage bus, which is probably only allowed to the kernel driver |
| 18:52.46 | DocScrutinizer05 | so backporting the according IOCTL should suffice for that |
| 18:56.47 | DocScrutinizer05 | >> * This program uses FITRIM ioctl to discard parts or the whole filesystem * online (mounted). You can specify range (start and length) to be * discarded, or simply discard whole filesystem.<< https://github.com/karelzak/util-linux/blob/master/sys-utils/fstrim.c |
| 19:09.18 | *** join/#maemo japa-fi (~jani@mobile-access-5d6a0c-238.dhcp.inet.fi) |
| 19:11.17 | DocScrutinizer05 | hmmm http://lxr.free-electrons.com/source/drivers/mmc/core/core.c#L2052 dunno if I wound the right runway to land |
| 19:12.51 | DocScrutinizer05 | anyway I guess backporting the low level mmc driver can't be too hard since at least the API shouldn't have changed since lernel 2.6.xx |
| 19:12.59 | DocScrutinizer05 | kernel even |
| 19:15.24 | DocScrutinizer05 | http://lxr.free-electrons.com/source/drivers/mmc/core/core.c#L2198 |
| 19:19.25 | *** join/#maemo handaxe (~chatter@c83-248-22-153.bredband.comhem.se) |
| 19:56.46 | *** join/#maemo handaxe (~chatter@c83-248-22-153.bredband.comhem.se) |
| 19:57.40 | kerio | Pali: whenever you boot your mainline linux kernel, can you see if mounting a partition with discard actually works as intended? |
| 19:58.10 | Pali | do not know, I have never used discard |
| 19:59.12 | kerio | just mount a partition with -o discard |
| 19:59.17 | kerio | idk how to test if it worked tho |
| 19:59.33 | Pali | I'm not going to test any discard on any machine |
| 19:59.37 | kerio | :c |
| 19:59.55 | Pali | it is buggy and unsupported on lot of places |
| 20:04.33 | kerio | ok |
| 20:16.44 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 20:43.12 | *** join/#maemo tryagain (~quassel@178.216.76.204) |
| 21:01.53 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 21:02.00 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 21:28.10 | *** join/#maemo zGrr (~Grr@188.146.67.56.nat.umts.dynamic.t-mobile.pl) |
| 21:28.52 | zGrr | moin ;) |
| 21:44.20 | *** join/#maemo trx (ns-team@devbin/founder/trx) |
| 21:53.33 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 21:57.10 | *** join/#maemo handaxe (~chatter@c83-248-22-153.bredband.comhem.se) |
| 22:12.14 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 22:50.32 | *** join/#maemo sunshavi (~user@190.235.18.236) |
| 22:53.00 | *** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net) |
| 22:59.43 | *** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net) |
| 23:24.43 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
