mpettit
Forum Replies Created
- AuthorPosts
today i noticed that the Ubuntu image doesn’t load the same drive as the Debian image for the phy …
ubuntu@arm:~$ dmesg | grep phy
[ 0.000000] Booting Linux on physical CPU 0x0
[ 1.887704] libphy: Fixed MDIO Bus: probed
[ 1.977736] davinci_mdio 4a101000.mdio: detected phy mask ffffffef
[ 1.986222] libphy: 4a101000.mdio: probed
[ 1.990310] davinci_mdio 4a101000.mdio: phy[4]: device 4a101000.mdio:04, driver unknown
[ 2.042184] am335x-phy-driver 47401300.usb-phy: 47401300.usb-phy supply vcc not found, using dummy regulator
[ 2.057993] am335x-phy-driver 47401b00.usb-phy: 47401b00.usb-phy supply vcc not found, using dummy regulator
[ 7.824009] Generic PHY 4a101000.mdio:04: attached PHY driver [Generic PHY] (mii_bus:phy_addr=4a101000.mdio:04, irq=POLL)
………
debian@beaglebone:~$ dmesg | grep phy
[ 0.000000] Booting Linux on physical CPU 0x0
[ 2.425604] libphy: Fixed MDIO Bus: probed
[ 2.481775] davinci_mdio 4a101000.mdio: detected phy mask ffffffef
[ 2.496055] libphy: 4a101000.mdio: probed
[ 2.496086] davinci_mdio 4a101000.mdio: phy[4]: device 4a101000.mdio:04, driver Atheros 8035 ethernet
[ 2.506836] 47401300.usb-phy supply vcc not found, using dummy regulator
[ 2.513461] 47401b00.usb-phy supply vcc not found, using dummy regulator
[ 21.798813] Atheros 8035 ethernet 4a101000.mdio:04: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=4a101000.mdio:04, irq=-1)
Thanks for looking into this,
ubuntu@arm:~$ systemctl status networking
??? networking.service – Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese
Drop-In: /run/systemd/generator/networking.service.d
??????50-insserv.conf-$network.conf
Active: failed (Result: timeout) since Sat 2017-12-09 19:40:42 UTC; 4 days ag
Docs: man:interfaces(5)
Process: 195 ExecStart=/sbin/ifup -a –read-environment (code=killed, signal=T
Process: 184 ExecStartPre=/bin/sh -c [ “$CONFIGURE_INTERFACES” != “no” ] && [
Main PID: 195 (code=killed, signal=TERM)
Dec 09 19:40:03 arm dhclient[289]: DHCPDISCOVER on eth0 to 255.255.255.255 port
Dec 09 19:40:03 arm ifup[195]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 i
Dec 09 19:40:22 arm dhclient[289]: DHCPDISCOVER on eth0 to 255.255.255.255 port
Dec 09 19:40:22 arm ifup[195]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 i
Dec 09 19:40:39 arm dhclient[289]: DHCPDISCOVER on eth0 to 255.255.255.255 port
Dec 09 19:40:39 arm ifup[195]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 i
Dec 09 19:40:42 arm systemd[1]: networking.service: Start operation timed out. T
Dec 09 19:40:42 arm systemd[1]: Failed to start Raise network interfaces.
Dec 09 19:40:42 arm systemd[1]: networking.service: Unit entered failed state.
Dec 09 19:40:42 arm systemd[1]: networking.service: Failed with result ‘timeout’
lines 1-20/20 (END)
ok, let me try this again. apparently minicom did not overwrite the capture file the last time.
This capture shows the boot finding the file correctly and the contents of the /boot/uEnv.txt file.
I did notice that i mentioned to add uboot_enable_overlays=1 might that be what i am missing?
Attachments:
lets try that again, i hae a couple of disks and i see the file was missing on the last. putting file in place did not fix problem though.
this is the contents of the fresh build disk and log of boot up.
ubuntu@arm:~$ cat /boot/uEnv.txt
uname_r=4.15.16-bone4
dtb=osd3358-bsm-refdesign.dtb
Mike
Attachments:
sorry seems i had to rename the capture file
Attachments:
Thank you for the reply. The steps you described are what i have done. I included a capture of the boot up. This is my /boot/uEnv.txt file contents:
#uname_r=4.1.12-bone16
uname_r=4.14.32-ti-rt-r42
#dtb=
dtb=am335x-boneblack.dtb
#dtb=am335x-bonegreen.dtb
#dtb=am335x-bonegreen-2can.dtb
#dtb=am335x-bonegreen-2can-uart.dtb
#dtb=osd3358-bsm-refdesign.dtb
#UUID=”e2a653e7-8499-43b6-a7bf-a8221fe4f5e0
UUID=”a00e5cc6-ef2d-45d3-b817-186e74496e3d”
- AuthorPosts