System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
narodnik has quit [Ping timeout: 260 seconds]
narodnik has joined #maemo-leste
xmn has joined #maemo-leste
joerg has quit [Killed (iridium.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
ceene has joined #maemo-leste
saeed has joined #maemo-leste
saeed has quit [Ping timeout: 248 seconds]
akossh has quit [Ping timeout: 276 seconds]
_fab has joined #maemo-leste
vectis_ has joined #maemo-leste
_fab_ has joined #maemo-leste
_fab has quit [Ping timeout: 260 seconds]
_fab_ is now known as _fab
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
System_Error has joined #maemo-leste
jrayhawk has quit [Ping timeout: 245 seconds]
<sicelo>
Wizzup: i guess daedalus is releasing soon? :-)
pere has quit [Ping timeout: 248 seconds]
_fab has quit [Quit: _fab]
vectis_ has quit [Ping timeout: 244 seconds]
<Wizzup>
yeah just need to make the post I guess
g4rrgl3n0m4d has joined #maemo-leste
apac has joined #maemo-leste
xinomilo has joined #maemo-leste
pere has joined #maemo-leste
<erebion>
Wizzup: That's what I did, but with emulation as my laptop is ARM. I see some OpenRC stuff, then the screen goes blank and stays that way. Not sure whether related to the emulation or not.
<Wizzup>
erebion: I wonder if you're just seeing the screen blank
<Wizzup>
erebion: try to click the 'power off' option, does that show the lock screen for you?
<erebion>
Wizzup: Will try
<erebion>
Wizzup: btw, could arm VM images alao be generated? I'm not sure what that requires, but that'd be meat. :)
<Wizzup>
probably if we make the image generation better yeah, then we can piggyback off of other solutions
<Wizzup>
brb
<erebion>
Shall I try forking mobian-recipes and add a file for the maemo rootfs and see if I can get that to build an image?
<erebion>
Wizzup: I don't think it's the screen blanking, power button has no effect
<erebion>
I'll just leace it running for an hour. Maybe it's just the emulation being really slow.
<erebion>
Oh, it works
<erebion>
Why does it work now..?
<erebion>
It definitely had nothing visible on screen the first one or two boot ups
<erebion>
Can't see my mouse pointer, so I cannot actually use it, though :/
<erebion>
Wizzup: My N900 will arrive in an hour or two. If you tell me the minimum that I'd need to implement in mobian-recipes for an image build, I'd try building one with that and test it. If it works, I could implement the rest of the current build script stuff in that branch.
<erebion>
Wizzup: Unusably slow in emulation, unfortunately
<sicelo>
aarch64 -> x86_64? i wouldn't be surprised
<erebion>
Well, as Maemo Leste runs on low end devices, by today's standards, I thought it might at least be enough to try out the UI, even if very slow.
g4rrgl3n0m4d has quit [Ping timeout: 248 seconds]
_fab has joined #maemo-leste
<erebion>
That current build script stuff really is hard to read
<erebion>
(compared with debos)
jrayhawk has joined #maemo-leste
<erebion>
So... You run daedalus.blend, it sources vars from daedalus.config, then the few dozens steps run and the image comes out of it?
<erebion>
is daedalus.blend really all that's required to build an image?
<Wizzup>
11:01 < erebion> Can't see my mouse pointer, so I cannot actually use it, though :/
<Wizzup>
I can see my regular mouse in virt-manager, unless I do the input lock thing
<Wizzup>
erebion: keep in mind you're not just emulating x86-64 but also opengl software renderer
<Wizzup>
erebion: yes, the current image builder is hard to read
<erebion>
Yeah, I'll just wait an hour for the N900 to arrive, then I'll be able to play with the UI
<Wizzup>
this is how we build the droid4 image for example
<Wizzup>
in CI/CD
<Wizzup>
wd=$(pwd)
<Wizzup>
release="$(readlink maemo.blend | sed 's/.blend//')"
<erebion>
Didn't realise there was something I could read
<erebion>
Will do
<Wizzup>
most people probably install u-boot from fremantle or flash it via 0xFFFF
<Wizzup>
so u-boot is *not* part of the .img file
<Wizzup>
(unlike with say sunxi images)
<sicelo>
don't build n900 u-boot. the build system can't do anything with it
<sicelo>
ah, Wizzup beat me to it
<Wizzup>
sicelo: just to be clear, our CI/CD does build a n900 u-boot version every time we build the image and scp that to maedevu separately
<Wizzup>
this is ultimately instrumented through arm-sdk, but I think for the initial debos stuff it probably doesn't make sense to reproduce that
<sicelo>
i see, but yes, we don't need it (and don't even have a way to use it)
* sicelo
is testing a patch for the wifi problem, and may submit MR in a bit ... bugs me a lot while daily'ing the Droid 4
<Wizzup>
sicelo: which problem, that upon disconnect, it doesn't stop trying?
<erebion>
Ah, ok
<erebion>
Where is the size of the rootfs defined?
<Wizzup>
erebion: arm-sdk/boards/ I think
<Wizzup>
see arm-sdk/boards/nokia-n900.sh
<Wizzup>
(and again, ignore the gitkernel/gitbranch and kernel building stuff there.)
<Wizzup>
this script is also what builds u-boot fwiw
apac has quit [Ping timeout: 272 seconds]
<sicelo>
Wizzup: yes, or remaining 'connected' falsely
<Wizzup>
sicelo: so it didn't used to do this
<Wizzup>
but fmg added this as a 'fix' to the droid4 kernel driver being buggy
<sicelo>
yes. that's what i think i've fixed
<Wizzup>
the actual kernel driver bug?
<sicelo>
let me submit the MR, and see if you can test it right away. if it also works for you, and we get some testing from fmg as well, then we could include that in the official daedalus release, becasuse the current behavior is really not nice
<sicelo>
no, i fixed fmg's MR
lel has quit [Ping timeout: 252 seconds]
<sicelo>
Wizzup: git.maemo.org having issues?
ceene has quit [Ping timeout: 252 seconds]
<Wizzup>
sicelo: just for a moment, was redoing some wires
<sicelo>
give that a try and let's see where that takes us
arno11 has joined #maemo-leste
<sicelo>
from what i understand from reading fmg's findings in backlog, and trying to understand the subsequent commit - the issue is that the D4's driver will send "disconnect" event during or immediately after a scan, which throws things off because it resets our state
<Wizzup>
not during a scan, but during association
<Wizzup>
this will make it so that if we get disconnected temporarily, we won't reconnect again, which was a side effect from fmg's change, but icd2 has reconnection mechanisms, so we better just use those yeah?
<sicelo>
from my testing, the MR has desired effect :-)
<Wizzup>
imo we can just merge and build for -devel now
<sicelo>
sounds good to me. then we can get more testing.
<sicelo>
and yeah it would be really great to have solved this issue by the time we go 'official' with daedalus
<Wizzup>
I'm going to need to help remembering what changes since the last news post :)
<Wizzup>
want ot add a debian/changelog entry or shall I do it
<Wizzup>
I'll do it
<Wizzup>
sicelo: ah... the gconf fix was already in maemo/daedalus I think
<Wizzup>
hm... I am not sure if your fix is correct here
<Wizzup>
(for gconf)
<Wizzup>
I'll fix master
<sicelo>
mmm, on device, all other schemas are in /usr/share
<Wizzup>
maemo ones are not
<sicelo>
in fact, i was going to ask why dh_gconf isn't doing what i think it should
<sicelo>
oh
<sicelo>
Wizzup: at least on my Droid 4, /etc/gconf/schemas dir does not exist
<Wizzup>
it exists on mine
<Wizzup>
and has all libicd schemas in it
<Wizzup>
I'm not very hot on revisiting the general place for gconf topic, we tried to fix it proper and realised it wouldn't work due to some dh stuff
<Wizzup>
the current pkg installs it into /etc/gconf/schemas
<Wizzup>
and that seems to work, so let's stick to that for now
<Wizzup>
what you built from master likely did not, because that lacked one commit that was only in maemo/daedalus
<Wizzup>
omg am I jus out date?
<Wizzup>
let me double check
<Wizzup>
ah, no, I don't think so
<sicelo>
sure, i only did the gconf part because it wasn't building otherwise :-)
<sicelo>
as long as we end up with the updated code, i'm ok with it
<Wizzup>
building now
<Wizzup>
I'm hopeful that we can migrate to forgejo actions this year
<Wizzup>
(and debos for images would be wild/great)
<Wizzup>
(forgejo actions as opposed to jenkins)
<sicelo>
as for the gconf schema topic ... you may be outdated :p
<sicelo>
so yeah, let's keep it in /etc as you say. i think i get how it works from there
<Wizzup>
I think otherwise triggers don't fire or something silly, don't remember exactly
<sicelo>
however, your having them in /etc on device is suspect either way ... since dh_gconf would have moved them :p
<Wizzup>
probably because I do a bunch of dev it
<sicelo>
*should
<Wizzup>
remnants probably
<sicelo>
right
<sicelo>
:-)
pere has quit [Ping timeout: 244 seconds]
<Wizzup>
bbiab
<arno11>
sicelo: on my daedalus (from fresh img and updates), i have schemas in both /etc and /usr/share lol
<arno11>
just clock and him in /etc btw
<arno11>
and everything else in /usr/share
<arno11>
nope, in fact, everything in /usr/share
<arno11>
clock and him-ui3 in both directories
<erebion>
Wizzup: see arm-sdk/boards/nokia-n900.sh: size=4000 as in 4 GB rootfs?
funderscore is now known as f_
<arno11>
@4GB, yes iirc
f_ is now known as funderscore
Anasko has joined #maemo-leste
System_Error has joined #maemo-leste
<erebion>
Wizzup: And what packages need to be added for the UI? Right now I only have Devuan and need to add the Maemo Leste specific packages. I can find some things in the build scripts, like the hostname getting set, some packages getting cleaned up, things like that. But I can't find the Maemo specific stuff that needs to be added to Devuan.
<arno11>
erebion: i think you mostly need hildon-meta and hildon-meta-core pkgs iirc
<erebion>
My N900 and N9 arrived. Both don't really look like they've been used much, although the N900 has an old U-Boot version flashed to it. I should probably reset it to some sort of factory state.
<arno11>
erebion: IMO you should start your n900 'as is' first, to see which Fremantle version you have inside
<erebion>
1.3
<arno11>
ok nice
<arno11>
see wiki for u-boot version needed
<erebion>
I've seen that somewhere in the menu, but can't find it now xD
<arno11>
'U-boot with kernel 2.6.28-omap1'
<arno11>
*from fremantle
<arno11>
and 'linux kernel for power user'
<erebion>
Yeah, exactly that one
<arno11>
cool
<erebion>
Where does it say the power user part?
<arno11>
that's another recommended pkg
<arno11>
just follow the wiki
<erebion>
Will do. Right now busy trying to re-implement the build script in debos xD
<arno11>
ok
<erebion>
>After updating device firmware with included script (eg. flash-droid-4-fw.sh):
<erebion>
But where do I start to get the flash on this phone back to a factory state? Or how do I replace someone's U-Boot build with my own?
<erebion>
The guide seems to assume I already know that all
<erebion>
>If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly (dual boot mode):
<erebion>
idk
<erebion>
Do I want to?
<erebion>
I'm just looking for a bootloader image to flash and a rootfs to flash
<erebion>
Don't want to keep what was left on the device by a previous owner.
<Wizzup>
16:01 < erebion> Which one do I want to use?
<Wizzup>
you can use either the one from the link above, or the one we build
<Wizzup>
all of them should work, with different functionality
<Wizzup>
I'd use whatever the wiki page recommends
<erebion>
But why would I flash Mameo Leste to the microSD?
<sicelo>
erebion: i already explained?
<sicelo>
you can use emmc, but we don't bother because it's much slower than SD card <<---
<erebion>
I already have eMMC and there's a really old OS on it, why not flash there?
<erebion>
Ah, yes
<erebion>
How did I miss that?
<erebion>
wt
<erebion>
f
<erebion>
thx
<Wizzup>
yeah there's a few reasons, one of them is that I like to keep the old nokia OS intact
<sicelo>
we can explain the uboot situation in a bit more details if it helps you to understand it better
<Wizzup>
the other is that the emmc is hard to replace so if we have some daemon going nuts and fills up the emmc with nonsense logs, it's not great
<Wizzup>
and yes, the microsd can be faster than emmc
<erebion>
Makes sene
<erebion>
*sense
<erebion>
Thanks. That's exactly what I would have loved to see in the docs instead of just "here's how you flash it to you microSD without any info why"
<sicelo>
the N900 has a stock bootloader, and a specific kernel partition. we install/flash our 'custom' uboot in the kernel area. then u-boot boots the normal linux kernel (in legacy uImage format).
<sicelo>
the flashing steps happen outside of the distro/Leste, and we never touch them afterwards
arno11 has left #maemo-leste [#maemo-leste]
<sicelo>
as long as you have proper rootfs, and the uImage in /boot on first partition of the SD card, it'll boot
<erebion>
Huh, neat
<erebion>
Then I'll need to know where in the blend file that uImage is added
<erebion>
I really wish there were a lot of comments explaining both files
<erebion>
T
<erebion>
Then it'd be really easy to do that all in debos
<erebion>
Oh and as I leave the eMMC as is and not use it for Maemo Leste: How do I flash that one to the latest version from Nokia?
<sicelo>
i also have never checked who creates the uImage ... might even be the kernel package itself
<erebion>
Installing Hildon using debos, ist tries to start, which then fails:
<Wizzup>
but I imagine debos must have a way for this
<Wizzup>
actually I figured debos would do this by default, but that is just a guess
<erebion>
It shouldn't do that, maybe it doesn't do that on systemd, but does not have provisions for OpenRC
<Wizzup>
erebion: or maybe that is it, it only works for systemd (sigh)
<Wizzup>
in any case the policy-rc.d should work
<erebion>
nope
<erebion>
still tries to start it
<Wizzup>
erebion: can you share some logs + how you set it up
<erebion>
Wizzup: Right now it is a chaotic mix of Mobian-recipes + Devuan repos + Maemo repos xD
<Wizzup>
ok, well, make sure the file is there, has +x perms, is in the right place, etc
<erebion>
I will push all the stuff to git once I have something that at least boots and I have cleaned it up a bit, right now it's complete mess, as my goal for now is only to get it to boot and then I will make it look good.
<erebion>
The file exists and is executable, I added a task that does ls -l and cat
<sicelo>
you can push 'dirty' work :-)
<sicelo>
and maybe someone else might have the time to also help you clean it up
parazyd has quit [Ping timeout: 248 seconds]
<Wizzup>
btw, I am planning to turn off pkgweb creation for beowulf soon and later for chimaera
<Wizzup>
the files will probably still be there / searchable, but I don't think we need to search for new pkgs, right?
parazyd has joined #maemo-leste
<Wizzup>
erebion: there are some more tips in the debian chroot wiki that you can try
<Wizzup>
I don't know if it matters but if this tab vs space issue?
<Wizzup>
but is this*
<Wizzup>
and I wonder if it needs to run before deboostrap?
<erebion>
shouldn't but I'll change it
<erebion>
It can't, as there's no chroot yet
<Wizzup>
ok
<erebion>
Tabs vs spaces on what line?
<Wizzup>
the line that I linked
<erebion>
GitLab does not show me
<Wizzup>
rootfs-maemo-leste.yaml line 33
<erebion>
It's all just spaces and no tabs anywhere
<Wizzup>
ok, strange that it's highlighted in red
<erebion>
idk why
<erebion>
yammlint says lines 35 and 36 are "too long", maybe because of that
<Wizzup>
ok
<erebion>
Anyway, for now my branch will only deboostrap Devuan, set up Maemo repo key and repo and then install Hildon, where it fails
<erebion>
Plus some stuff from Mobian like adding a user
<erebion>
I'd already be done if the blend files were easier to read xD
<Wizzup>
well, there's perhaps also specifics inside arm-sdk or the libdevuansdk stuff which I'm trying to help you navigate
<Wizzup>
but right now the problem seems to be starting/stopping services when that should not happen
<sicelo>
as far as users go, you want to setup username as 'user' for now
<dsc_>
Wizzup: git.maemo down?
<dsc_>
nvm
<erebion>
./build_maemo_leste.sh -t omap3 -s -u user <- then this :D
<erebion>
the -u is for username
<erebion>
Account setup: Jabber (gabble) vs XMPP (haze), what's going on there?
<erebion>
What do I have to choose for what reason?
<dsc_>
erebion: what are you trying to achieve and where? :P
<erebion>
Adding an XMPP account :D
<dsc_>
ah k, pick Jabber
<Wizzup>
dsc_: I was trying out my custom forgejo build but reverted it
<sicelo>
erebion: xmpp? you're in Hildon now?
<Wizzup>
dsc_: should be back
<dsc_>
ty
<Wizzup>
I'll make a test bed for git.maemo.org so I don't test live :)
<Wizzup>
good to know people ues it
<Wizzup>
I just want the fscking code search to be enabled :)
funderscore is now known as f_
<sicelo>
:p
<erebion>
sicelo: Flashed Maemo Leste to an SD card, after I got the reason for that, now trying it out. Looks neat so far, really like it. Bit unresponsive at times, but still great.
<erebion>
Reason for getting an N900 and N9 was to see whether they'd be good at being little portable XMPP clients
<dsc_>
erebion: how are you using xmpp?
<dsc_>
via conversations?
<Wizzup>
erebion: they're ok for it, but not if you need OMEMO
<Wizzup>
we were working on a tp client for qxmpp and support OMEMO that way, but at the time qxmpp did only OMEMOv2 (which most clients didn't do)
ikmaak has quit [Read error: Connection reset by peer]
ikmaak has joined #maemo-leste
<sicelo>
erebion: arno11 might have some suggestions to share with you on how to make the N900 a bit more bearable
_fab has joined #maemo-leste
_fab has quit [Ping timeout: 260 seconds]
arno11 has joined #maemo-leste
<arno11>
erebion: well, it highly/mostly depends on sd card speed: i.e with class 10, it will be slow and unresponsive sometimes anyway.
<arno11>
with good u3 (like sandisk extreme) and few tweaks, you can expect a responsive device (and fast hildon-desktop UI)
arno11 has left #maemo-leste [#maemo-leste]
vectis_ has quit [Ping timeout: 248 seconds]
akossh has joined #maemo-leste
System_Error has quit [Ping timeout: 244 seconds]
cockroach has joined #maemo-leste
cockroach has left #maemo-leste [#maemo-leste]
xinomilo has quit [Ping timeout: 248 seconds]
Livio has joined #maemo-leste
<Wizzup>
ok, full text search is avail not on git.maemo.org for all repos under leste (not leste-upstream-forks or other user forks)
<Wizzup>
s/not/now/
<Wizzup>
We can enable it for more repos, but not say organicmaps, mesa or linux kernel repos, those are purposefully excluded
dos has quit [Quit: Kabum!]
dos has joined #maemo-leste
<Wizzup>
translation too, now
akossh has quit [Quit: Leaving.]
<erebion>
arno11: I know the microSD is the issue, but it was the only one at hand, so it's also the best one I have :p
<erebion>
Where do I get factory images for the internal flash of the N900?
<erebion>
All links I found are dead
<erebion>
Would like to get the version in the flash to a clean state.