ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | | Github: | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Type 'help' for help | Logs: ->
<stipa> let's just hope they'll lower the price in half after the first batch
<stipa> and that actually someoen will buy the first one
<stipa> at least they should make the one with allwinner works first
<stipa> and not like apple putting phones on the market like brad and butter
<stipa> bread*
<stipa> pricks
<c0rnelius> stipa: They give no shits. Honestly I wouldn't purchase anything from them.
<stipa> c0rnelius: i'll wait
<c0rnelius> Or you could just take that $399 and place it straight in the garbage. You'll probs get the same amount of satisfaction from the whole experience. :)
<stipa> i guess throwing money in garbage would be a less painful one
<c0rnelius> Strange they even went with the RK3399. Thing heats up like crazy?
<stipa> it's an optimized version
<stipa> for low power
<stipa> = less heat
<stipa> and it+s probably slower too
<stipa> less heat = less processing power
<c0rnelius> Well its says "1.5 GHz" which is over clocked last time I checked, unless they mean thats where both BIG and little are?
<c0rnelius> I guess that is what they did.
<c0rnelius> If I'm reading that right.
<stipa> i have no idea what they did to the old version of chip to make it more efficient but by some logic it should be slower too
<c0rnelius> I can't tell exactly from the article.
<stipa> maybe leaving everything as is but going smaller could achieve that
<c0rnelius> Thats easy enough to do, we could do that right now :)
<stipa> they could
<c0rnelius> stick the governor on schedutil so its mostly in chill mode.
<stipa> we can only guess
<stipa> and that's a waste of time
<stipa> let's just hope someone will buy it and tell us what's going on with the cpu
<stipa> soc *
<c0rnelius> I have no doubt someone will.
<stipa> right
<Armbian-Discord> <l​anefu> Congratulations on continuing to be maintainer.
<stipa> lanefu: you think that because of the soc change?
<stipa> like, completely new brand?
Redentor has joined #armbian
archetech has joined #armbian
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
Redentor has quit [Remote host closed the connection]
<Armbian-Discord> <k​prasadvnsi>
chewitt has joined #armbian
<Armbian-Discord> <k​prasadvnsi> What game should I try first? SuperTuxKart is available in Debian
<steev> neverball
<Armbian-Discord> <k​prasadvnsi> glmark2 score is 103. I don't know if this is a good score or the worst score
<chewitt> no more card alias maps required :)
<chewitt> we still didn't figure out the cause of the errant static noise in the AIU driver
Malditron has quit [Quit: Konversation terminated!]
ArmbianHelper has quit [*.net *.split]
jschwart has quit [*.net *.split]
binarym has quit [*.net *.split]
jschwart has joined #armbian
binarym has joined #armbian
ArmbianHelper has joined #armbian
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
<Armbian-Discord> <N​eonFetch> Its horrible
<Armbian-Discord> <N​eonFetch> Hahha
<Armbian-Discord> <N​eonFetch> But, doesnt matter..
<Armbian-Discord> <N​eonFetch> Maybe an x86_64 linux game with box64 😋
<Armbian-Discord> <N​eonFetch> To expose opengl 3.3 you need to use PAN_MESA_DEBUG=gl3
<Armbian-Discord> <k​prasadvnsi> GPU is running at lower frequency. I we retest once gpu-dvfs is ready.
archetech has quit [Quit: Konversation terminated!]
chewitt has quit [Quit: Zzz..]
<Armbian-Discord> <p​orkchop> I recently updated armbian on my odroid c2. I am having issues when I try to reboot. I noticed that there was a large upgrade recently (last week or so?). I rebooted and only noticed that the machine would not respond to a ping the next day. I did a reboot a few hours ago and this also failed.
<Armbian-Discord> <p​orkchop> unfortunately, it is headless right now and i didn't see the output. power cycling the machine fixed it again.
<Armbian-Discord> <p​orkchop> what is the best way I can troubleshoot this?
<IgorPec> did you search forums?
<HerculeP> its an old odroid issue depending on the kernel version, for me it helped to go back to an older kernel via armbian-config
steev has quit [Ping timeout: 245 seconds]
steev has joined #armbian
barnumbirr has quit [Ping timeout: 245 seconds]
barnumbirr has joined #armbian
<Armbian-Discord> <p​orkchop> IgorPec, HerculeP: yes, I did that since I posted the message. I tried to reinstall the bootloader from armbian-config but that didn't work. I saw the note about the kernel. The distribution that I installed about 2 weeks ago worked fine, i believe it was a 5.10.x kernel. Perhaps this new one has issues? I'll try an older one in a little while. Thank you both 🙂
<Armbian-Discord> <d​oodaadoo81> hello everybody.
qqqhhh has quit [Ping timeout: 252 seconds]
archetyp has joined #armbian
qqqhhh has joined #armbian
marco44 has quit [Ping timeout: 252 seconds]
marco44 has joined #armbian
stipa has quit [Ping timeout: 264 seconds]
<Armbian-Discord> <l​anefu> @stipa think what cuz of SoC change
Werner has quit [Quit: ZNC 1.7.2+deb3 -]
Werner has joined #armbian
Werner has joined #armbian
Werner has quit [Changing host]
<Armbian-Discord> <T​onymac32> Nice chewitt
Proxysna has quit [Remote host closed the connection]
Proxysna has joined #armbian
stipa has joined #armbian
marco44 has quit [Quit: ZNC 1.8.2+deb2+b1 -]
marco44 has joined #armbian
<Armbian-Discord> <p​orkchop> re: armbian update, c2 and reboot issue: i had a sandisk extreme but it was not an A1. Turns out i had one that matched the photo on the c2 page on the website, swapped it out and all is fine.
<Armbian-Discord> <T​onymac32> ??? Now that is interesting
<Armbian-Discord> <p​orkchop> there is one other thing i did. i usually update with sudo apt update && sudo apt dist-upgrade from the command line. i did this last night i think and there were over 100 sources that downloaded, and it did a u-boot upgrade. i ended up with 5.10.60 i think, and i was on maybe .57 before that? it's okay to upgrade from the commnand line right?
<Armbian-Discord> <p​orkchop> anyway i did the upgrade from armbian-config and it was also a long upgrade, but i didn't see the details. and things are working. I can say i've had issues with odroid boards and sd cards before, so nothing new. i should have known but this c2 has been in a drawer for a few years.
<Armbian-Discord> <k​prasadvnsi> Where should I add board specific kernel configs in the Armbian build?
<HerculeP> porkchop, I always do those apt ... on the CLI, armbian-config does the same internally I think (running just a script)
<IgorPec> board specific kernel config is needed??
<IgorPec> make a PR to sunxi64 and lets see what can be done. not sure if we want to maintain yet another kernel config
<steev> HerculeP: is it actually a kernel issue? if so, it still exists in 5.14 sadly. and it's not armbian specific as i use the mainline kernel on my c2
<HerculeP> steev: I currently dont use my c2, but on my hc2 (xu .img) the current kernel supports reboot very well (didnt work on an ancient version)
<Armbian-Discord> <k​prasadvnsi> It's OPi zero2 WiFi driver. It doesn't make sense to add it to the main sunxi64 configuration. It's just one board using this driver.
<HerculeP> steev: I powered up my c2: Linux c2eye 5.10.60-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:29:40 UTC 2021 aarch64 GNU/Linux <-- reboot works
<steev> HerculeP: ah, 5.14 reboot is working, but 5.10.(whatever debian has) did not
archetech has joined #armbian
<HerculeP> as I said: reboot DOES work here on odroidc2 armbian bullseye 5.10.60
<IgorPec> k​prasadvnsi: having extra kernel for zero2 is far more expensive to maintain then having a driver in
<IgorPec> we used to do this all the time, dragging all sorts of wifi drivers into one kernel
<IgorPec> steev: upstream support is more buggy even on very old devices such as c2
<c0rnelius> I really like 5.14.y :) Its had a few probs here and there, but spiffy for the most part on arm devices. The ones I have anyway.
<c0rnelius> I've actually had way more trouble with it on x86-64.
<HerculeP> IgorPec: c2 may be old, but still a useful device (it served me very well for a long time)
<Armbian-Discord> <I​gorPec> it is. just saying that support is kind of matured
<Armbian-Discord> <I​gorPec> but the kernel that comes with ubuntu or debian is not a match
<Armbian-Discord> <I​gorPec> armbian provides 5.14.y, not a problem 😉
<steev> IgorPec: si, sadly, one thing i really miss from downstream is the otg port, i really want to use my touch screen
<steev> debian has 5.14 as well now, the one hold out from letting it enter testing was the nvidia driver, which armbian doesn't have to deal with :)
<steev> i have an odroid c2 inside the vu7 (can't recall if it's just 7 or 7a), and can't use the touch screen portion :(
<Armbian-Discord> <I​gorPec> armbian 5.14 is not debian 5.14
<Armbian-Discord> <I​gorPec> where do you test nvidia on arm?
qqqhhh has quit [Ping timeout: 260 seconds]
<steev> i'm not, but a debian kernel can't enter the repos if there are any bugs, even if they don't affect a given architecture
Malditron has joined #armbian
oihan has joined #armbian
<Armbian-Discord> <I​gorPec> do you really believe this?
<Armbian-Discord> <R​ichNeese> breaks out the grill there is a porkchopin the channel ..
qqqhhh has joined #armbian
<steev> what do you mean do i really believe this? that's literally the reason why the debian 5.14 kernel wasn't. they were waiting on a fixed nvidia-driver-dkms package. it's not about belief
<steev> also, am i reading this patch correctly - that this enables the vu7+ with the 5.14 kernel?
<steev> ah, but that still likely only works when not plugged into the micro otg port, right?
<c0rnelius> contrary to popular belief, most of the patches you'll find in Armbian are commits over here ->
<c0rnelius> For Odroid anyway.
<c0rnelius> The end result I find is a cleaner kernel. But just my opinion.
<c0rnelius> I don't believe tobetter or anyone else over the takes into consideration mainline uboot though? so there is that.
<c0rnelius> But that is easily resolved with the nomap patch.
<steev> ah, but he doesn't rebase his stuff on top, so you have to dig through the commits to find them
<c0rnelius> yeah
<c0rnelius> only when he has too
<steev> that is unfortunate
<steev> i prefer to keep my stuff on top so it's easier for others to see what i'm changing
<c0rnelius> you'll see stuff from armstrong and whatnot there as well.
<IgorPec> no, i meant in general. not for this single nvidia driver
<steev> IgorPec: well, yes, because debian has to support multiple different architectures, not just X devices. so that is their process
<IgorPec> lol
<IgorPec> each arm family is like different family
<IgorPec> architecture
<c0rnelius> thats also true
<steev> i suppose so, but that's also why mainline is so "hard" - they want the stance that things must be able to co-mingle, not having 50 different branches for each release because of incompatible changes
<IgorPec> i know mainline is hard
<steev> hell downstream is hard too, especially tracking down all the various patches
<steev> especially when downstream kinda just do their own thing
<steev> just as an example, the pinebook pro has the tsys kernel stuff, manjaro patch on top of that, you guys have other patches, i have patches, no idea if ubuntu has patches but i assume they do too
<steev> c0rnelius might have patches for that as well, i didn't actually look in his builder :)
<steev> c0rnelius: fwiw, if you do, i use that same nanopc t4 patch with my pbp and haven't had any stability issues
<steev> for the 2ghz bump
oihan has quit [Remote host closed the connection]
<c0rnelius> steev: Well thats good news :)
<steev> it also makes the pbp feel a whole lot smoother
<IgorPec> pinebook pro is an old device, almost mainline due heavy pushing
<c0rnelius> Most of my patches for RK3399 came from Armbian. I believe I only tacked on a few from study and or looking through
<IgorPec> if we would stick to debian, we would remain in stone age ;)
<IgorPec> or ubuntu. or manjaro
<steev> that is because, sadly, debian's kernel team has the rule that things have to be in -next at least to be included
<c0rnelius> I think Ubuntu and Manjaro are usually ahead of Debian right?
<IgorPec> yes they are
<steev> manjaro definitely are, ubuntu are usually both behind and ahead because they typically do a ton of backporting to their hwe kernels
<IgorPec> manjaro just ships mainline
<steev> debian does too?
<IgorPec> in sid i think yes
<IgorPec> without any checking, just build and ship
<steev> in sid and bookworm
<steev> they definitely rely on others for the testing, yeah :/
<IgorPec> kernels are tested to some degree
<IgorPec> but when its down to diverse arm world
<IgorPec> things are totally different
<steev> i'm very aware as the only one who does all of the kali arm stuff
<IgorPec> what kali arm stuff?
<steev> all of it? i build the images, do the testing, the kernel work (or pulling patches from across the webs), decide what goes in, so on and so forth
<IgorPec> tesing on hardware is the question
<steev> every image we release, i test on the hardware
<IgorPec> which hardware??
<IgorPec> armbian currently covers 100 different arm hardware
<steev> congrats?
<steev> you also have more than just you
<IgorPec> no, i am curious what is tested
<IgorPec> we don't test everything, its impossible
<IgorPec> but when people start to mention "tested" and "stable" in this world ... i start to listen ;)
<steev> i do rpi0, 0w, 1, 2, 2 v1.2, 3, 3B+, 4, pinebook, pinebook pro, banana pi, banana pro, odroid-c2, odroid-xu3, nanopc t3, nanopc t4, neo plus2, gateworks ventana, gateworks newport, usb armory mk1, usbarmory mk2
<steev> i'm hoping to, at some point, bring back release images of some of the others that are now considered "build it from the script"
<steev> and next tuesday my radxa zero's should arrive so i'm hoping what i've built will work
<IgorPec> its already known what works and what not
<IgorPec> so you have fixed bananapi sata port ?
<IgorPec> i have notice people complain it stop working. since we didn't do anything i suspect its an upstream problem
<steev> that i don't test :/ i don't have the hardware
<steev> i'm too lazy to buy the adapter or make one
<steev> do they have any dmesg output?
<IgorPec> if you are in the testing mood, join our automated testing effort
<IgorPec> we do have a primitive system now, but lots of plans for improvement
<steev> is it lava based?
<IgorPec> nope. bash scripts goint to ansible
<steev> ah, i'm hoping to use lava to automate mine in the future. currently i do mostly bash scripts as well
<IgorPec> both way its a lot of work
<steev> actually, now i kinda wanna get the adapter for the sata
<steev> this is true
<steev> especially when it's just me :D
<IgorPec> that's also crazy ;) here we are more then I, but still totally underpowered for serious actions
<steev> i think, most open source is underpowered :D
<c0rnelius> Because its done by people whom fund their selves. Most of the boards I have I paid for. :)
<IgorPec> well, that's ofc also true. doing things together is the way to go. alone is really diffucult
<[TheBug]> [17:32] <IgorPec> so you have fixed bananapi sata port ? - which board?
<IgorPec> [thebug] no, i read on forums.
<[TheBug]> which board?>
<[TheBug]> the A20?
<IgorPec> yeah
<[TheBug]> I have one right here
<[TheBug]> which image are reporting issues
<[TheBug]> I can burn a sd card and test it as I have time
<IgorPec> you have ssd connected?
<[TheBug]> I can
<[TheBug]> I have A10s with old 2.5" drive on it also
<[TheBug]> lol
<IgorPec> i also have a10 somewhere ;)
<[TheBug]> I have original Cubieboard
<[TheBug]> ;)
<[TheBug]> with 4GB emmc
<IgorPec> yes, me12
<[TheBug]> hehe
<steev> ah, i have the cubieboard2, and my bananpi is an a20 variety
<[TheBug]> was first SBC I bought other than an RPi
<steev> i used to work for genesi, so i had a bunch of our competitors boards
<IgorPec> this was before rpi came out IIRC
<[TheBug]> but if y ou want to link me whatever image to test I will grab it on my image server burn it and pull out the board after bit
<steev> and, i typically buy all my boards too, though work yells at me to put in purchase orders
<[TheBug]> A10 was after original RPi, I had RPi first pretty sure then got the A10, even if A10 came out before RPi
<steev> if the board is the size of an rpi, it likely came after the rpi because all the vendors started chasing the rpi's market
<[TheBug]> yeah it is
<steev> now, thankfully, apple are putting out decent arm64 cpus so hopefully manfacturers will try to chase that market
<IgorPec> this came before
<IgorPec> yes, it was world before rpi ;)
* IgorPec is upgrading Ubuntu hirsute to impish on x86 ... lets see
<steev> at some point i need to pull the schematics out and get it into mainline
stipa has quit [Ping timeout: 258 seconds]
archetyp has quit [Quit: Leaving]
stipa has joined #armbian
stipa has quit [Quit: WeeChat 3.3-dev]
stipa has joined #armbian
<Armbian-Discord> <T​onymac32> Cubieboard? I had mini2440. :-)
<sunshavi> tablet topwise a721