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 | Type 'help' for help | Logs: -> irc.armbian.com
<lanefu> There were several layout changes. For example, the RAM has been split into two separate banks and the 16GB eMMC has moved to where the RAM used to be. Once again, Android, Ubuntu, and Debian will be available. Like other Orange Pi SBCs this should be an open-spec, community backed product
<lanefu> how do you split 3 gigs of ram
<lanefu> lol
<lanefu> so dumb question
<lanefu> if they swap out the chips for ethernet and sound n stuff, but its all mixed to the same pins
<lanefu> is there any device tree changes needed?
<lanefu> assuming all voltages and delays n stuff are teh same
cheakoirccloud has joined #armbian
<steev> dt changes would be needed for the new bits, but conceivably, it would boot with the old ones assuming the pins really are the same
cheakoirccloud has quit []
ermine[m] has quit [Bad user info]
threenp1 has quit [Quit: Bridge terminating on SIGTERM]
samythemany has quit [Quit: Bridge terminating on SIGTERM]
califax- has joined #armbian
samythemany has joined #armbian
threenp has joined #armbian
califax has quit [Ping timeout: 276 seconds]
califax- is now known as califax
<Armbian-Discord> <T​onymac32> yeah but drivers are likely different. Boot, sure, work, not as much
califax- has joined #armbian
califax has quit [Ping timeout: 276 seconds]
califax- is now known as califax
phipli has quit [Ping timeout: 240 seconds]
phipli has joined #armbian
Net147 has quit [Quit: Quit]
Net147 has joined #armbian
Net147 has quit [Changing host]
Net147 has joined #armbian
<Armbian-Discord> <I​gorPec> https://github.com/armbian/build/pull/3420
<Armbian-Discord> <I​gorPec> @Werner good morning. IRC is down?
archetech has quit [Quit: Konversation terminated!]
<Armbian-Discord> <W​erner> Good morning. Seems fine to me
<Armbian-Discord> <W​erner> Ah hold on
<JackFrost> Seems OK so far.
<Armbian-Discord> <W​erner> @IgorPec should be good to go. retry
<Werner> JackFrost, I assume he means access to his bouncer and yes, I messed up firewall somewhen yesterday I guess
<JackFrost> Hah, oops!
<Armbian-Discord> <I​gorPec> @Werner works now, tnx
<Armbian-Discord> <W​erner> Np and sorry
<IgorPec> i took a break, so it was added value ;)
walidasl__ has joined #armbian
walidasl__ has quit [Read error: Connection reset by peer]
walidasl has joined #armbian
walidasl has quit [Remote host closed the connection]
maknho has quit [Ping timeout: 240 seconds]
samythemany has quit [Quit: Bridge terminating on SIGTERM]
threenp has quit [Quit: Bridge terminating on SIGTERM]
Dagger has quit [Ping timeout: 250 seconds]
BCMM has joined #armbian
Dagger has joined #armbian
maknho has joined #armbian
samythemany has joined #armbian
threenp has joined #armbian
juri_ has quit [Ping timeout: 240 seconds]
alekksander has joined #armbian
juri_ has joined #armbian
peterm6881 has joined #armbian
peterm6881 has quit [Quit: Leaving]
peterm6881 has joined #armbian
peterm6881 has quit [Client Quit]
peterm6881 has joined #armbian
peterm6881 has quit [Client Quit]
samythemany has quit [Quit: Bridge terminating on SIGTERM]
threenp has quit [Quit: Bridge terminating on SIGTERM]
peterm6881 has joined #armbian
peterm6881 has left #armbian [#armbian]
samythemany has joined #armbian
threenp has joined #armbian
BCMM has quit [Quit: Konversation terminated!]
threenp has quit [Remote host closed the connection]
samythemany has quit [Remote host closed the connection]
BCMM has joined #armbian
samythemany has joined #armbian
threenp has joined #armbian
BCMM has quit [Ping timeout: 256 seconds]
<IgorPec> yeah
Mony_ is now known as Mony
Mony has quit [Changing host]
Mony has joined #armbian
<juri_> so, just a data point: just moved my my cubieboard2 to nightly, rebooted.. fail.
<IgorPec> anything on uart?
<juri_> no uart hooked to it, for now. i'll let you know when i do my next debugging cycle.
<juri_> about the onl useful datum i still have is that it ran 5.10.60-sunxi with sata, successfully.
BCMM has joined #armbian
* nekomancer[m] kill loving N2 with do-release-upgrade to impish.
<nekomancer[m]> already try to restore uboot with https://docs.armbian.com/User-Guide_Recovery/#flashing-boot-loader from manually build u-boot from armbian/master.
<nekomancer[m]> part of conole log https://dpaste.com/D44M5GZQ9
<nekomancer[m]> but marked files available in /boot... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/f660ab737a38da11cbb3f5e256ab1e3b489c6454)
<IgorPec> yeah, dirty n2 boot
<nekomancer[m]> and I can boot from self just-created armbian impish image
<nekomancer[m]> from sdcard
<nekomancer[m]> broken image on module
<nekomancer[m]> will try to build edge kernel package and install it with apt in chroot, booted from sdcard...
<nekomancer[m]> what to try if that not helps?
<IgorPec> check if dtb and kernel images has proper linkx
<IgorPec> according to boot script
<nekomancer[m]> not like to move to fresh image... that was a pet, not a kettle™
<IgorPec> you can recover - there is a hint / walk trou in docs
<nekomancer[m]> hm.. you are right — there are simlinks to kernel images, but not images itself! nice!
<nekomancer[m]> dtb on place
<IgorPec> winning question is - how this happen?
<nekomancer[m]> after system reboot at the end of `do-systemupgrade` script work
<nekomancer[m]> at start it was ubuntu-hirsute system.
<nekomancer[m]> sorry, `do-release-upgrade` script
<nekomancer[m]> s/systemupgrade/release-upgrade/
<IgorPec> i did the same upgrade few days ago, but don't remember on which device ... and it went well
<nekomancer[m]> and what do you answerto upgrader questions about changed files /etc/issue and like it? where old was with something like "current armbian version", and new was "new ubunru version"?
<IgorPec> keep current
<nekomancer[m]> now I see on broken system in os-release fi;e PRETTY_NAME="Ubuntu 21.10", on just-generated with armbian system impish image PRETTY_NAME="Armbian 22.02.0-trunk Impish"
* nekomancer[m] choose `keep current` too
Guest8359 has joined #armbian
<juri_> ok, bringing up my first bpim2berry.
<nekomancer[m]> bpim2berry,
<nekomancer[m]> * bpim2berry?
<juri_> banana pi m2 berry.
<nekomancer[m]> good luck!
indy has quit [Read error: Connection reset by peer]
indy has joined #armbian
marco44 has quit [Ping timeout: 268 seconds]
marco44 has joined #armbian
technomancy has joined #armbian
<technomancy> I seem to have bricked my Pine64 A64-LTS by running the "firmware" upgrade command in armbian-config on buster. any idea if it is possible to undo this?
<technomancy> it was working fine until I ran apt update+upgrade which made it lose the ability to scan for wifi, I ran the firmware update thinking that might fix the wifi but instead it lost the entire ability to boot, even with a fresh install on a fresh SD card which I've confirmed works fine on a separate pine64 device.
<technomancy> (at least I've learned a very important lesson about never upgrading anything that currently works)
<Armbian-Discord> <I​gorPec> we do a lot of upgrade testings ... strange
<Armbian-Discord> <I​gorPec> but ofc not all cases can be checked ... can you debug /boot folder on your SD card?
<technomancy> nah, none of the files in /boot have been modified this year
<technomancy> in fact, none of the files on the entire SD card have been modified
<technomancy> I guess at this point maybe it's more of a pine64 question than an armbian question
<technomancy> "why not run an upgrade? worst case scenario is I just flash a fresh OS image on my SD card" - me, an idiot
<Armbian-Discord> <I​gorPec> pine64 provides no software support
<Armbian-Discord> <I​gorPec> we cover everything until you power the hardware
<Armbian-Discord> <I​gorPec> also sometimes power cycle helps. if you haven't tried it yet
<technomancy> many, many times
<Armbian-Discord> <I​gorPec> ok, then https://docs.armbian.com/User-Guide_Recovery/
<Armbian-Discord> <I​gorPec> or reflash with latest
<Armbian-Discord> <I​gorPec> perhaps sd card died
<Armbian-Discord> <I​gorPec> the boot part. also seen that before
<technomancy> I've tried 3 different A1 cards with both the buster and the bullseye images
<Armbian-Discord> <I​gorPec> and none works?*?
<Armbian-Discord> <I​gorPec> well, i don't have this hardware to confirm
<technomancy> consistently they all work on my one pine64 which did not get the firmware update and not on the board that did
<technomancy> the u-boot recovery method isn't an option if there's no display signal, right?
<technomancy> I don't have a serial adapter on hand
<Armbian-Discord> <I​gorPec> serial console is usually needed. not sure if u-boot hdmi is enabled
<technomancy> all these recovery options seem to involve making changes to the SD card, but I feel pretty confident that the problem is not on the SD card
<Armbian-Discord> <I​gorPec> then it could also break down
<Armbian-Discord> <I​gorPec> hw failure
<technomancy> I mean it's possible but this board has been sitting on my shelf untouched for a couple years; all morning it's perfectly fine across multiple reboots, and then immediately following a firmware upgrade it stops booting.
<Armbian-Discord> <I​gorPec> without proper debugging ... there is nothing we can do
<technomancy> ok, well, thanks for confirming
<technomancy> better to know it's hopeless than to spend a bunch of time trying to revive something that's irrevocably destroyed
<Armbian-Discord> <I​gorPec> i can't even confirm this board works since i don't have it. someone else would need
technomancy has left #armbian [ERC (IRC client for Emacs 26.1.50)]
<juri_> ok, and the bpim2u (berry version) also has working sata on 5.10.60-sunxi.
Guest8359 has quit [Quit: Client closed]
chris64 has joined #armbian
archetech has joined #armbian
bosje has joined #armbian
<bosje> A question: I'm trying to install wireguard on an SBC (odroid n2+ with armbian/bullseye) - why does apt want to install a new kernel?
<archetech> probly cuz it reqs some network features
<bosje> Ah ok, I don
<bosje> I don't want to change the kernel *
<bosje> i guess i can try to install wireguard-dkms?
<archetech> would still need kern
<bosje> In the debian package list, i don't see the rt kernel as a requirement
<bosje> it requires the wireguard-module
<bosje> but this should already be built in the kernel (5.10.81)
<archetech> either upg kern or build your own
<bosje> i installed the kernel headers and dkms, then wireguard. The requirement for RT went away
<bosje> weird
<archetech> well ya could have looked in curr kern to see if wg stuff was ticked
<bosje> how do you do that?
<archetech> grep the config
<archetech> or look in the armbian kern repo for config
<bosje> I don't see wireguard or wg in the /boot/config
<bosje> not even commeted out
<bosje> ah no, it is set:
<bosje> cat /boot/config-5.10.81-meson64 | grep CONFIG_WIREGUARD
<bosje> CONFIG_WIREGUARD=m
<archetech> now ya know
<bosje> :)
<archetech> now im curious why the wg deps wanted a rt kernel
<archetech> or dif kern at all
<bosje> that was my question too
<bosje> From #debian:
<bosje> ] <sney> wireguard requires a kernel driver in order to work, so it depends on wireguard-modules which is a Provides of linux-image-rt-$arch
<bosje> [23:38] <sney> the necessary module may already be in the odroid kernel, but odroid probably didn't provide that information to ap
<bosje> [23:38] <sney> t
<bosje> [23:39] <sney> if the driver is present, you can use equivs to tell apt that the kernel is already installed, and you may want to email the odroid devs about this issue.
<bosje> [23:39] <sney> !equivs
<bosje> [23:39] <dpkg> equivs is a package that enables you to create dummy packages that tell <apt> you really have installed (through some other means) the package. apt install equivs, and read /usr/share/doc/equivs/*, see also <usrlocal>. A better plan is often to adapt the Debian packages to your needs, ask me about <package recompile> <uupdate> <ssb>.
<archetech> ah a deb-ism
<archetech> figures
<archetech> one reason I use all odroid or arch/manjaro on my N2+
<IgorPec> bosje is not using armbian
<archetech> right its plain deb it seems
<bosje> No, i am using armbian
<IgorPec> nope
<bosje> ?
sunshavi_ has quit [Ping timeout: 256 seconds]
<IgorPec> The following NEW packages will be installed:
<IgorPec> linux-image-5.10.0-10-rt-arm64 linux-image-rt-arm64 wireguard
<IgorPec> wiregoard is preinstalled on armbian btw
<bosje> this is what i got when i typed sudo apt install wireguard
<bosje> i didn't know that
sunshavi_ has joined #armbian
<IgorPec> wireguard on debian will probably go to compile module
<bosje> i literally installed armbian bullseye 30 minutes ago
<IgorPec> this dependency is strange ... anyway. just install tools
<bosje> yes; it worked
<IgorPec> wireguard tools is all you need
<bosje> its pretty fast :)
<bosje> 16mbps
<IgorPec> aha, you already got it working?
<bosje> yes I used this script: https://github.com/Nyr/wireguard-install
<bosje> i already had my domain set up.
<bosje> I tried it last night, but it installed the other kernel I mentioned above, and this messed up the system, so I re-flashed it with a fresh image
<IgorPec> yeah, you got luck that it booted at all
<bosje> yea
<bosje> it is back to the correct kernel now
<bosje> Linux obox 5.10.81-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:21:51 UTC 2021 aarch64 GNU/Linux
<IgorPec> yes. that should be fine. we might bump to 5.15.y in 1.5 month
<bosje> neat
<bosje> how do i preform kernel upgrades? (When it is time) With armbian-config?
<IgorPec> this one will be automatic, otherwise armbian-config -> alternative kernels
<bosje> cool thanks
<bosje> wait, you can push kernel updates remotely?
<IgorPec> no no, i mean when you will do apt update upgrade
<IgorPec> we have 3 tags, legacy, current and edge
<bosje> ahh
<IgorPec> current is now 5.10.y and that will be 5.15.y
<IgorPec> regardless of userland (Debian x, Ubuntu y)
<IgorPec> Linux is the king at Armbian ;)
<bosje> ahh i see
<bosje> thanks for the help!!
threenp has quit [Ping timeout: 276 seconds]
samythemany has quit [Ping timeout: 276 seconds]
samythemany has joined #armbian
<nekomancer[m]> I run in chroot of my dead N2 `# dpkg -i armbian-bsp-cli-odroidn2_22.02.0-trunk_arm64.deb linux-dtb-edge-meson64_22.02.0-trunk_arm64.deb linux-headers-edge-meson64_22.02.0-trunk_arm64.deb linux-image-edge-meson64_22.02.0-trunk_arm64.deb linux-libc-dev_22.02.0-trunk_arm64.deb`
<nekomancer[m]> And got a kernel crash in btrfs :)
<nekomancer[m]> sad sad sad
threenp has joined #armbian
flyback has quit [Quit: Leaving]
flyback has joined #armbian
<nekomancer[m]> next run no kernek crash, but install unsuccessful