Building on xubuntu 64bits, and at the end this message appears:
/usr/sbin/debootstrap: 1290: /usr/sbin/debootstrap: cannot create /media/user/debian/debian-mini-odroid-c1/trunk/rootfs.base.tmp/test-dev-null: Permission denied
E: Cannot install into target '/media/user/debian/debian-mini-odroid-c1/trunk/rootfs.base.tmp' mounted with noexec or nodev
make[1]: *** [rootfs.base] Error 1
make[1]: Leaving directory `/media/user/debian/debian-mini-odroid-c1/trunk'
make: *** [build-rootfs] Error 2

I`ve tried both with "sudo make" and sudo su from root account, yet without any success...
Anyone could help with this?

When doing make I get an error that is not installed, so dosfstools need to be installed on debain system.

The C2 image takes 2-3 minutes to successfully boot up. The guys from #odroid (Freenode) suggested that this could be related to some Ethernet driver. And indeed the board does not get a DHCP lease. eth0 and lo interfaces are up.
Anyone else having problems with the C2 image / was able to resolve them?

Neither the Hardkernel Ubuntu 16.04 nor the C1 image (from this repo) had such problems.

EDIT:

Tried to debug this via UART: The last message which is logged to the kernel ring buffer is random nonblocking pool is initialized. Something which runs after that causes the lag.
I was also able to reproduce the issue with several different kernels, ranging from latest odroidc2-3.14.y (2016/11/20) to a version from early 2016.

Here's the full boot log: https://pastebin.ubuntu.com/23565023/

make DIST=jessie IMAGE_MB=1024 results in the follwong error

Mounting boot partition on /dev/loop1...
cp: failed to preserve ownership for ‘mnt/meson8b_odroidc.dtb’: Operation not permitted
cp: failed to preserve ownership for ‘mnt/uImage’: Operation not permitted
rootfs.mak:64: recipe for target 'sdcard-jessie.img' failed
make[1]: *** [sdcard-jessie.img] Error 1
make[1]: Leaving directory '/usr/local/src/debian-mini-odroid-c1'
Makefile:34: recipe for target 'build-rootfs' failed
make: *** [build-rootfs] Error 2

# lsb_release -a
Distributor ID: Debian
Description:    Debian GNU/Linux 8.3 (jessie)
Release:        8.3
Codename:       jessie

# uname -r
3.16.0-4-amd64

# dpkg -D777 -i /var/cache/apt/archives/linux-image-3.10.69-69_20150214_armhf.deb
D000001: ensure_diversions: new, (re)loading
D000001: ensure_statoverrides: new, (re)loading
D000010: ensure_pathname_nonexisting '/var/lib/dpkg/tmp.ci'
(Reading database ... 35821 files and directories currently installed.)
Preparing to unpack .../linux-image-3.10.69-69_20150214_armhf.deb ...
D000001: process_archive oldversionstatus=not installed
D000002: fork/exec /var/lib/dpkg/tmp.ci/preinst ( install )
Done.
D000001: ensure_diversions: same, skipping
Unpacking linux-image-3.10.69-69 (20150214) ...
D000010: tarobject ti->name='.' mode=40755 owner=0:0 type=53(d) ti->linkname='' namenode='/.' flags=2 instead='<none>'
D000100: setupvnamevbs main='/.' tmp='/..dpkg-tmp' new='/..dpkg-new'
D000100: tarobject already exists
D000100: tarobject directory exists
D000010: tarobject ti->name='./boot' mode=40755 owner=0:0 type=53(d) ti->linkname='' namenode='/boot' flags=2 instead='<none>'
D000100: setupvnamevbs main='/boot' tmp='/boot.dpkg-tmp' new='/boot.dpkg-new'
D000100: tarobject already exists
D000100: tarobject directory exists
D000010: tarobject ti->name='./boot/uImage-3.10.69-69' mode=100600 owner=0:0 type=48(-) ti->linkname='' namenode='/boot/uImage-3.10.69-69' flags=2 instead='<none>'
D000100: setupvnamevbs main='/boot/uImage-3.10.69-69' tmp='/boot/uImage-3.10.69-69.dpkg-tmp' new='/boot/uImage-3.10.69-69.dpkg-new'
D000100: tarobject nonexistent
D000010: ensure_pathname_nonexisting '/boot/uImage-3.10.69-69.dpkg-new'
D000010: ensure_pathname_nonexisting '/boot/uImage-3.10.69-69.dpkg-tmp'
D000100: tarobject file open size=5319236
D000100: tarobject file hash=57f89da1a47cc20fd9a89233eaafae9a
D000100: tarobject new - no backup
D000100: tarobject done and installation deferred
D000010: tarobject ti->name='./boot/meson8b_odroidc.dtb' mode=100644 owner=0:0 type=48(-) ti->linkname='' namenode='/boot/meson8b_odroidc.dtb' flags=2 instead='<none>'
D000100: setupvnamevbs main='/boot/meson8b_odroidc.dtb' tmp='/boot/meson8b_odroidc.dtb.dpkg-tmp' new='/boot/meson8b_odroidc.dtb.dpkg-new'
D000100: tarobject already exists
D000010: ensure_pathname_nonexisting '/boot/meson8b_odroidc.dtb.dpkg-new'
D000010: ensure_pathname_nonexisting '/boot/meson8b_odroidc.dtb.dpkg-tmp'
D000100: tarobject file open size=18305
D000100: tarobject file hash=6ae005f627a81c0d79fbb90ea8feb0ce
D000100: tarobject nondirectory, 'link' backup
dpkg: error processing archive /var/cache/apt/archives/linux-image-3.10.69-69_20150214_armhf.deb (--install):
 unable to make backup link of `./boot/meson8b_odroidc.dtb' before installing new version: Operation not permitted
D000010: cu_installnew '/boot/meson8b_odroidc.dtb' flags=202
D000100: setupvnamevbs main='/boot/meson8b_odroidc.dtb' tmp='/boot/meson8b_odroidc.dtb.dpkg-tmp' new='/boot/meson8b_odroidc.dtb.dpkg-new'
D000100: cu_installnew not restoring
D000100: secure_remove '/boot/meson8b_odroidc.dtb.dpkg-new' unlink OK
D000010: cu_installnew '/boot/uImage-3.10.69-69' flags=602
D000100: setupvnamevbs main='/boot/uImage-3.10.69-69' tmp='/boot/uImage-3.10.69-69.dpkg-tmp' new='/boot/uImage-3.10.69-69.dpkg-new'
D000100: cu_installnew not restoring
D000100: secure_remove '/boot/uImage-3.10.69-69.dpkg-new' unlink OK
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
D000002: fork/exec /var/lib/dpkg/tmp.ci/postrm ( abort-install )
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.10.69-69 /boot/vmlinuz-3.10.69-69
D000001: ensure_diversions: same, skipping
D000010: ensure_pathname_nonexisting '/var/lib/dpkg/tmp.ci'
D000010: ensure_pathname_nonexisting running rm -rf '/var/lib/dpkg/tmp.ci'
D000010: ensure_pathname_nonexisting '/var/lib/dpkg/reassemble.deb'
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-3.10.69-69_20150214_armhf.deb

Odroid mounts the FAT32 to /media/boot.

I get the following error

/bin/sh: 1: bc: not found
/usr/local/src/debian-mini-odroid-c1/linux/kernel/Makefile:141: recipe for target 'kernel/timeconst.h' failed
make[3]: *** [kernel/timeconst.h] Error 127
Makefile:803: recipe for target 'kernel' failed
make[2]: *** [kernel] Error 2
make[2]: Leaving directory '/usr/local/src/debian-mini-odroid-c1/linux'
linux.mak:42: recipe for target 'linux/arch/arm/boot/uImage' failed
make[1]: *** [linux/arch/arm/boot/uImage] Error 2
make[1]: Leaving directory '/usr/local/src/debian-mini-odroid-c1'
Makefile:34: recipe for target 'build-linux' failed
make: *** [build-linux] Error 2

bc should be added to the list of package requirements.

I've tried building this image twice (awesome code btw, love your project!!) but gotten the same error both times. I tried the clearing loop device thing you suggested to the other similar issue, but still had this problem. Any ideas? (I'm building on: Linux xxxx 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:45 UTC 2014 i686 i686 i686 GNU/Linux on an Intel Atom first gen with 1GB ram). Thanks!

update-initramfs: Generating /boot/initrd.img-3.10.66
for i in patches/.patch ; do patch -p0 -d rootfs < $i ; done
patching file etc/init.d/ssh
patching file etc/default/tmpfs
umount rootfs/proc
umount rootfs/sys
umount rootfs/dev
rm rootfs/postinstall
rm -rf rootfs/postinst/
rm rootfs/usr/bin/qemu-arm-static
touch rootfs
mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n uInitrd -d rootfs/boot/initrd.img- uInitrd
Image Name: uInitrd
Created: Thu Jan 29 21:14:46 2015
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 12866402 Bytes = 12564.85 kB = 12.27 MB
Load Address: 00000000
Entry Point: 00000000
if test -f "sdcard.img.tmp"; then rm "sdcard.img.tmp" ; fi
./createimg sdcard.img.tmp 32 768 boot rootfs u-boot/sd_fuse uInitrd
787185+0 records in
787185+0 records out
806077440 bytes (806 MB) copied, 39.3685 s, 20.5 MB/s
2+0 records in
2+0 records out
2 bytes (2 B) copied, 0.000260504 s, 7.7 kB/s
442+0 records in
442+0 records out
442 bytes (442 B) copied, 0.0142314 s, 31.1 kB/s
63+0 records in
63+0 records out
32256 bytes (32 kB) copied, 0.00910132 s, 3.5 MB/s
460+1 records in
460+1 records out
235964 bytes (236 kB) copied, 0.0398957 s, 5.9 MB/s
Warning: sdcard.img.tmp is not a block device
Disk sdcard.img.tmp: cannot get geometry

Disk sdcard.img.tmp: 98 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
sdcard.img.tmp1 0 - 0 0 Empty
sdcard.img.tmp2 0 - 0 0 Empty
sdcard.img.tmp3 0 - 0 0 Empty
sdcard.img.tmp4 0 - 0 0 Empty
New situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
sdcard.img.tmp1 * 2048 80324 78277 c W95 FAT32 (LBA)
sdcard.img.tmp2 80325 1574369 1494045 83 Linux
sdcard.img.tmp3 0 - 0 0 Empty
sdcard.img.tmp4 0 - 0 0 Empty
Successfully wrote the new partition table

Re-reading the partition table ...
BLKRRPART: Inappropriate ioctl for device

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
Error: /dev/loop0: unrecognised disk label
make[1]: *** [sdcard.img] Error 1
make[1]: Leaving directory `/home/xxxx/Downloads/debian-mini-odroid-c1-master'
make: *** [build-rootfs] Error 2

Just a thought on this. It's likely that if you run partprobe (from the parted package) before the mkfs and mount commands, the problem goes away.

Hi all,

I'm trying to run this script on Gentoo. (I think) I've installed all the dependencies, but now somewhere in the middle of make I'm getting

/mnt/ramdisk/debian-mini-odroid-c1 $ sudo make DIST=jessie IMAGE_MB=1024
...
/mnt/ramdisk/debian-mini-odroid-c1/u-boot/mkconfig -A odroidc
make[2]: execvp: /mnt/ramdisk/debian-mini-odroid-c1/u-boot/mkconfig : Permission denied

The same happens if I try to execute the like in question by hand:

/mnt/ramdisk/debian-mini-odroid-c1 $ sudo /mnt/ramdisk/debian-mini-odroid-c1/u-boot/mkconfig -A odroidc
sudo: unable to execute /mnt/ramdisk/debian-mini-odroid-c1/u-boot/mkconfig: Permission denied
/mnt/ramdisk/debian-mini-odroid-c1 $ ll /mnt/ramdisk/debian-mini-odroid-c1/u-boot/ | grep mkconf
-rwxrwxrwx   1 root root   4495  3 June  02:32 mkconfig

I have u-boot-tools 2014.01, the last version marked stable in the repository.

How do I go about solving this?

The boot.ini containing a few lines to disable the video core will give the system 100MB+ of more usable memory.

fdt addr 21800000
fdt rm /mesonfb
fdt rm /mesonstream
fdt rm /vdec
fdt rm /ppmgr

#12

The odroid bootini package already contains this in a neat and configurable format.

I have noticed the framebuffer init script is forwarding the output to the display after kernel file system in mounted. That is why the screen remains black (empty) during boot up until the login prompt pops up. Just like every other Linux OS, how can I display the console output to the monitor while booting?

http://www.freedesktop.org/software/systemd/man/systemd-firstboot.html

This would include hostname, timezone, locale, ssh hostkey generation and sshd configuration changes (no root login with passwords per default in jessie).

I can look into this later when jessie becomes stable.

Trying to build the jessie image, I'm hitting a failure in createimg:

sfdisk: unrecognized option '--in-order'

Searching for information about the --in-order option, I found it referred to as an "undocumented dangerous option". Perhaps it was removed after a certain version? Do others typically build in an older version of Ubuntu?

build target jessie
sfdisk from util-linux 2.26.2
Ubuntu 15.10

Has anybody succeeded running Docker on this image? I've installed it per these instructions, then installed Apparmor (somehow it wasn't pulled as a dependency), but running Hello World crashes with

root@odroidc1:~# docker run --rm hello-world
FATA[0000] Error response from daemon: Cannot start container 1e9962970cc67fba6c333d8bfd6b68782c616f05db831e3d3f2c8dff7b8e900d: [8] System error: operation not supported

I have also created an issue in the Docker bugtracker.

# make ODROID=c2 DIST=jessie IMAGE_MB=4096
make -f uboot.mak build
make[1]: Entering directory '/root/debian-mini-odroid-c1'
wget -O gcc-linaro-aarch64-none-elf-4.9-2014.09_linux.tar.xz https://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-aarch64-none-elf-4.9-2014.09_linux.tar.xz
--2016-12-07 14:59:15--  https://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-aarch64-none-elf-4.9-2014.09_linux.tar.xz
Resolving releases.linaro.org (releases.linaro.org)... 64.28.99.46
Connecting to releases.linaro.org (releases.linaro.org)|64.28.99.46|:443... connected.
HTTP request sent, awaiting response... 404 NOT FOUND
2016-12-07 14:59:16 ERROR 404: NOT FOUND.

The file gcc-linaro-aarch64-none-elf-4.9-2014.09_linux.tar.xz can not be found on the server.

Hello! This is a great piece of software and makes things a lot easier, so big thanks!

Could anyone tell me how I could install additional packages into a ROM I'd like to create?
Is it possible to also add additional repositories in the finished ROM's /etc/apt/sources.list ? I notice you can add files so would I need to put in a modified file at /etc/apt/sources.list ?

Thank you

hello,

thanks for this repo !
I have an error after one hour of compilation:

I: Extracting xz-utils...
I: Extracting zlib1g...
cp `which qemu-arm-static` rootfs.base.tmp/usr/bin
chroot rootfs.base.tmp /bin/bash -c "/debootstrap/debootstrap --second-stage"
chroot: failed to run command '/bin/bash': Exec format error
make[1]: *** [rootfs.base] Error 126
make[1]: Leaving directory `/odroid'
make: *** [build-rootfs] Error 2

I'm running ubuntu 14.04 in a docker on my mack and followed the readme.
Any idea ?

Hi All

I am working on building/porting Julia on ppc64le architecture. I am using Ubuntu 14.10 on top of ppc64le hardware, while compiling Julia code (master branch) I was getting segmentation fault, I am able to resolve this segmentation fault by turning on ‘MEMDEBUG’ flag from ‘src/options.h’ file.

I decided to work more this issue and try to find out root cause of segmentation fault, so I started studying/understanding memory management scheme of Julia.

To understanding GC and de-allocation mechanism I turn on profiling options ‘MEMPROFILE’ ,’ GC_TIME’ from ‘options.h’ file (by default they are commented out I uncomment those) but when I try to compile code with these profiling flags on julia compilation (make debug) gets failed.

Below compilation errors I observed after enabling,

1. ‘GC_TIME’ flag
   gc.c:237:26: error: current_heap undeclared (first use in this function)
   #define HEAP(x) (*((void)current_heap,&(x)))
2. ‘MEMPROFILE’ flag
   gc.c:2414:21: error: pool_t has no member named pages

My Machine details are:
Linux 3.16.0-30-generic #40-Ubuntu SMP ppc64le ppc64le ppc64le GNU/Linux

-Mahesh

`mihau@home:debootstrap$ cat debootstrap.log
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg':
missing description
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 5 package 'dpkg':
missing architecture
Selecting previously unselected package base-passwd.
(Reading database ... 0 files and directories currently installed.)
Preparing to unpack .../base-passwd_3.5.37_arm64.deb ...
Unpacking base-passwd (3.5.37) ...
dpkg: base-passwd: dependency problems, but configuring anyway as you requested:
base-passwd depends on libc6 (>= 2.17); however:
Package libc6 is not installed.
base-passwd depends on libdebconfclient0 (>= 0.145); however:
Package libdebconfclient0 is not installed.

Setting up base-passwd (3.5.37) ...
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 24 package 'dpkg':
missing description
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 24 package 'dpkg':
missing architecture
Selecting previously unselected package base-files.
dpkg: regarding .../base-files_8+deb8u4_arm64.deb containing base-files, pre-dependency problem:
base-files pre-depends on awk
awk is not installed.

dpkg: warning: ignoring pre-dependency problem!
(Reading database ... 41 files and directories currently installed.)
Preparing to unpack .../base-files_8+deb8u4_arm64.deb ...
Unpacking base-files (8+deb8u4) ...
dpkg: error processing archive /var/cache/apt/archives/base-files_8+deb8u4_arm64.deb (--install):
symbolic link '/etc/os-release' size has changed from 50 to 21
Errors were encountered while processing:
/var/cache/apt/archives/base-files_8+deb8u4_arm64.deb`

so i followed the steps and got a running debian jessie.

df -h however gives:

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       926M  788M  114M  88% /
devtmpfs        407M     0  407M   0% /dev
tmpfs           411M     0  411M   0% /dev/shm
tmpfs           411M   12M  399M   3% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           411M     0  411M   0% /sys/fs/cgroup
tmpfs           411M     0  411M   0% /tmp
/dev/mmcblk0p1   38M   24M   15M  63% /boot

seems like not all 32 gb of the sd card are used. how can i expand the fs?

http://en.wikipedia.org/wiki/F2FS

As the storage of these devices is MicroSD or eMMC, using F2FS for the rootfs would make sense as it is a purpose specific tool for this scope versus the currently used general purpose ext4.

Setting the block size to 4K makes sense to me, but my deeper understanding of flash storage there fails to grasp why set the stride and stripe-width? These are usually set to match up the filesystem to the underlying geometry in a RAID array - is there a parallel of such sorts in flash storage?

If so, how to replicate for F2FS?

mkfs.f2fs -h

    F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-09-18)

mkfs.f2fs: invalid option -- 'h'
    Error: Unknown option ?

Usage: mkfs.f2fs [options] device [sectors]
[options]:
  -a heap-based allocation [default:1]
  -d debug level [default:0]
  -e [extension list] e.g. "mp3,gif,mov"
  -l label
  -o overprovision ratio [default:5]
  -s # of segments per section [default:1]
  -z # of sections per zone [default:1]
  -t 0: nodiscard, 1: discard [default:1]
sectors: number of sectors. [default: determined by device size]

Hello, thanks for this image, works perfectly.

I would like to know if you have some experience with installing drivers for wifi dongles as for the moment, none of them are recognized with this debian ?

Hello,

I wanted to use the meson ir sensor on the odroid-c1 board but the package in the debian repo obviously has no support for this driver.
Any hint would be appreciated.

I see that the meson-irblaster module is present in the kernel, or at least some data is available via sysfs.

Hi ,

is it normal that /boot/system.map is in read file system only. I can't install the new image of linux ? Have you a idea ? :)

PS : i have used this to update the kernel : https://github.com/mdrjr/odroid-utility

Thank you for your help

I wonder wether the build debian will also work and accelerate all features of ODROID C1+.

Can't build the final image.

sfdisk complains that sdcard.img.tmp ain't a proper block device.
Seems like dd fails to create the block device in createimg.sh, line 86-90.

Build machine:

Linux cube 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Description:    Ubuntu 14.04.1 LTS

Build console output:

if test -f "sdcard.img.tmp"; then rm "sdcard.img.tmp" ; fi
./createimg.sh sdcard.img.tmp 32 768 boot rootfs u-boot/sd_fuse uInitrd
787185+0 records in
787185+0 records out
806077440 bytes (806 MB) copied, 6.16638 s, 131 MB/s
2+0 records in
2+0 records out
2 bytes (2 B) copied, 7.9592e-05 s, 25.1 kB/s
442+0 records in
442+0 records out
442 bytes (442 B) copied, 0.000525154 s, 842 kB/s
63+0 records in
63+0 records out
32256 bytes (32 kB) copied, 0.000185517 s, 174 MB/s
460+1 records in
460+1 records out
235963 bytes (236 kB) copied, 0.000633836 s, 372 MB/s
Warning: sdcard.img.tmp is not a block device
Disk sdcard.img.tmp: cannot get geometry

Disk sdcard.img.tmp: 98 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
sdcard.img.tmp1             0         -          0   0  Empty
sdcard.img.tmp2             0         -          0   0  Empty
sdcard.img.tmp3             0         -          0   0  Empty
sdcard.img.tmp4             0         -          0   0  Empty
New situation:
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
sdcard.img.tmp1   *      2048     80324      78277   c  W95 FAT32 (LBA)
sdcard.img.tmp2         80325   1574369    1494045  83  Linux
sdcard.img.tmp3             0         -          0   0  Empty
sdcard.img.tmp4             0         -          0   0  Empty
Successfully wrote the new partition table

Re-reading the partition table ...
BLKRRPART: Inappropriate ioctl for device

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
losetup: could not find any free loop device
make[1]: *** [sdcard.img] Error 255

createimg.sh expands the dd commands whith these values:

dd if=/dev/zero of=sdcard.img.tmp bs=1024 count=787185
echo -e "\x55\xaa" | dd bs=1 count=2 seek=510 of=sdcard.img.tmp conv=notrunc
dd if=u-boot/sd_fuse/bl1.bin.hardkernel of=sdcard.img.tmp bs=1 count=442 conv=notrunc
dd if=u-boot/sd_fuse/bl1.bin.hardkernel of=sdcard.img.tmp bs=512 skip=1 seek=1 conv=notrunc
dd if=u-boot/sd_fuse/u-boot.bin of=sdcard.img.tmp bs=512 seek=64 conv=notrunc

Hi,

I think it should it be possible to use https://wiki.debian.org/FakeRoot instead of requiring root for building.
Building kernels as root is strongly discouraged.

(Almost) right after installation on a 16Gb microSD card, this is what my partition table looks like:

# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0000de21

Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk0p1 *     2048   80324   78277 38.2M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      80325 2040254 1959930  957M 83 Linux

Which, translated into human units, means that I don't have much storage available:

# df -h 
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       926M  773M  128M  86% /
devtmpfs        407M     0  407M   0% /dev
tmpfs           411M     0  411M   0% /dev/shm
tmpfs           411M   12M  399M   3% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           411M     0  411M   0% /sys/fs/cgroup
tmpfs           411M     0  411M   0% /tmp
/dev/mmcblk0p1   38M   24M   15M  63% /boot

The way odroid-utility.sh resizes the partition won't work with this setup, since they remove /dev/mmcblk0p2 and create a new one in its place, while this installation mounts that partition on /:

# mount | grep mmc
/dev/mmcblk0p2 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,stripe=16384,data=ordered)
/dev/mmcblk0p1 on /boot type vfat (ro,nosuid,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,flush,errors=remount-ro)

So is there any way to resize /dev/mmcblk0p2 from within Debian?

Hi,
i don't understand , i'm trying for four hours but without success :(.

I built and created the image and then copy on the SD card with the command "dd" on linux.

But when i start the odroid. I have the red light and blue light ( blink) with the ethernet ( blink ) but my screen is black or grey when i change the resolution in boot.ini. But never blank line on the screen :(.

Have you a idea of the problem ?
( i tried ubuntu 14.04 LTS and if i configure the resolution of the screen in boot.ini , that works, btw, it's the only which works )

Thanks you :)

Exemple of the boot.ini whick works with ubuntu 14.04 :

ODROIDC-UBOOT-CONFIG

// Possible screen resolutions
// Uncomment only a single Line! The line with setenv written.
// At least one mode must be selected.

// setenv m "vga" # 640x480
// setenv m "480p" # 720x480
// setenv m "576p" # 720x576
// setenv m "800x480p60hz" # 800x480
// setenv m "800x600p60hz" # 800x600
// setenv m "1024x600p60hz" # 1024x600
setenv m "1024x768p60hz" # 1024x768
// setenv m "1360x768p60hz" # 1360x768
// setenv m "1366x768p60hz" # 1366x768
// setenv m "1440x900p60hz" # 1440x900
// setenv m "1600x900p60hz" # 1600x900
// setenv m "1680x1050p60hz" # 1680x1050
// setenv m "720p" # 720p 1280x720
// setenv m "800p" # 1280x800
// setenv m "sxga" # 1280x1024
// setenv m "1080i50hz" # 1080I@50Hz
// setenv m "1080p24hz" # 1080P@24Hz
// setenv m "1080p50hz" # 1080P@50Hz
// setenv m "1080p" # 1080P@60Hz
// setenv m "1920x1200" # 1920x1200

// HDMI DVI Mode Configuration
setenv vout_mode "hdmi"
// setenv vout_mode "dvi"

// HDMI BPP Mode
setenv m_bpp "32"
// setenv m_bpp "24"
// setenv m_bpp "16"

// UHS Card Configuration
// Uncomment the line below to DISABLE UHS-1 MicroSD support
// This might break boot for some brand models of cards.
// setenv disableuhs "disableuhs"

// Disable VPU (Video decoding engine, Saves RAM!!!)
// 0 = disabled
// 1 = enabled
setenv vpu "1"

// Disable HDMI Output (Again, saves ram!)
// 0 = disabled
// 1 = enabled
setenv hdmioutput "1"

// Default Console Device Setting
// setenv condev "console=ttyS0,115200n8" # on serial port
setenv condev "console=tty0" # on display (HDMI)
// setenv condev "console=ttyS0,115200n8 console=tty0" # on both

// Boot Arguments
setenv bootargs "root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro ${condev} no_console_suspend vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full dmfc=3 cvbsmode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs}"

// Booting
fatload mmc 0:1 0x21000000 uImage
fatload mmc 0:1 0x22000000 uInitrd
fatload mmc 0:1 0x21800000 meson8b_odroidc.dtb
fdt addr 21800000

if test "${vpu}" = "0"; then fdt rm /mesonstream; fdt rm /vdec; fdt rm /ppmgr; fi

if test "${hdmioutput}" = "0"; then fdt rm /mesonfb; fi

bootm 0x21000000 0x22000000 0x21800000"

Hi,

I plane to buy ODroid-C1 but, I just receive from LinuxGizmo a comment with this link : http://g3zarstudios.com/blog/odroid-c1-more-like-the-oh-no-droid-c1/#comment-355

To resume, device is not stable, i plan to buy it to code a custom media player using libVLC, is your OS is enough stable to work? Do you have the same issue than the original OS provide by hardkernel ?

Thanks for your help,

WCdr

http://deb.odroid.in/c1.html

We could:

• Skip the manual kernel compilation and use their maintained kernel packages
• Use their uboot packages
• Grab the module blacklist fix package
• Use their boot.ini package

This would make the whole installation process a lot more lightweight.

How to reproduce: simply substitute "stable" with "jessie" in common.mk.

Since Debian jessie is using systemd per default, the patch for the SysV init file will not get executed on the first boot due to there being a distro provided valid systemd setup. Jessie will be under the keyword 'stable' soon and thus break this script.

Alternatives:

1. Make a systemd-tolerant solution for the first-boot ssh host key generation
2. Pin the script release in common.mk wheezy (it will be maintained oldstable for a year when jessie comes out)
3. Make debootstrap use SysV Init