I'm quite sure I have a wrt54gs v1.0 as it has an admtek switch built in.
But regardless of the exact model i build for (v1.0 or v1.1) both images
show an error at boot-time when trying to load the `switch-adm.o' kernel
module. This behaviour is reproducable, the `switch-core.o' module loads
without errors, then when trying to insmod the `switch-adm.o' module the
following happens:
root@FreeWRT:/# insmod /lib/modules/2.4.32/switch-adm.o
insmod: unresolved symbol bcm947xx_sbh
Just to make sure I don't have a switch made by US Robotics
I build an image with support for the `switch-robo.o' kernel
module built in. At boot-time the following happens:
Probing device eth0: No Robo switch in managed mode found
Probing device eth1: No such device
Probing device eth2: No such device
Probing device eth3: No such device
insmod: init_module: switch-robo: No such device
When assigning an IP to eth0 manually, the network is accessible.
My nvram settings should not be involved in creating the non-working
setup as I already erased it and rebooted, resulting in the same
situation.
