Debian User Forums

Help out with development, perhaps?

Trying out Debian & Debian-based live openbox desktops in QEMU/KVM (Arch host running sway): https://i.postimg.cc/LsmhXqk8/20230715-17h31m58s-grim.png Clockwise from top-right: BunsenLabs Beryllium, Debian bookworm LXDE, CrunchBang++ 12, deadbang 12.0 (Debian bookworm pure blend, alpha version)....

sunrat wrote: ↑2023-07-10 09:12 We expect the issue will be fixed for 12.1 images.

The issue was fixed upstream on 2023-07-09:

https://salsa.debian.org/live-team/live ... a453eb6307

No idea when the new live-build version will be pushed to sid though.

I've never used Samba but there are Windows drivers for VirtIO that can be used with 9pfs under QEMU/KVM. The speed isn't the best but it should work.

Arokan wrote: ↑2023-07-16 10:09

Code: Select all

      VAProfileAV1Profile0            : VAEntrypointVLD

Looks like AV1 decoding ("VAEntrypointVLD") is supported by VA-API but not encoding ("VAEntrypointEncSlice"), unfortunately.

Does VA-API work for AV1 yet? It won't be as fast as AMF but at least you won't need the proprietary drivers.

Read the upgrade guide, it is very comprehensive: https://www.debian.org/releases/bookwor ... ng.en.html

And yes, I'm waiting for 12.1 before upgrading my production machines

For ethernet try the r8168-dkms package; for the wireless device perhaps try https://ubuntuforums.org/showthread.php?t=2181558, if this is an ASUS machine.

The Debian 12.0 live images add the raspi-firmware package and cause upgrade problems afterwards. This kernel command line parameter removes the package as part of the installation process: preseed/late_command="in-target dpkg --purge raspi-firmware ; in-target rm -r /boot/firmware" To app...

Is this another wind-up?

You don't have PATH set correctly because you've used this command to get root permisions: When you should have used either or We've had at least a thousand threads here about this exact subject, why couldn't you find them?

Only ARM machines store firmware under /boot/firmware/, x86 systems use /lib/firmware/ instead.

The solution to that has already been linked to earlier in the thread. There are several active threads here with the same (or a very similar) error message. Here is another link to a solution in a single, short post: https://forums.debian.net/viewtopic.php?p=777091#p777091 ^ Follow the advice there...

So is `nala upgrade` quicker than that GUI monstrosity?

No need to full quote btw.

viewtopic.php?p=777091#p777091

Please search the boards before posting.

dpkg: warning: 'ldconfig' not found in PATH or not executable dpkg: warning: 'start-stop-daemon' not found in PATH or not executable dpkg: error: 2 expected programs not found in PATH or not executable Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin And also be sure to...

I don't understand what is happening The raspi-firmware arm64 package was added to the amd64 ISO images by mistake; the kernel & initramfs scripts installed by that package produce the error and also prevent removal once they've been triggered. Additionally the raspi-firmware package installs s...

My method to fix this problem was this (be very careful with the last command!): Nothing else was required.

Are you using https://deb.debian.org? That should redirect to the fastest local mirror using the magic of CDN.

Otherwise try And only use nala(8) to update in future. GUIs are for suckers!

Just because an AI created the image doesn't mean the prompt author doesn't deserve credit. Duchamp didn't make that urinal but "Fountain" is a hugely significant piece of modern art.

The actual problem is only encountered when the raspi-firmware package is (re)configured or when the kernel/initramfs is updated.