Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | Armbian 20.11 Tamandua released | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
<c0rnelius>
oh shit I was just getting beer
<c0rnelius>
I thought we just got started
<stipa>
c0rnelius: cheers bro
<c0rnelius>
stipa: cheers sir
<c0rnelius>
the shit I find most funny is the peps that fork Amrbian.
<c0rnelius>
Like why not just make a contribution and add to the project?
<c0rnelius>
seems stupid to me
<stipa>
well, there's no reason to reinvent the wheel
<c0rnelius>
Karmbian as an example
<IgorPec>
they are underestimating the project and overestimating their work :)
<c0rnelius>
lie what... ur using a diff rootfs? major change there!
<c0rnelius>
like*
* IgorPec
got a chance for a 1st beer today
<stipa>
c0rnelius: diid you hear that your balls could fell of if you take a pfizer vaccine?
<c0rnelius>
well exactly they under estimate all the work you all put in. keeping up with patching alone is a major under taking.
<c0rnelius>
stipa: not yet, but I heard ur dick can fly off if you eat gluten :D
<IgorPec>
its really nice to get something back. like from balbes fork - he is also trying to get even with upstream
<IgorPec>
bit sometimes its hard to do that
<c0rnelius>
for sure
torv has quit [Ping timeout: 240 seconds]
oida has quit [Ping timeout: 240 seconds]
<c0rnelius>
like I don't know whats up with rockchip and 5.10 yet, but it seems like a bit has changed.
stipa has quit [Ping timeout: 240 seconds]
<c0rnelius>
like some patching was added and yet other left out
<c0rnelius>
i need to review it, but have been to lazy and had other things to deal with.
<IgorPec>
yeah, its always sometghing
<c0rnelius>
exactly
<IgorPec>
in case you feel boored, we need folks to play with desktops
<IgorPec>
whole desktop engine has been changed and its comming to the main script in 1/2021
<IgorPec>
also easier to handle new upstream releases
<c0rnelius>
I messed around with someone here who was working on it for the C4. Checking out panfrost and all that, but in my testing it seemed like you guys needed to bump up mesa.
<c0rnelius>
And yeah panfrost is still a bit unstable
<IgorPec>
yeah, i just built it for N2 before on Ubuntu 21.04 but its also crappy
<archetech>
component called schedulaer isnt ready yet on pfrost
<IgorPec>
but perhaps it was not correct mesa, didn0't check
<archetech>
component called scheduler isnt ready yet on pfrost
<IgorPec>
ok
<archetech>
gives timeouts and faults
<IgorPec>
anyway, we have to come up with a system. that's our job, collabora are working on those 3d drivers
<c0rnelius>
I had build I was playing around with using mesa 20.3 and panfrost and video play back was pretty ok.
<IgorPec>
there is little we can do here
<c0rnelius>
nothing to call home about
<c0rnelius>
but better
* archetech
uses mesa 21.0
<c0rnelius>
some one the other day told me to check that out
<archetech>
IgorPec: you can still get DE work ready pfrost when it works will just pop in on an update
<IgorPec>
i know
<c0rnelius>
I've been doing my testing using bullseye.
<IgorPec>
we are on to that, but there are many small issues + we have no documentation ready
<archetech>
now what ya use in the mean time is a good question
<c0rnelius>
ubuntu has to much overhead
stipa has joined #armbian
<IgorPec>
in the mean time? One option is have enable / disable button :)
<archetech>
for a driver
<IgorPec>
currently we use that PPA - its actually 21.0
oida has joined #armbian
* archetech
wonders what rneese has been using on amlogic mali gpu's
<IgorPec>
i have to check tomorrow once again, perhaps xorg settings is failed
<archetech>
fbdev maybe
<IgorPec>
not sure if he is doing anything in this area
torv has joined #armbian
vbatts has joined #armbian
<archetech>
hmm if bullseye uses that mesa 21.0 i may build it later
<archetech>
see what works breaks
<c0rnelius>
I find Bullseye to be a much better test bed than you Ubuntu. Especially if you don't mind doing the build under chroot whilst putting the image together.
<archetech>
I got a nice bullseye from odroid using lxqt and idk what gpu driver
<IgorPec>
not sure about bullseye, but ubuntu focal / groovy / hirsute
<archetech>
c0rnelius: +1
<IgorPec>
in desktop, we also added Debian Sid
<IgorPec>
not sure how much diff is to bullseye
<archetech>
ubu 20.04 is what you use now Igor?
<IgorPec>
i tried 21.04 today, works
<archetech>
for n2?
<IgorPec>
yeah
<archetech>
that could be fun too 21.04
<IgorPec>
but it was one try. i was looking into other stuff
<IgorPec>
yeah, it boots
<c0rnelius>
There isn't a huge difference. But bullseye is headed for stable where sid obviously is always in flux.
<archetech>
21.04 = sid?
<IgorPec>
yeah, kind of. so we added two flux variants now, accesible under EXPERT="yes" only
<IgorPec>
21.04 = "sid"
<IgorPec>
its Ubuntu
<IgorPec>
most recent packages possible for Ubuntu
rneese has joined #armbian
<archetech>
cool Im on grovvy for odroid
<archetech>
20.10
<IgorPec>
groovy is already a bit old
<archetech>
but more stable than 21.04 id think
<IgorPec>
its last release tbh
<IgorPec>
oh ,thats for sure
<IgorPec>
but usually problems are kernel related
<IgorPec>
if you are super adventorous, you can use DEV kernel, 5.10.RC7 :)
<IgorPec>
i just pimp it together few hours ago, N2 boots
<archetech>
what config line did you use
<IgorPec>
for making image?
<c0rnelius>
one neat thing I figured out the other day, if you put net.ifnames=0 in ur boot cmdline it cleans up the interface naming schemes and gets rid of the crazy wlwhatever shit is going on there. So you can just have proper eth0 wlan0 going on and don't need any udev rules.
<archetech>
yea
<IgorPec>
don't have it for copy / paste anymore ... just DEV kernel, Hirsai Ubuntu, Desktop ...
<archetech>
ok
<archetech>
extrawifi off too ?
<IgorPec>
nothing off
<IgorPec>
everything works
<archetech>
k
<IgorPec>
we are 5.10.y ready
<archetech>
c0rnelius: you gonna do a build tonight?
<rneese>
are you building basic build or testing desktops ?
<c0rnelius>
build what?
<archetech>
of armbian bullseye
<c0rnelius>
nah
* IgorPec
ran out of beer. Crashing is next best thing
<archetech>
rneese: yeah ill test a de with my build thats what Igor wants peeps to try
<rneese>
ok
<c0rnelius>
I've been stuck dealing with the pi kids. seems my builder has garnered a lot of attention as of late and taking up to much time.
<archetech>
got LXQT yet?
<rneese>
its in there
<archetech>
ill do that with my bulls build
<rneese>
we are adding in a marker for aadvance build
<rneese>
at the min with new change dont know if the builder wil build
<rneese>
you can make 2 files in the dir for it to build
<archetech>
choose release base no bullseye choice now I remb why I havent used this
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 258 seconds]
ChriChri_ is now known as ChriChri
<rneese>
archetech, you using normal builder or desktop ?
<archetech>
normal ubu 20
<rneese>
ok
drobo_00 has quit [Ping timeout: 258 seconds]
archetech has quit [Quit: Konversation terminated!]
rneese has left #armbian ["Leaving"]
<greypilgrim[m]>
this is at least the second time my Pine H64 has fallen off the network and become unpingable even though the lights (including NIC) stay lit :(
<greypilgrim[m]>
gonna have to dig around logs better this time since i didn't find anything the first time
archetech has joined #armbian
<TRS-80>
greypilgrim[m]: No idea, man. You check the forum? Maybe you are not the only one. If not, make a thread? Supported Boards sections are like second level bug tracker, if you were not aware of that already.
<greypilgrim[m]>
i will look there if i don't find something. i'm still at the stage where i think i probably made a bad configuration somewhere
<TRS-80>
rodger dodger
<TRS-80>
In other news, it only took me a little under 2 weeks of harranguing, begging, pleading, submitting a patch, etc... but now exporting .org -> .md is now properly supported by sr.ht HTML renderer... Yaaaay!
<TRS-80>
And now I can continue uploading all my Orgmode / Elisp based projects there...
sassinak-work has quit [Ping timeout: 272 seconds]
sassinak-work has joined #armbian
Toast has quit [Ping timeout: 240 seconds]
TRS-80 has joined #armbian
<ArmbianTwitter>
@unfnknblvbl (unfunk™): hey @kobol_io I have a silly question - is it possible to take the array from my Armbian Helios 4 and put it in my newly arrived Helios64 and not lose data? That would certainly help with data migration... (23s ago)
<ArmbianTwitter>
@DieZuckerbude (Ben Zucker 🍰): @unfnknblvbl @kobol_io Depending on other features you may want or not want to use I suggest to pay close attention to the current support status list and decide your kernel accordingly: https://t.co/kUOJPHYa9g (3s ago)
<ArmbianTwitter>
@armbian (armbian): @ezeaqui @Fox0x01 Almost. Mainline is raw material ... Probably you can boot it, but for proper / good functioning you need to use Armbian improved mainline kernel which is currently based on 5.9.y (21s ago)
LanDi has joined #armbian
drobo_00 has joined #armbian
drobo_00 has quit [Quit: drobo_00]
drobo_00 has joined #armbian
ChriChri_ has joined #armbian
ChriChri- has joined #armbian
ChriChri has quit [Ping timeout: 260 seconds]
ChriChri_ has quit [Ping timeout: 258 seconds]
LanDi has quit [Remote host closed the connection]
drobo_00 has quit [Ping timeout: 240 seconds]
drobo_00 has joined #armbian
vbatts has quit [Remote host closed the connection]
drobo_00 has quit [Ping timeout: 260 seconds]
Toast has joined #armbian
drobo_00 has joined #armbian
drobo_01 has joined #armbian
drobo_00 has quit [Ping timeout: 256 seconds]
drobo_01 is now known as drobo_00
vbatts has joined #armbian
R0b0t1 has quit [Ping timeout: 265 seconds]
R0b0t1 has joined #armbian
archetech has quit [Quit: Leaving]
drobo_00 has quit [Ping timeout: 240 seconds]
archetech has joined #armbian
drobo_00 has joined #armbian
drobo_00 has quit [Quit: drobo_00]
raver has joined #armbian
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #armbian
pakcjo has quit [Ping timeout: 260 seconds]
<ArmbianTwitter>
@armbian (armbian): Having a reliable automated testing for boards is absolutely mandatory. Help us improve our autotests system! #community #software #making https://t.co/L2fd1N5JMlhttps://t.co/J0kM1ZElNA (17s ago)
marco44 has quit [Ping timeout: 258 seconds]
oida has quit [Ping timeout: 240 seconds]
<[TheBug]>
Afternoon
marco44 has joined #armbian
<IgorPec>
hej bug
marco44 has quit [Disconnected by services]
marco44_ has joined #armbian
torv has quit [Remote host closed the connection]
torv has joined #armbian
<[TheBug]>
quiet in here today
R0b0t1 has quit [Ping timeout: 260 seconds]
<IgorPec>
say something
<IgorPec>
:)
<IgorPec>
we are all in devel room
<TRS-80>
point release tomorrow
<IgorPec>
release notes are done
<TRS-80>
you saying I should update? :)
<IgorPec>
you will be forced or your hw will die off :)
<IgorPec>
you are welcome to add few lines of text if you wish
<TRS-80>
lots of stuff for a point release, wow
<TRS-80>
so soon after quarterly
<IgorPec>
well, some things were almost done, but not ready for a major release
<TRS-80>
This reminds me though, I think we shoulc change date format as it was initially confusing to me, I thought the second number was some other version for Ubuntu or something, I dunno. I think we should change date format to ISO like, which would be much less ambiguous, e.g., 2020-12-12.
<TRS-80>
What do you think?
<IgorPec>
we can follow two paths here, full date might be too overwhelming
<IgorPec>
we had a large disucssion a while back
<TRS-80>
I just mean periods are confusing, I did not even recognize that as a date at first.
<IgorPec>
its the same as on Ubuntu
<IgorPec>
patch versions are anyway hidden behind
<TRS-80>
I am not talking about our version numbering, which I realize is also somewhat date based (e.g., YY.MM.P where p is point release)
<IgorPec>
aha, date format
<IgorPec>
US folks
<TRS-80>
I am taking about the actual date, in your commit for example is 12.12.2020 should instead be 2020-12-12
<TRS-80>
no not that either, I am proposing ISO
<IgorPec>
ISO is fine for me
<TRS-80>
period are confusing I think, at first I did not realize that was even a date
<TRS-80>
esp next to version, which are period
<IgorPec>
you are welcome to correct thios
<TRS-80>
If you are OK with change, it's easy to write a macro and do. I just wanted to make sure first.
<IgorPec>
sed + awk |
<TRS-80>
I can also put them in headings as discussed previously, all at the same time.