unable to upgrade new kernel?

Support Update
,
1

Building module:
Cleaning build area…
make -j4 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/r8168/8.051.02/build…(ba
d exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/r8168/8.051.02/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
‘make’ -j4 KVER=6.5.0-3parrot1-amd64 KSRC=/lib/modules/6.5.0-3parrot1-amd64/build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/realtek-rtl8188eus/5.3.9~git20230101.f8ead57/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.5.0-3parrot1-amd64 (–configure):
installed linux-image-6.5.0-3parrot1-amd64 package post-installation script subprocess returned error exit status 1

1 Like
2

+1

#parrot-upgrade
Сущ:1 Index of /parrot/ lory InRelease
Сущ:2 Index of /direct/parrot/ lory-security InRelease
Сущ:3 Index of /parrot/ lory-backports InRelease
Чтение списков пакетов… Готово
Построение дерева зависимостей… Готово
Чтение информации о состоянии… Готово
Может быть обновлено 2 пакета. Запустите «apt list --upgradable» для их показа.
Настраивается пакет linux-headers-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/virtualbox-guest/6.1.22/build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.5.0-3parrot1-amd64.postinst line 11.
dpkg: ошибка при обработке пакета linux-headers-6.5.0-3parrot1-amd64 (–configure):
подпроцесс из пакета linux-headers-6.5.0-3parrot1-amd64 установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет linux-headers-amd64:
linux-headers-amd64 зависит от linux-headers-6.5.0-3parrot1-amd64 (= 6.5.3-3parrot1), однако:
Пакет linux-headers-6.5.0-3parrot1-amd64 пока не настроен.

dpkg: ошибка при обработке пакета linux-headers-amd64 (–configure):
проблемы зависимостей — оставляем не настроенным
Настраивается пакет linux-image-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/virtualbox-guest/6.1.22/build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: ошибка при обработке пакета linux-image-6.5.0-3parrot1-amd64 (–configure):
подпроцесс из пакета linux-image-6.5.0-3parrot1-amd64 установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет linux-image-amd64:
linux-image-amd64 зависит от linux-image-6.5.0-3parrot1-amd64 (= 6.5.3-3parrot1), однако:
Пакет linux-image-6.5.0-3parrot1-amd64 пока не настроен.

dpkg: ошибка при обработке пакета linux-image-amd64 (–configure):
проблемы зависимостей — оставляем не настроенным
При обработке следующих пакетов произошли ошибки:
linux-headers-6.5.0-3parrot1-amd64
linux-headers-amd64
linux-image-6.5.0-3parrot1-amd64
linux-image-amd64
failed to fix interrupted upgrades
Чтение списков пакетов… Готово
Построение дерева зависимостей… Готово
Чтение информации о состоянии… Готово
Следующий пакет устанавливался автоматически и больше не требуется:
wireguard-tools
Для его удаления используйте «sudo apt autoremove».
Обновлено 0 пакетов, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 2 пакетов не обновлено.
Установлено или удалено не до конца 4 пакетов.
После данной операции объём занятого дискового пространства возрастёт на 0 B.
Настраивается пакет linux-headers-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/virtualbox-guest/6.1.22/build…(ba
d exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/
build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.5.0-3parrot1-amd64.postinst line 11.
dpkg: ошибка при обработке пакета linux-headers-6.5.0-3parrot1-amd64 (–configure):
подпроцесс из пакета linux-headers-6.5.0-3parrot1-amd64 установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет linux-headers-amd64:
linux-headers-amd64 зависит от linux-headers-6.5.0-3parrot1-amd64 (= 6.5.3-3parrot1), однако:
Пакет linux-headers-6.5.0-3parrot1-amd64 пока не настроен.

dpkg: ошибка при обработке пакета linux-headers-amd64 (–configure):
проблемы зависимостей — оставляем не настроенным
Настраивается пакет linux-image-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/virtualbox-guest/6.1.22/build…(ba
d exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/
build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: ошибка при обработке пакета linux-image-6.5.0-3parrot1-amd64 (–configure):
подпроцесс из пакета linux-image-6.5.0-3parrot1-amd64 установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет linux-image-amd64:
linux-image-amd64 зависит от linux-image-6.5.0-3parrot1-amd64 (= 6.5.3-3parrot1), однако:
Пакет linux-image-6.5.0-3parrot1-amd64 пока не настроен.

dpkg: ошибка при обработке пакета linux-image-amd64 (–configure):
проблемы зависимостей — оставляем не настроенным
При обработке следующих пакетов произошли ошибки:
linux-headers-6.5.0-3parrot1-amd64
linux-headers-amd64
linux-image-6.5.0-3parrot1-amd64
linux-image-amd64
Scanning application launchers
Removing duplicate launchers or broken launchers
Launchers are updated
E: Sub-process /usr/bin/dpkg returned an error code (1)
failed to fix conflicts
Чтение списков пакетов… Готово
Построение дерева зависимостей… Готово
Чтение информации о состоянии… Готово
Расчёт обновлений… Готово
Следующий пакет устанавливался автоматически и больше не требуется:
wireguard-tools
Для его удаления используйте «sudo apt autoremove».
Следующие пакеты будут оставлены в неизменном виде:
gvm gvmd
Обновлено 0 пакетов, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 2 пакетов не обновлено.
Установлено или удалено не до конца 4 пакетов.
После данной операции объём занятого дискового пространства возрастёт на 0 B.
Настраивается пакет linux-headers-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/virtualbox-guest/6.1.22/build…(ba
d exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/
build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.5.0-3parrot1-amd64.postinst line 11.
dpkg: ошибка при обработке пакета linux-headers-6.5.0-3parrot1-amd64 (–configure):
подпроцесс из пакета linux-headers-6.5.0-3parrot1-amd64 установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет linux-headers-amd64:
linux-headers-amd64 зависит от linux-headers-6.5.0-3parrot1-amd64 (= 6.5.3-3parrot1), однако:
Пакет linux-headers-6.5.0-3parrot1-amd64 пока не настроен.

dpkg: ошибка при обработке пакета linux-headers-amd64 (–configure):
проблемы зависимостей — оставляем не настроенным
Настраивается пакет linux-image-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/virtualbox-guest/6.1.22/build…(ba
d exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.22/build/make.log for more information.
Sign command: /lib/modules/6.5.0-3parrot1-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j1 KERNELRELEASE=6.5.0-3parrot1-amd64 -C /lib/modules/6.5.0-3parrot1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/
build…(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-3parrot1-amd64 (x86_64)
Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: ошибка при обработке пакета linux-image-6.5.0-3parrot1-amd64 (–configure):
подпроцесс из пакета linux-image-6.5.0-3parrot1-amd64 установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет linux-image-amd64:
linux-image-amd64 зависит от linux-image-6.5.0-3parrot1-amd64 (= 6.5.3-3parrot1), однако:
Пакет linux-image-6.5.0-3parrot1-amd64 пока не настроен.

dpkg: ошибка при обработке пакета linux-image-amd64 (–configure):
проблемы зависимостей — оставляем не настроенным
При обработке следующих пакетов произошли ошибки:
linux-headers-6.5.0-3parrot1-amd64
linux-headers-amd64
linux-image-6.5.0-3parrot1-amd64
linux-image-amd64
Scanning application launchers
Removing duplicate launchers or broken launchers
Launchers are updated
E: Sub-process /usr/bin/dpkg returned an error code (1)

3

+2. Not even a tutorial nowhere or info about release 6.0…?

4

+3
Got the same problem.
I need to boot on the previous kernel to use my computer.

Errors are the same.

1 Like
5
6

Stick to 5.3 ARA I suggest until they sort this out.

7

I’ve had the same error. What I just did was to remove realtek related packages for both kernel - version 5 and 6. Leaving rtl8188 which is the one that I’m using.

2 Likes
8

They really have to fix this issue. I’m currently using parrot as my host OS and got the same error. I may loss all my data damn :hot_face:

9

Hi. Do you know how to select the grub menu? Go into advanced and choose an older kernel.

Grub
Grub642×481 426 KB

GrubAdvanced
GrubAdvanced642×481 428 KB

1 Like
10

I created a clone VM of Parrot 5.3 and used parrot-upgrade. I’m facing the same issue @dmknght.

11

After looking over the output I posted to Pastebin, I can confirm @neo_phyte’s fix of removing realtek-rtl8188eus-dkms package for proper kernel 6.5.0-3 build.

Removing realtek-rtl8188eus-dkms (5.3.9~git20230101.f8ead57-0parrot3) …
Module realtek-rtl8188eus-5.3.9~git20230101.f8ead57 for kernel 6.1.0-1parrot1-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

8188eu.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.1.0-1parrot1-amd64/updates/dkms/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.
      depmod…
      Deleting module realtek-rtl8188eus-5.3.9~git20230101.f8ead57 completely from the DKMS tree.
      Setting up linux-headers-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
      /etc/kernel/header_postinst.d/dkms:
      dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
      dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64.
      Setting up linux-headers-amd64 (6.5.3-3parrot1) …
      Setting up linux-image-6.5.0-3parrot1-amd64 (6.5.3-3parrot1) …
      /etc/kernel/postinst.d/dkms:
      dkms: running auto installation service for kernel 6.5.0-3parrot1-amd64.
      dkms: autoinstall for kernel: 6.5.0-3parrot1-amd64.
      /etc/kernel/postinst.d/initramfs-tools:
      update-initramfs: Generating /boot/initrd.img-6.5.0-3parrot1-amd64
      /etc/kernel/postinst.d/vboxadd:
      VirtualBox Guest Additions: Building the modules for kernel
      6.5.0-3parrot1-amd64.
      update-initramfs: Generating /boot/initrd.img-6.5.0-3parrot1-amd64
      /etc/kernel/postinst.d/zz-update-grub:
      Generating grub configuration file …
      Found background image: /usr/share/images/desktop-base/desktop-grub.png
      Found linux image: /boot/vmlinuz-6.5.0-3parrot1-amd64
      Found initrd image: /boot/initrd.img-6.5.0-3parrot1-amd64
      Found linux image: /boot/vmlinuz-6.1.0-1parrot1-amd64
      Found initrd image: /boot/initrd.img-6.1.0-1parrot1-amd64
      Warning: os-prober will not be executed to detect other bootable partitions.
      Systems on them will not be added to the GRUB boot configuration.
      Check GRUB_DISABLE_OS_PROBER documentation entry.
      done
      Setting up linux-image-amd64 (6.5.3-3parrot1) …
      (Reading database … 535412 files and directories currently installed.)
      Purging configuration files for realtek-rtl8188eus-dkms (5.3.9~git20230101.f8ead57-0parrot3) …
      Scanning application launchers
      Removing duplicate launchers or broken launchers
      Launchers are updated

After rebooting into 6.5.0:

Lorikeet
Lorikeet1333×622 407 KB

12

This error happened because some DKMS are old and not compatible with kernel 6.5. The solution is either remove kernel 6.5, stick with 6.1 for the most stable experience or remove the DKMS and stick with 6.5. The solution to fix was posted on telegram. I guess the forum became a Wasteland for a while

3 Likes
13

Thanks, I’ll stick to 6.1 works good for me.

14

There have been a couple of dozen posts on the forum about problems with this upgrade and its solutions, none of which have involved failing back to 6.1 kernel. I’m not sure where you came up with that shotgun apprroach, or how you missed the forum activity.

In my case, for both hardware and Virtualbox VM upgrades, I had to:

  1. remove rtl8188 driver
  2. remove exploitdb
  3. remove exploitdb-tiny
  4. upgrade
  5. reinstall exploitdb

If you don’t have exploitdb installed, then clearly it’s a bit easier. Delete steps 2,3,and 5 in that case. :wink: As always VMMV because of other unsatisfied dependencies in this upgrade. That depends on what besides the base OS you have installed. Example:

exploitdb-bin-sploits is an installable package. The results of apt install are:
The following packages have unmet dependencies:
exploitdb-bin-sploits : Depends: kali-defaults but it is not installable
E: Unable to correct problems, you have held broken packages.
┌─[✗]─[rbot@mothra]─[~]
└──╼ #apt search kali-defaults
Sorting… Done
Full Text Search… Done
┌─[rbot@mothra]─[~]
└──╼ #

The worst part of this upgrade seems to have been insufficient bandwidth on the update servers when it first released. I’d see tons of Ignored repositories because of timeouts.

Anyway, I have got 6.5 running fine. I can’t offer any congrats to the dev team on the upgrade, sadly.

15

Idk. Maybe i’m a random user who doesn’t fucking know a piece of shit?

1 Like
16

To quote the great Mahatma Gandhi, there is a way out of hell. We, the acolytes of divine “Live,” “Encrypted Persistence” installations on USB drives, require kind instructions on how to troubleshoot this upgrade on read-only media, which is the typical arrangement of Balena Etcher-flashed installations, and which presently generates errors during upgrade to the new “sorry lory” repository-held packages.

However, I suspect we will need a new version of Parrot (5.4?) with which to flash to our USB drives, and then clone back our “Encrypted Persistence” storage partitions (which we dutifully cloned to a spare USB drive before we flashed the new Parrot upgrade to the working USB drive).

Once the “Encrypted Persistence” partition is cloned back to the reflashed USB, then all its custom-selected packages can be upgraded to the new Parrot core and Debian kernel?

P.S.: We all have trouble identifying pieces of shit from time to time, depending on the lighting, wind direction, and other various and sundry field conditions, etc. If getting closer and using artificial lighting (e.g., a flashlight (torch)) doesn’t help with visual identification, try getting down wind of it, and also close enough to smell it. --mmmmmmmm-- THAT’S THE STUFF!! Upon positive identification, please evaluate it according to the Bristol Stool Scale, and submit your report back to this forum. Thank you for your kind cooperation and valuable service.

17

You def. would have been considered such on any OS project I’ve worked on. Perhaps you’re in charge of naming variables correctly?

Regardless, this release was an abortion, unless you’ve never shipped a line of code in your life and you don’t know any better. The DKMS/driver issue was the least of the problems with it.

A actual developer would ask:
Why are incompatible DKMS STILL in the 6.5 kernel?
and do something about it instead of waving their hands and trying to blame other developers and users.

Who are you going to blame for the unavailable distro servers? The colo people?

18

Woah, dude. Does a BDSM flogging come with this gratuitous verbal humiliation beat-down? If so, can he get fries and a reach-around with that? Newbies on this forum (like you) are expected to “put out” during your probationary period.

And remember, always service us veterans with a SMILE. :wink:

19

You and the rest of the dev team should spend a bit more time on your POS test and release plans, and less time trying to impress us with your mighty wit and title.

20

Turdwallets should put their money where their mouths are. Impress us with your contributions, not your grandstanding.