Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Forums Feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
<ArmbianTwitter>
@SOLUFLEXSRL (SOLUFLEX S.R.L.): Meet Karmbian, an ARM Linux Distro for Ethical Hackers Based on Kali Linux and Armbian https://t.co/iXUPnVocSx (11s ago)
<lanefu>
and he's got that polish speed i've heard so much about
<Werner>
Nice
sassinak-work has quit [Ping timeout: 244 seconds]
sassinak-work has joined #armbian
archetech has quit [Read error: No route to host]
sassinak-work has quit [Ping timeout: 244 seconds]
sassinak-work has joined #armbian
townkat has quit [Remote host closed the connection]
bigbrovar has quit [Ping timeout: 260 seconds]
bigbrovar has joined #armbian
livingsilver94 has quit [Ping timeout: 265 seconds]
livingsilver94 has joined #armbian
<ArmbianTwitter>
@fosshost1 (fosshost): We have been fighting fires for days with our Poland mirror and have taken the decision to remove it from service with immediate effect. We will now focus and concentrate on US / UK mirrors. Full announcement https://t.co/iSfRJ3F70G #mirrors #xiph #manjaro #ubuntudde #armbian (9s ago)
<eth01>
lanefu: the pl server was rigged with various issues and we are not happy with the performance of it - for now we will focus only on UK & US
<eth01>
Sorry
<Werner>
Most important for us was having a proper US mirror so no worries :)
<eth01>
The UK / US are working as we expect and we are future proofed. PL had limitations and Iām not prepared to run with PL to then only let you and other projects down in the future so best to be honest and upfront. Was up till very late discussing with our volunteers best way forward.
<ArmbianTwitter>
@Superna9999 (Neil Armstrong): @lanefu @armbian @thepine64 @LibreELEC Indeed 1440p is not handled, I have to look at this, I had multiple people asking for this mode ! (31s ago)
archetech has joined #armbian
<ArmbianTwitter>
@Cultcoders (Thomas Soldan): Meet Karmbian, an ARM Linux Distro for Ethical Hackers Based on Kali Linux and Armbian https://t.co/lkp93dZmRB #ARM #KaliLinux #Linux via @mariusnestor (31s ago)
RzR has joined #armbian
RzR has quit [Changing host]
<ArmbianTwitter>
@Superna9999 (Neil Armstrong): @lanefu @armbian @thepine64 @LibreELEC Should be doable, amlogic seems to support it https://t.co/S4zAgE2xKb (7s ago)
<eth01>
Nice documentation well done whoever wrote it š
<Werner>
It needs some tuning like exclude pages that are actually not in use
<Werner>
Its more a proof of concept now
livingsilver94_ has joined #armbian
livingsilver94 has quit [Ping timeout: 240 seconds]
<ArmbianTwitter>
@BrideOfLinux (Christine Hall): "Launched just a few days ago, Karmbian is a Kali Linux based distribution optimized for devices like the Raspberry Pi, ROCK64 and ARM laptops": Meet Karmbian, an ARM Linux Distro for Ethical Hackers Based on Kali Linux and Armbian - @9to5linux https://t.co/qUlSyFSkpk (26s ago)
<lanefu>
Well i hope karmbian brings more attention to armbian
<Werner>
My best guess is that the attention it will receive are bugs ^^
<lanefu>
Yeah i was wondering if we should make a karmbian subforum as a honeypot
<Werner>
Haha
<Werner>
Kind a like tvboxes
<lanefu>
Yup
<lanefu>
I need to quote that dudes tweet where he explains that he plans to make the fork super different
<lanefu>
Maybe we need to address tvboxes support and karmbian in docs
<lanefu>
Since they're derivatives
<Werner>
We could mention but I don't see a strong reason for it besides advertisement for Armbian to be base of something else.
thefinn93 has quit [Remote host closed the connection]
<lanefu>
Werner: yeah maybe we just mention "derivatives" w/o specifics
<lanefu>
IgorPec: eth01 I'm gonna start sending apt traffic to the fosshost US mirror
<lanefu>
DL isn't ready yet
xwigg has joined #armbian
<lanefu>
looks like i'll be adding UK mirror for apt and DL now!
<Werner>
\o/
* lanefu
grateful of the bandwidth of others
<eth01>
No worries guys
<xwigg>
nice...
<lanefu>
man i totally forgot what i'm supposed to do today, but i nkow its a lot lol
<ArmbianTwitter>
@FOSSForce (FOSS Force): Meet Karmbian, an ARM Linux Distro for Ethical Hackers Based on Kali Linux and Armbian - 9to5Linux https://t.co/xPEBVALdNi (24s ago)
<xwigg>
just built trunk for OpiPC+, works alright, except htop shows 0Mhz
<xwigg>
mm cpufreq userspace seems to have changed
<Werner>
armbianmonitor -m shows freq?
praselv has joined #armbian
prasel89 has quit [Ping timeout: 246 seconds]
<xwigg>
nope. n/a
<xwigg>
no or unknown cpufreq driver is active on this CPU
<IgorPec>
which image?
<xwigg>
compiled trunk for testing, based on debian buster image july
<Werner>
PC+ is H3?
<IgorPec>
probably dvfs bits are missing for this board
<xwigg>
pc+ is H3
<IgorPec>
because in general works
<Werner>
Just tested with an OPi One. 5.7.11, all good there
<IgorPec>
yeah, i test many h3 boards but no pc+
<xwigg>
something spiffy at my end it is
<lanefu>
womp womp.. my h64 crashed :P
<lanefu>
i need to rig up full console capture logs on all these things
<lanefu>
IgorPec: BTW I'm gonna be juggling a few things for a while, so easiest way for me to help keep things moving along is for you to just assign me work in Jira :)
<lanefu>
so feel free to do so
<IgorPec>
ok
<IgorPec>
btw. espressobin seems to be fu* up
<IgorPec>
mine doesn't boot ... huhh
<xwigg>
k switch to nightly OPiPC+ seems 100% at least 99%
<lanefu>
IgorPec: really? damn mine hda been going strong from that build a few weeks ago
<IgorPec>
with 5.6?
<lanefu>
IgorPec: maybe reset your u-boot stuff
<lanefu>
yeah with 5.6
<lanefu>
worked on v4 and v5
<IgorPec>
ok, will check closly
<IgorPec>
i only have two the same version
<IgorPec>
v5
<IgorPec>
lanefu: pineh6 you run desktop / panfrost?
<lanefu>
IgorPec: deb buster desktop with slightly custom X config http://ix.io/2sYc
<IgorPec>
i disabled acceleration until things gets stable
<IgorPec>
is your config helps?
praselv has quit [Read error: Connection reset by peer]
<lanefu>
honestly not sure... but i do think we may want to default to having this Driver "modesetting"
<lanefu>
so that it uses that over fb driver
<lanefu>
i got those X settings from archetech
<IgorPec>
btw. ebin is ok, i did something wrong
<lanefu>
:) yay
<lanefu>
anybody here good with google forms?
<Werner>
Depends...
<lanefu>
Werner: for our RC testing.. I'd like to have a google form somewaht similar to what we did with Driver "modesetting"
<Werner>
Sure it would be possible to create a form that fills the table accordingly but I think noone will use it since it is a lot of work to put all the values in their fields
<IgorPec>
we have 25 board in the test rig, ready to report :)
<lanefu>
but just quick adn easy for someone to say which RC image for "supported" device they used.. whether it was fine. and whether or not they had problems.. like "crash, network, desktop, other" and just an open filed and a place for this armbianmontir -u ink
<lanefu>
link
<lanefu>
IgorPec: yeah that's awesome.. we still need user testing :)
<lanefu>
but yeah we can catch a LOT of stuff early with tha tsweet test rig
<Werner>
Hm let me do some testing with the forms
<lanefu>
Werner: yeah i generated that form last time.. and people did report
<Werner>
The response data can be automatically exported to a sheet in realtime
<lanefu>
yeah that's what i was hoping
<lanefu>
ArmbianHelper can tell us when shit fails :P
<lanefu>
maybe an optional picture or screenshot attachment too?
<lanefu>
but yeah all for simplicity
<Werner>
You cannot upload stuff to a google form
<lanefu>
oh
<lanefu>
well no worries
prasel has quit [Ping timeout: 265 seconds]
<Werner>
But we can say "if yo have a foto or soemthing put it to xyfotohost.com and share the link here"
_prasel has quit [Remote host closed the connection]
<Werner>
What new boards are getting support with 20.08?
<Werner>
Neo3 I know
<Werner>
Okay, got it a bit enhanced
<lanefu>
Even a sweet experience on mobile
<lanefu>
We could even put a link to sheet in the motd
<lanefu>
Thanks Werner!
<Werner>
lanefu, did you just edit board nr. 17? "is"? :P
<Werner>
Basically I copied the column of your sheet and sorted it alphabetical
<lanefu>
Werner: sorry i think i fat fingered something when i looked at link from phone
<Werner>
xD
<Werner>
Found it. Was espessobin
<xwigg>
are there really that many boot issues? (apart from the focal incident)
<lanefu>
That sheet i think also had csc boards so may need to filter list?
<Werner>
RC images will be generated for CSC too I guess? We can take the data but do not have to use it
<xwigg>
the only culprit I can imagine is people who installed to EMMC/NAND with ext2/ext3 where kernelsupport is not enabled by default (missing ext2/ext3)
<Werner>
Or put their status behind their names? To say "Orange Pi 3 (CSC)" for example
<Werner>
xwigg, all kernels should have ext2 and 3 support I suppose?
<lanefu>
I think we should only collect on supported and only publish RCs of supported
<lanefu>
To drive home the difference
<Werner>
Hm yeah, then I need a list of all officially supported boards
<xwigg>
Werner: ext2/ext3 disabled in current OPI kernel config by default
<Werner>
lol?
<Werner>
fact...lol
<Werner>
Why?
<lanefu>
Yah we do need to standardize on our base kernel settings
<Werner>
There is already some work done in this direction. Much stuff got pulled from upstream default
<Werner>
Btw. lanefu do we need something else from the form besides the sheet backend?
<lanefu>
Reading the report in sheets should be sufficient. If you wanted to go over the top armbianhelper could tell us when a supported board is reported with a did not boot so that we can feel frustrated and beat down
<Werner>
Nah I probably wont. Too much effort for very little fancy messages
<lanefu>
Ha
<lanefu>
Seriously thanks for rigging up that form gonna be helpful
<Werner>
No big deal
<lanefu>
I had some unrelated ideas to consider after the release
<lanefu>
We've tried recruiting for board maintainers in the past
<Werner>
Worked partially as I saw
<lanefu>
Yah. I have another half for it
<lanefu>
Originally we said a maintainer could just be a glorified tester but that didnt seem to connect with the people
<lanefu>
So i was thinking about a new campaign / initiative for official community testers.... and you can only be a tester for a single SBC.... even if its stupid similar. Example opi lite, vs opi one
<lanefu>
That way maybe we can get some deep testing on devices
<lanefu>
And eventually work with them to persue performance tuning
<Werner>
The weird thing about that is that most people that like to contribute most likely have multiple SBCs laying around on their shelves.
<lanefu>
Yeah.... i know causes them not to test deeply
<Werner>
As for myself I did not think about having half a dozen of them here all blinking when buying the OPi Zero a few years ago ^^
<lanefu>
Preachin to the choir
<lanefu>
Bought an opione because of same day delivery on a Sunday
<Werner>
LOL
<lanefu>
Now i have... a lot
<Werner>
If I include the ones given away as well as are still in the mail it should be around 10 for me.
<lanefu>
Oh you're doing well
<lanefu>
I have 8 running in my rack
<lanefu>
Doesnt include the ones running at desk or the one in the bedroom or the unplugged ones lol
<Werner>
Nice
<lanefu>
Okay im gonna go count for grins
<lanefu>
okay 15 currently on line
<lanefu>
plus
dddddd has quit [Ping timeout: 260 seconds]
<Werner>
I am still thinking about a replacement for the space heater aka PC. But it is a bummer that the M4V2 is only halfway good desktop supported by old 4.4 kernel :/
<Werner>
And the next issue is that I think there is no SBC out there that supports 8k output ^^
<lanefu>
plus 18-ish unplugged.. excluding RPI and Atomic Pi
<lanefu>
you have 4k display?
<Miouyouyou>
No, 8k display
<Miouyouyou>
He's going for the 12K challenge the next month
<Werner>
dell u4919dw. Needs 8k because it has 5120px in the width
<Miouyouyou>
12K 240HZ on a SBC !
<lanefu>
well given my current 4k rage... still with x86 or downground your monitor :P
<lanefu>
*downgrade
<Miouyouyou>
*burry
<lanefu>
and technically it 2k rage i have
<Miouyouyou>
Well, the Tinkerboard can up to 4K YUV 4:2:0 at 30Hz
<Miouyouyou>
So... maybe ?
<Miouyouyou>
What's the resolution of 8K exactly
<lanefu>
yeah most of them can do 4k30
<Miouyouyou>
7680āĆā4320 ?
<lanefu>
btw Werner what do you do with opi zero
<Werner>
Atm still debugging the broken OPi One
<lanefu>
I GUESS I SHOULD USE IT FOR KARMNBIAN
<lanefu>
Werner: yeah my new favorite UART is an opi lite
dddddd has joined #armbian
<lanefu>
i can just ssh in
<Miouyouyou>
So, 7680āĆā4320 x 2 bytes per pixel (compressed YUV) x 60 Hz -> 3 981 312 000 bytes of bandwidth
<Miouyouyou>
What's the best bandwidth with QSPI ?
Nakaori has joined #armbian
<Werner>
Where did we start with this?...Ah yeah, the maintainer idea
<lanefu>
:P
<Miouyouyou>
Got traumatized by Karmbian ?
livingsilver94 has joined #armbian
<lanefu>
yeah i got some karmbian ptsd
livingsilver94_ has quit [Ping timeout: 264 seconds]
<Miouyouyou>
What did Karl do to you ?
Coraxyn has joined #armbian
<Coraxyn>
Morning
<Werner>
Evening :P
<Coraxyn>
...
<ArmbianHelper>
. [en~>eng]
<Coraxyn>
:)
<Coraxyn>
Trying to reset LoRa phat via gpio
Nakaori has quit [Remote host closed the connection]
<Miouyouyou>
They want you to use some utilities now
<Coraxyn>
Went through steps and everything seems to work at linux level, but not getting reset message via UART
<Miouyouyou>
Do you have a way to measure the signal (Oscillo, ...) ?
<Coraxyn>
No
<Coraxyn>
Will tomorrow though
<Coraxyn>
Using gpio17 for pin 11
<Coraxyn>
Is this correct
<Miouyouyou>
Anyway to connect a LED, just to check that the GPIO programming is actually working ? The driver might just send bogus values.
<Coraxyn>
Have phat working. It sends and receiveed data from sensor packs just fine
<Coraxyn>
It is only hardware reset function that is not working
<Miouyouyou>
So, it's just the reset not working ?
<Coraxyn>
Correct
<Miouyouyou>
Tried every combination I guess ? The reset on some chips tend to be inverted.
<Coraxyn>
Mm
<Coraxyn>
Setting 0 for 10ms then back to 1
<Miouyouyou>
And no change
<Coraxyn>
nuffin
<Coraxyn>
First, is pin 11 gpio17?
<Miouyouyou>
What's your board to begin with ? :3
<Coraxyn>
Also, have gpio settings on armbian-config
<Coraxyn>
+no
<Miouyouyou>
They all have their "naming schemes"
<Coraxyn>
They were previously both on
<Coraxyn>
Niticed :)
<Miouyouyou>
Sometimes the kernel driver has other naming schemes. So maybe a led check on the reset pin might do the trick. See if the signal is really sent.
<Miouyouyou>
You're trying this on a RaspPi ? OrangePi ? Some Rockchip board ?
<Miouyouyou>
Else, you might have to wait for OPI specialist here, there's a few of them lying around there
<Coraxyn>
K, thanks
<Miouyouyou>
You just have to wait for them to wake up, or throw some fresh water on them
<Coraxyn>
May have found issue
<Miouyouyou>
Nice
Nakaori has joined #armbian
<Coraxyn>
Nope :|
<Miouyouyou>
:C
torv has quit [Remote host closed the connection]
torv has joined #armbian
<Coraxyn>
Had UART2 enabled. Turned it off, no change
<Coraxyn>
Reading last link you sent
<Miouyouyou>
I guess that the GPIO are soldered ? No way you can try to unplug and replug the reset GPIO to the board, see if that works ?
<Miouyouyou>
Ok, so the current way of dealing with gpio on linux is gpiod with commands like gpioget gpioset. But if everything works through sysfs, I don't know why that single pin would not work.
<Coraxyn>
Ok
<xwigg>
gpio layout is the same as RPI3
<Coraxyn>
Yes
<xwigg>
yaj 3231 works! Last login: Sat Jan 1 01:26:03 2000
<lanefu>
xwigg: sweet your RTC clock?
<xwigg>
yup .. without overlay though will need to fix that some future.
<lanefu>
which board?
<xwigg>
opipc+ so there's samples, but it didn't work before my patience ran out