Debian User Forums

I also have a 11th gen Core i7 NUC that works fine on 6.1 but the NIC is Intel. My NIC on the Asustek board is Realtek. Maybe that is the real problem?

I don't think there is any harm is running the 6.11 backport kernel. It solved my problem for now and nothing else has popped up. I have a N100 NUC that does require the 6.11 kernel so the WiFi and Bluetooth work. Both of those devices are also Realtek.

I've been running the backport kernel, 6.11.10+bpo-amd64, for about 24hr. with multiple reboots. Things were either fixed by that kernel or the firmware-realtek, 20240709-2~bpo12+1. That firmware package from backport brings in a lot of newer firmware beyond just Realtek.

At this point I'm installing the backport kernel and firmware on any hardware that is gen 10 or newer. I do know the same hardware works fine on Ubuntu 24.04 LTS which is 6.8 kernel.

I installed Debian 12.8 without a DE today on a Intel 10th gen PC. I ended up with the 6.1.29 kernel. I was working with it via ssh and every time I rebooted nothing happened. I hit the reset button to recover. I also tested shutdown, same issue. I finally re-hooked up a monitor to the PC and saw that a kernel panic happened. I've never seen this behavior. I remembered that on a very new N100 PC I had to install the bookworm backport kernel and firmware just to have wifi and bluetooth work. In ...

I did play with the stable-backport and got my N100 WiFi and BT working. So now I know that backports are the solution I was looking for. Good to know.

So that's what backports are for. Yes I'm a Debian newbie. That worked for me I have the new kernel and realtek firmware and now my BT and WiFi are working.

Sounds like I have some experiments to try. Thanks a lot

I've been playing with Debian 12 on a number of my PCs, more as an educational effort than anything else. It was not an issue on my 10+yr old hardware or my 4 year old laptop. Not even an issue on 2 yr old Intel or AMD systems.

But recently I caught a sale on an Intel based N100 NUC from GMKtec. It came with 8GB of DRAM, 256GB NVME m2.2280 SSD with Windows pre-installed for $129. I clicked buy immediately as I was looking for an improved performance box to replace my Rasberry Pi 4. This wasn't ...

I think I have bigger problems. I just found out I have RTK WiFi as well as BT. The kernel is not new enough to support the N100 shipped with the Realtek WiFi/BT mini card.

Thanks for your reply. I did install with non-free firmware and software enabled.

I just tried: That fixed the firmware error in dmesg, but I still have some issue with bluetooth audio. however I can see I'm on the right path.

Not sure why the firmware was not picked up automatically, but at least I know where to get it.

I just received a new GMKtec G3 N100 NUC Box. I'm currently testing a bunch of distros to see what works and what doesn't. I removed the include nvme SSD with Win11 and filed it away. So on a new nvme ssd I installed Debian 12 xfce4 using the expert method in order to be able to use btrfs with my choice of subvolumes.

After booting I check dmesg to see if things were broken and found some firmware issues. On an earlier test I found Bluetooth was not connecting so I went back start over so I ...

More data. I have 2 workarounds.

1. clone the fedora VM. I chose to create a new drive and not use the existing one. When I started the clone it worked a normal.

2. I deleted the VM without deleting it's storage and then created a new VM importing an existing storage image and that also worked.

Not sure how to fix the original problem though.

I'm running Debian 12 plasma KDE Wayland.

Normally when I open a VM I have a window with menu items and icons to start up the VM. Once I start the VM I have an icon on the far right that allows me to make the VM's console full screen. I also have a way to mouse to the middle of the top margin and 2 icons pop up so I can exit full screen mode or send a combination key sequence.

Normally this works regardless of what OS is running in the VM.

However, today I created a VM of Fedora 40 and ...

Thanks for the explanation. I've only used Stable up to this point and not really familiar as to how things work beyond stable.

I'm experimenting with Trixie on a Macbook Pro that used broadcom-sta-dkms to make the WiFi work on Bookworm stable. I wanted to experiment with Hyprland and needed Trixie. I did not install broadcom-sta-dkms before I changed all the repo names from bookworm to trixie.

Is that what's needed? I can't find any broadcom packages for Trixie.

after installing spice-vdagent I rebooted and checked for errors, The VM did not autostart.

Oct 06 17:30:35 den-pc systemd[1]: Starting libvirtd.service - Virtualization daemon...
Oct 06 17:30:35 den-pc systemd[1]: Started libvirtd.service - Virtualization daemon.
Oct 06 17:30:36 den-pc libvirtd[985]: libvirt version: 9.0.0, package: 9.0.0-4 (Debian)
Oct 06 17:30:36 den-pc libvirtd[985]: hostname: den-pc
Oct 06 17:30:36 den-pc libvirtd[985]: Unable to read from monitor: Connection reset by ...

I assume spice-vdagent is installed in the guest?

Does the vm start manually?


spice-vdagent was not installed so I just installed it.

The vm starts manually just fine. This VM is running debian 12 without a DE. Just console. WHen I install a new host os on this hardware I can install this VM from the disk image since it's on another SSD that I keep for VMs only. The last Host OS was Linux Minut 21.2. I just switched the Host to LMDE 6 which is based on Debian 12 and this is the first time ...

I'm having the same issue. Can't autostart even though it's selected. I get the same sort of error. internal error: Failed to autostart VM 'debian-mythtv': internal error: process exited while connecting to monitor: 2023-10-06T20:55:47.455638Z qemu-system-x86_>
2023-10-06T20:55:47.455666Z qemu-system-x86_64: warning: Spice: ../server/reds.cpp:3442:do_spice_init: Failed to open SPICE sockets
2023-10-06T20:55:47.455677Z qemu-system-x86_64: failed to initialize spice server

CwF wrote: 2023-08-16 22:08 https://tracker.debian.org/pkg/kodi-pvr-mythtv

I'm a bit slow. The tracker page only tells me the current state of things. I created a login but that doesn't let me do anything. It's not clear that anyone is monitoring that site. Some of the requests have not been done or commented on.

I know that Debian maintains their own Kodi repositories. How can I request that the maintainers update the package to the latest verison? There was a very recent bug fix that bumped the version to 20.4.0. I've tested that fix on Ubuntu but my main systems are on Debian 12.

RayCovert wrote: 2023-07-04 12:13 Hey! That's odd. Have you tried checking if the necessary packages are installed on Debian 12?

How do you ever know if you have all the packages installed? Where is that list?