I just flashed r48479 on my WNDR3700v1 I have laying around because I am able to serial into it, but it booted fine (it looks like it has the 4.1.15 kernel though). I cannot find the r48616 though, as you probably removed it. Wouldn't mind trying it and report the serial log here.
Topic: Optimized and feature rich trunk build for select routers
The content of this topic has been archived between 20 Aug 2014 and 5 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Page 130 of 155
I don't know if I am the only one who is experiencing this, but my R8000 is bricking. Starting with the most recent, I have gone back to Jan 16, and they all are becoming doorstops for me. Will be trying Jan 14 in a couple of minutes. See here: http://pastebin.com/m42wHWHn
edit:
yup, all posted images are bricking my R8000. perhaps it is just my special one.
reverting back to stock.
(Last edited by mojolacerator on 6 Feb 2016, 18:52)
Saw that the 48616 was back and decided to flash it and I got the bootloop on the WNDR3700v1 now, here is the log:
▒
U-Boot 1.1.4DNI1.6 (May 22 2009 - 16:37:44)
WNDR3700U (ar7100) U-boot 0.0.12
DRAM: b8050000: 0xc0140180
64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 315k for U-Boot at: 83fb0000
Reserving 192k for malloc() at: 83f80000
Reserving 44 Bytes for Board Info at: 83f7ffd4
Reserving 36 Bytes for Global Data at: 83f7ffb0
Reserving 128k for boot params() at: 83f5ffb0
Stack Pointer at: 83f5ff98
Now running in RAM - U-Boot at: 83fb0000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash: 8 MB
In: serial
Out: serial
Err: serial
Net: ag7100_enet_initialize...
CHH:mac: 0 if: 2
CHH:mac:verify: 0 if: 00000002
: cfg1 0xf cfg2 0x7014
eth0: xx:xx:xx:xx:xx
eth0 up
CHH:mac: 1 if: 1
CHH:mac:verify: 1 if: 00000001
: cfg1 0xf cfg2 0x7014
eth1: xx:xx:xx:xx:xx
eth1 up
eth0, eth1
Trying eth0
: unit 0 phy is up...RGMii 1000Mbps full duplex
#259:ag7100_set_mac_from_link
: pll reg 0x18050010: 0x11110000
: cfg_1: 0x1ff0000
: cfg_2: 0x3ff
: cfg_3: 0x8001ff
: cfg_4: 0xffff
: cfg_5: 0xfffef
: done cfg2 0x7215 ifctl 0x40605060 miictrl 0x22
Client starts...[Listening] for ADVERTISE...TTT
Retry count exceeded; boot the image as usual
nmrp server is stopped or failed !
Hit any key to stop autoboot: 0
Verifying Checksum ... OK
### SQUASHFS loading 'image/uImage' to 0x80800000
### SQUASHFS load complete: 1441792 bytes loaded to 0x80800000
## Booting image at 80800000 ...
Image Name: MIPS OpenWrt Linux-4.4
Created: 2016-02-01 22:38:28 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1412745 Bytes = 1.3 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 67108864
Starting kernel ...
[ 0.000000] Linux version 4.4.0 (trondah@ff0) (gcc version 5.2.0 (OpenWrt GCC 5.2.0 r48616) ) #1 Sat Feb 6 13:25:58 UTC 2016
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[ 0.000000] SoC: Atheros AR7161 rev 2
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 04000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] No valid device tree found, continuing without
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
[ 0.000000] Kernel command line: board=WNDR3700 mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,7680k(firmware),64k(art)ro console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 60164K/65536K available (3062K kernel code, 158K rwdata, 660K rodata, 272K init, 200K bss, 5372K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.000000] Clocks: CPU:680.000MHz, DDR:340.000MHz, AHB:170.000MHz, Ref:40.000MHz
[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 5621354254 ns
[ 0.000008] sched_clock: 32 bits at 340MHz, resolution 2ns, wraps every 6316128254ns
[ 0.007736] Calibrating delay loop... 452.19 BogoMIPS (lpj=2260992)
[ 0.070376] pid_max: default: 32768 minimum: 301
[ 0.075080] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.081606] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090665] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.101026] NET: Registered protocol family 16
[ 0.106331] MIPS: machine is NETGEAR WNDR3700/WNDR3800/WNDRMAC
[ 2.752427] registering PCI controller with io_map_base unset
[ 2.765701] PCI host bridge to bus 0000:00
[ 2.769761] pci_bus 0000:00: root bus resource [mem 0x10000000-0x16ffffff]
[ 2.776548] pci_bus 0000:00: root bus resource [io 0x0000]
[ 2.782098] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[ 2.788845] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[ 2.796813] pci 0000:00:11.0: fixup device configuration
[ 2.803487] pci 0000:00:12.0: fixup device configuration
[ 2.810177] pci 0000:00:11.0: BAR 0: assigned [mem 0x10000000-0x1000ffff]
[ 2.816869] pci 0000:00:12.0: BAR 0: assigned [mem 0x10010000-0x1001ffff]
[ 2.823651] pci 0000:00:11.0: using irq 40 for pin 1
[ 2.828551] pci 0000:00:12.0: using irq 41 for pin 1
[ 2.834235] clocksource: Switched to clocksource MIPS
[ 2.840224] NET: Registered protocol family 2
[ 2.845321] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 2.852200] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 2.858561] TCP: Hash tables configured (established 1024 bind 1024)
[ 2.864927] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 2.870671] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 2.877136] NET: Registered protocol family 1
[ 2.882332] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 2.902107] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 2.907913] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 2.919629] io scheduler noop registered
[ 2.923468] io scheduler deadline registered (default)
[ 2.929025] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
¦[ 2.959199] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 10625000) is a 16550A
[ 2.967822] console [ttyS0] enabled
[ 2.967822] console [ttyS0] enabled
[ 2.974738] bootconsole [early0] disabled
[ 2.974738] bootconsole [early0] disabled
[ 2.985421] m25p80 spi0.0: found mx25l6405d, expected m25p80
[ 2.991085] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
[ 2.996027] 4 cmdlinepart partitions found on MTD device spi0.0
[ 3.001935] Creating 4 MTD partitions on "spi0.0":
[ 3.006740] 0x000000000000-0x000000050000 : "u-boot"
[ 3.013438] 0x000000050000-0x000000070000 : "u-boot-env"
[ 3.020123] 0x000000070000-0x0000007f0000 : "firmware"
[ 3.032689] 2 netgear-fw partitions found on MTD device firmware
[ 3.038750] 0x000000070000-0x0000001ca440 : "kernel"
[ 3.045031] 0x0000001ca440-0x0000007f0000 : "rootfs"
[ 3.051296] mtd: device 4 (rootfs) set to be root filesystem
[ 3.057056] 1 squashfs-split partitions found on MTD device rootfs
[ 3.063237] 0x000000790000-0x0000007f0000 : "rootfs_data"
[ 3.069991] 0x0000007f0000-0x000000800000 : "art"
[ 3.076997] Realtek RTL8366S ethernet switch driver version 0.2.2
[ 3.083121] rtl8366s rtl8366s: using GPIO pins 5 (SDA) and 7 (SCK)
[ 3.089430] rtl8366s rtl8366s: RTL8366 ver. 1 chip found
[ 3.140583] libphy: rtl8366s: probed
[ 3.465930] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
[ 3.786052] ag71xx ag71xx.1: connected to PHY at rtl8366s:04 [uid=001cc960, driver=Generic PHY]
[ 3.795370] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RGMII
[ 3.803347] NET: Registered protocol family 10
[ 3.811088] NET: Registered protocol family 17
[ 3.815645] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 3.828287] Bridge firewalling registered
[ 3.832393] 8021q: 802.1Q VLAN Support v1.8
[ 3.843864] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[ 3.851797] Freeing unused kernel memory: 272K (8042c000 - 80470000)
[ 4.883335] init: Console is alive
[ 4.886987] init: - watchdog -
[ 6.499824] usbcore: registered new interface driver usbfs
[ 6.505429] usbcore: registered new interface driver hub
[ 6.510801] usbcore: registered new device driver usb
[ 6.520413] exFAT: Version 1.2.9
[ 6.551875] SCSI subsystem initialized
[ 6.560486] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 6.568351] ehci-platform: EHCI generic platform driver
[ 6.573639] ehci-platform ehci-platform: EHCI Host Controller
[ 6.579449] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[ 6.587471] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[ 6.604265] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[ 6.611284] hub 1-0:1.0: USB hub found
[ 6.615343] hub 1-0:1.0: 2 ports detected
[ 6.621771] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 6.629216] ohci-platform: OHCI generic platform driver
[ 6.634576] ohci-platform ohci-platform: Generic Platform OHCI controller
[ 6.641374] ohci-platform ohci-platform: new USB bus registered, assigned bus number 2
[ 6.649362] ohci-platform ohci-platform: irq 14, io mem 0x1c000000
[ 6.719037] hub 2-0:1.0: USB hub found
[ 6.723048] hub 2-0:1.0: 2 ports detected
[ 6.730811] usbcore: registered new interface driver usb-storage
[ 6.893657] init: - preinit -
[ 7.554317] eth0: link up (1000Mbps/Full duplex)
▒
U-Boot 1.1.4DNI1.6 (May 22 2009 - 16:37:44)Stopped the log after the second U-Boot message, that was the automatic reboot, doesn't seem to "tell" the error it seems.
(Last edited by johan81 on 6 Feb 2016, 21:16)
exrwagon wrote:
hnyman wrote:arokh wrote:@extenue
Create a ticket in the proper place, or send me a fix. I am not the developer of any of the components, I just run make.
Extenue's problem is Luci issue #620, which has been fixed two days ago by #632, so the next build should have the fix.
https://github.com/openwrt/luci/issues/620
https://github.com/openwrt/luci/pull/634Build 48616 fixes this issue (Archer C7 v2).
Thanks guyz
Can you help me to share (smb) an external HD?
I connect to USB but I can see in SMB share.
Regards,
Simpy wrote:
same, r48479 and r48616 won't fully boot for my WNDR3700v4 either (when flashed with sysupgrade.tar [with or without keep settings])
Thanks @Simpy, you saved me on r48616 before I tried!
arokh wrote:
Probably related to this:
https://dev.openwrt.org/changeset/48456/trunk
I used to add this patch manually, then it went upstream, but now it seems they removed it because it can overwrite the caldata partition. I could add it back in, anyone got any input on this?
@arokh, if you want to create a build with the patch added back in I'm happy to try (I don't have a serial but I can add one if it does go horribly wrong!)
What exactly needs to be modified to allow SSH, as the WRT1200 firmware refuses authentication even with all custom firewall rules and port forwards disabled. This is due to one of the modifications done to the firmware, as this doesn't occur with any other firmware.
I also created a new dropbear instance specifically for LAN, and the connection was still denied. I've tried both with and without key authentication, however I'm at a loss since this should not be occurring. The error message is always "Network error: connection refused", even with the password login boxes checked (which should not be occurring until after a password has been entered incorrectly).
It also appears the System - Administration page is broken, which could explain the above issues. For example, clearing the SSH keys box and then clicking save and apply results in a page refresh with the keys still there.
Something else I noticed, albeit this could have been completely disabled in firmware running the 4.x kernel, is telnet is completely disabled. On firmware running the 3.x kernel, telnet is enabled until you set an admin password, at which point telnet is disabled and you can SSH in. I'm wondering if this was disabled in firmwares running the 4.x kernel, as I just flashed trunk and telnet was disabled prior to setting an admin password as well.
(Last edited by JW0914 on 7 Feb 2016, 22:14)
@johan81
Thanks for that, unfortunately it doesn't contain any indication on what went wrong as you say. Looks like the kernel starts to boot fine though. Might be something related to the 4.4 kernel upgrade. Did you try any recent trunk snapshot? I'm rebuilding with 4.1 kernel.
arokh wrote:
@johan81
Thanks for that, unfortunately it doesn't contain any indication on what went wrong as you say. Looks like the kernel starts to boot fine though. Might be something related to the 4.4 kernel upgrade. Did you try any recent trunk snapshot? I'm rebuilding with 4.1 kernel.
lol I just realized your reply was to someone else. Either way, I'm sure the info will be helpful
I did, I flashed trunk's update from today and was able to ssh in without issue. I really love your firmware, and you obviously spent a decent amount of time on it, but without the ability to ssh it to transfer configs, it's quite an inconvenience.
The WRT1200 I'm setting up is someone else's and I will be flashing your firmware to my WRT1900, so if it occurs on there as well and there's any information you need me to grab, let me know. I could also get you whatever information you need from the WRT1200, however It would probably be tomorrow before I could get back to you (as I'll reflash your firmware after getting everything setup and backup taken of trunk).
I suspect it has something to do with what's going on on the backend of the System - Administration page, as I'd be willing to bet if it's not erasing keys when told to do so, it's probably not completely applying other settings on there as well, such as the SSH port (which would explain the connection refused error).
(Last edited by JW0914 on 8 Feb 2016, 00:13)
You'd need console access to find out what's going on. I know there's been someone else reporting the same issue, but I really haven't a clue as to why it would not work on the WRT1200. It's the exact same build and root filesystem as the WRT1900 which I hear works well.
I was able to tftp the r48479 build onto my WNDR3700v1 and it's working normally again, so it looks like you were right and it was a 4.4 issue.
arokh wrote:
@johan81
Thanks for that, unfortunately it doesn't contain any indication on what went wrong as you say. Looks like the kernel starts to boot fine though. Might be something related to the 4.4 kernel upgrade.
Just documenting here: I made a kernel 4.4 test build from my own wndr3700 build and ended up with similar endless reboot loop :-(
Really interesting that there is nothing special in the boot log until the reboot. I compared also the .configs and noticed just one possibly interesting difference. 4.4 .config has this new line:
CONFIG_USES_DEVICETREE=ywhich then is also visible on Johan81's bootlog:
[ 0.000000] No valid device tree found, continuing without
[ 0.000000] Zone ranges:I have no idea if that could lead to trouble (kernel does not find devicetree, but on Openwrt side something might need if as it is supposedly enabled), but that is roughly the only thing that points out.
arokh wrote:
You'd need console access to find out what's going on. I know there's been someone else reporting the same issue, but I really haven't a clue as to why it would not work on the WRT1200. It's the exact same build and root filesystem as the WRT1900 which I hear works well.
I installed your firmware on my WRT1900 this morning and experienced no issues. Once I finalize everything and get a backup of the WRT1200, I'm going to try installing your firmware again, as I kept having other issues like wireless working, then completely going out, one booting into the previously installed firmware when it loaded it as a recovery version, and a few others... I realized all the issues were being caused by running the WRT1900 and WRT1200 in the same vicinity, however I haven't the slightest why both being on at the same time 10' feet apart would create issues, just that as soon as I turned one off, the other worked fine again and vice versa.
I'd be curious to know if the other user experiencing issues had another wifi router in the same vicinity as the WRT1200 or not. Perhaps I'm missing something, as it doesn't make any sense to me why having them both on and in the same vicinity would cause issues with the other. It didn't matter if they were apart of the same LAN, if one was only connected to my laptop via LAN but not connected to anything else, or if one was disconnected from everything but was simply on. I thought it was wireless radio drivers causing the WiFi issues until I happened to have only the WRT1900 on while loading the firmware this morning.
(Last edited by JW0914 on 8 Feb 2016, 19:40)
mojolacerator wrote:
I don't know if I am the only one who is experiencing this, but my R8000 is bricking. Starting with the most recent, I have gone back to Jan 16, and they all are becoming doorstops for me. Will be trying Jan 14 in a couple of minutes. See here: http://pastebin.com/m42wHWHn
edit:
yup, all posted images are bricking my R8000. perhaps it is just my special one.
reverting back to stock.
Me too.
I go with all the trunks with my R8000, but all of them make it bricked.
How about yours?
Trunk bricks mine as well.
Had this problem with the R8000 a few months back, but they fixed it. Back to
the drawing board I guess. I really don't like the stock firmware, ddwrt(Kong)
has an image for the R8000, but it doesn't work well in "Access Point" mode for me.
Why is samba so slow on Archer C7 v2? 500kb/s from/to 128GB USB flash drive ext4, r47896.
Tested on PC and tablet and phone.
Why do you did not try a newer version? Which pattern? Small, big files, Random, Sequential?
Hexxer2 wrote:
Why do you did not try a newer version? Which pattern? Small, big files, Random, Sequential?
I use samba to watch videos on my tablet (they keep stopping randomly). I tested with some 200Mb files, this is the speed I got.
Downloading from internet, speed is not a problem.
I was just asking if it is some known problem, i'll update over the weekend. Speed was OK with some previous builds, but I wasn't using samba much recently.
Updated to r48717
Archer C7 v2
Everything working fine.
Did anyone try the last r48616 rebuild for wndr3x00? I switched to 4.1 kernel again, should work. New build with 4.1 kernel for r8000 coming as well.
(Last edited by arokh on 13 Feb 2016, 19:11)
Will try the R8000 build when I see it up.
48616 rebuild working fine for me on the WNDR3700v1
Using the latest (r48616) build on my WRT1900ACv1, and it's doing great. I do have a question, though. I see references to the "sensors" command relative to openWRT for the WRT1900AC, but I don't see it in this build. I assume that it's in a package that's not included in this build, then. If the package is compatible with this build, does anyone know what package that would be? Is it available through opkg? Or is there an equivalent command for getting CPU and radio temperatures that I'm not aware of in this build?
Couple of other things that I'm hoping are in the pipeline...the internet connection light isn't working in this build, but it does work on the latest trunk snapshot, so it seems that's coming. The other one is that ping times for my iPad Air are much lower on the most recent BrainSlayer dd-wrt releases, they went from about 38ms to 18ms on the Ookla internet speed test. So I'm thinking that they have picked up a wireless driver change from Marvell that affected that Apple client. Something else to look forward to in a newer build (I hope).
Anyways, really appreciate all the work that goes into getting this put together and working so well. Thanks so much!
Update: I see that r48717 just appeared. Looks like neither the internet connection light or ping time improvement is in r48717, but it is working well so far.
(Last edited by RogerSC on 13 Feb 2016, 21:17)
Seems latest build revert to 4.1.x kernel in C5. Its correct?
Sorry, posts 3251 to 3250 are missing from our archive.
Page 130 of 155