I have seen this problem repeatedly by A6 revision hardware, but not with
revision A5C hardware (I am running exactly the same software on both).
Noteworthy is that the "PHY problem" only appears when powering the BBB via
the headers. Powering via USB does not give any problems.
I tried the following:
-Use the kernel from the v3.8.13-bone40 image
-Change some lines in davinci_mdio.c to hardcode the mask to 0
("desperately scan all phys")
Both tries weren't lucky. It seems to me that the CPU cannot find the PHY
chip, because it never powers up.
On Wednesday, March 19, 2014 9:31:00 PM UTC+1, David wrote:
>
> FWIW I have seen the "PHY problem" repeatedly using the 3.8 kernel, but
> not yet with the RCN 3.13 kernel.
>
>
> Regards,
>
> Dave.
>
> On 03/19/2014 02:52 PM, Robert Nelson wrote:
> > On Wed, Mar 19, 2014 at 2:47 PM, <bko...@scanimetrics.com <javascript:>>
> wrote:
> >> Does anyone happen to know if the 3.8 kernel compiled as per these
> >> instructions here
> >> http://eewiki.net/display/linuxonarm/BeagleBone+Blackalso
> >> contains the fix? I have a root file system already that I want to use
> but
> >> would like to update my kernel to fix this problem.
> > Sorry, "the fix" is too generic of a term, therefore I can neither
> > confirm nor deny it. Either way, that 3.8 branch listed is the one
> > currently used in all debian/ubuntu images being shipped.
> >
> > Regards,
> >
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
