Hi bodhi, Thank you very much for your efforts! I have successfully installed Linux kernel version 'linux-6.7.5-mvebu-370xp-tld-3' on a Readynas RN102. It works a expected. To check the system clock, I disabled the 'crontab' job that updates the system clock from the hardware clock once a minute. I also made the RN102 trust my laptop so that 'ssh' works withoutby tme - Debian
Nice project, whitepawn. I wish you good luck, and hope you succeed!by tme - Debian
Hi bodhi, A difference in the U-Boot environment between the boxes caught my attention: $ diff /tmp/fw*.sorted 32c31 < fdt_skip_update=no --- > fdt_skip_update=yes What does 'fdt_skip_update' do to U-Boot? Which is the recommended setting? Regards, Trond Melenby tme - Debian
Hi bodhi, Quote Indeed a strange problem! Could you delete the /etc/fw_env.config file and create it again by manually typing in /dev/mtd1 0x0 0x20000 0x20000 Note that tab or space is not relevant. And "Number of sectors" is not used anymore (it should not hurt to have, though). The configuration file '/etc/fw_env.config' is just fine: $ hexdump -C /etc/fw_env.cby tme - Debian
Hi bodhi, Quote Check the modules load option on both boxes: cat /etc/initramfs-tools/initramfs.conf | grep MODULES If MODULES=dep then this rootfs started from Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2. That'd explain why the uInitrd is much smaller. The previous rootfs has MODULES=most. This configuration file is indeed different between the two boxes: $ LC_TIME= ls -Aby tme - Debian
Hi bodhi, I have successfully updated my 2nd RN102 to Linux version 6.7.5. I noticed that the size of 'uInitrd' differs significantly between the two boxes. On the 1st box: -rw-r--r-- 1 root root 5665854 Mar 1 09:13 initrd.img-6.7.5-mvebu-370xp-tld-2 -rw-r--r-- 1 root root 5665918 Mar 1 09:13 uInitrd On the 2nd: -rw-r--r-- 1 root root 10744490 Mar 1 08:53 initrd.imgby tme - Debian
Hi bodhi, Sorry, for the mishap! I gave it a new try, and now it booted. The system clock is still lagging, but a bit less than before. It used to be lagging 6 to 7 seconds per minute. Now it's lagging just above 5 seconds per minute. Btw, the title of this thread has a spelling error: RN120/RN104 should read RN102/RN104. Regards, Trond Melenby tme - Debian
Hi bodhi, Booting my RN102 with the new DTB with the audio controller nodes removed failed with the message: Error: invalid dtb and unrecognized/unsupported machine ID The full log is attached. Did I do something wrong? Regards, Trond Melenby tme - Debian
Hi bodhi, Where do I find the new DTB with the audio controller nodes removed? Regards, Trond Melenby tme - Debian
Hi bodhi, Following your directions in the first post of this thread, I have successfully installed Linux kernel version 6.7.5 on one of my Netgear RN102 file servers (mainly used as a dlna server). The root file system is on an SSD connected to the rear eSata port. This new kernel works as expected. Thanks! The lagging system clock issue (https://forum.doozan.com/read.php?2,133814) still rby tme - Debian
Hi bodhi, QuoteIt should be 4x RAM (at the minimum) with BFQ IO scheduler. Good tip! Fixed: $ diff /etc/dphys-swapfile.orig /etc/dphys-swapfile 20c20 < #CONF_SWAPFACTOR=2 --- > CONF_SWAPFACTOR=4 $ /sbin/swapon NAME TYPE SIZE USED PRIO /var/swap file 1.9G 256K -2 Regards, Trond Melenby tme - Debian
Hi bodhi, I would recommend the package 'dphys-swapfile' rather than manually creating a swap file. By default it creates '/var/swap' twice the size of the onboard memory and enables swapping and paging to it. The 'dphys-swapfile' package is very small (~20 kB). One advantage is that swap size increases if extra memory is added. Another is that '/etc/rc.loby tme - Debian
Hi bodhi, QuoteBummer! 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 88F6710by tme - Debian
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, buby tme - Debian
Hi bodhi, I'm glad to hear you found this trick useful! - Trond Melenby tme - Debian
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 Auby tme - Debian
Hi bodhi Quotebodhi 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 Melenby tme - Debian
Hi wdq, The tutorial bodhi refers to is about a USB-to-Ethernet dongle, while you have a USB-to-WiFi dongle, so there will be some differences. For one, unless you want your Stora to act as a router, you probably want it to be a DHCP client rather than a DHCP server. To me it seems you already got that part right. Your issue seem to be related to the authentication of the Stora by the routeby tme - Debian
Hi rayknight, Quote Perhaps you should try the kernel images hosted at Natisbad (where support for the device was first introduced) to see if the issue has been present from the introduction of support for this device. Great suggestion! I downloaded the Linux kernel version 4.4.1 'uImage' and the Debian installer 'uInitrd' for "Efikamx mx5" from Natisbad toby tme - Debian
Thanks bodhi, for providing these outdated kernels for testing. On Netgear RN102, the lagging issue is present in both Linux 4.20.6 and 5.8.5. This is from the serial console with kernel 4.20.6 and Debian 10.0. The delay between the two 'date' commands was 60 s: debian login: root Password: Last login: Thu Sep 5 01:58:44 PDT 2019 from 192.168.0.100 on pts/0 Linux debian 4.by tme - Debian
Hi bodhi, I would like to check if the time lagging issue has been around for a long time, or if has been introduced more recently. Without success, I tried to boot the kernel in 'Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2'. I assume it lacks support for 370xp? As you know, the file ' Linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2' has been purged from your dropbox. Is tby tme - Debian
Hi Gravelrash, Quote This is an awesome tip!!! Thanks! I'm not sure exactly what kind of debugging you want. If the box you want to debug is on a network you cannot access outside the machine room, I suggest you connect the Ethernet cable to a wireless router. As long as you're within the reach of the wireless router, you may access it through the WiFi interface on your PC. Ifby tme - Debian
Hi bodhi, Quote Not sure why the timer@20300 was spesificed in the Mirabox, there is no need for it, this could be old code for the L2 cache frequency. I installed the device tree compiler on a Netgear RN102 with you latest kernel and root file system and converted its dtb-file to dts format. There where 23 warnings: $ sudo apt-get install device-tree-compiler $ sudo dtc -I dtb -O dtsby tme - Debian
Hi bodhi, Quote One thing I'd question: is the name enx* always the pattern, or a different adapter will give you a different name pattern? As stated above, USB-to-Ethernet adapters seems to always be named 'enx0123456789ab' by the Linux kernel where '01:23:45:67:89:ab' is their MAC addresses. This is also the case for the USB 3.0 gigabit adapter (picture attached)by tme - Debian
Thanks for the boot log bodhi, As expected, booting my RN102 with a device tree for Mirabox fails, but only after 4.7 seconds: [ 4.693689][ T1] mdio_bus d0072004.mdio-mii: MDIO device at address 1 is missing. The full boot log is attached. Before that, there is a one-to-one correspondence between the RN102 and Mirabox boot log messages with just two exceptions: [ 0.000000][by tme - Debian
Thanks bodhi, for powering up your Mirabox and for running the 'urandom' test! To me it seems that the RN102 CPU and its free running timer run at the same speed as on the Mirabox. My hypothesis now is that the RN102 system clock is updated by timer interrupts from the free running timer (Timer 0) at regular intervals, and that about 1 out of 12 interrupts are missed, alternativelby tme - Debian
Hi JoeyPogoPlugE02, It's good to hear that the box arrived safely! If you connect the box to a router with DHCP and plug-and-play, you should be able to reach it with 'ssh': $ ssh root@debian or $ ssh root@debian.local Or you may use 'putty' from a MS Window PC. Have fun! Regards, Trond Melenby tme - Off-Topic
Hi bodhi, The two adapters in the picture are fairly different, but they are both named 'enx0123456789ab' by the kernel where '01:23:45:67:89:ab' is their MAC addresses. I assume it's universal until someone reports something else. I have a third one in order (about $8 from China) so I can report about one more in, say, 3 weeks. Regards, Trond Melenby tme - Debian
With multiple boxes around, it may be hard to remember the hostname or IP address of each box, and be certain which box one is connected to. One solution is to connect directly with a cable to the box's front USB connector. This post describes how to set up the box such that plugging a USB-to-Ethernet adapter into the front USB port and connecting it to a PC with an Ethernet cable givesby tme - Debian
I was curious about whether there were further escape sequence codes than just '+' and '-' (back light on and off). Yes, there are: tme@rn104:/tmp$ wget https://github.com/torvalds/linux/raw/master/drivers/auxdisplay/charlcd.c tme@rn104:/tmp$ grep "case.**/" charlcd.c case 'D': /* Display ON */ case 'd': /* Display OFF */ case 'C&by tme - Displays