Re: GTI Mirabox and Netgear RN120/RN104 (Armada 370) Installation & Kernel Upgrade (Linux-6.5.7) March 02, 2024 03:02PM |
Admin Registered: 13 years ago Posts: 18,821 |
root@HomeMedia1:~# cat /etc/debian_version 11.1 root@HomeMedia1:~# grep -i modules /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] # dep - Try and guess which modules to load. # netboot - Add the base modules, network modules, but skip block devices. # list - Only include modules from the 'additional modules' list MODULES=most
Re: GTI Mirabox and Netgear RN120/RN104 (Armada 370) Installation & Kernel Upgrade (Linux-6.5.7) March 02, 2024 03:10PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox and Netgear RN120/RN104 (Armada 370) Installation & Kernel Upgrade (Linux-6.5.7) March 03, 2024 02:57PM |
Admin Registered: 13 years ago Posts: 18,821 |
md5: a44771dd7d586d2171d9c68aeb19e96e sha256: d9e82ba31cf2ddc123aa882bee0dd4c4c05ab5095eccc7546c6c8d33fb9f100cThis tarball contains 5 files
linux-image-6.7.5-mvebu-370xp-tld-3_3_armhf.deb linux-headers-6.7.5-mvebu-370xp-tld-3_3_armhf.deb zImage-6.7.5-mvebu-370xp-tld-3 config-6.7.5-mvebu-370xp-tld-3 linux-dtb-6.7.5-mvebu-370xp-tld-3.tar
Re: GTI Mirabox and Netgear RN102/RN104 (Armada 370) Installation & Kernel Upgrade (Linux-6.5.7) March 03, 2024 03:55PM |
Registered: 7 years ago Posts: 181 |
$ uname -a Linux rn102 6.7.5-mvebu-370xp-tld-3 #1 SMP PREEMPT Thu Feb 29 19:03:59 PST 2024 armv7l GNU/Linux $ cat /etc/debian_version 12.4 $ ssh rn102 date -R && sleep 300 && ssh rn102 date -R Sun, 03 Mar 2024 22:41:39 +0100 Sun, 03 Mar 2024 22:46:14 +0100So the rn102's system clock lagged 25 seconds in 5 minutes. That's 5 seconds per minute.
Re: GTI Mirabox and Netgear RN102/RN104 (Armada 370) Installation & Kernel Upgrade (Linux-6.5.7) March 03, 2024 04:18PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.7.5) March 13, 2024 06:23PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.7.5) March 19, 2024 05:30PM |
Admin Registered: 13 years ago Posts: 18,821 |
halt -d -f $netdown $poweroff $hddown
halt -d -f $poweroff $hddown
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 21, 2024 02:47PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 22, 2024 01:54PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 27, 2024 11:59AM |
Registered: 7 years ago Posts: 181 |
[ 28.050207] BUG: scheduling while atomic: mdadm/1710/0x00000002
$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 1.8T 0 disk `-sda1 8:1 1 1.8T 0 part `-md0 9:0 0 1.8T 0 raid1 /home sdb 8:16 1 1.8T 0 disk `-sdb1 8:17 1 1.8T 0 part `-md0 9:0 0 1.8T 0 raid1 /home sdc 8:32 0 149.1G 0 disk `-sdc1 8:33 0 149G 0 part / mtdblock0 31:0 0 1.5M 0 disk mtdblock1 31:1 0 128K 1 disk mtdblock2 31:2 0 6M 0 disk mtdblock3 31:3 0 4M 0 disk mtdblock4 31:4 0 116M 0 disk $
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 27, 2024 04:13PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102
[ 0.000000] Unknown kernel command line parameters "reason=normal bdtype=rn102", will be passed to user space.
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 28, 2024 02:03AM |
Registered: 7 years ago Posts: 181 |
$ sudo fw_printenv | egrep -i 'bootcmd=|sata_set_bootargs=|sata_boot=|mtdparts=|load_uimage=|load_uinitrd=' | sort bootcmd=ide reset; run sata_bootcmd; reset load_uimage=ext2load ide 0:1 0x2000000 /boot/uImage load_uinitrd=ext2load ide 0:1 0x3000000 /boot/uInitrd mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) sata_boot=run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi sata_bootcmd=run sata_set_bootargs; run sata_boot sata_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial $
$ sudo fw_printenv | egrep -i 'reason|normal|bdtype|rn102' SKUNum=RN102 Startup=Normal
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 28, 2024 02:26PM |
Admin Registered: 13 years ago Posts: 18,821 |
sata_bootcmd=run sata_set_bootargs; run sata_boot sata_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial
> $ sudo fw_printenv | egrep -i > 'reason|normal|bdtype|rn102' > SKUNum=RN102 > Startup=Normal >>
[ 3.184866] 5 fixed-partitions partitions found on MTD device pxa3xx_nand-0 [ 3.191969] Creating 5 MTD partitions on "pxa3xx_nand-0": [ 3.197597] 0x000000000000-0x000000180000 : "u-boot" [ 3.206874] 0x000000180000-0x0000001a0000 : "u-boot-env" [ 3.215802] 0x000000200000-0x000000800000 : "uImage" [ 3.225242] 0x000000800000-0x000000c00000 : "minirootfs" [ 3.234744] 0x000000c00000-0x000008000000 : "ubifs"
mtdparts=mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)But currently you cannot set env in Debian using fw_setenv, because the envs are read-only in the DTB definition.
setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)'
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 28, 2024 04:57PM |
Registered: 7 years ago Posts: 181 |
[ 1.990632] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.000817] debugfs: Directory 'd0018100.gpio' with parent 'regmap' already present! [ 2.010570] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.020570] debugfs: Directory 'd0018140.gpio' with parent 'regmap' already present! [ 2.029418] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 6.393683] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead. [ 6.406327] mtdblock: MTD device 'uImage' is NAND, please consider using UBI block devices instead. [ 6.420679] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead. [ 6.462804] mtdblock: MTD device 'minirootfs' is NAND, please consider using UBI block devices instead. [ 6.491866] mtdblock: MTD device 'ubifs' is NAND, please consider using UBI block devices instead. [ 23.088713] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead. [ 23.317898] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead. [ 23.404877] mtdblock: MTD device 'uImage' is NAND, please consider using UBI block devices instead. [ 23.484129] mtdblock: MTD device 'minirootfs' is NAND, please consider using UBI block devices instead. [ 23.590980] mtdblock: MTD device 'ubifs' is NAND, please consider using UBI block devices instead.
Marvell>> printenv mtdparts mtdparts=mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)and 'dmesg' by 'ssh':
[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 28, 2024 06:37PM |
Admin Registered: 13 years ago Posts: 18,821 |
> [ 0.000000] Kernel command line: > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 > mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) > earlyprintk=serial > mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) > reason=normal bdtype=rn102 >>
setenv mtdparts 'mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)' setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial'
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 29, 2024 01:45AM |
Registered: 7 years ago Posts: 181 |
Marvell>> printenv mtdparts sata_set_bootargs mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) sata_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial Marvell>> setenv mtdparts 'mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)' Marvell>> setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' Marvell>> printenv mtdparts sata_set_bootargs mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) sata_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial
[ 29.948156][ T110] BUG: scheduling while atomic: kworker/0:2/110/0x00000002
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) May 30, 2024 02:17PM |
Admin Registered: 13 years ago Posts: 18,821 |
QuoteMarvell>> printenv mtdparts sata_set_bootargs mtdparts=mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)
> The BUG message is back:
>> [ 29.948156][ T110] BUG: scheduling while > atomic: kworker/0:2/110/0x00000002 >
setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)' setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial'and then save it (for this boot, it is not necessary to save it, but for the next boot so it can be booted withtout interruption).
saveenv boot
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 06, 2024 02:02PM |
Registered: 7 years ago Posts: 181 |
[ 29.788241] BUG: scheduling while atomic: kworker/0:2/110/0x00000002 na. [ 30.028215] BUG: scheduling while atomic: kworker/0:2/110/0x00000002 [ 27.944406] BUG: scheduling while atomic: mdadm/1710/0x00000002 [ 27.628423][ T110] BUG: scheduling while atomic: kworker/0:2/110/0x00000002 (Got stuck here! Power cycle required to reset.) na. [ 29.948205][ T8] BUG: scheduling while atomic: kworker/0:0/8/0x00000002 [ 29.868228][ T110] BUG: scheduling while atomic: kworker/0:2/110/0x00000002 [ 29.948315][ T110] BUG: scheduling while atomic: kworker/0:2/110/0x00000002 (Got stuck here! Power cycle required to reset.) na.To me this looks like a race condition where the end result depends on small timing differences. It may (or may not) be related to the flaw in the system clock. I did not check if the real time clock will reset the box when it's stuck, but it would come as a surprise.
[ 3.310045][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing.and powered off the the box! The serial console output is attached.
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 06, 2024 02:47PM |
Admin Registered: 13 years ago Posts: 18,821 |
> [ 3.310045][ T1] mdio_bus d0072004.mdio-mii: > MDIO device at address 1 is missing. >
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 07, 2024 01:54PM |
Registered: 7 years ago Posts: 181 |
Quote
I think you might be right about the timing difference. I ran the new kernel on the Mirabox for a day, and saw no BUG.
Quote
So to confirm, if the bootargs is sane (no repeated mtdparts and other bad garbage), you don't see the BUG?
root@rn102:~# dmesg | grep mtdparts | fold -sw 80 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102I assume that $mtdparts is also reported twice on the serial console during boot, even though I don't see it. I assume 'minicom' truncates long lines.
stop_machine_cpuslocked+0x108/0x13c from patch_text+0x24/0x4c stop_machine_cpuslocked+0x108/0x13c from patch_text+0x24/0x4cThese messages are not present in the 'dmesg' output.
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 07, 2024 03:43PM |
Admin Registered: 13 years ago Posts: 18,821 |
setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' boot(I just don't like to see the kernel bootargs being messed up. Apparently, if you notice "reason=normal bdtype=rn102" looks like garbage that comes after the mtdparts env. This u-boot could have bug that when it resolved the $mtdparts it has read a longer string in memory).
Quote
mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@
0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial
mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@
0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal
bdtype=rn102
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 07, 2024 08:52PM |
Registered: 7 years ago Posts: 181 |
Quote
I just don't like to see the kernel bootargs being messed up.
root@rn102:~# dmesg | grep mtdparts | fold -sw 80 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102 root@rn102:~# dmesg | grep "scheduling while atomic" [ 29.788416] BUG: scheduling while atomic: kworker/0:2/110/0x00000002
[ 36.188439][ T110] BUG: scheduling while atomic: kworker/0:2/110/0x00000002
root@rn102:~# dmesg | grep mtdparts | fold -sw 80 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102 root@rn102:~# dmesg | grep "scheduling while atomic" [ 30.348387] BUG: scheduling while atomic: kworker/0:2/110/0x00000002
root@rn102:~# dmesg | grep mtdparts | fold -sw 80 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102 root@rn102:~# dmesg | grep "scheduling while atomic" [ 30.348387] BUG: scheduling while atomic: kworker/0:2/110/0x00000002
root@rn102:~# dmesg | grep mtdparts | fold -sw 80 [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn102 root@rn102:~# dmesg | grep "scheduling while atomic" root@rn102:~#
Quote
tme
When the line "BUG: scheduling while atomic" appears on the serial console (and later in the 'dmesg' output), it is always between 27 s and 30 s into the kernel boot.
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 07, 2024 10:11PM |
Admin Registered: 13 years ago Posts: 18,821 |
> [ 0.000000] Kernel command line: > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 earlyprintk=serial > mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@ > 0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) > reason=normal > bdtype=rn102
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 12, 2024 03:18PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 13, 2024 02:18PM |
Registered: 7 years ago Posts: 181 |
Quote
Have you seen this problem that Jugle is seeing with networkk receive buffer overrun?
tme@rn102:~$ uptime 19:45:39 up 5 days, 5:10, 2 users, load average: 0.00, 0.00, 0.00 tme@rn102:~$ dmesg | grep overrun tme@rn102:~$
[ 10.428258] BUG: scheduling while atomic: kworker/0:0/8/0x00000002
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.8.7) June 13, 2024 02:47PM |
Admin Registered: 13 years ago Posts: 18,821 |
>Quote
Have you seen this problem that Jugle is
> seeing with networkk receive buffer
> overrun?
> tme@rn102:~$ uptime > 19:45:39 up 5 days, 5:10, 2 users, load > average: 0.00, 0.00, 0.00 > tme@rn102:~$ dmesg | grep overrun > tme@rn102:~$ >>
Quote
[ 692.478184] mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
> [ 10.428258] BUG: scheduling while atomic: > kworker/0:0/8/0x00000002 >>
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.9.6) June 28, 2024 12:42AM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.9.6) June 30, 2024 04:46AM |
Registered: 3 months ago Posts: 16 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.9.6) June 30, 2024 03:00PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.9.6) July 01, 2024 07:04AM |
Registered: 3 months ago Posts: 16 |