New Build - 03/13/2024 - r55363

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
strange
DD-WRT User


Joined: 18 Jun 2006
Posts: 233

PostPosted: Thu Mar 14, 2024 21:25    Post subject: Reply with quote
SurprisedItWorks wrote:
Request: If you are reporting on SMB/USB success/failure, please state the drive format. Are these ext2/ext4 drives? Or are we talking one of the Windozy formats?


My SSD is formatted with ext4. FTP works fine but I can no longer (since the kernel upgrade) log-in smb with my computer which is running Linux Mint Cinnamon edition. Hope that helps.

_________________
Netgear XR500 - Gateway
R6700 v3 - Station Bridge
Sponsor
whitebeard
DD-WRT User


Joined: 26 Jul 2013
Posts: 127
Location: Canada

PostPosted: Thu Mar 14, 2024 21:50    Post subject: Reply with quote
Router/Version: Netgear R7500v2
Kernel: Linux 6.1.80 #114 SMP Tue Mar 5 13:32:55 +07 2024 armv7l
Previous/Reset: 55179 / No Reset
Mode: Gateway+AP, SFE Disabled, STP Disabled, Wifi 5(VANILLA)/2.4(VANILLA) Main+Guest(VAP), DNSMasq, USB(3.2, Ext2)/Entware, DNSCrypt, NAS/Samba, Static & DHCP, SSH, FTP, QoS (WAN) using MAC.
Issues/Errors: Upgraded Ok. SMB still crashes the router on saves to router mounted USB Drive. Otherwise everything else seems Ok.

Thanks to BS and crew for all your good work.

The USB's format is EXT2. Note that prior to doing the test for writing to the USB Drive via SMB this log popped up which I don't recall seeing before:
Code:

Mar 13 21:10:28   192.168.1.1      local5   err   ksmbd   [ksmbd-worker/4349]: ERROR: SRVSVC: unsupported INVOKE method 21


This is the crash report from the router's syslog during the write that leads to the router restarting:
Code:

Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.758410] <--- cut here ---
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.758436] Unable to handle kernel NULL pointer dereference at virtual address 00000032
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.761317] [00000032] *pgd=00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89830.768576] Internal error: Oops - BUG: 17 [#1] SMP ARM
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.772074] Modules linked in: ksmbd ext4 jbd2 mbcache crc32_generic sdhci_pltfm sdhci mmc_block pwrseq_simple pwrseq_emmc mmc_core imq ahci_platform ahci libahci_platform libahci ses libata uas usb_storage sr_mod cdrom sd_mo
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.816248] CPU: 0 PID: 6294 Comm: kworker/0:0 Not tainted 6.1.80 #114
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.838482] Hardware name: Generic DT based system
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.844904] Workqueue: ksmbd-io _34 [ksmbd]
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.849677] PC is at _658+0x10/0x1b4 [ksmbd]
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.853755] LR is at _6+0x17c/0x1c4 [ksmbd]
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.858269] pc : [<bf4e7de8>]    lr : [<bf4e8108>]    psr: 200b0013
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.862178] sp : cdb93d48  ip : cdb93d70  fp : cdb93d6c
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.868427] r10: 00000029  r9 : c7aadb00  r8 : c7aadb9c
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.873635] r7 : bf521284  r6 : c7aadb00  r5 : c7aadb00  r4 : 00000000
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.878847] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : c7aadb00
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.885443] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89830.891956] Control: 10c5787d  Table: 47e2406a  DAC: 00000051
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.899157] Register r0 information: slab maple_node start c7aadb00 pointer offset 0
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.904889] Register r1 information: NULL pointer
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.912697] Register r2 information: NULL pointer
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.917297] Register r3 information: NULL pointer
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.921984] Register r4 information: NULL pointer
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.926672] Register r5 information: slab maple_node start c7aadb00 pointer offset 0
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.931365] Register r6 information: slab maple_node start c7aadb00 pointer offset 0
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.939177] Register r7 information: 83-page vmalloc region starting at 0xbf4db000 allocated at layout_and_allocate.isra.0+0x34c/0x788
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.946910] Register r8 information: slab maple_node start c7aadb00 pointer offset 156
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.958794] Register r9 information: slab maple_node start c7aadb00 pointer offset 0
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.966695] Register r10 information: non-paged memory
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.974590] Register r11 information: non-slab/vmalloc memory
Mar 14 21:42:39   192.168.1.1      kern   alert   kernel   [89830.979539] Register r12 information: non-slab/vmalloc memory
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89830.985355] Process kworker/0:0 (pid: 6294, stack limit = 0x9f52b82d)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89830.991086] Stack: (0xcdb93d48 to 0xcdb94000)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89830.997509] 3d40:                   00000000 c7aadb00 c7aadb00 bf521284 c7aadb9c c7aadb00
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.001854] 3d60: cdb93d94 cdb93d70 bf4e8108 bf4e7de4 00000000 c7aadb00 c4f78ee4 bf521284
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.010014] 3d80: c7aadb9c c7aadb00 cdb93dbc cdb93d98 bf4e2508 bf4e7f98 c7aadb08 c7aadb00
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.018172] 3da0: c141e300 c4f78ee4 c7aadb9c c7aadb00 cdb93de4 cdb93dc0 bf4e2c38 bf4e242c
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.026333] 3dc0: c4425414 00000000 c141e300 00000001 00000000 c7aadb00 cdb93ebc cdb93de8
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.034493] 3de0: bf4fff8c bf4e2b60 cdb93e04 cdb93df8 c07bc168 bf52132c 000007ff 000081a4
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.042654] 3e00: 00000001 00000800 00000000 00000000 00301874 00000000 00000038 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.050813] 3e20: 00800001 00000000 00000000 00000000 0000001c 00000000 65da5c4b 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.058972] 3e40: 00000000 00000000 65f36f4f 00000000 00000000 cdb93bc0 65f36f4f 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.067132] 3e60: 00000000 cdb93bc0 00000000 00000000 00000000 00000000 00000008 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.075291] 3e80: 00000000 00000000 00000000 00000000 ff7f1d05 c141e300 00000006 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.083450] 3ea0: bf5212b4 c5c59600 00000018 bf520950 cdb93eec cdb93ec0 bf4e55a8 bf4ffce8
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.091611] 3ec0: 00000001 c141e300 c5c59600 000000b7 00000000 00000000 ff7f1d05 c4f78164
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.099770] 3ee0: cdb93f0c cdb93ef0 bf4e58c8 bf4e5448 c141e374 c4671080 dda0cd40 ff7f1d00
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.107930] 3f00: cdb93f4c cdb93f10 c0353654 bf4e588c dda0cd5c c0e03d40 cdb93f34 c46710c0
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.116089] 3f20: c0354cf0 dda0cd40 dda0cd5c c0e03d40 c4671098 c1c5e300 dda0cd40 c4671080
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.124249] 3f40: cdb93f84 cdb93f50 c03537f4 c0353490 cdb93f84 cdb93f60 c035a044 c510ae40
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.132410] 3f60: c1cb9e98 c1c5e300 c510a7c0 c035379c c4671080 00000000 cdb93fac cdb93f88
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.140570] 3f80: c035b42c c03537a8 c510ae40 c035b380 00000000 00000000 00000000 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.148733] 3fa0: 00000000 cdb93fb0 c030014c c035b38c 00000000 00000000 00000000 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.156889] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.165047] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.173205] Backtrace: 
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.181357] [<bf4e7dd8>] (_658 [ksmbd]) from [<bf4e8108>] (_6+0x17c/0x1c4 [ksmbd])
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.183626]  r9:c7aadb00 r8:c7aadb9c r7:bf521284 r6:c7aadb00 r5:c7aadb00 r4:00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.191261] [<bf4e7f8c>] (_6 [ksmbd]) from [<bf4e2508>] (_271+0x3a0/0x76c [ksmbd])
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.199164]  r9:c7aadb00 r8:c7aadb9c r7:bf521284 r6:c4f78ee4 r5:c7aadb00 r4:00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.206539] [<bf4e2420>] (_271 [ksmbd]) from [<bf4e2c38>] (_78+0xe4/0x148 [ksmbd])
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.214440]  r9:c7aadb00 r8:c7aadb9c r7:c4f78ee4 r6:c141e300 r5:c7aadb00 r4:c7aadb08
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.221818] [<bf4e2b54>] (_78 [ksmbd]) from [<bf4fff8c>] (_602+0x2b0/0x538 [ksmbd])
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.229718]  r9:c7aadb00 r8:00000000 r7:00000001 r6:c141e300 r5:00000000 r4:c4425414
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.237094] [<bf4ffcdc>] (_602 [ksmbd]) from [<bf4e55a8>] (_204+0x22c/0x504 [ksmbd])
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.245083]  r10:bf520950 r9:00000018 r8:c5c59600 r7:bf5212b4 r6:00000000 r5:00000006
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.252808]  r4:c141e300
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.260525] [<bf4e543c>] (_204 [ksmbd]) from [<bf4e58c8>] (_34+0x48/0xac [ksmbd])
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.263138]  r10:c4f78164 r9:ff7f1d05 r8:00000000 r7:00000000 r6:000000b7 r5:c5c59600
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.270515]  r4:c141e300
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.278320] [<bf4e5880>] (_34 [ksmbd]) from [<c0353654>] (process_one_work+0x1d0/0x318)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.280933]  r7:ff7f1d00 r6:dda0cd40 r5:c4671080 r4:c141e374
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.288655] [<c0353484>] (process_one_work) from [<c03537f4>] (worker_thread+0x58/0x474)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.294562]  r10:c4671080 r9:dda0cd40 r8:c1c5e300 r7:c4671098 r6:c0e03d40 r5:dda0cd5c
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.302633]  r4:dda0cd40
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.310352] [<c035379c>] (worker_thread) from [<c035b42c>] (kthread+0xac/0xb0)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.312966]  r10:00000000 r9:c4671080 r8:c035379c r7:c510a7c0 r6:c1c5e300 r5:c1cb9e98
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.319994]  r4:c510ae40
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.327887] [<c035b380>] (kthread) from [<c030014c>] (ret_from_fork+0x14/0x28)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.330496] Exception stack(0xcdb93fb0 to 0xcdb93ff8)
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.337526] 3fa0:                                     00000000 00000000 00000000 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.342652] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.350813] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.358973]  r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c035b380 r4:c510ae40
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.365397] Code: e1a0c00d e92ddbf0 e24cb004 e5903024 (e5d32032) 
Mar 14 21:42:39   192.168.1.1      kern   warning   kernel   [89831.373442] ---[ end trace 0000000000000000 ]---
Mar 14 21:42:39   192.168.1.1      kern   emerg   kernel   [89831.379412] Kernel panic - not syncing: Fatal exception
nyddwrtuser330
DD-WRT User


Joined: 05 Mar 2018
Posts: 224

PostPosted: Fri Mar 15, 2024 0:28    Post subject: Reply with quote
SurprisedItWorks wrote:
Request: If you are reporting on SMB/USB success/failure, please state the drive format. Are these ext2/ext4 drives? Or are we talking one of the Windozy formats?

r9000
k 4.9
ext4
120Gb ssd drive in a usb case

works fine on this build however i am logging
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:19:04 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:20:29 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:20:29 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
Mar 13 13:24:22 Cisco99533 local5.err ksmbd: [ksmbd-worker/4300]: ERROR: SRVSVC: unsupported INVOKE method 21
IONK
DD-WRT Guru


Joined: 19 Aug 2011
Posts: 1012

PostPosted: Fri Mar 15, 2024 1:46    Post subject: Reply with quote
SurprisedItWorks wrote:
Request: If you are reporting on SMB/USB success/failure, please state the drive format. Are these ext2/ext4 drives? Or are we talking one of the Windozy formats?
ext2 & swap partitions, 2K block size.
Note: dd-wrt will likely show ext4 even if the partition is ext2.
dale_gribble39 wrote:
IONK wrote:
for ext4/ext2 misdetection, I remember it's been a thing for a long time even before moving to kernel 6.1.

Most devices supporting ext* filesystems use the ext4.ko kernel module which is backwards-compatible, but doesn't necessarily "detect" it as ext2 or ext3:

Ext2 USB detected as Ext4
BrainSlayer wrote:
anyway. doesnt matter. ext4 driver handles all ext versions. i assume all is working.

_________________
▫ RSS feed for DD-WRT releases (2024): https://rsseverything.com/feed/7d36ab68-7733-46c3-bd8a-9c54c5cef08c.xml
easyddup - A simple upgrade/downgrade utility by yoyoma2 --- as featured in 📌 Reference Links, stickies retired back to forum (Moderator's Pick 🌟)
lexridge
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 1294
Location: WV, USA

PostPosted: Fri Mar 15, 2024 2:51    Post subject: Reply with quote
IONK wrote:
ext2 & swap partitions, 2K block size.

Curious. Are you actually using the swap partitions?

My router (EA8500) handles a ton of traffic and I am still only using about 26% of memory. Never has it needed to write to swap. If I may ask, what kind of use case requires this?

_________________
- Linksys EA8500: I-Gateway, AP/VAP 5ghz only r56820: Features: WDS-AP, VLANs, Samba, WG, Entware
- Linksys EA8500: WDS Station x2 - r56941
- Netgear R6400v2: WAP/VAP 2.4ghz only w/VLANs over single trunk port. r56820
- Netgear R7800 (WDS-AP, WAP/VAP) - r56820: Features in use: multiple VLANs over single trunk port
- Linksys MR7350: Testing r56941
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.

- Forum member #248
IONK
DD-WRT Guru


Joined: 19 Aug 2011
Posts: 1012

PostPosted: Fri Mar 15, 2024 3:03    Post subject: Reply with quote
lexridge wrote:
IONK wrote:
ext2 & swap partitions, 2K block size.

Curious. Are you actually using the swap partitions?

My router (EA8500) handles a ton of traffic and I am still only using about 26% of memory. Never has it needed to write to swap. If I may ask, what kind of use case requires this?
swap was needed for MariaDB, details here: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1270794#1270794 (may not be accurate anymore with new dd-wrt / new Entware packages)
_________________
▫ RSS feed for DD-WRT releases (2024): https://rsseverything.com/feed/7d36ab68-7733-46c3-bd8a-9c54c5cef08c.xml
easyddup - A simple upgrade/downgrade utility by yoyoma2 --- as featured in 📌 Reference Links, stickies retired back to forum (Moderator's Pick 🌟)
lexridge
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 1294
Location: WV, USA

PostPosted: Fri Mar 15, 2024 3:15    Post subject: Reply with quote
IONK wrote:
swap was needed for MariaDB

Well that makes perfect sense. I would never have thought of running a SQL DB server on a router, but that's interesting for sure. Yes, it would use up serious memory so I can see why you would need a swap now. Thanks. You got me thinking......

_________________
- Linksys EA8500: I-Gateway, AP/VAP 5ghz only r56820: Features: WDS-AP, VLANs, Samba, WG, Entware
- Linksys EA8500: WDS Station x2 - r56941
- Netgear R6400v2: WAP/VAP 2.4ghz only w/VLANs over single trunk port. r56820
- Netgear R7800 (WDS-AP, WAP/VAP) - r56820: Features in use: multiple VLANs over single trunk port
- Linksys MR7350: Testing r56941
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.

- Forum member #248
IONK
DD-WRT Guru


Joined: 19 Aug 2011
Posts: 1012

PostPosted: Fri Mar 15, 2024 4:56    Post subject: Reply with quote
lexridge wrote:
IONK wrote:
swap was needed for MariaDB
I would never have thought of running a SQL DB server on a router, but that's interesting for sure.
You're missing out because that's one good benefit of using ddwrt instead of stock firmware. Wink
_________________
▫ RSS feed for DD-WRT releases (2024): https://rsseverything.com/feed/7d36ab68-7733-46c3-bd8a-9c54c5cef08c.xml
easyddup - A simple upgrade/downgrade utility by yoyoma2 --- as featured in 📌 Reference Links, stickies retired back to forum (Moderator's Pick 🌟)
lexridge
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 1294
Location: WV, USA

PostPosted: Fri Mar 15, 2024 5:26    Post subject: Reply with quote
IONK wrote:
You're missing out because that's one good benefit of using ddwrt instead of stock firmware. Wink

Oh, I am not missing out. I have been running nothing but DD-WRT since a few months of its initial release on the WRT54G. Been through many routers since then. I currently have four EA8500s (three in use) and one R7800 WAP (plus a closet full of others, mostly Broadcom). Entware installed on Gateway and a WPS station (both EA8500s). I am using BASH, Lighttpd, mosquito (MQTT) and a few other services. Still barely uses RAM. Running a SQL database is pretty heavy duty compared to this of course. I love BASH because it retains all my command line history. I may be experimenting with SQLite on DD-WRT in the future....if it's available.

_________________
- Linksys EA8500: I-Gateway, AP/VAP 5ghz only r56820: Features: WDS-AP, VLANs, Samba, WG, Entware
- Linksys EA8500: WDS Station x2 - r56941
- Netgear R6400v2: WAP/VAP 2.4ghz only w/VLANs over single trunk port. r56820
- Netgear R7800 (WDS-AP, WAP/VAP) - r56820: Features in use: multiple VLANs over single trunk port
- Linksys MR7350: Testing r56941
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.

- Forum member #248
Deltabongo2
DD-WRT User


Joined: 11 Nov 2016
Posts: 52
Location: Canada

PostPosted: Sat Mar 16, 2024 14:06    Post subject: Reply with quote
Router/Version: D-Link DIR-859 rev A3
Firmware: DD-WRT v3.0-r55363 std (03/13/24)
File/Kernel: dir859-webflash.bin/Linux 3.18.140-d6 #195569 Wed Mar 13 15:03:20 +06 2024 mips
Previous: DD-WRT v3.0-r53339 std (08/01/23)
Update Method: GUI
Mode/Status: Gateway/AP/Ok
Reset: No
Setup Using: 2.4 GHz, 2 x 2.4 GHz guest (VAP), 5.0 GHz - Vanilla, IPv4, DHCP, DNSMasq, Port Forwarding, SFE automatically disabled due to unbridged guest VAPs.
Issues/Errors: Ok
sumbuddie
DD-WRT User


Joined: 28 Mar 2009
Posts: 77

PostPosted: Sat Mar 16, 2024 17:36    Post subject: Reply with quote
kernel-panic69 wrote:
It always pays to have a little look around to know what's going on and know that the EA8500's current status is not good for DD-WRT:

EA8500 and other models not booting after 53562 builds

Full reset and rebuild of EA8500 Gateway Router [r53562]

Complaints noted.


Would it be possible to prevent new builds for the EA8500 being built until a fix is found?

IMO, that would be a good idea to prevent others from bricking their EA8500s - either no directory or just a link back to the last working build version (v.53562)
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14569
Location: Texas, USA

PostPosted: Wed Mar 20, 2024 15:37    Post subject: Reply with quote
@sumbuddie: I can try to email BS, but I'm pretty sure the answer I will get will be a resounding "NO" on that. In other news, someone can't read and opened an issue on github regarding the reboots on the R7800. It would've served the purpose better to post in this or any other build thread, and it was most likely already stated what is needed (serial logs)... Rolling Eyes *SIGH*
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
lexridge
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 1294
Location: WV, USA

PostPosted: Wed Mar 20, 2024 17:50    Post subject: Reply with quote
Or better yet, write to BS and ask him to work with EA8500 owners in an attempt to get this fixed. Whether the fix is making it functional on k6.1 or reverting to k4.9, I doubt many EA8500 owners would care at this point.
_________________
- Linksys EA8500: I-Gateway, AP/VAP 5ghz only r56820: Features: WDS-AP, VLANs, Samba, WG, Entware
- Linksys EA8500: WDS Station x2 - r56941
- Netgear R6400v2: WAP/VAP 2.4ghz only w/VLANs over single trunk port. r56820
- Netgear R7800 (WDS-AP, WAP/VAP) - r56820: Features in use: multiple VLANs over single trunk port
- Linksys MR7350: Testing r56941
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.

- Forum member #248
Mucee
DD-WRT Novice


Joined: 09 Apr 2022
Posts: 2

PostPosted: Sat Mar 23, 2024 17:39    Post subject: Reply with quote
Router/Version: Netgear XR450
File/Kernel: DD-WRT v3.0-r55363 std (03/13/24)
Previous/Reset: DD-WRT v3.0-r50906 (11/18/22), accidental reset
Mode/Status: Working, but syslog flood
Issues/Errors:

I thought I selected do not reset nvram, but it was reset

Seems to take longer to become accessible after reboot

DD-WRT identifies it as an XR500, but that happened with the previous version noted above. I'm not sure if the two images on ftp are different. I read from forum posts that the difference between the XR450 and XR500 is QAM256 support, so I think I can just not enable that. I noticed a commit in October 2023 that split two different devicetrees for the XR450 and XR500, but they seemed identical otherwise.

I haven't had time to re-enable DDNS and Wireguard yet. Otherwise, things seem stable. I am using SFE because it seems slightly faster at 100 Mbps and I have no issues.
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6526
Location: UK, London, just across the river..

PostPosted: Sat Mar 23, 2024 17:47    Post subject: Reply with quote
i guess both are the same and its ok to report xr500.....
also you dont need SFE with 100Mbit WAN..but you know your thing... Cool

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 56941 WAP
TP-Link WR1043NDv2 -DD-WRT 56941 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 57515 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 57525 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 57515 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum