This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/682831
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** 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
Bugs, which is subscribed to Ubu
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/682831
Title:
lost console
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/682831
Title:
l
** 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
Bugs, which
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
Bugs, which is subscribed to Ubuntu.
ht
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 --
Oh, one more note, it seems that
drivers/xen/console/console.c:
# * Modes:
# * 'xencons=off' [XC_OFF]: Console is disabled.
# * 'xencons=tty' [XC_TTY]: Console attached to '/dev/tty[0-9]+'.
# * 'xencons=ttyS' [XC_SERIAL]: Console attached to '/dev/ttyS[0-9]+'.
# * 'xencons=xvc' [XC_XVC]: Console a
In maverick, I see
$ egrep "(console.*enabled|Kernel command|console.*installed|Linux ver)"
maverick-console.txt
[0.00] Linux version 2.6.35-23-virtual (bui...@roseapple) (gcc version
4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #41-Ubuntu SMP Wed Nov 24 10:53:14 UTC
2010 (Ubuntu 2.6.35-23.41
In lucid, I see:
$ egrep "(console.*enabled|Kernel command|console.*installed|Linux ver)"
lucid-console.txt
[0.00] Linux version 2.6.32-310-ec2 (bui...@palmer) (gcc version 4.4.3
(Ubuntu 4.4.3-4ubuntu5) ) #21-Ubuntu SMP Mon Nov 29 19:50:24 UTC 2010 (Ubuntu
2.6.32-310.21-ec2 2.6.32.24+drm
I just commited the change to the build process at
http://bazaar.launchpad.net/%7Eubuntu-on-ec2/vmbuilder/automated-ec2-builds/revision/210
.
What that does is make a change to lucid /boot/grub/menu.lst entries so that
they have 'xencons=hvc0'.
A couple things to point out
a.) I'm only doing t
** Branch linked: lp:~ubuntu-on-ec2/vmbuilder/automated-ec2-builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/682831
Title:
lost console output early in boot
--
ubuntu-bugs mailing list
ubuntu-
at this point I would really like to get jjohansen or smb's thoughts on
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/682831
Title:
lost console output early in boot
--
ubuntu-bugs mailing l
OK. so I realize how I incorrectly read the comments in
drivers/xen/console/console.c. I had assumed that you should pass
'xencons=hvc' and it would allocate one hvcX device. Instead, I tried:
xencons=hvc0 console=hvc0 and I see:
[0.00] Kernel command line: root=LABEL=uec-rootfs ro xenco
I did some more poking, and found a lot of good information. I noticed in
drivers/xen/console/console.c (kernel) the following comments:
# * Modes:
# * 'xencons=off' [XC_OFF]: Console is disabled.
# * 'xencons=tty' [XC_TTY]: Console attached to '/dev/tty[0-9]+'.
# * 'xencons=ttyS' [X
After doing all of the previous comment, I replaced the lucid -ec2 kernel with
maverick -virtual kernel:
$ cat /proc/cmdline
root=LABEL=uec-rootfs ro console=hvc0
$ dpkg -S /boot/vmlinuz-$(uname -r)linux-image-2.6.35-23-virtual:
/boot/vmlinuz-2.6.35-23-virtual
All data got to the console.
**
Well, I think I've eliminated plymouth as the source of the problem. I did:
a.) booted ami-2c738545 with pv-grub kernel aki-407d9529
us-east-1 ami-2c738545 canonical ebs/ubuntu-lucid-daily-i386-server-20101214
us-east-1 aki-407d9529 amazon pv-grub-hd0-V1.01-i386.gz
$ cat /proc/cmdline
root=LABEL=ue
just for reference here, the i386 log accompanies the following. Note,
that boot.log indeed had our missing data.
$ cat /var/log/boot.log
MY_HACK: line 13: /handler: Read-only file system
[0]: 1, could not write to /handler
init.real: console-setup main process (178) terminated with status 1
[1]:
** Attachment added: "i386 log with myhack in place"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/682831/+attachment/1767206/+files/console-i386_new.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "amd64 console log with myhack in place"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/682831/+attachment/1767205/+files/console-amd64_new.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
attached init wrapper
** Attachment added: "myhack-init replacement/wrapper for /sbin/init"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/682831/+attachment/1767204/+files/myhack-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've nominated this bug for lucid.
We've got all the support into lucid for booting via pv-grub, and recent daily
images have an appropriate /boot/grub/menu.lst inside and will "just work".
I've verified today that on both i386 and amd64 early console output is
lost. I've also verified that the
I'm marking 'fix released' as this is not an issue on maverick (worked
around by adding 'console=hvc0' under Bug 606373)
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Status: New => Fix Released
--
lost console output early in boot
--
lost console output early in boot
https://bugs.launchpad.net/bugs/682831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
28 matches
Mail list logo
