Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| user:jiringgot [2021/05/05 15:02] – jiringgot | user:jiringgot [2021/05/05 17:11] – jiringgot | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ==== Jiringgot ==== | ||
| + | * Casual computer nerd | ||
| + | * Teaching sand to think was a good mistake. | ||
| + | |||
| + | |||
| ====== WIP ZyXEL NBG6515 AC750====== | ====== WIP ZyXEL NBG6515 AC750====== | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| {{page> | {{page> | ||
| - | |||
| - | == TODO == | ||
| - | * Instruct users how to modify the device tree for cluing in the mt76x0 driver on where to find factory data. | ||
| - | * Update informatory sections to reflect current findings and activites | ||
| - | * Sprinkle some more information around instructions that are obvious to experienced users, but completely oblivious to people scrolling by. | ||
| Line 13: | Line 13: | ||
| * MEDIATEK MT7620A: CPU, WLAN | * MEDIATEK MT7620A: CPU, WLAN | ||
| * MEDIATEK MT7530WU: Switch | * MEDIATEK MT7530WU: Switch | ||
| - | * MEDIATEK MT7610EN: WLAN | + | * MEDIATEK MT7610EN: WLAN (not working in the provided release build) |
| /*****/ | /*****/ | ||
| Line 35: | Line 35: | ||
| ===== Supporting activities ===== | ===== Supporting activities ===== | ||
| //Describe if there are any ongoing activities that might lead to OpenWrt support.// | //Describe if there are any ongoing activities that might lead to OpenWrt support.// | ||
| - | * A dedicated device profile is being worked on. A preliminary patch which fixes previous [[MT76x0E errors]]https:// | + | * A dedicated device profile is being worked on. A preliminary patch which fixes previous [[https:// |
| * 2.4Ghz WLAN works with the RaLink driver: rt2x00 in conjunction with data from the <color # | * 2.4Ghz WLAN works with the RaLink driver: rt2x00 in conjunction with data from the <color # | ||
| * The overlayFS only works after flashing the sysupgrade image from inside a running OpenWrt system, e.g. one that has been started via TFTP boot | * The overlayFS only works after flashing the sysupgrade image from inside a running OpenWrt system, e.g. one that has been started via TFTP boot | ||
| Line 79: | Line 79: | ||
| - If you plan to permanently install OpenWrt, do so by flashing the previously downloaded " | - If you plan to permanently install OpenWrt, do so by flashing the previously downloaded " | ||
| - The bootloader offers an alternative option " | - The bootloader offers an alternative option " | ||
| - | ==== Enabling wireless through information taken from the mt2 (factory) partition of the original firmware ==== | + | |
| + | |||
| + | ==== Enabling | ||
| - After booting into OpenWrt, open an ssh session and verify that you have a working overlayfs: '' | - After booting into OpenWrt, open an ssh session and verify that you have a working overlayfs: '' | ||
| - To make sure that overlayfs is functional, create a new directory by '' | - To make sure that overlayfs is functional, create a new directory by '' | ||
| Line 90: | Line 92: | ||
| - After logging into LuCi, you can now use the WLAN as usual. | - After logging into LuCi, you can now use the WLAN as usual. | ||
| + | Note: OpenWRT source contains patches that add device-tree tags in the rt2x00 driver. " | ||
| + | |||
| + | ==== Enabling device 5GHz wireless with a custom build ==== | ||
| + | This section assumes you have read and understood in detail what is explained above and why. Enabling the 5GHz radio requires that you know how to patch the source tree of OpenWRT. | ||
| + | It is also asumed that the " | ||
| + | |||
| + | The preliminary patch adds a <color # | ||
| + | |||
| + | Patch Link: https:// | ||
| + | |||
| + | - Clone the OpenWRT source tree to a directory of your choosing. | ||
| + | - Download the patch and apply using '' | ||
| + | - Now configure the source tree as described here: [[: | ||
| + | - If you have already completed the previous section enabling 2.4 wireless, you can run '' | ||
| + | - Depending on your hardware the build could take a while, but when it finishes you should have a [[: | ||
| + | - If done correctly, the produced build can be flashed onto the device as described in the previous installation section. Note however that the compatability-identifier is changed in the patch so you have to do a force-flash. | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| Line 170: | Line 188: | ||
| </ | </ | ||
| ***/ | ***/ | ||
| + | ==== Flash Layout ==== | ||
| + | |||
| + | === Stock === | ||
| + | ^ Start ^ Stop ^ Name ^ | ||
| + | ^ 0x000000 | 0x800000 | ALL | | ||
| + | ^ 0x000000 | 0x030000 | Bootloader | ||
| + | ^ 0x030000 | 0x040000 | Config | ||
| + | ^ 0x040000 | 0x048000 | Factory | ||
| + | ^ 0x048000 | 0x050000 | iNIC_rf | ||
| + | ^ 0x050000 | 0x724000 | Kernel | ||
| + | ^ 0x210000 | 0x724000 | user | | ||
| + | ^ 0x724000 | 0x7ba000 | manufacture | | ||
| + | ^ 0x7ba000 | 0x7ca000 | backup | ||
| + | ^ 0x7ca000 | 0x800000 | storage | ||
| + | === Wrt === | ||
| + | ^ Device ^ Size ^ Name ^ | ||
| + | ^ mtd0 | 00030000 | " | ||
| + | ^ mtd1 | 00010000 | " | ||
| + | ^ mtd2 | 00010000 | " | ||
| + | ^ mtd3 | 007b0000 | " | ||
| + | ^ mtd4 | 00138694 | " | ||
| + | ^ mtd5 | 0067796c | " | ||
| + | ^ mtd6 | 00442000 | " | ||
| /*==== Photos ====*/ | /*==== Photos ====*/ | ||