Build for Linksys EA9500


#103

Oh great! That saves me some work :slight_smile:


#104

So what needs to happen to have the EA9500 build into the normal release of Lede.

It is working perfect for me right now. I'm about to put it into more real life action as my main router.


#105

Good question. I've submitted a few patches to the mainline. When they get accepted, we should have official OpenWrt releases.


#106

Hey folks, enjoyed the read and props to npcomplete on this build. My question is, are the serial pins blocked thru the vent holes by the plastic reinforcement cover cause it would be sweet to just slide in small clips thru the holes and not void the warranty. TIA


#107

I doubt that's possible.


#108

could you take a photo with the top cover off when you get a chance?


#109

The pins are covered by a metal barrier (black in color). See: https://www.snbforums.com/threads/ea9500-serial-console-to-cfe.35228/


#110

yeah saw that oh well it was a thought thanks again


#111

It's actually pretty straight forward to open the housing when you follow ncomplete's link.

I ended up adding a headphone plug to the housing so I can connect now all the time without opening the housing.

But I'm very pleases with the result of the built with the 4.14 kernel I have 867Mbs on both 5GHz wifi and ncomplete helped me compiling the firmware which now works and I can compile new packages myself.

Hope it will be part of Lede in the near future.


#112

Thank you so much for this build npcomplete. I've had a love/hate relationship with the ea9500 since it first came out and it's truly nice to finally be able to customize till my heart's content.

I have run into a few quirks (probably just me missing something :smile: ).

  1. I can only get radio0 (5ghz) to work with channel 36, 80 MHz, US, power 20. Any other option causes it to not enable and fall back to client from master.
  2. I can only get radio2 (5ghz) to work with channel 120, 40 MHz, US, power 20. Any other option causes it to not enable and fall back to client from master.
  3. I have a centurylink gigabit connection that requires pppoe and the wan port to be tagged 201. Everytime I try to set this up in the network config I end up losing access and having to factory reset. I think it has something to do with the tagging of eth0 and eth1 with the cpu, and this being overwritten when I try to create the config switch to tag the wan with 201.

Thanks again for all your work on this!


#113

hey guys got a question for npcomplete's build. With the help of chadster766 (verified by him) on linksys' site a trouble ticket has been opened as to why the max advertised data rate cant be negotiated with any setting changes. Just wondering if yall have been able to acquire the 2166 for 5ghz and the 1000 for the 2.4ghz bands? TIA


#114

did you try the latest version?


#115

i havent tried any version im debating on tearing it open flashing lede or returning before i cant


#116

Replace 102 in /etc/fix_interfaces.sh to 201

Then in network config change wan config to

config interface 'wan'
        option type 'bridge'
        option ifname 'wan eth0.201'
        option proto 'pppoe'
        option username 'xxxxxxxx'
        option password 'yyyyyyyy'

#117

lol moot point praise science i didnt open it the ethernet crapped out, gotta return it and ponder some more. thanks though


#118

having some trouble with mtdblock6

I have not seen anything that does not work due to it, but is there something I could do to fix this?

I see this is the failsafe partition --> maybe it does not matter at all?

[    4.089566] 5 bcm47xxpart partitions found on MTD device brcmnand.0
[    4.095846] Creating 5 MTD partitions on "brcmnand.0":
[    4.100999] 0x000000000000-0x000000080000 : "boot"
[    4.106263] 0x000000080000-0x000000180000 : "nvram"
[    4.111550] 0x000000180000-0x000000200000 : "nvram"
[    4.116836] 0x000000200000-0x000001f00000 : "firmware"
[    4.123180] 2 trx partitions found on MTD device firmware
[    4.128594] Creating 2 MTD partitions on "firmware":
[    4.133587] 0x00000000001c-0x000000400000 : "linux"
[    4.138903] 0x000000400000-0x000001d00000 : "ubi"
[    4.144096] 0x000001f00000-0x000008000000 : "failsafe"

root@OpenWrt:/bin# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00100000 00020000 "nvram"
mtd2: 00080000 00020000 "nvram"
mtd3: 01d00000 00020000 "firmware"
mtd4: 003fffe4 00020000 "linux"
mtd5: 01900000 00020000 "ubi"
mtd6: 06100000 00020000 "failsafe"

This different than you have it in your random noise blog:

[    3.967344] Creating 7 MTD partitions on "brcmnand.0":
[    3.972500] 0x000000000000-0x000000080000 : "boot"
[    3.977913] 0x000000080000-0x000000180000 : "nvram"
[    3.983348] 0x000000180000-0x000000200000 : "nvram"
[    3.988757] 0x000000200000-0x000001f00000 : "firmware"
[    3.994846] 0x000001f00000-0x000008000000 : "failsafe"
[    4.000664] 0x00000020001c-0x00000037c000 : "linux"
[    4.006107] 0x00000037c000-0x000001f00000 : "rootfs"
[    4.023962] 0x000000620000-0x000001f00000 : "rootfs_data"
...
...
 
root@LEDE:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00020000 "boot"
mtd1: 00100000 00020000 "nvram"
mtd2: 00080000 00020000 "nvram"
mtd3: 01d00000 00020000 "firmware"
mtd4: 06100000 00020000 "failsafe"
mtd5: 0017bfe4 00020000 "linux"
mtd6: 01b84000 00020000 "rootfs"
mtd7: 018e0000 00020000 "rootfs_data"

Here are some messages from dmesg

42.447266] print_req_error: 30 callbacks suppressed
[   42.447270] print_req_error: I/O error, dev mtdblock6, sector 198400
[   42.459360] print_req_error: I/O error, dev mtdblock6, sector 198400
[   42.465729] buffer_io_error: 10 callbacks suppressed
[   42.465733] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   42.685316] print_req_error: I/O error, dev mtdblock6, sector 198400
[   42.692500] print_req_error: I/O error, dev mtdblock6, sector 198400
[   42.698876] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   42.908176] print_req_error: I/O error, dev mtdblock6, sector 198400
[   42.915383] print_req_error: I/O error, dev mtdblock6, sector 198400
[   42.921759] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   43.130302] print_req_error: I/O error, dev mtdblock6, sector 198400
[   43.137507] print_req_error: I/O error, dev mtdblock6, sector 198400
[   43.143877] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   43.252159] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[   43.258771] br-lan: port 3(wlan1) entered blocking state
[   43.264176] br-lan: port 3(wlan1) entered forwarding state
[   43.393398] print_req_error: I/O error, dev mtdblock6, sector 198400
[   43.400450] print_req_error: I/O error, dev mtdblock6, sector 198400
[   43.406823] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   43.648404] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   43.858002] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   44.067634] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[   44.281965] Buffer I/O error on dev mtdblock6, logical block 24800, async page read

#119

I would open a bug report. I have seen this myself but haven't had time to file one myself. Also, I have't tired to use latest sources. Where it seems to have been fixed.


#120

i reported the bug

https://bugs.openwrt.org/index.php?do=details&task_id=1440


#121

Thanks. I've upvoted it.


#122

Can you try to make it available for EA9500 v2?
Router information: https://wikidevi.com/wiki/Linksys_EA9500_v2