** Changed in: plymouth (Ubuntu Lucid)
Status: Triaged => Won't Fix
** Changed in: linux-ec2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: Triaged => Invalid
** Changed in: cloud-init (Ubuntu Lucid)
Status: Triaged => Won't Fix
Adolfo,
Lucid has *not* reached end of life. The desktop did, but not the server.
Please be aware, and if you've changed other things similarly, please put
them back also.
https://wiki.ubuntu.com/Releases
** Also affects: plymouth (Ubuntu Lucid)
Importance: Undecided
Status: New
(I'm untargetting Lucid as it has reached EOL.)
** No longer affects: cloud-init (Ubuntu Lucid)
** No longer affects: linux-ec2 (Ubuntu Lucid)
** No longer affects: plymouth (Ubuntu Lucid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
@Emmanuel,
I don't expect to fix this in grub-legacy-ec2. It onliy affects lucid era
kernels, as far as I know/remember.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/682831
T
@scott: hit by this bug today any ideas when this will be fixed in
legacy-grub-ec2 ?
in the meantime. for others running an Ubuntu 10.04.* domU with the
linux-image-ec2 kernel and getting no console, the proper way to fix
this is to add
console=hvc0 xencons=hvc0
in /boot/grub/menu.lst in the kop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-ec2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: cloud-init (Ubuntu Lucid)
Status: New => Triaged
** Changed in: plymouth (Ubuntu Lucid)
Status: New => Triaged
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I was tracking down this exact same bug today when I came across this bug
report.
I can confirm that adding "xencons=hvc0" works around the issue on Lucid based
builds, thanks Scott!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clo
There is, in my opinion, a real bug here in plymouth. However, it can
be easily worked around by adding 'xencons=hvc0 console=hvc0' as I've
done now in [1] (a slight fix at rev 211 also). I think this can be
further fixed in legacy-grub-ec2 in lucid by adding the appropriate
xencons to the defaul
I just tested with the most recent lucid build, and the adding of
'xencons' param in the post-build fixups fixes this problem
# us-east-1 ami-f8b44591 canonical ebs/ubuntu-lucid-daily-i386-server-20101220
# us-east-1 aki-407d9529 amazon pv-grub-hd0-V1.01-i386.gz
$ ec2-run-instances ami-f8b44591 --
10 matches
Mail list logo
