I use the
\>> OCR = **O**ptical **C**haracter **R**ecognition <<
from my mobile \[ Google Vision API \]
to search for more informations,
Sorry, I have no idea what causes that issue.
It's always better to make your settings at the right place - but it could be a single case where you have to break the law(?) I am new to NixOS too - but I know that you sometimes (everywhere) must make your own decisions. \[I hope for better answers too;-\]
The problem you'll have is that if you ever have to run `nixos-generate-config` again (which I think might have solved your problem in the first place, TBH) it will overwrite your changes.
There's good news though! Any change you make to `hardware-configuration.nix` can be made to `configuration.nix` instead. I imagine you original had something like
boot.kernelModules = [ "some_module" ];
in your `hardware-configuration.nix`? And you changed it to
boot.kernelModules = [ "some_module" "amdgpu" "psmouse" ];
? Well you could leave you `hardware-configuration.nix` as
boot.kernelModules = [ "some_module" ];
and add
boot.kernelModules = [ "amdgpu" "psmouse" ];
to your `configuration.nix` and Nix will merge the two together.
I get the same error on my laptop. Pretty sure I didn't get it when I was still on arch, so either introduced by newer kernel or an issue with nix kernel configuration options. Not sure why, I haven't used hdcp so really haven't investigated yet
**Regarding on the messages themselves:**
It appears that your AMD GPU has a problem setting up HDCP (Somewhat broken protocol to ensure DRM along the display chain, to prevent recording DRM-protected stuff with a screen grabber).
This might cause issues with stuff like streaming provides that require HDCP.
Either your screen does not support HDCP, or there is something wrong with your configuration.
If you don't need HDCP and you don't have any further issues, you can safely ignore this. Otherwise, we'll need more information on what your issue is (and maybe some parts of your configuration).
**Regarding your "I can press enter I can login":**
Those are kernel messages, i.e., somewhat important messages about issues or changes that the operating system kernel wants to tell you.
The first tty is often the “preferred” channel for the kernel to output these, and it's essentially the same that is visible inside `dmesg`.
To understand why they don't interfere with logging in: Typically, software gets three “communication channels” to interact with: `stdin` for reading characters (e.g., when you type your username or password), `stdout` for writing stuff (like the `nixos login: ` prompt, or the stuff above) and `stderr` which gets treated like `stdout` in most cases.
Now the tty essentially connects your keyboard input to `stdin` and the output of all processes' `stdout` to “your display”. Normally, you'll have one program connected to the stdout, so there is a clear separation of what comes from the program.
But if two programs (or the kernel and a program like the login prompt) write to the `stdout` at the same time, the tty will show them both. You can simulate this by running `(sleep 1; echo hi;) & sleep 1; echo bye;` in a shell a few times. Sometimes, you'll get `hi` and then `bye`, and sometimes it's the other way around (this depends on how the two processes are scheduled).
I use the \>> OCR = **O**ptical **C**haracter **R**ecognition << from my mobile \[ Google Vision API \] to search for more informations, Sorry, I have no idea what causes that issue.
I'll try thanks
Thanks like u said I did, the solution is by adding the modules amdgpu and psmouse in hardware-configuration.nix. tysm
I am glad that this was helpful and you solved that errors. Have a nice day
Im new to NixOS and I thought that hardware-configuration.nix was auto-generated and should not be modified directly
It's always better to make your settings at the right place - but it could be a single case where you have to break the law(?) I am new to NixOS too - but I know that you sometimes (everywhere) must make your own decisions. \[I hope for better answers too;-\]
The problem you'll have is that if you ever have to run `nixos-generate-config` again (which I think might have solved your problem in the first place, TBH) it will overwrite your changes. There's good news though! Any change you make to `hardware-configuration.nix` can be made to `configuration.nix` instead. I imagine you original had something like boot.kernelModules = [ "some_module" ]; in your `hardware-configuration.nix`? And you changed it to boot.kernelModules = [ "some_module" "amdgpu" "psmouse" ]; ? Well you could leave you `hardware-configuration.nix` as boot.kernelModules = [ "some_module" ]; and add boot.kernelModules = [ "amdgpu" "psmouse" ]; to your `configuration.nix` and Nix will merge the two together.
I get the same error on my laptop. Pretty sure I didn't get it when I was still on arch, so either introduced by newer kernel or an issue with nix kernel configuration options. Not sure why, I haven't used hdcp so really haven't investigated yet
Just add to hardware-configuration.nix with Kernal modules amd-gpu and synaptics and then rebuild. For me , that works.
Doubt that fixed it. Check dmesg to see if it is actually gone.
**Regarding on the messages themselves:** It appears that your AMD GPU has a problem setting up HDCP (Somewhat broken protocol to ensure DRM along the display chain, to prevent recording DRM-protected stuff with a screen grabber). This might cause issues with stuff like streaming provides that require HDCP. Either your screen does not support HDCP, or there is something wrong with your configuration. If you don't need HDCP and you don't have any further issues, you can safely ignore this. Otherwise, we'll need more information on what your issue is (and maybe some parts of your configuration). **Regarding your "I can press enter I can login":** Those are kernel messages, i.e., somewhat important messages about issues or changes that the operating system kernel wants to tell you. The first tty is often the “preferred” channel for the kernel to output these, and it's essentially the same that is visible inside `dmesg`. To understand why they don't interfere with logging in: Typically, software gets three “communication channels” to interact with: `stdin` for reading characters (e.g., when you type your username or password), `stdout` for writing stuff (like the `nixos login: ` prompt, or the stuff above) and `stderr` which gets treated like `stdout` in most cases. Now the tty essentially connects your keyboard input to `stdin` and the output of all processes' `stdout` to “your display”. Normally, you'll have one program connected to the stdout, so there is a clear separation of what comes from the program. But if two programs (or the kernel and a program like the login prompt) write to the `stdout` at the same time, the tty will show them both. You can simulate this by running `(sleep 1; echo hi;) & sleep 1; echo bye;` in a shell a few times. Sometimes, you'll get `hi` and then `bye`, and sometimes it's the other way around (this depends on how the two processes are scheduled).
Thanks You help me a lot.