8577f5d5e4
Use upstream Device Tree
2019-06-27 21:40:35 +01:00
8b6acd8207
Enable the bootloader UART
2019-06-27 21:39:49 +01:00
06ae6de858
Use the "rpi" kernel
2019-06-27 21:37:40 +01:00
822f75662d
Use Sid, instead of buster
2019-06-27 21:34:53 +01:00
6a51dedbf4
Create spec for Zero W
2019-06-27 21:05:18 +01:00
bfc2385c02
Experimentally adding recipes for building for models Zero+1, 2
...
I received reports the "lesser" raspberries do work. Lets try!
2019-02-15 17:28:28 -06:00
d8e2e24dde
Follow liw's suggestion of using a rootfs-tarball for a huge performance gain
2019-01-14 18:02:42 -06:00
b785c4837f
Merge pull request #49 from liwfi/liw/fix-for-vmdb2
...
Liw/fix for vmdb2
2019-01-14 17:25:34 -06:00
fe68770d3e
Change: use mount point names for all tags
...
/ and /boot specifically. I find these names to be clearer.
2019-01-13 15:48:00 +02:00
5e2dc9c569
Add: support for caching and unpacking the rootfs
...
This speeds up iterative development of a vmdb specification file: the
output of qemu-debootstrap and the apt installation additinal packages
are cached. They take up most of the time of a full run. If modifying
other parts of raspi3.yaml, this means an iteration drops from about
20 minutes to 16 seconds on my laptop.
If making changes to the cached parts, the cache tarball needs to be
deleted between runs.
The --rootfs-tarball options MUST now be used on all invocations.
2019-01-13 15:43:12 +02:00
92f08cce01
Fix: make raspi3.yaml work with current vmdb2
...
Add the kpartx step. It is now mandtory for building an image
file. (Not necessary if building on a real drive directly.)
Use only one set of tag names: boot-part and root-fs. vmdb2 has
changed so that partitions and mount points share the same tag name
space: there's no need to have a tag for the partition and for the
mount point for that partition, anymore. As part of that, there's no
need to specify both the partition tag for the root partition, and
then also the tag for the mount point for that partition.
ea7b9bc1d3e5de362b5edf12603ee83c708ad1a1 is the commit of vmdb2 that
this works with.
2019-01-13 15:39:43 +02:00
7137dfb51f
Update vmdb2
2018-12-04 18:43:09 -06:00
bf7dc84c50
FAT labels should be uppercase
...
...and both filesystem labels should be in the same case, for consistency
2018-12-04 18:39:03 -06:00
badf0da112
Fix and update minor issues in the README
2018-12-04 18:38:09 -06:00
bb2907474a
Merge pull request #44 from praseodym/kernel-and-firmware-from-buster
...
Install kernel and firmware from Buster
2018-11-26 13:00:30 -06:00
0682611f0f
Install kernel and firmware from Buster
...
Kernel 4.18 and raspi3-firmware 1.20180619-1 are now included in Buster,
so we no longer need to install those from unstable or experimental.
2018-11-24 22:51:28 +01:00
bf61a9bcdc
Install kernel 4.18 from experimental (fixes the unreliable eth0)
2018-08-27 18:37:32 -05:00
79a32b324d
Fix the chroot step introduced in my previous commit
...
${ROOT?} does not make sense within a chroot, was causing the build to fail
2018-08-23 09:15:18 -05:00
554020cc94
Fix the cmdline.txt options to boot by label, not by partition
...
This is done in order to allow for booting from non-MMC media (i.e. USB thumbdrives)
2018-08-15 19:13:27 -05:00
1aa73ced0f
Updated vmdb2 snapshot to support labels in mkfs
2018-08-15 17:36:10 -05:00
11943e5dde
Mount filesystems by label, not partition
2018-08-14 14:11:13 -05:00
68344d79da
Merge branch 'resizerootfs'
2018-07-25 14:44:27 +08:00
34ae4edb00
Updating README
2018-07-18 17:57:39 -05:00
fc3d384e86
Merge pull request #29 from gwolf/master
...
First steps towards adopting the project
2018-07-18 16:16:03 -05:00
8f0b6f3fac
Updating references to vmdb2 to its current repository location
...
Removing also the notice looking for a new maintainer
(that is, I am adopting it ;-) )
2018-07-18 12:44:35 -05:00
e918d6d0b6
Fix resizerootfs string manipulation
...
Works with several usb devices plugged in on first boot.
2018-07-17 08:32:30 +02:00
e196f6caec
Move rpi3-resizerootfs.service further up the chain
2018-07-16 17:12:52 +02:00
47cc06fe3a
Move resizerootfs.service further up the chain
2018-07-15 13:03:32 +02:00
a2557f3720
Disable resizerootfs service timeout
2018-07-15 11:12:56 +02:00
4341e7353d
Fix resizerootfs
2018-07-15 00:03:02 +02:00
d4874ba3df
Screw parted, use sfdisk
2018-07-14 21:57:03 +02:00
9adfac6964
Fix parted invocation again
2018-07-11 06:49:42 +02:00
6e0b7a4a96
Fix parted invocation
2018-07-10 22:42:06 +02:00
dc9ced8ed8
Flexible resizerootfs
...
Catches issue #15
2018-07-10 13:11:05 +02:00
308e004bb2
README: add deprecation note
2018-06-10 18:57:36 +02:00
8ab6aa7ffc
Unify dd command with https://wiki.debian.org/RaspberryPi3
2018-04-05 20:02:36 +02:00
fa47ee98fb
Copying the keyring makes debootstrap to fail ( #13 )
...
Tested on debootstrap 1.0.93+nmu2
2018-03-26 17:51:10 +02:00
fd176e159d
README: explicitly add /usr/sbin and /sbin
...
Not all $PATHs contain the two.
fixes #8
2018-01-18 20:21:12 +01:00
78e1206670
Switch to xz compression
...
fixes #4
2018-01-08 22:47:43 +01:00
14e097a42c
Enlarge image, content has grown (building fails without this)
2018-01-08 22:46:35 +01:00
f7aaf94080
Update comment to state which kernel/firmware we need for WiFi
2018-01-08 22:46:02 +01:00
ae08f58b9b
temporarily switch away from snapshot.debian.org
...
I can’t get an image built from any of the recent snapshot.debian.org
directories. Some file always can’t be found. Will need to take a closer look
and file a bug.
2018-01-08 22:45:15 +01:00
67120477a4
move rpi3-resizerootfs to /usr/sbin/
2018-01-04 09:05:03 +01:00
96fc719bef
resizerootfs: don’t touch user-modified table, disable on first boot (Thanks mrvnr)
...
fixes #3
2018-01-04 09:04:58 +01:00
28566d7f29
document firewall rules ( #6 )
2017-12-11 08:44:34 +01:00
82d6b7ea28
Merge pull request #2 from a3nm/master
...
Document apt-get workaround
2017-10-25 12:37:43 +02:00
70ddd530f4
simplify environment invocation
...
https://github.com/Debian/raspi3-image-spec/pull/2#discussion_r146799419
2017-10-25 11:41:54 +02:00
dff4a40534
clean the environment but keep important variables
...
building the image fails otherwise (encoding issues, missing PATH,
etc.); took invocation from https://unix.stackexchange.com/a/49057
2017-10-25 11:17:50 +02:00
5d5fca8794
point out that bugs can cause unbootable images
2017-10-25 11:11:50 +02:00
b3e44ee51e
add umask and env -i workaround for vmdb2#26
2017-10-25 11:11:30 +02:00
Daniel Moran