Building chromium os with kernel 3.18 for samus board

65 views
Skip to first unread message

Maksim Sisov

unread,
Nov 14, 2016, 8:25:28 AM11/14/16
to Chromium OS dev
Hi,

I have a pixel chromebook (samus board). I'm trying to build an image with kernel 3.18 in order to test some chromium changes on kernel 3.18 onwards.

I've modified the following var - USE=-kernel-3_14 kernel-3_18, which makes my image to be build against kernel 3-18 instead of 3-14. But I get some driver errors.

Here they are -

chromeos-kernel-3_18-9999:   LD      drivers/net/built-in.o
chromeos-kernel-3_18-9999: /usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51/ld.bfd.real: cannot find drivers/net/wireless-3.8/built-in.o: No such file or directory
chromeos-kernel-3_18-9999: make[3]: *** [/mnt/host/source/src/third_party/kernel/v3.18/scripts/Makefile.build:336: drivers/net/built-in.o] Error 1
chromeos-kernel-3_18-9999: make[3]: Target '__build' not remade because of errors.
chromeos-kernel-3_18-9999: make[2]: *** [/mnt/host/source/src/third_party/kernel/v3.18/scripts/Makefile.build:402: drivers/net] Error 2

and another -

chromeos-kernel-3_18-9999:   LD      drivers/usb/built-in.o
chromeos-kernel-3_18-9999: make[2]: Target '__build' not remade because of errors.
chromeos-kernel-3_18-9999: make[1]: *** [/mnt/host/source/src/third_party/kernel/v3.18/Makefile:963: drivers] Error 2
chromeos-kernel-3_18-9999: make[1]: Target '_all' not remade because of errors.
chromeos-kernel-3_18-9999: make[1]: Leaving directory '/build/samus/var/cache/portage/sys-kernel/chromeos-kernel-3_18'
chromeos-kernel-3_18-9999: make: *** [Makefile:145: sub-make] Error 2
chromeos-kernel-3_18-9999: make: Target '_all' not remade because of errors.
chromeos-kernel-3_18-9999:  * __helpers_die: WARNING: emake failed
chromeos-kernel-3_18-9999:  * If this failure is due to build-dir corruption, run:
chromeos-kernel-3_18-9999:  *   sudo rm -rf '/build/samus/var/cache/portage/sys-kernel/chromeos-kernel-3_18'
chromeos-kernel-3_18-9999:  * ERROR: sys-kernel/chromeos-kernel-3_18-9999::chromiumos failed (compile phase):
chromeos-kernel-3_18-9999:  *   command: emake ARCH=x86_64 LDFLAGS=-O1 -O2 --as-needed CROSS_COMPILE=x86_64-cros-linux-gnu- O=/build/samus/var/cache/portage/sys-kernel/chromeos-kernel-3_18 LD=/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51/ld  CC=x86_64-cros-linux-gnu-gcc -B/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51 CXX=x86_64-cros-linux-gnu-g++ -B/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51 -k WIFIVERSION=-3.8
chromeos-kernel-3_18-9999:  *
chromeos-kernel-3_18-9999:  * Call stack:
chromeos-kernel-3_18-9999:  *     ebuild.sh, line   93:  Called src_compile
chromeos-kernel-3_18-9999:  *   environment, line 5071:  Called cros-kernel2_src_compile
chromeos-kernel-3_18-9999:  *   environment, line 1530:  Called kmake '-k'
chromeos-kernel-3_18-9999:  *   environment, line 4005:  Called cw_emake 'ARCH=x86_64' 'LDFLAGS=-O1 -O2 --as-needed' 'CROSS_COMPILE=x86_64-cros-linux-gnu-' 'O=/build/samus/var/cache/portage/sys-kernel/chromeos-kernel-3_18' 'LD=/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51/ld ' 'CC=x86_64-cros-linux-gnu-gcc -B/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51' 'CXX=x86_64-cros-linux-gnu-g++ -B/usr/x86_64-pc-linux-gnu/x86_64-cros-linux-gnu/binutils-bin/2.25.51' '-k' 'WIFIVERSION=-3.8'
chromeos-kernel-3_18-9999:  *   environment, line 2126:  Called die
chromeos-kernel-3_18-9999:  * The specific snippet of code:
chromeos-kernel-3_18-9999:  *           die "command: emake $*";

In overall, my USE looks like this -

USE="acl amd64 bzip2 cros_host crypt cxx dri expat fortran hardened iconv ipv6 kernel-3_18 mmx mmxext modules mudflap multilib ncurses nls nptl nptlonly openmp pic pie python readline sse sse2 ssl sysfs transparent_hugepage unicode vaapi xattr xorg zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" QEMU_SOFTMMU_TARGETS="aarch64 arm i386 mips mips64 mips64el mipsel x86_64" QEMU_USER_TARGETS="aarch64 arm i386 mips mips64 mips64el mipsel x86_64" RUBY_TARGETS="ruby19 ruby18" TTY_CONSOLE="tty2" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa vga via vmware dummy v4l" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, SYNC, USE_PYTHON

Appreciate your help!

Vincent Palatin

unread,
Nov 14, 2016, 8:31:16 AM11/14/16
to Maksim Sisov, Chromium OS dev
On Mon, Nov 14, 2016 at 2:25 PM, Maksim Sisov <maksim...@intel.com> wrote:
> Hi,
>
> I have a pixel chromebook (samus board). I'm trying to build an image with
> kernel 3.18 in order to test some chromium changes on kernel 3.18 onwards.
>
> I've modified the following var - USE=-kernel-3_14 kernel-3_18, which makes
> my image to be build against kernel 3-18 instead of 3-14. But I get some
> driver errors.

Despite not being in your list below, it seems that you are building
with the "wireless38" USE flag (forcing the old Wifi stack),
you should either remove it from overlay-samus/make.conf or try with
USE="-wireless38"
> --
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>

Gwendal Grignou

unread,
Nov 14, 2016, 11:54:26 AM11/14/16
to Vincent Palatin, Maksim Sisov, Chromium OS dev
You can verify kernel_3-18 is using wireless38 flags with
"emerge-samus -pv chromeos-kernel-3_18".
Remove that falgs in overlay-samus/make.conf when compiling 3.18 on Samus.

Gwendal.

Gwendal Grignou

unread,
Nov 15, 2016, 9:21:00 PM11/15/16
to Sisov, Maksim, chromium-os-dev
On Tue, Nov 15, 2016 at 4:19 AM, Sisov, Maksim <maksim...@intel.com> wrote:
> Hi,
>
> I've managed to build an image with kernel 3.18, but iio drivers are missing. Do you know name the exact name of the packages I should include?
Which drivers are missing? Are you thinking about motion sensors
drivers for accelerometer/gyroscope?
The 3.18 cros ec sensor drivers do not work (yet) with the current
samus firmware. I am planning a firmware upgrade.

Gwendal.
>
> Thanks for your help.
> Br,
> Maksim
> ________________________________________
> From: gwe...@google.com [gwe...@google.com] on behalf of Gwendal Grignou [gwe...@chromium.org]
> Sent: Monday, November 14, 2016 18:54
> To: Vincent Palatin
> Cc: Sisov, Maksim; Chromium OS dev
> Subject: Re: [cros-dev] Building chromium os with kernel 3.18 for samus board
> You received this message because you are subscribed to the Google Groups "Chromium OS dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.
>
> ---------------------------------------------------------------------
> Intel Finland Oy
> Registered Address: PL 281, 00181 Helsinki
> Business Identity Code: 0357606 - 4
> Domiciled in Helsinki
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>

Sisov, Maksim

unread,
Nov 16, 2016, 2:46:35 AM11/16/16
to Gwendal Grignou, chromium-os-dev
Yes, I am talking about motion sensors + ambient light sensor. We are developing generic sensors API and I need to test sensors with 3.14 and 3.18 onwards.
________________________________________
From: gwe...@google.com [gwe...@google.com] on behalf of Gwendal Grignou [gwe...@chromium.org]
Sent: Wednesday, November 16, 2016 04:20
To: Sisov, Maksim
Cc: chromium-os-dev
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages