PHY not being found at boot on kernel 3.10.17

Trying to bring up Linux kernel 3.10.17 on a Beagleboard-xM. The Ethernet isn’t working as the phy isn’t being found; error is: “unable to find transceiver” when ehci is being initialized.

If I go back to a previous kernel, such as 3.8.0, then all is fine.

Does anyone have a solution to this?

Make sure the SW turns on the power to the HUB. It comes up off.

Gerald

Build with
CONFIG_NOP_USB_XCEIV=M

as it's been broken sinc 6022671

Regards,

That’s D14, correct? That’s on so I think the power is okay.

Yep, D14.

Gerald

I have CONFIG_NOP_USB_XCEIV=y, so it should be built in. Should I build it as a module?

Correct, build with
CONFIG_NOP_USB_XCEIV=M

as "CONFIG_NOP_USB_XCEIV=y" been broken since 6022671

Regards,

Built the NOP driver as a module and put ‘modprobe phy-nop’ as the first line in the rcS file. Still have the same error:

[ 2.492553] unable to find transceiver
[ 2.496948] ehci-omap ehci-omap.0: Can’t get PHY device for port 1: -517
[ 2.504180] platform ehci-omap.0: Driver ehci-omap requests probe deferral
[ 2.595275] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts:
(null)
[ 2.604125] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 2.616333] devtmpfs: mounted
[ 2.619903] Freeing unused kernel memory: 176K (c0484000 - c04b0000)
[ 2.876312] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
[ 3.039093] platform nop_usb_xceiv.2: Driver nop_usb_xceiv requests probe deferral
Starting logging: OK
Initializing random number generator… [ 3.245544] hub 1-0:1.0: Cannot enable por
t 1. Maybe the USB cable is bad?
done.
Starting system message bus: done
Starting network…
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCSIFHWADDR: No such device
ifconfig: SIOCGIFFLAGS: No such device
Starting dropbear sshd: Copying dropbear host key files
OK
[ 4.444000] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 5.643951] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?

Built the NOP driver as a module and put 'modprobe phy-nop' as the first
line in the rcS file. Still have the same error:

[ 2.492553] unable to find transceiver
[ 2.496948] ehci-omap ehci-omap.0: Can't get PHY device for port 1: -517
[ 2.504180] platform ehci-omap.0: Driver ehci-omap requests probe
deferral
[ 2.595275] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data
mode. Opts:
(null)
[ 2.604125] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 2.616333] devtmpfs: mounted
[ 2.619903] Freeing unused kernel memory: 176K (c0484000 - c04b0000)
[ 2.876312] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
[ 3.039093] platform nop_usb_xceiv.2: Driver nop_usb_xceiv requests probe
deferral
Starting logging: OK
Initializing random number generator... [ 3.245544] hub 1-0:1.0: Cannot
enable por
t 1. Maybe the USB cable is bad?
done.
Starting system message bus: done
Starting network...
ifconfig: SIOCGIFFLAGS: No such device
ifconfig: SIOCSIFHWADDR: No such device
ifconfig: SIOCGIFFLAGS: No such device
Starting dropbear sshd: Copying dropbear host key files
OK

Okay, well here is my patchset:

It 'booted' last i tried, but i'm running v3.12-rc7 now days using
device tree's so i haven't tested in a while.. So dig thru it..

[ 4.444000] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is
bad?
[ 5.643951] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is
bad?

Also, because of that dmesg noise, test with this enabled/disabled..

Regards,

Okay, thanks, Robert. I will dig into it and let you know what I find.

I’m trying to get 3.10.18 running, and with this option already set as indicated I get “unable to find transceiver” and “can’t get PHY device” in syslog, both with ehci. So is there any news on this ?

Thanks,

hvn