ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
danilogondolfo has quit [Quit: Leaving]
popolon has quit [Quit: Leaving]
KREYREN_ has quit [Remote host closed the connection]
DC-IRC has quit [Remote host closed the connection]
<IgorPec>
i have three things to put on agenda: check critical problems before starting RC builds, find out which boards to retire and general FYI (have prepared few items)
<Werner>
That's be late topics so yeah
<Werner>
--testen ob das ding noch funktioniert
<ArmbianHelper>
test whether the thing still works [de~>en]
<Werner>
Alright, translator if necessary is available. Wanna tell us something but prefer your native language? Put -- at the very beginning of your message. It will be translated from whatever you feed in to English.
<IgorPec>
lets wait awhile if more peole show up
<jock>
last time I checked, only me and you Igor where in the rsvp list
<IgorPec>
adeepv is there
<DC-IRC>
[Discord] <Werner> @adeepv ping
<IgorPec>
ok
<DC-IRC>
[OFTC] <Werner> --brückentest
<IgorPec>
notified ... so we can started
<Werner>
Bummer. Anyway, lets move on
<Werner>
#topic development Allwinner
ArmbianHelper changed the topic of #armbian to: development Allwinner (Meeting topic: Kereru release planning)
<DC-IRC>
[Discord] <adeepv> pong)
<IgorPec>
for allwinner we only have H618
<IgorPec>
that is new
<IgorPec>
and here i don't know much what is the progress, officially no board on the list, Bananapi zero is coming, but not within this release
<IgorPec>
others I am not aware if there is any critical problem
<IgorPec>
perhaps werner you know any ?
<Werner>
Nothing that critical that I kept it in mind
<IgorPec>
ok. what about retiring / advancing to supported in this segment?
<IgorPec>
i would say to drop forums from boards that are operational, supported, but with little to no activitiy
<Werner>
Needs to be checked. I guess there are a few that could be dropped
<IgorPec>
like duo and prime. Also I discussed with SwartzCat to drop Orangepi R1 (H3) from supported list. Also more or less no changes
<Werner>
#action Check forums of standard support boards with little to no activity to consider moving to csc
<IgorPec>
this means we only Have: Bananapi Zero, Opi Zero and Zero2 in the forums at the end, IMO
<Werner>
I could test against H3 and H6 but I think you have those in auto tests anyways?
<IgorPec>
yes, this is in autotests
<Werner>
Alright
<IgorPec>
the aim here is to reduce this board count
<IgorPec>
regarding Allwinner, this is more or less it
<Werner>
#topic development Amlogic
ArmbianHelper changed the topic of #armbian to: development Amlogic (Meeting topic: Kereru release planning)
<IgorPec>
here i count on adeepv to share some info
<DC-IRC>
[Discord] <adeepv> There are questions regarding the build system: in the standard 5.15 kernel from Ubuntu Jammy, there are issues with loop devices.
<IgorPec>
this PR was merged few moments ago
<DC-IRC>
[Discord] <adeepv> Lately, I've been busy with other projects, so I got a bit distracted)
<IgorPec>
1h ago, sorry
<IgorPec>
ok. for loop devices - is this happening on WSL?
<IgorPec>
this is known
<DC-IRC>
[Discord] <adeepv> lxc vm build with jammy
<Werner>
Upstream support for Buster will end on June
<Werner>
*in
<IgorPec>
buster ah, no i mean, we have legacy kernel there
<jock_>
yes everything for multimedia is pretty ok in mainline
<IgorPec>
this seems pretty old stuff from JMCC. I wonder if I just unpin that topic as it seems outdated
<jock_>
rk3399 and rk3328 also have h.265 patches, so multimedia framework is really legacy nowadays
<IgorPec>
great. what about other boards? PinebookPRO, Rockpro64 (mine doesn't boot), Rockpi 4
<IgorPec>
We have nobody doing anything there, complicated to support due to so many different revisions
<jock_>
no news from them sorry, I have a Rockpi-E (rk3328, CSC) which is also working pretty fine except for the rtl88x1 wifi
<Werner>
Then support must be dropped
<jock_>
which I'm trying to let it work with rtw88, but with no real success yet
<IgorPec>
yeah, i would also say to drop rockpi4, rockpiE kind of works
<IgorPec>
also rockpi-s is well maintained by Roman, but there is also a problem of many revisions and not all owrks
<jock_>
yes, rockpi-e could be promoted to supported, I usually use it to test changes on rk3328
<Werner>
#action drop rockpi4
<Werner>
#action promote rockpi-e (jock)
<IgorPec>
move back rockpi-s but dunno if its worth having forums for both?
<IgorPec>
this is another change i want to emphasises. we have some boards which are supported, but there are no users
<IgorPec>
also from adeepv ... do we need forum in standard support section?
<adeepv>
In the long term, yes, we plan to start worldwide sales by the end of the year.
<IgorPec>
we could say to enable it when posts starts?
<IgorPec>
in general, not just in this case. as it looks strange having a dedicated forum for one or two topics
<IgorPec>
ok, lets move this up at the end, otherwise ... #rockchip
<IgorPec>
3588
<adeepv>
ok. at this moment, there is no need
<IgorPec>
3588 Bananapi M7 is coming in
<IgorPec>
Nanopi R6S is also not very active, one user made mosst of the posts
<Werner>
In terms of known issues: legacy rk3588 kernel has the loadavg >=1 issue on opi5+
<IgorPec>
is there a fix yet?
<IgorPec>
i assume all boards have this problem?
<Werner>
Interestingly not. Opi5 is fine
<Werner>
No known fix I am aware of. Joshua is aware but won't take action
<Werner>
Waste of time dealing with already dead code :)
<IgorPec>
yes, indeed
<Werner>
Also mainline does good progress
<IgorPec>
yes, but that is also not really production quality
<Werner>
Not yet, indeed
<IgorPec>
do we have a ticket for this problem? Perhaps this is the only action here. Also I would propose to drop R6S to CSC. Its the same sh* as others and we don't plan any additional involvement
<IgorPec>
and R1LTS too
<Werner>
No, I don't think there is a ticket for that
<IgorPec>
Regarding Rock 5 is similar problem as Rock 4. Not sure what to do here
<Werner>
If there is nobody that deals with it the best is drop to csc
<IgorPec>
ok, then lets do that
smcavoy has joined #armbian
<Werner>
#action drop rock5 to csc
<Werner>
what about r6c? its similar to r6s?
<IgorPec>
yes, they are the same, just a bit different configuration
<Werner>
#action drop r6s/r6c to csc
totally_not_2o has joined #armbian
<IgorPec>
rock 3? anyone faimiliar how we are here?
<jock_>
nope
<Werner>
nope
<IgorPec>
i am just seeing there is no much activity, so lets CSC it
<Werner>
#action move rock3 to csc
<IgorPec>
there is some new board from Roman at PR, but this is already out of the scope of this meeting, too new
<IgorPec>
any other rockchip related?
lyri has quit [Ping timeout: 260 seconds]
<jock_>
yes
<totally_not_2o>
hello
<jock_>
About the rockchip patch archives cleanup...
<IgorPec>
aha, shoot
<jock_>
I would open a merge request with the removal of rockpi-s family, which contains only things for the rockpi S
lyri has joined #armbian
<jock_>
and those are only for legacy kernel
<jock_>
so Roman is chief there, but I would open a MR with a cleanup proposal
<IgorPec>
oh, yeah, let Roman decide but I think he is not interersted in legacy anymore
<jock_>
I don't know the status on mainline, but my understanding is that they work fine right now and keeping a legacy/vendor kernel for that still alive is useless
<jock_>
*work fine in mainline
<IgorPec>
yep, that is my understanding too
<IgorPec>
just not all revisions are supported, but this is not possible to cover just like that
<jock_>
perfect, just a question: do I open the MR before or after the release?
<IgorPec>
#action remove rockpi-s legacy stuff
<IgorPec>
leave it for next, as its not relevant to release
<jock_>
agree
<jock_>
I think it is done for me
<IgorPec>
k
<Werner>
Alright, let's move on
<Werner>
#topic development other SoCs/families
ArmbianHelper changed the topic of #armbian to: development other SoCs/families (Meeting topic: Kereru release planning)
<IgorPec>
other - odroidxu4 - it seems hardkernel has some issues
<IgorPec>
do we retire this board too? Problem is that 6.1.y is buggy
<IgorPec>
vs. 5.4.y
<IgorPec>
and both are some hybrid kernels, not mainline
<IgorPec>
we have leave as is
<IgorPec>
Raspberry Pi 4 and 5 seems ok
<IgorPec>
TI AM64B is maintained by vendor, have no info, probably ok
<IgorPec>
also here we have empty forum
<Werner>
So no issues :)
<IgorPec>
x86 is also fine, i would propose to enable Qemu x86 / arm64
<Werner>
#idea i would propose to enable Qemu x86 / arm64
<IgorPec>
we have Lenovo X13S that is used by few people and it seems alright
<IgorPec>
Jetson Nano was fixed by someone not long time ago, but don't know how is with care taking?
<IgorPec>
Mekotronics, Mixtile, ... all those are going to CSC
<IgorPec>
Xiaomi PAD is maintained by Amazinfate, promoted to supported?
<IgorPec>
Radxa E25 -> csc
<Werner>
You can use #action too ;)
<IgorPec>
now I am done ;)
<jock_>
@Igor do armbian has a mechanism to send back, from time to time, a packet from installed systems to identify the installation age and board?
<IgorPec>
no
<Werner>
There are no metrics, only armbianmonitor -u which must be issued by the user
<adeepv>
jock_ any internet query to servers not issued by user - bad idea
<jock_>
indeed is a bad idea if not issued by user, but in fact it would be an opt-in survey
<IgorPec>
we would need to develop that
<IgorPec>
action: x13s, xiaomi to supported
<Werner>
Kind of something like popularity-contest?
<IgorPec>
action: meko, mixtile, jetson nano, e25 to csc
<jock_>
many do that, if it is opt-in and it is done in good faith I see no harm and could help define which boards are still used around and needs to be kept supported
<Werner>
You have to use the # before action, otherwise it is not recognized :)
<IgorPec>
# action: x13s, xiaomi to supported
<IgorPec>
# action: meko, mixtile, jetson nano, e25 to csc
<adeepv>
space :)
<IgorPec>
#action meko, mixtile, jetson nano, e25 to csc
<IgorPec>
#action: x13s, xiaomi to supported
* IgorPec
gives up if this doesn't work ;)
<IgorPec>
ok, anything else here? moving on*
<Werner>
#topic build system
ArmbianHelper changed the topic of #armbian to: build system (Meeting topic: Kereru release planning)
<IgorPec>
this is relevant to release and what adeepv mention before regarding loop devices, which is probably host kernel problems
<IgorPec>
#action we have to workaround systemd changes before release.
<IgorPec>
ok
<Werner>
That's so far for the framework?
<IgorPec>
yeah, the rest seems fine as images are generating
<Werner>
#topic infrastructure
ArmbianHelper changed the topic of #armbian to: infrastructure (Meeting topic: Kereru release planning)
<IgorPec>
there are ofc other problems, burt nothing critical IMO
<IgorPec>
except mentioned
<IgorPec>
#info JSON powered download pages adds options for complex images mixing (stable, community, nightly, applications) and for images where we have boot loaders separate from image and where image is in different format (qcow2)
<IgorPec>
this was completed this week, so now all images shows up correctly, redirector was also reworked and is up and running
<IgorPec>
#info - documentation is getting JSON database as a center of development (WIP)
<adeepv>
ru <-> ua mirrors?
<IgorPec>
#action ru/ua mirrors needs to be addressed
<adeepv>
The problem is still relevant. We need to at least prioritize mirrors within the country
<IgorPec>
no, this was not implmented yet AFAIK
<IgorPec>
yes, this is the idea
<IgorPec>
but its up to Cats. We had enough of troubles with JSON switching
<IgorPec>
this problem remains
<adeepv>
At the moment the question is whether we will do our own fork or continue with you.
<IgorPec>
you mean to have own repository?
<adeepv>
The problem is that there is 90% no internet connectivity between the countries for various reasons on both sides.
<IgorPec>
i am aware of the problem
<DC-IRC>
[Discord] <sunmaster> How do I fsck root/boot-drive?
<IgorPec>
but i don't know how far is cats with implementing solution
<adeepv>
jethome own repositories is already up and running. but our users
<adeepv>
but our users have been having a lot of trouble with updates lately (even if you don't take ideological issues into context)
<adeepv>
it's just that the package updates aren't going through
buzzmarshall has joined #armbian
<IgorPec>
there are other possible workarounds that can be executed
<Werner>
Maybe remove both ru and ua mirrors from rotation until this is fully addressed?
<IgorPec>
live patch that would set mirror related to COUNTRY settings
<IgorPec>
that is also an option
<IgorPec>
just pick one and we will do it
<IgorPec>
#action temporally disable UA and Russia apt mirrors
<Werner>
I'd say we skip the agenda directly to misc since we overshot time once again :)
<Werner>
#topic misc
ArmbianHelper changed the topic of #armbian to: misc (Meeting topic: Kereru release planning)
<IgorPec>
yes, lets close it ... i am disabling mirrors as we speak @adeepv
<Werner>
IgorPec: you mentioned a few open topics at the beginning of this you wanna cover?
<IgorPec>
yes, more just infos
<Werner>
shoot
<IgorPec>
#info few days ago one german company contacted me for platinum support on their Rockchip HW. They forgot to name the SoC
<Werner>
oO
<IgorPec>
#info new boards with platinum support: Bpi M7, perhaps Zero
<IgorPec>
#info - documentation is getting JSON database as a center of development (WIP)
<IgorPec>
#info - Swartkat is also moving to new board, undetermined atm. I have asked him to help Terrain kicking armbian-config for now
<IgorPec>
so this is more or less all from my side.
<Werner>
So its time to check if it crashes or does the job
<IgorPec>
yeah!
<Werner>
#endmeeting
<ArmbianHelper>
Meeting ended Sat Feb 10 16:34:16 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
<IgorPec>
and for showing up this Saturday (afternoon for me)
<Werner>
likewise
<Werner>
afk - kitchen
<jock_>
just a question: don't know if this is relevant, but a forum user today reported that imola and users.armbian.com are down
<cornelius>
unless you want lots of complaints. i was able to get it to boot 6.8-rc3, but no hdmi. I assume this will get ironed out eventually, but in my testing its not ready for prime time yet.
<IgorPec>
jock_: thanks for informing me, let me check
<jock_>
you're welcome, thanks!
<IgorPec>
its back on
<jock_>
oh that was fast :D I'll report on the forums, thanks again!
<IgorPec>
i knew what to do ;)
<cornelius>
there has been some movement for dts inclusion into mainline for the M4BERRY. which would be beneficial for the ZERO. i have no clue if the BERRY has the same issues as the ZERO though.
<IgorPec>
i can ask for a board mix and we do some preliminary investigation?
<cornelius>
sounds like a plan.
<jock_>
ok I got to go, see you on next meeting, bye!
<IgorPec>
bye
jock_ has quit [Quit: Leaving]
junaid_ has quit [Remote host closed the connection]
archetech has quit [Quit: Konversation terminated!]
alekksander has quit [Quit: Konversation terminated!]
archetech has joined #armbian
zeemate has quit [Ping timeout: 240 seconds]
<DC-IRC>
[Discord] <therealmarcone> Is there any particular reason that on first boot the root partition isn't extended to use the entire disk (it leaves a little over 1GB of unused space), and is resized to an odd number of sectors?
<DC-IRC>
[Discord] <therealmarcone> (I'm using the Armbian_24.2.0-trunk.519_Orangepizero3_trixie_current_6.6.15_minimal image in case that matters)
<DC-IRC>
[Discord] <viraniac> If I understand correctly, the root partition did got resized, but still left 1GB of unused space at the end?
<DC-IRC>
[Discord] <therealmarcone> Did you mean to link to a different issue? Because the resize operation being a "first boot" task doesn't really have much to do with why it resizes to an uneven number of sectors while leaving free space at the end.
<DC-IRC>
[Discord] <therealmarcone> (If it isn't done on purpose I'll see if I can fix it)
<DC-IRC>
[Discord] <igorpec> systemd messes up with startup services at certain conditions due to upstream changes. this is what came up at once. as this is trixie and board that is not supported ... it can be something else too
junaid_ has joined #armbian
junaid_ has quit [Client Quit]
lyri has quit [Ping timeout: 252 seconds]
junaid_ has joined #armbian
lyri has joined #armbian
TheCoffeMaker has quit [Ping timeout: 240 seconds]
adeepv has quit [Quit: Leaving]
TheCoffeMaker has joined #armbian
TheCoffeMaker has quit [Quit: So long and thanks for all the fish]
califax has quit [Remote host closed the connection]
califax has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
junaid_ has quit [Remote host closed the connection]
Neoon has quit [Remote host closed the connection]
Neoon has joined #armbian
zeemate has joined #armbian
<DC-IRC>
[Discord] <nicod_sbc> There seems to be something wrong with VIM3. GPU issue. In desktop it crashes and with server display flikkers out at times.
<DC-IRC>
[Discord] <nicod_sbc> It's a panfrost issue. dmesg shows gpu errors but it crashes every time I do armbianmonitor -u.
<DC-IRC>
[Discord] <therealmarcone> That aligns `last sector` to a 16 MB boundary, so the last sector of the partition will be made to start on a 16 MB boundary, instead of ending before the 16 MB boundary as was clearly the intention. In other words, it should subtract one from `lastsector`.
<DC-IRC>
[Discord] <therealmarcone> That aligns `lastsector` to a 16 MB boundary, so the last sector of the partition will be made to start on a 16 MB boundary, instead of ending before the 16 MB boundary as was clearly the intention. In other words, it should subtract one from `lastsector`.
archetech has quit [Quit: Konversation terminated!]