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 | Development Talk: #armbian-devel | Type 'help' for help | Logs: -> irc.armbian.com
oida has quit [Remote host closed the connection]
oida has joined #armbian
redentor has joined #armbian
stipa has quit [Remote host closed the connection]
stipa has joined #armbian
reden-tor has joined #armbian
redentor has quit [Read error: Connection reset by peer]
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #armbian
DaRock has joined #armbian
xecuter has quit [Ping timeout: 264 seconds]
xecuter has joined #armbian
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 260 seconds]
ChriChri_ is now known as ChriChri
PPAChao has joined #armbian
PPA has quit [Ping timeout: 268 seconds]
DigitalMan1983 has joined #armbian
<DigitalMan1983>
can anyone confirm whether or not the Armbian build tools ever at any point in time rendered an image that functioned properly on Lime A64?
<DigitalMan1983>
more specifically USB functionality
<DigitalMan1983>
I'm beginning to suspect that the A64 is perhpaps the red-headed stepchild of Armbian-supported processors and am thinking of a platform switch
sunshavi has quit [Ping timeout: 240 seconds]
archetech has quit [Quit: Konversation terminated!]
<lanefu>
Don't know. I assume it did at one time. Maybe wrong device tree?
<lanefu>
What's find /boot/dtb return
sunshavi has joined #armbian
reden-tor has quit [Remote host closed the connection]
<DigitalMan1983>
returns /boot/dtb
<DigitalMan1983>
oh...tried it with a slash and got a list
archetech has joined #armbian
<DigitalMan1983>
namely the folder "allwinner"
<Tonymac32>
hi digitalman1983
<Tonymac32>
I would check in armbian-config to see if there are overlays to enable the USB ports. Usually not for the first one or two, but I am unfamiliar with that particular board, and which USB it actually makes available
<DigitalMan1983>
hi
<Tonymac32>
and I would guess I need to know what is improper about the function, there is none or it's buggy?
<DigitalMan1983>
none
<Tonymac32>
OK, so it has OTG on the micro-USB, USB on a 4-pin header and on that Type A connector
<DigitalMan1983>
yup
<Tonymac32>
is it dead on all of those?
<DigitalMan1983>
I haven't tried the OTG
<Tonymac32>
but you have tried the header and the type A
<DigitalMan1983>
not the header
<Tonymac32>
OK, so I saw this on my H3 board, USB-0 and 1 were enabled, but not 2
<Tonymac32>
so maybe that's the issue
<DigitalMan1983>
how did you enable it?
<Tonymac32>
sudo armbian-config
<DigitalMan1983>
unfortunately armbian-config doesn't have anything from what I can see
<Tonymac32>
then I'll need to actually do it while sitting here because I can't remember the steps
<Tonymac32>
ok, armbian-config --> system --> hardware should have a list of options
<Tonymac32>
for H3 it has usbhost 0 - 3
<DigitalMan1983>
huh....not there
<DigitalMan1983>
all my uarts and other serial data ports
<DigitalMan1983>
but no usbhost
<Tonymac32>
odd
<Tonymac32>
my only A64 is a pinetab and that is not currently in our build system
<DigitalMan1983>
this olinuxino is having all kinds of strange problems
<Tonymac32>
OK, yeah, it doesn't look like there are any USB overlays, which would tell me they should be enabled by default
<Tonymac32>
output of lsusb?
<DigitalMan1983>
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
<DigitalMan1983>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
<DigitalMan1983>
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
<DigitalMan1983>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
<DigitalMan1983>
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
<Tonymac32>
well that says it knows you have USB controllers
<DigitalMan1983>
usb lights on external USB device come on momentarily at bootup
<DigitalMan1983>
then the 5V goes dead on the port
<Tonymac32>
what is the device, a drive?
<DigitalMan1983>
in my case it's either a keyboard or a mouse or a hub
<Tonymac32>
ok, so nothing that should kill a thermal polyfuse
<Tonymac32>
no, the entry looks ok, so I'm not sure why it would be misbehaving. Maybe pop a question into the forums to see if anyone who has the board knows
<Tonymac32>
PAge 3 of the schematic, "Wifi&BT
<Tonymac32>
USB1-DRV is attached to PG9 as the DTS says
<Tonymac32>
but that is also UART1-CTS, which UART1 goes to the bluetooth
<c0rnelius>
I think the key was fdtdir, as with other boards I can just point at the dtb file.
indy has quit [Read error: No route to host]
indy has joined #armbian
oida has quit [Ping timeout: 240 seconds]
oida has joined #armbian
Hokedli has quit [Remote host closed the connection]
Hokedli has joined #armbian
oida has quit [Ping timeout: 240 seconds]
oida has joined #armbian
frog has joined #armbian
frog is now known as thebigfrog
thebigfrog is now known as frog
Hokedli has quit [Quit: Konversation terminated!]
frog has quit [Quit: Gateway shutdown]
frog has joined #armbian
frog is now known as thebigfrog
thebigfrog is now known as frog
<frog>
Hey all, I'm just looking through the build system trying to figure out if the odroid c2 has any binary blobs. Is the stuff in packages/blobs the only place they would be stored? Thanks
frog has quit [Quit: Gateway shutdown]
thebigfrog has joined #armbian
<thebigfrog>
Hey all, I'm just looking through the build system trying to figure out if the odroid c2 has any binary blobs. Is the stuff in packages/blobs the only place they would be stored? Thanks
pokui has joined #armbian
<chewitt>
I have no knowledge of where Armbian keeps stuff, but c2 has blobs for u-boot signing and if using the ARM mali GPU driver
<chewitt>
if using mesa/lima you avoid one of them
<chewitt>
the vdec also has blobs
<pokui>
hi all, armbian-config has the ability to start an iperf daemon. How is this implemented? I can't seem to find a startup script. (I'd like to set an option)
<thebigfrog>
chewitt: thanks, the u-boot blobs I saw in the armbian repo and vpu I assumed because libreelec is using a legacy kernel
<chewitt>
mainline vdec ultimately uses the same firmware(s) as vendor kernel, only they've been extracted into multiple files
<chewitt>
vendor kernel merges them all into a single file
<chewitt>
because. monolithic.
<chewitt>
LE uses mesa/lima for some time btw, it's working nicely
<chewitt>
in fact I think we were one of the first apps to ever run it :)
<chewitt>
app = Kodi
<chewitt>
(me wears two hats, one LE, one Kodi)
raver has quit [Quit: Gateway shutdown]
raver has joined #armbian
<thebigfrog>
Really? LE is using foss mesa/lime on the c2? But in a legacy kernel?
<chewitt>
nope
<chewitt>
I haven't booted an Amlogic bsp kernel since 2018
<chewitt>
and I haven't used mali utgard blobs since early 2019
<chewitt>
and I haven't used mali midgard blobs since late summer 2019
<thebigfrog>
so odroid c2 can run mainline kernel with the foss lima drivers for vpu acceleration?
<chewitt>
and bifrost blobs since .. a month or so ago
<chewitt>
yes, lima should be fine
<thebigfrog>
let me ask you this: which SBCs can run kodi (libreelec or otherwise) with only foss drivers for gpu and vpu and mainline kernel? basically a blob-free kodi experience on a SBC
<buZz>
lol
<buZz>
none, thebigfrog
DigitalMan1983 has quit [Ping timeout: 256 seconds]
<thebigfrog>
But what about the Cedrus project? I thought this was currently the best bet for foss vpu acceleration on arm SBCs
<thebigfrog>
That's what I thought. From my understanding lima is for the gpu, not for video decoding.
<buZz>
thebigfrog: that project is awesome if all you want is xvid
<thebigfrog>
what's xvid?
<buZz>
a sign that you're too young
<buZz>
actually from software support it seems the only 100% supported thing in cedrus is mjpeg? :D
<thebigfrog>
h264 is somewhat there, which would cover my needs
<buZz>
its not really :P try it out
<chewitt>
the Allwinner and RK stuff we support is stateless for vpu and both run lima/panfrost
<chewitt>
i'm afk-ish, on a work call
<thebigfrog>
buZz: so it's basically still a WIP is what you're saying?
<buZz>
thebigfrog: yes, its been WIP since launch, not even allwinner implemented it fully
<thebigfrog>
oh really? I never tried the proprietary CedarX stuff
<buZz>
if you want gpu decoding of video, just get a SBC with PCIe , stuff a nvidia on it
<buZz>
and pray nvidia finally releases the arm driver
<chewitt>
the kernel v4l2 stateless request api is now 'done' afaik, which means we can start upstreaming ffmpeg drmprime bits (which are refused until the api's are set)
DaRock has joined #armbian
<thebigfrog>
chewitt: ok, for which platforms is that? and what will it enable?
<chewitt>
Allwinner, Rockchip
<thebigfrog>
maybe I should really be asking this in the libreelec channel, but I saw the lime A20 appear in the testing build of libreelec, and wondered how the h264 support was doing and if its using a foss vpu driver?
<chewitt>
not all SoC are equal for codec(s) etc.
<chewitt>
and there are ongoing efforts to make 'Hantro' IP using devices share common code
<chewitt>
so the wheel is being slowly reinvented in places as that happens
<chewitt>
A20 support has been dropped
<chewitt>
in LE
pokui has quit [Remote host closed the connection]
<chewitt>
it's "different" to most of the other Allwinner SoCs, and doesn't inherit much code
<buZz>
chewitt: whats LE
<buZz>
lets encrypt?
<chewitt>
LibreELEC
<buZz>
oh that distro for kodi fans?
<chewitt>
correct
<buZz>
didnt know it still existed :P
<chewitt>
still going strong
<thebigfrog>
I saw that happened recently. Is it basically due to lack of manpower?
<buZz>
i've had 100% issues with it in the past
<buZz>
replacing it with plain debian solved 100% of the issues :P
<chewitt>
A20 users seem to turn up with particularly low spec boards, and the SoC reached the point where we realised it's quite different
<chewitt>
i.e. needs a large amount of work, needing a larger than normal amount of reverse engineering
<chewitt>
so the maintainer prefers to drop support and focus on other devices where progress is more worthwhile
<chewitt>
buZz whatever works for you (for Kodi) works for us
<chewitt>
Amlogic SoCs need the v4l2 statefull api to firm up, and lots more work to be done on the vdec and audio capabilities, they are a bit rough
<thebigfrog>
ok, interesting to hear the A20 is that different. Hopefully the work with H3,H5 and H6 goes well. Best of luck !
<chewitt>
sadly there's still too much interest in the vendor kernel, which is ugly crap code but more functional
<chewitt>
the rest have a lot in common
<chewitt>
it's already possible for LE to build an "ARM" image that boots any supported Allwinner, Rockchip, NXP, Amlogic device (one image, lots of u-boot blobs)
<chewitt>
for maintenance and support reasons we'll probably keep them separate
<chewitt>
but at some point we might combine them
<chewitt>
GBM/V4L2 things need to evolve a little further
<chewitt>
Raspberry Pi will likely drive some of it
<chewitt>
LE10 (next release) is still rather "work in progress" for RPi hardware, but we dropped OMX and MMAL .. will use GBM/V4L2 going forwards
<thebigfrog>
If I understood you correctly you said that the vendor blobs for C2 vpu accel work in a mainline kernel. The LE download page for the C2 says it's a 3.14 kernel. Is moving the C2 to mainline also one of the current goals?
<chewitt>
LE 9.0 was the last release we did for Amlogic which used 3.14
<chewitt>
LE 9.2 was skipped because we'd had enough for 3.14 and mainline wasn't really ready
<chewitt>
LE 10.0 is debatable because progress on vdec/audio has stalled badly for multiple reasons
<chewitt>
but I have what runs, running on 5.9.2
<chewitt>
there is currently an audio regression to track down, which is why LE master hasn't been updated in a while
DaRock has quit [Ping timeout: 240 seconds]
<chewitt>
and my work workload is high, and LE doesn't fun my vacations or porsche habit :)
<chewitt>
ss/fun/fund
<chewitt>
^ Apple keyboard is fcuked, lots of typos
<chewitt>
I suspect it will fault like crazy due to the audio issue, but.. I'll get to that eventually
drobo_00 has joined #armbian
drobo_01 has joined #armbian
drobo_00 has quit [Ping timeout: 260 seconds]
drobo_01 is now known as drobo_00
<Werner>
Good day
<lanefu>
howdy werner
redentor has quit [Remote host closed the connection]
redentor has joined #armbian
rneese has joined #armbian
rneese has left #armbian ["Leaving"]
oida has quit [Quit: byez]
<lanefu>
Werner: He brought up that readme change and i told him to open an issue :)
<Werner>
I know. And I reviewed it and came to the conclusion that it is not particular necessary ;)
<lanefu>
ha, well he had some good perspectives on the documentation as an outsider who isn't a newb
<lanefu>
just cuz its there, doens't mean its easy to find
<lanefu>
or understand
<Werner>
True
archetech_ has joined #armbian
archetech has quit [Ping timeout: 240 seconds]
Tonymac32 has quit [Quit: Leaving]
sassinak-work has quit [Ping timeout: 264 seconds]
sassinak-work has joined #armbian
archetech_ has quit [Quit: Leaving]
archetech has joined #armbian
Tonymac32 has joined #armbian
archetech has quit [Remote host closed the connection]
archetech has joined #armbian
archetech has quit [Read error: Connection reset by peer]
archetech has joined #armbian
archetech has quit [Quit: Leaving]
archetech has joined #armbian
initbasti[m] has joined #armbian
<initbasti[m]>
Hello, I recently tried out the dev branch with the 5.9.y kernel and it works fine. But for developing patches for the mainline I would like to use the very latest kernel. Now I don't have a good understanding of all the steps involved in packaging an armbian image. Is it possible to use the latest repository as the basis and keep the rest as it is?
<initbasti[m]>
Not entierly but if that means it is possible I will dive into it straight away
<initbasti[m]>
thank you
<archetech>
sure what board is it?
<initbasti[m]>
nano pc t4
redentor has quit [Quit: Leaving]
<archetech>
supported
<initbasti[m]>
Ah cool, can you explain what the difference is between supported or not supported? Like what causes a board not to be compatible with a non standard kernel repo?
<archetech>
too many problems, old
<archetech>
if ya want rcx kernels ya have to build that as a deb I think
<archetech>
rc2 is out today
<initbasti[m]>
Ok, I will try to find out from the documentation how to build a custom deb
<archetech>
builder wont build rc2 yet
<archetech>
just take the install ya got and build it on there
<archetech>
I have same issue on my n2 I need rc for it
<archetech>
plus patches
<initbasti[m]>
I am not entierly sure what you mean by taking the install and building it on there. You probably don't mean to build it directly on the nanopc-t4, so do you mean using the created data from the last builder image creation for a new image?
<archetech>
on the nano why not
<archetech>
no CC then
<initbasti[m]>
Oh I thought that I would need around 30GB to build the linux kernel and my nano has like 5GB
<initbasti[m]>
I mean I could add a SATA to it
<archetech>
well yes ya need some space not 30gb
<initbasti[m]>
if that is what you mean?
<archetech>
30 gb is for a whole image+kernel build
<archetech>
on the builder
<archetech>
and then its usu less
<initbasti[m]>
ok I will see if I can make that work
<initbasti[m]>
Thanks for showing me the opportunity
<archetech>
np use a fan too its rockchip
<archetech>
-j4 it will glow red
<initbasti[m]>
Ye I have one installed but maybe I need an external as well ;)
archetech has quit [Quit: Leaving]
archetech has joined #armbian
sunshavi has quit [Ping timeout: 240 seconds]
drobo_00 has quit [Ping timeout: 264 seconds]
rneese has joined #armbian
drobo_00 has joined #armbian
<rneese>
quiet day
<rneese>
sorry I have been resting today
<rneese>
I have to go over every desktop tomoroow
<rneese>
and work iin the builder
<lanefu>
rneese: mondays..... yeah dude i bet yoru beat still
<rneese>
yeah my knee is healing
<rneese>
so I slept alot today
BCMM has joined #armbian
<rneese>
so sorry just going to be a slow week but I am going to get them done
<rneese>
running a groovy build totest
<rneese>
but I know focal will be a base groovy is for testing and devel
bzyx has joined #armbian
gediz0x5391 has joined #armbian
gediz0x5391 has quit [Client Quit]
bzyx has quit [Client Quit]
bzyx has joined #armbian
bzyx has quit [Client Quit]
bzyx has joined #armbian
Elpaulo has quit [Read error: Connection reset by peer]
Elpaulo has joined #armbian
<Tonymac32>
woooo off day job
<Tonymac32>
now to cook dinner
<Tonymac32>
I slow cooked a pork shoulder last night, shredded it, today I fry it up for some tacos
<c0rnelius>
are the boot fips diff for the n2 and n2+?
<rneese>
no the n2 and n2+ are the same foor the most part
<rneese>
just faaster clock times
<c0rnelius>
I must be missing something in the mainline front then. Looking at chewitts uboot bin its 0.3 bigger than the one I generate.
Aurora_v_kosmose has joined #armbian
<Aurora_v_kosmose>
I have a system which on flashing the image shows the kernel splash screen, starts ethernet... and then kill both HDMI & ethernet and doesn't react any further.
<[TheBug]>
have you hooked up a UART TTL adapter and checked the console?
<Aurora_v_kosmose>
No output through usb-serial, unfortunately.
<[TheBug]>
huh?
sunshavi has joined #armbian
<[TheBug]>
That doesn't make much sense. First, what board and what image are you running?
<Aurora_v_kosmose>
It worked when I tried the debian installer (which failed ot install a working system due to not direclty supporting uboot)
<Aurora_v_kosmose>
imx6
<[TheBug]>
Secondly, pretty sure all Armbian images enable UART serial console by default
<[TheBug]>
which image
<[TheBug]>
what is the name of the image
<Aurora_v_kosmose>
20.08 Cubox-i buster current
<[TheBug]>
what is the actual name of the file you burnt to the sdcard?
<[TheBug]>
Have you tried older images and seen if that same issue persists in older versions?
<[TheBug]>
It is possible while it passed internal testing there is still issues with newest image and no one has tested yet...
<Aurora_v_kosmose>
I have no tried older images yet.
<[TheBug]>
If you can at least test previous image then we can at least isolate this to that image and investigate more
<[TheBug]>
They should be listed at bottom of device page
<Aurora_v_kosmose>
Is there a last "known working" version?
<[TheBug]>
lanefu: do all images have UART enabled by default, does that include imx6 boards?
<[TheBug]>
Aurora_v_kosmose: guessing not a lot of people using the device image if there is an issue and its only being reported now, so I would just go backwards chronologically