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>
<Tonymac32> yeah but drivers are likely different. Boot, sure, work, not as much
<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>
<IgorPec> we do a lot of upgrade testings ... strange
<Armbian-Discord>
<IgorPec> but ofc not all cases can be checked ... can you debug /boot folder on your SD card?
<Armbian-Discord>
<IgorPec> or reflash with latest
<Armbian-Discord>
<IgorPec> perhaps sd card died
<Armbian-Discord>
<IgorPec> 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>
<IgorPec> and none works?*?
<Armbian-Discord>
<IgorPec> 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>
<IgorPec> 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>
<IgorPec> then it could also break down
<Armbian-Discord>
<IgorPec> 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>
<IgorPec> 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>
<IgorPec> 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>
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:
<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