Booting alternate kernels 4.6~4.7

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Booting alternate kernels 4.6~4.7

Unread post by brad » Sat Apr 30, 2016 11:47 am

Trying to get my C2 with a standard hardkernel image to boot with new kernel version. Yes I know this may be challenging but hear me out...

- Standard hardkernel Ubuntu image, completely updated
- Linux 4.6-next kernel, compiled natively on the odroid, with amlogic-meson platform, meson i2c, meson spi, RTL821x PHY support, sd/mmc, gpio & device tree support.
- Modifications to uboot.ini to attempt to disable hdmi and to point to the new device tree meson-gxbb-odroidc2.dtb

Im interesting in initially minimal support for odroid features as I will be running in headless mode with no display support. I will need Ethernet for ssh access and web interface and also access to sdcard storage for the OS. Im not interested in usb, gpu / hdmi, audio yet.

Now I currently dont have a UART -> usb interface so cannot see the console during boot.

With my current set-up im just getting red and blue lights on solid and I cant see the console to see what uboot is doing. I suspect it has something to do with either sd/mmc or maybe memory controller support. Possibly even looking and failing for display support. If I have it plugged into hdmi and ethernet ports I can see that its in a reset cycle with both ethernet and hdmi flicking on and off every 2 secs or so. To me it appears to be failing to load the boot Image and then going into a reset cycle.

Now to some questions...

- Can I force or set uboot to log the console to the fat partition for later review (im ordering a UART->serial interface now)
- A solid blue light indicates that uboot is running but no pulse from the kernel, Does this mean uboot has failed to attempt to load the linux Image or does it mean the Image is not pinging back to uboot? I guess I could mean either.
- Newer versions of uboot seems to have some nice features to assist me has anyone attempted to get a newer version of uboot working with the C2?

Some of my reasoning for the newer kernel..

- Improved support for new devices (in particular some codecs with i2c and i2s support im interested in developing alsa drivers for, eg PCM3168A)
- Current odroid kernel is EOL (I dont want to be developing against something that is End of Life)
- Improved support for ZFS filesystem (or maybe btrfs but I dont like its stability for what I want)
- New dev kernel now supports most features for meson im interested in

If im barking up the wrong tree here please let me know, I haven't had much experience with uboot as yet.

Thanks for your time.

Brad.

umiddelb
Posts: 451
Joined: Thu Jan 29, 2015 6:42 am
languages_spoken: English, German
ODROIDs: ODROID-C1, ODROID-XU4, ODROID-C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels

Unread post by umiddelb » Sun May 01, 2016 6:36 am

brad wrote: Now I currently dont have a UART -> usb interface so cannot see the console during boot.
You may use any of the available 3.3 Volt USB - UART connectors (or another device offering 3.3V UART ports like the C1 or PINE64) and three breadboard wires to get serial access...

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sun May 01, 2016 8:35 am

umiddelb wrote:
brad wrote: Now I currently dont have a UART -> usb interface so cannot see the console during boot.
You may use any of the available 3.3 Volt USB - UART connectors (or another device offering 3.3V UART ports like the C1 or PINE64) and three breadboard wires to get serial access...
Thanks ive got one on order now from local supplier, dont have any 3.3v ones laying around :|

umiddelb
Posts: 451
Joined: Thu Jan 29, 2015 6:42 am
languages_spoken: English, German
ODROIDs: ODROID-C1, ODROID-XU4, ODROID-C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels

Unread post by umiddelb » Mon May 02, 2016 3:16 am

For the meantime you may read this blog post about u-uboot, and this project. I'm using u-571 to boot alternate kernels / linux userlands from different devices. But it still requires serial access at this time.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Tue May 03, 2016 5:55 pm

Thanks for this info its very helpful, hopefully I receive my new UART -> USB soon so I can see what is happening. Ill be sure to share.

Best Regards, Brad.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sat May 07, 2016 11:05 am

If anyone is interested ive connected up the UART -> usb ive just received. This is the reboot cycle I can see...
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 119780
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000017c0
Wait bl30...Done
Sending bl301......OK.
Run bl301...
0100000, size: 0x00011130x00020200, des: 0x


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630 2015-10-28 15:24:31 xiaobo.gu@droid05]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: ef be Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00065af0
ad de d f0 ad ba ef be ad de not ES chip
[0.234679 Inits done]
secure task start!
high task start!
low task start!
NOTICE: BL3-1: v1.0(debug):4d2e34d
NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015
INFO: BL3-1: Initializing runtime services
INFO: BL3-1: Preparing for EL3 exit to normal world
INFO: BL3-1: Next image address = 0x1000000
INFO: BL3-1: Next image spsr = 0x3c9


U-Boot 2015.01-gf416a76 (May 01 2016 - 23:20:06)

DRAM: 2 GiB
Relocation Offset is: 76f40000
-------------------------------------------------
* Welcome to Hardkernel's ODROID-C2
-------------------------------------------------
CPU : AMLogic S905
S/N : HKC213254DFCD95D
MAC : 00:1e:06:33:25:dd
BID : HKC2211602
-------------------------------------------------
register usb cfg[1][0] = 0000000077f97dc0
register usb cfg[0][1] = 0000000077f97de0
vpu detect type: 5
vpu clk_level = 7
set vpu clk: 666667000Hz, readback: 666660000Hz(0x300)
MMC: aml_priv->desc_buf = 0x0000000073f38d30
aml_priv->desc_buf = 0x0000000073f3aec0
SDIO Port B: 0, SDIO Port C: 1
ret = 1 .[mmc_init] mmc init success
In: serial
Out: serial
Err: serial
----------------------------------
MMC Size : 32 GB
----------------------------------
reading boot-logo.bmp.gz
** Unable to read file boot-logo.bmp.gz **
reading boot-logo.bmp
** Unable to read file boot-logo.bmp **
movi: the partiton 'logo' is reading...

MMC read: dev # 0, block # 58976, count 4096 ... 4096 blocks read: OK
hpd_state=1
[CANVAS]addr=0x3f800000 width=3840, height=1440

[720p60hz] is invalid for cvbs.
set hdmitx VIC = 4
hdmitx phy setting done
set hdmitx VIC = 4
hdmitx phy setting done
Error: Bad gzipped data
There is no valid bmp file at the given address
Saving Environment to MMC...
Writing to MMC(0)... done
Net: Meson_Ethernet
Hit [Enter] key twice to stop autoboot: 0
reading boot.ini
2763 bytes read in 4 ms (673.8 KiB/s)
cfgload: applying boot.ini...
cfgload: setenv m "1080p60hz" # Progressive 60Hz
cfgload: setenv m_bpp "32"
cfgload: setenv condev "console=ttyS0,115200n8 console=tty0" # on both
cfgload: setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait rw ${condev} no_console_suspend hdmimode=${m} m_bpp=${m_bpp} vout=${vout} fsck.fix=yes net.ifnames=0"
cfgload: setenv loadaddr "0x11000000"
cfgload: setenv dtb_loadaddr "0x1000000"
cfgload: setenv initrd_loadaddr "0x13000000"
cfgload: fatload mmc 0:1 ${initrd_loadaddr} uInitrd-4.6.0-rc3-next-20160415
reading uInitrd-4.6.0-rc3-next-20160415
9279777 bytes read in 410 ms (21.6 MiB/s)
cfgload: fatload mmc 0:1 ${loadaddr} vmlinuz-4.6.0-rc3-next-20160415
reading vmlinuz-4.6.0-rc3-next-20160415
10562048 bytes read in 473 ms (21.3 MiB/s)
cfgload: fatload mmc 0:1 ${dtb_loadaddr} meson-gxbb-odroidc2.dtb
reading meson-gxbb-odroidc2.dtb
2734 bytes read in 5 ms (533.2 KiB/s)
cfgload: booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
"Synchronous Abort" handler, esr 0x96000010
ELR: 77f4a790
LR: 77f4a784
x0 : 0000000077fa6648 x1 : 0000000000080000
x2 : 0000000000b13000 x3 : 0000000000b13000
x4 : 000000000000006c x5 : 0000000011000000
x6 : 0000000077fa6508 x7 : 0000000000000044
x8 : 0000000077f99740 x9 : 0000000000000000
x10: 0000000073f37398 x11: 0000000077f86000
x12: 000000000000000f x13: 0000000000000000
x14: 0000000000000000 x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 0000000073f37e28 x19: 0000000077fa6508
x20: 0000000011000000 x21: 0000000073f3f380
x22: 0000000000000003 x23: 0000000073f3f388
x24: 0000000000000000 x25: 0000000077f9b780
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 0000000073f37600

Resetting CPU ...

resetting ...
Its failing early with what appears to be stack alignment issue for an external device, found something from arm which may be of relevance to the issue http://infocenter.arm.com/help/index.js ... 14269.html

Now that I can see what is happening at boot my short term plan is upgrade to latest version before attempting to debug to far.

- Remove display support from boot.ini
- update to latest next kernel (rc6 rather than rc3) disabling further unneeded features in the kernel
- attempt to update uboot to newer version using some of the information umiddelb has provided
- research the forums here some more to see what others have experienced
- analyse hardkernel source to see how it may have been overcome in earlier kernel releases.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sat May 07, 2016 11:59 pm

latest kernel and still the same issues, and tryed to disable uInitrd..

Code: Select all

cfgload: applying boot.ini...
cfgload: setenv m "1080p60hz" # Progressive 60Hz
cfgload: setenv m_bpp "32"
cfgload: setenv condev "console=ttyS0,115200n8 console=tty0"   # on both
cfgload: setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait rw ${condev} no_console_suspend fsck.fix=yes net.ifnames=0"
cfgload: setenv loadaddr "0x11000000"
cfgload: setenv dtb_loadaddr "0x1000000"
cfgload: setenv initrd_loadaddr "0x13000000"
cfgload: fatload mmc 0:1 ${loadaddr} vmlinuz-4.6.0-rc6-next-20160506
reading vmlinuz-4.6.0-rc6-next-20160506
9069568 bytes read in 402 ms (21.5 MiB/s)
cfgload: fatload mmc 0:1 ${dtb_loadaddr} meson-gxbb-odroidc2.dtb
reading meson-gxbb-odroidc2.dtb
2734 bytes read in 5 ms (533.2 KiB/s)
cfgload: booti ${loadaddr}  ${dtb_loadaddr}
"Synchronous Abort" handler, esr 0x96000010
ELR:     77f4a790
LR:      77f4a784
x0 : 0000000077fa6648 x1 : 0000000000080000
x2 : 00000000009a6000 x3 : 00000000009a6000
x4 : 00000000000000a9 x5 : 0000000011000000
x6 : 0000000077fa6508 x7 : 0000000000000044
x8 : 0000000077f99740 x9 : 0000000000000000
x10: 0000000073f37398 x11: 0000000077f86000
x12: 000000000000000f x13: 0000000000000000
x14: 0000000000000000 x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 0000000073f37e28 x19: 0000000077fa6508
x20: 0000000011000000 x21: 0000000073f3f2f0
x22: 0000000000000002 x23: 0000000073f3f2f8
x24: 0000000000000000 x25: 0000000077f9b780
x26: 0000000000000000 x27: 0000000000000000
x28: 0000000000000000 x29: 0000000073f37600

Resetting CPU ...
Now looking further into

- create a kernel image which current u-boot version can boot without a sychronous abort, going to try using bootm see if I can overcome this
- upgrade u-boot to a newer version

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sun May 08, 2016 6:30 pm

OK, ive tried booting with the normal u-boot version and cannot get around the Synchronous Abort error. tried boot-m and many different configuration settings in both kernel and u-boot.

Now im pushing forward with getting C2 to boot with the master branch of u-boot and fortunately others have already started the good work.

Ive got it to booting now into full uboot, but now work on starting the new kernel (or even the hardkernel for the moment)...

Code: Select all

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 243811
no sdio debug board detected 

BL2 Built : 11:44:26, Nov 25 2015. 
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK. 
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000017c0
Wait bl30...Done
Sending bl301......OK. 
Run bl301...
 0x10100000, size: 0x0001113020200, des


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630 2015-10-28 15:24:31 xiaobo.gu@droid05]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: ef beLoad bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x0004de60
 ad de d f0 ad ba ef be ad de not ES chip
[0.358605 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9
No match for driver 'eth_designware'
Some drivers were not found


U-Boot 2016.05-rc3-gbbca710-dirty (May 08 2016 - 15:35:57 +1000) odroid-c2

DRAM:  2 GiB
No matsing default environment

In:    serial@4c0
Out:   serial@4c0
Err:   serial@4c0
Net:   No ethernet found.
=>

Patches or uboot are here https://patchwork.ozlabs.org/project/ub ... tter=47773 thanks to Beniamino Galvani (ive been trying with version 6, but he released version 7 today)

Need to also copy over the fips directory from the original hardkernel source along with the sd_fuse dir.

You need to manually run the aml scripts/ binaries in the fips dirs to sign / crypto the newly generated u-boot to enable the first stage loader to be able to boot u-boot. There is no doco I can find on this but the hardkernel original Makefile contains enough enough information to work it out.

It goes something along the lines of

- Download latest u-boot version master branch git://git.denx.de/u-boot.git
- Patch with patches listed above
- run make odroid-cd_defconfig
- run make menuconfig if you need
- make
- copy across sd_fuse and fips dirs from original hardkernel u-boot source
- Log of the rest.... (See Makefile in org hardkernel u-boot source for info, if I get somewhere further ill make some doco)

Code: Select all

brad@proaudio:~/new/u-boot/fip/gxb$ cp ../../u-boot.bin bl33.bin
brad@proaudio:~/new/u-boot/fip/gxb$ ../fip_create --bl30 bl30.bin --bl301 bl301.bin --bl31 bl31.bin --bl33 bl33.bin fip.bin
Updating "fip.bin"
brad@proaudio:~/new/u-boot/fip/gxb$ ../fip_create --dump fip.bin
Firmware Image Package ToC:
---------------------------
- SCP Firmware BL3-0: offset=0x4000, size=0x9E88
- SCP Firmware BL3-0-1: offset=0x10000, size=0x1758
- EL3 Runtime Firmware BL3-1: offset=0x14000, size=0x110D0
- Non-Trusted Firmware BL3-3: offset=0x28000, size=0x4DEEE
---------------------------
brad@proaudio:~/new/u-boot/fip/gxb$ cat bl2.package fip.bin > boot_new.bin
brad@proaudio:~/new/u-boot/fip/gxb$ ./aml_encrypt_gxb --bootsig --input boot_new.bin --output u-boot.bin
brad@proaudio:~/new/u-boot/fip/gxb$ dd if=u-boot.bin of=../../sd_fuse/u-boot.bin bs=512 skip=96
960+0 records in
960+0 records out
491520 bytes (492 kB) copied, 0.00995591 s, 49.4 MB/s
brad@proaudio:~/new/u-boot/fip/gxb$ cd ../../sd_fuse/
brad@proaudio:~/new/u-boot/sd_fuse$ dd if=bl1.bin.hardkernel of=../u-boot.bin conv=fsync,notrunc bs=512 skip=1 seek=1
96+0 records in
96+0 records out
49152 bytes (49 kB) copied, 0.0421576 s, 1.2 MB/s
brad@proaudio:~/new/u-boot/sd_fuse$ dd if=bl1.bin.hardkernel of=../u-boot.bin conv=fsync
97+0 records in
97+0 records out
49664 bytes (50 kB) copied, 0.0449271 s, 1.1 MB/s
brad@proaudio:~/new/u-boot/sd_fuse$ dd if=bl1.bin.hardkernel of=../u-boot.bin conv=fsync,notrunc bs=512 skip=1 seek=1
96+0 records in
96+0 records out
49152 bytes (49 kB) copied, 0.0463661 s, 1.1 MB/s
brad@proaudio:~/new/u-boot/sd_fuse$ dd if=u-boot.bin of=../u-boot.bin conv=fsync,notrunc bs=512 skip=1 seek=97
959+0 records in
959+0 records out
491008 bytes (491 kB) copied, 0.0768868 s, 6.4 MB/s
brad@proaudio:~/new/u-boot/sd_fuse$ ./sd_fusing.sh /dev/mmcblk0
[sudo] password for brad: 
442+0 records in
442+0 records out
442 bytes (442 B) copied, 0.00739899 s, 59.7 kB/s
96+0 records in
96+0 records out
49152 bytes (49 kB) copied, 0.028556 s, 1.7 MB/s
960+0 records in
960+0 records out
491520 bytes (492 kB) copied, 0.135575 s, 3.6 MB/s
not an sg device, or old sg driver
eject: unable to eject, last error: Invalid argument
Finished.
Install sdcard into odroid C2 and boot into u-boot

Ill update again if I have new information.

User avatar
odroid
Site Admin
Posts: 33277
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 366 times
Been thanked: 448 times
Contact:

Re: Booting alternate kernels

Unread post by odroid » Sun May 08, 2016 6:38 pm

Oh~~ You made the latest "2016.05-rc3" u-boot work on the C2. :o

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sun May 08, 2016 9:01 pm

odroid wrote:Oh~~ You made the latest "2016.05-rc3" u-boot work on the C2. :o
Yes and hopefully the 4.6-rc7 kernel is next, I think there will be a bit missing at the moment but I hope to see

u-boot starts but there is no mmc driver only UART and ethernet at the moment. Going to either try tftp or see if I can load and pass through from the initial bootloader

xxxbugxxxx
Posts: 10
Joined: Thu May 05, 2016 5:50 pm
languages_spoken: english
ODROIDs: c2
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels

Unread post by xxxbugxxxx » Mon May 09, 2016 10:24 am

Found something maybe helpful to u here

http://rglinuxtech.com/?p=1723



ARM64 – Odroid C2 U-Boot – Latest..
Posted on May 7, 2016 by RG
I discovered there was a later version (6) of the U-boot patch for the Odroid C2, and also – after more research – found the reason for the compile error…
It turns out that the GIT version (May 5, 2016) of U-boot currently needs two patches..
The first one is to provide psci_system_reset for armv8, and details can be found here: http://article.gmane.org/gmane.comp.boo ... ot/259967/
The second is the C2 support patch itself, which needs psci_system_reset to compile correctly, and details of version 6 of the patch can be found here: http://article.gmane.org/gmane.comp.boo ... ot/259968/
After applying these two patches, and adding the Hardkernel binary in sd_fuse, then U-boot compiled and installed OK, but the C2 still failed to initialise:
BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton
Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
aml log : SIG CHK : 351 for address 0x01700000
reset...
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
<< repeated... >>
I had already found that the latest ‘mainline’ kernel code for the C2 (in linux-next) would not boot with the Hardkernel-supplied version of U- Boot, which is why this new/patched version is needed..
More info when I have made some more progress..
Robert Gadsdon. May 6, 2016.

Share this:
TwitterLinkedIn
Posted in aarch64, alpha release, ARM64, boot, compilation, Crash and Burn.., Hacks, Odroid C2, Opinion, Performance, U-Boot Tagged boot fails, compile cleanly, odroid c2, psci_system_reset, two patches needed, u-boot permalink

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Thu May 12, 2016 6:58 am

The linux-next kernel can be started with ethernet support by loading it via tftp.

The 2 immediate issues now

- mmc support in u-boot
- mmc support for linux kernel

I dont have much time during the week but will provide more details when I can.

Robert from this post http://rglinuxtech.com/?p=1723 has also been successful

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sun May 15, 2016 12:27 pm

A little update to where I am booting into rc7 trying to mount rootfs over NFS (its all a little messy at the moment)....

U-BOOT
========
- Latest rc3 U-boot booting with version 7 patches listed in post above not yet in official uboot master
- Number of changes to u-boot via menuconfig (some not needed but im cleaning up to minimise to I can produce a decent config file)
- enable tftp environment manually via a script to past into UART (some not needed)
- boot kernel from tftp server via ethernet
- pass boot args to mount NFS root filesystem

LINUX KERNEL (rc7-next)
======================

- Latest master branch from kernel.org, no patches applied
- Numerous changes to kernel via menuconfig for testing at the moment (going to get back to a clean environment soon)
- Support for early network, NFS, and root file-system support
- Removal of anything not needed in kernel to reduce size

I'm now working on setting the root file-system up on the nfs host to see if I can actually mount the rootfs over Ethernet, more to come hopefully soon when I get nfs working (im manually setting U-boot environment see log below)...

Code: Select all

=> GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 282583
no sdio debug board detected 

BL2 Built : 11:44:26, Nov 25 2015. 
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK. 
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000017c0
Wait bl30...Done
Sending bl301......OK. 
Run bl301...
1 from SD, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630 2015-10-28 15:24:31 xiaobo.gu@droid05]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: ef be ad de d f0 ad ba Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00043600
ef be ad de not ES chip
[0.397035 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2016.05-rc3-g4cf4600-dirty (May 15 2016 - 12:10:12 +1000) odroid-c2

DRAM:  2 GiB
Using default environment

In:    serial@4c0
Out:   serial@4c0
Err:   serial@4c0
Net:   eth0: eth_designware
=> setenv kernel_addr 11000000
=> setenv fdt_addr 1000000
=> setenv tftpbootfile Image
=> setenv bootfile /nfs_export/Image
=> setenv tftpfdtfile meson-gxbb-odroidc2.dtb
=> setenv fdtfile /nfs_export/meson-gxbb-odroidc2.dtb
=> setenv ipaddr 10.1.1.105
=> setenv serverip 10.1.1.104
=> setenv netdev eth0
=> setenv hostname 10.1.1.105
=> setenv rootpath /nfs_export/rootfs
=> setenv nfsargs "setenv bootargs root=/dev/nfs rw nfsroot=10.1.1.104:/nfs_export/rootfs"
=> setenv addip 'setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off'
=> setenv net_nfs 'tftp ${kernel_addr} ${tftpbootfile};tftp ${fdt_addr} ${tftpfdtfile};run nfsargs addip;booti ${kernel_addr} - ${fdt_addr}'
=> run net_nfs
Speed: 100, full duplex
Using eth_designware device
TFTP from server 10.1.1.104; our IP address is 10.1.1.105
Filename 'Image'.
Load address: 0x11000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###########################################################
         2.3 MiB/s
done
Bytes transferred = 9444352 (901c00 hex)
Speed: 100, full duplex
Using eth_designware device
TFTP from server 10.1.1.104; our IP address is 10.1.1.105
Filename 'meson-gxbb-odroidc2.dtb'.
Load address: 0x1000000
Loading: #
         889.6 KiB/s
done
Bytes transferred = 2734 (aae hex)
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
   Loading Device Tree to 000000007df9a000, end 000000007df9daad ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.6.0-rc7-next-20160513+ (odroid@odroid64) (gcc version 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1) ) #5 SMP PREEMPT Sun May 15 11:45:10 AEST 2016
Boot CPU: AArch64 Processor [410fd034]
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
cma: Reserved 8 MiB at 0x000000007f800000
psci: probing for conduit method from DT.
psci: PSCIv0.2 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
psci: Trusted OS migration not required
percpu: Embedded 21 pages/cpu @ffffffc07f791000 s45848 r8192 d31976 u86016
Detected VIPT I-cache on CPU0
CPU features: enabling workaround for ARM erratum 845719
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 512064
Kernel command line: root=/dev/nfs rw nfsroot=10.1.1.104:/nfs_export/rootfs ip=10.1.1.105:10.1.1.104:::10.1.1.105:eth0:off
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
software IO TLB [mem 0x79000000-0x7d000000] (64MB) mapped at [ffffffc079000000-ffffffc07cffffff]
Memory: 1960120K/2080768K available (5808K kernel code, 839K rwdata, 1868K rodata, 704K init, 947K bss, 112456K reserved, 8192K cma-reserved)
Virtual kernel memory layout:
    modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)
    vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)
      .text : 0xffffff8008080000 - 0xffffff8008620000   (  5760 KB)
    .rodata : 0xffffff8008620000 - 0xffffff8008800000   (  1920 KB)
      .init : 0xffffff8008800000 - 0xffffff80088b0000   (   704 KB)
      .data : 0xffffff80088b0000 - 0xffffff8008981c00   (   839 KB)
       .bss : 0xffffff8008981c00 - 0xffffff8008a6e814   (   948 KB)
    fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)
    PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)
    vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)
              0xffffffbf00040000 - 0xffffffbf02000000   (    31 MB actual)
    memory  : 0xffffffc001000000 - 0xffffffc080000000   (  2032 MB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Preemptible hierarchical RCU implementation.
        Build-time adjustment of leaf fanout to 64.
NR_IRQS:64 nr_irqs:64 0
GIC: Using split EOI/Deactivate mode
Architected cp15 timer(s) running at 24.00MHz (phys).
clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
Console: colour dummy device 80x25
console [tty0] enabled
Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
pid_max: default: 32768 minimum: 301
Security Framework initialized
AppArmor: AppArmor initialized
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
ftrace: allocating 23085 entries in 91 pages
ASID allocator initialised with 65536 entries
EFI services will not be available.
Detected VIPT I-cache on CPU1
CPU1: Booted secondary processor [410fd034]
Detected VIPT I-cache on CPU2
CPU2: Booted secondary processor [410fd034]
Detected VIPT I-cache on CPU3
CPU3: Booted secondary processor [410fd034]
Brought up 4 CPUs
SMP: Total of 4 processors activated.
CPU features: detected feature: 32-bit EL0 Support
CPU: All CPU(s) started at EL2
alternatives: patching kernel code
devtmpfs: initialized
DMI not present or invalid.
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
NET: Registered protocol family 16
vdso: 2 pages (1 code @ ffffff8008626000, 1 data @ ffffff80088b4000)
hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
DMA: preallocated 256 KiB pool for atomic allocations
Serial: AMBA PL011 UART driver
HugeTLB registered 2 MB page size, pre-allocated 0 pages
SCSI subsystem initialized
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
dmi: Firmware registration failed.
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
clocksource: Switched to clocksource arch_sys_counter
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
AppArmor: AppArmor Filesystem Enabled
NET: Registered protocol family 2
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
UDP hash table entries: 1024 (order: 3, 32768 bytes)
UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
futex hash table entries: 1024 (order: 5, 131072 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(0.156:1): initialized
workingset: timestamp_bits=44 max_order=19 bucket_order=0
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
io scheduler noop registered (default)
io scheduler deadline registered
io scheduler cfq registered
c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 10, base_baud = 1500000) is a meson_uart
console [ttyAML0] enabled
Unable to detect cache hierarchy from DT for CPU 0
loop: module loaded
mtdoops: mtd device (mtddev=name/number) must be supplied
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Synopsys Designware Multimedia Card Interface Driver
ledtrig-cpu: registered to indicate activity on CPUs
GACT probability on
Mirror/redirect action on
u32 classifier
    Performance counters on
    input device check on
    Actions configured
NET: Registered protocol family 17
NET: Registered protocol family 15
NET: Registered protocol family 35
Key type dns_resolver registered
AppArmor: AppArmor sha1 policy hashing enabled
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.6.0-rc7-next-20160513+ #5
Hardware name: Hardkernel ODROID-C2 (DT)
Call trace:
[<ffffff8008088f08>] dump_backtrace+0x0/0x1d0
[<ffffff80080890fc>] show_stack+0x24/0x30
[<ffffff800839bbf4>] dump_stack+0x90/0xb0
[<ffffff800816b8bc>] panic+0x114/0x250
[<ffffff80088011c4>] mount_block_root+0x200/0x254
[<ffffff8008801330>] mount_root+0x118/0x130
[<ffffff8008801480>] prepare_namespace+0x138/0x180
[<ffffff8008800d8c>] kernel_init_freeable+0x218/0x23c
[<ffffff8008608344>] kernel_init+0x18/0x104
[<ffffff8008084e10>] ret_from_fork+0x10/0x40
SMP: stopping secondary CPUs
Kernel Offset: disabled
Memory Limit: none
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

mscdex
Posts: 74
Joined: Sun Jan 04, 2015 11:09 am
languages_spoken: english
ODROIDs: ODROID C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels

Unread post by mscdex » Tue May 17, 2016 1:55 am

So the Linux 4.6 kernel was released today. Can someone post about the current state of what works and what doesn't work for the C2 in the 4.6 release?

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Tue May 17, 2016 7:49 am

Morning,
Currently the 4.6 release kernel release has very minimal support for the C2...

- UART, memory, CPU & possibly Ethernet.

There is much missing including, sdcard/ mmc, sound, video, gpio, LED, USB, etc. but now that the 4.6 is booting progress will be much quicker. Look forward to see what
is incorporated in release 4.7.

New U-boot version also has minimal support for odroid C2, and a new mmc driver patch for sd card is available so it may now be possible to boot the kernel from the sdcard
but still no mmc for Linux.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Mon May 23, 2016 9:15 pm

Still trying to get kernel 4.6 to fully boot using tftp, uInitrd & NFS but no matter which method I try I hit a kernel panic following execution of a el0_svc_naked+0x24/0x28

An example boot log with kgdb is in kgdb.txt attached
An example boot log with UBSAN events is in ubsan.txt attached

The logs are an interesting look if you have the time, but im still some way off getting anything workable on the NFS path. If anyone has any suggestions or leads on how to workaround or solve the issues above please let me know.

In addition latest u-boot works well with the patches applied hopefully these make it through to a stable version for odroid-c2 in time. sd & emmc support is being tested also and hopefully this is included rather than having to use tftp to boot. (although it suits me fine)
Attachments
ubsan.txt
ubsan events + debug events 4.6 kernel
(165.89 KiB) Downloaded 152 times
kgdb.txt
kgdb + extra debug 4.6 kernel
(128.19 KiB) Downloaded 182 times

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sun May 29, 2016 3:08 pm

I've finally got a patched version of 4.6.0 booting with NFS..
Had to snip the start to fit it in...

Code: Select all

[    0.000000] psci: Trusted OS migration not required
[    0.000000] percpu: Embedded 19 pages/cpu @ffffffc07f794000 s37144 r8192 d32488 u77824
[    0.000000] pcpu-alloc: s37144 r8192 d32488 u77824 alloc=19*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: enabling workaround for ARM erratum 845719
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 512064
[    0.000000] Kernel command line: debug root=/dev/nfs rw ip=dhcp nfsroot=10.1.1.106:/nfs_export/rootfs/4.6.0+ consolelog=9
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] software IO TLB [mem 0x78a00000-0x7ca00000] (64MB) mapped at [ffffffc078a00000-ffffffc07c9fffff]
[    0.000000] Memory: 1954704K/2080768K available (5570K kernel code, 357K rwdata, 1916K rodata, 448K init, 775K bss, 117872K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)
[    0.000000]     vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)
[    0.000000]       .text : 0xffffff8008080000 - 0xffffff80085e0000   (  5504 KB)
[    0.000000]     .rodata : 0xffffff80085e0000 - 0xffffff80087d0000   (  1984 KB)
[    0.000000]       .init : 0xffffff80087d0000 - 0xffffff8008840000   (   448 KB)
[    0.000000]       .data : 0xffffff8008840000 - 0xffffff8008899720   (   358 KB)
[    0.000000]        .bss : 0xffffff8008899720 - 0xffffff800895b3d4   (   776 KB)
[    0.000000]     fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)
[    0.000000]     PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)
[    0.000000]     vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)
[    0.000000]               0xffffffbf00040000 - 0xffffffbf02000000   (    31 MB actual)
[    0.000000]     memory  : 0xffffffc001000000 - 0xffffffc080000000   (  2032 MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000] NR_IRQS:64 nr_irqs:64 0
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000092] Console: colour dummy device 80x25
[    0.000544] console [tty0] enabled
[    0.000559] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.000581] pid_max: default: 32768 minimum: 301
[    0.000652] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000666] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.001239] ASID allocator initialised with 65536 entries
[    0.040682] Detected VIPT I-cache on CPU1
[    0.040712] CPU1: Booted secondary processor [410fd034]
[    0.056681] Detected VIPT I-cache on CPU2
[    0.056696] CPU2: Booted secondary processor [410fd034]
[    0.072695] Detected VIPT I-cache on CPU3
[    0.072709] CPU3: Booted secondary processor [410fd034]
[    0.072739] Brought up 4 CPUs
[    0.072804] SMP: Total of 4 processors activated.
[    0.072816] CPU features: detected feature: 32-bit EL0 Support
[    0.072830] CPU: All CPU(s) started at EL2
[    0.072851] alternatives: patching kernel code
[    0.073579] devtmpfs: initialized
[    0.074656] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.074863] pinctrl core: initialized pinctrl subsystem
[    0.075356] NET: Registered protocol family 16
[    0.075685] vdso: 2 pages (1 code @ ffffff80085e6000, 1 data @ ffffff8008844000)
[    0.075709] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.076168] DMA: preallocated 256 KiB pool for atomic allocations
[    0.076207] Serial: AMBA PL011 UART driver
[    0.088306] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.088930] usbcore: registered new interface driver usbfs
[    0.088969] usbcore: registered new interface driver hub
[    0.089014] usbcore: registered new device driver usb
[    0.089110] pps_core: LinuxPPS API ver. 1 registered
[    0.089122] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.089147] PTP clock support registered
[    0.089668] clocksource: Switched to clocksource arch_sys_counter
[    0.089746] VFS: Disk quotas dquot_6.6.0
[    0.089785] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.089864] FS-Cache: Loaded
[    0.090003] CacheFiles: Loaded
[    0.093904] NET: Registered protocol family 2
[    0.094268] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[    0.094367] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[    0.094559] TCP: Hash tables configured (established 16384 bind 16384)
[    0.094630] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[    0.094672] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[    0.094787] NET: Registered protocol family 1
[    0.094999] RPC: Registered named UNIX socket transport module.
[    0.095011] RPC: Registered udp transport module.
[    0.095022] RPC: Registered tcp transport module.
[    0.095032] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.095168] Trying to unpack rootfs image as initramfs...
[    0.284044] Freeing initrd memory: 6516K (ffffffc07d940000 - ffffffc07df9d000)
[    0.284263] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    0.285222] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    0.285295] audit: initializing netlink subsys (disabled)
[    0.285355] audit: type=2000 audit(0.280:1): initialized
[    0.285738] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.291438] FS-Cache: Netfs 'nfs' registered for caching
[    0.291772] NFS: Registering the id_resolver key type
[    0.291805] Key type id_resolver registered
[    0.291816] Key type id_legacy registered
[    0.291831] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.291973] fuse init (API version 7.24)
[    0.293856] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.293940] io scheduler noop registered (default)
[    0.293952] io scheduler deadline registered
[    0.294037] io scheduler cfq registered
[    0.318351] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 10, base_baud = 1500000) is a meson_uart
[    0.972193] console [ttyAML0] enabled
[    0.976075] Unable to detect cache hierarchy from DT for CPU 0
[    0.986553] brd: module loaded
[    0.989481] loop: module loaded
[    0.990600] nbd: registered device at major 43
[    0.995225] zram: Added device: zram0
[    0.995796] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.002287] libphy: Fixed MDIO Bus: probed
[    1.006267] tun: Universal TUN/TAP device driver, 1.6
[    1.011167] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.017617] KJH: kjh_reset_hack: base=0xffffff80089ce000,addr=0xffffff80089ce144 id=35, bank=1, bit=3, assert=0
[    1.027342] meson6-dwmac c9410000.ethernet: no reset control found
[    1.033423] stmmac - user ID: 0x11, Synopsys ID: 0x37
[    1.038420]  Ring mode enabled
[    1.041434]  DMA HW capability register supported
[    1.045922]  Normal descriptors
[    1.049195]  RX Checksum Offload Engine supported
[    1.053859]  COE Type 2
[    1.056267]  TX Checksum insertion supported
[    1.060500]  Wake-Up On Lan supported
[    1.064143]  Enable RX Mitigation via HW Watchdog Timer
[    1.075023] libphy: stmmac: probed
[    1.075059] eth0: PHY ID 001cc916 at 0 IRQ POLL (stmmac-0:00) active
[    1.079113] eth0: PHY ID 001cc916 at 7 IRQ POLL (stmmac-0:07)
[    1.084930] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.090942] ohci-platform: OHCI generic platform driver
[    1.096197] usbcore: registered new interface driver usbserial
[    1.101886] i2c /dev entries driver
[    1.105500] sdhci: Secure Digital Host Controller Interface driver
[    1.111453] sdhci: Copyright(c) Pierre Ossman
[    1.115776] Synopsys Designware Multimedia Card Interface Driver
[    1.121742] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.127543] ledtrig-cpu: registered to indicate activity on CPUs
[    1.133478] usbcore: registered new interface driver usbhid
[    1.138793] usbhid: USB HID core driver
[    1.142669] ashmem: initialized
[    1.146021] Initializing XFRM netlink socket
[    1.149930] NET: Registered protocol family 17
[    1.154335] NET: Registered protocol family 15
[    1.158769] Key type dns_resolver registered
[    1.163572] eth0: device MAC address 00:1e:06:33:25:dd
[    3.229733] meson6-dwmac c9410000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[    3.245672] Sending DHCP requests ., OK
[    3.265669] IP-Config: Got DHCP answer from 10.1.1.1, my address is 10.1.1.105
[    3.267359] IP-Config: Complete:
[    3.270439]      device=eth0, hwaddr=00:1e:06:33:25:dd, ipaddr=10.1.1.105, mask=255.255.255.0, gw=10.1.1.1
[    3.280030]      host=10.1.1.105, domain=, nis-domain=(none)
[    3.285617]      bootserver=0.0.0.0, rootserver=10.1.1.106, rootpath=     nameserver0=10.1.1.1
[    3.299922] Freeing unused kernel memory: 448K (ffffffc0017d0000 - ffffffc001840000)
Loading, please wait...
[    3.330232] systemd-udevd[149]: starting version 229
[    3.332120] random: systemd-udevd urandom read with 1 bits of entropy available
[    4.214280] systemd[1]: System time before build time, advancing clock.
[    4.306443] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
[    4.321797] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
[    4.326358] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
[    4.335364] systemd[1]: Mounting cgroup to /sys/fs/cgroup/perf_event of type cgroup with options perf_event.
[    4.345082] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
[    4.354202] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls,net_prio of type cgroup with options net_cls,net_prio.
[    4.364946] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
[    4.374135] systemd[1]: Mounting cgroup to /sys/fs/cgroup/hugetlb of type cgroup with options hugetlb.
[    4.383384] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
[    4.392272] systemd[1]: Mounting cgroup to /sys/fs/cgroup/debug of type cgroup with options debug.
[    4.401156] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFU)
[    4.419112] systemd[1]: Detected architecture arm64.

Welcome to Ubuntu 16.04 LTS!

[    4.444523] systemd[1]: Set hostname to <odroid64>.
[    4.455045] systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd.
[    4.459804] systemd[1]: Installed release agent.
[    4.480151] systemd[1]: Controller 'cpu' supported: no
[    4.480192] systemd[1]: Controller 'cpuacct' supported: yes
[    4.485202] systemd[1]: Controller 'blkio' supported: yes
[    4.490531] systemd[1]: Controller 'memory' supported: yes
[    4.495999] systemd[1]: Controller 'devices' supported: yes
[    4.501508] systemd[1]: Controller 'pids' supported: yes
[    4.506774] systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
[    4.518344] systemd[1]: Enabling showing of status.
[    4.524457] systemd[187]: Spawned /lib/systemd/system-generators/systemd-dbus1-generator as 188.
[    4.528011] systemd[187]: Spawned /lib/systemd/system-generators/systemd-hibernate-resume-generator as 189.
[    4.537656] systemd[187]: Spawned /lib/systemd/system-generators/systemd-fstab-generator as 190.
[    4.546437] systemd[187]: Spawned /lib/systemd/system-generators/systemd-rc-local-generator as 191.
[    4.555397] systemd[187]: Spawned /lib/systemd/system-generators/systemd-insserv-generator as 192.
[    4.564359] systemd[187]: Spawned /lib/systemd/system-generators/systemd-getty-generator as 193.
[    4.573001] systemd[187]: Spawned /lib/systemd/system-generators/systemd-gpt-auto-generator as 194.
[    4.579518] systemd-fstab-generator[190]: Parsing /etc/fstab
[    4.584594] systemd-fstab-generator[190]: Found entry what=10.1.1.106:/nfs_exports/rootfs/4.6.0 where=/ type=nfs4 nofail=no noauto=no
[    4.599502] systemd[187]: Spawned /lib/systemd/system-generators/systemd-debug-generator as 195.
[    4.601764] systemd-rc-local-generator[191]: Automatically adding rc-local.service.
[    4.615798] systemd[187]: Spawned /lib/systemd/system-generators/systemd-sysv-generator as 196.
[    4.624393] systemd[187]: Spawned /lib/systemd/system-generators/systemd-cryptsetup-generator as 197.
[    4.631540] systemd-gpt-auto-generator[194]: Neither root nor /usr file system are on a (single) block device.
[    4.643434] systemd[187]: Spawned /lib/systemd/system-generators/systemd-system-update-generator as 198.
[    4.652589] systemd[187]: /lib/systemd/system-generators/systemd-debug-generator succeeded.
[    4.660787] systemd[187]: /lib/systemd/system-generators/systemd-hibernate-resume-generator succeeded.
[    4.664403] systemd-sysv-generator[196]: Looking for unit files in (higher priority first):
[    4.664411] systemd-sysv-generator[196]:     /etc/systemd/system
[    4.664415] systemd-sysv-generator[196]:     /run/systemd/system
[    4.664418] systemd-sysv-generator[196]:     /usr/local/lib/systemd/system
[    4.664421] systemd-sysv-generator[196]:     /lib/systemd/system
[    4.664424] systemd-sysv-generator[196]:     /usr/lib/systemd/system
[    4.664454] systemd-sysv-generator[196]: Looking for SysV init scripts in:
[    4.664458] systemd-sysv-generator[196]:     /etc/init.d
[    4.664463] systemd-sysv-generator[196]: Looking for SysV rcN.d links in:
[    4.664466] systemd-sysv-generator[196]:     /etc
[    4.682878] systemd-sysv-generator[196]: Native unit for brltty.service already exists, skipping.
[    4.686688] systemd-sysv-generator[196]: Native unit for unattended-upgrades.service already exists, skipping.
[    4.689410] systemd-sysv-generator[196]: Native unit for checkfs.service already exists, skipping.
[    4.695691] systemd-sysv-generator[196]: Native unit for network-manager.service already exists, skipping.
[    4.698443] systemd-sysv-generator[196]: Native unit for single.service already exists, skipping.
[    4.701957] systemd-sysv-generator[196]: Native unit for rsyslog.service already exists, skipping.
[    4.707614] systemd-sysv-generator[196]: Native unit for pppd-dns.service already exists, skipping.
[    4.710495] systemd-sysv-generator[196]: Native unit for umountnfs.service already exists, skipping.
[    4.714005] systemd-sysv-generator[196]: Native unit for cups.service already exists, skipping.
[    4.714782] systemd-getty-generator[193]: Automatically adding serial getty for /dev/ttyAML0.
[    4.717571] systemd-sysv-generator[196]: Native unit for rc.service already exists, skipping.
[    4.721239] systemd-sysv-generator[196]: Native unit for dbus.service already exists, skipping.
[    4.724889] systemd-sysv-generator[196]: Native unit for rsync.service already exists, skipping.
[    4.728492] systemd-sysv-generator[196]: Native unit for console-setup.service already exists, skipping.
[    4.731932] systemd-sysv-generator[196]: Native unit for cgmanager.service already exists, skipping.
[    4.734532] systemd-sysv-generator[196]: Native unit for mountall-bootclean.service already exists, skipping.
[    4.737086] systemd-sysv-generator[196]: Native unit for hostname.service already exists, skipping.
[    4.742338] systemd-sysv-generator[196]: Native unit for anacron.service already exists, skipping.
[    4.745801] systemd-sysv-generator[196]: Native unit for whoopsie.service already exists, skipping.
[    4.751420] systemd-sysv-generator[196]: Native unit for rpcbind.service already exists, skipping.
[    4.754870] systemd-sysv-generator[196]: Native unit for uuidd.service already exists, skipping.
[    4.757643] systemd-sysv-generator[196]: Native unit for checkroot-bootclean.service already exists, skipping.
[    4.761195] systemd-sysv-generator[196]: Native unit for lightdm.service already exists, skipping.
[    4.764640] systemd-sysv-generator[196]: Native unit for cron.service already exists, skipping.
[    4.767428] systemd-sysv-generator[196]: Native unit for mountkernfs.service already exists, skipping.
[    4.775516] systemd-sysv-generator[196]: Native unit for procps.service already exists, skipping.
[    4.779023] systemd-sysv-generator[196]: Native unit for ssh.service already exists, skipping.
[    4.781602] systemd-sysv-generator[196]: Native unit for rcS.service already exists, skipping.
[    4.787800] systemd-sysv-generator[196]: Native unit for kmod.service already exists, skipping.
[    4.790605] systemd-sysv-generator[196]: Native unit for sendsigs.service already exists, skipping.
[    4.796745] systemd-sysv-generator[196]: Native unit for urandom.service already exists, skipping.
[    4.802186] systemd-sysv-generator[196]: Native unit for avahi-daemon.service already exists, skipping.
[    4.804830] systemd-sysv-generator[196]: Native unit for mountall.service already exists, skipping.
[    4.807423] systemd-sysv-generator[196]: Native unit for umountfs.service already exists, skipping.
[    4.813494] systemd-sysv-generator[196]: Native unit for plymouth.service already exists, skipping.
[    4.819636] systemd-sysv-generator[196]: Native unit for plymouth-log.service already exists, skipping.
[    4.824100] systemd-sysv-generator[196]: Native unit for halt.service already exists, skipping.
[    4.826626] systemd-sysv-generator[196]: Native unit for checkroot.service already exists, skipping.
[    4.833040] systemd-sysv-generator[196]: Native unit for rc.local.service already exists, skipping.
[    4.835573] systemd-sysv-generator[196]: Native unit for saned.service already exists, skipping.
[    4.837395] systemd-sysv-generator[196]: Native unit for mysql.service already exists, skipping.
[    4.839916] systemd-sysv-generator[196]: Native unit for x11-common.service already exists, skipping.
[    4.842580] systemd-sysv-generator[196]: Native unit for umountroot.service already exists, skipping.
[    4.845183] systemd-sysv-generator[196]: Native unit for alsa-utils.service already exists, skipping.
[    4.847705] systemd-sysv-generator[196]: Native unit for hwclock.service already exists, skipping.
[    4.854030] systemd-sysv-generator[196]: Native unit for smartmontools.service already exists, skipping.
[    4.857459] systemd-sysv-generator[196]: Native unit for lm-sensors.service already exists, skipping.
[    4.863745] systemd-sysv-generator[196]: Native unit for udev.service already exists, skipping.
[    4.867622] systemd-sysv-generator[196]: Native unit for bluetooth.service already exists, skipping.
[    4.871999] systemd-sysv-generator[196]: Native unit for bootmisc.service already exists, skipping.
[    4.874590] systemd-sysv-generator[196]: Native unit for mountnfs-bootclean.service already exists, skipping.
[    4.878155] systemd-sysv-generator[196]: Native unit for tlp.service already exists, skipping.
[    4.881749] systemd-sysv-generator[196]: Native unit for ufw.service already exists, skipping.
[    4.885274] systemd-sysv-generator[196]: Native unit for networking.service already exists, skipping.
[    4.890635] systemd-sysv-generator[196]: Native unit for cups-browsed.service already exists, skipping.
[    4.893300] systemd-sysv-generator[196]: Native unit for killprocs.service already exists, skipping.
[    4.896928] systemd-sysv-generator[196]: Native unit for kerneloops.service already exists, skipping.
[    4.901303] systemd-sysv-generator[196]: Native unit for mountdevsubfs.service already exists, skipping.
[    4.904798] systemd-sysv-generator[196]: Native unit for resolvconf.service already exists, skipping.
[    4.908371] systemd-sysv-generator[196]: Native unit for cgproxy.service already exists, skipping.
[    4.910913] systemd-sysv-generator[196]: Native unit for mountnfs.service already exists, skipping.
[    4.914972] systemd-sysv-generator[196]: Native unit for avahi-dnsconfd.service already exists, skipping.
[    4.917689] systemd-sysv-generator[196]: Native unit for reboot.service already exists, skipping.
[    4.922143] systemd-sysv-generator[196]: Ignoring S06checkroot.sh symlink in rcS.d, not generating checkroot.service.
[    4.922153] systemd-sysv-generator[196]: Ignoring S04brltty symlink in rcS.d, not generating brltty.service.
[    4.922169] systemd-sysv-generator[196]: Ignoring S02mountkernfs.sh symlink in rcS.d, not generating mountkernfs.service.
[    4.922178] systemd-sysv-generator[196]: Ignoring S02alsa-utils symlink in rcS.d, not generating alsa-utils.service.
[    4.922186] systemd-sysv-generator[196]: Ignoring S04procps symlink in rcS.d, not generating procps.service.
[    4.922195] systemd-sysv-generator[196]: Ignoring S09networking symlink in rcS.d, not generating networking.service.
[    4.922204] systemd-sysv-generator[196]: Ignoring S10rpcbind symlink in rcS.d, not generating rpcbind.service.
[    4.922212] systemd-sysv-generator[196]: Ignoring S02ufw symlink in rcS.d, not generating ufw.service.
[    4.922220] systemd-sysv-generator[196]: Ignoring S13bootmisc.sh symlink in rcS.d, not generating bootmisc.service.
[    4.922230] systemd-sysv-generator[196]: Ignoring S08checkroot-bootclean.sh symlink in rcS.d, not generating checkroot-bootclean.service.
[    4.922238] systemd-sysv-generator[196]: Ignoring S02lm-sensors symlink in rcS.d, not generating lm-sensors.service.
[    4.922246] systemd-sysv-generator[196]: Ignoring S03udev symlink in rcS.d, not generating udev.service.
[    4.922254] systemd-sysv-generator[196]: Ignoring S07checkfs.sh symlink in rcS.d, not generating checkfs.service.
[    4.922261] systemd-sysv-generator[196]: Ignoring S08kmod symlink in rcS.d, not generating kmod.service.
[    4.922269] systemd-sysv-generator[196]: Ignoring S02resolvconf symlink in rcS.d, not generating resolvconf.service.
[    4.922277] systemd-sysv-generator[196]: Ignoring S05hwclock.sh symlink in rcS.d, not generating hwclock.service.
[    4.922286] systemd-sysv-generator[196]: Ignoring S02plymouth-log symlink in rcS.d, not generating plymouth-log.service.
[    4.922294] systemd-sysv-generator[196]: Ignoring S02hostname.sh symlink in rcS.d, not generating hostname.service.
[    4.922302] systemd-sysv-generator[196]: Ignoring S11mountnfs.sh symlink in rcS.d, not generating mountnfs.service.
[    4.922311] systemd-sysv-generator[196]: Ignoring S01console-setup symlink in rcS.d, not generating console-setup.service.
[    4.922319] systemd-sysv-generator[196]: Ignoring S04mountdevsubfs.sh symlink in rcS.d, not generating mountdevsubfs.service.
[    4.922328] systemd-sysv-generator[196]: Ignoring S10mountall-bootclean.sh symlink in rcS.d, not generating mountall-bootclean.service.
[    4.922336] systemd-sysv-generator[196]: Ignoring S09mountall.sh symlink in rcS.d, not generating mountall.service.
[    4.922345] systemd-sysv-generator[196]: Ignoring S12mountnfs-bootclean.sh symlink in rcS.d, not generating mountnfs-bootclean.service.
[    4.922353] systemd-sysv-generator[196]: Ignoring S02x11-common symlink in rcS.d, not generating x11-common.service.
[    4.922361] systemd-sysv-generator[196]: Ignoring S08urandom symlink in rcS.d, not generating urandom.service.
[    4.925338] systemd-sysv-generator[196]: Ignoring K01alsa-utils symlink in rc1.d, not generating alsa-utils.service.
[    4.925349] systemd-sysv-generator[196]: Ignoring K01smartmontools symlink in rc1.d, not generating smartmontools.service.
[    4.925358] systemd-sysv-generator[196]: Ignoring K01whoopsie symlink in rc1.d, not generating whoopsie.service.
[    4.925366] systemd-sysv-generator[196]: Ignoring K01lightdm symlink in rc1.d, not generating lightdm.service.
[    4.925374] systemd-sysv-generator[196]: Ignoring S01killprocs symlink in rc1.d, not generating killprocs.service.
[    4.925382] systemd-sysv-generator[196]: Ignoring K03rsyslog symlink in rc1.d, not generating rsyslog.service.
[    4.925391] systemd-sysv-generator[196]: Ignoring K01avahi-dnsconfd symlink in rc1.d, not generating avahi-dnsconfd.service.
[    4.925399] systemd-sysv-generator[196]: Ignoring K01mysql symlink in rc1.d, not generating mysql.service.
[    4.925407] systemd-sysv-generator[196]: Ignoring K01ufw symlink in rc1.d, not generating ufw.service.
[    4.925418] systemd-sysv-generator[196]: Ignoring K05rpcbind symlink in rc1.d, not generating rpcbind.service.
[    4.925426] systemd-sysv-generator[196]: Ignoring K01bluetooth symlink in rc1.d, not generating bluetooth.service.
[    4.925434] systemd-sysv-generator[196]: Ignoring K01cups-browsed symlink in rc1.d, not generating cups-browsed.service.
[    4.925442] systemd-sysv-generator[196]: Ignoring K01kerneloops symlink in rc1.d, not generating kerneloops.service.
[    4.925450] systemd-sysv-generator[196]: Ignoring S02single symlink in rc1.d, not generating single.service.
[    4.925458] systemd-sysv-generator[196]: Ignoring K01uuidd symlink in rc1.d, not generating uuidd.service.
[    4.925465] systemd-sysv-generator[196]: Ignoring K01cups symlink in rc1.d, not generating cups.service.
[    4.929423] systemd-sysv-generator[196]: Ignoring S04cups-browsed symlink in rc2.d, not generating cups-browsed.service.
[    4.929432] systemd-sysv-generator[196]: Ignoring S02cron symlink in rc2.d, not generating cron.service.
[    4.929449] systemd-sysv-generator[196]: Ignoring S02rsync symlink in rc2.d, not generating rsync.service.
[    4.929461] systemd-sysv-generator[196]: Ignoring S02smartmontools symlink in rc2.d, not generating smartmontools.service.
[    4.929470] systemd-sysv-generator[196]: Ignoring S02avahi-dnsconfd symlink in rc2.d, not generating avahi-dnsconfd.service.
[    4.929478] systemd-sysv-generator[196]: Ignoring S03lightdm symlink in rc2.d, not generating lightdm.service.
[    4.929486] systemd-sysv-generator[196]: Ignoring S01rsyslog symlink in rc2.d, not generating rsyslog.service.
[    4.929499] systemd-sysv-generator[196]: Ignoring S02mysql symlink in rc2.d, not generating mysql.service.
[    4.929521] systemd-sysv-generator[196]: Ignoring S02ssh symlink in rc2.d, not generating ssh.service.
[    4.929531] systemd-sysv-generator[196]: Ignoring S05rc.local symlink in rc2.d, not generating rc.local.service.
[    4.929544] systemd-sysv-generator[196]: Ignoring S02whoopsie symlink in rc2.d, not generating whoopsie.service.
[    4.929551] systemd-sysv-generator[196]: Ignoring S05plymouth symlink in rc2.d, not generating plymouth.service.
[    4.929560] systemd-sysv-generator[196]: Ignoring S02kerneloops symlink in rc2.d, not generating kerneloops.service.
[    4.929567] systemd-sysv-generator[196]: Ignoring S03bluetooth symlink in rc2.d, not generating bluetooth.service.
[    4.929575] systemd-sysv-generator[196]: Ignoring S02dbus symlink in rc2.d, not generating dbus.service.
[    4.929583] systemd-sysv-generator[196]: Ignoring S01uuidd symlink in rc2.d, not generating uuidd.service.
[    4.929594] systemd-sysv-generator[196]: Ignoring S04cups symlink in rc2.d, not generating cups.service.
[    4.933813] systemd-sysv-generator[196]: Ignoring S04cups-browsed symlink in rc3.d, not generating cups-browsed.service.
[    4.933822] systemd-sysv-generator[196]: Ignoring S02cron symlink in rc3.d, not generating cron.service.
[    4.933835] systemd-sysv-generator[196]: Ignoring S02rsync symlink in rc3.d, not generating rsync.service.
[    4.933848] systemd-sysv-generator[196]: Ignoring S02smartmontools symlink in rc3.d, not generating smartmontools.service.
[    4.933857] systemd-sysv-generator[196]: Ignoring S02avahi-dnsconfd symlink in rc3.d, not generating avahi-dnsconfd.service.
[    4.933864] systemd-sysv-generator[196]: Ignoring S03lightdm symlink in rc3.d, not generating lightdm.service.
[    4.933872] systemd-sysv-generator[196]: Ignoring S01rsyslog symlink in rc3.d, not generating rsyslog.service.
[    4.933886] systemd-sysv-generator[196]: Ignoring S02mysql symlink in rc3.d, not generating mysql.service.
[    4.933905] systemd-sysv-generator[196]: Ignoring S02ssh symlink in rc3.d, not generating ssh.service.
[    4.933915] systemd-sysv-generator[196]: Ignoring S05rc.local symlink in rc3.d, not generating rc.local.service.
[    4.933926] systemd-sysv-generator[196]: Ignoring S02whoopsie symlink in rc3.d, not generating whoopsie.service.
[    4.933934] systemd-sysv-generator[196]: Ignoring S05plymouth symlink in rc3.d, not generating plymouth.service.
[    4.933942] systemd-sysv-generator[196]: Ignoring S02kerneloops symlink in rc3.d, not generating kerneloops.service.
[    4.933950] systemd-sysv-generator[196]: Ignoring S03bluetooth symlink in rc3.d, not generating bluetooth.service.
[    4.933958] systemd-sysv-generator[196]: Ignoring S02dbus symlink in rc3.d, not generating dbus.service.
[    4.933965] systemd-sysv-generator[196]: Ignoring S01uuidd symlink in rc3.d, not generating uuidd.service.
[    4.933977] systemd-sysv-generator[196]: Ignoring S04cups symlink in rc3.d, not generating cups.service.
[    4.937962] systemd-sysv-generator[196]: Ignoring S04cups-browsed symlink in rc4.d, not generating cups-browsed.service.
[    4.937971] systemd-sysv-generator[196]: Ignoring S02cron symlink in rc4.d, not generating cron.service.
[    4.937984] systemd-sysv-generator[196]: Ignoring S02rsync symlink in rc4.d, not generating rsync.service.
[    4.937997] systemd-sysv-generator[196]: Ignoring S02smartmontools symlink in rc4.d, not generating smartmontools.service.
[    4.938005] systemd-sysv-generator[196]: Ignoring S02avahi-dnsconfd symlink in rc4.d, not generating avahi-dnsconfd.service.
[    4.938013] systemd-sysv-generator[196]: Ignoring S03lightdm symlink in rc4.d, not generating lightdm.service.
[    4.938021] systemd-sysv-generator[196]: Ignoring S01rsyslog symlink in rc4.d, not generating rsyslog.service.
[    4.938035] systemd-sysv-generator[196]: Ignoring S02mysql symlink in rc4.d, not generating mysql.service.
[    4.938053] systemd-sysv-generator[196]: Ignoring S02ssh symlink in rc4.d, not generating ssh.service.
[    4.938062] systemd-sysv-generator[196]: Ignoring S05rc.local symlink in rc4.d, not generating rc.local.service.
[    4.938074] systemd-sysv-generator[196]: Ignoring S02whoopsie symlink in rc4.d, not generating whoopsie.service.
[    4.938083] systemd-sysv-generator[196]: Ignoring S05plymouth symlink in rc4.d, not generating plymouth.service.
[    4.938091] systemd-sysv-generator[196]: Ignoring S02kerneloops symlink in rc4.d, not generating kerneloops.service.
[    4.938099] systemd-sysv-generator[196]: Ignoring S03bluetooth symlink in rc4.d, not generating bluetooth.service.
[    4.938107] systemd-sysv-generator[196]: Ignoring S02dbus symlink in rc4.d, not generating dbus.service.
[    4.938115] systemd-sysv-generator[196]: Ignoring S01uuidd symlink in rc4.d, not generating uuidd.service.
[    4.938126] systemd-sysv-generator[196]: Ignoring S04cups symlink in rc4.d, not generating cups.service.
[    4.942121] systemd-sysv-generator[196]: Ignoring S04cups-browsed symlink in rc5.d, not generating cups-browsed.service.
[    4.942130] systemd-sysv-generator[196]: Ignoring S02cron symlink in rc5.d, not generating cron.service.
[    4.942144] systemd-sysv-generator[196]: Ignoring S02rsync symlink in rc5.d, not generating rsync.service.
[    4.942156] systemd-sysv-generator[196]: Ignoring S02smartmontools symlink in rc5.d, not generating smartmontools.service.
[    4.942165] systemd-sysv-generator[196]: Ignoring S02avahi-dnsconfd symlink in rc5.d, not generating avahi-dnsconfd.service.
[    4.942173] systemd-sysv-generator[196]: Ignoring S03lightdm symlink in rc5.d, not generating lightdm.service.
[    4.942181] systemd-sysv-generator[196]: Ignoring S01rsyslog symlink in rc5.d, not generating rsyslog.service.
[    4.942194] systemd-sysv-generator[196]: Ignoring S02mysql symlink in rc5.d, not generating mysql.service.
[    4.942213] systemd-sysv-generator[196]: Ignoring S02ssh symlink in rc5.d, not generating ssh.service.
[    4.942222] systemd-sysv-generator[196]: Ignoring S05rc.local symlink in rc5.d, not generating rc.local.service.
[    4.942234] systemd-sysv-generator[196]: Ignoring S02whoopsie symlink in rc5.d, not generating whoopsie.service.
[    4.942242] systemd-sysv-generator[196]: Ignoring S05plymouth symlink in rc5.d, not generating plymouth.service.
[    4.942250] systemd-sysv-generator[196]: Ignoring S02kerneloops symlink in rc5.d, not generating kerneloops.service.
[    4.942257] systemd-sysv-generator[196]: Ignoring S03bluetooth symlink in rc5.d, not generating bluetooth.service.
[    4.942265] systemd-sysv-generator[196]: Ignoring S02dbus symlink in rc5.d, not generating dbus.service.
[    4.942272] systemd-sysv-generator[196]: Ignoring S01uuidd symlink in rc5.d, not generating uuidd.service.
[    4.942283] systemd-sysv-generator[196]: Ignoring S04cups symlink in rc5.d, not generating cups.service.
[    4.946272] systemd-sysv-generator[196]: Ignoring K02sendsigs symlink in rc0.d, not generating sendsigs.service.
[    4.946282] systemd-sysv-generator[196]: Ignoring K01alsa-utils symlink in rc0.d, not generating alsa-utils.service.
[    4.946290] systemd-sysv-generator[196]: Ignoring K07umountfs symlink in rc0.d, not generating umountfs.service.
[    4.946299] systemd-sysv-generator[196]: Ignoring K08umountroot symlink in rc0.d, not generating umountroot.service.
[    4.946307] systemd-sysv-generator[196]: Ignoring K01lightdm symlink in rc0.d, not generating lightdm.service.
[    4.946315] systemd-sysv-generator[196]: Ignoring K03rsyslog symlink in rc0.d, not generating rsyslog.service.
[    4.946324] systemd-sysv-generator[196]: Ignoring K01avahi-dnsconfd symlink in rc0.d, not generating avahi-dnsconfd.service.
[    4.946332] systemd-sysv-generator[196]: Ignoring K01mysql symlink in rc0.d, not generating mysql.service.
[    4.946340] systemd-sysv-generator[196]: Ignoring K05rpcbind symlink in rc0.d, not generating rpcbind.service.
[    4.946347] systemd-sysv-generator[196]: Ignoring K01bluetooth symlink in rc0.d, not generating bluetooth.service.
[    4.946356] systemd-sysv-generator[196]: Ignoring K06networking symlink in rc0.d, not generating networking.service.
[    4.946364] systemd-sysv-generator[196]: Ignoring K01plymouth symlink in rc0.d, not generating plymouth.service.
[    4.946372] systemd-sysv-generator[196]: Ignoring K04hwclock.sh symlink in rc0.d, not generating hwclock.service.
[    4.946380] systemd-sysv-generator[196]: Ignoring K01cups-browsed symlink in rc0.d, not generating cups-browsed.service.
[    4.946388] systemd-sysv-generator[196]: Ignoring K09halt symlink in rc0.d, not generating halt.service.
[    4.946397] systemd-sysv-generator[196]: Ignoring K01unattended-upgrades symlink in rc0.d, not generating unattended-upgrades.service.
[    4.946406] systemd-sysv-generator[196]: Ignoring K01kerneloops symlink in rc0.d, not generating kerneloops.service.
[    4.946414] systemd-sysv-generator[196]: Ignoring K01resolvconf symlink in rc0.d, not generating resolvconf.service.
[    4.946422] systemd-sysv-generator[196]: Ignoring K04umountnfs.sh symlink in rc0.d, not generating umountnfs.service.
[    4.946430] systemd-sysv-generator[196]: Ignoring K01uuidd symlink in rc0.d, not generating uuidd.service.
[    4.946444] systemd-sysv-generator[196]: Ignoring K01urandom symlink in rc0.d, not generating urandom.service.
[    4.950429] systemd-sysv-generator[196]: Ignoring K02sendsigs symlink in rc6.d, not generating sendsigs.service.
[    4.950439] systemd-sysv-generator[196]: Ignoring K01alsa-utils symlink in rc6.d, not generating alsa-utils.service.
[    4.950447] systemd-sysv-generator[196]: Ignoring K07umountfs symlink in rc6.d, not generating umountfs.service.
[    4.950456] systemd-sysv-generator[196]: Ignoring K08umountroot symlink in rc6.d, not generating umountroot.service.
[    4.950464] systemd-sysv-generator[196]: Ignoring K01lightdm symlink in rc6.d, not generating lightdm.service.
[    4.950472] systemd-sysv-generator[196]: Ignoring K03rsyslog symlink in rc6.d, not generating rsyslog.service.
[    4.950481] systemd-sysv-generator[196]: Ignoring K01avahi-dnsconfd symlink in rc6.d, not generating avahi-dnsconfd.service.
[    4.950488] systemd-sysv-generator[196]: Ignoring K01mysql symlink in rc6.d, not generating mysql.service.
[    4.950496] systemd-sysv-generator[196]: Ignoring K05rpcbind symlink in rc6.d, not generating rpcbind.service.
[    4.950504] systemd-sysv-generator[196]: Ignoring K01bluetooth symlink in rc6.d, not generating bluetooth.service.
[    4.950512] systemd-sysv-generator[196]: Ignoring K06networking symlink in rc6.d, not generating networking.service.
[    4.950520] systemd-sysv-generator[196]: Ignoring K01plymouth symlink in rc6.d, not generating plymouth.service.
[    4.950528] systemd-sysv-generator[196]: Ignoring K04hwclock.sh symlink in rc6.d, not generating hwclock.service.
[    4.950536] systemd-sysv-generator[196]: Ignoring K01cups-browsed symlink in rc6.d, not generating cups-browsed.service.
[    4.950546] systemd-sysv-generator[196]: Ignoring K01unattended-upgrades symlink in rc6.d, not generating unattended-upgrades.service.
[    4.950554] systemd-sysv-generator[196]: Ignoring K01kerneloops symlink in rc6.d, not generating kerneloops.service.
[    4.950562] systemd-sysv-generator[196]: Ignoring K01resolvconf symlink in rc6.d, not generating resolvconf.service.
[    4.950570] systemd-sysv-generator[196]: Ignoring K04umountnfs.sh symlink in rc6.d, not generating umountnfs.service.
[    4.950578] systemd-sysv-generator[196]: Ignoring K01uuidd symlink in rc6.d, not generating uuidd.service.
[    4.950586] systemd-sysv-generator[196]: Ignoring K09reboot symlink in rc6.d, not generating reboot.service.
[    4.950598] systemd-sysv-generator[196]: Ignoring K01urandom symlink in rc6.d, not generating urandom.service.
[    4.952435] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/ntp
[    4.955234] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/apparmor
[    4.958590] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/apport
[    4.961413] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/ondemand
[    4.964055] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/cpufrequtils
[    4.966746] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/hddtemp
[    4.969395] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/loadcpufreq
[    4.972802] systemd-sysv-generator[196]: Loading SysV script /etc/init.d/speech-dispatcher
[    6.902156] systemd[187]: /lib/systemd/system-generators/systemd-dbus1-generator succeeded.
[    6.910384] systemd[187]: /lib/systemd/system-generators/systemd-insserv-generator succeeded.
[    6.918831] systemd[187]: /lib/systemd/system-generators/systemd-sysv-generator succeeded.
[    6.927028] systemd[187]: /lib/systemd/system-generators/systemd-rc-local-generator succeeded.
[    6.935573] systemd[187]: /lib/systemd/system-generators/systemd-fstab-generator succeeded.
[    6.943844] systemd[187]: /lib/systemd/system-generators/systemd-cryptsetup-generator succeeded.
[    6.952562] systemd[187]: /lib/systemd/system-generators/systemd-getty-generator succeeded.
[    6.960836] systemd[187]: /lib/systemd/system-generators/systemd-system-update-generator succeeded.
[    6.969813] systemd[187]: /lib/systemd/system-generators/systemd-gpt-auto-generator succeeded.
[    6.978719] systemd[1]: system-generators succeeded.
[    6.983487] systemd[1]: Looking for unit files in (higher priority first):
[    6.990049] systemd[1]:      /etc/systemd/system
[    6.994274] systemd[1]:      /run/systemd/system
[    6.998501] systemd[1]:      /run/systemd/generator
[    7.002985] systemd[1]:      /usr/local/lib/systemd/system
[    7.008073] systemd[1]:      /lib/systemd/system
[    7.012298] systemd[1]:      /usr/lib/systemd/system
[    7.016869] systemd[1]:      /run/systemd/generator.late
[    7.021807] systemd[1]: Looking for SysV init scripts in:
[    7.027134] systemd[1]:      /etc/init.d
[    7.030670] systemd[1]: Looking for SysV rcN.d links in:
[    7.035930] systemd[1]:      /etc
[    7.066820] systemd[1]: Unit type .busname is not supported on this system.
[    7.092541] systemd[1]: run-systemd-journal-socket.mount: Failed to load configuration: No such file or directory
[    7.097186] systemd[1]: run.mount: Failed to load configuration: No such file or directory
[    7.105360] systemd[1]: run-systemd.mount: Failed to load configuration: No such file or directory
[    7.114245] systemd[1]: run-systemd-journal.mount: Failed to load configuration: No such file or directory
[    7.123817] systemd[1]: run-systemd-journal-stdout.mount: Failed to load configuration: No such file or directory
[    7.155034] systemd[1]: sys.mount: Failed to load configuration: No such file or directory
[    7.157692] systemd[1]: sys-kernel.mount: Failed to load configuration: No such file or directory
[    7.169418] systemd[1]: run-systemd-ask\x2dpassword.mount: Failed to load configuration: No such file or directory
[    7.179719] systemd[1]: systemd-vconsole-setup.service: Failed to load configuration: No such file or directory
[    7.190860] systemd[1]: systemd-sysusers.service: Failed to load configuration: No such file or directory
[    7.202078] systemd[1]: run-udev.mount: Failed to load configuration: No such file or directory
[    7.205146] systemd[1]: run-udev-control.mount: Failed to load configuration: No such file or directory
[    7.217392] systemd[1]: dev.mount: Failed to load configuration: No such file or directory
[    7.226053] systemd[1]: var.mount: Failed to load configuration: No such file or directory
[    7.230856] systemd[1]: var-log.mount: Failed to load configuration: No such file or directory
[    7.239395] systemd[1]: var-log-journal.mount: Failed to load configuration: No such file or directory
[    7.257927] systemd[1]: var-tmp.mount: Failed to load configuration: No such file or directory
[    7.266820] systemd[1]: tmp.mount: Failed to load configuration: No such file or directory
[    7.288842] systemd[1]: var-lib.mount: Failed to load configuration: No such file or directory
[    7.291843] systemd[1]: var-lib-systemd.mount: Failed to load configuration: No such file or directory
[    7.301061] systemd[1]: var-lib-systemd-timers.mount: Failed to load configuration: No such file or directory
[    7.328300] systemd[1]: run-systemd-fsck.progress.mount: Failed to load configuration: No such file or directory
[    7.338891] systemd[1]: proc.mount: Failed to load configuration: No such file or directory
[    7.341608] systemd[1]: proc-sys.mount: Failed to load configuration: No such file or directory
[    7.350246] systemd[1]: proc-sys-fs.mount: Failed to load configuration: No such file or directory
[    7.364907] systemd[1]: sys-fs.mount: Failed to load configuration: No such file or directory
[    7.367821] systemd[1]: sys-fs-fuse.mount: Failed to load configuration: No such file or directory
[    7.396092] systemd[1]: keyboard-setup.service: Failed to load configuration: No such file or directory
[    7.411624] systemd[1]: var-log-wtmp.mount: Failed to load configuration: No such file or directory
[    7.415048] systemd[1]: auditd.service: Failed to load configuration: No such file or directory
[    7.429661] systemd[1]: systemd-update-done.service: Failed to load configuration: No such file or directory
[    7.437998] systemd[1]: var-lib-systemd-random\x2dseed.mount: Failed to load configuration: No such file or directory
[    7.445517] systemd[1]: var-lib-brltty.mount: Failed to load configuration: No such file or directory
[    7.462135] systemd[1]: var-lib-systemd-clock.mount: Failed to load configuration: No such file or directory
[    7.473079] systemd[1]: run-systemd-netif.mount: Failed to load configuration: No such file or directory
[    7.476936] systemd[1]: run-systemd-netif-state.mount: Failed to load configuration: No such file or directory
[    7.503787] systemd[1]: var-run.mount: Failed to load configuration: No such file or directory
[    7.506794] systemd[1]: var-run-dbus.mount: Failed to load configuration: No such file or directory
[    7.515747] systemd[1]: var-run-dbus-system_bus_socket.mount: Failed to load configuration: No such file or directory
[    7.547691] systemd[1]: root.mount: Failed to load configuration: No such file or directory
[    7.556547] systemd[1]: run-systemd-journal-syslog.mount: Failed to load configuration: No such file or directory
[    7.569258] systemd[1]: run-systemd-journal-dev\x2dlog.mount: Failed to load configuration: No such file or directory
[    7.586041] systemd[1]: run-systemd-initctl.mount: Failed to load configuration: No such file or directory
[    7.590077] systemd[1]: run-systemd-initctl-fifo.mount: Failed to load configuration: No such file or directory
[    7.605953] systemd[1]: var-run-cups.mount: Failed to load configuration: No such file or directory
[    7.609361] systemd[1]: var-run-cups-cups.sock.mount: Failed to load configuration: No such file or directory
[    7.623257] systemd[1]: var-run-avahi\x2ddaemon.mount: Failed to load configuration: No such file or directory
[    7.629135] systemd[1]: var-run-avahi\x2ddaemon-socket.mount: Failed to load configuration: No such file or directory
[    7.643947] systemd[1]: run-apport.socket.mount: Failed to load configuration: No such file or directory
[    7.651938] systemd[1]: run-rpcbind.sock.mount: Failed to load configuration: No such file or directory
[    7.665296] systemd[1]: run-uuidd.mount: Failed to load configuration: No such file or directory
[    7.668475] systemd[1]: run-uuidd-request.mount: Failed to load configuration: No such file or directory
[    7.690756] systemd[1]: nfs-blkmap.service: Failed to load configuration: No such file or directory
[    7.772629] systemd[1]: festival.service: Failed to load configuration: No such file or directory
[    7.811263] systemd[1]: passwd.service: Failed to load configuration: No such file or directory
[    7.827830] systemd[1]: var-cache.mount: Failed to load configuration: No such file or directory
[    7.831015] systemd[1]: var-cache-cups.mount: Failed to load configuration: No such file or directory
[    7.840143] systemd[1]: var-cache-cups-org.cups.cupsd.mount: Failed to load configuration: No such file or directory
[    7.864337] systemd[1]: syslog.target: Failed to load configuration: No such file or directory
[    7.902216] systemd[1]: Using notification socket /run/systemd/notify
[    7.903177] systemd[1]: Successfully created private D-Bus server.
[    7.909257] systemd[1]: init.scope changed dead -> running
[    7.914619] systemd[1]: -.mount: Changed dead -> mounted
[    7.919906] systemd[1]: -.slice changed dead -> active
[    7.924990] systemd[1]: Activating default unit: default.target
[    7.941407] systemd[1]: var-lib-ureadahead.mount: Failed to load configuration: No such file or directory
[    7.950905] systemd[1]: graphical.target: Trying to enqueue job graphical.target/start/isolate
[    7.954291] systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount not found.
[    7.962763] systemd[1]: passwd.service: Cannot add dependency job, ignoring: Unit passwd.service not found.
[    7.972465] systemd[1]: mysql.service: Cannot add dependency job, ignoring: Unit mysql.service is masked.
[    7.981896] systemd[1]: nfs-blkmap.service: Cannot add dependency job, ignoring: Unit nfs-blkmap.service not found.
[    7.992821] systemd[1]: plymouth-quit.service: Looking at job plymouth-quit.service/stop conflicted_by=yes
[    8.001754] systemd[1]: plymouth-quit.service: Looking at job plymouth-quit.service/start conflicted_by=no
[    8.011329] systemd[1]: plymouth-quit.service: Fixing conflicting jobs plymouth-quit.service/stop,plymouth-quit.service/start by deleting job plymouth-quit.service/start
[    8.026349] systemd[1]: lightdm.service: Looking at job lightdm.service/start conflicted_by=no
[    8.034879] systemd[1]: lightdm.service: Looking at job lightdm.service/stop conflicted_by=no
[    8.043323] systemd[1]: lightdm.service: Fixing conflicting jobs lightdm.service/start,lightdm.service/stop by deleting job lightdm.service/stop
[    8.056467] systemd[1]: systemd-update-utmp-runlevel.service: Installed new job systemd-update-utmp-runlevel.service/start as 91
[    8.067660] systemd[1]: avahi-daemon.socket: Installed new job avahi-daemon.socket/start as 65
[    8.076187] systemd[1]: systemd-binfmt.service: Installed new job systemd-binfmt.service/start as 44
[    8.085246] systemd[1]: systemd-ask-password-console.path: Installed new job systemd-ask-password-console.path/start as 32
[    8.096199] systemd[1]: nfs-client.target: Installed new job nfs-client.target/start as 111
[    8.104478] systemd[1]: ureadahead.service: Installed new job ureadahead.service/start as 133
[    8.112928] systemd[1]: systemd-hwdb-update.service: Installed new job systemd-hwdb-update.service/start as 38
[    8.122848] systemd[1]: getty.target: Installed new job getty.target/start as 101
[    8.130263] systemd[1]: getty-static.service: Installed new job getty-static.service/start as 104
[    8.139070] systemd[1]: sysinit.target: Installed new job sysinit.target/start as 7
[    8.146652] systemd[1]: NetworkManager-wait-online.service: Installed new job NetworkManager-wait-online.service/start as 83
[    8.157781] systemd[1]: user.slice: Installed new job user.slice/start as 72
[    8.164759] systemd[1]: system-getty.slice: Installed new job system-getty.slice/start as 103
[    8.173216] systemd[1]: ntp.service: Installed new job ntp.service/start as 79
[    8.180375] systemd[1]: systemd-udevd.service: Installed new job systemd-udevd.service/start as 28
[    8.189259] systemd[1]: rpc-gssd.service: Installed new job rpc-gssd.service/start as 112
[    8.197366] systemd[1]: remote-fs-pre.target: Installed new job remote-fs-pre.target/start as 116
[    8.206168] systemd[1]: anacron.service: Installed new job anacron.service/start as 85
[    8.214012] systemd[1]: alsa-state.service: Installed new job alsa-state.service/start as 69
[    8.222381] systemd[1]: sockets.target: Installed new job sockets.target/start as 61
[    8.230055] systemd[1]: systemd-journald.socket: Installed new job systemd-journald.socket/start as 18
[    8.239283] systemd[1]: ufw.service: Installed new job ufw.service/start as 73
[    8.246441] systemd[1]: time-sync.target: Installed new job time-sync.target/start as 27
[    8.254463] systemd[1]: local-fs.target: Installed new job local-fs.target/start as 33
[    8.262313] systemd[1]: systemd-tmpfiles-setup-dev.service: Installed new job systemd-tmpfiles-setup-dev.service/start as 40
[    8.273441] systemd[1]: ssh.service: Installed new job ssh.service/start as 78
[    8.280597] systemd[1]: rsyslog.service: Installed new job rsyslog.service/start as 109
[    8.288532] systemd[1]: network.target: Installed new job network.target/start as 82
[    8.296208] systemd[1]: kmod-static-nodes.service: Installed new job kmod-static-nodes.service/start as 25
[    8.305784] systemd[1]: systemd-journald.service: Installed new job systemd-journald.service/start as 17
[    8.315185] systemd[1]: ModemManager.service: Installed new job ModemManager.service/start as 89
[    8.323896] systemd[1]: system-serial\x2dgetty.slice: Installed new job system-serial\x2dgetty.slice/start as 106
[    8.334074] systemd[1]: systemd-udev-trigger.service: Installed new job systemd-udev-trigger.service/start as 41
[    8.344165] systemd[1]: cpufrequtils.service: Installed new job cpufrequtils.service/start as 74
[    8.352875] systemd[1]: systemd-journald-dev-log.socket: Installed new job systemd-journald-dev-log.socket/start as 19
[    8.363485] systemd[1]: systemd-tmpfiles-clean.timer: Installed new job systemd-tmpfiles-clean.timer/start as 59
[    8.373576] systemd[1]: apt-daily.timer: Installed new job apt-daily.timer/start as 60
[    8.381422] systemd[1]: cups.socket: Installed new job cups.socket/start as 64
[    8.388581] systemd[1]: cgmanager.service: Installed new job cgmanager.service/start as 117
[    8.396862] systemd[1]: uuidd.socket: Installed new job uuidd.socket/start as 66
[    8.404192] systemd[1]: syslog.socket: Installed new job syslog.socket/start as 110
[    8.411783] systemd[1]: systemd-ask-password-wall.path: Installed new job systemd-ask-password-wall.path/start as 86
[    8.422221] systemd[1]: run-rpc_pipefs.mount: Installed new job run-rpc_pipefs.mount/start as 113
[    8.431018] systemd[1]: whoopsie.service: Installed new job whoopsie.service/start as 98
[    8.439039] systemd[1]: systemd-remount-fs.service: Installed new job systemd-remount-fs.service/start as 34
[    8.448786] systemd[1]: avahi-daemon.service: Installed new job avahi-daemon.service/start as 76
[    8.457496] systemd[1]: systemd-initctl.socket: Installed new job systemd-initctl.socket/start as 63
[    8.466557] systemd[1]: systemd-tmpfiles-setup.service: Installed new job systemd-tmpfiles-setup.service/start as 46
[    8.476990] systemd[1]: plymouth-start.service: Installed new job plymouth-start.service/start as 49
[    8.486045] systemd[1]: apparmor.service: Installed new job apparmor.service/start as 15
[    8.494066] systemd[1]: systemd-udevd-control.socket: Installed new job systemd-udevd-control.socket/start as 29
[    8.504159] systemd[1]: cups.service: Installed new job cups.service/start as 100
[    8.511575] systemd[1]: remote-fs.target: Installed new job remote-fs.target/start as 127
[    8.519682] systemd[1]: timers.target: Installed new job timers.target/start as 58
[    8.527185] systemd[1]: dbus.service: Installed new job dbus.service/start as 70
[    8.534516] systemd[1]: cryptsetup.target: Installed new job cryptsetup.target/start as 22
[    8.542711] systemd[1]: speech-dispatcher.service: Installed new job speech-dispatcher.service/start as 126
[    8.552372] systemd[1]: lightdm.service: Installed new job lightdm.service/start as 135
[    8.560305] systemd[1]: smartd.service: Installed new job smartd.service/start as 123
[    8.568068] systemd[1]: proc-sys-fs-binfmt_misc.automount: Installed new job proc-sys-fs-binfmt_misc.automount/start as 47
[    8.579024] systemd[1]: apport.service: Installed new job apport.service/start as 87
[    8.586708] systemd[1]: lm-sensors.service: Installed new job lm-sensors.service/start as 97
[    8.595065] systemd[1]: graphical.target: Installed new job graphical.target/start as 1
[    8.602999] systemd[1]: systemd-ask-password-plymouth.path: Installed new job systemd-ask-password-plymouth.path/start as 50
[    8.614128] systemd[1]: systemd-timesyncd.service: Installed new job systemd-timesyncd.service/start as 26
[    8.623701] systemd[1]: basic.target: Installed new job basic.target/start as 3
[    8.630943] systemd[1]: getty@tty1.service: Installed new job getty@tty1.service/start as 102
[    8.639397] systemd[1]: systemd-machine-id-commit.service: Installed new job systemd-machine-id-commit.service/start as 21
[    8.650353] systemd[1]: sys-kernel-debug.mount: Installed new job sys-kernel-debug.mount/start as 48
[    8.659410] systemd[1]: plymouth-quit-wait.service: Installed new job plymouth-quit-wait.service/start as 88
[    8.669155] systemd[1]: serial-getty@ttyAML0.service: Installed new job serial-getty@ttyAML0.service/start as 105
[    8.679332] systemd[1]: systemd-udevd-kernel.socket: Installed new job systemd-udevd-kernel.socket/start as 30
[    8.689251] systemd[1]: hddtemp.service: Installed new job hddtemp.service/start as 108
[    8.697184] systemd[1]: systemd-sysctl.service: Installed new job systemd-sysctl.service/start as 42
[    8.706241] systemd[1]: systemd-networkd-resolvconf-update.path: Installed new job systemd-networkd-resolvconf-update.path/start as 52
[    8.718232] systemd[1]: cups-browsed.service: Installed new job cups-browsed.service/start as 99
[    8.726943] systemd[1]: paths.target: Installed new job paths.target/start as 55
[    8.734272] systemd[1]: dev-mqueue.mount: Installed new job dev-mqueue.mount/start as 43
[    8.742293] systemd[1]: ureadahead-stop.timer: Installed new job ureadahead-stop.timer/start as 134
[    8.751263] systemd[1]: pppd-dns.service: Installed new job pppd-dns.service/start as 124
[    8.759370] systemd[1]: apport-forward.socket: Installed new job apport-forward.socket/start as 67
[    8.768256] systemd[1]: ondemand.service: Installed new job ondemand.service/start as 119
[    8.776362] systemd[1]: swap.target: Installed new job swap.target/start as 31
[    8.783519] systemd[1]: cups.path: Installed new job cups.path/start as 128
[    8.790416] systemd[1]: systemd-random-seed.service: Installed new job systemd-random-seed.service/start as 8
[    8.800254] systemd[1]: dev-ttyAML0.device: Installed new job dev-ttyAML0.device/start as 107
[    8.808755] systemd[1]: system.slice: Installed new job system.slice/start as 5
[    8.815952] systemd[1]: systemd-modules-load.service: Installed new job systemd-modules-load.service/start as 16
[    8.826043] systemd[1]: slices.target: Installed new job slices.target/start as 57
[    8.833545] systemd[1]: console-setup.service: Installed new job console-setup.service/start as 118
[    8.842516] systemd[1]: rc-local.service: Installed new job rc-local.service/start as 77
[    8.850536] systemd[1]: brltty.service: Installed new job brltty.service/start as 23
[    8.858213] systemd[1]: systemd-logind.service: Installed new job systemd-logind.service/start as 71
[    8.867270] systemd[1]: alsa-restore.service: Installed new job alsa-restore.service/start as 56
[    8.875981] systemd[1]: resolvconf.service: Installed new job resolvconf.service/start as 51
[    8.884347] systemd[1]: nss-user-lookup.target: Installed new job nss-user-lookup.target/start as 132
[    8.893492] systemd[1]: systemd-journald-audit.socket: Installed new job systemd-journald-audit.socket/start as 20
[    8.903755] systemd[1]: network-online.target: Installed new job network-online.target/start as 80
[    8.912637] systemd[1]: sys-kernel-config.mount: Installed new job sys-kernel-config.mount/start as 37
[    8.921866] systemd[1]: loadcpufreq.service: Installed new job loadcpufreq.service/start as 125
[    8.930491] systemd[1]: avahi-dnsconfd.service: Installed new job avahi-dnsconfd.service/start as 75
[    8.939548] systemd[1]: tlp.service: Installed new job tlp.service/start as 121
[    8.946791] systemd[1]: dbus.socket: Installed new job dbus.socket/start as 68
[    8.953950] systemd[1]: systemd-journal-flush.service: Installed new job systemd-journal-flush.service/start as 24
[    8.964219] systemd[1]: multi-user.target: Installed new job multi-user.target/start as 2
[    8.972322] systemd[1]: accounts-daemon.service: Installed new job accounts-daemon.service/start as 131
[    8.981637] systemd[1]: local-fs-pre.target: Installed new job local-fs-pre.target/start as 35
[    8.990179] systemd[1]: systemd-update-utmp.service: Installed new job systemd-update-utmp.service/start as 92
[    9.000096] systemd[1]: dev-hugepages.mount: Installed new job dev-hugepages.mount/start as 14
[    9.008633] systemd[1]: nfs-config.service: Installed new job nfs-config.service/start as 115
[    9.017085] systemd[1]: rpcbind.socket: Installed new job rpcbind.socket/start as 62
[    9.024761] systemd[1]: networking.service: Installed new job networking.service/start as 81
[    9.033127] systemd[1]: cron.service: Installed new job cron.service/start as 93
[    9.040459] systemd[1]: sys-fs-fuse-connections.mount: Installed new job sys-fs-fuse-connections.mount/start as 39
[    9.050724] systemd[1]: NetworkManager.service: Installed new job NetworkManager.service/start as 120
[    9.059866] systemd[1]: plymouth-read-write.service: Installed new job plymouth-read-write.service/start as 45
[    9.069785] systemd[1]: bluetooth.service: Installed new job bluetooth.service/start as 122
[    9.078064] systemd[1]: cgproxy.service: Installed new job cgproxy.service/start as 96
[    9.085913] systemd[1]: systemd-user-sessions.service: Installed new job systemd-user-sessions.service/start as 90
[    9.096195] systemd[1]: graphical.target: Enqueued job graphical.target/start as 1
[    9.103689] systemd[1]: Loaded units and determined initial transaction in 4.5s.
[    9.111130] systemd[1]: var-lib-ureadahead.mount: Collecting.
[    9.116700] systemd[1]: var-cache.mount: Collecting.
[    9.121613] systemd[1]: var-cache-cups.mount: Collecting.
[    9.126961] systemd[1]: var-cache-cups-org.cups.cupsd.mount: Collecting.
[    9.133637] systemd[1]: run-uuidd.mount: Collecting.
[    9.138518] systemd[1]: run-uuidd-request.mount: Collecting.
[    9.144127] systemd[1]: run-rpcbind.sock.mount: Collecting.
[    9.149644] systemd[1]: run-apport.socket.mount: Collecting.
[    9.155250] systemd[1]: var-run-avahi\x2ddaemon.mount: Collecting.
[    9.161374] systemd[1]: var-run-avahi\x2ddaemon-socket.mount: Collecting.
[    9.168102] systemd[1]: var-run-cups.mount: Collecting.
[    9.173276] systemd[1]: var-run-cups-cups.sock.mount: Collecting.
[    9.179315] systemd[1]: run-systemd-initctl.mount: Collecting.
[    9.185093] systemd[1]: run-systemd-initctl-fifo.mount: Collecting.
[    9.191307] systemd[1]: run-systemd-journal-dev\x2dlog.mount: Collecting.
[    9.198031] systemd[1]: run-systemd-journal-syslog.mount: Collecting.
[    9.204413] systemd[1]: root.mount: Collecting.
[    9.208898] systemd[1]: var-run.mount: Collecting.
[    9.213640] systemd[1]: var-run-dbus.mount: Collecting.
[    9.218816] systemd[1]: var-run-dbus-system_bus_socket.mount: Collecting.
[    9.225547] systemd[1]: run-systemd-netif.mount: Collecting.
[    9.231150] systemd[1]: run-systemd-netif-state.mount: Collecting.
[    9.237276] systemd[1]: var-lib-systemd-clock.mount: Collecting.
[    9.243226] systemd[1]: var-lib-brltty.mount: Collecting.
[    9.248575] systemd[1]: var-lib-systemd-random\x2dseed.mount: Collecting.
[    9.255303] systemd[1]: var-log-wtmp.mount: Collecting.
[    9.260481] systemd[1]: sys-fs.mount: Collecting.
[    9.265132] systemd[1]: sys-fs-fuse.mount: Collecting.
[    9.270221] systemd[1]: proc.mount: Collecting.
[    9.274705] systemd[1]: proc-sys.mount: Collecting.
[    9.279535] systemd[1]: proc-sys-fs.mount: Collecting.
[    9.284627] systemd[1]: run-systemd-fsck.progress.mount: Collecting.
[    9.290927] systemd[1]: var-lib.mount: Collecting.
[    9.295664] systemd[1]: var-lib-systemd.mount: Collecting.
[    9.301099] systemd[1]: var-lib-systemd-timers.mount: Collecting.
[    9.307141] systemd[1]: var-tmp.mount: Collecting.
[    9.311882] systemd[1]: var.mount: Collecting.
[    9.316278] systemd[1]: var-log.mount: Collecting.
[    9.321022] systemd[1]: var-log-journal.mount: Collecting.
[    9.326457] systemd[1]: dev.mount: Collecting.
[    9.330854] systemd[1]: run-udev.mount: Collecting.
[    9.335685] systemd[1]: run-udev-control.mount: Collecting.
[    9.341211] systemd[1]: run-systemd-ask\x2dpassword.mount: Collecting.
[    9.347675] systemd[1]: sys.mount: Collecting.
[    9.352071] systemd[1]: sys-kernel.mount: Collecting.
[    9.357087] systemd[1]: run-systemd-journal-socket.mount: Collecting.
[    9.363459] systemd[1]: run.mount: Collecting.
[    9.367855] systemd[1]: run-systemd.mount: Collecting.
[    9.372945] systemd[1]: run-systemd-journal.mount: Collecting.
[    9.378723] systemd[1]: run-systemd-journal-stdout.mount: Collecting.
[    9.385512] systemd[1]: Received SIGCHLD from PID 187 (n/a).
[    9.390972] systemd[1]: systemd-journald-audit.socket: ConditionCapability=CAP_AUDIT_READ succeeded.
[    9.399812] systemd[1]: systemd-journald-audit.socket: ConditionSecurity=audit succeeded.
[    9.407937] systemd[1]: systemd-journald-audit.socket: Changed dead -> listening
[    9.415222] systemd[1]: systemd-journald-audit.socket: Job systemd-journald-audit.socket/start finished, result=done
[    9.425685] systemd[1]: Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Audit Socket.
[    9.441744] systemd[1]: nss-user-lookup.target changed dead -> active
[    9.442547] systemd[1]: nss-user-lookup.target: Job nss-user-lookup.target/start finished, result=done
[    9.451800] systemd[1]: Reached target User and Group Name Lookups.
[  OK  ] Reached target User and Group Name Lookups.
[    9.470025] systemd[1]: system.slice changed dead -> active
[    9.470063] systemd[1]: system.slice: Job system.slice/start finished, result=done
[    9.477494] systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
[    9.493761] systemd[1]: swap.target changed dead -> active
[    9.493797] systemd[1]: swap.target: Job swap.target/start finished, result=done
[    9.500969] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    9.517731] systemd[1]: systemd-udevd-kernel.socket: ConditionPathIsReadWrite=/sys succeeded.
[    9.520653] systemd[1]: systemd-udevd-kernel.socket: Changed dead -> listening
[    9.527778] systemd[1]: systemd-udevd-kernel.socket: Job systemd-udevd-kernel.socket/start finished, result=done
[    9.537873] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    9.553738] systemd[1]: proc-sys-fs-binfmt_misc.automount: ConditionPathIsReadWrite=/proc/sys/ succeeded.
[    9.557690] systemd[1]: proc-sys-fs-binfmt_misc.automount: ConditionPathExists=/proc/sys/fs/binfmt_misc/ succeeded.
[    9.568198] systemd[1]: Autofs kernel version 1.0
[    9.572793] systemd[1]: Autofs protocol version 5.2
[    9.577504] systemd[1]: proc-sys-fs-binfmt_misc.automount: Changed dead -> waiting
[    9.585004] systemd[1]: proc-sys-fs-binfmt_misc.automount: Job proc-sys-fs-binfmt_misc.automount/start finished, result=done
[    9.596139] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
[    9.621742] systemd[1]: cryptsetup.target changed dead -> active
[    9.622110] systemd[1]: cryptsetup.target: Job cryptsetup.target/start finished, result=done
[    9.630502] systemd[1]: Reached target Encrypted Volumes.
[  OK  ] Reached target Encrypted Volumes.
[    9.653729] systemd[1]: systemd-udevd-control.socket: ConditionPathIsReadWrite=/sys succeeded.
[    9.656780] systemd[1]: systemd-udevd-control.socket: Changed dead -> listening
[    9.663951] systemd[1]: systemd-udevd-control.socket: Job systemd-udevd-control.socket/start finished, result=done
[    9.674218] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    9.698765] systemd[1]: systemd-initctl.socket: Changed dead -> listening
[    9.699917] systemd[1]: systemd-initctl.socket: Job systemd-initctl.socket/start finished, result=done
[    9.709176] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[    9.729862] systemd[1]: systemd-ask-password-wall.path: Changed dead -> waiting
[    9.731533] systemd[1]: systemd-ask-password-wall.path: Job systemd-ask-password-wall.path/start finished, result=done
[    9.742164] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[    9.766776] systemd[1]: syslog.socket: Changed dead -> listening
[    9.767149] systemd[1]: syslog.socket: Job syslog.socket/start finished, result=done
[    9.774846] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[    9.789793] systemd[1]: systemd-journald-dev-log.socket: Changed dead -> listening
[    9.791726] systemd[1]: systemd-journald-dev-log.socket: Job systemd-journald-dev-log.socket/start finished, result=done
[    9.802538] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    9.822055] systemd[1]: system-serial\x2dgetty.slice changed dead -> active
[    9.823376] systemd[1]: system-serial\x2dgetty.slice: Job system-serial\x2dgetty.slice/start finished, result=done
[    9.833675] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    9.857842] systemd[1]: systemd-journald.socket: Changed dead -> listening
[    9.859074] systemd[1]: systemd-journald.socket: Job systemd-journald.socket/start finished, result=done
[    9.868500] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    9.886349] systemd[1]: resolvconf.service: About to execute: /bin/mkdir -p /run/resolvconf/interface
[    9.890284] systemd[1]: resolvconf.service: Forked /bin/mkdir as 199
[    9.905872] systemd[1]: resolvconf.service: Changed dead -> start-pre
[    9.906715] systemd[1]: Starting Nameserver information manager...
         Starting Nameserver information manager...
[    9.925956] systemd[1]: dev-hugepages.mount: ConditionCapability=CAP_SYS_ADMIN succeeded.
[    9.928538] systemd[1]: dev-hugepages.mount: ConditionPathExists=/sys/kernel/mm/hugepages succeeded.
[    9.937640] systemd[1]: dev-hugepages.mount: Failed to check symlink /dev/hugepages, ignoring: No such file or directory
[    9.949115] systemd[1]: dev-hugepages.mount: About to execute: /bin/mount hugetlbfs /dev/hugepages -t hugetlbfs
[    9.958754] systemd[1]: dev-hugepages.mount: Forked /bin/mount as 200
[    9.964919] systemd[1]: dev-hugepages.mount: Changed dead -> mounting
[    9.971156] systemd[1]: Mounting Huge Pages File System...
         Mounting Huge Pages File System...
[    9.990527] systemd[1]: ufw.service: About to execute: /lib/ufw/ufw-init start quiet
[    9.993030] systemd[1]: ufw.service: Forked /lib/ufw/ufw-init as 201
[    9.999308] systemd[1]: ufw.service: Changed dead -> start
[   10.004424] systemd[1]: Starting Uncomplicated firewall...
         Starting Uncomplicated firewall...
[   10.021859] systemd[1]: run-rpc_pipefs.mount: Failed to check symlink /run/rpc_pipefs, ignoring: No such file or directory
[   10.028066] systemd[1]: run-rpc_pipefs.mount: About to execute: /bin/mount sunrpc /run/rpc_pipefs -t rpc_pipefs
[   10.037734] systemd[1]: run-rpc_pipefs.mount: Forked /bin/mount as 202
[   10.043924] systemd[1]: run-rpc_pipefs.mount: Changed dead -> mounting
[   10.050248] systemd[1]: Mounting RPC Pipe File System...
         Mounting RPC Pipe File System...
[   10.065815] systemd[1]: systemd-remount-fs.service: ConditionPathExists=/etc/fstab succeeded.
[   10.069434] systemd[1]: systemd-remount-fs.service: About to execute: /lib/systemd/systemd-remount-fs
[   10.078341] systemd[1]: systemd-remount-fs.service: Forked /lib/systemd/systemd-remount-fs as 203
[   10.087035] systemd[1]: systemd-remount-fs.service: Changed dead -> start
[   10.093430] systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems...
[   10.196840] systemd[1]: kmod-static-nodes.service: ConditionFileNotEmpty=/lib/modules/4.6.0+/modules.devname succeeded.
[   10.202170] systemd[1]: kmod-static-nodes.service: ConditionCapability=CAP_SYS_MODULE succeeded.
[   10.211424] systemd[1]: kmod-static-nodes.service: About to execute: /bin/kmod static-nodes --format=tmpfiles --output=/run/tmpfiles.d/kmod.conf
[   10.223973] systemd[1]: kmod-static-nodes.service: Forked /bin/kmod as 205
[   10.238064] systemd[1]: kmod-static-nodes.service: Changed dead -> start
[   10.239186] systemd[1]: Starting Create list of required static device nodes for the current kernel...
         Starting Create list of required st... nodes for the current kernel...
[   10.261991] systemd[1]: sys-kernel-debug.mount: ConditionCapability=CAP_SYS_RAWIO succeeded.
[   10.264832] systemd[1]: sys-kernel-debug.mount: ConditionPathExists=/sys/kernel/debug succeeded.
[   10.274353] systemd[1]: sys-kernel-debug.mount: About to execute: /bin/mount debugfs /sys/kernel/debug -t debugfs
[   10.284151] systemd[1]: sys-kernel-debug.mount: Forked /bin/mount as 211
[   10.290581] systemd[1]: sys-kernel-debug.mount: Changed dead -> mounting
[   10.297074] systemd[1]: Mounting Debug File System...
         Mounting Debug File System...
[   10.314529] systemd[1]: systemd-journald.service: About to execute: /lib/systemd/systemd-journald
[   10.318180] systemd[1]: systemd-journald.service: Forked /lib/systemd/systemd-journald as 215
[   10.326666] systemd[1]: systemd-journald.service: Changed dead -> start
[   10.332853] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[   10.350494] systemd[1]: brltty.service: About to execute: /bin/sh -c 'grep -sq '^ *RUN_BRLTTY=no' /etc/default/brltty || exec /sbin/brltty -P /run/brltty.pid'
[   10.359440] systemd[1]: brltty.service: Forked /bin/sh as 217
[   10.365063] systemd[1]: brltty.service: Changed dead -> running
[   10.370594] systemd[1]: brltty.service: Job brltty.service/start finished, result=done
[   10.378458] systemd[1]: Started Braille Device Support.
[  OK  ] Started Braille Device Support.
[   10.402359] systemd[1]: systemd-modules-load.service: ConditionKernelCommandLine=|rd.modules-load failed.
[   10.406365] systemd[1]: systemd-modules-load.service: ConditionKernelCommandLine=|modules-load failed.
[   10.415589] systemd[1]: systemd-modules-load.service: ConditionDirectoryNotEmpty=|/run/modules-load.d failed.
[   10.533469] systemd[1]: systemd-modules-load.service: ConditionDirectoryNotEmpty=|/etc/modules-load.d succeeded.
[   10.539592] systemd[1]: systemd-modules-load.service: ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d failed.
[   10.559712] systemd[1]: systemd-modules-load.service: ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d failed.
[   10.566979] systemd[1]: systemd-modules-load.service: ConditionDirectoryNotEmpty=|/lib/modules-load.d failed.
[   10.574368] systemd[1]: systemd-modules-load.service: ConditionCapability=CAP_SYS_MODULE succeeded.
[   10.583914] systemd[1]: systemd-modules-load.service: About to execute: /lib/systemd/systemd-modules-load
[   10.593040] systemd[1]: systemd-modules-load.service: Forked /lib/systemd/systemd-modules-load as 220
[   10.610085] systemd[1]: systemd-modules-load.service: Changed dead -> start
[   10.611457] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
[   10.622506] systemd-journald[215]: Fixed min_use=1.0M max_use=19.2M max_size=2.4M min_size=512.0K keep_free=28.8M n_max_files=100
[   10.633128] systemd-journald[215]: Reserving 4380 entries in hash table.
[   10.639310] systemd-journald[215]: Vacuuming...
[   10.643055] systemd-journald[215]: Vacuuming done, freed 0B of archived journals on disk.
[   10.659580] systemd-journald[215]: Flushing /dev/kmsg...
[   10.670001] systemd[1]: dev-mqueue.mount: ConditionCapability=CAP_SYS_ADMIN succeeded.
[   10.672343] systemd[1]: dev-mqueue.mount: ConditionPathExists=/proc/sys/fs/mqueue succeeded.
[   10.680760] systemd[1]: dev-mqueue.mount: Failed to check symlink /dev/mqueue, ignoring: No such file or directory
[   10.688630] systemd-journald[215]: systemd-journald running as pid 215
[   10.689170] systemd-journald[215]: Sent READY=1 notification.
[   10.689183] systemd-journald[215]: Sent WATCHDOG=1 notification.
[   10.709785] systemd[1]: dev-mqueue.mount: About to execute: /bin/mount mqueue /dev/mqueue -t mqueue
[   10.718447] systemd[1]: dev-mqueue.mount: Forked /bin/mount as 224
[   10.733825] systemd[1]: dev-mqueue.mount: Changed dead -> mounting
[   10.734537] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[   10.749280] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.754883] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.763500] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.772147] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.780774] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.789499] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.798020] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.806547] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.815341] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.823831] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.838144] systemd[1]: system-getty.slice changed dead -> active
[   10.838615] systemd[1]: system-getty.slice: Job system-getty.slice/start finished, result=done
[   10.847217] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[   10.865966] systemd[1]: user.slice changed dead -> active
[   10.866007] systemd[1]: user.slice: Job user.slice/start finished, result=done
[   10.872926] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[   10.889727] systemd[1]: slices.target changed dead -> active
[   10.889764] systemd[1]: slices.target: Job slices.target/start finished, result=done
[   10.897458] systemd[1]: Reached target Slices.
[  OK  ] Reached target Slices.
[   10.913728] systemd[1]: ureadahead.service: ConditionVirtualization=no succeeded.
[   10.916170] systemd[1]: ureadahead.service: About to execute: /sbin/ureadahead
[   10.923122] systemd[1]: ureadahead.service: Forked /sbin/ureadahead as 227
[   10.924448] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[   10.946013] systemd[1]: ureadahead.service: Changed dead -> running
[   10.946656] systemd[1]: ureadahead.service: Job ureadahead.service/start finished, result=done
[   10.955268] systemd[1]: Started Read required files in advance.
[  OK  ] Started Read required files in advance.
[   10.973964] systemd[1]: systemd-binfmt.service: ConditionDirectoryNotEmpty=|/run/binfmt.d failed.
[   10.999025] systemd[1]: systemd-binfmt.service: ConditionDirectoryNotEmpty=|/etc/binfmt.d failed.
[   11.003565] systemd[1]: systemd-binfmt.service: ConditionDirectoryNotEmpty=|/usr/local/lib/binfmt.d failed.
[   11.014592] systemd[1]: systemd-binfmt.service: ConditionDirectoryNotEmpty=|/usr/lib/binfmt.d failed.
[   11.022030] systemd[1]: systemd-binfmt.service: ConditionDirectoryNotEmpty=|/lib/binfmt.d failed.
[   11.029928] systemd[1]: systemd-binfmt.service: ConditionPathIsReadWrite=/proc/sys/ succeeded.
[   11.038445] systemd[1]: systemd-binfmt.service: Starting requested but condition failed. Not starting unit.
[   11.048074] systemd[1]: systemd-binfmt.service: Job systemd-binfmt.service/start finished, result=done
[   11.070764] systemd[1]: libmount event [rescan: yes]
[   11.071876] systemd[1]: sys-kernel-debug.mount: Changed mounting -> mounting-done
[   11.077578] systemd[1]: sys-kernel-debug.mount: Job sys-kernel-debug.mount/start finished, result=done
[   11.086789] systemd[1]: Mounted Debug File System.
[  OK  ] Mounted Debug File System.
[   11.101818] systemd[1]: dev-hugepages.mount: Changed mounting -> mounting-done
[   11.103399] systemd[1]: dev-hugepages.mount: Job dev-hugepages.mount/start finished, result=done
[   11.112146] systemd[1]: Mounted Huge Pages File System.
[  OK  ] Mounted Huge Pages File System.
[   11.129750] systemd[1]: dev-mqueue.mount: Changed mounting -> mounting-done
[   11.131072] systemd[1]: dev-mqueue.mount: Job dev-mqueue.mount/start finished, result=done
[   11.139296] systemd[1]: Mounted POSIX Message Queue File System.
[  OK  ] Mounted POSIX Message Queue File System.
[   11.157747] systemd[1]: run-rpc_pipefs.mount: Changed mounting -> mounting-done
[   11.159417] systemd[1]: run-rpc_pipefs.mount: Job run-rpc_pipefs.mount/start finished, result=done
[   11.168327] systemd[1]: Mounted RPC Pipe File System.
[  OK  ] Mounted RPC Pipe File System.
[   11.185951] systemd[1]: systemd-journald.service: Got notification message from PID 215 (READY=1, STATUS=Processing requests...)
[   11.191883] systemd[1]: systemd-journald.service: Changed start -> running
[   11.198672] systemd[1]: systemd-journald.service: Job systemd-journald.service/start finished, result=done
[   11.208260] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[   11.225728] systemd[1]: systemd-journald-dev-log.socket: Changed listening -> running
[   11.227932] systemd[1]: systemd-journald.socket: Changed listening -> running
[  OK  ] Started Uncomplicated firewall.
[   11.251426] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[  OK  ] Started Nameserver information manager.
[   11.323512] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Mounting Configuration File System...
[   11.431451] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Mounting FUSE Control File System...
[   11.449359] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Starting Apply Kernel Variables...
[   11.465289] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Starting Create Static Device Nodes in /dev...
[   11.481115] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Starting udev Coldplug all Devices...
[   11.567405] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Starting Load/Save Random Seed...
[   11.585111] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
         Starting Flush Journal to Persistent Storage...
[   11.601603] systemd-journald[215]: Successfully sent stream file descriptor to service manager.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting LSB: AppArmor initialization...
         Starting Set console keymap...
         Starting Preprocess NFS configuration...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting udev Kernel Device Manager...
[FAILED] Failed to start Set console keymap.
See 'systemctl status console-setup.service' for details.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Preprocess NFS configuration.
[  OK  ] Reached target NFS client services.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Started LSB: AppArmor initialization.
         Starting Raise network interfaces...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Reached target System Initialization.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Started Daily apt activities.
[  OK  ] Listening on CUPS Scheduler.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on UUID daemon activation socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
         Starting Permit User Sessions...
         Starting LSB: Speech Dispatcher...
[  OK  ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
         Starting Initialize hardware monitoring sensors...
         Starting System Logging Service...
         Starting Modem Manager...
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started Cgroup management daemon.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started crash report submission daemon.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Started Avahi DNS Configuration Daemon.
         Starting LSB: automatic crash report generation...
         Starting Network Manager...
         Starting Login Service...
         Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
         Starting Restore /etc/resolv.conf i...re the ppp link was shut down...
[  OK  ] Started Run anacron jobs.
         Starting Accounts Service...
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started System Logging Service.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started LSB: Speech Dispatcher.
[  OK  ] Started Restore /etc/resolv.conf if...fore the ppp link was shut down.
[  OK  ] Started Initialize hardware monitoring sensors.
[  OK  ] Found device /dev/ttyAML0.
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started Raise network interfaces.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Network Manager.
[  OK  ] Started Login Service.
         Starting Network Manager Script Dispatcher Service...
         Starting Network Manager Wait Online...
[  OK  ] Started Make remote CUPS printers available locally.
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
[  OK  ] Reached target Network.
         Starting OpenBSD Secure Shell server...
         Starting LSB: set CPUFreq kernel parameters...
         Starting Light Display Manager...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting Hostname Service...
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started Accounts Service.
[  OK  ] Started Hostname Service.
[  OK  ] Started Light Display Manager.
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Modem Manager.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting /etc/rc.local Compatibility...
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: Start NTP daemon...
[  OK  ] Started /etc/rc.local Compatibility.
         Starting Hold until boot process finishes up...
[  OK  ] Started Hold until boot process finishes up.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyAML0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Reached target Multi-User System.
[  OK  ] Started TLP system startup/shutdown.
[  OK  ] Started Light Display Manager.
[  OK  ] Reached target Graphical Interface.
[  OK  ] Started Stop ureadahead data collection 45s after completed startup.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 16.04 LTS odroid64 ttyAML0

odroid64 login: 
The patches provided by others will hopefully make it into the 4.7 kernel release.

Going to now spend some time cleaning up my environment and documenting. Ive used a patched version u-boot rc3 & kernel and the new new GCC 6.1 to compile directly on the odroid c2.

I want to see if I can get back to original u-boot or get mmc working on new u-boot for an automated start. Would also like to see which version of GCC works best so I can cross compile on the host.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels

Unread post by brad » Sun May 29, 2016 3:12 pm

Start of the log from the previous post....

Code: Select all

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 116820
no sdio debug board detected 

BL2 Built : 11:44:26, Nov 25 2015. 
gxb gfb13a3b-c2 - jcao@wonton

Board ID = 8
set vcck to 1100 mv
set vddee to 1050 mv
CPU clk: 1536MHz
DDR channel setting: DDR0 Rank0+1 same
DDR0: 2048MB(auto) @ 912MHz(2T)-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK. 
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000017c0
Wait bl30...Done
Sending bl301......OK. 
Run bl301...
31 from SD, src: 0x00020200, des: 0x10100000, size: 0x00011130


--- UART initialized after reboot ---
[Reset cause: unknown]
[Image: unknown, amlogic_v1.1.3046-00db630 2015-10-28 15:24:31 xiaobo.gu@droid05]
bl30: check_permit, count is 1
bl30: check_permit: ok!
chipid: ef be ad de Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x00043600
d f0 ad ba ef be ad de not ES chip
[0.231363 Inits done]
secure task start!
high task start!
low task start!
NOTICE:  BL3-1: v1.0(debug):4d2e34d
NOTICE:  BL3-1: Built : 17:08:35, Oct 29 2015
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2016.05-rc3-g4cf4600-dirty (May 15 2016 - 12:10:12 +1000) odroid-c2

DRAM:  2 GiB
Using default environment

In:    serial@4c0
Out:   serial@4c0
Err:   serial@4c0
Net:   eth0: eth_designware
=> #NFS Boot DHCP
=> setenv kernel_addr 11000000
=> setenv fdt_addr 1000000
=> setenv initrd_loadaddr 13000000
=> setenv tftpbootfile Image
=> setenv tftpfdtfile meson-gxbb-odroidc2.dtb
=> setenv tftpinitrdfile uInitrd-4.6.0+
=> setenv ipaddr 10.1.1.105
=> setenv serverip 10.1.1.106
=> setenv nfsargs "setenv bootargs debug root=/dev/nfs rw ip=dhcp nfsroot=${serverip}:/nfs_export/rootfs/4.6.0+ consolelog=9"
=> setenv start_odroidc2 'tftp ${initrd_loadaddr} ${tftpinitrdfile} ;tftp ${kernel_addr} ${tftpbootfile};tftp ${fdt_addr} ${tftpfdtfile};run nfsargs ;booti ${kernel_addr} ${initrd_loadaddr}'
=> run start_odroidc2
Speed: 100, full duplex
Using eth_designware device
TFTP from server 10.1.1.106; our IP address is 10.1.1.105
Filename 'uInitrd-4.6.0+'.
Load address: 0x13000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         2.3 MiB/s
done
Bytes transferred = 6672639 (65d0ff hex)
Speed: 100, full duplex
Using eth_designware device
TFTP from server 10.1.1.106; our IP address is 10.1.1.105
Filename 'Image'.
Load address: 0x11000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###########################################################
         2.3 MiB/s
done
Bytes transferred = 8492832 (819720 hex)
Speed: 100, full duplex
Using eth_designware device
TFTP from server 10.1.1.106; our IP address is 10.1.1.105
Filename 'meson-gxbb-odroidc2.dtb'.
Load address: 0x1000000
Loading: #
         862.3 KiB/s
done
Bytes transferred = 5301 (14b5 hex)
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
   Data Size:    6672575 Bytes = 6.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
   Loading Ramdisk to 7d940000, end 7df9d0bf ... OK
   Loading Device Tree to 000000007d93b000, end 000000007d93f4b4 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.6.0+ (odroid@odroid64) (gcc version 6.1.0 (GCC) ) #2 SMP PREEMPT Sun May 29 15:40:06 AEST 2016
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    0.000000] cma: Reserved 8 MiB at 0x000000007f800000
[    0.000000] On node 0 totalpages: 520192
[    0.000000]   DMA zone: 8128 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 520192 pages, LIFO batch:31
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv0.2 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sat Jun 04, 2016 8:51 am

Initial support is starting to be implemented into U-boot mainline for Odorid C2 which is good news....

http://git.denx.de/?p=u-boot.git&a=sear ... =odroid-c2

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 19, 2016 1:14 pm

There is work being done for mmc on both uboot mainline & linux kernel 4.7 which will hopefully get into the official development trees in the not so distant future. (Hopefully into 4.8 stable as well)

This should allow u-boot to be upgraded to an offical development version with support to boot for sdcard/mmc and allow new development linux kernel to be installed & then configured via a defconfig to run on the c2 without modification in the Hardkernel Ubuntu image.

Of course it will still only be minimal support for a headless server and will likely be missing usb, hdmi, audio amongst others.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 19, 2016 1:37 pm

I should also make mention of the great work of the developers over here, they have my full respect and support. Please note as they mention
Not for end users - yet!
http://linux-meson.com/doku.php

stmicro
Posts: 251
Joined: Tue Apr 28, 2015 4:23 pm
languages_spoken: english, chinese
ODROIDs: Many Odroids and Rpis.
Location: shenzhen china
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by stmicro » Sun Jun 19, 2016 1:44 pm

Nice progress! Once the SD/eMMC and USB drivers work stably, it should be okay to build some server/headless applications. please keep updating this thread.
kernel 4.7RC seems to be working well on XU4 too with HDMI output . very good news for many odroid users and developers.

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Sun Jun 19, 2016 1:46 pm

brad wrote:There is work being done for mmc on both uboot mainline & linux kernel 4.7 which will hopefully get into the official development trees in the not so distant future. (Hopefully into 4.8 stable as well)
Link to the MMC work for Meson-GXBB in kernel? I've tested the patches on U-Boot and they seem to work, but the only MMC work I've seen for kernel is for Meson8, and seen mentions that they are substantially different.

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels

Unread post by BlueMatt » Sun Jun 19, 2016 1:50 pm

brad wrote:I've finally got a patched version of 4.6.0 booting with NFS..

The patches provided by others will hopefully make it into the 4.7 kernel release.

Going to now spend some time cleaning up my environment and documenting. Ive used a patched version u-boot rc3 & kernel and the new new GCC 6.1 to compile directly on the odroid c2.

I want to see if I can get back to original u-boot or get mmc working on new u-boot for an automated start. Would also like to see which version of GCC works best so I can cross compile on the host.
Any update on posting your configs? I spent some time trying various patches and have only ever managed to get as far as loading the kernel with a "Bad mode" error in the stmmac interrupt handler right when it sends its first packet to the network to DHCP.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Mon Jun 20, 2016 5:24 pm

BlueMatt wrote:Link to the MMC work for Meson-GXBB in kernel?
https://git.kernel.org/cgit/linux/kerne ... fe7a65f9d6

I will post my latest configs after I build a new version.

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Mon Jun 20, 2016 5:45 pm

brad wrote:
BlueMatt wrote:Link to the MMC work for Meson-GXBB in kernel?
https://git.kernel.org/cgit/linux/kerne ... fe7a65f9d6
Am I missing something? I believe that just adds references to the pins themselves in the device tree, it does not actually contain any code to interface with the MMC itself?

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Tue Jun 21, 2016 4:30 pm

BlueMatt wrote:Am I missing something? I believe that just adds references to the pins themselves in the device tree, it does not actually contain any code to interface with the MMC itself?
No but like I mentioned soon, watch this space! :)

In the meantime I will post my configs after my next build to open up discussion.

I hope to be able to get a head start with the help from others on the optimal kernel build for the c2.

We can start planning on a number of things not limited to..

- the ideal environment for build
- How to easily switch between kernel's and configurations
- ideal optimum kernel builds (lightweight or fully featured)
- Thoughts on testing of various kernel features to identify whats possible
- Utilising advanced hardware features of both the meson architecture and odroid board (Hardware Crypto and DIN on the I2S are on my list)

umiddelb
Posts: 451
Joined: Thu Jan 29, 2015 6:42 am
languages_spoken: English, German
ODROIDs: ODROID-C1, ODROID-XU4, ODROID-C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by umiddelb » Tue Jun 21, 2016 7:17 pm

brad wrote:...
- How to easily switch between kernel's and configurations
may be u-571

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Sat Jun 25, 2016 3:07 am

brad wrote: No but like I mentioned soon, watch this space! :)
You win https://git.kernel.org/cgit/linux/kerne ... v4.7/integ :D :D :D

Gonna go test later today.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sat Jun 25, 2016 7:50 am

BlueMatt wrote:Gonna go test later today.
Very nice :D Will try a build now

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Sat Jun 25, 2016 9:50 am

brad wrote: Very nice :D Will try a build now
Works great here, fwiw, was able to debootstrap and get into a working system over serial no problem.

For those following along at home: latest u-boot rc will get you into a serial console. Theoretically the eth driver is hooked up but was disabled due to the major driver subsystem rewrite effort in u-boot, so that'll have to wait. MMC is also not merged in u-boot: there is a patch that seems to work, but it does not seem to function properly when applied to master (bad mode when Linux unmasks exceptions meaning there is some unhandled exception in u-boot). Still, serial console image upload works, so it is possible to boot with a serial adapter just fine.

The v4.7/integ branch of the linux-amlogic tree also seems to work great, as well, just do a default defconfig, and most basic things work, you might also check that CONFIG_STMMAC_ETH and CONFIG_REALTEK_PHY are built-in and not modules for eth to function (note that I'm still getting a bad mode error when enabling these drivers, so there is something amuck here, possibly)

What this means: When Linux v4.8 mainline rolls around we should have a pretty reliable mainline kernel, at least for basic server tasks. u-boot probably wont be until the next release after 2016.07

stmicro
Posts: 251
Joined: Tue Apr 28, 2015 4:23 pm
languages_spoken: english, chinese
ODROIDs: Many Odroids and Rpis.
Location: shenzhen china
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by stmicro » Sat Jun 25, 2016 9:57 am

Good news. We have a standalone 64bit ARM board runs the upstream kernel at least. :o
Once the USB and ETH drivers work stably on kernel 4.8, we will have a nice affordable low energy server machine soon.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sat Jun 25, 2016 10:13 am

Nice! now in linux-next

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Sat Jun 25, 2016 10:22 am

stmicro wrote:Good news. We have a standalone 64bit ARM board runs the upstream kernel at least. :o
Once the USB and ETH drivers work stably on kernel 4.8, we will have a nice affordable low energy server machine soon.
No word on USB yet, as far as I've seen.

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels

Unread post by BlueMatt » Sat Jun 25, 2016 1:07 pm

BlueMatt wrote:
brad wrote:I've finally got a patched version of 4.6.0 booting with NFS..
Any update on posting your configs? I spent some time trying various patches and have only ever managed to get as far as loading the kernel with a "Bad mode" error in the stmmac interrupt handler right when it sends its first packet to the network to DHCP.
You don't happen to be running 100M ethernet instead of 1G?

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sat Jun 25, 2016 2:23 pm

BlueMatt wrote:You don't happen to be running 100M ethernet instead of 1G?
I had troubles with 1G & NFS, reverted back to 100M switch to solve the problems.

Was hoping new timer setup would solve these problems but haven't got that far yet

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Sun Jun 26, 2016 3:40 am

brad wrote: I had troubles with 1G & NFS, reverted back to 100M switch to solve the problems.
Heh, you could have told me that before I spent time digging into it...anyway, xdarklight on IRC found some issues and posted a patch to linux-amlogic, which with one other patch that I have works, so 1G ethernet should be working in -next soon enough :).

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 26, 2016 11:12 am

I was wrong about mmc in the linux-next, its starting to be implemented there.

Interestingly though next does have some Mali display support coming in which might be good news for c2...
CONFIG_DRM_MALI_DISPLAY: │
│ │
│ Choose this option if you want to compile the ARM Mali Display │
│ Processor driver. It supports the DP500, DP550 and DP650 variants │
│ of the hardware. │
│ │
│ If compiled as a module it will be called mali-dp.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 26, 2016 12:38 pm

Here are my steps for building a working kernel for the c2. You also need to build a recent version of uboot that supports ethernet for tftp or use serial to load the kernel image, device tree and uinitrd.
This example uses tftp as mmc is not in u-boot as yet but boots into Linux with mmc support. Done on a new updated version of hard-kernel ubuntu. Ill post my uboot config and install details soon.

Edit: See updates in this post and scripts later in thread for mmc booting via BlueMatt's git, i have modified this post to provide info on building and installing the kernel to boot via mmc or tftp

Make sure you have backups or you are prepared to recreate as this will stop your c2 from booting normally

You will also need serial UART support to see the u-boot console.

Code: Select all

git clone --depth=1 -b v4.7/integ git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git
sudo apt-get install git build-essential gcc libncurses5-dev
cd linux-amlogic
Attached is a working config or

Code: Select all

make menuconfig
enable meson spi, i2c, watchdog, arm64 hardware crypt instructions, sd/ mmc, serial console, virtualisation, and nfs
make and install modules..

Code: Select all

make -j4
sudo make modules_install
Edit: added install dtbs to allow boot from mcc ext partitions
Installed the dtbs

Code: Select all

sudo make dtbs_install
I backup the images on the fat partition as the install step will overwrite them

Code: Select all

sudo cp /media/boot/uInitrd /media/boot/uInitrd.orig
sudo cp /media/boot/Image /media/boot/Image.orig
sudo make install
Edit: as this procedure works for mmc uboot as well
To boot via tftp via a host machine copy over boot files (Not needed if you are booting a version of u-boot supporting mmc)...

Code: Select all

scp -p arch/arm64/boot/Image brad@10.1.1.104:/tftpboot
scp -p arch/arm64/boot/dts/amlogic/* brad@10.1.1.104:/tftpboot
scp -p /boot/uInitrd-4.7.0-rc4+  brad@10.1.1.104:/tftpboot
Next my script to paste into u-boot command over UART interface to boot from the tftp server I have setup and start the kernel with mmc support (change the ip addresses and kernel names )..
Edit: For MMC supported u-boot see scripts further down the thread

Code: Select all

#MMC Boot via tftp
setenv kernel_addr 11000000
setenv fdt_addr 1000000
setenv initrd_loadaddr 22000000
setenv tftpbootfile Image
setenv tftpfdtfile meson-gxbb-odroidc2.dtb
setenv tftpinitrdfile uInitrd-4.7.0-rc4+
setenv ipaddr 10.1.1.106
setenv serverip 10.1.1.104
setenv fsargs "setenv bootargs root=UUID=e139ce78-9841-40fe-8823-96a304a09859 ro no_console_suspend fsck.fix=yes"
setenv start_odroidc2_mmc 'tftp ${initrd_loadaddr} ${tftpinitrdfile} ;tftp ${kernel_addr} ${tftpbootfile};tftp ${fdt_addr} ${tftpfdtfile};run fsargs ;booti ${kernel_addr} ${initrd_loadaddr} ${fdt_addr}'
run start_odroidc2_mmc
Attachments
config_c2_mmc.txt
Test build c2 mmc v4.7/integ
(125.48 KiB) Downloaded 160 times
Last edited by brad on Mon Jun 27, 2016 11:35 am, edited 1 time in total.

stmicro
Posts: 251
Joined: Tue Apr 28, 2015 4:23 pm
languages_spoken: english, chinese
ODROIDs: Many Odroids and Rpis.
Location: shenzhen china
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by stmicro » Sun Jun 26, 2016 1:04 pm

Can I use hk's stock u-boot instead of the upstream one?

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 26, 2016 1:27 pm

stmicro wrote:Can I use hk's stock u-boot instead of the upstream one?
Unfortunately not, it wont boot 4.x kernels

New Uboot Host machine config (This will build u-boot with no sd card support (Ethernet and Serial Only)

I haven't tested what dependencies are needed to do this if you have trouble let me know and ill work it out hopefully. Also let me know if you have troubles I may have missed something.

=======================
Ubuntu 15.10 wily x64 host
download the GNU toolchain (dont use an elf one) https://releases.linaro.org/components/ ... gnu.tar.xz

Code: Select all

sudo mkdir -p /opt/toolchains
sudo tar xvf gcc-linaro-5.3-2016.02-x86_64_aarch64-linux-gnu.tar.xz -C /opt/toolchains/
edit your .bashrc
vi ~/.bashrc

Code: Select all

export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
export PATH=/opt/toolchains/gcc-linaro-5.3-2016.02-x86_64_aarch64-linux-gnu/bin/:$PATH
Regrap your bashrc source..

Code: Select all

source ~/.bashrc
download source from this commit as its before the eth was disabled...
http://git.denx.de/?p=u-boot.git;a=snap ... 153;sf=tgz

Edit: or better yet use BlueMatt's U-boot git with mmc support posted in this thread

Code: Select all

tar -xf u-boot-bfcef28.tar.gz
cd u-boot-bfcef28
make odroid-c2_defconfig
make -j4
copy fips and sd_fuse directories accross from hardkernel u-boot source https://github.com/hardkernel/u-boot/tr ... 2-v2015.01

Once all copied the following should create the new image for you which can boot from the secure loader (run from the source tree root still)...

Code: Select all

cd fip/gxb/
cp ../../u-boot.bin bl33.bin
../fip_create --bl30 bl30.bin --bl301 bl301.bin --bl31 bl31.bin --bl33 bl33.bin fip.bin
../fip_create --dump fip.bin
cat bl2.package fip.bin > boot_new.bin
./aml_encrypt_gxb --bootsig --input boot_new.bin --output u-boot.bin
dd if=u-boot.bin of=../../sd_fuse/u-boot.bin bs=512 skip=96
cd ../../sd_fuse/
dd if=bl1.bin.hardkernel of=../u-boot.bin conv=fsync
dd if=bl1.bin.hardkernel of=../u-boot.bin conv=fsync,notrunc bs=512 skip=1 seek=1
dd if=u-boot.bin of=../u-boot.bin conv=fsync,notrunc bs=512 skip=1 seek=97
Finally this will install the new u-boot into your sdcard (make sure you check you have the correct path for sd)

Code: Select all

./sd_fusing.sh /dev/mmcblk0
Last edited by brad on Mon Jun 27, 2016 11:37 am, edited 1 time in total.

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Sun Jun 26, 2016 2:55 pm

https://github.com/TheBlueMatt/u-boot has the MMC patches rebased against u-boot v2016.07-rc2 (the latest rc). It still has eth disabled because I didnt bother to revert that change from the rc.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 26, 2016 3:10 pm

BlueMatt wrote:https://github.com/TheBlueMatt/u-boot has the MMC patches rebased against u-boot v2016.07-rc2 (the latest rc). It still has eth disabled because I didnt bother to revert that change from the rc.
Ill try this now as Im wanting to look at
umiddelb wrote:may be u-571

stmicro
Posts: 251
Joined: Tue Apr 28, 2015 4:23 pm
languages_spoken: english, chinese
ODROIDs: Many Odroids and Rpis.
Location: shenzhen china
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by stmicro » Sun Jun 26, 2016 5:22 pm

@brad,
Thank you the nice beginner friendly instruction to build the upstream u-boot.
I'm going to configure my TFTF server. But the MMC patches can enable the SD/eMMC function on u-boot soon hopefully.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Sun Jun 26, 2016 5:45 pm

stmicro wrote:@brad,
Thank you the nice beginner friendly instruction to build the upstream u-boot.
I'm going to configure my TFTF server. But the MMC patches can enable the SD/eMMC function on u-boot soon hopefully.
thanks to BlueMatt you can use the link above to create a u-boot which supports mmc

still need to use the UART serial as far as i can workout to start

here is my script i paste in to start kernel images from the fat partition using BlueMatt's git, i haven't tried ext yet but i can read the filesystem ok.

Code: Select all

#MMC Boot
setenv kernel_addr 11000000
setenv fdt_addr 1000000
setenv initrd_loadaddr 13000000
setenv bootfile Image
setenv fdtfile meson-gxbb-odroidc2.dtb
setenv initrdfile uInitrd
setenv fsargs "setenv bootargs root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rw no_console_suspend fsck.fix=yes"
setenv bootcmd 'fatload mmc 0:1 ${initrd_loadaddr} ${initrdfile} ;fatload mmc 0:1 ${kernel_addr} ${bootfile};fatload mmc 0:1 ${fdt_addr} ${fdtfile};run fsargs ;booti ${kernel_addr} ${initrd_loadaddr} ${fdt_addr}'
boot
Id love to know now to make u-boot autoboot, just cant seem to get it to boot from boot.ini , uEnv.txt or whatever other names.
Anyone know how to compile in the default search areas / filenames?

Maybe I need to compile it as a scr

KARL23
Posts: 15
Joined: Sun Jun 26, 2016 10:59 pm
languages_spoken: english
ODROIDs: c1, c2,xu4
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by KARL23 » Mon Jun 27, 2016 12:02 am

I got the v4.7/integ branch with BlueMatt uboot running. it starts the odroidian basic image. The only thing I'm missing at this point is the usb support. does anyone know an usb patch flying around for the mainline 4.7rc4 kernel?

Any Info appreciated.

I disabled the mmc debug Info in the kernel config. to stop flooding the logs with these messages:

Code: Select all

Jun 26 16:45:24 odroid64 kernel: [ 8251.453157] mmc0: starting CMD13 arg 00010000 flags 00000195
Jun 26 16:45:24 odroid64 kernel: [ 8251.453179] mmc0: req done (CMD13): 0: 00000900 00000000 00000000 00000000
Jun 26 16:45:24 odroid64 kernel: [ 8251.453191] mmc0: starting CMD25 arg 00339fe0 flags 000000b5
Jun 26 16:45:24 odroid64 kernel: [ 8251.453200] mmc0:     blksz 512 blocks 8 flags 00000100 tsac 3000 ms nsac 0
Jun 26 16:45:24 odroid64 kernel: [ 8251.453206] mmc0:     CMD12 arg 00000000 flags 0000049d
Jun 26 16:45:24 odroid64 kernel: [ 8251.454236] mmc0: req done (CMD25): 0: 00000900 00000000 00000000 00000000
Jun 26 16:45:24 odroid64 kernel: [ 8251.454242] mmc0:     4096 bytes transferred: 0
Jun 26 16:45:24 odroid64 kernel: [ 8251.454248] mmc0:     (CMD12): 0: 00000c00 00000000 00000000 00000000
Jun 26 16:45:24 odroid64 kernel: [ 8251.454261] mmc0: starting CMD13 arg 00010000 flags 00000195
Jun 26 16:45:24 odroid64 kernel: [ 8251.454282] mmc0: req done (CMD13): 0: 00000900 00000000 00000000 00000000
Jun 26 16:45:24 odroid64 kernel: [ 8251.454294] mmc0: starting CMD18 arg 0020aff0 flags 000000b5
Jun 26 16:45:24 odroid64 kernel: [ 8251.454301] mmc0:     blksz 512 blocks 8 flags 00000200 tsac 100 ms nsac 0
Jun 26 16:45:24 odroid64 kernel: [ 8251.454307] mmc0:     CMD12 arg 00000000 flags 00000095
Jun 26 16:45:24 odroid64 kernel: [ 8251.454886] mmc0: req done (CMD18): 0: 00000900 00000000 00000000 00000000
Jun 26 16:45:24 odroid64 kernel: [ 8251.454892] mmc0:     4096 bytes transferred: 0

Thanks
Attachments
odroidc2-dmesg-4.7-rc4.txt
Dmesg after disable debug mmc
(19.15 KiB) Downloaded 142 times

BlueMatt
Posts: 14
Joined: Sun Jun 19, 2016 1:44 pm
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by BlueMatt » Mon Jun 27, 2016 3:35 am

I'm not aware of any USB patches as of yet. I spent some time playing around with it and it looks like the existing dwc2 driver will work for us, but I was unable to get the clocks to reset to initialize it. There are some folks on IRC working on it, so expect some progress sooner or later, in time for 4.8, I'd hope.

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Mon Jun 27, 2016 11:24 am

U-boot script to start using the u-boot mmc (BlueMatt's uboot git) and booting installed 4.x kernels direct from the ext partition (does not look at fat partition)..

You need to change the versions of the kernel in the filenames and fdtfile to suit which kernel you are wanting to start with (this is for the v4.7/integ branch kernel posted above)

Code: Select all

#MMC Boot from ext partition any installed 4.x kernel
setenv kernel_addr 11000000
setenv fdt_addr 1000000
setenv initrd_loadaddr 13000000
setenv bootfile /boot/vmlinuz-4.7.0-rc4+
setenv fdtfile /boot/dtbs/4.7.0-rc4+/amlogic/meson-gxbb-odroidc2.dtb
setenv initrdfile /boot/uInitrd-4.7.0-rc4+
setenv fsargs "setenv bootargs root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rw no_console_suspend fsck.fix=yes"
setenv bootcmd 'ext2load mmc 0:2 ${initrd_loadaddr} ${initrdfile} ;ext2load mmc 0:2 ${kernel_addr} ${bootfile};ext2load mmc 0:2 ${fdt_addr} ${fdtfile};run fsargs ;booti ${kernel_addr} ${initrd_loadaddr} ${fdt_addr}'
boot
You also need to perfrom an additional step after you to a kernel install which is a

Code: Select all

odroid@odroid64:~/linux-amlogic$ sudo make dtbs_install
This will install the dtb's into and easy to find structure under ext boot share /boot/dtbs/ which we can use to read the device tree

Now going to try to boot the hardkernel 3.14.x kernel from new u-boot

brad
Posts: 1050
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 26 times
Been thanked: 55 times
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by brad » Tue Jun 28, 2016 5:06 pm

brad wrote:Id love to know now to make u-boot autoboot, just cant seem to get it to boot from boot.ini , uEnv.txt or whatever other names.
Anyone know how to compile in the default search areas / filenames?
OK I think I worked this out, normally done inside the board source and compiled into U-boot, each board has its own default boot config defined. Here is the odroid-c2 at the moment..

http://git.denx.de/?p=u-boot.git;a=blob ... droid-c2.h

There is no environment setup (As it is in early stage and has not yet been completed)

This raises a couple of questions to hardkernel if its not too early for answers....

Are there any plans to provide input into the default boot environment in the upcoming u-boot?
Are there any plans to support the 4.8 kernel and possibly u-boot mainline if it happens to be compatible enough with the C2 when released?

Thanks, Brad.

daggs
Posts: 229
Joined: Tue Mar 22, 2016 6:34 pm
languages_spoken: english, spanish
ODROIDs: odroid c2
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Booting alternate kernels 4.6~4.7

Unread post by daggs » Tue Jun 28, 2016 5:34 pm

brad wrote:
brad wrote:Id love to know now to make u-boot autoboot, just cant seem to get it to boot from boot.ini , uEnv.txt or whatever other names.
Anyone know how to compile in the default search areas / filenames?
OK I think I worked this out, normally done inside the board source and compiled into U-boot, each board has its own default boot config defined. Here is the odroid-c2 at the moment..

http://git.denx.de/?p=u-boot.git;a=blob ... droid-c2.h

There is no environment setup (As it is in early stage and has not yet been completed)

This raises a couple of questions to hardkernel if its not too early for answers....

Are there any plans to provide input into the default boot environment in the upcoming u-boot?
Are there any plans to support the 4.8 kernel and possibly u-boot mainline if it happens to be compatible enough with the C2 when released?

Thanks, Brad.
I've asked about the kernel in another thread, their method of work afaiu, is to forward port their local branch to mainline.
e.g. 3.14 > mainline. some of the code reached 3.18 I think.

Post Reply

Return to “Other OS”

Who is online

Users browsing this forum: No registered users and 0 guests