** Changed in: linux (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-1 => ubuntu-10.04-beta-2
** Summary changed:
- Can't boot initramfses
+ versatile: Can't boot initramfses
** Changed in: linux (Ubuntu Lucid)
Status: New => Triaged
--
versatile: Can't boot initramfses
https://bugs.lau
Reopening the bug since:
- the patch was just a workaround to support the RAMDISK method, but doesn't
fix initramfs support
- it actually doesn't work even with the patch :-(
qemu-system-arm -m 256 -drive file=lucid.img,media=disk -M versatilepb -cpu
cortex-a8 -kernel
linux-image-2.6.32-16-ver
@Dustin: I'd love if you could assist on this bug; to reproduce, boot:
http://ports.ubuntu.com/ubuntu-ports/dists/lucid/main/installer-armel/current/images/versatile/netboot/
with qemu-system-arm -M versatilepb -cpu cortex-a8 -m 256 -kernel
vmlinuz -initrd initrd.gz
what you will probably see is
Loic-
I'm a bit unclear on how to reproduce this bug. If you're looking for
me to assist with it, please provide a bit more information on how I
might reproduce it. If, instead, this is your own stream of conscious
notes and you're working on it, then that's fine too (I often use LP in
that way
This bug was fixed in the package linux - 2.6.32-15.21
---
linux (2.6.32-15.21) lucid; urgency=low
[ Andy Whitcroft ]
* Revert "(pre-stable) drm/i915: Increase fb alignment to 64k"
* Revert "[Config] lenovo-sl-laptop -- enable"
* Revert "ubuntu: lenovo-sl-laptop -- git tip (b
** Changed in: qemu-kvm (Ubuntu Lucid)
Importance: Undecided => Low
** Changed in: qemu-kvm (Ubuntu Lucid)
Status: New => In Progress
--
Can't boot initramfses
https://bugs.launchpad.net/bugs/524893
You received this bug notification because you are a member of Ubuntu
Server Team, whic
** Changed in: linux (Ubuntu Lucid)
Milestone: lucid-alpha-3 => ubuntu-10.04-beta-1
--
Can't boot initramfses
https://bugs.launchpad.net/bugs/524893
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server
@Dave: Ack, I understand the same as you do so far. The initramfs is
the output of building the "debian-installer" packages, and it allows
setting in which format you want that file; I've put "initramfs"
explicitly and checked the code which does call cpio -H newc back then,
so I confirm that it's
The initramfs image is an optionally gzipped cpio archive (which must
have been built with cpio --format=newc in order for the kernel to
recognise it --- note this is not the default behaviour for cpio). The
filesystem is unpacked into a ramfs or similar, so there is no special
size restriction. T
@Bryan: I hope you can help me debug the qemu loader issue; I'm not
familiar with the contents of initrd versus initramfs, so I don't
understand the failure.
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) => Bryan Wu (cooloney)
** Also affects: linux (Ubuntu Lucid)
Importance: Lo
Since this works on other platforms such as imx51, I suspect it's a qemu
bug; I've sent a patch to the ubuntu kernel-team list to set
CONFIG_CRAMFS=y and bump the default ramdisk size to 64 MB as on the
other platforms as a workaround for now.
** Changed in: linux (Ubuntu)
Importance: Undecided
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
Can't boot initramfses
https://bugs.launchpad.net/bugs/524893
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mai
12 matches
Mail list logo