I am seeing this bug in 17.10. If I carry out a minimal install with no
packages selected at the final stage, I see a blank screen on boot.
The first time I saw this I did a hard reset and was presented with a
boot menu. I presume this is some sort of failsafe behaviour in the
event of a failed
Still happends on 17.04 (minimal)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still hands off to blank tty7 on non-Server command-line-only
systems and some Server systems
This bug happens to me every time in Xenial (none in Trusty) when
installing a server using minimal ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still hands off to blank
Note on comment #47 and the oem-config bug: That was found to be
unrelated, and a fix for it has already been released.
As for this bug, it appears to have gone away. I tested a minimal Raring
install, and even through the GRUB boot options are the default quiet
splash, it does correctly switch
I am seeing this on Ubuntu-12.04-server-amd64 installs on both raw
hardware (standard Intel server platforms) and also when installing in
kvm/qemu. I am wondering if this is the cause of oem-config crashing on
the ubuntu server installs (lp:1180880). More testing to see if they
are related.
--
I found the perfect fix for this bug. I wiped my disk and installed a
different (not Ubuntu) distro. I am much happier now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still
This looks like it affects daily spins of Quantal too (as of today's date).
Using Quantal Server amd64 it boots into vt7.
There's a crazy if .. else block in /etc/grub.d/10_linux that sets
linux_gfx_mode=text or linux_gfx_mode=grub which is possibly setting
keep instead of text but I'm not sure
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still hands off to blank tty7 on non-Server command-line-only
systems and some Server systems
To manage
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still hands off to blank tty7 on non-Server command-line-only
systems and some Server systems
To manage
Kind of unbelievable that this is still unfixed and still marked low
priority. Can we at least have an explanation of what's broken in
plymouth that makes it impossible to apply the suggested fix? I can look
at fixing plymouth if that's the problem.
--
You received this bug notification because
It looks like this gets added automatically if the splash option is
specified in /etc/default/grub. It appears this option is there by
default, but is removed at some point when installing from the server
cd. However that happens on the server probably needs to behave the
same on the alternate
The vt.handoff kernel param shouldn't be there in the first place. See
my comment above. And I don't see why this would be an uncommon
installation. It's the only way I know of to install a command line
system that's not a server.
--
You received this bug notification because you are a member of
I'm still getting this with the 11.11 beta2. Why is this considered
low importance? It makes the system unusable and can take a while to
figure out, even for someone who knows what they're doing. It's
especially pernicious in a VirtualBox VM, where ctl-alt-F1 doesn't do
what you expect. Please
@Jim Rees
This does not speak to the question of this bug's importance, but please note
that Alt+F1 is sufficient (and more appropriate) for switching from a virtual
terminal that does not have X11 running on it, and Alt+F1 will typically behave
as expected with VirtualBox and other
The real bug here is not so much that grub is asking the kernel to
switch to vt7 when there is no splash. The real bug is that grub is
requesting a vt switch at all. Grub has no business making this request
because it has no way of knowing whether there is anything on vt7.
The way this should
Jim, I agree that having grub switch the VT rather than the program
needing same is rather cart-before-horse-ish. It does have the advantage
of happening very early in the boot process, however (even before the
kernel/initrd are loaded), and I suspect the rationale for doing things
this way is
Firstly skunk's fix works for me.
Second, this is critical. Quite how many people realise you can do an
Alt+F1 to gain access to their systems I don't know, but those that do
not and have no remote access will be reinstalling and probably ending
up in the same hole.
My platform: 64-but Win7Pro
Skunk,
Awesome... Works Great
Jeff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830
Title:
grub2 still hands off to blank tty7 on non-Server command-line-only
systems and some Server
I've dug into this issue a bit. I don't think there's much use in
distinguishing between the various Ubuntu flavors here; it all comes
down to this bit in /etc/grub.d/10_linux:
for word in $GRUB_CMDLINE_LINUX_DEFAULT; do
if [ $word = splash ]; then
I am able to reproduce this bug on Natty i386 Server by using VMware
Easy Install (in VMware Workstation 7.1.4 build-385536 on a Natty amd64
host). When I install Natty i386 Server manually (as I had always done
in the past) on the same virtual machine, this bug does not occur. I am
not sure what
20 matches
Mail list logo
