[email protected] wrote:
Hi,
Jose Vasconcellos wrote:
I've built a redboot for the WRV54G and it can be found here:
http://mysite.verizon.net/jvasco/openwrt/rb-wrv54g-ROM.bin
http://mysite.verizon.net/jvasco/openwrt/rb-wrv54g-RAM.img
Following the upgrade procedure described in the MI424-WR
wiki page works.
RedBoot works, good job, would be worth updating with instructions how
to create the redboot image (once there is the new wiki).
Regarding making the kernel and openwrt images, I've tested
with the trunk. kernel_menuconfig must be used to select the
device (GTWX5715). Only issue I've found was that wifi fails
after a while; this is more of an issue with configuring the prism54
properly.
Using current openwrt trunk the npe interfaces do not work, the driver
does not load:
ixp4xx_eth: probe of ixp4xx_eth.16 failed with error -5
ixp4xx_eth: probe of ixp4xx_eth.32 failed with error -5
Compiling the npe, eth and qmgr driver as modules and inserting npe at
runtime lead to:
"failed to request memory region!".
which is in
static int __init npe_init_module(void)
Ideas?
MfG
Markus
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I have a wrv54g running without modifying the bootloader (using the
original patches + the ones I submitted a long time ago), and have no
problem with the Ethernet working. Only issue is that the MAC addresses
aren't automagically set at boot, but after configuring them the
interfaces work fine.
A redboot problem?
Regards
Stuart
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
