<f00b4r0>
robimarko: thanks. The context is completely lost in the current patch (which was poorly formatted to begin with). But I wonder if we should still carry this hack, considering that ATU violations handling code has been improved upstream, according to a quick google search
<ynezz>
grift: thanks for heads up about that busybox login applet fix with SELinux https://github.com/openwrt/openwrt/pull/19080 (I've included there the selinux-policy v2.8.2 there as well)
n3ph_ has quit [Ping timeout: 480 seconds]
<enyc>
f00b4r0 nbd : Hrrm; any updates on that silly maybe hostapd-triggered slab-leak kernel-patches suspected, etc? I may be able to try to work out if particular devices or not; is it the sort of thing likely improved in newer kernel / 24.10.2 anyway?
<enyc>
Happy to *try* to help with a proper bug report, if that is needed/best.
SlimeyX has quit [Read error: Connection reset by peer]
goliath has quit [Quit: SIGSEGV]
SlimeyX has joined #openwrt-devel
lucas__ has quit []
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
goliath has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
danitool has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX_ has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
AtomiclyCursed has quit [Quit: ZNC 1.9.1 - https://znc.in]
SlimeyX_ is now known as SlimeyX
AtomiclyCursed has joined #openwrt-devel
sorinello has quit [Ping timeout: 480 seconds]
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX_ has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX_ is now known as SlimeyX
SlimeyX_ has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
<Moe1978>
I am quite motived (7/10) to get openwrt working on a RBSXTG-5HPacD-SA (mikrotik SXT SA5). This device is specifically not supported and I am aware of what this means. I read several threads at attempts at getting this device working, specifically found out that the RX/TX serial probe points are actually disconnected on the board - only after having soldered onto them and been frustrated in my attempt at dumping boot messages.
<Moe1978>
my question is: is there a sane approach to this for someone that has a solid motivation to get it done.
goliath has quit [Quit: SIGSEGV]
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
cmonroe has joined #openwrt-devel
xdarklight_ has joined #openwrt-devel
nixuser has quit [Ping timeout: 480 seconds]
xdarklight has quit [Ping timeout: 480 seconds]
SlimeyX_ has joined #openwrt-devel
SlimeyX has quit [Ping timeout: 480 seconds]
nixuser has joined #openwrt-devel
SlimeyX_ has quit [Read error: No route to host]
SlimeyX_ has joined #openwrt-devel
SlimeyX_ is now known as SlimeyX
nixuser has quit [Read error: Connection reset by peer]
nixuser has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
aiyion_ is now known as aiyion
SlimeyX has quit [Ping timeout: 480 seconds]
SlimeyX has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
SlimeyX_ has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]