Could you please tell me which firmware you are using ? (original Netgear or DD-WRT or tomato or OpenWRT)
It would be better if you give some detail information about your problem.
Every firmware (mentioned above) has one wireless driver (wl.o) and when board is booting up this driver is automatically installed by insmod. In that case you do not need to insmod driver separately.
I think you are using some older version of firmware. Please check with new firmware which are available in this site.
Categories: WGR614L (Legacy Product)
Hello,
I'm trying to insmod wl.o without success, I'm not sure what happened with this because it was Ok.
root@(none):/jffs# insmod wl.o
Using /lib/modules/2.4.35.4/wl.o
Warning: loading wl will taint the kernel: non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
PCI/DMA
wl0: wlc_attach: failed with err 16
wl%d: 4.150.10.5 driver failed with code 16
Memory leak of bytes 10724
insmod: init_module: wl: No such device
Thanks for any hint to correct it.
Das,
I'm using an hybrid kernel. It is an OpenWrt patched kernel with some parts of DD-WRT and some modifications.
I fix this problem as Nachi say:
root@(none):/# nvram show | grep sromrev
sromrev=2
size: 9452 bytes (23316 left)
root@(none):/# nvram set sromrev=3
root@(none):/# nvram commit
root@(none):/# insmod wl
Using /lib/modules/2.4.35.4/wl.o
Warning: loading wl will taint the kernel: non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
PCI/DMA
wl0: wlc_attach: chiprev 3 coreunit 0 corerev 13 cccap 0x104001ea maccap 0x30482205 band 2.4G, phy_type 5 phy_rev 0 ana_rev 6
wl0: Broadcom BCM4318 802.11 Wireless Controller 4.150.10.5
root@(none):/# insmod wlcompat
Using /lib/modules/2.4.35.4/wlcompat.o
Thanks again.
It error always happens after pressing reset button. (WGR614v8 NA)
Yes, this error will happen if you press the factory reset. One way to handle this is to force the preinit script to do the sromrev checking and then do a reboot after correcting that if it was wrong.
Other part is to correct it at the time of nvram initialization in the Kernel.
Nachi

RSS

