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
<Macer>
pinebook pro is really crushing it with the nvme. should have gotten the adapter sooner
xispita has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
xispita has joined #armbian
johnjaye has quit [Read error: Connection reset by peer]
johnjaye has joined #armbian
norwich_ has joined #armbian
norwich has quit [Ping timeout: 260 seconds]
norwich_ is now known as norwich
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
lemonzest has quit [Quit: WeeChat 3.5]
lemonzest has joined #armbian
flyback has quit [Read error: Connection reset by peer]
ikmaak has quit [Read error: Connection reset by peer]
ikmaak has joined #armbian
lemonzest has quit [Ping timeout: 244 seconds]
lemonzest has joined #armbian
abws has joined #armbian
<abws>
I cannot send magic sysrq via serial console to my two armbian boxes . Is it disabled on purpose ? helios64 and odroid n2+
<abws>
I have another box with plain debian and magix sysrq from serial console works
<abws>
an odroid u2
<Armbian-Discord>
<ManoftheSea> does linux need to be told that a serial console is secure to make that work?
<abws>
how do you tell the kernel that a serial console is secure ?
<abws>
mind the serial console is listed in the kernel cmdline on all boxes (the ones that works and the ones that do not)
<abws>
"console=tty1 console=ttySAC1,115200n8" < works
<abws>
"console=ttyAML0,115200n8 console=tty1" and "console=ttyS2,1500000 console=tty1" <<< discards magic sysrq
<Armbian-Discord>
<ManoftheSea> I hoped you knew, since you're trying to use it.
<Armbian-Discord>
<ManoftheSea> look at /etc/securetty
<Armbian-Discord>
<ManoftheSea> ttySAC appears, ttyAML does not.
<Armbian-Discord>
<ManoftheSea> but then, so does ttySn, and the file itself just mentions it being useful for root. So, sorry, don't know
<abws>
well I see the console is set to secure on the armbian box but this file is not there on the box where the magix sysrq works
<abws>
I doubt /etc/securetty is related to the kernel
<abws>
kernel devs are strongly opposed to userspace files to setup the kernel
<abws>
this looks like /sbin/login related
<Armbian-Discord>
<ManoftheSea> then you know more than I od
<abws>
not that I know that much, just seen module devs being flamed for adding userspace files to tweaks their behavior
johnjaye has quit [Read error: Connection reset by peer]
<abws>
still I don't know much about armbian. I don't know what could prevent magic sysrq on the odroid n2+ serial console (it is exactly the same serial console HW on the armbian odroid n2+ that fails and on the debian odroid u2 that succeed)
<Armbian-Discord>
<ManoftheSea> Complete wild speculation: is there something in the kernel configuration that would tell you anything? Can you access that through... /proc or /sys?
<Armbian-Discord>
<ManoftheSea> I doubt it was intentionally done, and it's something that could be enabled with a PR
<abws>
grep MAGIC /boot/config* shows settings that matches on both odroids (armbian and debian)
alekksander has joined #armbian
Malditron has joined #armbian
<abws>
indeed it could be a bug in armbian. I am bothered about this breakage but this is less critical than getting the helios64 stable to me
<abws>
it affects both helios64 and odroid n2+ it is an armbian patch that is applied to all archs
<abws>
has anyone on any arch got serial console magic sysrq with armbian ?
<Armbian-Discord>
<ManoftheSea> you have a specific patch?
<Armbian-Discord>
<ManoftheSea> Do you know where to look for kernel configuration patches? In the armbian/build repo, it's generally going to be under patch/kernel/
qqqhhh8619 has joined #armbian
qqqhhh861 has quit [Ping timeout: 246 seconds]
qqqhhh8619 is now known as qqqhhh861
<abws>
thanks, yes I already tweaked a patch once
<abws>
Shouldn't I bugreport so the issue is not lost ?
<nekomancer[m]>
sure!
<nekomancer[m]>
<abws> "thanks, yes I already tweaked..." <- what was wrong?
alekksander has quit [Quit: Konversation terminated!]
<abws>
emmc hs400 breakage . hs400 is disabled since a year. I bisected the wrong upstream commit and ended up finding the fix was not wrong but caused the regression
<nekomancer[m]>
😱
<abws>
I never bug report uptream linux though , maybe they would have found out (the order they init the regulator ends up breaking emmc hs400 on at least a few rockchip 3399 boards
<abws>
but I am uneasy bugging upstream, armbian has too many diffs