Werner 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/Twitter feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
rpardini has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Dagger has joined #armbian
s1b1 has joined #armbian
BCMM has quit [Ping timeout: 272 seconds]
wwilly has quit [Ping timeout: 268 seconds]
CrashTestDummy2 has quit [Quit: Leaving]
CrashTestDummy has joined #armbian
nimmen has joined #armbian
wwilly has joined #armbian
wwilly has quit [Ping timeout: 265 seconds]
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 252 seconds]
wwilly has joined #armbian
wwilly_ has joined #armbian
wwilly has quit [Ping timeout: 252 seconds]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
archetyp` has joined #armbian
archetyp has quit [Ping timeout: 252 seconds]
wwilly_ has quit [Quit: Leaving]
wwilly has joined #armbian
psydroid has quit [Quit: Bridge terminating on SIGTERM]
akanouras has quit [Quit: Bridge terminating on SIGTERM]
nekomancer[m] has quit [Quit: Bridge terminating on SIGTERM]
solderfumes has quit [Quit: Bridge terminating on SIGTERM]
MaxT[m] has quit [Quit: Bridge terminating on SIGTERM]
Findus has quit [Ping timeout: 252 seconds]
<archetyp`>
Rock Pi 4 B ordered, it should replace the Raspberry Pi 4 B as a desktop replacement.
<archetyp`>
Next month, a first-generation Asus Thinkerboard will be ordered for my second-generation RasPad.
<archetyp`>
Just want to say hello for a moment. :-)
<archetyp`>
Möchte nur kurz hallo sagen. ;-)
<Armbian-Discord>
<IgorPec> Hello!
archetyp has joined #armbian
archetyp` has quit [Ping timeout: 265 seconds]
<archetyp>
Oops, my Fritz!Box lost the connection, again.
<stipa>
i know it's not Armbians fault but i can't rely on building something reliable with that SBC stuff
<stipa>
and as i managed to notice it's all over the place, not just with my board that runs H6
<stipa>
too much bugs in silicon
<stipa>
that silicon manufacturers try to blame on kernel devs
<stipa>
and it goes round and round
<stipa>
there's not much that can be done if the chip is bogus on physical level
<stipa>
probably the peripherals are crap too
<stipa>
i've never saw a chip designer trying to help
<stipa>
i na year of beeing here
<stipa>
if you've screwed the chip at least you could fix your mess in software...
<Xogium>
well look at the pi 4, for a time they fscked up DMA at the hardware level which resulted in not being able to use more than 4 gb of ram
<Xogium>
they came up with a software fix, but *only* for their own kernel
<stipa>
yeah, software devs have no clue what's going on, it should be in datasheet or in clean open code
<stipa>
but it seems like the code is bogus too that manufacturers provide
<stipa>
so it must be that silicon is faulty
<Xogium>
hm
<Xogium>
on which board is that ? I didn't quite see
<stipa>
well, you know that the images that board producers give on their websites rarely work
<Xogium>
ah, yes. Definitely
<stipa>
and something like Armbian is soultion for that because they fix some things
<Xogium>
I never quite figured why they bother if it is to produce a broken image
<stipa>
Xogium: seems like it's the best they can offer
<stipa>
the most functional version of what they sell
<stipa>
board and crappy image that can't boot
<stipa>
everything after that is hacking
<Xogium>
yeah, but why bother
<stipa>
because there's soem info devs can use that can't be found in datasheets, it's in the code
<Xogium>
if all you can do is a broken image, better have no image
<stipa>
well, they have to offer something and dissapear
<stipa>
if there is image people think it works
<stipa>
if you tell them buy board without image, hmm, that won't really work
<Xogium>
that's crappy
<stipa>
very
<Xogium>
I toyed with the seeed stm32mp157c odyssey board, and I was actually pleasantly surprised to discover their debian image actually works very good, and doesn't appear broken
<stipa>
that's a great start for something like Armbian and such
<stipa>
that's just saying that manufacturing went well
<stipa>
and that there's not much scam involved
<Xogium>
there better not be, with the price of 50.54 euros
<Xogium>
;)
<stipa>
yeah, try to push it
<Xogium>
the only bad thing that happened so far with it was the proprietary boradcom wifi blob crashing the chip. But I replaced that with the linux-fimware package
<Xogium>
*broadcom
<Xogium>
only seems to happen on very large downloads
parabyte has joined #armbian
<parabyte>
so um what xorg driver do i use for s905x soc
<parabyte>
i want bare minimum to run kodi
<stipa>
i'm not sure but kodi is standalone os
<Xogium>
not always
<Xogium>
there's also a kodi app
<Armbian-Discord>
<Tonymac32> Kodi is not, a couple purpose-built distros that only run Kodi exist
<parabyte>
yeah i know about libreelec
<parabyte>
i wanted to learn something and run kodi on armbian
<Xogium>
well, I know we can run kodi on archlinux-arm
<parabyte>
i tried kodi-standalone
<parabyte>
can anyone here recommend documentation i need to read to understand?!
<Armbian-Discord>
<Tonymac32> Kodi runs on Armbian with JMCC's media scripts for Rockchip, I don't know about the Amlogic boards
<stipa>
probably github
<parabyte>
i assumed i was required to run a x session and run kodi on that?
<parabyte>
im sure ill figure it out
<parabyte>
otherwise im having a really good time. extracted dtb from original android firmware and applied to armbian, installed onto emmc with dd
<parabyte>
all was rather painless really
<stipa>
fancy man
<Armbian-Discord>
<Tonymac32> A TV box?
<Armbian-Discord>
<Tonymac32> Which kernel?
<parabyte>
Armbian-Discord, what kernel am i running now?
<parabyte>
or was i running?
<parabyte>
i never checked its original firmware
<Armbian-Discord>
<Tonymac32> No, which one with Armbian. The Android device trees are... Interesting
<parabyte>
apart from boot into android 6 briefly just to see what it was like out of curiosity
<Armbian-Discord>
<Tonymac32> 🙂
<parabyte>
hang on let me look to what i installed!
<parabyte>
i have a few different box's here, as a side business, i convert the occasional box into a multi purpose linux box and sell them on ebay
<parabyte>
only rarely
<parabyte>
tonymac32 Armbian 21.05.6 Buster Linux 5.10.43-meson64
<Armbian-Discord>
<Tonymac32> If I can ever escape Rockchip64 Hell, I am/was the primary Amlogic guy at Armbian, although Balbes now contributes directly and I think he is better. ;-)
<parabyte>
haha in a few words what would you do to get kodi working on that box? i know i need to read the documentation on this kodi subject abit more
<Armbian-Discord>
<Tonymac32> I would make sure the device tree is actually working, Android has their own bindings for almost anything graphics related
<parabyte>
im assuming libreelec guys/girls do it with xorg
<parabyte>
oh crap i see what your saying now
<parabyte>
yeah i did get a few warnings come to think about it when i converted to dtb file to dts
<Armbian-Discord>
<Tonymac32> So compare it to the Le Potato device tree as a starting point, that is an S905X board we support
<parabyte>
well the file iv used it kinda working cause ethernet is up and running
<parabyte>
but i see your point now
<Armbian-Discord>
<Tonymac32> Most of the generic devices will work, but the graphics stack is special. USB is hit or miss too, even kernel to kernel on linux
<Armbian-Discord>
<Tonymac32> Vim1, one of the wetek boxes as well can be good reference points
<Armbian-Discord>
<Tonymac32> If you go to the forums and search in the Amlogic subforum you might find something recent, otherwise a new topic asking about Kodi specifically on that SoC should get some replies
<Armbian-Discord>
<Tonymac32> Media is not my specialty unfortunately
<parabyte>
usb is working fine
<parabyte>
i will take a good hard look at it later, compare it again what armbian dev's have done
<stipa>
i've noticed that linux doesn't like usb hubs
<parabyte>
haha sure enough tonymac32 the errors in dmesg are concerning the lima soc graphics driver yes thanks for giving me the correct nudge on what i need to look at tonymac32
<parabyte>
stipa, i do not have issues with any usb hubs
<parabyte>
iv used all sorts of random usb hubs on linux desktops
<parabyte>
across many different platforms
<stipa>
i'm unlucky gal
<stipa>
idea of splitting traffic of one USB3 port with USB3 hub isn't something i have had luck with
<stipa>
it looks fine but when pushed it dies
<stipa>
i'm curious how usb C hubs work
<stipa>
ha ha
<parabyte>
ah usb3 hubs do not convert to usb2
<parabyte>
most dont anyway from my understanding
<parabyte>
they have like 2 hubs in 1
<parabyte>
1 hub for usb2 traffic and another hub for 3
<parabyte>
on the elcheapo ones anyway
<stipa>
i have an external one
<parabyte>
both hubs in the same IC
<stipa>
not like a chip that is connected to pci lane
<parabyte>
yeah im on about the hub controller inside the external usb hub
<parabyte>
um maybe its a power issue stipa
<parabyte>
maybe you are exceeding your boards power output
<stipa>
damn you, maybe it is
<stipa>
i'll connect nuclear power plant just to be sure
<parabyte>
i have like 7 dvb receivers plugged into 1 hub
<parabyte>
but i have cut the power lines and i use a big honking 20amp 5v psu
<parabyte>
bit overkill but its what i had on hand
<parabyte>
i do not use any of the systems 5v rails for powering my receivers
<stipa>
you mean of the power that powers the sbc?
<stipa>
you're powering just receivers with that additional PSU?
<stipa>
parabyte: what chip is in your external usb hub?
<parabyte>
stipa, um
<parabyte>
i dont know
<parabyte>
its just a usb2 hub i got out of my local super market
<parabyte>
while doing food shopping!
<stipa>
parabyte: lsusb|grep Hub
<parabyte>
haha id love to stipa but i am not at home hence why i dont know
<stipa>
ha
<stipa>
if i plug usb3 hub into usb2 port many crap goes away
<parabyte>
tonymac32, before we part ways, i just wish to thank you for pointing out to me the mistake i have made
<Armbian-Discord>
<Tonymac32> Haha you're welcome. I wouldn't call it a mistake, it is certainly a good starting point
<parabyte>
tonymac32, the android dts derived file is a mess. its not as clean and tidy like the supplied ones with armbian. and as you mentioned all the names are different!
<Xogium>
it could be also because you converted it from the dtb file
<Xogium>
in my experience dtc converts them quite badly
<Xogium>
at least, part of the mess could be due to that
CrashTestDummy2 has joined #armbian
syntaxman has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 272 seconds]
<syntaxman>
I'm just now looking at getting a NAS/Server that I would like to run at work. I'd like to run a SAMBA/PDC and a http/DB/Python stack on it too. It's a small office, low-load. Is a Helios64 up to that? Anyone have any other suggestions?
<Werner>
Should do it
<syntaxman>
Excellent. Thank you, Werner
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 240 seconds]
CrashTestDummy2 has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 256 seconds]
<[TheBug]>
RockPi 4c with Penta Hat
<IgorPec>
or nanopim4 with sata hat
stipa has quit [Read error: Connection reset by peer]
<Armbian-Discord>
<Tonymac32> Functionally equivalent, but you don't get a case
<Armbian-Discord>
<Tonymac32> And power delivery is... Well up to you
<IgorPec>
true
<Armbian-Discord>
<rneese> grumble
kilobyte_ch has quit [Ping timeout: 268 seconds]
psydroid has joined #armbian
akanouras has joined #armbian
nekomancer[m] has joined #armbian
attah has quit [Ping timeout: 268 seconds]
attah_ has joined #armbian
MaxT[m] has joined #armbian
solderfumes has joined #armbian
attah_ is now known as attah
kilobyte_ch has joined #armbian
psydroid has quit [Quit: node-irc says goodbye]
akanouras has quit [Quit: node-irc says goodbye]
nekomancer[m] has quit [Quit: node-irc says goodbye]
MaxT[m] has quit [Quit: node-irc says goodbye]
solderfumes has quit [Quit: node-irc says goodbye]