I still see this message on a fully up-to-date Kubuntu 19.10 system.
However the system boots fine and everything seems to be working ok.
This is apparently a non-fatal error message? It sounds pretty bad but
it still seems to have been able to load the initramfs image fine. What
does this really
I think I encountered the same thing. The screen would not wake up
though I could still ssh to the system, a lot of commands were not
working, they would just hang or do nothing. Had to resort to a hard
reset. The crash just continued to loop over and over again in the logs
4/30/17 11:11 PM
Like I said, -29 was basically renamed to -31. It HAS been fixed since -29 (now
-31)
On Tuesday, December 13, 2016 11:42:11 PM EST Scott Cowles Jacobs wrote:
> The Linux changelog people seem a bit comfused...
>
> I just received Linux 4.8.0-31.33,
> and ITS changlog says:
>
> " * Yakkety
4.8.0-29 does/did indeed include the fix but never made it out of
proposed and has since been bumped to -31
On Dec 12, 2016, Scott Cowles Jacobs <1630...@bugs.launchpad.net> wrote:
>>4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6
>
>Is "Michael Bock (michi-bock)" referring to a
4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6. It's been
pushed back to 4.8.0-31
https://people.canonical.com/~kernel/info/kernel-version-map.html
On Sunday, December 11, 2016 12:01:45 PM EST Michael Bock wrote:
> Sorry, but updating to 4.8.0-30-generic yesterday still didn't
Ubuntu 16.10 has up to the 4.8.6 patches? According to this we're still at 4.8.1
http://people.canonical.com/~kernel/info/kernel-version-map.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Because Kabylake support is new. Unless you have a Kabylake CPU this bug
doesn't really affect you other than the warning message itself from
update-initramfs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
The btusb driver is built into the kernel. There is no separate package.
On Nov 19, 2015, groby <1065...@bugs.launchpad.net> wrote:
>Bluetooth seems to work now on my computer. I made a mistake by
>installing btusb. I got the driver from a dropbox-folder somewhere in
>the internet, and
What's weird is the file names it's looking for keep changing. For mine
it used to look for "BCM920702 Bluetooth 4.0-0a5c-21e8.hcd". Then at
some point it started looking for "BCM20702A0-0a5c-21e8.hcd". Now it's
looking for "BCM20702A1-0a5c-21e8.hcd". I don't know why these keep
changing.
--
You
What is your test case? Are you sure this is the same bug?
On Friday, August 28, 2015 01:21:14 AM Aaahh Ahh wrote:
Back at it in Ubuntu 15.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
Apparently in 14.10 the .hcd file needs to be /lib/firmware/brcm.
Here is the .hcd file for the IOGEAR GBU521 (0a5c:21e8). Place it in
/lib/firmware/brcm/BCM920702 Bluetooth 4.0-0a5c-21e8.hcd (Yes including the
spaces in the file name)
modprobe -r btusb
modprobe btusb
Looks like it is
apport information
** Tags added: apport-collected
** Description changed:
After resuming from hibernate I have no network connection. This doesn't
happen with suspend, only hibernate. I'm guessing this is something with
network-manager as doing 'sudo service network-manager restart'
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275378/+files/CRDA.txt
--
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/1397501
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275381/+files/Lsusb.txt
--
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/1397501
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275382/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275377/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275383/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275379/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275380/+files/Lspci.txt
--
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/1397501
I don't know how much this will help. I had to restart network-manager
before it let me collect the data.
--
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/1397501
Title:
No network after
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275389/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275386/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275385/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275384/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275387/+files/UdevDb.txt
--
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/1397501
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1397501/+attachment/4275388/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is there a bug for the missing IDs? AFAIK 0a5c:21e8 still needs to be
added.
--
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/1065400
Title:
Support for loading Broadcom bluetooth
13.10 release images boot.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
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/1200986
Title:
Ubuntu live USB will not
** This bug is no longer a duplicate of bug 1123403
Installer is blocked by UEFI Secure Boot
--
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/1200986
Title:
Ubuntu live USB will not
I have an Asus 1015e but my UEFI settings look slightly different than
that and I still can't get it to boot a live USB stick using the 9-2
daily image. It still hangs at a blank screen even with secure boot
disabled as described in #1200986
--
You received this bug notification because you are
30 matches
Mail list logo
