please, try to compile the latest kernel. Follow the steps from here:
We have updated the Ethernet initialization in the Linux kernel. This may help you. We still need to do extensive testing, but this new update should also fix the uboot ping requirement. Let us know.
Another problem now is the boot up time is very very long without
Yes, the truth is, Linux should not be looking for DHCP if ethernet is not connected – but it does (I dont know why). Maybe check with a Linux programmer how this could be fixed or have a look on Internet for example:
You can also try to use a fixed IP – that should also help but may not be the final solution.
When I unplug the ethernet cable, the ehternet socket will generate a
high frequency sound (this will not happen in uboot). This sound is
This could be caused by looping grounds (e.g. if you use different main plugs for each device). Be sure all your devices are powered up from the same power socket and grounded properly. Be sure, the screws which hold the module on baseboard are tight up.
There is still something not right in the ethernet network – the board should get IP OK at the first time:
eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY]
(mii_bus:phy_addr=1: 03, irq=-1) Sending DHCP requests …… PHY:
1:03 – Link is Up – 100/Full timed out!
IP-Config: Reopening network
devices… eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY]
(mii_bus:phy_addr=1: 03, irq=-1) PHY: 1:03 – Link is Up – 100/Full
Sending DHCP requests ., OK
May be it is problem of some switch.
This could be possible. Also double check your Ethernet cable. Try to buy a new gigabit switch. For the FEC registers, check Freescale website: http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q
When I unplug the cable in our kit and plug again .. works all the time – in uboot and linux, no problem.
When you keep having problems, please, try to take the kit home and test it in completely different place, completely different network and let me know if it behaves same.
Please attach the full console log from the different network.
- Guest answered 1128 days ago
- last edited 1128 days ago
All gigabit switch works fine. Most of the 100M switch doesn’t work.
This is important. We are closer to solve your problem.
I can confirm, I can see exactly same behaviour (if we use a 100Mb switch). We will update the Linux driver and let you know.
I know imx 3.10.17 kernel version is nearly out. Any plan to have a
rex support version of 3.10.17? We may need this newer keneral as one
of our wifi driver based on this newer kernel. 3.0.35 doesn’t have the
kernel API for this driver!!!
If we have our own project where we need to use the 3.10, we will port it. Maybe some other iMX6 Rex users may port it before us.
Please, can you COPY and PASTE your console output of these commands running on your board:
Reset your board, go to uboot and:
- full log from booting uboot
- full log from booting Linux
ls -la /
This is not our kernel. Download the latest kernel here:
Please login first to submit.