I don't recognize any errors here.

root@arm:/home/debian# ifconfig -a
eth0      Link encap:Ethernet  HWaddr C8:A0:30:C3:70:BE
          inet addr:192.168.1.11  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fd78:6a89:d8ad:3100:caa0:30ff:fec3:70be/64 
Scope:Global
          inet6 addr: fe80::caa0:30ff:fec3:70be/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:199 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:37848 (36.9 KiB)  TX bytes:2104 (2.0 KiB)
          Interrupt:40

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:160 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12960 (12.6 KiB)  TX bytes:12960 (12.6 KiB)

root@arm:/home/debian# dhclient eth0
RTNETLINK answers: File exists
root@arm:/home/debian#

Thanks for the quick response!

On Friday, May 29, 2015 at 2:56:06 PM UTC+1, James S wrote:
>
> I'm using BBB A5A hardware.
>
> I just built a  card with the Debian 8 (Small Flash) kernel using the 
> instructions at https://eewiki.net/display/linuxonarm/BeagleBone+Black.
>  (With the following exception: Instead of
> sudo cp -v ./ti-linux-kernel-dev/deploy/${kernel_version}.zImage /media/
> rootfs/boot/vmlinuz-${kernel_version}
> I used 
> sudo cp -v ./bb-kernel/deploy/${kernel_version}.zImage /media/rootfs/boot/
> vmlinuz-${kernel_version}
> since ti-linux-kernel-dev directory didn't exist. All instances of 
> ti-linux-kernel-dev were substituted.)
>
> It boots fine but the ethernet connection refuses connection. Using the 
> serial debug connection, I can ping from the BBB. 
> I also get the the following:
> root@arm:~# dmesg | grep -i phy
> [    0.000000] Booting Linux on physical CPU 0x0
> [    2.805706] 47401300.usb-phy supply vcc not found, using dummy regulator
> [    2.808594] 47401b00.usb-phy supply vcc not found, using dummy regulator
> [    3.372555] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
> [    3.372825] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffffffe]
> [    3.372849] davinci_mdio: dt: updated phy_id[1] from phy_mask[fffffffe]
> [    3.373837] libphy: 4a101000.mdio: probed
> [    3.373858] davinci_mdio 4a101000.mdio: phy[0]: device 
> 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
> [    6.399080] net eth0: phy found : id is : 0x7c0f1
> [    6.399150] libphy: PHY 4a101000.mdio:01 not found
> [    6.404248] net eth0: phy 4a101000.mdio:01 not found on slave 1
>
>
> I seen mention of the *0003-cpsw-search-for-phy.patch *here but I think 
> thats already applied. (Its in the patches folder in bb-kernel)
>
> The above output is from the 4.1 kernel, I get the following with the 3.8 
> kernel:
> root@arm:~# dmesg | grep -i phy
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.571890] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
> [    0.572897] libphy: 4a101000.mdio: probed
> [    0.572915] davinci_mdio 4a101000.mdio: phy[0]: device 
> 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
> [    4.163115] net eth0: phy found : id is : 0x7c0f1
> [    4.163144] libphy: PHY 4a101000.mdio:01 not found
> [    4.163155] net eth0: phy 4a101000.mdio:01 not found on slave 1
> [    7.240352] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
> root@arm:~#
>
> I've seen similar issues on this forum but I can't figure out what the 
> solution is - can anyone help?
>
> Regards,
> James
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to