start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
start [2011/04/08 02:49] – neutronscott | start [2023/11/04 22:30] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Introduction ====== | + | Welcome |
- | Someone had to be brave enough to take on the creation of a 3rd party firmware for this thing. I'm Scott Nicholas, aka neutronscott. This wiki describes my work of porting Linksys' | + | |
- | ====== Current Status ====== | + | **DISCLAIMER**: |
- | April 7th, 2011: Created a snapshot directory -- http://wrt.scottn.us/ | + | So nothing here is probably in any " |
- | FIXME (insert | + | ====== new firmware mod ====== |
+ | I got tired of the wifi speed in the 2.6 kernel and went back to the official firmware. I realized that I only used it for ssh port forwarding into the LAN, and dnsmasq' | ||
- | Working: serial port, ethernet ports (WAN and LAN are separate but identical), wifi. \\ | + | http://wrt.scottn.us/wrtu54g-tm-v1.00.25-ns.bin |
- | Not working: switch driver (VLANs), VINETIC SPI communications (Power LED control is here), [[wrtu54g-tm:usb|USB]], GPIO export. | + | |
- | ====== Downloads ====== | + | login: neutron |
+ | pass: scott | ||
- | * Snapshots at http:// | + | Yeah, I left root's default |
- | * Alex' | + | |
- | * @jdownj/ | + | |
- | * My latest | + | |
- | * source | + | |
- | * Browse my file store: http:// | + | |
- | + | ||
- | ====== Installation ====== | + | |
- | + | ||
- | ===== From official firmware ===== | + | |
- | + | ||
- | Just use Firmware Upgrade under Administration in the web interface. | + | |
- | + | ||
- | ===== From previous release ===== | + | |
- | + | ||
- | I recall keeping configuration not working before. Do so at your own risk! If you have the backfire b1 or b2 try [[wrtu54g-tm: | + | |
- | + | ||
- | root@OpenWrt: | + | |
- | root@OpenWrt:/ | + | |
- | root@OpenWrt:/ | + | |
- | Keep config files over reflash (y/N): n | + | |
- | Switching to ramdisk... | + | |
- | mount: mounting mini_fo:/ | + | |
- | Performing system upgrade... | + | |
- | Unlocking linux ... | + | |
- | Writing from < | + | |
- | Upgrade completed | + | |
- | Reboot (Y/n): y | + | |
- | Rebooting system... | + | |
- | + | ||
- | ===== From a broken state ===== | + | |
- | + | ||
- | If things go sour and you need to start fresh, you can also reflash an entire firmware from the bootloader. The bootloader doesn't offer a TFTP server, but a TFTP client, and access to the serial console is required. The procedure is documented [[wrtu54g-tm: | + | |
- | + | ||
- | If you break the bootloader as well, you will want to learn about [[wrtu54g-tm: | + | |
- | + | ||
- | ====== Usage ====== | + | |
- | + | ||
- | If you got this far, you may find http:// | + | |
- | + | ||
- | The only device specific function is that during bootup you may hold the SES button to activate fail-safe mode. This is useful for example if: you forgot your password, broke your configuration, or the writable filesystem is corrupted. It boots without mounting the writable system and you can telnet in, and if needed ' | + | |
- | + | ||
- | ===== Installing packages ===== | + | |
- | + | ||
- | If you need more packages, the user applications from nearly any other mipsel target should work, given that the libraries are at the same version. Replace **/ | + | |
- | + | ||
- | src/gz adm8668 http:// | + | |
- | src/gz snapshots http:// | + | |
- | dest root / | + | |
- | dest ram /tmp | + | |
- | lists_dir ext / | + | |
- | option overlay_root /overlay | + | |
- | arch all 5 | + | |
- | arch brcm47xx 10 | + | |
- | arch adm8668 20 | + | |
- | + | ||
- | Failing that, you'll have to build your own or ask on the mailing list. | + | |
- | + | ||
- | ====== Building from source ====== | + | |
- | + | ||
- | If you require functionality that is not included in a basic build (i.e. IPv6 or PPPoE), then you may have to build it yourself. This is because I don't have a full package repository yet. | + | |
- | + | ||
- | ====== Removal ====== | + | |
- | + | ||
- | Simply follow the [[wrtu54g-tm# | + | |
- | + | ||
- | I can't make these things more simple! ;) | + | |
- | + | ||
- | ====== Support ====== | + | |
- | + | ||
- | There is a mailing list available at http:// | + | |
- | You can contact me personally by methods described [[contact|here]]. \\ | + | |
- | I'll try to help out where I can, but honestly the active development pretty much ended after the patch was sent off for inclusion into OpenWRT. Other users have been assisting each other as well with questions and builds. Thanks everyone! :) | + | |
- | + | ||
- | It's not too complicated. | + | |
- | * Get into Linux. Install the devel essentials, svn, ... | + | |
- | * Checkout OpenWRT: **svn co < | + | |
- | * Configure OpenWRT: **make menuconfig** | + | |
- | * You are only required to select the target. Infineon ADM8668 WildPass. The rest is up to you. | + | |
- | * Issue **make** and take a nap. | + | |
- | + | ||
- | I tried building the entire thing, and it didn't workout. We really need the OpenWRT guys to include our platform in their buildbot snapshots. :( | + | |
- | + | ||
- | ====== Thanks ====== | + | |
- | * Helmut Schaa -- His work on the Ralink SoC devices with OpenWRT led him to becoming a maintainer for the rt2x00 wireless drivers. His patience with me and his tasklet patches significantly improved the wireless throughput for this device. | + | |
- | * Mayckel (a guy from Curacao) -- for being my guinea pig and putting up with my firmware breaking his routers. ;) | + | |
+ | http:// | ||
+ | Despite attempts, ' |
start.1302230971.txt.gz · Last modified: 2023/11/04 22:29 (external edit)