<Wizzup>
freemangordon: I set up push mirroring for conversations and hildon-meta and have a programmatic way to set it up now, and it seems to work fine
<Wizzup>
I will set it up for all the other repos tomorrow
<Wizzup>
freemangordon: do we want to migrate anakin-linux / lime2-linux / linux-beryllium / rockchip-linux ?
<Wizzup>
cloning all upstream-forks now too, but let's (re)move some of these to leste-deprecated or so
GaryM_ has quit [Ping timeout: 260 seconds]
akossh has quit [Quit: Leaving.]
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
parazyd has quit [Ping timeout: 252 seconds]
parazyd has joined #maemo-leste
lyubov has quit [Read error: Connection reset by peer]
lyubov has joined #maemo-leste
xmn_ has joined #maemo-leste
xmn has quit [Ping timeout: 248 seconds]
vectis_ has quit [Ping timeout: 276 seconds]
xmn_ has quit [Quit: Leaving]
vectis_ has joined #maemo-leste
xmn has joined #maemo-leste
vectis_ has quit [Ping timeout: 248 seconds]
joerg has quit [Ping timeout: 245 seconds]
joerg has joined #maemo-leste
_fab has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
ceene has joined #maemo-leste
hexnewbie has joined #maemo-leste
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
<sicelo>
we're not building beryllium images anymore?
<sicelo>
ah, last build over 3 years ago and no one has complained ... a bit sad, since the device is very well supported by mainline. iirc recently camera started working too. anyway, if no one has it and maintains it, it's fate is sealed
pere has quit [Ping timeout: 265 seconds]
halftux has joined #maemo-leste
System_Error has quit [Ping timeout: 264 seconds]
xes has quit [Ping timeout: 248 seconds]
System_Error has joined #maemo-leste
<halftux>
Wizzup: The magic for debian rpi and boot partition gets installed by the raspi-firmware package and it can self trigger a script or it gets triggerd when kernel gets updated
<halftux>
the scripts will copy new files to /boot/firmware
xes has joined #maemo-leste
pere has joined #maemo-leste
<halftux>
sicelo: the firmware and bootloader for rpi needs to be in the vfat because a CPU inside the GPU starts a binary blob from a small ROM which then loads the GPU firmware from the first fat partition. The GPU loads then the linux kernel from the fat partition into the RAM. After this the ARM CPU is switched on and booting with the loaded kernel. So the GPU is acting like a BIOS.
<sicelo>
ah yeah, I remember that now. never had an RPi. RPi4 still works that way, or it's up to the 3?
<halftux>
rpi 4 is similar but has now also an eeprom
<Wizzup>
sicelo: not since beowulf I think
<Wizzup>
sicelo: which device is that, the pocophone?
<Wizzup>
halftux: thanks for all the resources, so it seems like we should just ensure the right labels get set?
<halftux>
yes for the updates we should have the same labels. For the first image build I don't know if the raspi-firmware package can be installed
<Wizzup>
hm, why not?
<Wizzup>
freemangordon: push mirrors are now set up for core repos, this means that git.maemo.org will keep github in sync, but it's a one way sync: it's possible that if you now push to github our instance will remove it
<Wizzup>
all upstream repos push back now too
nela79 has quit [Ping timeout: 245 seconds]
nela7 has joined #maemo-leste
<halftux>
Wizzup: I can't judge I have not enough knowlegde about image builder. When the partiton gets created from one changeroot it could work. However I could try to build a new image. So which bit I must tweak to get first partition mounted on /boot/firmware instead of /boot? Is it somewhere in the sdk library in the helper script?
<Wizzup>
halftux: just for my understanding, is there still a place for /boot as well?
<halftux>
Or could I change it in the board config or board shell script
<halftux>
boot must be on the second partition the kernel gets installed there. So in principle you have the kernel twice
<Wizzup>
so there are different partitions for /boot and /boot/firmware
<Wizzup>
btw, I wonder if we should just switch to debos or whatever gets used these days and make that works with maemo/devuan
<Wizzup>
I will look at the image-builder changes that we can make, although I feel like perhaps in the near future we should switch to using debos or something more 'standard' for building images
<Wizzup>
the image-builder has a certain way it wants things to go (boot on separarte partition, root partition and nother else)
<Wizzup>
so that's not ideal
<Wizzup>
but I love the idea of using debian kernel and firmware packages
<halftux>
so should I still fill a bug? Is it worth, chance to get it changed is low and maybe makes no sence when we step back from image-builder. If you still want one what should be the title?
<Wizzup>
I think just something like 'building raspi images again'
<Wizzup>
and yes issue is very helpful
<Wizzup>
and I will look at changing the image builder, but longer term, I think we want to do whatever debian is doing
<halftux>
ok
<Wizzup>
I really want raspi images and the research here is super helpful
<halftux>
maybe it is also a solution to mount vfat partition to /boot and to /boot/firmware it is not nice but I think it could work
<halftux>
...when this is possible with fstab
apac has joined #maemo-leste
Livio has joined #maemo-leste
<Wizzup>
right, something like this could be done
<Wizzup>
we can run shell scripts in various parts of the process
<Wizzup>
it's just finnicky
<Wizzup>
did you manage to build an image without the additional firmware partition, manually copy some things and get that to work?
<Wizzup>
I'd be interested in that
vectis_ has joined #maemo-leste
<halftux>
yes I used a tiny raspi3 chimaera image copied /boot/*kernelfiles from linux-image-arm64 to vfat and also firmware files from https://github.com/raspberrypi/firmware/ (not tried files from raspi-firmware, but should work)
udder has quit [Quit: die in fire]
udder has joined #maemo-leste
<halftux>
modified config.txt (sorry for spam):
<halftux>
arm_64bit=1
<halftux>
enable_uart=1
<halftux>
upstream_kernel=1
<halftux>
device_tree=bcm2837-rpi-3-b-plus.dtb
<halftux>
kernel=vmlinuz-6.1.0-32-arm64
<halftux>
initramfs initrd.img-6.1.0-32-arm64
<Wizzup>
does linux-image-arm64 get installed in our image or did you also install it manually?
<Wizzup>
(also; this would be great to get in the issue report)
<halftux>
I need to look into my new build image. If it does.
<halftux>
But it does with the generic-arm64 build so I guess yes
<Wizzup>
ah sorry, this was the arm64 build?
<Wizzup>
I thought you said the raspi3 image, sorry
<Wizzup>
I have a bunch of raspis here and I figured if I can try it here it might be easier to look at the image-builder things
<halftux>
I used raspi3 image but kernel from generic-arm64 build
<halftux>
now I edited the raspi3 script remove kernel build and put the /bin/true kernel from generic build into raspi3 script
Guest6917 is now known as buZz
<halftux>
oh I forgot to edit beowulf.config to add linux-headers-arm64 and linux-image-arm64 to raspi*
<Wizzup>
did you edit the beowulf config or the chimaera one?
<halftux>
oh sorry for confusion I now try daedalus befor I build chimaera but there I did not edit config everything manual
Livio has quit [Ping timeout: 264 seconds]
<halftux>
and you need to copy all dtb files from /usr/lib/linux-image-6.1.0-32-arm64/broadcom/ to vfat bootfs
<Wizzup>
halftux: ok, can you pls put this in the git.maeom.org issue
<Wizzup>
I'll dig up my rpis
pere has quit [Ping timeout: 252 seconds]
<Wizzup>
hey I have a raspi3 here :)
<Wizzup>
two atually
<halftux>
when I log into git.maemo.org with github account I get Internal server error 500
<halftux>
should I create an account?
<halftux>
ok I managed it with the second try
<Wizzup>
halftux: did you log in with github?
<sicelo>
Wizzup: +1 for debos
<halftux>
yes
<halftux>
I will wait for image build and then writing the issue with the new steps.
<Wizzup>
halftux: ok, thanks, and please do, the issue will help keep track and give context
ceene has quit [Ping timeout: 248 seconds]
pere has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
i got the server error 500 too, but now able to log in to GH and git.maemo.org from n900 using new dillo :D
<arno11>
it is fast. we really need to build the new dillo imo
<arno11>
however, GH UI is not really usable with new dillo but forgejo is quite ok
<Wizzup>
:)
<Wizzup>
arno11: I can make a repo for dillo, should it be upstream forks or extras?
<Wizzup>
usually the easiest way is to take debian's packaging and add it to the new source
<Wizzup>
and then update the changelog etc
<arno11>
ok np
<arno11>
(btw i tried to add a random comment to an issue from dillo, it works fine. display is ugly but fast
<Wizzup>
:)
<arno11>
i also finally find the motivation to debianize maemo-gpt. still some code to clean but almost ready now for extras
<Wizzup>
cool, hopefully it isn't too hard to figure out the packaging
<Wizzup>
once you get used to it, it's mostly just copy pasteing some boilerplate
<arno11>
i meant *found. debian stuff is already ok
<Wizzup>
:)
<halftux>
there is already a rpi image issue from you Wizzup. I will comment to that. restore raspberry pi images #758
<mkf>
got my n900 rooted \o/
<mkf>
s/n900/v20/g
<mkf>
next is getting mainline linux running on it
_fab has quit [Quit: _fab]
<arno11>
oh nice
<arno11>
Wizzup: btw i still need to port pcsx and pico to daedalus (quite trivial) but i still need a fix for osso-games-startup (issue #763) for drnoksnes
<Wizzup>
sounds good
_fab has joined #maemo-leste
apac has quit [Ping timeout: 276 seconds]
<sicelo>
nice. upower upstream mostly approves of our patch ... there are a few modifications to make, but otherwise there will be minimal adjustments :-)
xmn has quit [Read error: Connection reset by peer]
<halftux>
I tried to log in with github there was that error and I tried again and there was no need of a password but asking if I would connect to an existing account and I said no
<halftux>
^^ignore that :-)
<Wizzup>
ok :)
<halftux>
Wizzup: but I posted the instruction hope everything is clear
<Wizzup>
halftux: this is perfect, thank you
<halftux>
compared to chimaera there are some issues in daedalus I made a second comment.
<Wizzup>
strange that usb keyboard wouldn't work, maybe different debian kernel version
<freemangordon>
Wizzup: what about CI?
<freemangordon>
what repos will it build?
<Wizzup>
git.maemo.org
<Wizzup>
for everything except extras and l10n
<Wizzup>
changes on git.maemo.org to core and upstream-forks are auto pushed to github upon commit/push, and also synced every 8 hours
<freemangordon>
great
<Wizzup>
this is done using an api key tied to my account, there was no way to do that with an api key tied to an orga
<Wizzup>
but I think that's fine
<Wizzup>
I can this locally:
<Wizzup>
I ran*
<Wizzup>
sed -i 's/git@github.com:maemo-leste\//git@git.maemo.org:leste\//' */.git/config
<halftux>
Wizzup: your right to many keyboards on my table it is working.
<Wizzup>
:D
<Wizzup>
I guess that means hdmi wake up also works then
<halftux>
yes think so but I also disabled the lock screen
<halftux>
after wake up mouse is in the left upper corner and does not move only after a mouse click
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
halftux: oh yes the lock screen might be the issue here, you need to press the 'power button'
<Wizzup>
only after click could be a power feature
<Wizzup>
power saving
xmn has joined #maemo-leste
<Wizzup>
halftux: building an image with your changes on phoenix now, it doesn't have the final steps yet, but I at least made all your mods
<halftux>
ok nice hope it will work made a small untested change to daedalus.config that cmdline.txt and config.txt gets copied. Therefore I added copy-root-overlay. I just building it now with this change. But just for record check if the two files are on the bootfs partition.
<halftux>
not daedalus.config I mean raspberry-pi3.sh
buZz has quit [Ping timeout: 265 seconds]
buZz has joined #maemo-leste
buZz is now known as Guest513
<Wizzup>
I think we can make a change to set labels on some of the partitions in the devuan sdk for image building, do you know if we need to use dos or gpt for these labels?
<halftux>
I don't know but I would use dos for rpi
<Wizzup>
ok, and we can set labels that way?
<Wizzup>
because that is what we need right?
<halftux>
we don't need labels we can use partitions in fstab
<halftux>
so debian are using labels in cmdline.txt and fstab
<halftux>
you are building chimaera raspi3 image right?
akossh has joined #maemo-leste
<halftux>
did you edited the right config for kernel usage?
<halftux>
maybe I missed something in regard of the labels but I think we are fine if we are using /dev/mmcblk0p1 and /dev/mmcblk0p1 unless we want to support more options as only sd cards
<Wizzup>
halftux: oh, I thought the postinst scripts/triggers you mentioned look at the labels, but if they just look at things being mounted, it might be ok
<Wizzup>
18:10 < halftux> you are building chimaera raspi3 image right?