The binary firmware I downloaded and installed for the WRT54GS runs and the Cisco bridge logo is not lit up.  When I build my own firmware and run it the logo is lit up white.  Can someone please tell me what controls the color of that logo light?  The stock Linksys firmware lights it up amber.

Is this really a question for the developers forum? I think this is a General forum question.

Linksys uses it for the Secure Easy Setup function. Currently not much utilized in alternate firmware.

(Last edited by vincentfox on 12 Mar 2006, 21:26)

You're right about the forum.  I'm new here and have been bouncing between the forums searching and trying to find out a few answers.  I assumed the dev forum would be the place to post Buildroot questions, but a search for "buildroot" in the General forum does return a lot of hits.  I'll be more careful.  Thanks for replying.

Hmmmm, okay I perhaps did not read your question closely enough. You downloaded SVN today, did a make and got what? The SES might light during boot but I would expect it to go dark during normal operation.  I have an SL and don't see same. The only GS I have is v1.0 so no Cisco button can't confirm that.

Yesterday, actually...  Make ran and produced the usual binary files under bin/.  I uploaded openwrt-wrt54gs-squashfs.bin to the router.  It boots and runs.  Everything works OK (well, not really, but that's another question).  I telnetted into it, changed the password and now I can ssh into it.  No problems there.

So it's not really a problem per se, but the cisco logo on the front of the router is now constantly lit.  The binary firmware I downloaded last week when I was just getting started with OpenWrt also runs, but the logo is not lit up.  I was just wondering if this is configurable, or if maybe buildroot is picking up code that's newer than what came down with the svn download.  I did see it downloading things as it ran.  Mostly the toolchain source, but there were other things downloaded as well.  I didn't notice exactly what since the first run of buildroot "make" took 3 or 4 hours to run on my old and slow Linux box.

Can you give me a dump of your nvram?

Here it is.  This is a WRT54GS v2.1 running in Client Mode.  It's doing nothing but bridging my ps2 in one room to my wireless WAN router in another room.  I run it with WPA-PSK (TKIP) and the pre-built binary firmware I downloaded works just fine this way.

I created this list with "nvram show | sort > nvramlist.txt".

Intel_firmware_version=v1.41.8
aa0=3
ag0=255
artemis_provisioned=0
bcm4712_firmware_version=v1.50.0
boardflags2=0
boardflags=0x0318
boardnum=42
boardrev=0x10
boardtype=0x0708
boot_ver=v3.5
boot_wait=on
bootnv_ver=5
ccode=0
cctl=0
clkfreq=200
ddns_enable=0
ddns_interval=60
dhcp_num=20
dhcp_start=40
dl_ram_addr=a0001000
eou_configured=1
eou_device_id=RJXXM7QF
eou_expired_hour=72
eou_private_key=9858b098..... (* NOTE TRIMMED FOR BREVITY)
eou_public_key=b8fdfb01........ (* NOTE TRIMMED FOR BREVITY)
et0macaddr=00:14:BF:00:F0:CF
et0mdcport=0
et0phyaddr=30
flash_type=Intel 28F640J3 4Mx16
gpio2=ses_led
gpio3=ses_led2
gpio4=ses_button
gpio5=robo_reset
il0macaddr=00:14:bf:00:f0:d1
lan_dns=192.168.2.1  <=== * NOTE THIS IS THE WAN ROUTER IT CONNECTS TO WIRELESSLY
lan_gateway=192.168.2.1
lan_hwaddr=00:14:BF:00:F0:CF
lan_ifname=br0
lan_ifnames=vlan0 eth1 eth2 eth3
lan_ipaddr=192.168.2.94   <=== * NOTE THIS IS THE STATIC IP ADDRESS I ASSIGNED, NOT FROM DHCP
lan_netmask=255.255.255.0
lan_proto=static
lan_stp=0
os_date=Apr 24 2005
os_flash_addr=bfc40000
os_ram_addr=80001000
os_version=3.91.7.0
pa0b0=0x15eb
pa0b1=0xfa82
pa0b2=0xfe66
pa0itssit=62
pa0maxpwr=0x4e
pmon_ver=CFE 3.91.7.0
ppp_demand=0
ppp_idletime=5
ppp_mru=1500
ppp_mtu=1500
ppp_redialperiod=30
pppoe_demand=0
pppoe_idletime=5
router_name=WRT54GS
scratch=a0180000
sdram_config=0x0062
sdram_init=0x010b
sdram_ncdl=0xff0008
sdram_refresh=0x0000
sromrev=2
vlan0hwname=et0
vlan0ports=1 2 3 4 5*
vlan1hwname=et0
vlan1ports=0 5
wan_device=vlan1
wan_dns=10.0.0.4   <=== * NOTE PHONY WAN ADDRESS AND GATEWAY, NO CABLE PLUGGED INTO WAN PORT
wan_gateway=10.0.0.1
wan_hwaddr=00:14:BF:00:F0:D0
wan_iface=vlan1
wan_ifname=vlan1
wan_ifnames=vlan1
wan_ipaddr=10.0.0.2
wan_mtu=1500
wan_netmask=255.255.255.0
wan_proto=static
watchdog=5000
wl0_afterburner=auto
wl0_akm=psk
wl0_antdiv=-1
wl0_ap_isolate=0
wl0_auth=0
wl0_auth_mode=none
wl0_bcn=100
wl0_channel=5
wl0_closed=1
wl0_corerev=7
wl0_country=Worldwide
wl0_country_code=US
wl0_crypto=tkip
wl0_dtim=1
wl0_frag=2346
wl0_frameburst=on
wl0_gmode=1
wl0_gmode_protection=off
wl0_hwaddr=00:14:BF:00:F0:D1
wl0_ifname=eth1
wl0_infra=1
wl0_key=1
wl0_lazywds=1
wl0_macmode=disabled
wl0_maxassoc=128
wl0_mode=wet   <=== * NOTE CLIENT BRIDGE MODE
wl0_mrate=0
wl0_net_mode=mixed
wl0_net_reauth=36000
wl0_phytype=g
wl0_phytypes=g
wl0_plcphdr=long
wl0_radio=1
wl0_radioids=BCM2050
wl0_radius_port=1812
wl0_rate=0
wl0_rateset=default
wl0_rts=2347
wl0_ssid=xxyyzz  <=== * NOTE MATCHES SSID OF THE WIRELESS WAN ROUTER
wl0_wds_timeout=1
wl0_wep=disabled
wl0_wep_bit=64
wl0_wme=off
wl0_wme_ap_be=15 63 3 0 0 off
wl0_wme_ap_bk=15 1023 7 0 0 off
wl0_wme_ap_vi=7 15 1 6016 3008 off
wl0_wme_ap_vo=3 7 1 3264 1504 off
wl0_wme_no_ack=off
wl0_wme_sta_be=15 1023 3 0 0 off
wl0_wme_sta_bk=15 1023 7 0 0 off
wl0_wme_sta_vi=7 15 2 6016 3008 off
wl0_wme_sta_vo=3 7 2 3264 1504 off
wl0_wpa_gtk_rekey=3600
wl0_wpa_psk=b0guspassphrase
wl0gpio2=0
wl0gpio3=0
wl0id=0x4320

Testing a fix right now ...

Please try the new image at http://downloads.openwrt.org/people/nbd/whiterussian/

That seems to work.  Web interface shows...

Firmware Version       WHITE RUSSIAN (pre-RC5)
Kernel Version     Linux version 2.4.30 (nbd@ux-2y02) (gcc version 3.4.4 (OpenWrt-1.0)) #3 Mon Mar 13 00:59:11 CET 2006
Current Date/Time     Sat Jan 1 00:09:36 UTC 2000
MAC Address     00:14:BF:00:F0:CF

Are your changes committed to svn?  I want to see how it goes if I build from scratch.

On an unrelated note, I also d/l'ed ImageBuilder and "make" always errors out with

adding 992 bytes of garbage
/home/craven/OpenWrt-ImageBuilder-Linux-i686/staging_dir_mipsel/bin/mksquashfs-lzma: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
make[2]: *** [/home/craven/OpenWrt-ImageBuilder-Linux-i686/build_mipsel/linux-2.4-brcm/root.squashfs] Error 127
make[1]: *** [build] Error 2

I have libstdc++.so.6 but not 5.  Is .5 a requirement?  I tried symlinking so.6 to so.5 but it didn't like that either.  This happened for my downloaded ImageBuilder for RC3, RC4 and 'latest'.

Thanks for the help.  I know you're busy.

This thing was built using libstdc++ 5. If you want to use it, you probably need to install a compatibility package...