Issue was that os.snap (containing initrd.img) was being downloaded in
self.sourcedir + 'os.snap'.
Meaning the os.snap was being downloaded (and cached) in the kernel source dir.
Which I didn't clean and which "snapcraft clean" didn't clean either.
I guess this is not the correct behaviour.
So
Ah OK, right, I need to update my kernel snap.
It's been some time since I last built it (using snapcraft).
I'll rebuild it, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579767
Title:
the initrd should be shipped in the kernel snap, you need an updated initrd and
you need the squashfs module inside to actually be able to mount the snaps.
best would be if you used the snapcraft kernel plugin to build your kernel
snap, it will pull the latest initrd that is available at build
this sounds like you are using a very outdated initrd rather
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579767
Title:
udf does not support using aarch64 kernel snap with armhf 32 bits user
Maybe I should open a new bug but now I'm able to generate paros.img image with
ubuntu-device-flash.
But then when I flash it and boot it I get issues from the init of initrd.
initrd cannot mount the gadget/kernel/core snaps because it searches for them
in the wrong paths.
It searches at
The snappy_* vars would be similar to this ones:
snappy_boot=if test "${snappy_mode}" = "try"; then if test
"${snappy_trial_boot}" = "1"; then setenv snappy_os "${snappy_good_os}"; setenv
snappy_kernel "${snappy_good_kernel}"; saveenv; else setenv snappy_trial_boot
1; saveenv; fi; fi; run
not yet, no, i'm working on a porting guide that will cover these
basics, for now just do what i described above (the loading needs to be
adapted for your system, all snappy_* vars can be taken 1:1 and you need
to get the root= variable populated properly)
--
You received this bug notification
Allright, I fixed the linewraps issues and now the image is generated o/
Thanks!
Ok I see I need to put some snappy_* variables, is this documented somewhere?
What variables to use, and what they are supposed to contain?
--
You received this bug notification because you are a member of Ubuntu
hmm ... you also want whats in "mmcargs" to set the right root=
also what mkenvimage do you use (your u-boot build should have created
one, it is best to use that over something from the archive)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
also: the error you get above looks like there are line-wraps where they
shouldn't be in your uboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579767
Title:
udf does not support using
aha, so you are not having any of teh required snappy_* vars set at all
...
see http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-
systems/view/head:/pi2/boot-assets/uboot.env.in
you want the "loadfiles" bits (adjusted for your system (specifically the fdt
loading part i guess))
as well
Hmm the uboot.txt file got corrupted somehow, here is another try:
fallen@fallen-ThinkPad-X260:~/dev/snappy/paros/snappy_image/u-boot/tools$
./mkenvimage -r -s 131072 -o uboot.env uboot.txt
fallen@fallen-ThinkPad-X260:~/dev/snappy/paros/snappy_image/u-boot/tools$
uboot-go uboot.env print
panic:
fallen@fallen-ThinkPad-X260:~/dev/snappy/paros/snappy_image/u-boot/tools$ cat
uboot.txt
arch=arm
baudrate=115200
board=paros
board_name=paros
boot_a_script=load 29882{devtype} 29882{devnum}:29882{bootpart}
29882{scriptaddr}
29882{prefix}29882{script}; source 29882{scriptaddr}
well, the CRC error is gone, the remaining error looks more like it is
content related, how does your uboot.txt file look like ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579767
Title:
udf
I recompiled my u-boot with the mentioned config changes, then I regenerated my
uboot.env with -r -s 131072.
Here is what I get :
Unmounting...
panic: runtime error: index out of range
goroutine 1 [running, locked to thread]:
panic(0x94f960, 0xc82000e0c0)
the uboot.env file needs to be exactly 128k and redundant ... the
mkenvimage command you use to create must be:
mkenvimage -r -s 131072 -o uboot.env uboot.env.in
note that you need to adjust your u-boot build config similar to
http://paste.ubuntu.com/16199863/ in case your u-boot binary uses a
Re-packing the kernel snap editing the metadata gives a CRC error:
fallen@fallen-ThinkPad-X260:~/dev/packages/images$ sudo
./ubuntu-device-flash --verbose core 16 -o paros.img --channel edge
--gadget ../paros_gadget/paros_1.0_all.snap --kernel
../paros_kernel/paros-kernel_3.10.67_armhf.snap --os
The CRC error was related to one of the flags of mkenvimage (-r)
./mkenvimage -s 2600 -o uboot.env $CWD/uboot.txt
But running mkenvimage with -r and re-running the whole process of the
kernel snap build with modified metadata now gives another error:
Unmounting...
panic: runtime error: index
you could try to cheat and just re-pack the kernel snap with
"architectures: armhf" in the snap.yaml (using unsquashfs, changing
meta/snap.yaml in the unpacked binary and running "snapcraft snap
$path_to_unpack_dir"), then ubuntu-device-flash should not complain
anymore
--
You received this bug
19 matches
Mail list logo
