Bert, IIRC this has happened to people before and is a symptom of the EEPROM not being programmed correctly on the board. You'll want to contact Soekris or whoever you bought it from to either get it RMA'd or instructions on how to program it correctly.
Chris Bert Baron wrote: > Hello all, > > I didn't receive any answers yet, probably because I didn't resend the > request after subscribing. In the meen time I have upgraded the bios from > version 1.33 to 1.33c, which had no effect. I also downloaded the latest > monowall image > (http://m0n0.ch/wall/download.php?file=generic-pc-1.3b13.img), which gave > the following valid interfaces: > > -- > Valid interfaces are: > > vr0 ff:ff:ff:ff:ff:ff > vr1 ff:ff:ff:ff:ff:ff (up) > vr2 ff:ff:ff:ff:ff:ff > vr3 ff:ff:ff:ff:ff:ff > -- > > So it seems to think that the mac adresses of all interfaces equals to > ff:ff:ff:ff:ff:ff but it notices that the second interface is up, which is > the one to which the cable is connected! > > Could it be that the MAC adresses are actually not set in the ROM of the > ethernet adapters or does anyone has another clue for this result? > > Bert. > > > > Bert Baron wrote: > >> Although I haven't any network boot server running, I definitly have a >> cable attached (and a running DHCP server). I tried with different cables >> connected to different ethernet switches but all with the same result. >> The led of the connected adapter goes of after boot and when I disconnect >> the cable later on the led goes back on. All other ethernet leds are on. >> >> So before I go on with trying to install any software I want to clearify >> that this error is expected even when a cable is attached. Maybe someone >> can help me with this? >> >> > > _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
