I used the console image below. The ethernet USB gadget works. I'm not sure if lxqt and console use the same commit. Run the checksum on the kernel?
https://rcn-ee.com/rootfs/bb.org/testing/2016-01-24/console/bone-debian-8.3-console-armhf-2016-01-24-2gb.img.xz On Thursday, January 28, 2016 at 8:11:27 AM UTC-5, [email protected] wrote: > > I also tested in different host in Mac OS 10.11.3. It still doesn't work > even after manually assign static IP, network mast in host. The hosts works > fine with 3.8 kernel in BBB. > 4.1.15-ti-rt-43 image is from > https://rcn-ee.com/rootfs/bb.org/testing/2016-01-24/lxqt-4gb/bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz > > en5: flags=8923<UP,BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1486 > > ether 6c:ec:eb:b0:96:bd > > inet6 fe80::6eec:ebff:feb0:96bd%en5 prefixlen 64 scopeid 0xa > > nd6 options=1<PERFORMNUD> > > media: autoselect (<unknown type>) > > ping 192.168.7.2 > > PING 192.168.7.2 (192.168.7.2): 56 data bytes > > Request timeout for icmp_seq 0 > > Request timeout for icmp_seq 1 > > Request timeout for icmp_seq 2 > > ^C > > > On Wednesday, January 27, 2016 at 10:44:09 PM UTC-5, [email protected] > wrote: >> >> I experienced the same issue: >> BBB runs in 4.1.15-ti-rt-r43 >> Host runs in 4.2.5-300.fc23.x86_64. >> >> I thought I had network setup issue in host PC. So I checked the route, >> IP, net mask and gateway in host PC under 3.8 kernel, where host PC get >> connected to USB gadget ethernet correctly. >> >> But even I manually applied this setting for 4.1.15-ti-rt-r43. The >> connection is still broken. I wonder if/what DHCP server runs in 3.8? Is it >> possible that kernel USB gadget driver is broken in 4.1? >> >> thanks, >> Ricky >> >> >> On Wednesday, December 9, 2015 at 12:11:10 PM UTC-5, Fabian Dalbert wrote: >>> >>> seems to have been a driver compatibility problem on the host side >>> (linux mint 17.2, kernel 3.16). an update to linux mint 17.3 with kernel >>> 3.19 solved the problem. >>> >>> On Wednesday, December 9, 2015 at 9:13:47 AM UTC+1, Fabian Dalbert wrote: >>>> >>>> any ideas? >>>> >>> On Thursday, January 28, 2016 at 8:11:27 AM UTC-5, [email protected] wrote: > > I also tested in different host in Mac OS 10.11.3. It still doesn't work > even after manually assign static IP, network mast in host. The hosts works > fine with 3.8 kernel in BBB. > 4.1.15-ti-rt-43 image is from > https://rcn-ee.com/rootfs/bb.org/testing/2016-01-24/lxqt-4gb/bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz > > en5: flags=8923<UP,BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1486 > > ether 6c:ec:eb:b0:96:bd > > inet6 fe80::6eec:ebff:feb0:96bd%en5 prefixlen 64 scopeid 0xa > > nd6 options=1<PERFORMNUD> > > media: autoselect (<unknown type>) > > ping 192.168.7.2 > > PING 192.168.7.2 (192.168.7.2): 56 data bytes > > Request timeout for icmp_seq 0 > > Request timeout for icmp_seq 1 > > Request timeout for icmp_seq 2 > > ^C > > > On Wednesday, January 27, 2016 at 10:44:09 PM UTC-5, [email protected] > wrote: >> >> I experienced the same issue: >> BBB runs in 4.1.15-ti-rt-r43 >> Host runs in 4.2.5-300.fc23.x86_64. >> >> I thought I had network setup issue in host PC. So I checked the route, >> IP, net mask and gateway in host PC under 3.8 kernel, where host PC get >> connected to USB gadget ethernet correctly. >> >> But even I manually applied this setting for 4.1.15-ti-rt-r43. The >> connection is still broken. I wonder if/what DHCP server runs in 3.8? Is it >> possible that kernel USB gadget driver is broken in 4.1? >> >> thanks, >> Ricky >> >> >> On Wednesday, December 9, 2015 at 12:11:10 PM UTC-5, Fabian Dalbert wrote: >>> >>> seems to have been a driver compatibility problem on the host side >>> (linux mint 17.2, kernel 3.16). an update to linux mint 17.3 with kernel >>> 3.19 solved the problem. >>> >>> On Wednesday, December 9, 2015 at 9:13:47 AM UTC+1, Fabian Dalbert wrote: >>>> >>>> any ideas? >>>> >>> On Thursday, January 28, 2016 at 8:11:27 AM UTC-5, [email protected] wrote: > > I also tested in different host in Mac OS 10.11.3. It still doesn't work > even after manually assign static IP, network mast in host. The hosts works > fine with 3.8 kernel in BBB. > 4.1.15-ti-rt-43 image is from > https://rcn-ee.com/rootfs/bb.org/testing/2016-01-24/lxqt-4gb/bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz > > en5: flags=8923<UP,BROADCAST,SMART,PROMISC,SIMPLEX,MULTICAST> mtu 1486 > > ether 6c:ec:eb:b0:96:bd > > inet6 fe80::6eec:ebff:feb0:96bd%en5 prefixlen 64 scopeid 0xa > > nd6 options=1<PERFORMNUD> > > media: autoselect (<unknown type>) > > ping 192.168.7.2 > > PING 192.168.7.2 (192.168.7.2): 56 data bytes > > Request timeout for icmp_seq 0 > > Request timeout for icmp_seq 1 > > Request timeout for icmp_seq 2 > > ^C > > > On Wednesday, January 27, 2016 at 10:44:09 PM UTC-5, [email protected] > wrote: >> >> I experienced the same issue: >> BBB runs in 4.1.15-ti-rt-r43 >> Host runs in 4.2.5-300.fc23.x86_64. >> >> I thought I had network setup issue in host PC. So I checked the route, >> IP, net mask and gateway in host PC under 3.8 kernel, where host PC get >> connected to USB gadget ethernet correctly. >> >> But even I manually applied this setting for 4.1.15-ti-rt-r43. The >> connection is still broken. I wonder if/what DHCP server runs in 3.8? Is it >> possible that kernel USB gadget driver is broken in 4.1? >> >> thanks, >> Ricky >> >> >> On Wednesday, December 9, 2015 at 12:11:10 PM UTC-5, Fabian Dalbert wrote: >>> >>> seems to have been a driver compatibility problem on the host side >>> (linux mint 17.2, kernel 3.16). an update to linux mint 17.3 with kernel >>> 3.19 solved the problem. >>> >>> On Wednesday, December 9, 2015 at 9:13:47 AM UTC+1, Fabian Dalbert wrote: >>>> >>>> any ideas? >>>> >>> -- 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.
