NIC not properly initialized in uboot code
Bug #507887 reported by
Oliver Grawert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
uboot-imx (Ubuntu) |
Invalid
|
High
|
Oliver Grawert | ||
Lucid |
Won't Fix
|
High
|
Oliver Grawert |
Bug Description
with the recent uboot 2009.08 with freescale patches applied the FEC NIC doesnt get properly initialized under the running system this results in:
SIOCSIFFLAGS Cannot assign requested address
when running ifconfig eth0 up.
the NIC reportse a hardware address of 00:00:00:00:00:00
trying to initialize the NIC manually at the uboot prompt with setenv ethaddr (using the address printed on the label on the board) does not change the situation.
the file mxc_fec.c in the uboot code also seems to have many inconsistencies and some errors that show up during build.
tags: | added: armel |
Changed in uboot-imx (Ubuntu): | |
milestone: | none → lucid-alpha-3 |
importance: | Undecided → High |
Changed in uboot-imx (Ubuntu Lucid): | |
assignee: | nobody → Oliver Grawert (ogra) |
Changed in uboot-imx (Ubuntu Lucid): | |
status: | New → Confirmed |
tags: | added: patch-needswork |
To post a comment you must log in.
using:
setenv ethaddr <some random MAC address>
setenv ipaddr <a valid IP of the net the NIC is connected to>
seems to help. but indeed thats not usable in the automated SD card boot we are using since it would enforce to type in the IP each time you boot through serial console ... automated setting of the MAC and initializing of the NIC needs to work as it does under redboot.