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

2020-10-24 Thread Gon Solo
Has this to do with BLK_DEV_RAM being compiled as a module? From
init/initramfs.c:

>   if (IS_ENABLED(CONFIG_BLK_DEV_RAM))
>printk(KERN_INFO "Trying to unpack rootfs image as 
> initramfs...\n");
>else
>printk(KERN_INFO "Unpacking initramfs...\n");

>err = unpack_to_rootfs((char *)initrd_start, initrd_end - 
> initrd_start);
>if (err) {
>#ifdef CONFIG_BLK_DEV_RAM
>populate_initrd_image(err);
>#else
>printk(KERN_EMERG "Initramfs unpacking failed: %s\n", err);
>#endif

So the IS_ENABLED line is true while the ifdef CONFIG_BLK_DEV_RAM line
seems to evaluate to false.

-- 
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

Status in OEM Priority Project:
  New
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1994487] [NEW] NVIDIA vulkaninfo failing under wayland

2022-10-26 Thread Gon Solo
Public bug reported:

I got Wayland working with NVIDIA drivers by tweaking GRUB_CMDLINE_LINUX
and 61-gdm.rules.

vulkaninfo is failing with:

WARNING: [Loader Message] Code 0 : loader_icd_scan: Can not find 'ICD' object 
in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json.  Skipping ICD JSON
ERROR while creating surface for extension VK_KHR_wayland_surface : 
./vulkaninfo/vulkaninfo.h:237:vkGetPhysicalDeviceSurfacePresentModesKHR failed 
with ERROR_INITIALIZATION_FAILED
ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR 
failed with ERROR_INITIALIZATION_FAILED

Is nvidia_layers.json misplaced in /usr/share/vulkan/icd.d? It only
mentions libGLX_nvidia.so.0.

Similarly nvidia_icd.json has a libGLX_nvidia.so.0 in it, whereas intel or 
radeon have
"/usr/lib/x86_64-linux-gnu/libvulkan_intel.so" and 
"/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so".

** Affects: nvidia-graphics-drivers-515 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: nvidia vulkan wayland

** Tags added: nvidia vulkan wayland

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.
https://bugs.launchpad.net/bugs/1994487

Title:
  NVIDIA vulkaninfo failing under wayland

Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  I got Wayland working with NVIDIA drivers by tweaking
  GRUB_CMDLINE_LINUX and 61-gdm.rules.

  vulkaninfo is failing with:

  WARNING: [Loader Message] Code 0 : loader_icd_scan: Can not find 'ICD' object 
in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json.  Skipping ICD JSON
  ERROR while creating surface for extension VK_KHR_wayland_surface : 
./vulkaninfo/vulkaninfo.h:237:vkGetPhysicalDeviceSurfacePresentModesKHR failed 
with ERROR_INITIALIZATION_FAILED
  ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR 
failed with ERROR_INITIALIZATION_FAILED

  Is nvidia_layers.json misplaced in /usr/share/vulkan/icd.d? It only
  mentions libGLX_nvidia.so.0.

  Similarly nvidia_icd.json has a libGLX_nvidia.so.0 in it, whereas intel or 
radeon have
  "/usr/lib/x86_64-linux-gnu/libvulkan_intel.so" and 
  "/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1994487/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1994487] Re: NVIDIA vulkaninfo failing under wayland

2022-12-05 Thread Gon Solo
This is fixed in libnvidia-gl-525.

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.
https://bugs.launchpad.net/bugs/1994487

Title:
  NVIDIA vulkaninfo failing under wayland

Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released

Bug description:
  I got Wayland working with NVIDIA drivers by tweaking
  GRUB_CMDLINE_LINUX and 61-gdm.rules.

  vulkaninfo is failing with:

  WARNING: [Loader Message] Code 0 : loader_icd_scan: Can not find 'ICD' object 
in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json.  Skipping ICD JSON
  ERROR while creating surface for extension VK_KHR_wayland_surface : 
./vulkaninfo/vulkaninfo.h:237:vkGetPhysicalDeviceSurfacePresentModesKHR failed 
with ERROR_INITIALIZATION_FAILED
  ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR 
failed with ERROR_INITIALIZATION_FAILED

  Is nvidia_layers.json misplaced in /usr/share/vulkan/icd.d? It only
  mentions libGLX_nvidia.so.0.

  Similarly nvidia_icd.json has a libGLX_nvidia.so.0 in it, whereas intel or 
radeon have
  "/usr/lib/x86_64-linux-gnu/libvulkan_intel.so" and 
  "/usr/lib/x86_64-linux-gnu/libvulkan_radeon.so".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1994487/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2027996] [NEW] vulkaninfo fails with libnvidia-gl-535 under Wayland

2023-07-17 Thread Gon Solo
Public bug reported:

vulkaninfo under Wayland fails with:

WARNING: [Loader Message] Code 0 : loader_parse_icd_manifest: Can not find 
'ICD' object in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json. 
Skipping ICD JSON
ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR 
failed with ERROR_INITIALIZATION_FAILED

Removing nvidia_layers.json gets rid of the warning but not the error:

ERROR at
./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR
failed with ERROR_INITIALIZATION_FAILED

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2027996

Title:
  vulkaninfo fails with libnvidia-gl-535 under Wayland

Status in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  vulkaninfo under Wayland fails with:

  WARNING: [Loader Message] Code 0 : loader_parse_icd_manifest: Can not find 
'ICD' object in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json. 
Skipping ICD JSON
  ERROR at ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR 
failed with ERROR_INITIALIZATION_FAILED

  Removing nvidia_layers.json gets rid of the warning but not the error:

  ERROR at
  ./vulkaninfo/vulkaninfo.h:1472:vkGetPhysicalDeviceSurfaceSupportKHR
  failed with ERROR_INITIALIZATION_FAILED

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2027996/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp