<nlowe>
For those editing 4K footage and backing it up/transferring it around, makes perfect sense
<pkgadd>
I do regularly transfer files in the ~150 GB range over the network
<Borromini>
guys, the LEDs on my R6800 don't seem to do anything... how do i 'tickle' them?
<Borromini>
/sys/class/leds/ only has mt76 phy0/phy1 entries
<dorf_>
I use the Luci app to tickle leds.
<Borromini>
the predefined white:lan1/lan2/... ones in /sys/bus/platform/devices/leds/of_node/ have a file 'gpios' that's empty
<Borromini>
dorf_: that's not working here :(
<Borromini>
first thing i tried too.
<dorf_>
hmm
<Borromini>
it's very weird. LAN2 is on now, now that there's a loose cable inserted (...)
<dorf_>
what if you set the discovered leds' default state to on, Borromini?
<dorf_>
just to see if anything responds..
<Borromini>
when it had a device on the other end, it was off >_>
<Borromini>
sec
<dorf_>
the other thing to try in luci is adding an led action to any and every led that's not explicitly referenced in the UI (there are probably a bunch of unmapped dummy leds there)
<Borromini>
yeah, but the led name is a dropdown menu that basically only shows the phys
<Borromini>
which is a bit eird
<Borromini>
* weird
<Borromini>
even the predefined lan leds fall back to the phy ones when you edit them >_>
<dorf_>
I've noticed some weirdness with editing, as an aside. Here the configs save fine, work ok, but a router reboot resets them until you tweak a single led def, and then the previously saved configs kick in.
<Borromini>
ok
<Borromini>
are you on master or 19.07?
<dorf_>
19.07.04
<Borromini>
ok
<Borromini>
hmmm.
<Borromini>
it looks like someone tore out the whole led code from the r6800 dts in master.
<Borromini>
ok into a dtsi, so that shouldn't be an issue. weird.
<Borromini>
anyway... way past bedtime. goodnight!
Borromini has quit [Quit: leaving]
cfactory has quit [Remote host closed the connection]
swex has joined #openwrt-devel
nlowe has quit [Quit: Leaving]
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]
bkallus has quit [Remote host closed the connection]
Tost has quit [Ping timeout: 240 seconds]
heffer has joined #openwrt-devel
dorf_ has quit [Remote host closed the connection]
dorf_ has joined #openwrt-devel
luke-jr has quit [Ping timeout: 272 seconds]
luke-jr has joined #openwrt-devel
dorf_ has quit [Remote host closed the connection]
dorf_ has joined #openwrt-devel
shibboleth has quit [Quit: shibboleth]
Misanthropos has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
hbug has quit [Ping timeout: 240 seconds]
Misanthropos has joined #openwrt-devel
victhor_ has quit [Ping timeout: 264 seconds]
vpelletier has joined #openwrt-devel
DragoonAethis has quit [Quit: hej-hej!]
tobleminer-tSYS has quit [Quit: AS4242423214]
tobleminer-tSYS has joined #openwrt-devel
luke-jr has quit [Ping timeout: 264 seconds]
DragoonAethis has joined #openwrt-devel
luke-jr has joined #openwrt-devel
<vpelletier>
hello openwrt devs. I have one request from my very fresh experience with sysupgrade: would it be possible to backup installed packaged list when sysupgrade is running, similarly to how /etc/config is backed up ?
<pkgadd>
-k include in backup a list of current installed packages at /etc/backup/installed_packages.txt
<vpelletier>
in my specific case, I enable dnssec, which requires dnsmasq-full, which means that after a sysupgrade I do not get a working udhcpd (for which I have mixed feelings: on the one hand I would not like dnssec to silently not be checked, but OTOH having no dhcp at all is annoying...) and I realised I was not sure what I had installed before
<vpelletier>
mmh... any reason this is not enabled by default ?
goliath has quit [Quit: SIGSEGV]
<vpelletier>
I am also playing with "opkg extra" which seems to do what I would expect (dump installed packages in /etc/config and allow installing them after an upgrade)
hbug has joined #openwrt-devel
Tapper has quit [Ping timeout: 240 seconds]
Acinonyx has joined #openwrt-devel
Acinonyx_ has quit [Ping timeout: 246 seconds]
woodst0ck has quit [Read error: Connection reset by peer]
MichaelOF has quit [Ping timeout: 260 seconds]
MichaelOF has joined #openwrt-devel
rsalvaterra1 has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 264 seconds]
dorf has joined #openwrt-devel
dorf_ has quit [Remote host closed the connection]
valku has quit [Quit: valku]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
dorf_ has joined #openwrt-devel
dorf has quit [Ping timeout: 246 seconds]
damex_ has joined #openwrt-devel
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 264 seconds]
damex has quit [Ping timeout: 272 seconds]
damex_ has quit [Read error: Connection reset by peer]
damex has joined #openwrt-devel
damex has quit [Read error: Connection reset by peer]
damex has joined #openwrt-devel
Tapper has joined #openwrt-devel
SimJoSt has quit [Quit: WeeChat 2.9]
opal has quit [Ping timeout: 240 seconds]
opal has joined #openwrt-devel
Tapper has quit [Ping timeout: 240 seconds]
Tapper has joined #openwrt-devel
ivanich has joined #openwrt-devel
<aparcar[m]>
nbd: can you help me 5 minutes with makefile magic?
<bkallus>
I'm trying to port OpenWrt to the Actionte MI424WR Rev. I. It has an avanta CPU and there's an existing build of PandoraBox (an openwrt fork) for it. I'm looking at the kernel config file for that build, and it's for 3.18. Does anyone know what types of changes I'll have to make to make that config file compatible with 5.4?
bkallus21 has quit [Client Quit]
<plntyk>
bkallus, check if the avanta cpu (its a marvell?) is compatible with some other arch and kernel config - currently there seem to be no similar architecture with openwrt
<plntyk>
check if there is even mainline support for that cpu
<bkallus>
Thanks for that. How did they get the 3.14 and 3.18 kernels working then?
<bkallus>
according to their device tree files it should be compatible with marvell,kirkwood-88f6282
PaulFertser has joined #openwrt-devel
<plntyk>
the vendor (Marvell) provides a software package (BSP) - Board Support Package that normally includes a heavily patched kernel / or even a "ready to use" build system with a kernel
dedeckeh has quit [Quit: Connection closed]
<plntyk>
the code is public and gpl v2 but often the low code quality means it cannot be integrated in mainline linux kernel
<plntyk>
"someone" has to cleanup , test and submit it to mailing list where kernel development happens
<plntyk>
bkallus, the marvel readme says that kirkwood cpus are supported and iirc run fine in mainline - but they dont use device tree - i doubt that a kirkwood image / kernel will boot but you could try
<plntyk>
also: that cpu is armv5
<plntyk>
thats really "bad" - because many systems use armv7 or armv8 - so armv5 has not a large userbase
<bkallus>
Thanks. Do you know where I can find that board support package? I don't see anything on Marvell's website and searching doesn't come up with anything. I also don't see anything on their github
dorf has joined #openwrt-devel
<bkallus>
i tried booting a kirkwood image but it didn't get past uncompressing the kernel. should I try to boot other kirkwood images or will they not work as well?
<plntyk>
most "BSP" are for "customers" aka manufacturers of devices - the "GPL" with source code publishing does not mean you could have "all" the BSP - and the device with "gpl software" was probably not sold by marvell itself so marvell does not have to give you anything
<plntyk>
some cpu / board vendors publish their bsps / kernels - some have a more "hands on" approach
dorf_ has quit [Ping timeout: 246 seconds]
<bkallus>
got it. so how do you think the people at pandorabox built a 3.14 kernel for this device? it ships with a 2.x kernel and never was updated past that afaik
<plntyk>
actionte (?) should provide the kernel source since its selling / distributing those devices
<plntyk>
some "leaked" kernel (github?) / other manufacturer with marvel devices that had a 3.14 bsp .. dunno
<plntyk>
if you do a diff from vanilla 3.14 to vendor 3.14 you probably will end up with 1000s of diffs - and depending on your skill one might hack sth. - especially if some configs / registers / cpu behaviour is very similar
<bkallus>
i built all of them and they all produced a working GPL OpenRG image except the most recent 2, both of which hang after uncompressing the kernel
<bkallus>
To be clear, what you're saying is that if I don't have a leaked bsp for the 88f6560, I'm not going to be able to build a 5.4 kernel, even with the pandorabox imagebuilder, and even though the dts says the 88f6560 is compatible with the 88f6282 (given that the mi424wr can't boot the kirkwood images)
<plntyk>
yes - the pandorabox source code aka sourcecode of their openwrt fork should contain the links / sources how to make an image - but i think you failed to find the source code of that too ?
<plntyk>
bkallus, ? i did some google foo - seems that 88f6560 can boot kirkwood partially - see https://forum.doozan.com/read.php?2,78499,78559
<plntyk>
debian with 4.12 kernel
<bkallus>
wow! that is big news
<bkallus>
amazing find
<bkallus>
I guess I'm not sure if they distributed their sources. The only pandorabox sources I can find are from before they added support for avanta. I'm still working on getting the imagebuilder and sdk they distribute to work. Right now I'm getting make errors
kontaxis has joined #openwrt-devel
black_ant has quit [Ping timeout: 246 seconds]
<plntyk>
so if a 4.12 kernel is running from debian (it seems to use the sheevaplug dtb that is "compatible enough" to boot) - and the other thread there mentions 5.2 https://forum.doozan.com/read.php?3,112689,112764#msg-112764
<plntyk>
one could try to use a debian kernel with openwrt userspace for example or modify the openwrt kernel config of kirkwood target to match debian/doozan
Tost has joined #openwrt-devel
rmilecki has quit [Ping timeout: 246 seconds]
ivanich has joined #openwrt-devel
<bkallus>
Could we use the dtb from pandorabox? That one is based on the linksys ea4500 (kirkwood). I think I will take a shot at adapting those config files. I also have the 3.14 and 3.18 kernel configs from pandorabox, but I'm not sure how helpful those will be. Do you have any tips for telling which config flags are preventing the device from booting? I'm eager to contribute to this project, and I have a decent amount of experience with C and asm, but I
<bkallus>
haven't done any kernel development at all. Do you have any suggestions for resources I should look at?
<bkallus>
I assumed the kernel config would differ between avanta and kirkwood. Are you saying I shouldn't have to make any changes at all?
<plntyk>
bkallus, you should do some stuff with serial console like post the printenv bootloader (u-boot) into the openwrt wiki - compare it to the doozan forum post (should be the same except maybe for mac address)
<plntyk>
since kirkwood on debian booted fine - expections might be that kirkwood w. openwrt might work fine too
dorf_ has joined #openwrt-devel
<mangix>
bkallus: sounds like it should be possible
<mangix>
kirkwood is an older design so avanta should have backwards compatibility
<plntyk>
bootloader help command + doozan result seems to indicate test - booting from usb should work - so experimentation is easier
<plntyk>
see "usb" "usbboot" fatload extload commands
dorf has quit [Ping timeout: 256 seconds]
<bkallus>
How should I format a usb drive? Just stick a uimage on it, or some dd-ing, or something else?
<plntyk>
usb drive should be 2 partitions : 1 fat32, 1 ext2
<plntyk>
1 ext2 should work too
<bkallus>
what should I put in that partition?
<bkallus>
will any image I can boot with tftpboot work?
<plntyk>
tftpboot might work too if you configure the network right -
<bkallus>
I already have tftpboot set up so I think I'll stick with that
<plntyk>
help tftpboot or tftpboot help should output params iirc
<plntyk>
with doozan / debian /openwrt you have the roofs , and then in the u-boot bootload you just test via ext2load usb.0 /boot/kernelimage 0x<address>
<plntyk>
the kernelimage, uinit/initramfs and then run "bootm" or so - like the log from doozan - it has the bootloader commands there
bkallus_ has joined #openwrt-devel
bkallus has quit [Ping timeout: 264 seconds]
dangole has quit [Remote host closed the connection]
bkallus__ has joined #openwrt-devel
bkallus_ has quit [Ping timeout: 260 seconds]
Tost has quit [Ping timeout: 260 seconds]
ivanich has quit [Quit: Konversation terminated!]
<bkallus__>
so just trying to boot a kirkwood initramfs uimage doesn't work. Hangs at "Starting kernel ...". Do you have any suggestions for other images to try? I'm assuming I need to compile with the avanta (or i guess sheevaplug) dtb for it to work.