I just tested a Xubuntu 14.04 x64 LTS upgrade to Xubuntu 16.04. The value:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
is correct for Xubuntu. That is what causes the boot process to have the GUI
screen rather than text console messages.
So note to the upgrade package maintainers... it needs to be
Correct, it doesn't sound like this is a kernel bug, so I added the
upgrade package.
** Also affects: release-upgrader-apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux
@Joseph, Do you mean incomplete based on this bug report needing to
morph into an issue against the 14.04 to 16.04 LTS upgrade process?
How may I assist?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have now built brand new servers with Ubuntu Server 16.04 x64. The
initial state of the /etc/default/grub file is:
GRUB_CMDLINE_LINUX_DEFAULT=""
Must be that edit was missed in the LTS upgrade from 14.04 to 16.04.
I have modified our LTS upgraded 16.04 servers to this setting.
--
You
Excellent find, Joseph!
Here are the lines of interest from our /etc/default/grub files:
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
This may have been introduced by commit 4ae5bd9. However, I'd first
like to see if this is expected and not a bug.
Can you perform the following:
edit /etc/default/grub and remove quiet and splash from the line:
GRUB_CMDLINE_LINUX_DEFAULT
So the line will be:
GRUB_CMDLINE_LINUX_DEFAULT=""
Correct, 3.13.0-9.29 boots with appropriate "Ubuntu " text, then
lands at a busybox type interface.
So looks like something happened bad in-between there.
Purged back off. Ready for the next test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There was never a 3.14 based Ubuntu kernel released, so we may be at the
two bisectable versions.
Can you confirm 3.13.0-9.29 is goood:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/5589423
If 3.13.0-9.29 is good, I can bisect between 3.13.0-9.29 and 3.15.0-0.1
and
Looks like build 3.15.0-0.1 still has the issue. It also would not boot
correctly... landed the server at a busybox type interface.
Purged back off.
So, into the 3.14's next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I built a 3.15.0-0.1 kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1656605/
Can you give this kernel a test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Build 3.16.0-0.1 has the reported defect. Purged back off.
Next build to evaluate, please...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub
I built a 64 bit kernel. The 32 bit one is there now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted and
pressing
There does not appear to be i386 files in that directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted and
pressing
I built a 3.16.0-0.1 kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1656605/
Can you give this kernel a test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Build 3.16.0-23 has the reported defect. Purged back off.
Next build to evaluate, please...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen
Can you test 3.16.0-23.31:
https://launchpad.net/ubuntu/+source/linux/3.16.0-23.31/+build/6478451
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub
Yes that v3.13.0-108.155 kernel build boots up with the expected Ubuntu
splashscreen. Though would not boot up all the way cleanly... went
into busybox.
Received v4.4.0-62 via Xenial updates, so purging off both the
v3.13.0-108.155 and v4.4.0-59 kernel versions.
So yes, somewhere between
It looks like I'll have to build some kernels in between 3.13 and 3.19.
Just as a confirmation, can you ensure the latest Trusty kernel does not
have the bug:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11845243
--
You received this bug notification because you are
The 3.19.0-80 kernel build still has the defect. I purged it back off
our server. Booted back to 4.4.0-59.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display
Can you test the following 3.19 based kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11849331
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server
Sorry... defect is yet persisting with the 4.2.0-16.19 kernel build. I
purged it back off our server. Booted back to 4.4.0-59.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server
Correct, the v4.4-wily kernel is an upstream version of the kernel with
no Ubuntu customization. That is the reason we need to go back in time
and test the older Ubuntu kernels to find the specific version when the
bug was introduced. That will allow us to bisect and find the exact
commit that
Tested 4.2.0-19.23 kernel, same issue. Purging it off.
So, quick question... between "v4.4-wily" which worked and "linux-
image-4.4.0-1-generic", is the difference there the Ubuntu
customizations applied to the official Kernel build? Thus is something
in how Ubuntu customizes the Kernel source
Can you test the 4.2.0-19.23 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/8287821
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console
Same defect with both the https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11923303 and
https://launchpad.net/ubuntu/+source/linux/4.3.0-7.18 kernel builds.
I am back booted to linux-image-4.4.0-59-generic and all other kernels
have been purged back off the server.
Please
Yes, the top entry in GRUB is the one to boot.
Sorry about posting the amd64 link for Yakkety. The i386 link is:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11923303
Now that we know the bug is in the earlies 4.4 Ubuntu based kernel, it would be
good to know if it
... and I was not suppose to be booting from a lower entry than the top
entry for the particular kernel build I am testing, was I? Top has no
suffix text, next one I believe was labeled "Upstart" and third was
"Recovery".
--
You received this bug notification because you are a member of Ubuntu
Wowsers... this bug is already present in linux-image-4.4.0-1-generic!
So was linux-image-4.4.0-1-generic the very next version after
v4.4-wily? Or do I need to test some additional versions?
The URL link you posted for the Yakkey(16.10) kernel leads directly to
amd64 specific... this system is
Noted you want me to test the Yakkey(16.10) kernel specified.
About the Xenial kernels... I am thinking to walk the version list back
from 4.4.0-59 to land on one that does not have the error. Then post the
last one that was working, and the first one with the noted defect. Does
that sound like a
No need to test the 4.5-rc1 kernel. Because v4.4-wily is good, we can
not bisect between 4.4 and 4.5-rc1. It also means that the bug was
introduced by one of the 4.4 stable updates, or by an Ubuntu specific
SAUCE patch.
We should bisect between the 4.4 Ubuntu kernels. However, it would be good
OK, I got the first kernel (v4.4-wily) validated that it works properly.
I IPL'ed back to the 4.4.0-59 to validate the problem had not suddenly
vanished, still there.
So:
4.4.0-59 bad / has the issue
v4.4-wily working / no issue
Do you still need me to install / test / validate the v4.5-rc1-wily
Can you also confirm the bug does indeed happen with the upstream 4.4 final
kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
That will tell us if the bug was introduced in 4.4 or one of the 4.4
stable updates. It will also tell us that 4.4 final is the starting
kernel for the
Excellent, first try lucky. I downloaded all three requested kernel
packages. Started with the:
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
And this version already corrects the entire issue seen with the
4.4.0-59-generic official 16.04 version.
Here is the console
Thanks for the update. We can perform a "Reverse" bisect to identify the
commit that fixes the bug in v4.10-rc4. We first need to identify the
last bad kernel and first good one.
Can you test the following kernels:
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.8-rc1:
Question: So is there hope of getting this fixed in the default kernel
version for the 16.04 release, or is it going to be addressed only with
the "Ubuntu 16.04.2 LTS Point Release Coming On Feb 2 With Linux Kernel
4.8" newer kernel?
No... Linux Kernel 4.4 vs Linux Kernel 4.10, so that is not
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted and
Yes, working perfectly! Trying to remember how I set tags. Here is the
output of applying the test kernel:
mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay/v4.10-rc4$
sudo dpkg -i
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Ah, a notable difference between the hardware spec of the test servers
and the real servers:
The test server is on a test machine which has a graphics board
installed in it: EVGA e-GeForce 8400 GS Graphics Card - 512 MB RAM
512-P3-1301-KR
The real servers are using the on-board Intel graphics.
A friend advised me to check two more outputs between a 14.04 server and
16.04 impacted server. Attaching the following additional outputs:
mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay$
cat /proc/consoles > consoles.log
** Attachment added: "cmdline.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+attachment/4804629/+files/cmdline.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted and
pressing
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804496/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804497/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804494/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804495/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "linux-images.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804498/+files/linux-images.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
48 matches
Mail list logo
