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
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
<Armbian-Discord> <r​neese> so who has made a retropi out of a armbian box
qqqhhh has quit [Quit: Ping timeout (120 seconds)]
qqqhhh has joined #armbian
mrueg has quit [Ping timeout: 240 seconds]
<Armbian-Discord> <r​neese> low power
<Armbian-Discord> <r​neese> when is arm going to get 3 ghz and 4ghz
mrueg has joined #armbian
<Armbian-Discord> <T​onymac32> When the market for cheap processors needs it
<Armbian-Discord> <N​eonFetch> Well, retro orange pi is made based on armbian
nick_ has joined #armbian
nick_ has quit [Client Quit]
sams has joined #armbian
<sams> heh cool i sorted out the pis from going down on a daily basis, got a powerboard with 4 usb does 10A total and 3.4A per slot max, got two of the pi on it and they been up all week no dramas now, yay.
<sams> i initially thought it may have bbeen overheating from syncthing and nextcloud stuff, then kernel, then other custom apps, turns out it was because of the lack of power
<sams> well, sufficient power that is
<Armbian-Discord> <l​anefu> See retrorangepi project
<Armbian-Discord> <r​neese> have to get a controller now
<Armbian-Discord> <r​neese> so I can play some games
<Armbian-Discord> <r​neese> i miss playing wii bowling
<Armbian-Discord> <r​neese> I was good at it
<Armbian-Discord> <l​anefu> Wii retro probably needs to be x86
<Armbian-Discord> <l​anefu> But ill let the gaming experts speak to that
<Armbian-Discord> <l​anefu> Well probably just fine on your m1
<Armbian-Discord> <r​neese> i have a pi 3 bv2 here so I can run retro pi on it
<Armbian-Discord> <r​neese> I will have to find roms
<Armbian-Discord> <r​neese> to put it on the card
<Armbian-Discord> <r​neese> the only thing I would use it for it was for a mmdvm radio card
<stipa> sams: awesome
hyphop has joined #armbian
<hyphop> hello
sunshavi has joined #armbian
p0g0__ has joined #armbian
p0g0_ has quit [Ping timeout: 252 seconds]
<IgorPec> good morning
plntyk has quit [Quit: Leaving]
<Armbian-Discord> <l​anefu> Yo
<IgorPec> you, what's up
<Armbian-Discord> <l​anefu> Not much just busy day yesterday. Dog woke me up a few min ago so catchin up for a bit
<Armbian-Discord> <l​anefu> Martin recieved his khadas boards yesterday
<Armbian-Discord> <l​anefu> And yeah the nic is verrrry wonky on edge v
<IgorPec> if you let random mac as is, it works
<IgorPec> if you set mac with our tricks, its random failure.
<Armbian-Discord> <l​anefu> Oh
<IgorPec> something like that
<Armbian-Discord> <l​anefu> Yeah by default it got dhcp and yeah stops working
<IgorPec> let's try to work out on this problem with khadas
<Armbian-Discord> <l​anefu> So the khadas board has an efuse
<IgorPec> yes
<Armbian-Discord> <l​anefu> And uboot can read that.
<IgorPec> they also support nic in u-boot, so you can boot from network
<Armbian-Discord> <l​anefu> With a uboot command so it may just be some uboot script tweaks
<IgorPec> i am more worrying about that desktop failure on glx since it affects more boards
<Armbian-Discord> <l​anefu> I haven't been tracking that
<IgorPec> i was looking into and tony as well, but no resolution
<Armbian-Discord> <l​anefu> Are we accidentally installing multiple xorg configs?
<IgorPec> nope
<Armbian-Discord> <l​anefu> If you switch driver back to fbdev instead of modesetting does it work?
<IgorPec> i didn't change that
<IgorPec> you mean here setting driver to fbdev?
<Armbian-Discord> <l​anefu> Look at line 225 and hit blame button
<IgorPec> lets try it ...
<Armbian-Discord> <I​gorPec> also have to check CI - rneese is complaining it doesn't contain his changes
<Armbian-Discord> <I​gorPec> perhaps he is still copyig stuff to the desktop package, that would explain
<Armbian-Discord> <l​anefu> When CI beta images build does the subrevision get updated
<Armbian-Discord> <l​anefu> But yeah desktop package would explain also
<Armbian-Discord> <I​gorPec> building beta packages now, it was some break which was fixed
<Armbian-Discord> <I​gorPec> then images too see if changes are there
<Armbian-Discord> <l​anefu> Tony keeps on starting to type.. i wonder if he wants to choke me
<Armbian-Discord> <I​gorPec> haha
<Armbian-Discord> <l​anefu> I thought the modesetting driver worked on glx if we turned accel.off
<Armbian-Discord> <I​gorPec> i'll try both now, just made an image
<Armbian-Discord> <l​anefu> The modesetting driver is what lets users easily set screen resolution with the normal tools..
<Armbian-Discord> <I​gorPec> which apparently doesn't work or some additional setting is needed
<ArmbianHelper> AR-833 [Bug] "Khadas Edge V no HDMI audio" reported by Lane Jennison at 2021-07-05. Status: To Do
<hyphop> no audio device or just no sound ?
<Armbian-Discord> <I​gorPec> lanefu: waiting for system to finished booting - is that possible to wait for login, so we have a clear screen
<Armbian-Discord> <l​anefu> No audio device
<hyphop> kernel version ?
<Armbian-Discord> <l​anefu> 5.10.x
<Armbian-Discord> <l​anefu> Explain more please? Yeah you can delete that echo message
<Armbian-Discord> <I​gorPec> that we execute autologin after everything is loaded
<Armbian-Discord> <l​anefu> Oh have autologin the systemd service wait to launch instead of my inline wait?
<hyphop> grep SOC_ROCK config-5.12.0
<hyphop> CONFIG_SND_SOC_ROCKCHIP=m
<hyphop> CONFIG_SND_SOC_ROCKCHIP_I2S=m
<hyphop> CONFIG_SND_SOC_ROCKCHIP_MAX98090=m
<hyphop> CONFIG_SND_SOC_ROCKCHIP_PDM=m
<hyphop> CONFIG_SND_SOC_ROCKCHIP_RT5645=m
<hyphop> CONFIG_SND_SOC_ROCKCHIP_SPDIF=m
<Armbian-Discord> <I​gorPec> yes, i didn't know how to set that wait ... so basically we have to wait everything loads, then start with autologin procedure
<Armbian-Discord> <l​anefu> Hyphop nah its deeper than that ill have to share the dmesg errors later
<Armbian-Discord> <l​anefu> Yeah send me tickdt for that
<Armbian-Discord> <l​anefu> Going back to bed
<Armbian-Discord> <I​gorPec> ok, catch you later
<Armbian-Discord> <I​gorPec> changing from modesetting to fbdev fixes desktop in vim 1 and 2
ced117_ has quit [Ping timeout: 272 seconds]
ced117 has joined #armbian
ced117 has quit [Changing host]
ced117 has joined #armbian
hyphop has quit [Ping timeout: 240 seconds]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
hyphop1 has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
CrashTestDummy3 has joined #armbian
archetyp has quit [Remote host closed the connection]
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
CrashTestDummy2 has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 268 seconds]
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
<hyphop1> modesetting + glamore - works well for VIM1
CrashTestDummy has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 265 seconds]
hyphop1 has left #armbian [#armbian]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
<Armbian-Discord> <I​gorPec> tnx
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
willmore has quit [Remote host closed the connection]
<Armbian-Discord> <r​neese> Arm-Be-In
<nekomancer[m]> it's impossible for me to build image for hirsute on focal builder, with docker too.
<nekomancer[m]> should I upgrade my builder to hhirsute? but focal is LTS, hirsute not LTS
<Armbian-Discord> <r​neese> no
<Armbian-Discord> <r​neese> you have to build hirsute on hirsute now
<Armbian-Discord> <r​neese> due to small issues
<Armbian-Discord> <I​gorPec> but docker should work
<Armbian-Discord> <I​gorPec> docker is using hirsute image
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
rdo` has quit [Quit: Coyote finally caught me]
rdo has joined #armbian
<e3ef13f4ff44> what is not working on Orange Pi Zero 2 as for now?
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
lanefu has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
<Armbian-Discord> <r​neese> its a pi thats orange thats it
sunshavi has quit [Ping timeout: 272 seconds]
peterm6881 has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
<Armbian-Discord> <N​icoD> it's not even orange.
archetyp` has joined #armbian
archetyp` has quit [Remote host closed the connection]
archetyp` has joined #armbian
archetyp has quit [Ping timeout: 256 seconds]
<nekomancer[m]> I try to build with docker `BOARD=odroidn2 BRANCH=edge` on builder with ubuntu focal.
<nekomancer[m]> successful `RELEASE=` `focal`, `buster` not ok — `hirsute`, `bullseye`, `sid`. same error `ERROR in function create_rootfs_cache` https://paste.debian.net/1203841/
archetyp` has quit [Remote host closed the connection]
archetyp has joined #armbian
<Armbian-Discord> <I​gorPec> under docker?
<Armbian-Discord> <I​gorPec> are you sure you are using latest docker image?
<Armbian-Discord> <I​gorPec> this is not updated by force. you need to manually copy docker config to userpatches and run ./compile dockerpurge (to remove) and once again normally
<nekomancer[m]> fresh. but will recreate again now. remember — I submit patches to dockerfile some days ago.
<Armbian-Discord> <I​gorPec> huh
<Armbian-Discord> <I​gorPec> does it build ubuntu 21.04 docker system?
<Armbian-Discord> <I​gorPec> exactly this way it fails on focal
<nekomancer[m]> > <I​gorPec> does it build ubuntu 21.04 docker system?
<nekomancer[m]> sorry? not understand :(
<nekomancer[m]> yes, with docker
<nekomancer[m]> just rebuild docker image now. same result.
<Armbian-Discord> <I​gorPec> if you create docker image from scratch you should see in the console which ubuntu is going to be constructed in docker
<Armbian-Discord> <I​gorPec> just to make sure you are running 21.04 ... also you can execute shell by hand and check
<Armbian-Discord> <I​gorPec> let me check ... i also have it on my desktop
<Armbian-Discord> Command sent by IgorPec
<Armbian-Discord> ./compile.sh dockerpurge [ o.k. ] This script will try to update [ warn ] Purging Armbian Docker containers [ o.k. ] Using config file [ /home/igorp/Coding/build/userpatches/config-docker.conf ] [ .... ] Docker container not found or out of date [ .... ] Building a Docker container Sending build context to Docker daemon 512kB Step 1/10 : FROM ubuntu:21.04
<Armbian-Discord> <I​gorPec> for the future, we can expand docker unit test https://github.com/armbian/build/blob/master/.github/workflows/build.yml#L163-L230
<Armbian-Discord> <I​gorPec> currently its very primitive
<Armbian-Discord> <I​gorPec> works for me
<Armbian-Discord> <I​gorPec> [ o.k. ] Installing base system [ Stage 2/2 ] /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) W: Failure trying to run: mount -t proc proc /proc W: See //debootstrap/debootstrap.log for details I: Installing core packages... I: Unpacking required packages... I: Unpacking base-files... I: Unpacking base-passwd... I: Unpacking bash... I: Unpacking bsdutils... I: Unpacking coreutils... I: Unpac
<Armbian-Discord> I: Unpacking debconf...
<Armbian-Discord> <I​gorPec> hirsute cli
<nekomancer[m]> <Armbian-Discord "<I​gorPec> if you create docker "> sure hirsute there
<Armbian-Discord> <I​gorPec> one moment, i am using probably some older config
<Armbian-Discord> <I​gorPec> +DOCKER_FLAGS+=(--privileged)
<Armbian-Discord> <I​gorPec> this is the only diff
<Armbian-Discord> <I​gorPec> and probably the clue
<Armbian-Discord> <i​av> oh, yess!
<Armbian-Discord> <i​av> 90% it is
flyback has quit [Ping timeout: 240 seconds]
<nekomancer[m]> hm/. I uncomment `DOCKER_FLAGS+=(--privileged)` in `userp~hes/config-docker.conf` — but error still there
<Armbian-Discord> <I​gorPec> x86?
<Armbian-Discord> <i​av> yes.
<Armbian-Discord> <I​gorPec> running low on ideas
<nekomancer[m]> you have `focal` builder?
<nekomancer[m]> of hirsute already?
<Armbian-Discord> <I​gorPec> my host is linux mint
<nekomancer[m]> outside of docker
<Armbian-Discord> <I​gorPec> 20 / ulyana
<nekomancer[m]> it's focal sister I think. afaik mint based on LTS
<Armbian-Discord> <I​gorPec> yes, focal level
<nekomancer[m]> 😭
flyback has joined #armbian
f476_ has joined #armbian
f476 has quit [Ping timeout: 246 seconds]
f476_ has quit [Ping timeout: 255 seconds]
peterm6881 has quit [Quit: Leaving]
<nekomancer[m]> victory.
<nekomancer[m]> igorpec, it works with `--privileged` after `docker run --rm --privileged multiarch/qemu-user-static --reset -p yes`
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 268 seconds]