ceene has quit [Read error: Connection reset by peer]
_CN_ has joined #maemo-leste
arno11 has joined #maemo-leste
<Wizzup>
arno11: didn't we verify that even 'sw' wasn't enough, or?
<Wizzup>
I think booting a new image with verbose logging/serial might help, otherwise we can add some potential hack
Juest has joined #maemo-leste
<arno11>
Wizzup: i've just doublechecked on Debian.org (and ubuntu official doc) and sw seems necessary to enable swap (but not to create the partition)
<arno11>
i tried to add sw on my config and it works (to activate swap)
<arno11>
but we need to try from a fresh install...
<Wizzup>
so we need to dd, mount the sd card, add sw, then do first boot
<Wizzup>
technically the one time mount could make a difference, but maybe we want to rule that out for now
<arno11>
To be 100% sure (and avoiding bias) i think we should make a new N900image (with sw in postinst script), then dd and doing first boot
<Wizzup>
that will be the next step I think
<arno11>
i already tried this: completely remove swap (swapoff and fstab cleared) then reboot, then add a new fstab line without sw and...it works. So the problem is really during install/first boot
<arno11>
but if you want to try the first step, i have a sd card ready for this
<arno11>
i just need the process to add sw before the first boot
<Wizzup>
yes, that seems like a good step imo
<arno11>
ok :)
<arno11>
* dd new image
<arno11>
image ok and mounted on my desktop machine
<arno11>
postinstall script modified
<arno11>
i'll try to boot and see :)
<arno11>
booting
<arno11>
swap not activated
<arno11>
i'll check fstab
<arno11>
ah the script didn't work
<Wizzup>
what script?
<Wizzup>
oh
<Wizzup>
I see
<Wizzup>
uh
<arno11>
postinst
<Wizzup>
the postinstall won't do anything on boot
<Wizzup>
that should run in the image
<Wizzup>
wait, so the swap line isn't in etc/fstab when you dd the image?
<arno11>
exactly
<Wizzup>
ooooooooooooooooooooooo
<Wizzup>
can you add the line before first boot, either with 'sw' or 'defaults (or default I don't remember) and sahre if it works then?
<arno11>
you mean in fstab ?
<Wizzup>
yes
<arno11>
ok (just to be sure), let's go
<Wizzup>
make sure you use tabs of whatever fstab wants
<Wizzup>
(so that it can parse the line)
<arno11>
yep
<dsc_>
fstab is not a makefile :D
<dsc_>
dont think the tabs matter hehe
fab_ has joined #maemo-leste
<arno11>
fstab edited, booting on the device
<Wizzup>
dsc_: it does very much actually :)
<dsc_>
hmm
<arno11>
it works :) and make a HUUUUGE difference on first boot
<arno11>
/dev/mmcblk1p3 swap swap sw 0 0
<Wizzup>
great, so somehow arm-sdk overwrites the etc/fstab or the postinst doesn't work well
<Wizzup>
in any case we can work around this easily
<freemangordon>
does parazyd still support it?
<Wizzup>
I support it
<freemangordon>
ok
<Wizzup>
arno11: ty
<arno11>
no probs
<arno11>
ah and IMO we must modify swappiness a bit
<arno11>
30 is good and works well (with not too much things moved in swap and enough ram available)
<arno11>
60 by default is too much, specially if the sd card is a bit low
<freemangordon>
arno11: with swap on emmc, sdcard speed should not matter :)
<arno11>
pfff lol indeed
<freemangordon>
and yes, I am using 30 on fremantle for the last 10 years or so
<freemangordon>
so this should be the default, at least on n900
<arno11>
yes
<freemangordon>
ttyl
mdz has joined #maemo-leste
<mdz>
can anyone help me with 2G internet not working on N900?
<mdz>
also i am having trouble with phone app not really working, I understand that all of this is still in alpha but on the wiki its listed as working
<arno11>
mdz: hi
<arno11>
you need to upgrade to devel first
<arno11>
and phone is working 'manually'
<arno11>
not out of the box
<mdz>
wdym by manually?
<arno11>
you need to edit pulse/daemon.conf and run manually cmtspeech to be able to use phone functionalities
<arno11>
anyway it is better to wait a bit to try it
<mdz>
also any ideas on the cellular int not working?
<arno11>
you mean 2G data or?
<Wizzup>
mdz: is there 2g in your area? just checking
<mdz>
weird thing is that its trying to connect but fails to recive dhcp settings
<mdz>
yeah 2G data
<Wizzup>
so you are on the network, but gprs doesn't work
<Wizzup>
ok
<arno11>
ah
<Wizzup>
I *think* sicelo fixed this, and yes the fix should be in the -devel repos
<arno11>
you probably need to activate roaming
<arno11>
i mean data roaming
<mdz>
also still have the Maemo 5 working and thats able to connect to 2.5G net
<arno11>
ok let me check something
<mdz>
so dunno whats up withmthat
<mdz>
but thanks for the devel repos advice will upgrade to that
<Wizzup>
I think the iproute2 change + libicd-network-ofono pull request from recent days fixes this
<arno11>
maybe it can allow d4 to play higher res videos
<freemangordon>
Wizzup: yes, it is
<freemangordon>
but share the same problems with n900
<freemangordon>
like glimagesink not working
<Wizzup>
right
<freemangordon>
along with qtqmlwidget not working
<freemangordon>
like, unfortunately, we shall forget about 16bpp
<dsc_>
can it also be set to 8bit?
<freemangordon>
and find a way to speed-up 24bpp
<freemangordon>
dri3 it is
<freemangordon>
but I want to finish OMP as much as I can
<freemangordon>
first
<Wizzup>
freemangordon: so the always on top made it work for our leste programs
<freemangordon>
but that's a hack
<arno11>
but it works :P
<freemangordon>
but is a hack
<freemangordon>
and does not help glimagesink
<freemangordon>
see, I want 16bpp sisnce we started the project
<freemangordon>
*since
<freemangordon>
but we have too many applications not working properly
<freemangordon>
also, n900 was way faster with older blobs and omapfb
<arno11>
i think that's a key point
<freemangordon>
and at some point I had modesetting/glamor working, but then I hit omapdrm fences bug (whatever it is) and back then I didn;t know what the issue is
<freemangordon>
but with ms/glamor it was faster
<freemangordon>
not to say I made glamor replacement, that is using PVR blobs directly
<freemangordon>
that should be even faster
<freemangordon>
OTOH, I am not sure when would be ther right time to get back to it
<freemangordon>
given the pile of pending tasks :(
<Wizzup>
I think there are a few other things to take care of first year
<freemangordon>
mhm
<Wizzup>
s/year/yeah/
fab_ has quit [Ping timeout: 260 seconds]
<arno11>
Wizzup: what about light transitions ? IMO they are essential in a fresh install ATM. (i mean for calls and to not wait at least 45 sec to open a qt5 app...)
<arno11>
not really user-friendly without that
rafael2k has quit [Remote host closed the connection]
rafael2k has joined #maemo-leste
<Wizzup>
arno11: so the transitions cause this 45s startup delay?
<Wizzup>
arno11: let's first check if swap works now :)
<arno11>
i think zoom and animations are blocking apps startup
<arno11>
but it is really depending of the sd card type too
<Wizzup>
hm, maybe some shader compilation?
<arno11>
with U3, ootb around 12 sec to start qt5 app
pere has quit [Ping timeout: 255 seconds]
<arno11>
and far better with no zoom/animations
<arno11>
once we are ok with swap, i'll dd and boot the same img with all tweaks included to see how it runs ootb
<Wizzup>
ok, great, I hope to finally get my leste n900 going again
<Wizzup>
I have a few other n900's here, one should work at least
<arno11>
ok
<freemangordon>
afaik qml does shaders cache
<freemangordon>
but transitions duration should not affect that
fab_ has joined #maemo-leste
<arno11>
that's not transitions duration itself but zoom/animation deactivation that helps imo
<arno11>
from what i see in my device, transitions.ini file is not only affecting qt5 apps but it's slowing down the entire device (like Fremantle with no cssu in fact)
rafael2k has quit [Ping timeout: 252 seconds]
slep has left #maemo-leste [#maemo-leste]
slep has joined #maemo-leste
pere has joined #maemo-leste
akossh has joined #maemo-leste
mdz has quit [Ping timeout: 268 seconds]
<Wizzup>
arno11: the image is built
<arno11>
currently dd it :)
<arno11>
3 min remaining before first boot
<Wizzup>
:)
<arno11>
let's check fstab first
<arno11>
arghhh it seems erased
<Wizzup>
wtf
<arno11>
don't know
<Wizzup>
ok, I'll just keep trying to fix this until it works, I can build on my machine
<arno11>
ok cool
<arno11>
(i'm trying a first boot with tweaks to see how it works)
<Wizzup>
I guess skip_arm_device_root was set somehow?
<Wizzup>
arg we set it in our config
<Wizzup>
for n900
<Wizzup>
ok mystery solved...
<arno11>
ah
<Wizzup>
building again
<arno11>
ok
<arno11>
fingers crossed
<Wizzup>
this is it I'm pretty sure :)
<arno11>
cool :)
<Wizzup>
now let me see if I can get a n900 going again here
<arno11>
yep
akossh has quit [Ping timeout: 255 seconds]
<Wizzup>
looking forward, the only thing the generic-root copying gives us is an rc.local that generates a ssh-key on boot, a sshd_config and a etc/fstab that gets modified with the boot device
<Wizzup>
and zram by default
<Wizzup>
imo zram should be a pkg, not in there by default
<Wizzup>
the rc.local + ssh key generation I am not sure, doesn't debian generate host keys by default?
<arno11>
no idea
akossh has joined #maemo-leste
<arno11>
not 100% sure but seems automatically generated