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
<Armbian-Discord> <Z​anoryt> Preparing to unpack .../linux-dtb-current-rockchip64_22.02.1_arm64.deb ... Unpacking linux-dtb-current-rockchip64 (22.02.1) ... Setting up linux-dtb-current-rockchip64 (22.02.1) ... E: Unable to locate package armbian-bsp-cli-rockpi-4b
<nekomancer[m]> Z​anoryt: builder arm or x64? docker or no?
<Armbian-Discord> <Z​anoryt> rockpi-4b which is arm... yes docker
<nekomancer[m]> I have something looks similar if build image on arm64 and docker.
<nekomancer[m]> but still not found foots of problem. but seems arm-only for me
Mangix has joined #armbian
norwich_ has joined #armbian
norwich has quit [Ping timeout: 260 seconds]
norwich_ is now known as norwich
<Armbian-Discord> <Z​anoryt> The only way I bypass that is by not providing bsp in the REPOSITORY_INSTALL
<nekomancer[m]> uuu. I got my error trying to install just build kernel.
<nekomancer[m]> not from repository
<Armbian-Discord> <Z​anoryt> yeah i do kernel from repo, but bsp from not repository
<Armbian-Discord> <Z​anoryt> and that works
<Armbian-Discord> <Z​anoryt> REPOSITORY_INSTALL="u-boot,kernel,armbian-config,armbian-config,armbian-firmware"
<nekomancer[m]> with that addition my built breaks as:
DarkG has quit [Excess Flood]
slacker_HD has joined #armbian
DarkG has joined #armbian
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
xoan8 has joined #armbian
xoan has quit [Ping timeout: 255 seconds]
xoan8 is now known as xoan
<ArmbianHelper> ^ [ 77.446664] PM: suspend entry (s2idle)[ 77.482944] Filesystems sync: 0.03 - Pastebin.com
<Macer> blah
<Macer> there seems to be quite the tomfoolery going on there heh
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 240 seconds]
<stipa> Macer: try at #manjaro-arm
<stipa> you won't get much response since manjaro isn't supported here
<Macer> ah. naw. was just making a statement.
<Macer> that doesn't really look manjaro related. that looks more mainline kernel related to the pinebook pro
<stipa> steev: is manjaro arm dev
<steev> negative
<stipa> my bad
<steev> i'm kali
<Macer> kali kartel?
<Macer> when i tried the armbian img on it ... it didn't boot at all heh
<Macer> (from emmc)
<Macer> worked on SD though
<Macer> but i still had to manually write uboot to each
<stipa> yeah, better go to #manjaro-arm about manjaro stuff it's more appropriate
<stipa> if you can port the fix armbian do so
<stipa> to armbian*
<Macer> i wish i was that gifted
<Macer> the quick and easy fix was to write newer uboot
<Macer> or i may have used tow-boot for that one on spi
<stipa> maybe it's just the lack of someone who would look at it and is just a matter of simple patch
<Macer> (for armbian)
<Macer> stipa: for manjaro? maybe i'll head over there later. i'm already on the pin64 irc server and those guys are usually pretty good at working on stuff.. it's already a WIP
<Macer> i'm sure it's a difficult problem
<stipa> who knows
<stipa> what did you find ?
<Macer> nothing so far. i'm working on moving it back into a functional state. i just recently installed an nvme and different emmc module in it to rule that out
<stipa> if there's nothing you could be the one working on it
<Macer> i'm not a dev heh. missed my calling.
<Macer> i'll help them test later though
<stipa> if you think it's something serious report a bug so that it's not forgotten
<stipa> there was a pinebook over here but someone broken it hard
<stipa> armbina DE was also running on it and then nvme show up
<ArmbianHelper> ^ Board Maintainers - Armbian Documentation
<stipa> which one do you have pinebookpro or pinebook-a64 ?
<stipa> i doubt IgorPec has a pinebook...
<stipa> you lanefu and maybe someone else has it
<stipa> but IgorPec and lanefu are probably busy
<stipa> i guess it's a problem no one paid for solving
<stipa> Macer: does Manjaro with DE works on it?
amazingfate_ has joined #armbian
<steev> pinebook or pinebook pro? i saw mention of nvme so i'm assuming pbp?
<stipa> pbp
<stipa> do you have it?
amazingfate has quit [Ping timeout: 258 seconds]
xoan has quit [Ping timeout: 244 seconds]
<Macer> pinebook pro
<Macer> stipa: sure. i'm in manjaro with xfce right now. trying to figure out how to resize it since i just made an img of the old emmc and dd it to a new one so went from 64GB to 128GB
<Macer> and am mounting nvme as /home
<stipa> awesome, so there is a fix somewhere
<Macer> for armbian not booting? yah thought i twas odd because i actually used the copy app in armbian itself. i forgot its name. to install it fresh to emmc but didn't boot even if i wrote uboot to it
<Macer> although at the time i didn't have a serial cable. i do now so maybe later i'll take a look at it and see where it breaks.
<Macer> i vaguely remember not getting video at all but not being able to boot from sd afterwards. had to turn off emmc with the switch and turn it back on to fix it after booting an sd. i did manage to get it running on an sd though.
<Macer> but the pinebook pro has emmc issues. so that may be the problem. :)
<stipa> cool cool
amazingfate_ is now known as amazingfate
xoan has joined #armbian
smcavoy has quit [Read error: Connection reset by peer]
smcavoy has joined #armbian
schwarz_Kat has joined #armbian
lemonzest has joined #armbian
schwar3_Kat has joined #armbian
schwarz_Kat has quit [Ping timeout: 260 seconds]
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
Malditron has quit [Quit: Konversation terminated!]
alekksander has joined #armbian
xispita has quit [Read error: Connection reset by peer]
xispita has joined #armbian
<Armbian-Discord> <W​erner> Pbp neither has maintainer iirc nor is such device in the lab. So difficult to track issue down
<Armbian-Discord> <I​gorPec> Don't user REPOSITORY_INSTALL unless you are sure package exists there.
<Armbian-Discord> <I​gorPec> rockpi4b was without a maintainer for a while, which means status unknown
alekksander has quit [Quit: Konversation terminated!]
<Armbian-Discord> <Z​anoryt> Got it
<Armbian-Discord> <I​gorPec> after this upcoming release, packages for supported will certainly be there as we build images this way
slacker_HD has quit [Quit: Connection closed]
Myron has joined #armbian
Smedles has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Smedles has joined #armbian
Myron has left #armbian [#armbian]
Armbian-Discord has quit [Remote host closed the connection]
Armbian-Discord has joined #armbian
lemonzest has quit [Remote host closed the connection]
norwich_ has joined #armbian
norwich has quit [Ping timeout: 255 seconds]
norwich_ is now known as norwich
lemonzest has joined #armbian
archetech has quit [Quit: Konversation terminated!]
schwar3_Kat has left #armbian [Offline]
lemonzest has quit [Quit: WeeChat 3.5]
qqqhhh8615 has joined #armbian
qqqhhh861 has quit [Ping timeout: 256 seconds]
qqqhhh8615 is now known as qqqhhh861
<Macer> Werner: ah ok. i mean when it ran it ran well heh
lemonzest has joined #armbian
Smedles has quit [Remote host closed the connection]
Smedles has joined #armbian
maknho has quit [Ping timeout: 246 seconds]
Mangix has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
maknho has joined #armbian
walking_dead has joined #armbian
<nekomancer[m]> what does in `check_loop_device()` in `image-helpers`?
<nekomancer[m]> and I not understand how it should work.
<nekomancer[m]> I comment-out line `debootstrap.sh:657 #check_loop_device "$rootdevice"` and now build work again on my aarch64.
<nekomancer[m]> seems it not woks anymore on aarch64 platform.
<Armbian-Discord> <W​erner> Yes, at some point pbp ran very well on Armbian but then it broke. I had pbp for a few weeks and then gave it away to Nico
<Armbian-Discord> <I​gorPec> IMO it still works the same, but suspend was probably never working?
<Armbian-Discord> <W​erner> Apparently after install to eMMC it does no longer boot
<Armbian-Discord> <I​gorPec> aha, probably too optimistic eMMC settings in u-boot or similar
<Armbian-Discord> <I​gorPec> "mainline" features 😉
<Armbian-Discord> <W​erner> No idea. Maybe I can nag Nico to do some debugging once he is back from Netherlands. I gave him my audio serial adapter too so he has the hardware to dig 😉
<Armbian-Discord> <I​gorPec> i would do that https://github.com/armbian/build/pull/3719 if it will still be there
<ArmbianHelper> ^ move u-boot rockchip64 to 2022.04 by 150balbes · Pull Request #3719 · armbian/build · GitHub
<Armbian-Discord> <W​erner> @NicoD ☝️
Smedles has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Smedles has joined #armbian
<Armbian-Discord> <c​0rnelius> uboot v2021.10 broke eMMC on RK3399. so if you were running that version it could be why.
walking_dead has quit []
alekksander has joined #armbian
joshaspinall_ has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
joshaspinall has joined #armbian
<Armbian-Discord> <N​icoD> I'm back. Just working on finishing the videos. I'll try to do some tests on pbp. I wanted buster legacy xfce and that didn't boot.
joshaspinall has quit [Client Quit]
joshaspinall has joined #armbian
<Armbian-Discord> <I​gorPec> need review https://github.com/armbian/build/pull/3825
<ArmbianHelper> ^ Orangepizero2 fixing failed boot on current & edge by igorpecovnik · Pull Request #3825 · armbian/build · GitHub
archetech has joined #armbian
<Macer> c0rnelius: I’m guessing armbian img came with 2021.10
<Macer> Tbh tho I run 2021.07 on pbp now because emmc issues.
<Armbian-Discord> <I​gorPec> macer: ideally would be if you can test making image from https://github.com/armbian/build/pull/3719
<ArmbianHelper> ^ move u-boot rockchip64 to 2022.04 by 150balbes · Pull Request #3719 · armbian/build · GitHub
<Macer> Runs better with 2021.07 but suspend still won’t work and the emmc still does flakey things sometimes.
<Macer> IgorPec: are there changes from 2022.04 that the armbian team made? I tried manjaro 2022.04 and had no boot issues with emmc.
<Macer> ie: installed to emmc and wrote 2022.04 uboot and same issue. I can try it though.
<Armbian-Discord> <I​gorPec> aha. well, don't know
<Armbian-Discord> <I​gorPec> we never dealt with pinebook pro
<Armbian-Discord> <I​gorPec> a little yes
<Macer> (No boot issue with armbian for sure) manual tends to grind through sometimes.
<Macer> *manjaro
<Macer> 2021.07 is the most stable for actually booting. But I run into issues there also.
<Armbian-Discord> <I​gorPec> pinebook was manjaro business deal
<Macer> Yah.
<Macer> There is always tow-boot on spi which works the best but still no suspend.
<Macer> Suspend seems like a really odd problem for pbp. I guess at one point it actually worked but doesn’t now. Maybe I’ll try bsp uboot to see if it works out better.
<Macer> Rockchip is hiding the secret recipe.
<Armbian-Discord> <I​gorPec> they all do ;);
<Macer> Lol
<Armbian-Discord> <I​gorPec> it works so / so probably cause this support is hacked together by amateurs
<Macer> Makes me wonder if the hardware can actually even do it.
<Macer> Which would be a shame because having suspend functional would make the pbp the best device ever lol.
<Macer> Since my beloved n900.
<Armbian-Discord> <I​gorPec> i love my dell xps 13 more 😉
<Macer> I miss my n900 :(
<Macer> Haha. Well I want 14 hours of battery.
<Armbian-Discord> <I​gorPec> i am close to that, since i only use terminal, lol
<Macer> Hah
<Macer> Pbp is only 14 hours for office work on a sim screen tho.
<Macer> But it is a legit 14 or so hours. I can get actual work done.
<Armbian-Discord> <I​gorPec> and i always carry 20000mAh battery pack with me for another day of operations
<Macer> Ah. But I’d rather just have the laptop that I only need to charge once a week and let it suspend when necessary.
<Armbian-Discord> <I​gorPec> ofc it consumes more, but hey, suspend works 😉
<Armbian-Discord> <I​gorPec> apple m1 , but its locked even more
<Armbian-Discord> <T​enkawa> I got one of those and a 10000 in my bag as well
<Armbian-Discord> <T​enkawa> I was tired of carrying around a bunch of small 5A packs
<Armbian-Discord> <I​gorPec> yeah. 20k is i think also biggest you are allowed carrying to the plane
<Armbian-Discord> <T​enkawa> oh really?
<Armbian-Discord> <T​enkawa> goot to know
<Armbian-Discord> <I​gorPec> not sure if the number is correct, but there are some limits
<Armbian-Discord> <T​enkawa> I havent flown in a few years and getting ready to again
<Armbian-Discord> <I​gorPec> i think nobody did 😉
<Armbian-Discord> <T​enkawa> I didn't because of health
<Armbian-Discord> <T​enkawa> (havet since 2014)
<Armbian-Discord> <I​gorPec> i did eu / nz in 2019, that was last big one, this year just 3h flight
<Armbian-Discord> <T​enkawa> I use to fly to Europe a fair bit in the early 2000's
<Armbian-Discord> <I​gorPec> we plan Armbian meetup in Salzburg 😉
<Armbian-Discord> <I​gorPec> let's say no real planning yet, its more like an wish / idea
<Armbian-Discord> <I​gorPec> location sounds good for most people
<Armbian-Discord> <T​enkawa> heheh
Mangix has joined #armbian
<c0rnelius> Macer: to be honest I don't have pbp, but I recall it being an issue on rk3399.
<c0rnelius> in general.
<Armbian-Discord> <M​anoftheSea> Alas. I had two die by USB detachment
<Armbian-Discord> <I​gorPec> i only got Nokia E61 / still have it somewhere
<Armbian-Discord> <I​gorPec> BB style
<Armbian-Discord> <I​gorPec> and psion mx5
alekksander has quit [Ping timeout: 246 seconds]
* nekomancer[m] just found: during image preparation on jammy on aarch64 platform command `partprobe /dev/loop0` not creates device files for partitions in /dev. Then `check_loop_device()` detects it and fails.
* nekomancer[m] On x64 devices like `/dev/loop0p1` creates.
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
<juri_> oooh. i miss that psion.
amazingfate has quit [Remote host closed the connection]
amazingfate has joined #armbian
Mangix has quit [Ping timeout: 240 seconds]
Mangix has joined #armbian
Mony has joined #armbian
flyback has quit [Ping timeout: 244 seconds]
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #armbian
alekksander has joined #armbian
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #armbian
amazingfate has quit [Ping timeout: 255 seconds]
archetech has quit [Quit: Leaving]
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #armbian
<Macer> IgorPec you should have it in the fortress
amazingfate has joined #armbian
archetech has joined #armbian
<nekomancer[m]> J​ason123 ping
<nekomancer[m]> @J​ason123
<nekomancer[m]> J​ason123 I hope I fix our common bug. You can to try https://github.com/armbian/build/pull/3831
<ArmbianHelper> ^ Fix for build error on aarch64 with ERROR in function check_loop_device by iav · Pull Request #3831 · armbian/build · GitHub
flyback has joined #armbian
flyback has quit [Read error: Connection reset by peer]
flyback has joined #armbian
amazingfate has quit [Ping timeout: 240 seconds]
amazingfate has joined #armbian
alekksander has quit [Quit: Konversation terminated!]