Ubuntu has release kernel version "6.2.0-32-generic #32~22.04.1-Ubuntu
SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64
GNU/Linux" which has successfully resolved this defect case.
One of the Samba maintainers told me I should check if SMB 1.0 protocol
was purposely removed from
Public bug reported:
My Xubuntu system this weekend alerted me to a new kernel update being
available. The following versions are the existing/working version:
linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
And the updated/not working version:
linux-image-6.2.0-31-generic
The solution to this issue was documented in my #3 comment. The
misleading error messages coming from Linux were indicating that it was
time to fresh reformat the MP3 player and start over. Once done, no
issues.
This defect report may be close. Thank you.
--
You received this bug notification
I decided to have the Sony WalkMan reformat itself. MTP over USB working
much better now.
Very odd that I could play MP3 recordings with the player without
issues... only issues was removing files, copying new files to it.
The thing that tipped me off to try reformatting the device with itself
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
@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 Kernel
Packages, which is subscribed to linux in 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"
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 Kernel
Packages, which is
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 Kernel
Packages, which is subscribed to linux in
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display
There does not appear to be i386 files in that directory.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display
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
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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656605
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
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
... 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 Kernel
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
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
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until
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
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.
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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: "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 Kernel
Packages, which is subscribed to linux-meta in 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 Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** 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 Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** 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 Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** 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 Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
Public bug reported:
Today I did our first production 14.04 to 16.04 LTS server upgrade. I
had done so a couple of times successfully on test server machines. Upon
booting up on the 16.04 system/kernel, after the Grub screen the server
console screen is completely blank.
Someone suggested using
I just reloaded the production drive in the test machine with the GA
release of Xubuntu 14.04 x64 and find that the USB mouse is working as
expected.
I note the mention of nvidia drivers in #11. I had not added those what
I found USB ports dead. I need to install those. I had opened a bug
report
I last loaded the test ThinkPad T540p with a Xubuntu 14.04 20140225 Beta
1 ISO. New HDD today, thus new Xubuntu ISO, and I cannot get the USB
mouse to light up (optical mouse) in either USB port on each side of the
unit.
How can I help test to resolve this critical bug?
--
You received this bug
I put the former drive back in. It appears to have only one kernel
update older than current, and the USB mouse works fine. Packages on
that drive are as follows:
$ dpkg -l | grep linux-
ii linux-firmware1.125
all Firmware for
A while ago I upgraded from Ubuntu Server 10.04 LTS to 12.04 LTS, and
the USB HDD is properly attached automatically to a USB2 controller
rather than USB 1.1. I no longer need the script posted in #23 to wake
up the USB subsystem back to reality.
--
You received this bug notification because you
39 matches
Mail list logo
