<Wizzup>
uvos: do you need me to fix the dtb situation, or?
Daanct12 has joined #maemo-leste
crab has quit [Server closed connection]
crab has joined #maemo-leste
ahmed_sam has quit [Remote host closed the connection]
ahmed_sam has joined #maemo-leste
pr0ton has joined #maemo-leste
joerg has quit [Ping timeout: 246 seconds]
joerg has joined #maemo-leste
<freemangordon>
Wizzup: do we have any plans to upgrade to current stable?
<freemangordon>
bookworm that is
<freemangordon>
Wizzup: so, you say there is "unknown album" in OMP, but there are no songs in it?
<freemangordon>
that could be a tracker issue
ceene has joined #maemo-leste
<tmlind>
uvos: weird that cpufreq has disappeared
<tmlind>
what, we maybe get mainline mesa for pvr?
<freemangordon>
tmlind: looks like
<tmlind>
nice :)
antranigv has quit [Ping timeout: 240 seconds]
vahag has quit [Ping timeout: 240 seconds]
norayr has quit [Ping timeout: 240 seconds]
maxwelld has quit [Ping timeout: 246 seconds]
Twig has joined #maemo-leste
jrayhawk has quit [Server closed connection]
jrayhawk has joined #maemo-leste
gnarface has quit [Server closed connection]
gnarface has joined #maemo-leste
Twig has quit [Ping timeout: 246 seconds]
antranigv has joined #maemo-leste
<uvos>
tmlind: is it the same on your device?
<tmlind>
uvos: what is missing for you? i can do cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq just fine looks like
<uvos>
yeah thats missing
<uvos>
ok something got clobbered in the merge then
<tmlind>
sure you have up to date dtb installed?
<uvos>
yeah
akossh has joined #maemo-leste
<tmlind>
and the cpufreq whatever dt .ko is loaded?
<uvos>
yes its loaded
<tmlind>
weird
<uvos>
it also dosent seam to affect pm, but then again i gues cpufreq only helps when there is partial load
<uvos>
not at idle
<tmlind>
yeah if voltage gets scaled..
ceene has quit [Read error: Connection reset by peer]
ceene has joined #maemo-leste
ac_laptop has joined #maemo-leste
<ac_laptop>
Hello people
<ac_laptop>
there is *definitely* something wrong with my leste install concerning the battery
<ac_laptop>
I've let the device charge all night, when I woke up it was off, I boot it on leste, it boots and says the battery is empty
<ac_laptop>
I replace the battery with an other battery **that I had fully charged the day before**, I boot on leste, it says the battery is empty.
<ac_laptop>
I reboot on fremantle, it shows a full battery.
<ac_laptop>
I suspect maemo sometimes shows me an empty battery when it's actually full (or at least not empty), and shutw down as a security measure
<ac_laptop>
(maemo leste)
<ac_laptop>
I don't know if the battery is not properly calibrated or if something happens when the device is plugged that messes up battery calibration
arno11 has joined #maemo-leste
<arno11>
ac_laptop: showing an empty battery when it's full is normal if the battery is not calibrated at all. You need 5-10 cycles to get accurate battery data
<arno11>
*full cycles
<ac_laptop>
arno11: I'm going to do this then. I guess I need to start leste while the device is plugged, wait for a full charge, and then stress it until the battery is empty, and repeat ?
<ac_laptop>
what's the fastest way to empty the battery then ?
<arno11>
i recommend you to not plug the battery before booting Leste
<arno11>
it's buggy on n900
<ac_laptop>
arno11: the thins is, leste believes the battery is empty, right after X is started, it doesn't eve have the time to show all the applets on the desktop, and shots down
<ac_laptop>
thing*
<ac_laptop>
shuts*
<arno11>
ok
<arno11>
weird
<ac_laptop>
arno11: I guess battery management shutw down the device when it detects the battery is empty ? as a security measure ?
<arno11>
yes iirc but don't really know how it works if the battery is not calibrated
<arno11>
maybe better to start over with a fresh install ?
<ac_laptop>
arno11: it is a fresh install
<arno11>
ok lol
<arno11>
i really don't know what's going on. i've never seen this kind of issue (i'm using 2 original batteries)
<arno11>
for me it is battery related but maybe someone else has another idea
<arno11>
or maybe something else is shuting down the device
<arno11>
*shutting
<arno11>
is swap activated on your device ?
<arno11>
file system expanded ?
<arno11>
Was wifi off before the last clean shutdown?
<arno11>
And which image did you use ?
<arno11>
or is it a completely new fresh install and first boot ?
<arno11>
(i ask these questions because maybe we are OOM using last images if swap is still not activated on boot)
<ac_laptop>
arno11: swap is activated, fs is custom-expanded (I grew the partition to 8G), wifi was on the whole time and connected to my network, image is maemo-leste-1.0-armhf-n900-20231112.img
<ac_laptop>
arno11: and it's not first boot, the install was yesterday
<arno11>
ok
<ac_laptop>
arno11:the OOM at first boot is something I've experienced, but it has nothing to do with the battery
<arno11>
that's not what i'm saying, just symptoms could be similar
uvos__ has joined #maemo-leste
<uvos__>
we are oom on boot on n900 what!?
<uvos__>
the only thing we added recently is mafw stuff i think
<ac_laptop>
uvos__: happened to me with the first install on my U1 card. It didn't happen with the U3 card though
<uvos__>
hmm the sdcard is not related to bein oom
<Wizzup>
freemangordon: ugh @ bookworm, I am not sure
<uvos__>
or do you mean you where out of disk space?
<uvos__>
being out of disk space on boot is a solvable problem
<uvos__>
we can just bump the image size a bit
<Wizzup>
freemangordon: it's a multi month project and I wouldn't like to embark on it now. We should see if itremoves any sw that we depend on, like gtk2 or gconf
<Wizzup>
They probably remove python2 all together
<arno11>
Wizzup: need your help to check if emmc swap is really activated on boot
<Wizzup>
wait, still catching up on backlog :)
<Wizzup>
best share contents of /etc/fstab first
<ac_laptop>
uvos__: I don't know exactly what happened, it shut down immediately after first boot, either it was because of the lack of swap, or because of the lack of disk space, I suppose
<uvos__>
it would not shutdown on ether of those
<uvos__>
being out of disk space can cause wierd issues, but not a shutdown
<Wizzup>
disk full can cause a reboot in some cases
<uvos__>
bein out of ram would have caused the ire of the oom killer
<uvos__>
Wizzup: really? how
<uvos__>
dont we run with dsmes reboots disabled?
<ac_laptop>
uvos__: an Xorg crash causes a shutdown, and I suppose a lack of disk space could cause an Xorg crash
<uvos__>
xorg crash should not cause a shutdown
<uvos__>
we disable lifeguard iirc
<ac_laptop>
uvos__: what should it cause ? there's no tty
<uvos__>
ofc there is tty
<ac_laptop>
I can't get access to it, even when killing Xorg
<uvos__>
chvt 2
<Wizzup>
uvos__: oh, that is right @ dsme reboot disabled
<uvos__>
yeah so a reboot would be very wierd
<Wizzup>
freemangordon: to bookworm to me seems a while off, I would say let's get in beta first and then worry about it
<Wizzup>
because no python2 means no gtk2 for python at all
<Wizzup>
which means we need gtk3 or write our own python gtk2 bindings (afaict)
<uvos__>
do we have anything that uses gtk2 via python even?
<Wizzup>
yes
<uvos__>
or are you concerned about porting comunity pacakges?
<uvos__>
what package?
<Wizzup>
some stuff of hildon I think
<Wizzup>
but also community stuffyes
<Wizzup>
brb
maxwelld has joined #maemo-leste
Blikje has quit [Server closed connection]
Blikje has joined #maemo-leste
<ac_laptop>
uvos__: had to do it as root, but it works, thanks !
<uvos__>
you can also do this via ssh or plug in a keyboard and do ctrl-alt-f2
ahmed_sam has quit [Read error: Connection reset by peer]
<uvos__>
er nvm n900 dosent have otg so you cant do the latter on n900
vectis has quit [Ping timeout: 246 seconds]
<arno11>
ac_laptop: i'm currently burning a new img on another usdcard to see what's going on with fresh install
<uvos__>
arno11: once you flashed, before booting, on pc, see if /etc/no_lg_reboots is present
<uvos__>
should be a empty file
<arno11>
argh already booting...any i'll start over to check later
<arno11>
*anyway
<uvos__>
check after boot
<arno11>
ok
<arno11>
(For the moment, everything is fine)
<arno11>
battery ok
<arno11>
ah something is buggy with the display
vectis has joined #maemo-leste
<arno11>
wow, first boot is always difficult but now really difficult to use after the first boot
<uvos__>
details pls
<arno11>
uvos: no_lg_reboots present and emty
<arno11>
now it's ok the device is usable, i forgot we have to wait at least 3-4 min to be able to use the desktop
<arno11>
ah swap is NOT activated
<uvos__>
arno11: ok
<arno11>
Wizzup: (for emmc swap) weird
buZz has quit [Server closed connection]
buZz has joined #maemo-leste
<arno11>
it explains extreme slowness on first boot and probably ac_laptop OOM
buZz is now known as Guest8004
<Wizzup>
arno11: what is the contents of /etc/fstab
<Wizzup>
arno11: can you run dpkg-reconfigure leste-config-n900 after looking, and look again
<arno11>
argh i already activated emmc swap otherwise it was difficult to use the device
<Wizzup>
arno11: nevermind
<Wizzup>
oh, you mean you added it yourself to /etc/fstab ?
<arno11>
yes
<Wizzup>
checking if it line exists in the image can be done without dding it again using loopback mount, but the real interesting thing is to check if it gets added (again) with dpkg-reconfigure leste-config-n900
<Wizzup>
I can't look into this right now, but clearly something is wrong
<arno11>
yep just wait a min
<uvos__>
but us ooming with out swap isent good either
<arno11>
5 min in fact :)
<uvos__>
maybe we should have a light hildon meta
<uvos__>
like without mafw maybe, and maybe some other stuff too
<uvos__>
i gues outgrowing the n900 is pretty inevitable
<uvos__>
but im suprised its so big allready
<arno11>
(to be honest, for a new user, first boot is a nightmare)
<uvos__>
on n900 anyways :)
<uvos__>
but its good to see n900 is getting some more testing
<arno11>
oh yes definitely
<uvos__>
it deffintaly allways suffers a bit from the d4 being the defacto referance platform
<arno11>
but to be positive, once configured correctly, everything is ok on n900
<arno11>
definitely need to tweak first boot
<arno11>
Wizzup: dpkg-reconfigure works
<Wizzup>
hm
<arno11>
and swap is visible
<Wizzup>
uvos__: fremantle will oom without swap too
<Wizzup>
256MB just isn't enough
<uvos__>
yeah but its some startup spike
<uvos__>
on leste atm
<uvos__>
my d4 uses <200mb ram with everything and some more stuff in installed running
Pali has joined #maemo-leste
<arno11>
power button is not working ?!?
<uvos__>
hmm like not at all?
<arno11>
yes
<uvos__>
evtest /dev/input/event*
<uvos__>
dose it register on the event device its on?
<arno11>
sorry already run shutdown command
<ac_laptop>
honestly I didn't know about the d4 before hearing about leste. Is the d4 good ? both as a device in general and in terms of leste support ? Alos is there a page listing the nonfree blobs needed on each platform ?
<uvos__>
ac_laptop: the nonfree blobs are exactly the same: pvrsgx
<uvos__>
ac_laptop: d4 is slow by modern standarts
<uvos__>
but its mutch mutch faster than n900, by 5x on the cpu side and it has 4x the ram
<arno11>
ok so on first reboot everything seems ok and usable
<uvos__>
its leste support is by far the best of all supported devices
<uvos__>
the only thing that dosent work is the camera, and that includes good power managment
Guest8004 is now known as buZz
<arno11>
bbl
<ac_laptop>
uvos__: the hardware specs are tempting indeed. Is the keyboard pleasant to use ? In terms of freedom I guess it's all the same, unsigned kernel, unsigned bootloader, modem separation ?
<uvos__>
if find the keyboard vastly superior to the n900
<uvos__>
its helped by the device being bigger
<uvos__>
the bootloader is singed, so is the n900s (nolo) iirc
<uvos__>
modem seperation is execlent
<uvos__>
its connected via usb and is powerless to do anything without the cpus help
<uvos__>
the booloader is however locked
<uvos__>
but this dosent matter to us as we found a very conveniant way to defeat
<uvos__>
it
<ac_laptop>
uvos__:ok i thought the bootloader was unsigned on both devices. how are you able to change it then ?
<uvos__>
on d4 the primary bootloader (mbm) boots a secondary bootloader thats unsigned
<uvos__>
on n900 its mostly the same the primary bootloader (nolo) boots a secondary bootloader (uboot)
<uvos__>
but the d4 has more fuckery going on
<uvos__>
becuase the primay bootloader checks the signature of what is booted
<uvos__>
but we defeat this
<uvos__>
to boot our secondary bootloader
<uvos__>
so it ends up the same in practice
<ac_laptop>
oh but it's a capacitive screen I guess
<ac_laptop>
since it's an android
<uvos__>
yes
<sicelo>
ac_laptop: you charge the battery outside the device?
<uvos__>
imo its mutch better than the n900s ts, with not having the option of a stylus being the only downside
<ac_laptop>
sicelo: no, I charge the battery with the device, although both of the batteries have been charged yesterday with the device booted on fremantle, not leste
<uvos__>
but for thumb useage is vastly superior
<uvos__>
also you have multitouch gestures
<ac_laptop>
uvos__: we'll I'm not a big fan of touchscreens anyway, I just need to figure out how to configure maemo so it's entirely usable with keys+buttons
<sicelo>
the OS has nothing to do with it. could your cable or port be flakey?
<uvos__>
hildons keyboard support is really poor
<uvos__>
like -desktop dosent even let you select stuff with the arrow keys
<uvos__>
like android dose
<uvos__>
kinda ironic given that hildons only device was a kbd device
<uvos__>
while android is mostly used on ts-only devices
<uvos__>
you can navigate android with just the arrow keys
<freemangordon>
uvos: how's that? ofc you can select with keyboard
<uvos__>
in hildon-desktop? no
<freemangordon>
yes
<uvos__>
i cant
<freemangordon>
where?
<uvos__>
homescreen
<uvos__>
the app screen
<freemangordon>
umm....
<uvos__>
taskt nav
<uvos__>
*tasknav
<freemangordon>
what you want to select there?
<freemangordon>
there is no text
<uvos__>
the icons, android lest you select application icons
<freemangordon>
you want to switch between apps with kbd?
<uvos__>
with the arrow keys and open with enter
<uvos__>
like desktop linux dose too
<freemangordon>
ah, now I see what "select" means
<freemangordon>
yeah, no such functinality
<uvos__>
yeah that makes ac_laptops goal of using it with just the kbd not an option
<ac_laptop>
sicelo: Well I assumed leste wasn't able to perform a full charge, since I would never get the green LED with it. With fremantle I get the green LED at the end of a charge. But maybe it was just a calibration issue. Anyway what would be the symptoms of a flakey cable ? I know the original cable I had was not good (couldn't flash u-boot with it) and now I'm using an other one.
<ac_laptop>
uvos__: I know xbindkeys works so I guess I can create a keyboard shortcut to launch a terminal and do everything with the keyboard from there
<uvos__>
launch termial exists
<uvos__>
its ctl-x
<uvos__>
ctrl-shift-x
<ac_laptop>
uvos__: this works on fremantle, I can't do it on a leste fresh install
<sicelo>
in Fremantle you could switch between taskswotjctrl+bksp
<sicelo>
*with
<freemangordon>
this should work on leste as well
<uvos__>
you can switch to tasknav (same on leste), but you cant select a window to go to
<freemangordon>
you can
<freemangordon>
but can't remember how :)
<uvos__>
ah yes you can
<uvos__>
q is the firs w is second ...
<uvos__>
cool
<freemangordon>
and you you start typing on desktop, it automatacally serches contacts
<freemangordon>
*searches
<freemangordon>
*and if
<freemangordon>
argh
<freemangordon>
what a typo day
<uvos__>
but then i cant select a contact with the kbd
<freemangordon>
you should be able to
<uvos__>
dosent seam to work, neither arrows or tab
<freemangordon>
heh
<freemangordon>
right, you can't
<freemangordon>
that's osso-abook
<freemangordon>
anyway...
<uvos__>
thats a bit wierd since its just a gtk dialog
<freemangordon>
btw, I just built upstreamxorg
<freemangordon>
not sure how to test it though
<sicelo>
ctrl+bksp hasn't been working for a while ...
<freemangordon>
it has been broken
<freemangordon>
but now it should be functional again
<freemangordon>
unless I have missed something
<sicelo>
will test again. couple of days ago it didn't
<arno11>
so to resume what's wrong on new img: emmc swap is not activated and this is the biggest problem
<arno11>
power button works again after reboot
<freemangordon>
uvos: if I make install xorg in /usr/local, would it override my default install? in /usr?
<arno11>
no troubles with battery
<uvos__>
freemangordon: well for one thing stuff in /etc will overide /usr/local/share
<uvos__>
bin is ok since you can just have it later in path
<uvos__>
im not sure about how its going to load modules
<uvos__>
it might try /usr first and load the wrong ones
<freemangordon>
yeah
<uvos__>
sicelo: it should have allways worked on n900
<arno11>
apt-worker is activated by default, must be removed (unusable ATM)
<uvos__>
its "broken" or rather reasigned on d4/bionic
<freemangordon>
hmm, "modeset(G0): using drv /dev/dri/card1"
<freemangordon>
uvos: ^^^ do you remember how to fix that
<sicelo>
ac_laptop: it's curious for sure, but I'm reasonably sure it's not leste's fault. the fuel gauge and charger largely take cate of themselves in mainline
<uvos__>
freemangordon: hmm i think we figured that one out., i also remember just (re)moving card1
<uvos__>
cant quite remember if you can specify this in .conf
peterM has quit [Server closed connection]
<freemangordon>
yes, I think you can, but can't remember how :)
<uvos__>
Default: /dev/dri/card0 i wonder what i bases choosing card1 on
<uvos__>
*it
vectis has quit [Ping timeout: 260 seconds]
<freemangordon>
no idea
<arno11>
sicelo: i can confirm, nothing unusual with battery/jauge
<ac_laptop>
sicelo: I'm currently trying a full battery charge with leste booted. But I'm pretty sure the result is going to be the same as before : the green LED indicating full charge will never appear
<Wizzup>
that is correct, that won't happen atm
<Wizzup>
we are no longer carrying a patch from spinal to make that work
<Wizzup>
I don't know why it was dropped
<ac_laptop>
is there a way to "force" calibration ? To tell meamo "this battery is at 100% charge whether you believe it or not" ?
<sicelo>
don't worry about led
<sicelo>
ac_laptop: even being out of calibration won't shutdown thrdevice, so don't worry about it
<uvos__>
Wizzup: kernel patch? probubly just got lost in the transtion to unified kernel with d4
<Wizzup>
uvos__: not sure if kernel patch or upower patch
<ac_laptop>
sicelo: ok well I went back to the device to check the charge, and it's the same thing as usual: the battery icon is showing the charge animation, when I try to use the interface it stops and shows a full battery, while the message "the device is consuming more power than it receives" appears. I check the battery status, it says 100% (with the wrong value of 1794mAh). I guess now I should try
<ac_laptop>
to stress the device until the battery is empty and charge again ?
<arno11>
ac_laptop: before looking at the battery issue, you must check what is the root cause of "device is consuming more power than it receives"
<sicelo>
show cat /sys/class/power/bq27200-0/uevent
<sicelo>
paste it somewhere
vectis has joined #maemo-leste
<arno11>
uvos: freemangordon; btw on a fresh install, 16bpp makes a big difference
<ac_laptop>
out of curiosity what's written on your AC-to-USB charger ? mine says "Output: DC5V.1.3A"
<Wizzup>
arno11 freemangordon - did you figure out if we can use qml in 16bbp or not
<freemangordon>
we can't
<arno11>
:(
<freemangordon>
I am looking @ modesetting ATM
<arno11>
:)
<sicelo>
ac_laptop: that's the original charger?
<freemangordon>
no high hopes though
<freemangordon>
it starts, but that's all
<ac_laptop>
sicelo: that's the one that was in the box, anyway
<ac_laptop>
but since the cable was faulty and I had to change it, I want to be sure the specs are ok
<Wizzup>
freemangordon: what would modesetting bring us? working randr on n900?
<uvos__>
dri3
<Wizzup>
what does that bring us again? :)
<uvos__>
surface creation is managed by the client not xorg
<sicelo>
ac_laptop: i think the charger is fine
<freemangordon>
30 or more % increase in speed
Daanct12 has quit [Quit: WeeChat 4.1.1]
<freemangordon>
ok, upstream ms/glamor starts and xterm is shown
<freemangordon>
however, it hangs the same way as above
<arno11>
argh
<freemangordon>
hmm
<freemangordon>
actually no
<arno11>
?
<freemangordon>
no input drivers are loaded
<arno11>
uvos: chimaera-devel is still 6.1.48 and chimaera 6.1.9, is it normal ?
<freemangordon>
ok, glamor hangs exactly as berfore
<freemangordon>
Wizzup: ok, can we at least upgrade glibc?
<freemangordon>
if we cannot change the distro?
<uvos__>
arno11: yeah, altho we should stable
<uvos__>
arno11: but thats not my department
<arno11>
ok thx
<uvos__>
freemangordon: what for @ glibc
<uvos__>
freemangordon: updateing glibc is probubly a bad idea
<uvos__>
*we should update stable
<Wizzup>
I mean honestly I'd rather look at the 3d driver situation again later, we're very close to a beta now
<uvos__>
if ti really wants to open source stuff it might make sense to wait from that perspective too, maybe we can interrogate rs@ti.com about thair intentions with the mesa stuff
dsc_ has quit [Server closed connection]
dsc_ has joined #maemo-leste
norayr has joined #maemo-leste
<arno11>
Wizzup: everything seems fine with last image, the only problem is swap
<arno11>
i'm looking at leste-config-n900.postinst and i think i found what is not working
<arno11>
addind stuff directly in /etc/fstab without swapon command seems to not work
<arno11>
i think we rather try to add swapon /dev/mmcblk1p3 command instead of adding stuff in /etc/fstab (swap will be added automatically in fstab with swapon command, i already tried)
<arno11>
ah and default swappiness value seems to high for N900
<freemangordon>
uvos: new sgx blobs require 2.34
<freemangordon>
Wizzup: ok, maybe I can upgrade my device only
<freemangordon>
to see if it gets any better with the new blobs in regards to ms/glamor and in general
<arno11>
*too
arno11 has left #maemo-leste [#maemo-leste]
<ac_laptop>
I'm genuinely interested to try a D4 now
<ac_laptop>
There doesn't seem to be many offers on the internet though, it's not liek the n900
<ac_laptop>
like*
<uvos__>
it was only ever sold in the united states of america
<uvos__>
so anywhere else you need to import it
<uvos__>
also they have become sortof rare at this point
<uvos__>
it used to be that you could just pick one up for 25 euros
<uvos__>
but the existance of leste drew the pool down pretty quick
<ac_laptop>
I see there are some verizon-simlocked online
<ac_laptop>
I guess I can unlock them but I will need to have a google account and boot under android first, right ?
uvos__ has quit [Ping timeout: 260 seconds]
uvos__ has joined #maemo-leste
ahmed_sam has joined #maemo-leste
<uvos>
ac_laptop: evey single droid 4 is simlocked to verizon
<uvos>
ac_laptop: but only in the us, they are unlocked everywhere else
<uvos>
you dont have to interact with android at all
<uvos>
besides android dosent need a google account
<ac_laptop>
uvos: If I buy a droid 4 from the U.S. sold as "verizon-locked", what will happen ?
<Wizzup>
arno11: we do not want to swapon in image builder
arno11 has joined #maemo-leste
<arno11>
Wizzup: ok so maybe use an init script ?
<arno11>
for swap and swappiess
<arno11>
*swappiness
ahmed_sam has quit [Read error: Connection reset by peer]
<arno11>
btw the weird thing is that boot msg says swap is activated but in fact not
<uvos>
ac_laptop: as i said all d4 are verizon-locked but they are locked in the us only, as soon as they cross the border they are unlocked and will connect to anny carrier
<ac_laptop>
uvos: ok, that's good then :)
<ac_laptop>
uvos: but then imagine I go to the US with it, that means I need to swap the SIM for a verizon one I suppose ?
<uvos>
ac_laptop: no its totaly useless in us
<uvos>
ac_laptop: verizon refuses to activate phones of this age
<uvos>
if you want a simmular device with no simlock you can buy a droid bionic, its also fully supported by leste, and this one has no sim lock, but also no keyboard
<ac_laptop>
uvos: I'll test a d4 along with my n900 and see the one I'm the most comfortable with. :) If it's the d4 I'll just have to remember never to travel to the US with it
<uvos>
i dont think you will be able to use the n900 for another minute after using the d4 given the delta in performance :P
<ac_laptop>
uvos: yeah, and from the pictures the keyboard seems more comfortable too :)
<Wizzup>
arno11: are you sure that /etc/fstab with swap doesn't auto mount swap?
<Wizzup>
I'm quite sure that it should
elastic_dog has quit [Ping timeout: 268 seconds]
<ac_laptop>
38 keys vs 54
<ac_laptop>
can't wait :)
<arno11>
Wizzup: i can certify it doesn't work :(
<arno11>
uvos: don't forget that n900 is perhaps 300% faster with few tweaks ;) droid is faster, that's a fact but n900 is now usable with lot of fun
<arno11>
and enough if a user or dev don't need modern browsing
<bencoh>
(and n900's keyboard actually feels better imho, just with heavy remapping)
<Wizzup>
arno11: ok, let me try to debug that a bit further
<Wizzup>
maybe we just need to add 'auto'
elastic_dog has joined #maemo-leste
<uvos>
i strongly disagree on the keyboard, its just so flat and crampt on the n900, other wise sure it can be fun to make things work with limited resources
<uvos>
but the keyboard is allways a personal preferance/what you used more kind of thing
<arno11>
Wizzup: ok :)
<bencoh>
uvos: true
<Wizzup>
arno11: maybe there is some swap init script that is not started
<Wizzup>
arno11: I did find this somewhere:
<Wizzup>
>
<Wizzup>
Exchange auto with sw in the fstab line. This tells the system to activate it using swapon after booting.
<Wizzup>
I'll toy with this later today
<arno11>
ok interesting
<ac_laptop>
uvos: n900 keyboard is not the worst keyboard but the keys are so small that it's not very comfortable to press two close ones at the same time
<ac_laptop>
Shift-Ctrl-X in particular is not fun to do on the n900 :)
<arno11>
ac_laptop: true
<arno11>
and keys are weak
<ac_laptop>
apart from that it's ok (I have big fingers, I mostly use the nails of my thumbs on this keyboard)
<ac_laptop>
bencoh: which remapping do you have ? do you switch between mappings or not ?
<bencoh>
I have a custom xkb map for n900/fremantle from almost 10y ago
<ac_laptop>
bencoh: do you know if there's a way to simulate the alt key ?
<bencoh>
not sure what you mean by 'alt key'
TheTechRobo has quit [Quit: Leaving]
TheTechRobo has joined #maemo-leste
<ac_laptop>
bencoh: an additional modifier key
<ac_laptop>
Meta key in emacs
sch has quit [Ping timeout: 256 seconds]
<bencoh>
with xkb you could set any key as a modifier, so ...
<bencoh>
(pretty much at leasT)
sch has joined #maemo-leste
sch has quit [Ping timeout: 268 seconds]
sch has joined #maemo-leste
sch has quit [Ping timeout: 256 seconds]
sch has joined #maemo-leste
brabo has quit [Server closed connection]
brabo has joined #maemo-leste
<arno11>
Wizzup: i had a look and indeed we must use 'sw' instead of 'defaults' apparently
<Wizzup>
does that work for you?
<arno11>
so the correct line to add seems to be '/dev/mmcblk1p3 swap swap sw 0 0' iiuc
<arno11>
i'll try a bit later tonight and let you know
<Wizzup>
ty
<arno11>
no probs
<sicelo>
ac_laptop: i think Fn key is R_Alt
arno11 has left #maemo-leste [#maemo-leste]
uvos has quit [Remote host closed the connection]
sch has quit [Ping timeout: 260 seconds]
sch has joined #maemo-leste
akossh has quit [Quit: Leaving.]
arno11 has joined #maemo-leste
<arno11>
Wizzup: i can't reproduce the error: defaults or sw or even wizzup work in fstab. without rebuilding with new parameter (sw), i don't know what to do to confirm if it's really the problem
<arno11>
and apparently sw option is not working on first boot with every distros
<Wizzup>
right, so it could be a first boot only problem?
<arno11>
yes definitely
<arno11>
so i think if you can rebuild with the sw parameter, i can reburn the img and test
<Wizzup>
I think it seems like we have another problem not related to fstab
<arno11>
ah
<arno11>
what kind of issue ?
<Wizzup>
well, you said we have a problem on first boot only :)
<arno11>
yes lol because maybe the sw option is missing in postinstall fstab stuff
<Wizzup>
I would like to avoid rc.S swapon -a style hacks if we can, so it might take a bit more debugging
<Wizzup>
it could be a devuan init script or so
<arno11>
ok
<arno11>
maybe there is an easier way: if we remove the expand card message, deactivate nokia-modem and apt-worker on boot, i think n900 can run easely without swap on first boot (just an idea)
<arno11>
(i'm currently running n900 with almost no swap and it works well, rarely need more than 200megs of swap)
<arno11>
and then users/devs could choose the best option regarding swap
<arno11>
again, just an idea
<Wizzup>
I think we probably just want some swap working, that's easier to solve than not running certain things on boot
<arno11>
hope it will be easier to solve
<arno11>
*200megs of ram
sch has quit [Ping timeout: 260 seconds]
ac_laptop has quit [Ping timeout: 260 seconds]
arno11 has left #maemo-leste [#maemo-leste]
sunshavi has quit [Remote host closed the connection]