1081 2011-05-18 08:38:13 +0000 [jasperforest] network fails to start on jasperforest sato image 2011-09-07 18:40:39 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration unspecified JasperForest Multiple RESOLVED FIXED Lin Tong is helping on that (8/4) Medium normal 1.1 1 jiajun.xu tong.lin dongxiao.xu dvhart ke.yu sgw shane.wang yp.bsp.watcher yp.watcher --- --- --- oldest_to_newest 13868 0 jiajun.xu 2011-05-18 08:38:13 +0000 Target: Jasperforest Sato image Image location: http://autobuilder.pokylinux.org/downloads/yocto-1.0/machines/jasperforest/jasperforest-bernard-5.0.0.tar.bz2 With the repackaging 1.0 sato image for jasperforest, when system start up, network fails to start up. Then network interface(eth0) will get a 169.254.xxx.xxx IP address after a while. I have to run "ifup eth0" by manual to make eth0 get IP address. I have asked Dongxiao to have a first look but not gotten any clue yet. 13908 1 dvhart 2011-05-19 13:32:25 +0000 Does the same thing happen with minimal? If not, I'm guessing you're running into a connmon issues similar to what we saw for the 1.0 demo. What is the contents of /etc/network/interfaces? I believe this to be a generic issue and not meta-intel specific. Juijun or Dongxio, can one of you assign this to yourself and mark as Accepted? 13917 2 jiajun.xu 2011-05-19 19:23:17 +0000 (In reply to comment #1) > Does the same thing happen with minimal? If not, I'm guessing you're running > into a connmon issues similar to what we saw for the 1.0 demo. What is the > contents of /etc/network/interfaces? I believe this to be a generic issue and > not meta-intel specific. > Juijun or Dongxio, can one of you assign this to yourself and mark as Accepted? Hi Darren, Minimal image has no connman so we always need to manually start up the network. I never met such issue on other BSPs. Assign the bug to Dongxiao. The /etc/network/interfaces contents as below: ######## # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # Wireless interfaces iface wlan0 inet dhcp wireless_mode managed wireless_essid any wpa-driver wext wpa-conf /etc/wpa_supplicant.conf iface atml0 inet dhcp # Wired or wireless interfaces iface eth0 inet dhcp iface eth1 inet dhcp # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 # Bluetooth networking iface bnep0 inet dhcp ######## 13932 3 dvhart 2011-05-20 10:55:58 +0000 (In reply to comment #2) > (In reply to comment #1) > > Does the same thing happen with minimal? If not, I'm guessing you're running > > into a connmon issues similar to what we saw for the 1.0 demo. What is the > > contents of /etc/network/interfaces? I believe this to be a generic issue and > > not meta-intel specific. > > Juijun or Dongxio, can one of you assign this to yourself and mark as Accepted? > > Hi Darren, > Minimal image has no connman so we always need to manually start up the > network. Adding "auto eth0" to /etc/network/interfaces will make it automatically bring up eth0. 15352 4 dongxiao.xu 2011-08-09 17:21:02 +0000 Assign this bug to Lin, Tong 15461 5 tong.lin 2011-08-15 02:12:39 +0000 I build the core-image-sato-jasperforest.hddimg with the latest packages and then run it. The bug disappears and the network works well. The ip address is 192.168.106.133. 15462 6 tong.lin 2011-08-15 02:13:39 +0000 I build the core-image-sato-jasperforest.hddimg with the latest packages and then run it. The bug disappears and the network works well. The ip address is 192.168.106.133. 16091 7 dongxiao.xu 2011-09-07 18:40:39 +0000 Close this bug since jasperforest can get the correct IP address with the latest build.