Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.107SF

    Thank you @Voxel I never felt the need to restart my router till the next firmware update. Router runs buttery smooth for months without restart, like it runs just after the restart. Not to mention the control I have with SSH and my custom scripts. I think I may be blindly updating the...
  2. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.104SF

    Thank you @Voxel Working like a charm
  3. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.102SF

    Thank you @Voxel. Updated and working like a charm. Indeed. This one will be really appreciated who uses ssh bit often. Just tested and now the history is available on new ssh session. For viewing full history: tail ~/.ash_history
  4. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.101SF

    Yes it is different and thorough reset. It is mentioned in the kamoj's FAQ. https://www.voxel-firmware.com/Downloads/Voxel/Kamoj/FAQ.txt
  5. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.101SF

    Highly likely reasons could be [either] faulty power-supply/power-outlet [or] corrupted settings. 1 - Do a full factory reset and manually add settings, do not restore from existing saved settings. Run these cmds from telnet/ssh for reset: (Courtesy Kamoj FAQ) nvram default nvram commit mtd...
  6. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.101SF

    Yes that's true. I used it one time and then switched to ext4. I did not unlpug the drive from router for years. Ext4 makes it easier to format (when needed) and use drive from the router while keeping it plugged in. I use the same ssh drive for few other scripts as well.
  7. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.101SF

    The fact that you are not seeing sda1 because your usb is never mounted properly. When you plug in the usb, create partition table with mklabel, format it "mkfs.ext4" and disable the "metadata_csum". Reboot router (if needed) your usb will be automatically mounted to "/mnt/sda1/" Mount location...
  8. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.101SF

    This readme has evolved over years. That is why you are seeing ext2 at places. For SSH access you need to format usb wih ext4. "mkfs.ext4" enables "metadata_csum" feature, make sure you disable it with "tune2fs" cmd, otherwise usb will be mounted read-only. For ease of use it is recommended...
  9. fossil

    Trying to install Entware but usb drive is readonly (R7800)

    Did you disable the "metadata_csum" or it was already disabled? Try to force unmount usb: umount -f /mnt/sda1/ If force unmount does not work unplug the usb. Check if usb is still mounted with cmd "ls -l /mnt/" [OR] "df -h" [OR] "mount | grep sda1". If it is, router reboot is needed with usb...
  10. fossil

    Trying to install Entware but usb drive is readonly (R7800)

    You can use below cmd to check if "metadata_csum" feature is enabled by "mkfs.ext4" cmd on the usb: tune2fs -l /dev/sda1 | grep features
  11. fossil

    Trying to install Entware but usb drive is readonly (R7800)

    R7800 uses old version of mount cmd. Old version of mount can only mount usb/partition read-only with metadata_csum feature enabled. Disable Metadata-Checksum. Format Ext4: mkfs.ext4 -L <name> /dev/sda1 Disable Metadata-Checksum: tune2fs -O ^metadata_csum /dev/sda1 Mount Read/Write: mount...
  12. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.101SF

    Should be either of these two depending on remaining code: if (fpu == NULL) return; [OR] if (fpu != NULL) { snprintf(mnt_path, sizeof(mnt_path), "/mnt/%s", part_name); strcpy(partinfo->mount_name,part_name); fclose(fpu); }
  13. fossil

    Voxel Custom firmware build for Orbi RBK50/RBK53 (RBR50, RBS50) v. 9.2.5.2.27SF-HW & v. 9.2.5.2.27.1SF-HW

    It does start automatically, if you enable FTP under ReadyShare from UI. Enabled FTP under ReadyShare > Advanced Settings: Ran "ps -w" on shell and proftpd was running automatically: When proftpd runs automatically from UI it creates "/tmp/proftpd.conf" which is mentioned in "/sbin/cmdftp"...
  14. fossil

    Voxel Custom firmware build for Orbi RBK50/RBK53 (RBR50, RBS50) v. 9.2.5.2.27SF-HW & v. 9.2.5.2.27.1SF-HW

    It is in /usr/sbin/proftpd on R7800, should be same for Orbi. Type on shell: proftpd -h All you have to do is create conf file according to your liking. Default path is /etc/proftpd.conf on R7800. Type proftpd to see config path. This may be helpful for config...
  15. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.100SF

    Thank you @Voxel Another perfect release, working great. I was thinking is it going to be .2.100 or .3.1 Thanks for the binutils update
  16. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.98SF

    Make sure you keep a backup config before proceeding. "nvram unset" cmd does not accept regular expressions. It makes sense it could be devastating. Get the 3 lists copy them to some file: nvram show | grep device_list_* nvram show | grep device_name_user_set_* nvram show | grep...
  17. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.98SF

    These duplicate entries in the device_list* nvram indicate that this device was assigned the device name and device type (icon) once from the UI. Then if you change the device name [OR] you re-assign the icon (after loosing the icon) under Attached Devices, it will add a new entry in the...
  18. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.98SF

    That side effect was there, I only observed it when an "Attached Device" was removed from the device_list* nvram variable. That is why I specifically mentioned it in the caution, and recommended to take config backup. To find out corrupted nand is easy, you just have to reboot the router and...
  19. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.98SF

    May be you have reached the limit "Attached Devices" page can accommodate under nvram. (just my guess) A device that was assigned a name and type (icon) under "Attached Devices" remains in nvram even if it is never connected again to your network. And it will not be visible under "Attached...
  20. fossil

    Voxel Custom firmware build for R7800 v. 1.0.2.98SF

    @LeKeiser You can verify if it is the browser cache issue or the icon is not saving to the nvram. Run below from ssh/telent: nvram show | grep device_list* Result format: device_list<number>=<mac-address> _ <icon-number> <device-name-under-attached-devices> icon-number will be 41 for Apple TV...
Top