mueddib | ah I understand | 00:00 |
---|---|---|
Pali | http://talk.maemo.org/showthread.php?t=81613 --> works only if Maemo is installed | 00:00 |
Pali | what you can do is to decrease size of MyDocs partition | 00:00 |
Pali | and after that create new parition | 00:00 |
Pali | uboot is loading configuration from MyDocs | 00:00 |
Pali | so decrease MyDocs e.g. to 1GB | 00:01 |
Pali | and you should have ~~ 22GB empty after 3rd partition | 00:02 |
Pali | (maybe more 26GB probably) | 00:02 |
*** handaxe has joined #maemo | 00:06 | |
mueddib | Dear Pali, last time I delete all partition on the mmcblk0 and reboot and N900 work :) | 00:07 |
mueddib | right? | 00:07 |
Pali | if you delete all partitions on eMMC, then you delete Maemo5 | 00:08 |
mueddib | https://jpst.it/QlV4 | 00:08 |
mueddib | no Maemo is not delete, N900 boot :) | 00:08 |
mueddib | https://jpst.it/QlV8 | 00:09 |
mueddib | did you seen? https://jpst.it/QlV8 | 00:09 |
mueddib | :) | 00:09 |
Pali | probably is damaged | 00:11 |
mueddib | really? hm.. | 00:11 |
Pali | as all more parts are stored in /opt (=mount bind to /home/opt) and in /home/user/ | 00:11 |
mueddib | Pali, I wondering, can not I install gentoo on the N900? For example, grub start get the grub menu I select kernel and find to ext3 /boot folder boot the kernel and boot linux | 00:19 |
mueddib | just like computers. | 00:19 |
mueddib | can not it be that way? | 00:20 |
Pali | uboot supports that bootmenu | 00:22 |
Pali | you can | 00:22 |
Pali | but configuration is loaded from MyDocs | 00:22 |
Pali | so now you cannot use uboot | 00:23 |
Pali | as you deleted everything needed for it | 00:23 |
mueddib | Dear Pali, thanks for all informations, I install to uboot next time and I use Gentoo :) | 00:28 |
mueddib | I don't use Maemo, Maemo is good and based debian but I need compile packages everytime on the N900 | 00:28 |
mueddib | :) | 00:29 |
Wizzup | You're crazy | 00:29 |
Wizzup | I use gentoo on my n900, but I don't compile anything on it | 00:29 |
Pali | you can flash kernel image directly to nand | 00:29 |
Wizzup | I compile it on a different machine | 00:29 |
Pali | and use it without uboot | 00:29 |
mueddib | this problem, n900 is very very slow :) | 00:29 |
Pali | but in that case you need to ensure that you have everything needed for booting in zImage | 00:30 |
Pali | and that zImage size is < 2MB | 00:30 |
Pali | and cmdline and others is compiled in zImage | 00:30 |
mueddib | Wizzup, I compile only bitchx irc client, mutt, vi, and linux kernel | 00:30 |
mueddib | (chroot) Nokia-N900-42-11 media # df -h | 00:31 |
mueddib | Filesystem Size Used Avail Use% Mounted on | 00:31 |
Wizzup | so why not compile it on some other arm machine, or with qemu-user, or with cross compile | 00:31 |
mueddib | /dev/mmcblk0p1 30G 173M 28G 1% /media/mmcblk0 | 00:31 |
mueddib | this is good :) | 00:31 |
bencoh | seriously this is .... ridiculous | 00:31 |
mueddib | so, I have a problem | 00:33 |
mueddib | I connect to SSH and always freeze over ssh I'm waiting to enter the command. What could be the reason frozen? | 00:34 |
Wizzup | Maybe it's below 0 degrees celsius. | 00:34 |
mueddib | Wizzup right now, here it is snowing and weather is very cold. | 00:35 |
*** at1as has joined #maemo | 00:36 | |
mueddib | Wizzup are you serious? could it be cold? | 00:40 |
Wizzup | No, I wasn't serious. | 00:41 |
Wizzup | Maybe wifi power saving? You should figure out how it freezes, where it freezes, in what part in the exchange | 00:41 |
mueddib | hm, how do I resolve that it is waiting on ssh? | 00:41 |
Wizzup | ssh -vvv | 00:41 |
mueddib | hm I check now, thank you | 00:41 |
mueddib | OpenSSH_5.1p1 Debian-6.maemo5, OpenSSL 0.9.8g 19 Oct 2007 | 00:42 |
Wizzup | I was suggesting increasing the verbosity, not printing the version. | 00:43 |
mueddib | Where can I change to wifi power saving? | 00:44 |
Pali | iw | 00:46 |
Pali | and tell any other wifi sw to not enable it (network-manager, wicd, etc..) | 00:46 |
mueddib | I use default network-manager | 00:47 |
*** at1as has quit IRC | 00:58 | |
*** dreamer has quit IRC | 01:09 | |
*** dreamer has joined #maemo | 01:10 | |
*** louisdk has quit IRC | 01:23 | |
*** jonwil has quit IRC | 01:35 | |
*** Kilroo has joined #maemo | 01:58 | |
*** N-Mi_ has joined #maemo | 02:22 | |
*** florian has quit IRC | 02:42 | |
*** florian has joined #maemo | 02:43 | |
*** florian has quit IRC | 02:47 | |
*** cyphase has quit IRC | 03:07 | |
*** cyphase has joined #maemo | 03:11 | |
*** mueddib has quit IRC | 03:22 | |
*** krnlyng has quit IRC | 03:25 | |
*** krnlyng has joined #maemo | 03:39 | |
*** N-Mi_ has quit IRC | 03:42 | |
*** xes has joined #maemo | 04:13 | |
*** Pali has quit IRC | 05:02 | |
*** stryngs has quit IRC | 05:33 | |
*** stryngs has joined #maemo | 05:34 | |
*** stryngs is now known as Guest10263 | 05:34 | |
*** Guest10263 has quit IRC | 05:37 | |
*** stryngs_ has joined #maemo | 05:54 | |
DocScrutinizer05 | (([2016-12-13 Tue 21:10:49] <bencoh> mmc1 is external sdcard, mmc0 is (internal) eMMC)) WATCH OUT! this is not exactly totaly true | 05:55 |
*** lxp1 has joined #maemo | 06:02 | |
*** lxp has quit IRC | 06:04 | |
*** tm has quit IRC | 06:36 | |
*** tm has joined #maemo | 06:43 | |
DocScrutinizer05 | http://paste.opensuse.org/94100329 | 06:44 |
DocScrutinizer05 | actually maemo does explicitly rename / swap mmc0 and mmc1 if and only if both are detected, since the kernel first checks uSD and after that eMMC, so depending if a uSD is present or not, the naming is different before that explicit renaming | 06:46 |
DocScrutinizer05 | http://mg.pov.lt/maemo-irclog/%23maemo.2011-10-31.log.html#t2011-10-31T04:34:19 http://mg.pov.lt/maemo-irclog/%23maemo.2011-10-31.log.html#t2011-10-31T05:13:29 | 06:57 |
DocScrutinizer05 | cat /lib/udev/mmc_id | 07:17 |
DocScrutinizer05 | freemangordon: ^^^ is one of the many many things I think will be quite a pita to ship around when trying to "port fremantle" to devuan piece by piece | 07:18 |
DocScrutinizer05 | since I'm quite sure there's no such thing like /lib/udev/mmc_id and the framework calling it, in plain devuan. And yet basically _all_ maemo apps etc depend on the results of this little thingie, in that they have hardcoded path names etc | 07:19 |
DocScrutinizer05 | you can't build a house from roof to basement | 07:20 |
DocScrutinizer05 | in my book it's simpler to port devuan to maemo fremantle piece by piece, and fix the fallout after each ported piece | 07:24 |
DocScrutinizer05 | porting only one or a few fremantle pieces to devuan will be a real PITA to make them work since you need to fix a metric shitton of such little incompatibilities just to find you need to fix them *again* for the next piece you port, since e.g. _all_ are depending on same consistent persistent naming eMMC=mmc0 uSD=mmc1 and you either can fix that once in devuan or you fix it in *all* maemo pieces and even then it won't work as expected | 07:27 |
*** DocScrutinizer05 has quit IRC | 07:44 | |
*** DocScrutinizer05 has joined #maemo | 07:44 | |
*** at1as has joined #maemo | 07:47 | |
*** frals has quit IRC | 07:47 | |
KotCzarny | regarding partitions, on android it mounts partitions by-name | 07:56 |
KotCzarny | so it detects names first, then mounts what's needed | 07:57 |
DocScrutinizer05 | I'd first port new kernel from devuan to maemo and try how far that gets when installed and started on target platform. Should reach loading of PID1 which initially is messybox in fremantle. Then you probably need a glibc built with legacy ABI upward to apps but built against API of new kernel. You then might get PID1 actually starting and running into kernel API incompatibilities e.g. in /dev/* and /sys/ and /proc/, for which you may | 08:05 |
DocScrutinizer05 | implement simple (deprecated for future use) janus stubs to link /sys/obsolete/legacy -> /sys/new/leete, possibly with a driver in between to convert the semantics and/or syntax. Then you'll notice some 'proprietary' kernel device drivers are not yet there in Devuan so you might port those to new kernel. Once all that done, you actually could start replacing resp upgrading stuff to Devuan part by part, like cli programs in /bin/ /sbin/ | 08:05 |
DocScrutinizer05 | etc, and finally maybe even make busybox based "upstart" init system of maemo just one process started under the genuine Devuan init system, whatever you choose for that | 08:05 |
DocScrutinizer05 | in the end you'll have a set of files to install on top of a regular devuan, and that set of files implements a complete maemo running 'inside' devuan | 08:09 |
*** frals has joined #maemo | 08:23 | |
*** arcean has joined #maemo | 08:45 | |
freemangordon | DocScrutinizer05: "port new kernel from devuan to maemo" doesn't make much of a sense, since we already kind of have that, on n900 | 09:06 |
freemangordon | also, most of Fremantle API is dbus based, so "porting" is a matter of either implementing missing dbus services or fixing existing users to use upstream ones | 09:08 |
Maxdamantus | I'd imagine Debian/Devuan wouldn't use a very special kernel. | 09:09 |
freemangordon | :nod: | 09:09 |
* Maxdamantus just uses his own kernels with his Debian machines. | 09:10 | |
Maxdamantus | usually all you have to do is have a particular filesystem as your root then exec /sbin/init as pid 1. | 09:10 |
*** handaxe has quit IRC | 09:11 | |
Maxdamantus | (for typical Linux-based systems) | 09:11 |
freemangordon | what worries me much ATM, is that gtk3 h-d uses ~100MB of RAM when started | 09:11 |
KotCzarny | soo, can we please stay with gtk2? | 09:12 |
KotCzarny | :) | 09:12 |
freemangordon | we may end up like that, yes | 09:12 |
freemangordon | KotCzarny: but, that high memory usage might be some bug i've introduced, see https://ubuntu-mate.org/blog/mate-desktop-gtk2-vs-gtk3-memory-consumption/ | 09:14 |
KotCzarny | uhum | 09:16 |
KotCzarny | what worries me a bit, it's transitional period where both toolkits are in use | 09:19 |
KotCzarny | as not all apps are ported to gtk3, and some will never be | 09:19 |
freemangordon | lets decide on that after I've replaced tidy with mx | 09:19 |
KotCzarny | another factor to consider is toolkit speed, since gtk3 is css based, it might be slower | 09:22 |
freemangordon | KotCzarny: I am not sure right now we use any css in h-d | 09:25 |
KotCzarny | themes/config in h-d are defined via css | 09:26 |
KotCzarny | s/h-d/gtk3/ | 09:26 |
infobot | KotCzarny meant: themes/config in gtk3 are defined via css | 09:26 |
Maxdamantus | Let's just settle on dwm. | 09:27 |
KotCzarny | best test case will be machine set to some low speed and comparing | 09:28 |
freemangordon | KotCzarny: iiuc h-d itself has hardcoded image files names and hardcoded element distances | 09:28 |
KotCzarny | do you have gtk2's version of h-d handy for comparisons? | 09:29 |
KotCzarny | (to be ran on same machine) | 09:29 |
freemangordon | no | 09:31 |
KotCzarny | oh, wow.. gtk 4.0 | 09:31 |
KotCzarny | Each 6 months, the new release (Gtk 4.2, Gtk 4.4, Gtk 4.6) will break API and ABI vs. the release that came before it. | 09:32 |
KotCzarny | https://blogs.gnome.org/desrt/2016/06/13/gtk-4-0-is-not-gtk-4/ | 09:32 |
bencoh | oO | 09:33 |
KotCzarny | The first “API stable” version under this new scheme is likely to be something like Gtk 3.26. | 09:33 |
KotCzarny | maybe just stick to gtk2 and f*ck it all | 09:35 |
freemangordon | yes, it may end up like that | 09:35 |
freemangordon | KotCzarny: I don't have gtk2 h-d on the smae machine, but I have xfce4 | 09:36 |
KotCzarny | fmg, what is missing from gtk2 that gtk3 has? | 09:37 |
freemangordon | KotCzarny: touch support I guess | 09:37 |
KotCzarny | panned area is already done i think | 09:37 |
freemangordon | in maemo gtk? yes | 09:37 |
freemangordon | but it is not the same as upstream gtk2 | 09:38 |
KotCzarny | it should work automatically because its a framework | 09:38 |
freemangordon | what should work automatically? | 09:38 |
KotCzarny | so no need to rewrite apps to support scroll-via-gesture | 09:38 |
KotCzarny | and since gtk2 wouldnt seen plenty of future releases and maemo-gtk2 is drop in compatible with gtk2 | 09:40 |
KotCzarny | maybe just forward port them to latest gtk2 version ? | 09:40 |
KotCzarny | there is a chance there wouldnt be much to fix | 09:41 |
KotCzarny | s/seen/see/ | 09:41 |
DocScrutinizer05 | freemangordon: sure, don't take meaning of my "porting" as a huge work package, for kernel it's just "install the recent kernel (as it's also used in Devuan) to a stock fremantle" | 10:09 |
freemangordon | and we already did that :) | 10:09 |
DocScrutinizer05 | sure | 10:10 |
DocScrutinizer05 | :-) | 10:10 |
DocScrutinizer05 | I think I already mentioned it: the desired end result is absolutely identical for your and my approach. Just your is to lift maemo building blocks one by one onto the Devuan level while mine is dropping Devuan building block one by one down into the maemo level. The core difference is that lifting is prolly more effort than dropping. The result is 100% identical in the end | 10:13 |
freemangordon | yes, I see your point. But what I think is the problem with it, is that we can't put maemo patched gtk2 for example on devuan servers | 10:16 |
DocScrutinizer05 | hmm, that's a whole new aspect | 10:17 |
freemangordon | and I still insist that without upstream support, maemo is dead | 10:17 |
DocScrutinizer05 | sure | 10:17 |
freemangordon | yeas I know, but we should consider it | 10:17 |
KotCzarny | fmg: why not? | 10:17 |
KotCzarny | libjpegturbo coexists with libjpeg | 10:17 |
KotCzarny | and both target same api | 10:17 |
freemangordon | no libjepg in devuan, only turbo :) | 10:17 |
DocScrutinizer05 | of course. Everything relevant needs consideration. I just never thought of that | 10:18 |
KotCzarny | see? | 10:18 |
KotCzarny | then we will have maemogtk2 instaed of gtk2 in devuan at some point | 10:18 |
KotCzarny | :) | 10:18 |
KotCzarny | but it must be drop-in compatible | 10:18 |
freemangordon | KotCzarny: do you have maemo libjpeg sources? | 10:18 |
freemangordon | as I don;t | 10:18 |
DocScrutinizer05 | o.O | 10:19 |
DocScrutinizer05 | duh! | 10:19 |
KotCzarny | nono, it was an example that two libs share same api | 10:19 |
KotCzarny | and apps can be compiled without changes against any of them | 10:19 |
freemangordon | maemo gtk is not ABI/API compatible with upstream gtk | 10:19 |
freemangordon | so is maemo clutter, etc | 10:20 |
KotCzarny | hrm | 10:20 |
DocScrutinizer05 | wut? freaking weirdos @ Nokla | 10:20 |
freemangordon | don't ask me :) | 10:20 |
freemangordon | anyway, time to go to work | 10:21 |
*** florian has joined #maemo | 10:22 | |
*** geaaru has joined #maemo | 10:50 | |
*** ceene has quit IRC | 11:10 | |
*** ceene has joined #maemo | 11:19 | |
*** silviof has quit IRC | 11:55 | |
*** N-Mi_ has joined #maemo | 12:29 | |
Wizzup | freemangordon: I wouldn't worry too much about initial ram usage, I'm sure it can be reduced quite a bit | 12:42 |
DocScrutinizer05 | optimizing speed, sure. but optimizing a fubar data model, I've not seen that ever really fly | 13:17 |
Wizzup | How is gtk3 worse than gtk2? | 13:18 |
Maxdamantus | Wirth's law. | 13:18 |
Wizzup | *shrug* when it comes to widgetsets, you better just keep up with newer releases, or you're stuck with unsupported versions. I don't believe that gtk3 will use to much more ram that it's unsuitable | 13:19 |
KotCzarny | multiple toolkits, ahoy! | 13:20 |
Wizzup | KotCzarny: what do you even mean? | 13:21 |
KotCzarny | if you have os using gtk3, but apps use gtk2 you must load both libs | 13:21 |
Wizzup | Yes, and? | 13:21 |
Wizzup | It's not like qt isn't loaded often as well on the n900 atm | 13:22 |
Wizzup | Imagine not being able to use multiple widget sets at all | 13:22 |
*** louisdk has joined #maemo | 13:27 | |
*** Pali has joined #maemo | 13:55 | |
*** zGrr has joined #maemo | 13:57 | |
*** silviof has joined #maemo | 14:42 | |
*** louisdk has quit IRC | 14:59 | |
*** jskarvad has joined #maemo | 15:20 | |
* ceene testing hexchat... | 15:21 | |
*** sunshavi has quit IRC | 15:43 | |
*** heroux has quit IRC | 15:59 | |
*** at1as has quit IRC | 16:06 | |
*** dreamer has quit IRC | 16:19 | |
*** dreamer has joined #maemo | 16:19 | |
*** heroux has joined #maemo | 16:22 | |
*** arcean has quit IRC | 16:52 | |
*** florian has quit IRC | 17:15 | |
*** L29Ah has left #maemo | 17:27 | |
*** cebreidian_ has quit IRC | 17:30 | |
*** L29Ah has joined #maemo | 17:41 | |
*** Trizt has quit IRC | 17:50 | |
*** Trizt has joined #maemo | 17:52 | |
*** L29Ah has left #maemo | 17:56 | |
*** at1as has joined #maemo | 18:05 | |
pkill9 | anyone know how to fix/replace a dead vibration motor in the N900? and where to get a replacement? | 19:09 |
KotCzarny | google n900 service manual level 3 or something | 19:10 |
KotCzarny | another broken n900 is a good source of spare parts | 19:11 |
*** sunshavi has joined #maemo | 19:35 | |
*** dimw1t has joined #maemo | 19:38 | |
*** at1as has quit IRC | 19:38 | |
*** N-Mi_ has quit IRC | 19:55 | |
*** L29Ah has joined #maemo | 19:58 | |
*** dimw1t has quit IRC | 20:03 | |
*** at1as has joined #maemo | 20:06 | |
*** L29Ah has left #maemo | 20:07 | |
*** at1as has quit IRC | 20:13 | |
*** L29Ah has joined #maemo | 20:21 | |
*** L29Ah has quit IRC | 20:42 | |
*** florian has joined #maemo | 20:59 | |
*** Timo has joined #maemo | 21:10 | |
*** Vajb has quit IRC | 21:14 | |
*** ced117 has joined #maemo | 21:16 | |
*** geaaru has quit IRC | 21:29 | |
*** Vajb has joined #maemo | 21:31 | |
freemangordon | Wizzup: not sure, but will see once I replace tidy with mx | 21:35 |
freemangordon | otherwise I can't see how it can be reduced | 21:35 |
freemangordon | hmm, wait, maemo-launcher that is ;) | 21:36 |
*** erstazi has quit IRC | 21:39 | |
Pali | freemangordon: your omapfb patch which reserve memory fails in qemu on error: omapfb: dma_declare_coherent_memory failed | 21:42 |
KotCzarny | needs newer qemu? no cma enabled? bad kernel params? | 21:42 |
freemangordon | Pali: could be, dma_declare... semantics changed in 4.7 ot 4.8 iirc | 21:45 |
freemangordon | Pali: could I have the error | 21:45 |
freemangordon | -EINVAL? | 21:46 |
Pali | stacktrace | 21:46 |
freemangordon | no, just the error code | 21:46 |
Pali | memremap attempted on ram 0x8f800000 size: 0x700000 | 21:46 |
freemangordon | I should have patched that :( | 21:47 |
Pali | relevant part: http://pastebin.com/1CYQ75N2 | 21:47 |
Pali | maybe I do not have last version of your patch? | 21:47 |
freemangordon | could be | 21:48 |
freemangordon | is it the same as https://github.com/freemangordon/linux-n900/commit/259f17b2b2cdad6a0a0c106d9c10a7f1dee04729 ? | 21:48 |
*** slobber has left #maemo | 21:48 | |
freemangordon | I think you have the version with DMA_MEMORY_IO instead of DMA_MEMORY_EXCLUSIVE | 21:48 |
freemangordon | or somesuch | 21:48 |
freemangordon | Pali: which patch do you have? | 21:49 |
freemangordon | oh, and it was failing for > 2MB, something config has to be changed | 21:50 |
freemangordon | Pali: https://github.com/freemangordon/linux-n900/commit/a068c200c32dafa98a403312102ca198c125924f | 21:50 |
freemangordon | Pali: you definitely have old version of the patch :) | 21:51 |
freemangordon | Pali: still here?!? | 21:51 |
*** ecc3g has quit IRC | 21:52 | |
*** jskarvad has quit IRC | 21:52 | |
freemangordon | hmm, gtk h-d seems to leak, besides initial high memory usage | 21:52 |
Pali | freemangordon: I'm on #armlinux too :-) | 21:52 |
*** ecc3g has joined #maemo | 21:52 | |
Pali | I will try compare that path | 21:53 |
Pali | with current one | 21:54 |
*** clopez has quit IRC | 21:56 | |
*** erstazi has joined #maemo | 21:57 | |
*** clopez has joined #maemo | 21:59 | |
*** erstazi has quit IRC | 22:04 | |
*** erstazi has joined #maemo | 22:05 | |
*** Trizt has quit IRC | 22:19 | |
*** Trizt has joined #maemo | 22:21 | |
*** rm_work has quit IRC | 22:34 | |
*** rm_work has joined #maemo | 22:34 | |
Pali | freemangordon: older version with tidspbridge support... | 22:52 |
Pali | now going to update it to with that new commit | 22:53 |
Pali | yes, that version fixes it | 22:58 |
Wizzup | MoeIcenowy: freemangordon: where did you get the mali binary? | 23:06 |
Wizzup | wait, /me will rtfm the wiki | 23:06 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!