Posted: Mon Nov 11, 2024 15:04 Post subject: New Build - 11/11/2024 - r58662
Welcome to x86 / x64 r58662 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp) 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Debug Analyze: stracetcpdump.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
Router/Version: industrial PC N4000 4GB RAM, 2*intel i226-v
File: dd-wrt_x64-webupgrade_full_vga_2GB.bin
Firmware: DD-WRT v3.0-r58662 std (11/11/24) (prev. DD-WRT v3.0-r58627 std (11/02/24))
Kernel: Linux 6.6.60-rt29 #440 SMP Mon Nov 11 08:54:50 +07 2024 x86_64
Mode: Gateway, SFE disabled, Wireguard for external access, WAN (PPPoE/VLAN7) to GPON Modem, samba/nfs to access USB3-ext4 SSD, Force reconnect 5:00 in the morning, using my own local NTP, CPU governor set to on demand by startup script.
Reset: No
Status: Installed at release.
Some parts of Syslog timestamp are minus one hour off (on all DD-WRT devices of mine.). Time in upper right corner is ok.
USB Disks are not mounted at boot / restart. Enabling / disabling of Core USB Support, USB Storage Support or Automatic Drive Mount does not fix this, also rebooting does not fix this. Have to disconnect the USB cable by hand and reconnect it, otherwhise sda is not shown in Webif, resulting in Samba and NFS shares to be not available.
After reconnection by hand everything comes online and disk is shown in Webif.
I haven't had any problems with the past few releases. I'm running a vostro 620 i7 2600 with 16g ram. I run 2 drives for nas and have 2.4g and 5g wifi without issue all in one case. The cpu running full speed is the only issue I've been have but fixed with the script found here. Not trying to sound like an ass but do you think it might be hardware related?
This combination worked flawless with a WRT 1900ACS v2 before and before this with a Netgear R7800.
All sporting DD-WRT.
Also two similar drives where connected to these routers without any nuisance.
After formatting those disks over and over (on several routers) redoing and checking the configuration... I did not know how to proceed here and figured I'd report this, to receive feedback of any kind.
The (JMicron if I'm not mistaken) sATA bridge seems to be recognized as USB to ATA/ATAPI Bridge, at least according to
Code:
root@N4000:/sys/bus/usb/devices/usb1/driver/usb2/2-2# cat product
USB to ATA/ATAPI Bridge
The Host itself uses a normal intel USB Controller, as far as my google foo was able to take me:
Code:
root@N4000:/sys/bus/usb/devices/usb1/driver/usb2/2-2# lspci |grep USB
00:15.0 USB controller: Intel Corporation Celeron/Pentium Silver Processor USB 3.0 xHCI Controller (rev 03)
It should work, I think.
My current idea is to figure out what module is in charge for USB and unload and reload it by script.
But should I refrain from reporting this? No idea, maybe it is time, since I'm the only one :/
--EDIT--
I went ahead and figured which drivers are in charge, "usb-storage" and / or "hub":
So I went ahead and looked into lsmod. According to its output those drivers aren't loaded.
When trying to unload them with rmmod, I get no such file/directory error.
This had me curious, those modules arent available at /lib/modules/6.6.60-rt29 too.
So they are built into the kernel.
My knowledge ends here, but I know it is somehow possible to unbind a device and rebind it.
I'll research this way further and update this post.
My solution is simple:
/dev/sda was always available after each reboot, but the "Automatic Drive Mount" seemingly only worked after disconnecting and reattaching the disk by hand.
I solved it with adding mkdir and mount commands to startup and disabling the "Automatic Drive Mount" feature in "Services" --> "USB".
If someone is interested, this is my final "construct" I added to "Administration" --> "Commands" --> "Startup":
Code:
# mount USB disk if available
echo "if [ -e /dev/sda ]; then echo "/dev/sda available, mounting it">>/var/log/messages; mkdir -p /mnt/sda; mount /dev/sda /mnt/sda; else echo
"/dev/sda missing, nothing to mount">>/var/log/messages; fi" > /tmp/zyxx.sh
chmod +x /tmp/zyxx.sh
/bin/sh /tmp/zyxx.sh
Please note:
If you try to use this script a "modprobe ext4" might be in need if this module isn't already active and your disk is also ext4 formatted.
Ofc this is meant for /dev/sda, if your disk isn't listed there or you try to use this for sdXYZ, you have to edit this.
I haven't had any problems with the past few releases. I'm running a vostro 620 i7 2600 with 16g ram. I run 2 drives for nas and have 2.4g and 5g wifi without issue all in one case. The cpu running full speed is the only issue I've been have but fixed with the script found here. Not trying to sound like an ass but do you think it might be hardware related?
It's not hardware related it was a choice from the Dev to not to slow it down. I think there was inconsistent speed issues or crashes cause of the throttle control and it was disabled for now.
Fair warning. I have use the Startup command that Sp!derman did and it was causing the system to randomly crash with a Kernel Panic. I think my command was more stable which I need to test. Not sure why. I removed the command and let the cpu run at full speed. It has a really decent cooler so heat will never be an issue for it. It's been stable for over 2 days now.