Software > Operating Systems and Porting

[NEWS] Debian 11 is out

<< < (6/9) > >>

MauryG5:
Guys I suddenly got a pretty serious problem on Debian 11. I lost the audio, classic speaker icon at the top right and consequently no audio. I try to load volume control, it tries to open the preferences but it remains constantly loading. I tried uninstalling and reinstalling Pulse audio but got nothing. I tried to force alsa to start but it doesn't recognize alsa, I don't understand what happened ... If I turn up the volume in the settings I get nothing, it doesn't recognize anything anymore, what the hell is going on?

MauryG5:
In the various tests I have done, I have realized that the problem is not in some Kernel driver or even in pulse audio, apparently it depends on gnome.  In fact, as soon as I arrive at the login screen, the loudspeaker with the volume is regularly present and then disappears when you log in.  Trying to tap it on the login screen, it started working smoothly again even after.  There must be some small bug on gnome 3.38 regarding this thing ... See over time if the same thing happens to you too ...

MauryG5:
Hi guys, I wanted to ask you something that I have never been able to understand well. For some time now, I have been compiling the kernels myself to make sure that I use options that are more congenial to me and be able to use the infamous 4K page format as my friend Daniel Pocock taught me. To compile the Kernel, both on Debian and on Ubuntu which is a derivative, I use the universal procedure and then I do: make menuconfig and I configure the kernel, make -jx, obviously I put the number of treed in place of x, make modules, make modules install and finally make install. At that point after make install the grub updates and gives me the new kernel and actually at the new start, I find it in the list of usable kernels. The only thing I can't understand though is, why when I give the grep command to see the installed kernels, I never get my compiled files? Consequently if I have to remove one of mine, I can't because giving the classic remove command, it tells me that that kernel obviously doesn't exist. I would like to understand what is missing in my procedure, which allows the system to recognize 100 by 100 the kernel compiled and installed by me ... Thanks to all of you always











1

Borley:
make install places everything in the filepaths directly, so dpkg never sees it. You probably want to build into .deb packages instead, starting from apt source linux-image-X.XX.X-XX-powerpc64le. But don't ask me details, I'm really new to the procedure myself.

MauryG5:
Hi Borley, yes you are right, the installation part with the dpkg -i command is missing but the universal procedure does not bring you anything on how to do after the make install that's why I have never deepened further. Now I have found a procedure that reports the command: sudo make -j 32 KDEB_PKGVERSION = 1.-maury.ppc64le deb-pkg
I call my custom kernel as you understand of course, if I do this then he creates the .deb packages which can then be installed with the dpkg command, only I noticed that if I do this command, I try to compile the 5.15 kernel. X, it gives me an error towards the end of the compilation while if I try to compile a more recent version like 5.17, then the compilation procedure is successful and I honestly don't understand why. If I use the procedure that I have always done, that is the universal one I mentioned above, then the compilation takes place without problems even on version 5.15.X but as usual I have the problem that I do not have the .deb files to perform the actual installation. If I understood how to get the .deb files from the universal procedure, I would continue to use that without any problems ... I would like to understand well how to do after the make install, how to get the .deb files, I need the advice of a Debian expert like Daniel Pocock or Xlinder or Linux experts that there are many in here :-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page