GTI Mirabox, Netgear RN102/RN104, Netgear RN2120 Installation & Kernel Upgrade (Linux-6.13.8)

Hi Trond,

OK. Let me take a look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

Those options would also apply to the Kirkwood kernel for NETGEAR ReadyNAS NV+ v2 as well.

Ray

Hi Ray,

> Those options would also apply to the Kirkwood
> kernel for NETGEAR ReadyNAS NV+ v2 as well.

It's a bit late for Kirkwood kernel. Please make sure you boot up your ReadyNAS NV+ v2, pos tthe boot log, and make the request before next kernel release.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

Not a problem for me a I usually build my own kernels using your patches. Just thought it would be helpful to have the config options there for any current or future users of your kernel packages who might be using with that device.

Ray

Hi Trond,

> I checked. Contrary to what I believed,
> 'ide-disk1' and 'ide-disk2' work perfectly on the
> RN102. Sorry for my confusion!

So for the RN104. Does disk-activity trigger cause all 4 LEDs to flash when only one HDD is accessed?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Trond,

Here is the next kernel build (release version). Please try the LCD.

UPDATED: Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 3 time(s). Last edit at 01/28/2023 06:49PM by bodhi.

Hi bodhi,

Today I upgraded both my RN102s to Linux 6.1.8. No issues. 'dmesg' outputs attached. Thanks!

I currently do not have access to my RN104 box, but I'll upgrade it in a few weeks time.

Regards,
Trond Melen

Kernel linux-6.1.8-mvebu-370xp-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

My Netgear RN104 has been upgraded to your latest Linux kernel 6.1.8 for Armada 370XP. No issues. Boot log attached. Thanks!

I can't find anything about it in the boot log, but the 16 by 2 character LCD display is now supported. It says "Linux-6.1.8-mveb" for about 3 seconds early in the boot process. Then it turns dark until it says "Power off." for about 1 second just before the box is shutting down. I've not yet figured out how to make it show anything else on the display, but I've posted my findings.

The LED indicators for the disk bays can be turned on and off through the states 'default-on' and 'none'. For the RN102 they can indicate disk activity in the corresponding bay through the states 'ide-disk1' and 'ide-disk2', but this fails for the RN104. 'ide-disk1' and 'ide-disk2' do not work, and 'ide-disk3' and 'ide-disk4' are not defined. Selecting 'disk-activity' make all 4 LEDs indicate activity on the SSD connected to the eSata port, so you're close!

To avoid the system clock lagging, it still must be synchronized with the RTC every minute using 'crontab'. 'sleep 600' finishes in 10:55 minutes independently of the system clock:

tme@rn104:~$ sudo crontab -l | tail -1
#* * * * * /sbin/hwclock -s

tme@rn104:~$ ssh root@router date; sleep 600; ssh root@router date;
Sat Feb 11 08:46:58 CET 2023
Sat Feb 11 08:57:53 CET 2023

tme@rn104:~$ sudo crontab -l | tail -1
* * * * * /sbin/hwclock -s

tme@rn104:~$ ssh root@router date; sleep 600; ssh root@router date;
Sat Feb 11 08:59:02 CET 2023
Sat Feb 11 09:09:57 CET 2023

I'm uncertain if this indicates that the RN102/RN104 is under-clocked so that the CPU performance is degraded. When requested to generate 2 GiB of random numbers and dump them, the box overestimates it's own performance:

tme@rn104:~$ ssh root@router date -uR; echo -ne '\a'; dd if=/dev/urandom of=/dev/null bs=32k count=65536; echo -ne '\a'; ssh root@router date -uR
Sat, 11 Feb 2023 10:07:45 +0000
65536+0 records in
65536+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 59.5075 s, 36.1 MB/s
Sat, 11 Feb 2023 10:08:51 +0000

Since it finishes in about 66 s on a wall clock (in my case the router's clock) rather than 59.5 s on it's own clock, the actual data rate is about 32.5 MB/s rather than 36.1. How many seconds does you Mirabox spend on the same task?

Regards,
Trond Melen

EDIT: Typos only. :TIDE



Edited 2 time(s). Last edit at 02/11/2023 10:39AM by tme.

Hi Trond,

> I can't find anything about it in the boot log,
> but the 16 by 2 character LCD display is now
> supported. It says "Linux-6.1.8-mveb" for about 3
> seconds early in the boot process. Then it turns
> dark until it says "Power off." for about 1 second
> just before the box is shutting down. I've not yet
> figured out how to make it show anything else on
> the display, but I've posted my
> findings.

Please see my comments in that thread.

> The LED indicators for the disk bays can be turned
> on and off through the states 'default-on' and
> 'none'. For the RN102 they can indicate disk
> activity in the corresponding bay through the
> states 'ide-disk1' and 'ide-disk2', but this fails
> for the RN104. 'ide-disk1' and 'ide-disk2' do not
> work, and 'ide-disk3' and 'ide-disk4' are not
> defined. Selecting 'disk-activity' make all 4 LEDs
> indicate activity on the SSD connected to the
> eSata port, so you're close!

OK I think we can try to control the RN104 2 LEDs the same way with the RN102 to see if works. I'll compile another DTS to set it in the defautl trigger.

Now I think it's the time for me to patch that part of the kernel again to support 4 HDD LEDs. I did not bother to do that since nobody has requested 4 triggers :) And I don't have any 4-bay NAS (no need to).

> RN102/RN104 is under-clocked so that the CPU
> performance is degraded.

I also briefly thought about this. But if it was not up to the spec, then Marvell would have downgraded it to the next processor speed, as in we have the same Kirkwood SoC but CPU is 1Ghz, 1.2Ghz, ...

This one is spec at 1.2Ghz. I wonder if there is a way to underclock it to 1.Ghz.

In the Wiki thread, there was some example with the Pogo V4 where people over clock the chip

Quote

Overclock

Overclock the Pogo V4/Mobile to 1Ghz
Pogo V4/Mobile overlocked with USB2TTL adaptor
Pogo V4/Mobile overlocked with no resistor needed

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 02/11/2023 04:38PM by bodhi.

> Now I think it's the time for me to patch that
> part of the kernel again to support 4 HDD LEDs. I
> did not bother to do that since nobody has
> requested 4 triggers :) And I don't have any 4-bay
> NAS (no need to).

I think if I will work on this, it will be a different patch altogether (do it in a proper way, not a hack as I did from way back).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Trond,

> I'm uncertain if this indicates that the
> RN102/RN104 is under-clocked so that the CPU
> performance is degraded. When requested to
> generate 2 GiB of random numbers and dump them,
> the box overestimates it's own performance:
>

> tme@rn104:~$ ssh root@router date -uR; echo -ne
> '\a'; dd if=/dev/urandom of=/dev/null bs=32k
> count=65536; echo -ne '\a'; ssh root@router date
> -uR
> Sat, 11 Feb 2023 10:07:45 +0000
> 65536+0 records in
> 65536+0 records out
> 2147483648 bytes (2.1 GB, 2.0 GiB) copied, 59.5075
> s, 36.1 MB/s
> Sat, 11 Feb 2023 10:08:51 +0000
>

>
> Since it finishes in about 66 s on a wall clock
> (in my case the router's clock) rather than 59.5 s
> on it's own clock, the actual data rate is about
> 32.5 MB/s rather than 36.1. How many seconds does
> you Mirabox spend on the same task?

root@Mirabox:~# time dd if=/dev/urandom of=/dev/null bs=32k count=65536
65536+0 records in
65536+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 98.914 s, 21.7 MB/s

real	1m38.923s
user	0m0.090s
sys	1m38.722s

And the 1m38.923s is about the same as on my phone stop watch (1m39s).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

I'm preparing to reinstall my RN102 with debian and was so pleased to find your forum with its excelent guides.
I'm wondering what additional steps will be required after I follow the instructions here to upgrade to the 'Bookworm' edition?

cheers,

Rudy

Rudy,

> I'm wondering what additional steps will be
> required after I follow the instructions here to
> upgrade to the 'Bookworm' edition?

The latest rootfs is Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2. You can use that instead of the old rootfs (Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2) stated in the installation instruction.

And each of these released rootfs is a very basic rootfs with only a minimal number of Debian packages pre-installed. This is to provide a complete Debian system with no extras.

So you will need to install whatever packages/apps you will need (e.g. Samba). See the Wiki thread for ideas and some tutorials.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks Bodhi,

I'll give it a try.

Hi bodhi

Quote
bodhi
Kernel 6.4.11-mvebu-tld-1 package has been uploaded. See 1st post for download link.

If you create a release for Netgear RN102 and RN104 too, I'll be eager to check it out.

Regards,
Trond Melen

Hi Trond,

Quote

If you create a release for Netgear RN102 and RN104 too, I'll be eager to check it out.

Sure I will.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Kernel linux-6.4.11-mvebu-370xp-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

I have successfully installed Linux kernel version 6.4.11 on two Netgear RN102 file servers and one RN104. The root file system is on an SSD connected to the rear eSata port on all three servers. This new kernel works as expected. Thanks!

The lagging system clock issue (https://forum.doozan.com/read.php?2,133814) remains.

There are two minor typos in the instructions from 22 Aug 2023:

linux-image-6.4.11-mvebu-370xp-tld-1_1.0_armhf.deb ->
linux-image-6.4.11-mvebu-370xp-tld-1_1_armhf.deb

zImage-6.1.8-mvebu-370xp-tld-1 ->
zImage-6.4.11-mvebu-370xp-tld-1

Regards,
Trond Melen

Thanks Trond!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Kernel linux-6.5.7-mvebu-370xp-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

Some months ago, I tried, without success, to do a dist-upgrade of one of my Netgear RN102 boxes from Debian 11.7 to 12. Several things failed, but I have forgotten the details. The box has since been off, until I did this fresh install yesterday.

Using your latest tar-balls, I successfully installed Debian 12.4 and Linux kernel 6.5.7 on the RN102. It now seems to run smoothly, but the system clock is still loosing some 5-6 min per hour if not syncronizing the system clock with the hardware clock every minute as described here.

I did not make a new uImage as bescribed under the '06 Sept 2020' section, though. Rather I copied the '/boot' directory from another RN102 with kernel version 6.4.11. The following upgrade to 6.5.7 went flawlessly.

On RN102 the ethernet temporarily becomes 'end1' during boot, while '/etc/network/interfaces' assumes 'end0' so I had to modify the file:

$ diff /etc/network/interfaces.orig /etc/network/interfaces
1c1
< rename /end0=eth0
---
> rename /end1=eth0
$

There is a minor spelling error here:

Latest released kernel: linux-6.6.2-mvebu-tld-1-bodhi.tar.bz2 (21 Nov 2023)
Latest released rootfs: Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 (16 Dec 2021)

Both years should read 2023.

Thanks for continuosly posting new upgrades!

Regarsds,
Trond Melen

Hi Trond,

> Using your latest tar-balls, I successfully
> installed Debian 12.4 and Linux kernel 6.5.7 on
> the RN102. It now seems to run smoothly, but the
> system clock is still loosing some 5-6 min per
> hour if not syncronizing the system clock with the
> hardware clock every minute as described
> here.

Bummer! wish we have another RN102 user to compare notes. We can't eliminate HW problem easily without another box.

> I did not make a new uImage as bescribed under the
> '06 Sept 2020' section, though. Rather I copied
> the '/boot' directory from another RN102 with
> kernel version 6.4.11. The following upgrade to
> 6.5.7 went flawlessly.
>
> On RN102 the ethernet temporarily becomes 'end1'
> during boot, while '/etc/network/interfaces'
> assumes 'end0' so I had to modify the file:
>

> $ diff /etc/network/interfaces.orig
> /etc/network/interfaces
> 1c1
> < rename /end0=eth0
> ---
> > rename /end1=eth0
> $
>

>
> There is a minor spelling error
> here:
>

> Latest released kernel:
> linux-6.6.2-mvebu-tld-1-bodhi.tar.bz2 (21 Nov
> 2023)
> Latest released rootfs:
> Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 (16
> Dec 2021)
>

> Both years should read 2023.

Thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

Quote

Bummer! wish we have another RN102 user to compare notes. We can't eliminate HW problem easily without another box.

I'm operating two RN102s and one RN104. They all behave the same.

Since, according to you, the Mirabox does not have this issue, I'm pretty sure the cause is related to the difference between the Marvell 88F6707 (Mirabox SoC) and Marvell 88F6710 (RN102 SoC). The former is a stripped down version of the latter. My hottest hypothesis still is that one of the modules added in 88F6710 (I2S, S/PDIF, TDM and Device Bus Controller) is not fully disabled and disturbs the CPU with interrupts which regularly makes it miss timer interrupts that should have incremented the 64-bit Linux system clock.

I believe this issue has always been there in mainline Linux. I believe that, many years ago, NTP (Network Time Protocol) was masking the issue by overruling the system clock, while today it is more cautious.

- Trond

Hi Trond,

> Since, according to
> you,
> the Mirabox does not have this issue, I'm pretty
> sure the cause is related to the difference
> between the Marvell 88F6707 (Mirabox SoC) and
> Marvell 88F6710 (RN102 SoC). The former is a
> stripped down version of the latter. My hottest
> hypothesis
> still is that one of the modules added in 88F6710
> (I2S, S/PDIF, TDM and Device Bus Controller) is
> not fully disabled and disturbs the CPU with
> interrupts which regularly makes it miss timer
> interrupts that should have incremented the 64-bit
> Linux system clock.
>
> I believe this issue has always been there in
> mainline Linux. I believe that, many years ago,
> NTP (Network Time Protocol) was masking the issue
> by overruling the system clock, while today it is
> more cautious.
>

I configured this kernel the same way for all MVEBU SoCs (except for some UART addresses and SMP), which include the Marvell Dove SoC.

I think you're might be right about I2S, S/PDIF. Those sound drivers are really for the Dove SoC, because there are real devices on those Dove boards. Perhaps we can revisit this issue by removing some configs in the next kernel builds for linux-6.6.x-mvebu-370xp-tld-x.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I installed newest kernel 6.5.7-mvebu-370xp-tld-1 with hope that wake on lan will work, however it does not. Does anyone try wake on lan with debian on RN102?

Przemek,

Trond will be able to help you better. But what is the output of

ethtool eth0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

root@rn102:/home/nas# uname -a
Linux rn102 6.5.7-mvebu-370xp-tld-1 #2 PREEMPT Thu Oct 19 18:31:43 PDT 2023 armv7l GNU/Linux
root@rn102:/home/nas# ethtool end1
Settings for end1:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	                                     1000baseT/Full
	Link partner advertised pause frame use: Symmetric
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: external
	MDI-X: Unknown
	Supports Wake-on: pg
	Wake-on: g
	Link detected: yes
root@rn102:/home/nas# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug end1
iface end1 inet dhcp
    hwaddress ether 00:50:43:02:02:00
    ethernet-wol g


root@rn102:/home/nas# cat /sys/devices/platform/soc/soc:internal-regs/d0074000.ethernet/net/end1/power/wakeup
enabled

Sometimes when i do poweroff command i got kernel panic

[  256.300858][    T1] reboot: Power down                                                                                                                                                                          
[  266.505858][    T1] ------------[ cut here ]------------                                                                                                                                                        
[  266.510757][    T1] WARNING: CPU: 0 PID: 1 at drivers/power/reset/gpio-poweroff.c:46 legacy_pm_power_off+0x18/0x2c                                                                                              
[  266.520313][    T1] Modules linked in: binfmt_misc snd_soc_simple_card snd_soc_spdif_tx snd_soc_simple_card_utils snd_soc_kirkwood snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_timer snd s 
[  266.549803][    T1] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 6.5.7-mvebu-370xp-tld-1 #2                                                                                                                 s
[  266.557743][    T1] Hardware name: Marvell Armada 370/XP (Device Tree)                                                                                                                                          
[  266.563762][    T1]  unwind_backtrace from show_stack+0x10/0x14                                                                                                                                                 
[  266.569236][    T1]  show_stack from dump_stack_lvl+0x24/0x2c                                                                                                                                                   
[  266.574548][    T1]  dump_stack_lvl from __warn+0x68/0xc4                                                                                                                                                       
[  266.579539][    T1]  __warn from warn_slowpath_fmt+0x88/0x114                                                                                                                                                   
[  266.584856][    T1]  warn_slowpath_fmt from legacy_pm_power_off+0x18/0x2c                                                                                                                                       
[  266.591125][    T1]  legacy_pm_power_off from sys_off_notify+0x2c/0x50                                                                                                                                          
[  266.597151][    T1]  sys_off_notify from notifier_call_chain+0x40/0x64                                                                                                                                          
[  266.603190][    T1]  notifier_call_chain from atomic_notifier_call_chain+0x30/0x44                                                                                                                              
[  266.610179][    T1]  atomic_notifier_call_chain from do_kernel_power_off+0x3c/0x54                                                                                                                              
[  266.617165][    T1]  do_kernel_power_off from __do_sys_reboot+0xc0/0x1e8                                                                                                                                        
[  266.623352][    T1]  __do_sys_reboot from ret_fast_syscall+0x0/0x54                                                                                                                                             
[  266.629138][    T1] Exception stack(0xe0821fa8 to 0xe0821ff0)                                                                                                                                                   
[  266.634443][    T1] 1fa0:                   004ec99c 00000000 fee1dead 28121969 4321fedc 00000000                                                                                                               
[  266.642623][    T1] 1fc0: 004ec99c 00000000 00000003 00000058 be92bdd4 00000000 be92bb2c 4321fedc                                                                                                               
[  266.650801][    T1] 1fe0: 00000058 be92ba7c b6c90b55 b6c00616                                                                                                                                                   
[  266.656097][    T1] ---[ end trace 0000000000000000 ]---                                                                                                                                                        
[  266.676263][    T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000                                                                                                                     
[  266.683976][    T1] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G        W          6.5.7-mvebu-370xp-tld-1 #2                                                                                                 
[  266.693276][    T1] Hardware name: Marvell Armada 370/XP (Device Tree)                                                                                                                                          
[  266.699295][    T1]  unwind_backtrace from show_stack+0x10/0x14                                                                                                                                                 
[  266.704769][    T1]  show_stack from dump_stack_lvl+0x24/0x2c                                                                                                                                                   
[  266.710078][    T1]  dump_stack_lvl from panic+0xf4/0x2d4                                                                                                                                                       
[  266.715067][    T1]  panic from do_exit+0x22c/0x924                                                                                                                                                             
[  266.719585][    T1]  do_exit from __do_sys_reboot+0xc8/0x1e8                                                                                                                                                    
[  266.724816][    T1]  __do_sys_reboot from ret_fast_syscall+0x0/0x54                                                                                                                                             
[  266.730601][    T1] Exception stack(0xe0821fa8 to 0xe0821ff0)                                                                                                                                                   
[  266.735903][    T1] 1fa0:                   004ec99c 00000000 fee1dead 28121969 4321fedc 00000000                                                                                                               
[  266.744082][    T1] 1fc0: 004ec99c 00000000 00000003 00000058 be92bdd4 00000000 be92bb2c 4321fedc                                                                                                               
[  266.752260][    T1] 1fe0: 00000058 be92ba7c b6c90b55 b6c00616                                                                                                                                                   
[  266.757560][    T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 ]---  

> [ 266.683976][ T1] CPU: 0 PID: 1 Comm:
> systemd-shutdow Tainted: G W
> 6.5.7-mvebu-370xp-tld-1 #2

Are you running systemd ?

Instead of power off, how about doing

shutdown -h now

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)