sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #maemo-leste
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #maemo-leste
<Wizzup>
udoes it default to abook?
<Wizzup>
uvos& ^
<Wizzup>
sicelo: but with poor PM
Daanct12 has joined #maemo-leste
duuude has quit [Ping timeout: 250 seconds]
pagurus has quit [Ping timeout: 256 seconds]
pagurus has joined #maemo-leste
joerg has quit [Ping timeout: 272 seconds]
joerg has joined #maemo-leste
macros_ has quit [Ping timeout: 260 seconds]
macros_ has joined #maemo-leste
mardy has joined #maemo-leste
<freemangordon>
Wizzup: I resumed work on osso-addressbook, hopefully in a week or so we will have vcf import working in leste
<freemangordon>
IOW - there will be no need of anything else but a way to transfer vcf files generated on n900 to your leste device
duuude has joined #maemo-leste
Pali has joined #maemo-leste
Pali has quit [Ping timeout: 272 seconds]
dsc_ has quit [Remote host closed the connection]
The_Niz_ has quit [Ping timeout: 256 seconds]
The_Niz has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
uvos has joined #maemo-leste
pere has joined #maemo-leste
<uvos>
Wizzup: it syncs to eds so yes it works in abook
<uvos>
sicelo: yes also ofono works fine ootb. the problem is that these use the qmi interface, while working fine, uses a lot of power, so we need to use the other interfaces of motorolas customized firmware.
<sicelo>
ofono works fine ootb? i thought we have an ofono-d4 fork
<uvos>
yeah qmimodem works
<uvos>
the fork is about using the custom moto interfaces to save power
<sicelo>
ok. anyway, while i haven't profiled, i haven't really observed any massively worse power consumption (even with my supposedly bad battery)
* sicelo
wishes USSD was working :'(
<uvos>
afik there is no way the device can ever enter idle with the qmi interface active (which is nessecary if you cant get events from another place) since it keeps the usb device active wich blocks omap idle
Daanct12 has quit [Quit: Quit]
<sicelo>
mmm, was rebooting d4 (with `sudo reboot`), and it didn't start again
<uvos>
it dident shut down
<uvos>
know issue, uart oopses if you have the kernel console suspended
<uvos>
ocassionally causing a userspace lockup
mtekman[m] has joined #maemo-leste
<sicelo>
is it Leste userspace, or same issue happens everywhere?
<uvos>
depends anything that touches the tty device will hang after the oops
<uvos>
if something touches the tty depends on your specifc userspace ofc
<mtekman[m]>
Hi all, Im trying to update apt on my N900, but keep getting a missing key error from Wizzy (who I understand is a trusted dev). I have keyrings from devuan and debian dating back to 2017. Does anyone know where I can install newer keyrings?
<uvos>
mtekman[m]: yeah Wizzup let the key expire by accident
<uvos>
mtekman[m]: you might have to install maemo-keyring by hand
xmn has quit [Quit: ZZZzzz…]
<mtekman[m]>
okay, thanks -- I'll download that
duuude has quit [Ping timeout: 240 seconds]
<Wizzup>
uvos: no, I mean, does sphone default to abook
<Wizzup>
mtekman[m]: you should be able to ge tthe fix with just apt update and apt dist-upgrade
<crab>
Wizzup: i tried that a couple of days ago but i will try again right now.
<Wizzup>
ok, please let me know
<crab>
so the update warns about the expired key
<crab>
and the upgrade fails with conflicts regarding ti-omap3-sgx
<crab>
aah i didnt dist...
<crab>
hang on
<crab>
yeah that looks better sorry you are dealing with the reading comprehensionally challenged
<crab>
hmmm was it xession i was hacking the last time i was pestering you about errors? hmm.
<crab>
maybe i should have accepted the package maintainers version there instead of mindlessly accepting the default but hey, you live and leran.
<Wizzup>
:)
<crab>
well other than that looks like dist upgrade finished without incident
<crab>
the ti-omap3-sgx conflict persists but i guess that is wip?
<Wizzup>
no, that is solved after the dist-upgrade
<Wizzup>
I still need to push out the news post :(
<Wizzup>
I might just finish that on Sunday if it all works out
<crab>
oh that bit didnt seem to work for me.
<crab>
oh i see
<crab>
hmm. i wonder if i need to check my bootloader
<crab>
i have no idea how this works...
<crab>
meh...
<crab>
im gonna do a reboot!
n900 has quit [Ping timeout: 240 seconds]
<crab>
hmmm yeah it looks like i trashed X
<mtekman[m]>
<Wizzup> "mtekman: you should be able to..." <- oh whoops. I manually "built" the keys from https://github.com/maemo-leste/maemo-keyring. and then did `sudo apt-key add trsuted.gpg/maemo-blah-blah-blah.gpg` and then the update worked without problems
<humpelstilzchen[>
don't get too comfortable with apt-key
<mtekman[m]>
I was desperate and had no idea you guys would push our an easy fix so quickly :-) But yes, warning well taken
<crab>
Wizzup: hmmm. it looks like difference between my xession and pkg maintainers is simply "use ofono" do i need to reverse that now?
<crab>
(ill try anyway - cant make it worse...)
<crab>
hmmm how can i start network from cmdline?
<humpelstilzchen[>
start?
<crab>
yeah X is broken so networking doesnt seem to want to start
<humpelstilzchen[>
so you have a working terminal without X?
<crab>
well i can log in on the console yeah
<crab>
maybe i can do it long hand with ip
<humpelstilzchen[>
wifi?
<crab>
and associate with my ap using iw whatever it is :(
<crab>
yeah
<crab>
actually i may have a usb cable...
<crab>
that might be easier.
<humpelstilzchen[>
thats easier, yes. Or you just wait 10 minutes for the maemo autoconnection
<crab>
hmmm
<crab>
how does the autoconnection work?
<crab>
i think things are a bit hosed when it gets to starting x that craps out and eventually i get a console... is there an emergency network thing after that?
pere has quit [Ping timeout: 256 seconds]
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #maemo-leste
Twig has joined #maemo-leste
Twig has quit [Ping timeout: 240 seconds]
xmn has joined #maemo-leste
Twig has joined #maemo-leste
<crab>
Wizzup: ok im not sure whats happened here but this thing is in a bit of a state. neither x nor wifi seems to work.
<crab>
i can sort of get it networked via usb though...
<crab>
i might have to install some sort of apt proxy somewhere to let it use apt though. :(
<Wizzup>
crab: why not make usb0 the default gateway?
<Wizzup>
crab: weird I updated more than a few devices wiht dist-upgrade and it wasn't a problem
<crab>
i did but its behind 2 layes of nat
<crab>
and i cba to figure out the static routing.
<crab>
i might reinstall... im just debating...
<crab>
is the network stuff in these lxc things?
<crab>
thats pretty funky.
<crab>
oh...
<crab>
i was actually gonna look at this xorg log.
<sicelo>
I don't recall that an end device needs to care how many layers of NAT there are. i.e. it should be possible to make your usb0 default gw and have it work, as long as the other end (computer side) of this interface knows how to reach the Internet
<sicelo>
And computer has correct forwarding and firewall setup of course
<crab>
no screens found
<crab>
maybe i botched the forwarding
<crab>
i could ping hosts on the same network (as the host im connected to via usb)
<crab>
but nothing upstream of that
<crab>
ok networking (usb0) is fixed i think :(
<crab>
so as far as apt is concerned i have a hildon-meta-n900 coming down the line,
<crab>
but i also have this issue with ti-omap3-sgx which im guessing may relate to x.
<crab>
libegl1, iibgles1, libgles2 are conflicting
<Wizzup>
you still have the conflict?
<Wizzup>
dist-upgrade does not resolve it?
<crab>
nah
<crab>
thats telling me that the hildon-meta-n900 pkg is being held back
<Wizzup>
Broken sgx-ddk-um-ti343x:armhf Conflicts on sgx-ddk-um-ti443x:armhf < none -> 1.17.4948957+leste13-1+2m7.1 @un uN Ib >
<Wizzup>
uh what
<crab>
ive not installed a lot of crazy stuff on here really.
<crab>
weechat, mocp..
<crab>
thats about it.
<Wizzup>
yeah the debian output stuff in insane ot read
<Wizzup>
but I tried tis and it should work
<Wizzup>
maybe just take the latest image yeah.
<crab>
heheh
<crab>
ok...
<crab>
now, i think the way i do this, i need to put it on this card in p1,
<crab>
and make a swap somewhere too perhaps
<crab>
and then i need to boot into my power image to mess with the uboot iirc.
<Wizzup>
time to sleep
<Wizzup>
zzz
<crab>
nn
xmn has joined #maemo-leste
pere has joined #maemo-leste
Twig has quit [Remote host closed the connection]
Twig has joined #maemo-leste
Danct12 has quit [Quit: Quitting]
Pali has joined #maemo-leste
Danct12 has joined #maemo-leste
n900 has joined #maemo-leste
Danct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
uvos has quit [Ping timeout: 256 seconds]
avoidr has quit [Quit: leaving]
avoidr has joined #maemo-leste
uvos has joined #maemo-leste
_inky has quit [Ping timeout: 256 seconds]
inky has quit [Ping timeout: 272 seconds]
inky has joined #maemo-leste
n900 has quit [Ping timeout: 252 seconds]
n900 has joined #maemo-leste
Twig has quit [Ping timeout: 256 seconds]
Danct12 has quit [Ping timeout: 240 seconds]
_inky has joined #maemo-leste
Danct12 has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
avoidr has quit [Ping timeout: 250 seconds]
<sicelo>
so droid 4 - the flash chip is known. according to sre's matrix, we're just missing having it in dts. any idea what's the hold up? or just no one has had time to look at it?
<sicelo>
i suppose first step is to enable VIDEO_LM3560 in our kernel