[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2021-01-25 Thread vmc
This bug is still failing per current ISO dated 01/25/2021 booting from Kubuntu 21.04: $ sudo dmesg|grep failed [0.538632] Initramfs unpacking failed: Decoding failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2021-01-25 Thread vmc
The corrected ISO date is this: hirsute-desktop-amd64.iso 2021-01-26 05:51 from Kubuntu daily-live current. It still fails. -- 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/1835660

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2021-01-25 Thread vmc
This bug failure is still present as of current ISO dated 01/25/2021 using Kubuntu: [code]vmc@01-25-21:~$ sudo dmesg|grep failed [0.538632] Initramfs unpacking failed: Decoding failed[/code] -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-05 Thread vmc
Ye, I tried X,K,U,b ubuntu, and all boot without errors. I also prefer gzip. I had the reverse though. I find gzip is faster than lz4, and I'm using nvme for boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-10 Thread vmc
In post#14, I showed how my gzip booted faster. "We currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system." If 'harmless', then why the error in the first place? Something is causing it. Sticking the error in the sand is NOT

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-03-24 Thread vmc
Xubuntu 20.04 failed: $ dmesg |grep failed [0.456889] Initramfs unpacking failed: Decoding failed [5.838496] thermal thermal_zone2: failed to read out thermal zone (-61) [6.053231] [drm] failed to retrieve link info, disabling eDP Then issued the following: $ sudo update-initramfs

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-03-20 Thread vmc
My Secure Boot is always off, and all three U, X, Kubuntu have the error, as of yesterdays ISO. -- 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/1835660 Title: initramfs unpacking failed

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-10-13 Thread vmc
Boot up is actually faster after fix: dmesg, boot-time b4-fix $ dmesg|grep Decoding [0.461068] Initramfs unpacking failed: Decoding failed $ systemd-analyze Startup finished in 14.140s (firmware) + 4.226s (loader) + 6.079s (kernel) + 17.270s (userspace) = 41.717s graphical.target

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-10-13 Thread vmc
Did you read the part: "initramfs unpacking failed: Decoding failed". So what's the point if its faster and fails? If you have splash on, you won't see the error message. use dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-10-12 Thread vmc
as of 10/12/2019 eoan 19.10, Ubuntu, Lubuntu, Xubuntu still have this issue. What I do to "fix" it is change: COMPRESS=lz4, to COMPRESS=gzip, @: /etc/initramfs-tools/initramfs.conf, then sudo update-initramfs -u. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-18 Thread vmc
"initramfs unpacking failed: Decoding failed" message still fails. Using: eoan ubuntu-budgie, ISO dated 7/18/19 -- 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/1835660 Title: initramfs

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-11 Thread vmc
As of today's ISO (7/11) installed, there is no "initramfs unpacking failed: Decoding failed" message. It appears solved. -- 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/1835660 Title:

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-11 Thread vmc
I also noticed on July 3rd thereabouts, was a change for 'lz4', that was approved. Not sure if I had this error then. I just started noticing around July 7th. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2019-07-11 Thread vmc
There are two messages that appear, the first is "initramfs unpacking failed: Decoding failed", right afterwards the partitions is clean message appears. So, yes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)

2019-07-08 Thread vmc
Still fails: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan === thermald: Installed: 1.8.0-1ubuntu1 Candidate: 1.8.0-1ubuntu1 Version table: *** 1.8.0-1ubuntu1 500 500

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2019-03-06 Thread vmc
I get the pcie errors on all X,L,K Ubuntu's disco 19.04 [ 3056.549121] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [ 3056.549136] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 3056.549147] pcieport :00:1c.0:

[Kernel-packages] [Bug 1798880] Re: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

2019-03-03 Thread vmc
cat /proc/version Linux version 4.19.0-13-generic (buildd@lcy01-amd64-027) (gcc version 8.2.1 20190204 (Ubuntu 8.2.0-17ubuntu6)) #14-Ubuntu SMP Thu Feb 7 21:51:25 UTC 2019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

2016-10-17 Thread vmc
*** This bug is a duplicate of bug 1629714 *** https://bugs.launchpad.net/bugs/1629714 ** This bug has been marked a duplicate of bug 1629714 scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active -- You received this bug notification because you

[Kernel-packages] [Bug 1629714] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-1:1.0) is not active

2016-10-13 Thread vmc
Here's a kernel bug report on this: https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg201349.html -- 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/1629714 Title: scsi

[Kernel-packages] [Bug 1269296] Re: Linux 3.13.0-3-generic doesn't boot [HP Compaq Mini 700EW]

2014-01-16 Thread vmc
Not sure if I have the same problem, but linux-generic 3.13.0-3.18 stops booting right after the kernel message: Switched to clocksource tsc If I add nomodeset to the linux string it boots but with reduced solution, even after I install nvidia drivers. Downgrading back to 3.12.0-7, everything