ArmbianHelper 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 | Logs: -> irc.armbian.com
samythemany1 has joined #armbian
samythemany1 has quit [Ping timeout: 258 seconds]
samythemany1 has joined #armbian
norwich_ has joined #armbian
norwich has quit [Ping timeout: 268 seconds]
norwich_ is now known as norwich
Tenkawa has quit [Quit: Be back another time.]
xoan7 has joined #armbian
xoan has quit [Ping timeout: 244 seconds]
xoan7 is now known as xoan
xoan5 has joined #armbian
xoan has quit [Ping timeout: 252 seconds]
xoan5 is now known as xoan
samythemany11 has joined #armbian
samythemany1 has quit [Ping timeout: 258 seconds]
archetech has quit [Quit: Leaving]
xoan has quit [Read error: Connection reset by peer]
xoan has joined #armbian
samythemany11 has quit [Ping timeout: 258 seconds]
samythemany11 has joined #armbian
Smedles_ is now known as Smedles
samythemany11 has quit [Remote host closed the connection]
samythemany11 has joined #armbian
The_Loko has joined #armbian
xoan3 has joined #armbian
xoan has quit [Ping timeout: 244 seconds]
xoan3 is now known as xoan
lemonzest has joined #armbian
oida has quit [Ping timeout: 255 seconds]
ajfriesen6 is now known as ajfriesen
oida has joined #armbian
oida has quit [Ping timeout: 268 seconds]
samythemany111 has joined #armbian
samythemany1111 has joined #armbian
samythemany11 has quit [Ping timeout: 258 seconds]
samythemany111 has quit [Ping timeout: 258 seconds]
lanefu has quit [Ping timeout: 255 seconds]
lanefu has joined #armbian
califax has quit [Remote host closed the connection]
califax has joined #armbian
xoan8 has joined #armbian
xoan has quit [Ping timeout: 244 seconds]
xoan8 is now known as xoan
aasami_ has joined #armbian
wifasoi[m] has joined #armbian
<wifasoi[m]>
Hi, I'm trying to create an image for the SOQuartz board (based on rk35xx chipset). I'm using armbian-next, but i had some difficulties generating the rootfs (here a pastebi: https://pastebin.com/4AzKLwQY line 117)
<ArmbianHelper>
^ [🌱] Using config file [ /home/wifasoi/Projects/linux/armbian/userpatches/config- - Pastebin.com
<wifasoi[m]>
I read the code line suggested in the error, but I don't know if a problem with a combination of parameter, or a transient problem with the rootfs cache
<Armbian-Discord>
<bret> I'm going to try and see if I can get an image working for the MangoPi MQ Quad when it turns up, it's a H616 chip and they claim to have a working bodge of the Orange Pi Zero 2 images but they make me sad
<Armbian-Discord>
<bret> As good a time as any to get properly familiar with the build process and figure out what I need to do. Am big noob, pls no hate 😄
<Armbian-Discord>
<IgorPec> wifasoi[m]: use upstream build system, next is alfa / beta state
<wifasoi[m]>
well, I don't need the image badly.. this is why I wanted to use the new shiny things
<wifasoi[m]>
but i'll retry with upstream and compare
<wifasoi[m]>
in the mantime, Do i need to use the cached rootfs from the armbian project, or there is a config that make it possible to build it locally?
crabbedhaloablut has quit [Remote host closed the connection]
samythemany1111 has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
samythemany1111 has joined #armbian
samythemany11111 has joined #armbian
<Armbian-Discord>
<IgorPec> no, you don't need to use cached rootfs ... there is one switch which will always make it from packages
<Armbian-Discord>
<IgorPec> also if cache is not found upstream, it also go and make from packages
samythemany1111 has quit [Ping timeout: 258 seconds]
qqqhhh8617 has joined #armbian
qqqhhh861 has quit [Ping timeout: 260 seconds]
qqqhhh8617 is now known as qqqhhh861
samythemany11111 has quit [Ping timeout: 258 seconds]
<wifasoi[m]>
ok, i have almost the same problem with upstream armbian. It give a "chroot: failed to run command ‘/bin/bash’: No such file or directory" (i cleared the cache folder and output) and it download the cache rootfs. I think the chroot error is caused by a corrupted cache rootfs (but I'm not sure, so plz correct me). So I'll try to create it locally
<wifasoi[m]>
the flag is ROOT_FS_CREATE_ONLY I think
<wifasoi[m]>
don't know if there is some other flag combination to force the rootfs build locally
<wifasoi[m]>
ok.. tryed to set teh ROOT_FS.. flag and the unset it... still chroot error that it doesn't find /bin/bash
<wifasoi[m]>
someone can give me an hint of what it can be?
<ArmbianHelper>
^ cp error building for rockchip · Issue #4146 · armbian/build · GitHub
<Armbian-Discord>
<ManoftheSea> tales of my competence appear to be exaggerated. But I can look.
<Armbian-Discord>
<ManoftheSea> Yeah, okay, that's a harmless error
<nekomancer[m]>
thank you, manofthesea! :)
<Armbian-Discord>
<ManoftheSea> The script used to build by the one name, it is more correct to build them by the other name, but as you thought, the lack of a bin causes the lack of an operand on that line.
<nekomancer[m]>
shoul be an error (and building stop) if both copy fails?
<wifasoi[m]>
ok, switchd to the latest tagged release.. cleared the chache... ans still chroot error: https://pastebin.com/9DEn9WSN
<Armbian-Discord>
<IgorPec> like menu driven without changes?
<Armbian-Discord>
<IgorPec> give me commands so we can try to reproduce
kolla has joined #armbian
<wifasoi[m]>
no, i changed quite a bit. Custom Uboot and kustom kernel (6.0-rc3)... and a new board
<Armbian-Discord>
<IgorPec> ahaaa
<wifasoi[m]>
i can give you a well formatted patch
<Armbian-Discord>
<IgorPec> that i can't do right now
<wifasoi[m]>
(sorry if i did not say it sooner)
<Armbian-Discord>
<IgorPec> this can take hours to find a problem
<wifasoi[m]>
no, don't want waste time tryong to make reproduce my monster to someone else.. just fishing what can be the cause of the problem
<wifasoi[m]>
idf someone encoutered something similar
<Armbian-Discord>
<IgorPec> well, ruling out clean build system is 1st step
<Armbian-Discord>
<IgorPec> we could have troubles, but chances are ofc slim
<wifasoi[m]>
ok.. i'll try fro clean.. anch change one thing at the time
<nekomancer[m]>
wifasoi: try to remove rootfs cache. possible broken rootfs image in cache
<Armbian-Discord>
<IgorPec> and remove docker, start from clean
<Armbian-Discord>
<IgorPec> and start from a clean clone, then add your changes part by part
<Armbian-Discord>
<IgorPec> that would be best thing IMO
<wifasoi[m]>
nekomancer: I'm doing a rm -rf cache and output each time
<Armbian-Discord>
<IgorPec> understand, but something else is here the problem. i suspect
<wifasoi[m]>
ahaa, t does resuse the same cointainer each time?
<wifasoi[m]>
ok.. i'll try that too
<Armbian-Discord>
<IgorPec> yes
<nekomancer[m]>
then sorry. did you touch a rootfs building code?
<Armbian-Discord>
<Tenkawa> that looks like a binfmt-multiarch problem
<Armbian-Discord>
<Tenkawa> from the last pastebin
<wifasoi[m]>
rootfs no.. just uboot and kernel patches
<wifasoi[m]>
ok.. this can be something.. I did notice it gave a warning with the armbian-new
<wifasoi[m]>
but i verified the module is loaded and mounted
<wifasoi[m]>
so i dismissed the error.. but maybe I should investigate it further
<Armbian-Discord>
<Tenkawa> I would chroot into that container and make sure you can run /bin/bash manually
<Armbian-Discord>
<ManoftheSea> If both copies fail, yes, there's a problem and you don't have a... what is that, SPL stage?
<Armbian-Discord>
<ManoftheSea> but then... there should have been an earlier failure on the "make" command
<nekomancer[m]>
then just redirect error message to `null` there will be enough? no error handling required on this step?
<Armbian-Discord>
<ManoftheSea> I'm not opposed to belt-and-suspenders.
<Armbian-Discord>
<ManoftheSea> If you're cleaning it up already, by all means you can put a check there.
<Armbian-Discord>
<ManoftheSea> But I expect there'd be a failure either before it or later, when the script tries to grab that file to stuff it in the bootloader code location and it doesn't exist
<Armbian-Discord>
<ManoftheSea> Also, is this on armbian-next?
<nekomancer[m]>
no, it's master
<nekomancer[m]>
I see an error on a daily work and warn
The_Loko has quit [Quit: Leaving]
xoan5 has joined #armbian
xoan has quit [Ping timeout: 268 seconds]
xoan5 is now known as xoan
<wifasoi[m]>
ok.. after deleteing the immage, checkout a tagged release and clearing the cache... it still give me the chroot error.... So the problem is my machine. I'll spray some holy eater and pray :D
<wifasoi[m]>
* ok.. after deleteing the immage, checkout a tagged release and clearing the cache... it still give me the chroot error.... So the problem is my machine. I'll spray some holy water on the pc and pray :D
xoan7 has joined #armbian
xoan has quit [Ping timeout: 268 seconds]
xoan7 is now known as xoan
<nekomancer[m]>
`Use Branch Target Identification for kernel (ARM64_BTI_KERNEL) [Y/n/?] (NEW)`?
<Armbian-Discord>
<ManoftheSea> Y
<nekomancer[m]>
`Memory Tagging Extension support (ARM64_MTE) [Y/n/?] (NEW)`?
<Armbian-Discord>
<ManoftheSea> Isn't that an 8.2 feature? I mean, it doesn't hurt to compile it in, as demonstrated by the default Y choice, but I dont' think it'll benefit any of our boards.
<nekomancer[m]>
I use `SKIP_EXTERNAL_TOOLCHAINS=yes` and `gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)`
shoragan has quit [*.net *.split]
martinayotte has quit [*.net *.split]
steev has quit [*.net *.split]
[TheBug] has quit [*.net *.split]
shoragan has joined #armbian
steev has joined #armbian
<nekomancer[m]>
omg! that options appears if i use system gcc, and nott appears, if i use builder-downloaded gcc!
<nekomancer[m]>
magic!
<Armbian-Discord>
<Jason123> Is the nano pi neo the cheapest sbc with ethernet? or is there anything cheaper
archetech has joined #armbian
samythemany has joined #armbian
<Armbian-Discord>
<Werner> Did you check prices on OPi1 or OPi0?
<Armbian-Discord>
<Werner> 1 has HDMI which is more or less useless since memory is too low for desktop usage. 0 has no HDMI but WiFi which however is total crap ^^
<Armbian-Discord>
<Werner> Price should be almost identical
<Armbian-Discord>
<Jason123> i know I saw someone talk about it somewhere but can't find anything online
<Armbian-Discord>
<Jason123> do you happen to have a link
<ArmbianHelper>
^ For Orange Pi One H3 ARM Cortex A7 4 Core 1GB DDR3 Memory Open Source Programming Learning Board MCU Development Board| | - AliExpress
<Armbian-Discord>
<Jason123> what would be better? Or are they all almost the same
<Armbian-Discord>
<Werner> I have no experience with Zero Pi so cannot tell. I assume it'd run just fine
<Armbian-Discord>
<Jason123> its the same cpu and ram
<Armbian-Discord>
<Jason123> do i even need a case for the sbcs? I always tend to get one but it might not even be needed
<Armbian-Discord>
<Werner> That is up to you. I dont have any cases for mine
<Armbian-Discord>
<Werner> As long as you dont throw them somewhere that could cause short circuits on the board, like a bag of metal shavings, you will be fine.
<Armbian-Discord>
<Jason123> do i need a heat sink?
<Armbian-Discord>
<Werner> For H3? Nah
<Armbian-Discord>
<Jason123> the orange pi zero has a H3 cpu and the zero pi has a H3 and the Orange Pi One also has an H#
<Armbian-Discord>
<Jason123> is one much better or does it not matter much
<archetech>
I like the odroid c4
<archetech>
for low end
<archetech>
can run a desktop too
<archetech>
well $65 isnt low end was like $50
<Armbian-Discord>
<Werner> H2+ is basically a H3 with its balls cut off by removing GBe and 4k HDMI. Otherwise they are identical
<archetech>
too bad radxa zero 2 cant get its act together
<Armbian-Discord>
<Jason123> yeah i have the radxa zero and its a nice little board
<Armbian-Discord>
<Jason123> ok
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
samythemany has quit [Remote host closed the connection]
samythemany has joined #armbian
samythemany has quit [Ping timeout: 258 seconds]
Masterphi has joined #armbian
califax has quit [Ping timeout: 258 seconds]
califax has joined #armbian
crabbedhaloablut has quit [Ping timeout: 258 seconds]
crabbedhaloablut has joined #armbian
Manouchehri has quit [Quit: Connection closed for inactivity]