<noch>
sicelo, i3 is ok, as well as dwm, as well as anything. i just need a modern kernel running on it, modern libraries, and x.
<norly>
noch: maybe raspbian as a start, since that is armv6hf? with standard debian/devuan, you're stuck with armv5 non-hf.
<noch>
hmmm... interesting. i did not know that debian doesn't have armv6hf. if i do something, i'll do it with gentoo ecosystem, which i understand.
<noch>
thank you!
<noch>
though raspbian must be easy. so i take the rootfs, open it on sdcard
<noch>
and i configure the u-boot to boot the kernel i want.
<noch>
hmmm, need to try it.
<noch>
and no need to build anything.
<noch>
except, probably, kernel.
<noch>
no idea if u-boot on n810 can boot a kernel from the sdcard. i think it could. but i also can place a kernel in emmc and tell it to mount the system on sdcard.
<buZz>
was there ever something changed on kexecboot to allow 'charging when not really full enough to boot' to happen inside that?
* buZz
tries booting to android from kexecboot to see what happens there
<buZz>
considering just adding breakout wires to the battery to use some external charger :P
<buZz>
seems i destroyed my android install :P hehe
<buZz>
actually, i wonder if maybe battery contacts are loose? hmm
Daaanct12 is now known as Danct12
noidea_ has joined #maemo-leste
pere has quit [Ping timeout: 246 seconds]
xmn has joined #maemo-leste
uvos has joined #maemo-leste
noch has quit [Ping timeout: 256 seconds]
norayr has joined #maemo-leste
ceene has quit [Remote host closed the connection]
reinob has joined #maemo-leste
sixwheeledbeast has left #maemo-leste [Leaving.]
sixwheeledbeast has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
Pali has joined #maemo-leste
Twig has joined #maemo-leste
Twig has quit [Ping timeout: 272 seconds]
pere has joined #maemo-leste
Twig has joined #maemo-leste
norayr has joined #maemo-leste
uvos has quit [Ping timeout: 250 seconds]
<buZz>
alright, finally got it somewhat charged enough to boot into proper charging :P
<buZz>
seems that apt update; apt upgrade broke wifi though :P will try the wifi-calibration later
vagag has joined #maemo-leste
<sicelo>
buZz: at this point i'm not sure which has better behavior for charging from extremely depleted battery, if you don't have access to special equipment (e.g. bench power supply) - N900 vs. Droid 4
<bencoh>
I experienced the issue with droid4 (it probably wasn't really depleted though) and it was kinda funky
<bencoh>
I think it somehow booted when I plugged it in, but apparently stopped charging early, because when I tried booting afterwards leste showed an empty battery and quickly powered off
<bencoh>
after that it refused charging until I hw-reset it (power+volume) and booted to emergency shell
Twig has quit [Ping timeout: 256 seconds]
<buZz>
yeah 'usb condom' charging is needed for a while for me, its ~50mA and drops off all the time
<buZz>
need to trickle some power into droid4 with a couple cycles of that 50mA charging, until its charged enough to survive booting into linux :P
uvos has joined #maemo-leste
<buZz>
i think, a lot of specifically the droid4 issues could be handled if kexecboot could do 'if <some % battery, stick in a loop with charger enabled and display some msg'
<uvos>
it dose this on bionic
<uvos>
yeah the d4 has some issues with the boot taking to long
<uvos>
android boots very fast and enables pm features very fast
<uvos>
mbm/cpcap assumes the os will do so
<buZz>
yeah indeed, droid4, when booting with power already connected, doesnt even enable charging for me
<uvos>
but mainline + kexecboto is way to slow
<buZz>
i need to unplug & replug power before it'll charge
<uvos>
kernel?
<uvos>
there was a kernel bug that did this for a short time
<uvos>
it should work very realiably now
<buZz>
ah eh , not sure, whatever latest on leste
<uvos>
besides being underdischarged
<buZz>
but, as my wifi is broken now, i might just reinstall from image
<uvos>
also underdischarging should be avoided mostly
<uvos>
since we power off early
<uvos>
but if you leave it in a cuppobord for a while it will still do it
<uvos>
the mainline kernel fails to shutdown the device fully
<uvos>
we dont know what remains on but something draws about a mw
<uvos>
so if your going to store the device for some time
<uvos>
shut it down with android/kexecboot menu
<uvos>
nothing changed with wifi
<uvos>
so thats akward
<uvos>
what image is this?
<uvos>
oh i missread this
<uvos>
wifi is broken after an upgrade?
<buZz>
hehe yeah , the internetconnections menu in hildon shows no networks
<uvos>
ok so its just icd thats broken
<uvos>
ie wpa_cli works?
norayr has left #maemo-leste [Error from remote client]
<buZz>
lets see
<uvos>
also check if the modules are loaded pfc
<uvos>
ofc
<buZz>
wifi menus now appeared in menu ! after a long time of being booted
<buZz>
not sure wtf
<uvos>
hmm ok
<buZz>
-touchscreen- also stopped working :D so rebooting
<uvos>
no
<uvos>
just turn the screen off and on again
<uvos>
thats a hw bug
<buZz>
i did couple times, didnt fix anything
<uvos>
hmm ok
vagag has left #maemo-leste [Error from remote client]
<sicelo>
it's a known issue, and you see it easily when you don't have autoconnect to wifi set. at least i know i've mentioned it before.
norayr has joined #maemo-leste
<buZz>
yeah 'not charging when booting droid4 with power already connected' is still there for me
<buZz>
maybe i'll reinstall image
<buZz>
but , wifi has connected
mardy has quit [Quit: WeeChat 2.8]
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
<sicelo>
Wizzup: i hope/suppose this one doesn't affect N900 debug LEDs? "Subject: [PATCH 18/41] ARM: omap: remove debug-leds driver" - From: Arnd Bergmann <arnd@kernel.org>