For quite a while, I've been using the amdgpu firmware AMD provides for Ubuntu, which at the time I installed them also worked for my Debian install (11 then, but since upgraded to 12). I used those instead of the usual Debian-provided ones because I wanted ROCm for hobby AI work. However, since then I've been unable to upgrade or even reinstall the drivers due to kernel differences, but I let it be since it was still working. But recently it began causing even bigger problems, with the drivers preventing me from updating the kernel too, so I have decided to drop those drivers and revert to the default ones, and I'll figure out ROCm later.

However, it seems impossible to do so. After running the amdgpu-install uninstall option from those AMD-provided drivers, booting gets me only to a CLI login in TTY1, while TTY7 is a blinking cursor. I followed the instructions provided on Debian's wiki, and all of the relevant packages reported installed and up to date. I have tried uninstalling and reinstalling them, and I have double-checked that thee repositories are correct. When I check the troubleshooting section and run the dmesg command it provides, I get no output at all, and all it offers for that situation is installing the firmware I have already installed.

systemctl status lightdm reports that it is active and running, even though there's no actual GUI. If I add the nomodeset option to grub's boot command, then I can get a GUI, but it's stuck in a single display at 1024x768. It seems to me like that does confirm it is a GPU driver problem as opposed to something else, like an X configuration issue.

My uneducated guess is that the uninstall script is somehow incomplete, and there are still parts of the system looking for the amdgpu drivers I tried to remove, but I have no idea where to look. And due to the issues that made me try to switch back to the kernel drivers, I can't even reinstall the AMD-provided ones to get back to square 1.

I'd provide logs but I don't know which ones would be relevant. On booting I don't get any error messages; it just leaves me at the tty login.

My GPU is the RX 6800XT.

On Trixie testing using Gnome. My Bluetooth devices stopped working a week or so ago. Searching for new devices doesn't show anything, and unpairing/removing my current devices and rescanning gets me nowhere. I've tried all the advice from folks with similar problems from a year or two ago and nothing helps. I've tried making a new user and logging in with that profile, still no Bluetooth. Is it me, and do I have to reinstall, or is it everyone and I just have to wait until the Debian gods fix it?

Hello friends, I'm in trouble with Python3, I must have PIN priority configuration in a wrong way, basically I end up with installations of “testing” packages when I want to install only “stable” versions instead. In the case of Python3 I encounter several difficulties in being able to install other packages because they are not compatible with Python3 testing packages. My question is, how can I downgrade Python testing: 3.12.6-1 to stable: 3.11.2-1 without compromising the system?

root@anonymous:/# python3 --version

Python 3.12.7

How can I set everything up so that the default installations can only ever be the stable ones?

/etc/apt/preferences.d# cat pinning.pref

root@anonymous:/etc/apt/preferences.d# cat pinning.pref

Package: *

Pin: release a=stable

Pin-Priority: 900

#Package: *

#Pin: release a=testing

#Pin-Priority: 500

#Package: *

#Pin: release a=unstable

#Pin-Priority: 100

root@anonymous:/etc/apt/preferences.d#

/etc/apt# cat sources.list

root@anonymous:/etc/apt# cat sources.list

# See https://wiki.debian.org/SourcesList for more information.

deb http://deb.debian.org/debian bookworm main non-free-firmware

deb-src http://deb.debian.org/debian bookworm main non-free-firmware

deb http://deb.debian.org/debian bookworm-updates main non-free-firmware

deb-src http://deb.debian.org/debian bookworm-updates main non-free-firmware

deb http://security.debian.org/debian-security/ bookworm-security main non-free-firmware

deb-src http://security.debian.org/debian-security/ bookworm-security main non-free-firmware

# Backports allow you to install newer versions of software made available for this release

deb http://deb.debian.org/debian bookworm-backports main non-free-firmware

deb-src http://deb.debian.org/debian bookworm-backports main non-free-firmware

root@anonymous:/etc/apt#

root@anonymous:/# apt-cache policy

Package files:

100 /var/lib/dpkg/status

release a=now

100 http://deb.debian.org/debian bookworm-backports/non-free-firmware amd64 Packages

release o=Debian Backports,a=stable-backports,n=bookworm-backports,l=Debian Backports,c=non-free-firmware,b=amd64

origin deb.debian.org

100 http://deb.debian.org/debian bookworm-backports/main amd64 Packages

release o=Debian Backports,a=stable-backports,n=bookworm-backports,l=Debian Backports,c=main,b=amd64

origin deb.debian.org

500 http://security.debian.org/debian-security bookworm-security/non-free-firmware amd64 Packages

release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=non-free-firmware,b=amd64

origin security.debian.org

500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages

release v=12,o=Debian,a=stable-security,n=bookworm-security,l=Debian-Security,c=main,b=amd64

origin security.debian.org

500 http://deb.debian.org/debian bookworm-updates/non-free-firmware amd64 Packages

release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=non-free-firmware,b=amd64

origin deb.debian.org

500 http://deb.debian.org/debian bookworm-updates/main amd64 Packages

release v=12-updates,o=Debian,a=stable-updates,n=bookworm-updates,l=Debian,c=main,b=amd64

origin deb.debian.org

900 http://deb.debian.org/debian bookworm/non-free-firmware amd64 Packages

release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free-firmware,b=amd64

origin deb.debian.org

900 http://deb.debian.org/debian bookworm/main amd64 Packages

release v=12.7,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=amd64

origin deb.debian.org

Pinned packages:

root@anonymous:/#

I'm getting 429 error code. Is this happening to everyone or is it something local to me?

Complete noob here looking for assistance enabling QSV for use with Handbrake and PLEX.

SO far I have installed:
vainfo
flatpak
handbrake
flatpak --user install HandBrake.Plugin.IntelMediaSDK-1.8.2-x86_64.flatpak

Output from vainfo:
root@debian01:/home/anon/Downloads# vainfo

error: XDG_RUNTIME_DIR is invalid or not set in the environment.

libva info: VA-API version 1.17.0

libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

libva info: Found init function __vaDriverInit_1_17

libva info: va_openDriver() returns 0

vainfo: VA-API version: 1.17 (libva 2.12.0)

vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.1.1 ()

vainfo: Supported profile and entrypoints

VAProfileMPEG2Simple : VAEntrypointVLD

VAProfileMPEG2Main : VAEntrypointVLD

VAProfileH264Main : VAEntrypointVLD

VAProfileH264Main : VAEntrypointEncSliceLP

VAProfileH264High : VAEntrypointVLD

VAProfileH264High : VAEntrypointEncSliceLP

VAProfileJPEGBaseline : VAEntrypointVLD

VAProfileJPEGBaseline : VAEntrypointEncPicture

VAProfileH264ConstrainedBaseline: VAEntrypointVLD

VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP

VAProfileVP8Version0_3 : VAEntrypointVLD

VAProfileHEVCMain : VAEntrypointVLD

VAProfileHEVCMain10 : VAEntrypointVLD

VAProfileVP9Profile0 : VAEntrypointVLD

VAProfileVP9Profile2 : VAEntrypointVLD

QSV options ate still not showing in handbrake however.

Bonjour j'aimerais passer sur debian mais tout en continuant a jouer a valorant .

Serait'il possible de l'utiliser depuis un vm (virtualbox) ?

Merci

I assumed I was using systemd-networkd and therefore config should be under /etc/systemd/network

Am I using systemd-networkd or not?

Hello,

I am seeing a strange issue with the Firefox Flatpak on Debian Trixie.
When I launch it by clicking on the icon in my dock, it launches normally. If I want to open a second window by right clicking on the Firefox icon it takes forever to open. We are talking about 1 minute ish. Systemd does not give any errors, so I don't have much to go on.

A workaround is to open a new tab and drag out so I get a new Windows, however I would love for this to work as I use it quite often.

Anyone got any idea of what is going on?

Note: I have tested the Firefox ESR deb, there it works as expected so this seems to be a Firefox Flatpak issue.

Hello,

ok, so long story hopefully short: I've been trying to boot my debian (on a Raspberry Pi 4) desktop environment unto quite specific conditions, but I am at a point where I don't know any futher.

Longer story, I want to

1. access the desktop environment remotley with no monitor plugged into the pi and
2. want to have to enter the user and the password there after connecting and before accessing the desktop environment. Connecting to the "normal login screen", if you like.

I'm able to access the pi via SSH and I am also able to access the desktop environment via VNC (installed x11vnc) (but with a catch). Now there are two problems I just can't find a solution to. At the moment the access to the remote desktop environment is only possible if

1. a physical monitor is plugged into the pi and
2. the settings in raspi-config are set to boot into the desktop environment without having to enter the user name and the password.

Both these points I would like to avoid. I want this little device sitting on a bench and just power it up when I need to and then access the desktop environment via VNC (and then enter user and password). To address Problem 1 I found a "dummy" display driver (and got it working), but I was not able to let the pi boot use this dummy as if it was the "standard" display. I have a feeling that the solution to problem 1 might work somehow with this dummy display, but I don't quite know how. For this problem, at least, I have "a feeling" to which direction I could go.

How to tackle the second problem, I have no idea. Like, nope, nothing. My only guess is that I could maybe already connect to the pi via VNC as soon as it has booted up and "shows" the login screen on the dummy display, but I have no idea how to pull this off.

Do you guys have any suggestions how I could tackle these two problems?

Thank you!

I'm currently trying to setup a new Debian 12 virtual server so I can soon retire my old Debian 7 system (It's about time). However I got stuck super quickly and can't find a solution to it. I tried to install unbound and since I did that the server is no longer able to resolve DNS queries. Well that seems to be the result from unbound not able to even start. After a fresh install, unbound misses the file at '/var/lib/unbound/root.key' but as far as I understood it, this should have come with the installation of unbound?

SOLVED !

I have this macbook clamshell from 1998 running debian 8 jessie and a system 9 macos rice. I want to play an mp4 stream, but I can't upgrade the laptop as this is the last Debian version with the correct graphic driver.

I guess, I am looking for a small / cli contained MP4A player that I could compile from source. Any idea ?

edit: I am only interested in audio.

edit 2: After seeing that everybody says that VLC can do it. I looked carefully and discovered that I was missing libmp4v2-dev. So I installed it, recompiled VLC and IT WORKS NOW !!! Thanks to everybody for your help.

I'm currently developing software for an instrument with about 25 devices on it. The boards we are prototyping all run debian. However, our development laptops are all Windows. Consequently, a lot of my development work takes place in WSL. I find this less than ideal. I'd like to buy a few laptops that run debian (I don't even care if it dual boots). All of our laptops/desktops are Lenovo, so there's a preference to stick with something like a Thinkpad. When demoing hardware, we tend to move from room to room, which is the reason for a laptop request (I had recommended several of the cheap low power PCs I run at home). FWIW, because I'm the only person with debian experience at the office, I'm going to be the default IT guy for all of these machines.

Is there a currently recommended model? My desires (in mostly descending order):

1. Currently sold from Lenovo's website

2. USB works

3. Suspend works, preferably with minimal-to-no configuration

4. Roughly 1000 bucks, slightly less would make me look good

5. External Displays work

Anyone running a newer cheap development laptop?

Hello

I recently installed Debian on a partition of only 30Gbs and quickly realized how stupid that was and would now like to remove windows and set up Debian as my main OS and set WIndows and a dual boot option.

1. WIndows is located on my C drive. If i install Debian on the C drive, will it remove WIndows and anything installed from windows on my C drive AND my D drive?

2. Can I then reinstall WIndows later with my product key?

I'm interested in discovering how the project has been sponsored without corporate backing.

Hello on my second computer i have a 3060 rtx thats worked well untill the last update , now i dont have the nvidia driver running and cant made video editing or other stuff that need my gpu

The nvidia driver are installed but i dont know they dont run.

What i can do reinstall all my debian from scratch ?

it's possible to reinstall and dont lose my file and application ?

or how i can repair this problem ?

Edit

https://preview.redd.it/374z2np2iayd1.png?width=2006&format=png&auto=webp&s=6cf151d7c3ccc9a829cc58db53c14ddcfba4ffe9

this is not the name i see when nvidia driver is ok

https://preview.redd.it/zg74sbv8iayd1.png?width=881&format=png&auto=webp&s=e482a3ce70027dc994a99122b324574f9467b613

Hello so yesterday I installed Debian for the first time. I have very little experience with Linux. I was just looking through the normal settings page adjusting some Settings. After changing Monitor settings like refresh rate things got weird. The screen started flickering but it was barely noticable. After 1-2 minutes it got stronger and stronger so I changed it back to 60hz. Now the flickering was even worse like it refreshed at 10hz. Now i started to noticed ghost images when changing "tabs" not just slightly but so strong that i almost couldnt see what was going on in the backround (behind the "ghost images"). I thought great my monitor or gpu is dying. So I restarted the PC and monitor. When the monitor turned on and showed the Benq splash screen and even in the Bios screen the ghost images and flickering persisted. I booted Windows, factory reset the monitor, changed to HDMI, took apart my PC components, disconnected everything for one hour nothing helped. I accepted the fact that my Monitor is broken and its probably not the GPU because it occurs even when not connected to any display output. When I start the monitor or when I open the monitors built in settings menu for example. I already put the monitor to the sie to throw it away at some point. Today i was looking for a solution to output Video to my Smartphone because i dont have a second monitor. So i connected the glitching Monitor again to setup Team Viewer vor something similar so i could still use my PC. While settings up things in Windows the flickering and ghost images got better with each minute so about 30 Minutes in everything was back to normal. Long story short I really wonder what caused this I wasted hours trying to troubbleshoot it and was about to throw the monitor away. Did it have something to do with EDID ? Was it a known or unknown bug or compatibility issue ? Did I do something wrong during installation...

Hi Friends I'm new using GNU/LINUX. I want install debian my notebook old Intel celeron with 4gb of ram. Is a good idea?

I hear your suggestions, thanks

I'm on a Dell Precision 5540 with a Dell WD19TB dock, running Debian 12. This computer previously had Windows 10 but I removed it in September with Debian. It worked perfectly until yesterday, when I had to disconnect the laptop from its dock to attend a Zoom meeting. After I re-connected the laptop to the dock, it no longer identified the monitors. The monitors are connected via DisplayPort and HDMI. Since then I've tried everything. I'd disabled Secure Boot in the BIOS, installed nvidia-driver, ensured that "No Security" is set for Thunderbolt in the BIOS, replaced Debian with Ubuntu 18.04 LTS (the version stated as supported by Dell for the dock), and finally tried to use EnvyControl to disable the integrated GPU. This bricked my install of Debian so I've reinstalled it and the monitors are still not detected. I've installed the DisplayLink drivers from Synaptic, and unplugged / re plugged all replaced all cables countless times. I ran the Dell Update Utility for the WD19TB dock, but it crashed with an error about no permissions, even though I ran it as super user.

My laptop has one HDMI port, and any monitor connected from there works, but the USB C dock does not work.

I've tried it with many other docks, including the TB16, which used to work fine with my laptop but now has the same issue. But on the Dell WD15 and WD19 (non TB) dock, I was able to get xrandr to recognize the displays, and even display an output on the monitors momentarily, before they went back to "No SIgnal." Both the WD15 and WD19 recognize the monitors in xrandr, but the monitors do not receive any signal.

I have a Lenovo Chromebook with Debian 12 installed, and it is able to produce a signal to my monitors with the Dell WD19TB Dock, but for some reason my main laptop can't. I'm not sure what to do now. I really don't want to have to go back to Windows 10 but I can't see any other option now. Is there anything else I can do to fix this issue? What confuses me most is that it was working just yesterday morning and now nothing works. Thanks so much.

System specifications:
Debian GNU/Linux 12 (bookworm) x86_64

Host: Precision 5540

Kernel: 6.1.0-26-amd64

Shell: bash 5.2.15

Resolution: 1920x1080

DE: Xfce 4.18

WM: Xfwm4

WM Theme: Default

CPU: Intel i7-9850H (12) @ 4.600GHz

GPU: NVIDIA Quadro T1000 Mobile

GPU: Intel CoffeeLake-H GT2 [UHD Graphics 630]

Memory: 2924MiB / 15619MiB

So I was going to update my system, Running Debian stable with backports and Flatpak

But my flatpak failed to update, I get this error

OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:526:sock_cb: code should not be reached
Bail out! OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:526:sock_cb: code should not be reached
Aborted (core dumped)

Because it worked fine on my other computer that is running Debian stable without backports I assumed it was due to curl was a newer version from backports. But I still have the same error after downgrading curl to the stable version.

libostree is the same on both system, stable version.

I need to run a image generation model on my Debian 12,it needs nvidea drivers to run. I tried installing nvidea drivers following a tutorial but after that my second screen connected via Hdmi didn't work or get detected🥲

How can i solve this?

Hey everyone,

I'm new here so I will try to detail everything as much as I can even though I may not have every clues on how to write a proper post asking for help.

Here is the summarized problem: I have two 2560x1440 AOC screens working perfectly fine (tried on another computer), connected to an USB-C dock, itself connected to my laptop with a 2560x1440 screen. BUT the screens are not recognized by the laptop.

Laptop specifications: Asus ROG Zephyrus with an Nvidia RTX 3000 series, AMD Ryzen 5000 series.

Using xfce4-about, the "GPU" line shows "AMD Radeon graphics"

OS: Debian 12 hardened by Kicksecure, (not the problem here I think, as the screens on the dock connect perfectly with another laptop with exactly the same Kicksecure install, as well as on a classic Debian 12 laptop).

Graphical environment: Xfce 4.18

Display manager: X11 with LightDM

What I've tried:

First, the screens were not even recognized by the graphical interface display manager of XFCE.

I thought it was an Nvidia drivers problem, so I installed them, blacklisted the Nouveau drivers.

Now the screens showed up in the display manager, but were disabled. Enabling them graphically wasn't possible.

Using xrandr --output DP-1-0.1 --auto returned: xrandr: Configure crtc 4 failed

I tried using nvidia-xconfig tool, creating an xorg config file, manually adding each screen, and that was as far as I went: the two screens on the dock were connected, enabled, showing me the desktop environment, but my laptop's screen went black with an underscore in the top left corner, and only worked using Ctrl + Alt + F2 as a client interface.

I then tried purging everything nvidia related and installing amd drivers with:

apt install firmware-amd-graphics libgl1-mesa-dri libglx-mesa0 mesa-vulkan-drivers xserver-xorg-video-all

But now, the screens are not even detected, same situation as the beginning:

The display manager and xrandr don't detect any external screen, only the eDP (laptop's screen).

I've tried to do a clean install, connecting the dock with the two displays right after the new install, it didn't work either.

It has been three days trying to fix the issue now, maybe my issue is too vague, or even easy to fix, but I can't find anything working for me.

hello what's wrong i don really understand ?

https://preview.redd.it/ja65nnuyo3yd1.png?width=1230&format=png&auto=webp&s=251039abf8cd71b9bf01b2392bcfecd3855a979a

Currently debian sid and testing both have 535 version but the current version is 560. I tried using cuda repo to get the latest but this method gets the error of breaking changes, cannot be installed, since the cuda repo is specific for debian 12. I tried using .run install method but most ppl in the linux community don't prefer that. So is there a safe way to get the latest nvidia packages without breaking the system?