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
<schwarz_Kat>
Some of my Armbian SBC's have only DMA32, others have only Normal, and some only DMA. None have more than one type.
<ArmbianHelper>
^ Chris's Wiki :: blog/linux/KernelMemoryZones
<schwarz_Kat>
My Intel and AMD PC's have all three types.
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 256 seconds]
abws has quit [Ping timeout: 250 seconds]
xoan6 has joined #armbian
xoan has quit [Ping timeout: 256 seconds]
xoan6 is now known as xoan
slacker_HD has joined #armbian
p0g0 has quit [Ping timeout: 276 seconds]
p0g0 has joined #armbian
p0g0_ has joined #armbian
p0g0 has quit [Ping timeout: 272 seconds]
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 240 seconds]
kilobyte_ch has quit [Quit: WeeChat 2.3]
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 276 seconds]
schwarz_Kat has left #armbian [Offline]
slacker_HD has quit [Quit: Connection closed]
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 240 seconds]
amazingfate has joined #armbian
lemonzest has joined #armbian
amazingfate_ has quit [Ping timeout: 276 seconds]
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 256 seconds]
archetech has quit [Quit: Konversation terminated!]
Unit193 has quit [Read error: Connection reset by peer]
schwarz_Kat has joined #armbian
Unit193 has joined #armbian
argonautx has joined #armbian
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 240 seconds]
<schwarz_Kat>
Weekend at last. o/
<schwarz_Kat>
I want to submit a PR to fix the r8152 usb ethernet tx offload bug that affects NanoPi R2S, Orange Pi R1plus and Orange Pi R1plus LTS.
<schwarz_Kat>
The fix disables tx offload by running '/usr/sbin/ethtool -K lan0 tx off' via a file in /etc/udev/rules.d.
<schwarz_Kat>
Any reason that I shouldn't do the fix in config/sources/families/include/rockchip64_common.inc where the ethernet name is changed for those same SBC's via /etc/udev/rules.d and applied to all versions?
<schwarz_Kat>
I encounter the bug on Orange Pi R1plus LTS.
schwarz_Kat has left #armbian [Offline]
darsie has joined #armbian
schwarz_Kat has joined #armbian
<stipa>
sounds more like a nasty hack then a fix
<stipa>
but if the driver is a blob there's not many other alternatives to do it
<stipa>
oh, right, i have that usb nic too
<stipa>
last time i used it it was overheating in 1000 Mbs mode
<stipa>
doing practically nothing
<stipa>
i had to run it on 100Mbs if i wanted it cool
qqqhhh8611 has joined #armbian
qqqhhh861 has quit [Ping timeout: 276 seconds]
qqqhhh8611 is now known as qqqhhh861
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 246 seconds]
samythemany1 has quit [Remote host closed the connection]
samythemany1 has joined #armbian
argonautx has quit [Quit: Leaving]
amazingfate has joined #armbian
amazingfate_ has quit [Ping timeout: 256 seconds]
<binarym>
schwarz_Kat: months ago despite using this fix, i continue getting this my lan NIC hanging. The only way to get this work was to downgrade the driver
DarkG has quit [Excess Flood]
DarkG has joined #armbian
amazingfate_ has joined #armbian
amazingfate has quit [Ping timeout: 246 seconds]
lsafelix has joined #armbian
<lsafelix>
hello
schwarz_Kat has quit [Ping timeout: 276 seconds]
<lsafelix>
im having problem to compile image for orangepi lite .. this is this right channel?
martinayotte has joined #armbian
<lsafelix>
i m agetting this error during compile.sh
<lsafelix>
drivers/power/supply/axp20x_battery.c:292:10: error: implicit declaration of function ‘axp20x_get_ocv_voltage’; did you mean ‘axp20x_battery_get_max_voltage’? [-Werror=implicit-function-declaration]
<lsafelix>
drivers/power/supply/axp20x_battery.c:307:7: error: ‘info’ undeclared (first use in this function); did you mean ‘int’?
<lsafelix>
cc1: some warnings being treated as errors
<BigShip>
Hello! I built a jammy stable image successfully ,but after booting and logging in, it displays a warning on the log in screen about it having been built from Trunk.
<BigShip>
Is there a way for me to build a Jammy stable image without running into any issues updating later?
argonautx has joined #armbian
archetech has joined #armbian
glsorre has quit [Quit: You have been kicked for being idle]
craigevil has joined #armbian
amazingfate has joined #armbian
<Armbian-Discord>
<Werner> Trunk just means that the built is unsupported. Updates will work normally
amazingfate_ has quit [Ping timeout: 272 seconds]
<BigShip>
Oh, okay cool! Thank you
emanuele-f has joined #armbian
amazingfate_ has joined #armbian
BigShip has quit [Quit: Client closed]
amazingfate has quit [Ping timeout: 246 seconds]
BigShip has joined #armbian
archetech has quit [Quit: Konversation terminated!]
lemonzest has quit [Quit: WeeChat 3.4]
archetech has joined #armbian
argonautx has quit [Quit: Leaving]
<stipa>
lsafelix: which board mate?
<Armbian-Discord>
<Werner> seems like orangepi lite
<stipa>
"axp20x.h - Arduino library for X-Power AXP202 chip."
<stipa>
:S
abws has quit [Ping timeout: 272 seconds]
cheakoirccloud has quit [Quit: Connection closed for inactivity]
<ArmbianHelper>
^ Building Armbian - Armbian Documentation
<emanuele-f>
Reporting issues with the current nanopi neoplus 2 kernel. Too lazy to open a bug report, but issues include kernel crashes, long ssh transfers breaking and apt reporting invalid keys. So it seems something linked to encryption. Migrated to legacy kernel and it works great
<stipa>
emanuele-f: better report that as a bug otherwise it'll stay a bug forever
<emanuele-f>
I know, but the problem is that it runs "in production" so rolling back to buggy kernel to prodivde info can lead to data loss. Will open a bug with minimal info maybe
<ArmbianHelper>
^ nanopi neo plus2 weird issues and kernel oops with current kernel - Allwinner A64, H5, H6 and H616 - armbian forum
BigShip has left #armbian [#armbian]
sunshavi has quit [Ping timeout: 276 seconds]
sunshavi has joined #armbian
<steev>
emanuele-f: can you provide more info than that? like logs?
<emanuele-f>
steev: For that I need to switch back, even apt history file is now flushed (on reboot?)
<steev>
you have a device in production that you don't keep actual logs for?
<emanuele-f>
It should be quite easy to reproduce for anyone running the board on a daily basis
<emanuele-f>
steev: well, I'm reporting this bug to help the community as the board is running fine now for me, I've provided all the info I have, now it's up to you to investigate or close the issue
<c0rnelius>
Mine runs fine on straight Debian with 5.15.32. uptime 19 days currently. maybe its just a slip up in the kernel build?
amazingfate_ has joined #armbian
<c0rnelius>
although I do recall earlier versions of that LTS did create problems for the board. Kind of like what you described.
<emanuele-f>
Oh, I didn't know debian supported the board
<c0rnelius>
I don't know that they do, I just debootstraped it to life and built the uboot and kernel.
<emanuele-f>
c0rnelius: ok I see
<emanuele-f>
c0rnelius: it may be a bug in kernel config/patches or a bug in the kernel. But this board went end of life and I think no many people use it
amazingfate has quit [Ping timeout: 276 seconds]
<c0rnelius>
H5 in general is EOL I thought? and yeah its a solid board.
<c0rnelius>
I only patch a few things on the kernel for it. mostly everything is already in place really.
<emanuele-f>
c0rnelius: yep
<archetech>
c0rnelius, hey
<c0rnelius>
archetech: hows it going?
<archetech>
good ever try arch/manjaro on your boards
<c0rnelius>
only on x86_64
<archetech>
so ya stick to debian /ubu ?
<c0rnelius>
which sadly only lasted for like a year and half as after updates things would stop working. so I gave up.
<archetech>
ya arch needs regular attn
<emanuele-f>
Some years ago I used to run archarm on the raspberry but it broke different times during updates, I don't know if this is still the case
<c0rnelius>
generally, yes. i have played around with other distros on arm board. CRUX, OpenSUSE and Void. but getting them going using a debian based OS tends to be super easy.
<c0rnelius>
boards*
<c0rnelius>
CRUX is kind of a slug-fest, which is why I stopped doing that on arm. OpenSUSE is bloated and Void is just... Void. Good OS but takes effort.
<c0rnelius>
I've also messed with Fedora too, but I wasn't impressed.
<archetech>
ive got n2 with deb bookworm-lxqt its nice guess deb is for the install and forget types of peeps
<archetech>
but bworm id dev so it changes freq
<archetech>
id/is
<c0rnelius>
yeah I've played with it. It will be in flux for a long time to come.
<archetech>
how they roll ya
<c0rnelius>
Debian is indeed the lazy persons arm OS of choice I find.
<c0rnelius>
Usually have to do something pretty stupid to break it. "Usually".
<archetech>
that and its def not gonna break as much as a cutting edge arch
<archetech>
arch devs fix stuff fast I find
<c0rnelius>
indeed. i tried to like arch and gave it a fair chance. but I'm to old to care about holding its hand all the time.
<archetech>
depnds on your level of tolerance I guess it rearely breaks for me
<c0rnelius>
when I started using Linux 20 something how ever many years ago, I really disliked Debian and would generally use Slackware, CRUX and the BSD's. As I liked the level of control they gave me, but I find as time goes by I'm lazy :)
<archetech>
I still enjoy LFS and arch for the bleeding edge fun
<c0rnelius>
My problem with Arch and Manjaro is the instability and level of breakage that occurs. Its just obscene.
<archetech>
I dont run many apps I just cant relate ive heard what ya sayin but never experienced it
<c0rnelius>
I've never actually used LFS. oddly.
<archetech>
gentoo?
<c0rnelius>
nope
<c0rnelius>
I was a CRUX / BSD fella
<archetech>
source based is where im happy
<archetech>
call it control but its more just so darn fresh
<archetech>
and fast
<c0rnelius>
Thats what attracted me to CRUX. It was source based for the most part but was very much like the BSDs.
<c0rnelius>
edit a conf file and done.
<c0rnelius>
simples
<archetech>
yup and lean just what ya need
<c0rnelius>
yea
<c0rnelius>
you getting that new VIM?
<archetech>
tenkawa was sayin he works withyou some project
<archetech>
I use nano
<c0rnelius>
He's never mentioned it, but I wouldn't be surprised.
<c0rnelius>
oh I read that wrong
<c0rnelius>
no he tests shit for me
<archetech>
ah
<c0rnelius>
and bugs me to get things working on boards he has that I don't :)
<archetech>
you lookin at any new stuff comin out soon
<archetech>
like rock5b
<c0rnelius>
I am but I'm in no rush to get it. I was thinking the radxa zero2 next.
<c0rnelius>
hopefully they practice better quality control on that board. The radxa zero rev 1.5 is super hit and miss.
<archetech>
ya thats a neat board
<archetech>
catcha later gotta get some grub
<c0rnelius>
ok
<emanuele-f>
<c0rnelius> "My problem with Arch and Manjaro..." <- I run arch on a daily basis (x86_64) and it works reliably. The advantage over debian is that you always have fresh package versions. Being a rolling release with a huge user base, issues are identified and fixed promptly, as people have the same versions of software installed, so any bug affects everyone
<emanuele-f>
So as long as you update regularly, you should not face problems
<c0rnelius>
emanuele-f: My experience with it was, after updates "happened more than 3 times" my PC wouldn't boot anymore. After getting back into it and fixing the problem, by the 3rd time I was just like... forget it.
<c0rnelius>
Maybe I was doing something wrong? I have no clue now it was kind of a whiles ago.
<emanuele-f>
c0rnelius: in which part it was broken? kernel, graphics?
<c0rnelius>
I've met lots of people who love Arch.
<c0rnelius>
kernel
<emanuele-f>
c0rnelius: that's weird, I only experienced a kernel issue once in I think 8 years of arch
<c0rnelius>
maybe I was just unlucky? i don't feel like I'm missing out.
<c0rnelius>
bleeding edge every second of every day isn't that important to me.
<emanuele-f>
c0rnelius: maybe your hw was not properly supported by the kernel, breaking bugs should not even reach a kernel release. Anyway, arch also provides lts releases if you want full stability
<emanuele-f>
c0rnelius: for me it's like being always stable, I used debian in the past and upgrading major release was a pain with high probability of breakage
<c0rnelius>
that is possible. my main PC isn't that amazing and was once a college office computer :)
<emanuele-f>
also packages were too old so I had to use sid, which was constantly broken
amazingfate has joined #armbian
<emanuele-f>
lts kernel* (not release xD)
<c0rnelius>
as for Debian I've experienced the same thing. dist-upgrades usually don't work, but I will say going from Buster to Bullseye was painless.
<Armbian-Discord>
<MiAutomations> Hello it's possible to install the armbian into a box tanix X4 with the CPU Amlogic S905X4? Thank you
<ArmbianHelper>
^ ArmBian Tanix_X4-S905X4 - Amlogic CPU Boxes - armbian forum
<c0rnelius>
seems like a nice SoC. to bad its in a tv box.
<steev>
yes, debian's kernel supports the nanopi neo plus2, and their u-boot-sunxi also supports it
<steev>
emanuele-f: i'm not an armbian dev, but the point in providing logs is so that, if for example one CAN'T reproduce the issue, you can look at the logs on the box that it does happen on
<c0rnelius>
steev: looks like fdtoverlay support in u-boot v2022.04 works out of the box in allwinner, rockchip and amlogic.
<steev>
hype
<emanuele-f>
steev: ok, issues need motivation to be troubleshooted and fixed, I've contributed as I can based on my motivation on this subject, hope it's enough to bring up the problem and fix it
<c0rnelius>
in my latest testing. nothing special required.
<steev>
emanuele-f: if i see it happen on my neoplus2, i might try to look into it, but since mine are rock solid... *shrug*
<emanuele-f>
steev: try with long ssh transfers (e.g. 5 GB)
<steev>
when i circle back around to it, maybe
<emanuele-f>
yep, I'm not rolling back to the buggy kernel to test this, sorry for this
phenom has quit [Ping timeout: 260 seconds]
phenom has joined #armbian
lsafelix has quit [Read error: Connection reset by peer]