<freemangordon>
tmlind: what is channel 8 used for? I think it is enabled by mistake in the bitmap
ceene has joined #maemo-leste
alex1216 has joined #maemo-leste
<freemangordon>
Wizzup: I am not sure I'll be able to merge, but will try
pere has quit [Ping timeout: 268 seconds]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
Pali has joined #maemo-leste
alex1216 has quit [Ping timeout: 252 seconds]
alex1216 has joined #maemo-leste
pere has joined #maemo-leste
kabouik has joined #maemo-leste
kabouik has quit [Changing host]
kabouik has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
<Wizzup>
freemangordon: we can also just replace it branch
<Wizzup>
(contents)
xes has quit [Ping timeout: 268 seconds]
<freemangordon>
force-push?
<freemangordon>
Wizzup: ^^^
<Wizzup>
yeah, maybe also keep the other one as maemo-5.18-old
<freemangordon>
ok
xes has joined #maemo-leste
<freemangordon>
Wizzup: we'd better switch the branch
<Wizzup>
to what?
<freemangordon>
maemo-5.18.y :)
<Wizzup>
I am fine with it, but we'll change to change debian/gbp.conf as well
<freemangordon>
better than force-push I think
<Wizzup>
actually nevermind
<Wizzup>
that's not true, it's tag based
<Wizzup>
upstream-tag=maemo-kernel-%(version)s
<Wizzup>
so you can pick any branch name
<Wizzup>
my bad
<freemangordon>
ok
<freemangordon>
so, I am going to push maemo-5.18.y branch and will leave you to make the release, ok?
<Wizzup>
ok
<Wizzup>
if you can, maybe do make the tag and push the tag as well
<Wizzup>
it would be like maemo-kernel-5.18.NUMBERHERE
<freemangordon>
ok
<mglbg[m]>
I am experiencing incredibly slow boottimes, it takes like 2-3 mins. I have seen the n900 perform better than that just after the ML install. Checking dmesg indicates a gap between usb0 at 60s and bnep bleutooth at 200s. Is there any way to find out what is going on? I can only find guidance on systemd based tools...
uvos__ has joined #maemo-leste
<uvos__>
freemangordon: also please, a feature branch with just the modem/serdev patches on some otherwise mainline version
<uvos__>
i dont want to go huting around the tree for patches again next major release
<Wizzup>
that's why we rebase instead of merge in branches yeah?
<Wizzup>
so that all the relevant patches are just on top of the regular linux
<uvos__>
its still better to have them sorted by subject
<uvos__>
otherwise you have figure out what was merged into mainline on a per patch
<uvos__>
basis
<freemangordon>
uvos__: you should ask tmlind for that
<freemangordon>
He knows better what patch does what
<freemangordon>
Wizzup: maemo-kernel-5.18.19
<freemangordon>
Wizzup: hmm, wait a bit, I have to fix one thing (reorganize the patches)
<Wizzup>
ok
<Wizzup>
please retag as well
<freemangordon>
sure
<tmlind>
freemangordon: not sure about channel 8, 7 i think just echoes back what's typed to it
<tmlind>
or maybe 8, don't seem to have any notes on that
<tmlind>
the android numbering starts from 0 btw
<freemangordon>
it does not respond to SABM(P) at all
<freemangordon>
channe 8 that is
<freemangordon>
so I think it is better to remove it from the bitmap
<freemangordon>
it does not respond to DISC as well
<freemangordon>
so, nobody home I'd say
<tmlind>
ok, some of the unused ones might be wired to the lte modem when it's up
<freemangordon>
ah, Isee
<freemangordon>
ok, will not touch it
<tmlind>
well you could remove it and add a comment saying it's unsued :)
<tmlind>
unused
<tmlind>
i think channel 12 is the one i thought might be wired to some lte modem uart
<freemangordon>
not a biggie, it just slows down rmmod, as latest code tries to gracefully close the channels
<freemangordon>
but ok
<tmlind>
yeah ok just drop channel 8 then
<freemangordon>
ok
buZz has quit [Ping timeout: 268 seconds]
<freemangordon>
Wizzup: ready, please release
ceene has quit [Remote host closed the connection]
<Wizzup>
ok
<Wizzup>
freemangordon: summary for userspace, does this fix known problems atm?
<freemangordon>
yes
<Wizzup>
ok
<freemangordon>
missing modem on startup, missin messages, all kind of random issues
<Wizzup>
ok
<Wizzup>
great
<Wizzup>
it's building atm
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
<tmlind>
nice :)
<tmlind>
freemangordon: also the issue with unsol messages on ofono restart is gone now?
<freemangordon>
I added my sign-off to all the commits I made changes to
<freemangordon>
feel free to remove it as appropriate
<freemangordon>
I will send n_gsm fixes after I get back from holiday (after 13th)
<freemangordon>
Wizzup: obviously, there are more issues in ofono, but I'll chase them after I get back
<freemangordon>
you may gather a list in the meanwhile :)
Livio has quit [Ping timeout: 264 seconds]
<Wizzup>
ok
<Wizzup>
when are you leaving?
<freemangordon>
tomorrow morning
<Wizzup>
ok
<freemangordon>
bbl
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
<Wizzup>
hm I don't see /motmdm_0/context1 atm on my d4
<Wizzup>
same on the d4
<Wizzup>
er
<Wizzup>
same on the bionic
<Wizzup>
freemangordon: did you test network context?
Wizzup has quit [Ping timeout: 268 seconds]
Livio has quit [Ping timeout: 252 seconds]
Wizzup has joined #maemo-leste
<freemangordon>
no
<freemangordon>
will look at it later on
<Wizzup>
ok
<Wizzup>
currently I think the data contexts aren't working
<freemangordon>
some bug in ofono
<uvos__>
with all your digging up its amazing that this worked half way at all
<freemangordon>
hehe
<freemangordon>
yeah, list-context returns nothin
<freemangordon>
which is weird
<uvos__>
this rarely worked for me in the past
<uvos__>
i had to restart ofono lots
<uvos__>
allways
<Wizzup>
it worked more than it didn't for me, but yes, not always
xmn has joined #maemo-leste
alex1216 has quit [Quit: WeeChat 2.3]
<freemangordon>
hmm
<freemangordon>
somehow I have 2 contexts now
<freemangordon>
let me reboot to see if it will still work
<freemangordon>
ies, it still works
<freemangordon>
I have contexts after restart
<freemangordon>
and connections dialog lists GPRS connection
<Wizzup>
hmmm
<freemangordon>
it fails to connect, but that's another story :)
<freemangordon>
what I did is to issue qmicli --wds-get-profile-list=3gpp
<freemangordon>
tmlind: shouldn;t motmdm create WDS service as well?
<Wizzup>
so you must run qmicli before ofono works?
<freemangordon>
I did that only once
<freemangordon>
and after power cycle it still works
<Wizzup>
hm now I restart ofono again and I get a conte
<Wizzup>
but this is 4th restart
<Wizzup>
(didn't issue qmicli)
<freemangordon>
I think ofono driver shall create WDS service
<freemangordon>
but need tmlind to confirm
<Wizzup>
(btw still see the thing where if I send sms during context activation, the context finally activates)
<Wizzup>
but this time I also received the sms, which is a bug fixed :)
<freemangordon>
:)
<Wizzup>
but I think we knew about this context with with CIEV not being used fir kicking
<freemangordon>
sorry, don;t have time now to dig into that
<freemangordon>
either wait for me to get back or you fix it in the meanwhile
<Wizzup>
will probably wait, since you have the domain knowledge now
<Wizzup>
I will work on other parts
<freemangordon>
ok
<freemangordon>
hmm, actually after reboot there are no contexts, my bad
<freemangordon>
it is simply that ICD had that SIM card provisioned
<freemangordon>
ok, doing disable/enable/online makes them appear
<freemangordon>
actually offline/online is enough
<freemangordon>
it seems doing online too soon after enable bugs it
<Wizzup>
ok
<Wizzup>
just ofono restart didn't help
<Wizzup>
but I didn't try offline/online
<freemangordon>
which cellulard does
<Wizzup>
right
<freemangordon>
shall I hack cellulard to wait 1 second before putting modem online?
<Wizzup>
is it just the one second that makes a difference?
<freemangordon>
no idea, but I can try
<Wizzup>
maybe it's just a message that ofono is missing
<Wizzup>
I suppose can try, but it doesn't seem like a "proper" fix
<Wizzup>
but I'm fine with it
<freemangordon>
that's why 'hack' :)
<freemangordon>
we'll revert as soon as ofono is fixed
<Wizzup>
check
<freemangordon>
yep, that works
<freemangordon>
and actually it connected on the second try :D
<freemangordon>
lemme push, please release
<freemangordon>
I will release it
yanu has quit [Ping timeout: 260 seconds]
<freemangordon>
done
<Wizzup>
freemangordon: if you used the UI, then yes, it doesn't wait for the context to get active
<Wizzup>
freemangordon: ok ty
<freemangordon>
if it does not work right after reboot, enter/exit flight mode and it should be ok
<Wizzup>
ok
<freemangordon>
yeah, have to do that after reboot, otherwise contexts does not appear
<Wizzup>
I still had to offline/online mode
<Wizzup>
but nice otherwise
<Wizzup>
:)
<freemangordon>
yeah, some timing issue in ofono driver it seems
<freemangordon>
should be easy to fix
pere has quit [Ping timeout: 252 seconds]
l_bratch has quit [Quit: Leaving]
l_bratch has joined #maemo-leste
l_bratch is now known as Guest4868
Guest4868 has quit [Remote host closed the connection]
Bratch has joined #maemo-leste
uvos has joined #maemo-leste
pere has joined #maemo-leste
Aikon has joined #maemo-leste
<Aikon>
hey
<Aikon>
is the camera working on Maemo Leste in the Nokia N900?
armin_ has joined #maemo-leste
Aikon has quit [Client Quit]
<armin_>
Can I install Maemo Leste together with Maemo 5 on my N900's eMMC? Kind of like a dual boot
jeder[m] has joined #maemo-leste
<Wizzup>
No camera is currently working I believe, that's one of the missing drivers.
<Wizzup>
You can probably do it @ eMMC, but we don't have a guide for it
<Wizzup>
I would recomming using a microsd for leste and just picking it from u-boot
<Wizzup>
that's an easier way to dual boot and to troubleshoot
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
armin_ has quit [Ping timeout: 244 seconds]
armin_ has joined #maemo-leste
linmob has quit [*.net *.split]
[TheBug] has quit [*.net *.split]
[TheBug] has joined #maemo-leste
linmob has joined #maemo-leste
<jeder[m]>
Hey, I installed leste on my N900 today, and I have a certain problem. This N900 has a German QWERTZ layout, however it seems to be stuck on some weird QWERTY layout even after changing it in settings how you would on stock fremantle, and besides that, dot key is a left arrow key, the normal left arrow key does nothing, and i think i can't access up/down arrows too?
<freemangordon>
Wizzup: drivers/qmimodem/gprs.c:create_nas_cb() : Failed to request NAS service
<freemangordon>
this happens when there are no contexts
armin_ has quit [Client Quit]
<freemangordon>
CLIENT_IDS_EXHAUSTED
<Wizzup>
jeder[m]: I think your layout might be available with setxkbmap and the right variant, but I am not sure.
<jeder[m]>
it probably is, though i'd probably have to dig a bit
<Wizzup>
freemangordon: aha... ids exhausted?
[TheBug] has quit [Changing host]
[TheBug] has joined #maemo-leste
<freemangordon>
yes
<freemangordon>
something in qmimodem
yanu has joined #maemo-leste
<jeder[m]>
i am back, `setxkbmap -model nokiarx51 -layout de` fixed that
l_bratch has joined #maemo-leste
l_bratch has quit [Remote host closed the connection]
l_bratch has joined #maemo-leste
l_bratch has quit [Excess Flood]
l_bratch has joined #maemo-leste
Bratch has quit [Quit: Leaving]
<Wizzup>
jeder[m]: maybe see /etc/default/keyboard (or so)
<Wizzup>
if you can set it permanently there, we definitely want to document that
<jeder[m]>
changed that, and now reboot i am guessing, yes?
<Wizzup>
yes
akossh has joined #maemo-leste
<jeder[m]>
hm, it doesn't want to boot to os now
<Wizzup>
was the change syntactically correct?
<jeder[m]>
i just changed from us to de
<jeder[m]>
though i did change the shell to fish before that and i wonder if that broke something
<jeder[m]>
* to de in the file
<Wizzup>
yes that will break everything I think
<Wizzup>
(fish)
<jeder[m]>
ye
<jeder[m]>
so uh, reflash the card, i guess?
<Wizzup>
just undo the change on the microsd card if you can mount it anywhere
<Wizzup>
you can just edit /etc/passwd I imagine
<jeder[m]>
okay
<jeder[m]>
don't really have a linux distro installed, though i did mount a drive to wsl once, welp we'll see if it work
<jeder[m]>
s/work/works/
<jeder[m]>
it's back
<jeder[m]>
okay so, /etc/default/keyboard has XKBLAYOUT="de", however, it didn't change anything looks like
<jeder[m]>
and it discharged, oops
dev has quit [Quit: Gateway shutdown]
norayr has quit [Quit: Gateway shutdown]
<Wizzup>
jeder[m]: so it boots but didn't provide the fix that setxkbmap gave you?
<jeder[m]>
exactly
<Wizzup>
hm
<Wizzup>
maybe check how /etc/default/keyboard is used (or more specifically XKBLAYOUT)
<Wizzup>
I'll check as well
<Wizzup>
jeder[m]: hm, did you change anything in the settings applet? is that also set to 'Deutsch'?
<Wizzup>
settings->text input
<jeder[m]>
yes
<Wizzup>
ok
norayr has joined #maemo-leste
<Wizzup>
not sure right now what the best perm fix is
<Wizzup>
jeder[m]: maybe you can run setxkbmap -print
<Wizzup>
in your (fixed) scenario and then in the scenario that doesn't work
<Wizzup>
and then perhaps also with the /etc/default/keyboard fix (which isn't an actual fix atm) applied
<jeder[m]>
not fixed and /etc/default/keyboard fix are the same
<jeder[m]>
and the setxkbmap fix has de instead of us in xkb_symbols
<jeder[m]>
can i paste both outputs here so its clearer?