LjL has quit [Quit: Scappò via con la paura di arrugginire. Il giornale di ieri lo dà morto arrugginito. I becchini ne raccolgono spesso fra la gente che si lascia piovere addosso.]
<Wizzup>
tmlind: I don't seem to see these lines, I only have the panel disable/enable
<Wizzup>
I do sometimes see:
<Wizzup>
[1186414.293518] omap-mcbsp 40124000.mcbsp: CLKS: could not clk_get() prcm_fck
<Wizzup>
oh hey:
<Wizzup>
[1074080.898284] abe-clkctrl:0030:0: failed to disable
<Wizzup>
yup so I saw those too before:
<Wizzup>
May 28 09:30:16 localhost kernel: [1364651.545074] abe-clkctrl:0030:0: failed to disable
<Wizzup>
May 30 09:30:23 localhost kernel: [157271.035980] abe-clkctrl:0030:0: failed to disable
<Wizzup>
May 30 16:53:25 localhost kernel: [183853.249938] abe-clkctrl:0030:0: failed to disable
uvos has joined #maemo-leste
<uvos>
with the old kernel i gues
<Wizzup>
uvos: right
<Wizzup>
uvos: what do you think about n900 dts change for f7/f8 ?
<Wizzup>
to raise/lower volume
<uvos>
Wizzup: i allready mentioned ill implement it next kernel release
<uvos>
its allready in my tree
<Wizzup>
I missed that somehow, sry!
<uvos>
no problem :)
<Wizzup>
ah I see it now
<uvos>
do note that this has some down sides
<uvos>
like it will for instance make non-volume use of the buttons apply to external usb keyboards and bluetooth devices differently
<uvos>
(excepting bluetooth speakers headphones those will continue to work fine (volume only))
<Wizzup>
are you talking about if/when we would change the hildon key?
<uvos>
yes
<Wizzup>
right
<uvos>
but right now too for xterm
<uvos>
since it reacts to xf86vol*
<Wizzup>
xterm already handles both I think
<uvos>
yes
<uvos>
then again f7 f8 being volume on an external keyboard is really random allready
<uvos>
so idk if this is worse
<uvos>
i really dislike how fremantle handles/ uses the volume buttons
<uvos>
but thats a different storry
maxwelld has left #maemo-leste [Disconnected: closed]
<tmlind>
Wizzup: i think those abe-clkctrl errors are harmless, misconfigured source clock
<tmlind>
or device busy while trying to idle if it's a autoidle configured device
<Wizzup>
ok, then I am not sure if I can find the error you're talking about
<tmlind>
ok so nothing interesting in your logs sounds like
<tmlind>
those lcd messages are annoying
<Wizzup>
right
<uvos>
more annoying is the stuttering
<uvos>
:P
<uvos>
the kernel messages are easy to ignore
<tmlind>
which stuttering?
<Wizzup>
I was thinking of restarting for new kernel but maybe since I'm at 13 days I should wait
<uvos>
d4's lcd stutters, looses frames
<tmlind>
yeah and the ants
<uvos>
compeare a bionic side by side
<uvos>
its like butter compeared to d4
<tmlind>
weird
<uvos>
tmlind: yeah but the pannel dropping frames happens on android too
<uvos>
its a hw bug
<Wizzup>
imo the ants are more strange and sometimes mess up the fonts in tricky ways
<uvos>
the ants are some sw bug
<tmlind>
uvos: oh ok, did not know that
<tmlind>
yeah the ants might be some kind of cache issue
<buZz>
tmlind: you mean in the overflowing log? afaik its icd2.log thats just configured 'extra verbose' by default
<Wizzup>
no that's different buZz
<Wizzup>
you're talking about different things
<buZz>
ah ok, didnt get the question
<tmlind>
buZz: if your device ended up hanging, maybe check your /var/log/messages or syslog
<buZz>
i'm quite sure its because icd2.log is full , which somehow prevents hildon from finishing to start
<buZz>
but i'll let you know
<uvos>
hmm really
<uvos>
when my disk is full i get a popup from xsession to that effect and hildon stars when i click ok
<uvos>
ah the reson is presumably because my /home is on a different partion
<uvos>
(and not full)
<Wizzup>
some parts of icd2 are very verbose every x seconds
<Wizzup>
currently
<Wizzup>
the ofono/modem part
<uvos>
btw
<uvos>
should roaming work
<uvos>
i was in italy recently and could not get mobile data to work via icd2 at all
<uvos>
had to use qmicli
<uvos>
maybe apn issues again?
<uvos>
might be good to know whats failing when root is read only
<uvos>
@buzz
<buZz>
i had functional 3G in luxembourgh on leste
<buZz>
with a dutch sim
<Wizzup>
uvos: well you need to tell ofono to allow roaming
<uvos>
Wizzup: sure yeah i treid that
<uvos>
its probubly the apn thing, ill be in austria soon and will try an repo it
<uvos>
and get logs this time
<Wizzup>
great
maxwelld has joined #maemo-leste
<freemangordon>
hi!
<freemangordon>
so, I am not sure I understand that 'volume keys' change
<freemangordon>
still, please, don't do changes that will make BT HF volume keys to change pages in book readers
<buZz>
tmlind: btw in my 'hanging' it doesnt really hang, holding powerbutton still starts powerdown
Twig has joined #maemo-leste
pere_ has quit [Ping timeout: 240 seconds]
<Wizzup>
freemangordon: why would pages change in ebooks upon volume raise?
<uvos>
because bluetooth headphones have volume buttons
<uvos>
but they dont
<uvos>
not really
<freemangordon>
Wizzup: what device key would you use to turn pages?
<uvos>
the keys go over alsa
<uvos>
they do also go over evdev
<uvos>
but thats a legacy compat thing
<uvos>
we can just disable it
<freemangordon>
ok
<Wizzup>
freemangordon: I would swipe or press on-screen probably
<uvos>
(this is how pa mangaes to change the volume of the right stream when the vol buttons on bt headphones are pressed)
<freemangordon>
Wizzup: well, RN all book readers I used (on n900) use volume keys to turn pages
<freemangordon>
and that's really convenient
<uvos>
however on a bt keyboard the vol buttons will change the page
<uvos>
but then again on a bt keyboard as is f8 and f9 would change volume
<uvos>
witch is equally wierd
<freemangordon>
right
<freemangordon>
Wizzup: the similar stands for osso-xterm
<freemangordon>
anyway, I already got my answer :)
<Wizzup>
from my pov making n900 act the same as other devices improves the situation
<Wizzup>
this way it will work the same as other devices, volume applet will work, too
<uvos>
i men we could change the other devices to be f8 f9 too, (well except x86 tablets and the like, there it is impossible)
<Wizzup>
all other phones simply map these buttons to vol -/+. so I don't know why we would keep n900 different
<uvos>
*mean
<Wizzup>
it's f7/f8 btw, but yeah
<freemangordon>
Wizzup: I don;t really care if those are f7/f8 or volume keys or whatever
<freemangordon>
as long is we don;t break the UX
<Wizzup>
ok, so in that sense I think we can streamline it to be the volume keys for now
maxwelld has left #maemo-leste [#maemo-leste]
maxwelld has joined #maemo-leste
<maxwelld>
folks, my maemo xterm is crashing whe starting. i dont know what i did that started t cause that. restart does not help.
<maxwelld>
i have xterm luckily
<maxwelld>
imean normal xterm not maemo term
<maxwelld>
which runs
<maxwelld>
with very small letters
<maxwelld>
how can i start maemo terminal from xterm to see the prooblem?
<uvos>
osso-xterm
<uvos>
or osso_xterm
<uvos>
maybe
<maxwelld>
oh now it doesnt bring me eve debian app menu
<maxwelld>
very weird
<uvos>
smells hw failure
pere_ has joined #maemo-leste
Twiggy has joined #maemo-leste
Twig has quit [Ping timeout: 240 seconds]
pere_ has quit [Ping timeout: 240 seconds]
DPA has quit [Ping timeout: 260 seconds]
maxwelld has left #maemo-leste [#maemo-leste]
pere_ has joined #maemo-leste
DPA has joined #maemo-leste
maemish_ has joined #maemo-leste
<maemish_>
Is there still coming a new release. Have been checking twitter and maemo forum. Twitter the last post is from January promising more news next week.
<maemish_>
I recall something similar on maemo forum. I don't mind there is not coming news often but if someone says there is coming then people wait. Maybe better not to promise next news soon when posting.
<uvos>
we dont do "releases" just install and update (optionally to devel)
<uvos>
we operate like a rolling distro like arch linux for our packages really
Twiggy has quit [Remote host closed the connection]
Twig has joined #maemo-leste
pere_ has quit [Ping timeout: 265 seconds]
le0nklcpp has joined #maemo-leste
arno11 has joined #maemo-leste
pere_ has joined #maemo-leste
maxwelld has joined #maemo-leste
ceene has quit [Ping timeout: 240 seconds]
pere_ has quit [Ping timeout: 240 seconds]
norayr has joined #maemo-leste
xray256 has quit [Ping timeout: 240 seconds]
<maxwelld>
so it is a floating point exception
<maxwelld>
i am afraid it is indeed in hw, not just sdcard.
<maxwelld>
😕
<Wizzup>
or broken sd card
xray256 has joined #maemo-leste
<Wizzup>
flash a new image to a new or different sd card and check :)
<maxwelld>
uhu, doing that.
xmn has quit [Quit: ZZZzzz…]
xmn has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
Twig has quit [Remote host closed the connection]
<maxwelld>
so i found my old 'adata' sdcard, with it droid works well.
<maxwelld>
but with new sandisk - no. weird.
<maxwelld>
did fsck, but it didn't find anything.
<maxwelld>
so i am thinking what temporary files to delete.
<maxwelld>
i have strace of osso-xterm when it was dying.
<Wizzup>
fsck on ext4 won't show random data corruption
<Wizzup>
for integrity checks you would need a different file system
<Wizzup>
there can also be partial writes after some hang or power failure
maemish_ has quit [Quit: Connection closed for inactivity]
<Wizzup>
I don't think it makes sense to try to figure out where the SIGFPE comes from per se