Bug 1081

Summary:	[jasperforest] network fails to start on jasperforest sato image
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Jiajun Xu <jiajun.xu>
Component:	bsps-configuration	Assignee:	Tong Lin <tong.lin>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	dongxiao.xu, dvhart, ke.yu, sgw, shane.wang, yp.bsp.watcher, yp.watcher
Version:	unspecified
Target Milestone:	1.1
Hardware:	JasperForest
OS:	Multiple
Whiteboard:	Lin Tong is helping on that (8/4)
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Jiajun Xu 2011-05-18 08:38:13 UTC

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.

Comment 1 Darren Hart 2011-05-19 13:32:25 UTC

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?

Comment 2 Jiajun Xu 2011-05-19 19:23:17 UTC

(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
########

Comment 3 Darren Hart 2011-05-20 10:55:58 UTC

(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.

Comment 4 Dongxiao Xu 2011-08-09 17:21:02 UTC

Assign this bug to Lin, Tong

Comment 5 Tong Lin 2011-08-15 02:12:39 UTC

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.

Comment 6 Tong Lin 2011-08-15 02:13:39 UTC

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.

Comment 7 Dongxiao Xu 2011-09-07 18:40:39 UTC

Close this bug since jasperforest can get the correct IP address with the latest build.