Natty is no more a supported version; and grub legacy upstream is also
stopped, only receiving possible random fixes locally
** Changed in: grub (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
The permanent fix for this is likely in PV-GRUB. See:
https://patchwork.kernel.org/patch/727511/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot on t1.micro in
Verified fixed.
us-east-1 ami-0e6b9b67 canonical ebs/ubuntu-natty-daily-i386-server-20110207
$ uname -a
Linux ip-10-112-58-95 2.6.38-2-virtual #29-Ubuntu SMP Fri Feb 4 16:24:23 UTC
2011 i686 i686 i386 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package linux - 2.6.38-2.29
---
linux (2.6.38-2.29) natty; urgency=low
[ Andy Whitcroft ]
* rebase to 1f0324caefd39985e9fe052fac97da31694db31e
* [Config] updateconfigs following rebase to
1f0324caefd39985e9fe052fac97da31694db31e
* rebase to 70d1f
** Tags added: kernel-key
** Tags removed: kernel-uncat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot on t1.micro in arch i386
--
ubuntu-bugs mailing list
No, we go back to 0x10 (5 zeros ;)) for start and alignment. I have
tried in the test environment with both align and start being 0x100
(16M) which did *not* work when using pv-grub for the boot process. At
that point I wondered whether this is kernel code itself or something
going along wi
right. Stefan is going to move that back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot on t1.micro in arch i386
--
ubuntu-bugs mailing list
ubuntu-bugs@li
We use:
CONFIG_PHYSICAL_START=0x100
CONFIG_PHYSICAL_ALIGN=0x100
It sounds like that works for you too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot
> What is CONFIG_PHYSICAL_ALIGN?
$ egrep "(CONFIG_RELOCATABLE|CONFIG_PHYSICAL)" /boot/config-2.6.38-1-virtual
CONFIG_PHYSICAL_START=0x100
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
What is CONFIG_PHYSICAL_ALIGN?
-- Sent from my Palm Pre
On Feb 1, 2011 12:16 PM, Scott Moser wrote:
On Tue, 1 Feb 2011, Matt Wilson wrote:
> Are you using CONFIG_RELOCATABLE=y for your kernels? If so,
> CONFIG_PHYSICAL_START should not be a factor.
$ egrep "(
On Tue, 1 Feb 2011, Matt Wilson wrote:
> Are you using CONFIG_RELOCATABLE=y for your kernels? If so,
> CONFIG_PHYSICAL_START should not be a factor.
$ egrep "(CONFIG_RELOCATABLE|CONFIG_PHYSICAL_START)"
/boot/config-2.6.38-1-virtual
CONFIG_PHYSICAL_START=0x100
CONFIG_RELOCATABLE=y
$ uname -a
L
Are you using CONFIG_RELOCATABLE=y for your kernels? If so,
CONFIG_PHYSICAL_START should not be a factor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot on t1
Note about 0.97 grub... I failed to realize that the failure in pv-grub
is is limited to i386 kernels on t1.micro (ie, they boot fine in
m1.small or c1.medium).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I'm not sure if this actually occurs on "normal grub" (0.97) or only on
the grub version we get on amazon (pv-grub).
** Also affects: grub (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This is the same as I got in the test environment. Seems a silent update
of CONFIG_PHYSICAL_START to be 16M instead of 1M breaks boot with pv-
grub. I can still boot the new kernel when I boot it directly. But pv-
grub produces this dump. So for Natty, I am changing the physical start
back to 1M fo
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
You received this bug notification because you are a member of U
Well after the normal 4 minutes, console data did appear for the crashed
instance. It doesn't seem like its likely worth much, but its there.
** Attachment added: "console log of t1.micro in i386"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/710754/+attachment/1820137/+files/t1.micro
** Description changed:
$ ec2-run-instances --region us-east-1 --instance-type t1.micro --key
mykey ami-5c3fcf35
That results in instance that has no console output and is not
reachable.
Note, that under bug 686692 the amd64 on t1.micro was fixed.
ProblemType: Bug
DistroRel
18 matches
Mail list logo
