Linux Mint Forums

In the grub menu select LMDE 6 but don't confirm with 'return' but instead hit 'e' (edit mode), scroll down to the 'linux...' line (with arrow keys) and enter the value '3' after 'linux /boot/vmlinuz... ro ' and continue to boot with F10. You will end up in a text console. Log in at the prompt with ...

No timing needed. just wait until the system has booted up and the black scrren appears, then attempt CTRL+ALT+F1.

Seems that the kernel is not (auto)detecting your display properly, thus the black screen after boot. Boot the computer normally and when the black screen appears hit CTRL+ALT+F1 (to F6) to bring up a terminal text window. Enter you username and password there. Then run 'sudo Xorg -configure' and re...

Yep, rather more likely that a damn Windows update did that.

Probably went to sleep and didn't wake up again.
Try 'sudo modprobe -r ath10k_pc i&& sudo modprobe ath10k_pci'

Sorry for not following up on this thread.
Yes, I've found said blueman polkit too in the meantime and added the users to the netdev group.
Works now.
Thanks.

Linux (LMDE et al.) has nothing to do with WIndows whatsoever and operates completely different.
The sooner people stop hypeing it up as a Windows alternative, the better.

Download the latest linux firmware from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Extract the 'amdgpu' folder and copy it to /lib/firmware (i.e. /usr/lib/firmware on usrmerge). Backup of the existing 'amdgpu' folder recommended. These are non-arch binary blobs, no n...

Did you check whether the installed proprietary nvidia driver supports the linux kernel 6.5?
Otw you may need to install the 6.5 kernel headers and the nvidia-kernel-dkms module to have it built on boot.

I'm using gkrellm since ages.
Works fine with my AMD gpu.

Being a 2007 machine, I assumed it was 32 bit so 64 bit may be the solution. But first, I actually have access to the internet via tethered phone so can you elaborate please how I go about "pulling the the 'broadcom-sta-common' and 'broadcom-sta-dkms' .deb packages from the Debian 12 Bookworm ...

Since you have no internet you would have to pull the the 'broadcom-sta-common' and 'broadcom-sta-dkms' .deb packages from the Debian 12 Bookworm non-free repository on another system and then manually install both packages and restart your computer. The packages are arch-independent, so you dont ha...

... admin@PC:~$ sudo grub-install /dev/sda Installing for i386-pc platform. grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. H...

Seems to me you somehow managed to install the boot sector (MBR for Windows) on the blank HDD while the grub folder containing the necessary boot files is on the the new SSD, where the boot sector isnt finding it. When at the 'grub' prompt, type the 'set' command to check the grub setup. Take a look...

Nope.
Seems at boot/login blueman uses the settings from /etc/bluetooth/main.conf, where the value is set to 'true'.
Gernerally disabling the auto-power settings there isn't a viable solution.

Yes, I've read that too, but adding non-priviledged users to the 'bluetoooth' group is complete overkill and bad parctice just to get rid of a confirmation dialogue for rfkill.setstate.

After some digging on this topic I've found that according to this ArchWiki https://wiki.archlinux.org/title/Blueman and other sources, the users should be added to to the 'wheel' group and and '/etc/polkit-1/rules.d/51-blueman.rules' policy created to allow members of the 'wheel' group to execute '...

Blueman keeps pestering my non-priviledged users with a 'RfKill-Status' authorisation dialogue window upon session login.
I (sudo) can't seem to get rid of that dialoge without disabling the blueman applet at start.
Any other ideas?

Most probabbly because 'xserver-xorg-video-amdgpu' lib was/is already loaded at boot for your AMD iGPU. To use the nvidia card (driver) on your laptop you will most certainly have to disable (or uninstall?) that lib. I don't know if there is a way to dual-use use and easily switch between the AMD iG...

Well, the easiest way is probably to just run 'sudo apt autoremove'.
Unless otherwise configured apt only keeps the latest 2 kernels and flags any others as removable (similar to the deprecated purge-older-kernels).