Linksys WRT1900AC/Marvell support

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Goto page Previous  1, 2, 3 ... 43, 44, 45 ... 152, 153, 154  Next
Author Message
johnnytucats
DD-WRT Novice


Joined: 14 Oct 2010
Posts: 4

PostPosted: Wed Aug 05, 2015 12:37    Post subject: Reply with quote
I'm really looking forward to this as I'm hoping it will allow me to create a proper VPN either on or behind this router.
Sponsor
slidermike
DD-WRT Guru


Joined: 11 Nov 2013
Posts: 1487
Location: USA

PostPosted: Sat Aug 08, 2015 21:25    Post subject: Reply with quote
Kong,
does this mean you now added official/open beta support for the WRT1900AC v1?

http://svn.dd-wrt.com/changeset/27589

_________________
Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode

R7000 specific Tips/Tricks.
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=264152
MrDoh
DD-WRT Guru


Joined: 04 Dec 2012
Posts: 647

PostPosted: Sat Aug 08, 2015 22:19    Post subject: Reply with quote
slidermike wrote:
Kong,
does this mean you now added official/open beta support for the WRT1900AC v1?

http://svn.dd-wrt.com/changeset/27589


Interesting source integration, open support still requires that Kong make the firmware images themselves public, of course.

Just went and looked...don't know if this was the integration to the development trunk or not, but all those "mvebu" integrations are WRT1900AC stuff. Whole bunch of them.
Antonius123
DD-WRT Novice


Joined: 23 Jan 2015
Posts: 12

PostPosted: Sun Aug 09, 2015 22:48    Post subject: great work Reply with quote
Wow you guys are working realy hard on this!

http://svn.dd-wrt.com/changeset/27591

http://svn.dd-wrt.com/changeset/27590

Can`t wait for this but i have to like the rest of us.

Keep up the good work if i could donate i would if you guys need any help of a senior sys admin just let me know and i help you in any way i can.
SubElement
DD-WRT Novice


Joined: 04 Apr 2015
Posts: 9

PostPosted: Tue Aug 11, 2015 10:16    Post subject: Reply with quote
I can feel it almost here! So close!

Very Happy Laughing
xsk3l3t0rx
DD-WRT Novice


Joined: 08 Jun 2015
Posts: 30

PostPosted: Tue Aug 11, 2015 13:14    Post subject: count me in! Reply with quote
i just read through the peacock rules and the FAQs on this site, i wanna get my feet wet with DDWRT. in due time, make it awesome kong! congrats to the team for your progress and dedication. you're all saving this router's life! (plus im sick of F5'ing this thread for 2months at work everyday lol)
Bronk-S
DD-WRT User


Joined: 26 Jun 2012
Posts: 282

PostPosted: Wed Aug 12, 2015 17:40    Post subject: Reply with quote
Subscribe to this thread, I'm really interested or either to the EA9200.

Kong I saw in your personal test builds some notes and a couple of builds, but I'm unable to read the issues tracking.

How confortable you feel to mention an aproximate % of working features in the builds ?

Many thanks and keep that way mates.

Regards from warm Seville's airport. Wink

_________________
7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga

slidermike
DD-WRT Guru


Joined: 11 Nov 2013
Posts: 1487
Location: USA

PostPosted: Thu Aug 13, 2015 21:16    Post subject: Reply with quote
I am not sure how many WRT1900AC v1 users are still waiting but Kong posted his build on his PTB page a couple of days ago.

http://www.desipro.de/ddwrt/WRT1900ACV1/

So I guess its open season for the WRT1900AC v1.
At least until BS gets it fully integrated into his main release betas.

_________________
Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode

R7000 specific Tips/Tricks.
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=264152
xsk3l3t0rx
DD-WRT Novice


Joined: 08 Jun 2015
Posts: 30

PostPosted: Thu Aug 13, 2015 23:04    Post subject: Reply with quote
slidermike wrote:
I am not sure how many WRT1900AC v1 users are still waiting but Kong posted his build on his PTB page a couple of days ago.

http://www.desipro.de/ddwrt/WRT1900ACV1/

So I guess its open season for the WRT1900AC v1.
At least until BS gets it fully integrated into his main release betas.


count me as one Wink i dont know why kong didnt mention this in this thread but thanks for the ups. is this a stable release now? or is this beta/rc. i'd prefer to wait if it isnt a stable release. i read the readme and im still not really sure.

also: after much googling, i was not able to determine if the wrt1900ac is running a broadcom SoC or not. i have a v1, and i see that this thread is in the Broadcom subcategory, but i would like to know for sure, as im not sure if a 30/30/30 is necessary for this router since at the very top of the peacock thread it mentions "for Broadcom only", and i'd hate to fuck this up.

if i should wait til its a bit more user-friendly to install, i'll wait, but i feel relatively confident that if i follow the steps in the readme VERBATIM with no other instructions, that i'd be perfectly fine.
MrDoh
DD-WRT Guru


Joined: 04 Dec 2012
Posts: 647

PostPosted: Fri Aug 14, 2015 0:09    Post subject: Reply with quote
Linksys WRT1900AC, WRT1200AC, etc. use Marvell chipsets, not Broadcom. I don't think that 30-30-30 resets are any more effective than just resetting for any of the new routers (ARM or Marvell).
Goldencoin5
DD-WRT Novice


Joined: 14 Aug 2015
Posts: 5

PostPosted: Fri Aug 14, 2015 0:37    Post subject: Reply with quote
i can't be able to put this so awaiting build to my mamba.
really can't understand that why stock or AA builds have the ability to deal with factory bad blocks and provide a smooth installation.
CC builds and this DD-Wrt build can't handle the bad blocks so far.
may <Kong> address this issue also.
i just tried the test build but no luck'
MrDoh' 've you any clue to deal with such prob.
here is my post without solution = https://community.linksys.com/t5/Wireless-Routers/WRT1900AC-and-OpenWrt/m-p/963018#M306183

right now <Kong>'s test build is based on (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r42925)
here is my router's kernel log with <Kong> installation :



Code:
Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.18.19 (bluebat@opensuse) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r42925) ) #59 SMP Mon Jul 27 21:57:06 CEST 2015
[    0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine model: Linksys WRT1900AC (Mamba)
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] PERCPU: Embedded 9 pages/cpu @cfdd9000 s7040 r8192 d21632 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) uboot_active_root=5 ro origfstype=jffs2 init=/sbin/init
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 254060K/262144K available (3918K kernel code, 180K rwdata, 1000K rodata, 240K init, 306K bss, 8084K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc04d5e24   (4920 kB)
[    0.000000]       .init : 0xc04d6000 - 0xc0512000   ( 240 kB)
[    0.000000]       .data : 0xc0512000 - 0xc053f060   ( 181 kB)
[    0.000000]        .bss : 0xc053f060 - 0xc058b8ec   ( 307 kB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]    RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] Aurora cache controller enabled, 32 ways, 2048 kB
[    0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a69ef12
[    0.000000] CPU freq armada-xp 1200000000
[    0.000007] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798691800ns
[    0.000225] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    0.040055] pid_max: default: 32768 minimum: 301
[    0.040147] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040156] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040482] CPU: Testing write buffer coherency: ok
[    0.040630] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.043107] Setting up static identity map for 0x12f98 - 0x12ff0
[    0.043387] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x2
[    0.043518] mvebu-pmsu: Initializing Power Management Service Unit
[    0.044355] Booting CPU 1
[    0.044634] CPU1: Booted secondary processor
[    0.080043] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.080104] Brought up 2 CPUs
[    0.080118] SMP: Total of 2 processors activated (2382.23 BogoMIPS).
[    0.080123] CPU: All CPU(s) started in SVC mode.
[    0.080667] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    0.080855] pinctrl core: initialized pinctrl subsystem
[    0.083563] NET: Registered protocol family 16
[    0.083795] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.110065] cpuidle: using governor ladder
[    0.141045] SCSI subsystem initialized
[    0.141936] Switched to clocksource armada_370_xp_clocksource
[    0.142670] NET: Registered protocol family 2
[    0.143175] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.143198] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.143221] TCP: Hash tables configured (established 2048 bind 2048)
[    0.143259] TCP: reno registered
[    0.143270] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.143288] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.143419] NET: Registered protocol family 1
[    0.144419] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.145365] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.145379] jffs2: version 2.2. (NAND) (SUMMARY)  (LZMA) (RTIME) (CMODE_PRIORITY) © 2001-2006 Red Hat, Inc.
[    0.145537] msgmni has been set to 496
[    0.146367] io scheduler noop registered
[    0.146379] io scheduler deadline registered (default)
[    0.146964] armada-xp-pinctrl f1018000.pin-ctrl: registered pinctrl driver
[    0.147422] irq: Cannot allocate irq_descs @ IRQ38, assuming pre-allocated
[    0.147735] irq: Cannot allocate irq_descs @ IRQ70, assuming pre-allocated
[    0.148202] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[    0.148215] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.148225] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[    0.148235] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.148684] PCI: bus0: Fast back to back transfers disabled
[    0.148696] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.148707] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.148717] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.149108] PCI: bus1: Fast back to back transfers disabled
[    0.149530] PCI: bus2: Fast back to back transfers disabled
[    0.149929] PCI: bus3: Fast back to back transfers disabled
[    0.150078] pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
[    0.150091] pci 0000:00:02.0: BAR 8: assigned [mem 0xf8200000-0xf83fffff]
[    0.150101] pci 0000:00:03.0: BAR 8: assigned [mem 0xf8400000-0xf85fffff]
[    0.150114] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8007fff 64bit]
[    0.150135] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.150146] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80fffff]
[    0.150161] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8200000-0xf82fffff 64bit pref]
[    0.150182] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8300000-0xf83fffff 64bit pref]
[    0.150202] pci 0000:00:02.0: PCI bridge to [bus 02]
[    0.150211] pci 0000:00:02.0:   bridge window [mem 0xf8200000-0xf83fffff]
[    0.150225] pci 0000:03:00.0: BAR 0: assigned [mem 0xf8400000-0xf84fffff 64bit pref]
[    0.150244] pci 0000:03:00.0: BAR 2: assigned [mem 0xf8500000-0xf85fffff 64bit pref]
[    0.150261] pci 0000:00:03.0: PCI bridge to [bus 03]
[    0.150271] pci 0000:00:03.0:   bridge window [mem 0xf8400000-0xf85fffff]
[    0.150314] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    0.150336] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.150491] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.182015] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.222011] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.222107] mv_xor f10f0900.xor: Marvell shared XOR driver
[    0.262003] mv_xor f10f0900.xor: Marvell XOR: ( xor cpy )
[    0.302002] mv_xor f10f0900.xor: Marvell XOR: ( xor cpy )
[    0.302184] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.302620] console [ttyS0] disabled
[    0.322632] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 20, base_baud = 15625000) is a 16550A
[    0.987982] console [ttyS0] enabled
[    0.992230] pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device
[    0.999846] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[    1.006236] nand: AMD/Spansion S34ML01G1
[    1.010171] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    1.015861] pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
[    1.022952] Bad block table found at page 65472, version 0x01
[    1.029005] Bad block table found at page 65408, version 0x01
[    1.034940] nand_read_bbt: bad block at 0x000000a20000
[    1.040095] nand_read_bbt: bad block at 0x000003000000
[    1.045261] nand_read_bbt: bad block at 0x000003240000
[    1.050416] nand_read_bbt: bad block at 0x000006580000
[    1.055577] nand_read_bbt: bad block at 0x000006860000
[    1.060908] 10 ofpart partitions found on MTD device pxa3xx_nand-0
[    1.067122] Creating 10 MTD partitions on "pxa3xx_nand-0":
[    1.072637] 0x000000000000-0x000000100000 : "u-boot"
[    1.078082] 0x000000100000-0x000000140000 : "u_env"
[    1.083406] 0x000000140000-0x000000180000 : "s_env"
[    1.088685] 0x000000900000-0x000000a00000 : "devinfo"
[    1.094173] 0x000000a00000-0x000003100000 : "kernel1"
[    1.099714] 0x000000d00000-0x000003200000 : "ubi"
[    1.104914] 0x000003200000-0x000005900000 : "linux"
[    1.110286] 0x000003500000-0x000005900000 : "rootfs2"
[    1.115854] 0x000005900000-0x000005940000 : "nvram"
[    1.121167] 0x000005a00000-0x000008000000 : "syscfg"
[    1.127177] m25p80 spi0.0: mr25h256 (32 Kbytes)
[    1.132886] libphy: Fixed MDIO Bus: probed
[    1.137000] tun: Universal TUN/TAP device driver, 1.6
[    1.142090] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.148458] libphy: orion_mdio_bus: probed
[    1.154088] mvneta f1070000.ethernet eth0: Using random mac address 1a:0d:4d:28:15:20
[    1.163155] mvneta f1074000.ethernet eth1: Using random mac address a6:d2:a5:51:a7:70
[    1.171079] PPP generic driver version 2.4.2
[    1.175492] PPP BSD Compression module registered
[    1.180216] PPP Deflate Compression module registered
[    1.185309] PPP MPPE Compression module registered
[    1.190119] NET: Registered protocol family 24
[    1.194764] trying to register driver cpufreq-dt
[    1.201953] driver cpufreq-dt up and running
[    1.207596] GACT probability NOT on
[    1.211112] Mirror/redirect action on
[    1.214873] Simple TC action Loaded
[    1.219205] netem: version 1.3
[    1.222366] u32 classifier
[    1.225090]     Performance counters on
[    1.228940]     input device check on
[    1.232639]     Actions configured
[    1.236111] Netfilter messages via NETLINK v0.30.
[    1.240895] nf_conntrack version 0.5.0 (3969 buckets, 15876 max)
[    1.247995] nf_conntrack_rtsp v0.6.21 loading
[    1.252950] xt_time: kernel timezone is -0000
[    1.257370] ip_set: protocol 6
[    1.260792] gre: GRE over IPv4 demultiplexor driver
[    1.266042] nf_nat_rtsp v0.6.21 loading
[    1.269944] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.275619] TCP: bic registered
[    1.278791] TCP: cubic registered
[    1.282154] TCP: dctcp registered
[    1.285497] TCP: westwood registered
[    1.289096] TCP: highspeed registered
[    1.292828] TCP: hybla registered
[    1.296172] TCP: htcp registered
[    1.299421] TCP: vegas registered
[    1.302805] TCP: veno registered
[    1.306063] TCP: scalable registered
[    1.309661] TCP: lp registered
[    1.312798] TCP: yeah registered
[    1.316055] TCP: illinois registered
[    1.319653] NET: Registered protocol family 17
[    1.324239] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.336973] Bridge firewalling registered
[    1.341011] 8021q: 802.1Q VLAN Support v1.8
[    1.345435] Registering SWP/SWPB emulation handler
[    1.352614] nvram_init kernelspace:  131072 bytes
[    1.357353] searching for nvram
[    1.360526] nvram size = -1068972814
[    1.420845] UBI error: ubi_auto_attach: no valid UBI magic found inside mtd5
[    1.428413] mvsw61xx 1000000003.mvsw61xx: Found MV88E6172 at f1072004.mdio-mi:10
[    1.435912] mvsw61xx 1000000003.mvsw61xx: Using direct addressing
[    1.442163] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.451018] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
[    1.458812] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    1.466373] Please append a correct "root=" boot option; here are the available partitions:
[    1.474815] 1f00            1024 mtdblock0  (driver?)
[    1.479909] 1f01             256 mtdblock1  (driver?)
[    1.485053] 1f02             256 mtdblock2  (driver?)
[    1.490141] 1f03            1024 mtdblock3  (driver?)
[    1.495284] 1f04           39936 mtdblock4  (driver?)
[    1.500372] 1f05           37888 mtdblock5  (driver?)
[    1.505514] 1f06           39936 mtdblock6  (driver?)
[    1.510602] 1f07           36864 mtdblock7  (driver?)
[    1.515746] 1f08             256 mtdblock8  (driver?)
[    1.520833] 1f09           38912 mtdblock9  (driver?)
[    1.525990] 1f0a              32 mtdblock10  (driver?)
[    1.531163] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    1.539494] CPU1: stopping
[    1.542231] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.18.19 #59
[    1.548345] Backtrace:
[    1.550833] [<c001b7d4>] (dump_backtrace) from [<c001bb64>] (show_stack+0x18/0x1c)
[    1.558427]  r6:00000000 r5:00000000 r4:c0527778 r3:00000000
[    1.564172] [<c001bb4c>] (show_stack) from [<c01968a8>] (dump_stack+0x8c/0x9c)
[    1.571428] [<c019681c>] (dump_stack) from [<c001dcfc>] (handle_IPI+0xe8/0x174)
[    1.578760]  r5:c050f8f8 r4:00000001
[    1.582387] [<c001dc14>] (handle_IPI) from [<c000870c>] (armada_370_xp_handle_irq+0xa8/0xe0)
[    1.590850]  r6:c0560b74 r5:00000020 r4:00000005 r3:00000020
[    1.596596] [<c0008664>] (armada_370_xp_handle_irq) from [<c00097e0>] (__irq_svc+0x40/0x54)
[    1.604975] Exception stack(0xcf853f28 to 0xcf853f70)
[    1.610053] 3f20:                   0071be70 00000000 3b9aca00 00000000 5b338208 00000000
[    1.618265] 3f40: 00000002 cfde2a48 00000098 00000000 c051650c cf853f9c 0000001a cf853f70
[    1.626472] 3f60: 00000006 c0294c60 20000153 ffffffff
[    1.631540]  r10:c051650c r9:00000000 r8:00000098 r7:cf853f5c r6:ffffffff r5:20000153
[    1.639470]  r4:c0294c60
[    1.642042] [<c0294c04>] (cpuidle_enter_state) from [<c0294e28>] (cpuidle_enter+0x1c/0x20)
[    1.650332]  r9:00000000 r8:00000098 r7:c045b770 r6:c0538240 r5:cfde2a48 r4:cf852030
[    1.658189] [<c0294e0c>] (cpuidle_enter) from [<c0052e44>] (cpu_startup_entry+0x288/0x2a8)
[    1.666491] [<c0052bbc>] (cpu_startup_entry) from [<c001d9e4>] (secondary_start_kernel+0x144/0x14c)
[    1.675564]  r7:c0540240
[    1.678129] [<c001d8a0>] (secondary_start_kernel) from [<00008844>] (0x8844)
[    1.685198]  r5:00000015 r4:0f83c06a
[    1.688822] Rebooting in 5 seconds..
xsk3l3t0rx
DD-WRT Novice


Joined: 08 Jun 2015
Posts: 30

PostPosted: Fri Aug 14, 2015 0:53    Post subject: Reply with quote
MrDoh wrote:
Linksys WRT1900AC, WRT1200AC, etc. use Marvell chipsets, not Broadcom. I don't think that 30-30-30 resets are any more effective than just resetting for any of the new routers (ARM or Marvell).


may i ask why this thread is located in the broadcom section then? i was pretty sure it was marvell chipsets, but i just wanted to hear it from a dd-wrt dev or person with more familiarity on the topic. so you are saying that the 30/30/30 method is no longer necessary? can i get a few other people to chime on this as well?

its hard for someone relatively new on this forum because usually people just say "read the stickies", but the sticky itself says right at the top "regardless of the date posted, this sticky is always kept up to date", yet you just told me this is NOT a broadcom router, it DOESNT need a 30/30/30, nor is it an effective method on any new ARM/marvell routers. also, this whole thread is in a broadcom subforum.

surely you can see why i might be confused...
Rafkat
DD-WRT Novice


Joined: 20 Dec 2011
Posts: 24

PostPosted: Fri Aug 14, 2015 9:00    Post subject: Reply with quote
slidermike wrote:
I am not sure how many WRT1900AC v1 users are still waiting but Kong posted his build on his PTB page a couple of days ago.

http://www.desipro.de/ddwrt/WRT1900ACV1/

So I guess its open season for the WRT1900AC v1.
At least until BS gets it fully integrated into his main release betas.


Installed 12 hours ago, so far so good. Thanks.

Update 1: Couldn't find the option to activate JFFS (is it possible on this router?) and as a consequence, couldn't activate Open Radius server.
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Aug 14, 2015 16:26    Post subject: Reply with quote
Goldencoin5 wrote:
i can't be able to put this so awaiting build to my mamba.
really can't understand that why stock or AA builds have the ability to deal with factory bad blocks and provide a smooth installation.
CC builds and this DD-Wrt build can't handle the bad


That is nonsense, you either used linksys fw or uboot to flash dd-wrt and obviously it was not correctly flashed since ubi part is corrupt, of course it is also possible, that your hw is broken.

Thus no dd-wrt or openwrt issue.
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Aug 14, 2015 16:28    Post subject: Reply with quote
Rafkat wrote:
slidermike wrote:
I am not sure how many WRT1900AC v1 users are still waiting but Kong posted his build on his PTB page a couple of days ago.

http://www.desipro.de/ddwrt/WRT1900ACV1/

So I guess its open season for the WRT1900AC v1.
At least until BS gets it fully integrated into his main release betas.


Installed 12 hours ago, so far so good. Thanks.

Update 1: Couldn't find the option to activate JFFS (is it possible on this router?) and as a consequence, couldn't activate Open Radius server.


Radius should also work if you use usb disk and mount it to /jffs via usb setup.

JFFS is currently not enabled since the dual boot uses more flash.
Goto page Previous  1, 2, 3 ... 43, 44, 45 ... 152, 153, 154  Next Display posts from previous:    Page 44 of 154
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) 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