<arno11>
Wizzup: i fixed most issues in cloudgps (geocoding, routing, markers and route rendering)
<arno11>
it is very fast on my n900 (compo off)
<arno11>
will share soon
_fab has joined #maemo-leste
System_Error has quit [Ping timeout: 240 seconds]
hm has quit [Remote host closed the connection]
hm has joined #maemo-leste
hm has quit [Remote host closed the connection]
hm has joined #maemo-leste
Livio has quit [Ping timeout: 240 seconds]
<arno11>
(force) portrait and 3d view also work fine on n900
fmg_d4 has joined #maemo-leste
<arno11>
i still need to test gps sat fix and position rendering properly
Livio has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
apac has joined #maemo-leste
<Wizzup>
arno11: great
pere has joined #maemo-leste
Livio has quit [Quit: leaving]
apac has quit [Ping timeout: 244 seconds]
pere has quit [Ping timeout: 244 seconds]
narodnik has quit [Quit: WeeChat 4.7.0]
narodnik has joined #maemo-leste
System_Error has joined #maemo-leste
_fab has quit [Ping timeout: 252 seconds]
narodnik2 has quit [Quit: WeeChat 4.7.0]
narodnik2 has joined #maemo-leste
apac has joined #maemo-leste
Smatkovi1 has joined #maemo-leste
Smatkovi1 has quit [Client Quit]
Smatkovi1 has joined #maemo-leste
<Smatkovi1>
what should i do if during build of maemo-leste resolv.conf has wrong dns entries and cannot do apt update?
Smatkovi1 has quit [Quit: Leaving.]
Smatkovi1 has joined #maemo-leste
<Wizzup>
Smatkovi1: what do you mean 'during build of maemo leste'? what kind of build?
<Smatkovi1>
i want to build an n9 or n950 image
<Smatkovi1>
i could build an n9 image on the main branch today, but the kernel couldn't be built so i took the kernel from the 2019 release, but couldn't boot
<Smatkovi1>
now i try to rebuild on daedalus branch, but it cannot update sources anymore because resolve.conf points to localhost
<Smatkovi1>
and i don't know what files to edit to not make the rootfs read only or that resolve.conf doesn't get overwritten by a build script
<Wizzup>
'the main branch' is the 'image builder' ?
<Smatkovi1>
i mean chroot instead of rootfs
<Wizzup>
I wouldn't rely on a maemo leste image for the n9 ever having the correct kernel
<Smatkovi1>
yes i cloned image-builder
<Wizzup>
do you know of a kernel version that boots on the n9?
<Smatkovi1>
yes i could boot the version used in the 2019 image
<Smatkovi1>
but it's only called zImage, so i don't know which version it is
pere has joined #maemo-leste
<Wizzup>
I mean how about more recent mainline kernels?
<buZz>
Smatkovi1: the tool 'file' can read version numbers of binary kernel blobs, iirc
<buZz>
so ; file ./zImage
Smatkovi has quit [Quit: Smatkovi]
<buZz>
ok
<Wizzup>
right, but my point is that I am not sure if makes sense to try to build an old kernel inside image builder
<Wizzup>
just build a recent n900 image or so, and put your older kernel zimage and modules in it
<Wizzup>
and then figure out how to boot on our modern kernels - who knows, it might just work with the right dts
<buZz>
would likely be a more productive step to just figure out why the kernel doesnt build for n9
<buZz>
seems odd that it wouldnt build at all
<Wizzup>
do you think so? it's from 2019 so there's probably a million things that changed
<buZz>
well, maybe, yeah
<buZz>
i'm not their manager of time ;)
Smatkovi has joined #maemo-leste
fmg_d4 has quit [Ping timeout: 245 seconds]
<Smatkovi1>
lol meego has no file command and the output on pc is useless
<Smatkovi1>
zImage: Linux kernel ARM boot executable zImage (little-endian)
<Smatkovi1>
okay so i understand i can just take the n900 image and use this zImage to boot, but i don't know how to put other modules in it
arno11 has left #maemo-leste [#maemo-leste]
<Smatkovi1>
and to check: i can use an n900 image on an n950?
<Smatkovi1>
with the right kernel?
arno11 has joined #maemo-leste
<Wizzup>
mostly, yes
<Wizzup>
you would need to remove some udev files mostly, but that is leste-config-n900, so that is pretty easily done I think
<Wizzup>
btw, as part of the ci/cd work for forgejo actions we'll also have some docker images that folks can use to build packages with: https://git.maemo.org/leste-cicd/-/packages
<Wizzup>
for armhf/arm64/amd64 and chimaera/daedalus
Smatkovi2 has joined #maemo-leste
rhn has joined #maemo-leste
ac_laptop has joined #maemo-leste
<Smatkovi1>
intersting the directory for the n9 kernel is full of files about 1GB, only zImage wasn't created
<Smatkovi1>
okay i will look into this docker image
<Wizzup>
the docker image wasn't related to you fwiw
<Wizzup>
what is your goal, to make a merge request to build working images for the n9, or just to get it working for you first?
<Smatkovi1>
my main goal was to get it working for an n950, but i figured it would be maybe easier on an n9 first
<Smatkovi1>
if i manage to do it i gladly make a pull request
<Wizzup>
ok, and you're saying a really old image of ours boots on the n9?
<Smatkovi1>
yes it boots but doesn't react to touch input. there's also a youtubevideo someone made with the same result
<Smatkovi1>
i finally also acquired an n950 with 1Gb ram, but for me it doesn't boot meego with ubiboot.
<Smatkovi1>
i also tried booting the old image there, but after a few boot messages the n950 turns off
<Smatkovi1>
i tried also n9_easyboot to boot an .img file of the old build on the n950, but with a similar result
<Smatkovi1>
maybe i did something wrong booting the .img file
<Smatkovi1>
so to clarify maemo-leste tries to boot on the n950 but only succeeds partially, for meego ubiboot tells me to run a mainteanance boot
<Wizzup>
ok, so in general you'd probably want some other (preinstalled) system working first to ensure the hw works
<Wizzup>
regarding the n9 image, that's probably about where we stopped @ no touch working
<Wizzup>
have you done any research to see if others have the n9 working with a recent mainline kernel?
<Wizzup>
I have a n9 here but I realistically can't help for at least another 3-4 weeks
<Wizzup>
if it was me I'd try to boot some other OS and see if they have a recent n9 kernel that works, and then plant that on a droid4 or n900 image from maemo-leste and see if you can't get that to work
<Wizzup>
you can use qemu-arm and chroot to modify the image contents as you see fit
<Smatkovi2>
so the n950 has meego pr 1.3 installed, i also installed tls 1.3 and the recent root certificcates but flashed it again because ubiboot refused to flash, so it works
<Smatkovi2>
okay so a recent version of maemo-leste also won't have touch magically working?
<Smatkovi2>
not even on the n950?
<Wizzup>
hard to say, depends on the problem, but we don't have n9 or n950 images, so we haven't tested if things work
<Wizzup>
it could be a udev thing, it could be a kernel driver bug, it could be the touchscreen driver kernel module isn't built in our images
<Smatkovi2>
i see, so i would have to investigate
<Wizzup>
yes
<Smatkovi2>
i have too little knowledge to just put a kernel into an image of another device, on the pinephone pro i gave up after some time
<Wizzup>
I think others here might be able to help you with this, but yeah, nothing with embedded devices is trivial unfortunately.
<Smatkovi2>
so cool that you're doing this, it was a joy using maemo again on the pinephone and the droid4
<sicelo>
I think n9 requires some firmware for the touch. have a look at the elinux.org page
<sicelo>
Pyrenees something. maybe dmesg will give you a clue
<Wizzup>
Smatkovi1: it's only going to get better from here I hope :)
<Smatkovi2>
it says for the touchscreen driver: yes, the firmware is a .raw firmware and dt says no, so it's not in the device tree?
<Smatkovi2>
i don't really know what device tree is. i read earlier it describes the hardware the kernel boots from or something
<Wizzup>
This would make it easier for the community to build extras packages, we could make this the 'extras testing' or so, and still require jenkins for the 'stable' repo or so
<Wizzup>
(I'll make it so that it doesn't build daedalus if the branch is chimaera and vice versa)
xmn has quit [Read error: Connection reset by peer]