Normally to remove an old kernel from my debian stable systems, I issue the
following command:
apt purge linux-headers--amd64
linux-headers--common linux-image--amd64
Following this recipe, which has always worked in the past, I issued:
apt purge linux-headers-5.10.0-11
On Fri, Jun 17, 2022 at 12:45 AM Keith Bainbridge wrote:
>
>
> On 17/6/22 00:08, Boyan Penkov wrote:
> > On Thu, Jun 16, 2022 at 12:09 AM Keith Bainbridge
> > wrote:
> >>> Cheers!
> >>
> >> Good afternoon Boyan
> >>
> >> What happened when you installed to 2 suggested items?
> > Hey Keith --
On 17/6/22 00:08, Boyan Penkov wrote:
On Thu, Jun 16, 2022 at 12:09 AM Keith Bainbridge wrote:
Cheers!
Good afternoon Boyan
What happened when you installed to 2 suggested items?
Hey Keith -- yes, thanks for the pointer; you're absolutely correct...
Somehow linux-image-headers was not
On 16/6/22 06:11, Boyan Penkov wrote:
Hello folks,
Installing virtualbox and virtualbox-qt from sid, and running
`virtualbox --version` returns the below:
```
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
Hello folks,
Installing virtualbox and virtualbox-qt from sid, and running
`virtualbox --version` returns the below:
```
WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-amd64.
Muhammad Akbar Yanuar Mantari wrote:
> Dear Debian Developer,
>
> Please patch broadcom-sta for kernel 5.18 from arch linux
>
> https://github.com/archlinux/svntogit-community/commits/packages/broadcom-wl-dkms/trunk
This is the Debian Users' list, not developers.
In any
On 4/05/22 18:57, Tixy wrote:
On Wed, 2022-05-04 at 00:44 +0300, IL Ka wrote:
Linux kernel is backward compatible. Linus calls it "we do not break
userspace".
That means _old_ applications should work on new kernel
There's also the issue of what config options the kernel is built
On Wed, 2022-05-04 at 00:44 +0300, IL Ka wrote:
> Linux kernel is backward compatible. Linus calls it "we do not break
> userspace".
> That means _old_ applications should work on new kernel
There's also the issue of what config options the kernel is built with.
I'm sure th
Linux kernel is backward compatible. Linus calls it "we do not break
userspace".
That means _old_ applications should work on new kernel
On Wed, May 4, 2022 at 12:40 AM Richard Hector
wrote:
> Hi all,
>
> For various reasons, I have some stretch LXC containers, on a buste
Hi all,
For various reasons, I have some stretch LXC containers, on a buster
host that I now need to upgrade. That will mean they end up running on
buster's 5.10 kernel.
Is that likely to be a problem?
If so, I guess I can leave the host on buster's kernel for the time
being, but that's
On Thu, 2022-04-14 at 11:18 -0400, Stefan Monnier wrote:
> > I think it would be great to provide such a (semi-)official support
> > for
> > backported kernels in the installer again. There is probably a
> > significant number of users which use testing, just because they
> > can't
> > install
Thank you for your good hints, Andrew. My approach is different.
I am in the lucky position that the question is of theoretical interest
to me this time only, in the past I had cases where I had to use
testing, because the kernel of the installer was too old to support
basic functions of my
On Thu, Apr 14, 2022 at 11:16:00AM +0200, Christian Britz wrote:
> Hello dear Debianists,
>
> if a new system has at least basic hardware support by the kernel
> provided by the Debian installer, you can solve many hardware problems
> by installing a newer kernel from backports a
Hello dear Debianists,
if a new system has at least basic hardware support by the kernel
provided by the Debian installer, you can solve many hardware problems
by installing a newer kernel from backports after the system setup.
Is there a solution for the case where the installer kernel is too
e
> > system fails with kernel panics
> >
> > By adding init=/bin/bash from within grub works and we can then do
> things
> > like
> >
> > mount - o remount /
> > cd /etc/init.d
> > ./networking start
> > ./ssh start
> > apt install stress
> Our servers were running Debian 10 without any issues
> We have been trying to do a fresh install of debian 11.3 on exactly the
> same hardware. The install works without any errors but on rebooting the
> system fails with kernel panics
>
> By adding init=/bin/bash from
Hi
Our servers were running Debian 10 without any issues
We have been trying to do a fresh install of debian 11.3 on exactly the
same hardware. The install works without any errors but on rebooting the
system fails with kernel panics
By adding init=/bin/bash from within grub works and we can
On 19/03/2022 04:15, Kevin Exton wrote:
Hi All,
I just installed the latest kernel in the Debian Bullseye backports and
I'm getting these warnings:
W: Possible missing firmware /lib/firmware/i915/skl_guc_62.0.0.bin for
module i915
(...)
Normally the solution to these missing firmware
Hi All,
I just installed the latest kernel in the Debian Bullseye backports and I'm
getting these warnings:
W: Possible missing firmware /lib/firmware/i915/skl_guc_62.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_62.0.0.bin for
module i915
W: Possible missing
Respondo aquí para abreviar a los lectores: gracias Jhosue. Valiosa
información por lo que intuyo. En cuanto termine del trabajo investigaré
esos links y veré si intento lo del kernel (atinado vuestro consejo que
apunte a la placa y no al pen, creo) . Gracias otra vez.
Daniel
El 9/3/22 a las
a las 23:04, Daniel
> >>> () escribió:
> >>>> Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
> >>>> me suelo manejar mas en GUI).
> >>>>
> >>>> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con
GUI).
Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
instalación básica, sólo agregado Synaptic y poco más.
Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 MT7921).
Tengo instalado
anejar mas en GUI).
> >>
> >> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
> >> Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
> >> instalación básica, sólo agregado Synaptic y poco más.
> >>
> >>
On 2022-03-07 18:25:54 -0500, Stefan Monnier wrote:
> Obviously it depends who you ask. The kernel side doesn't consider
> itself to blame because they do expose a "stable" API which Nvidia
> could use.
But note that the Xorg API is not stable. The 340 branch can no long
On Tuesday, 8 Mar 2022 at 22:47, Richmond wrote:
> Now that I have it working I fear to change it.
And this is exactly my modus operandum. Once I get a system to a stable
productive working state, I leave it alone (except for security issues).
--
Eric S Fraga with org 9.5.2 in Emacs 29.0.50
t; me suelo manejar mas en GUI).
>>
>> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con
i5-1135G7. Instalado
>> Debian 11, kernel 5.10.0.11-amd64, KDE Plasma
5.20.5. Por ahora
>> i
didier gaumet writes:
> Le mardi 08 mars 2022 à 12:12 +, Richmond a écrit :
> [...]
>> I don't know if there are
>> any distributions other than debian which still support kernel 4.
>
> A RHEL 8 clone (Almalinux, Rocky Linux...) should do: kernel is blocked
> to
El 8/3/22 a las 15:12, Jhosue rui escribió:
El jue, 24 feb 2022 a las 23:04, Daniel
() escribió:
Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
me suelo manejar mas en GUI).
Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
Debian
On 3/8/22 5:05 AM, to...@tuxteam.de wrote:
On Tue, Mar 08, 2022 at 10:46:35AM +0100, Hans wrote:
No, of course not. It's you to blame, for upgrading your system.
Hilarious!!! (Please bear with me for a moment because it is actually
tragic, but ...)
Why might it be hilarious?. Well,
===
...
Setting up nvidia-legacy-340xx-kernel-dkms (340.108-10~bpo11+1) ...
Loading new nvidia-legacy-340xx-340.108 DKMS files...
Building for 5.10.0-11-amd64
Building initial module for 5.10.0-11-amd64
Done.
nvidia-legacy-340xx.ko:
Running module version sanity check.
- Original module
-
El jue, 24 feb 2022 a las 23:04, Daniel
() escribió:
>
> Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
> me suelo manejar mas en GUI).
>
> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
> Debian 11, kernel 5.10.0.11-a
Le mardi 08 mars 2022 à 12:12 +, Richmond a écrit :
[...]
> I don't know if there are
> any distributions other than debian which still support kernel 4.
A RHEL 8 clone (Almalinux, Rocky Linux...) should do: kernel is blocked
to 4.18 until EOL in 2029 (end of full support may 2024,
for almost the same long time.
>
> But whenever debian ships a new kernel version, the proprietrary
> nvidia kernel modules can not be built. If lucky, there is a patch for
> it after months.
>
> Yes, modern Nvidia cards are supported, but using an older noteb
On Tue, Mar 08, 2022 at 06:25:54AM -0500, Dan Ritter wrote:
> to...@tuxteam.de wrote:
[...]
> > (Sorry for the irony, but see, if NVIDIA's sources reference parts of
> > the kernel headers which aren't guaranteed to stay stable, well...)
> There is also the problem that NVidi
urse not. It's you to blame, for upgrading your system.
>
> Just stay with your old kernel, header files and toolchain and all will
> be well.
>
> (Sorry for the irony, but see, if NVIDIA's sources reference parts of
> the kernel headers which aren't guaranteed to stay stable, well...)
with your old kernel, header files and toolchain and all will
be well.
(Sorry for the irony, but see, if NVIDIA's sources reference parts of
the kernel headers which aren't guaranteed to stay stable, well...)
Cheers
--
t
signature.asc
Description: PGP signature
Am Dienstag, 8. März 2022, 00:25:54 CET schrieb Stefan Monnier:
No, you are completzely wrong! It is not Nvidia to blam,e when COMPILING
fails! It is NOT Nvidia to blame, when the packages are REMOVED from the repo,
because your KERNEL breaks the compiling! And it is NOT Nvidia to blame, when
, without being upset or stepping on someones
> > feet. But I believe, debian hates Nvidia, and debian does not want, to
> > use Nvidia.
> >
> > I am now for a long time using debian and also using nvidia graphic cards
> > for almost the same long time.
>
eeding to install, then "removing", NVidia's
proprietary drivers. I have a bunch of old NVidia cards, 8 years old and older.
All are running purely on FOSS:
1-the nouveau kernel device driver/module
2-the modesetting DIX display device driver (usually; optionally: nouveau DDX)
#2 is the
long time.
But whenever debian ships a new kernel version, the proprietrary nvidia kernel
modules can not be built. If lucky, there is a patch for it after months.
Yes, modern Nvidia cards are supported, but using an older notebook you can
not change the graphics card.
...
I have several older
em with
> nvidia quite well.
>
Yes, good idea.
> 1. You are probably not talking about Debian stable and the kernel that
> ships with it. I have not checked, but the binary nVidia packages almost
> certainly have not disappeared from Debian stable non-free within a
> release cycle. N
to your situation. I leave them in my text
though, because in my opionion they describe the general problem with
nvidia quite well.
1. You are probably not talking about Debian stable and the kernel that
ships with it. I have not checked, but the binary nVidia packages almost
certainly have
ships a new kernel version, the proprietrary nvidia kernel
modules can not be built. If lucky, there is a patch for it after months.
Yes, modern Nvidia cards are supported, but using an older notebook you can
not change the graphics card.
But this is not a problem of Nvidia, not IMO
iempos de cada uno que serán
tan apretados como los míos, muy elogiable pues regalarle atención
a un
desorientado! Ya me había rendido.
Ya probé, Leonardo, con firmware-misc-nonfree y no hay caso. Por eso
pensé en el Kernel pero desistí por la correcta opinión de varios.
entien
firmware-misc-nonfree y no hay caso. Por eso pensé
en el Kernel pero desistí por la correcta opinión de varios.
El 25/2/22 a las 05:39, Leonardo Marín escribió:
El vie, 25 feb 2022 a las 4:50, Camaleón (mailto:noela...@gmail.com>>) escribió:
(...)
> Pude hacer funcionar casi t
e y no hay caso. Por eso pensé
> en el Kernel pero desistí por la correcta opinión de varios.
>
> El 25/2/22 a las 05:39, Leonardo Marín escribió:
> >
> > El vie, 25 feb 2022 a las 4:50, Camaleón ( > <mailto:noela...@gmail.com>>) escribió:
(...)
> >
Hola y otra vez gracias, me imagino los tiempos de cada uno que serán
tan apretados como los míos, muy elogiable pues regalarle atención a un
desorientado! Ya me había rendido.
Ya probé, Leonardo, con firmware-misc-nonfree y no hay caso. Por eso
pensé en el Kernel pero desistí por la correcta
El vie, 25 feb 2022 a las 3:04, Daniel ()
escribió:
> Muchas gracias por las recomendaciones!!
>
> El uso del equipo es familiar y de trabajo no experimental digamos.
>
> Mi idea era (tal vez una locura) agregar el repositorio Testing,
> actualizar el kernel, solamente e inm
L15 Gen 2" con i5-1135G7. Instalado
> > Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
> instalación
> > básica, sólo agregado Synaptic y poco más.
> >
> > Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6
> MT7921).
>
> (..
El 2022-02-25 a las 00:04 -0300, Daniel escribió:
> Hola. Consulta bastante de novato, disculpas por eso (uso consola pero me
> suelo manejar mas en GUI).
>
> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
> Debian 11, kernel 5.10.0.11-amd64, KDE
Saludos:
No creo vayas a solucionar tú problema actualizando el kernel. Para mi es un
clásico que después de que caiga en mis manos un portátil diferente tenga que
instalar un firmware propietario para el dispositivo wifi sea reconocido y
poder trabajar con él. En tu caso (MediaTek) parece que
Muchas gracias por las recomendaciones!!
El uso del equipo es familiar y de trabajo no experimental digamos.
Mi idea era (tal vez una locura) agregar el repositorio Testing,
actualizar el kernel, solamente e inmediatamente quitar dicho repositorio.
Evaluaré el consejo, sí, de conseguir una
El vie, 25 feb 2022 a las 0:04, Daniel ()
escribió:
> Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
> me suelo manejar mas en GUI).
>
> Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
> Debian 11, kernel 5.10.0.11-amd6
GUI).
Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
instalación básica, sólo agregado Synaptic y poco más.
Pude hacer funcionar casi todo, pero no el WiFi (MediaTek Wi-Fi 6 MT7921).
Tengo in
Hola. Consulta bastante de novato, disculpas por eso (uso consola pero
me suelo manejar mas en GUI).
Tengo una Notebook Lenovo "ThinkPad L15 Gen 2" con i5-1135G7. Instalado
Debian 11, kernel 5.10.0.11-amd64, KDE Plasma 5.20.5. Por ahora
instalación básica, sólo agregado Synaptic
Hi,
> I just wrote about two places where Debian kernel packages with
> "trunk" in their names are visible. But I do not know what those
> packages are. If you can explain what those packages are,
> what their life cycle is, and why they are named "trunk", that
>
On Mi, 16 feb 22, 00:50:21, David wrote:
>
> I just wrote about two places where Debian kernel packages with
> "trunk" in their names are visible. But I do not know what those
> packages are. If you can explain what those packages are,
> what their life cycle is, and
t* tools can only find what's indexed in dists/ rather
> >> than anything that happens to be in the pool, but I'm not familiar
> >> with the policy issues (as a non-developer). I don't think dpkg
> >> makes that its business at all.
> >
> >> BTW the red line (at
. I don't think dpkg
>> makes that its business at all.
>
>> BTW the red line (attached) indicates that "trunk" doesn't appear
>> on the page. (It's a term I don't understand.)
>
> I found an explanation of "trunk" in Section 5.2.1 here:
> https:/
"trunk" doesn't appear
> on the page. (It's a term I don't understand.)
I found an explanation of "trunk" in Section 5.2.1 here:
https://kernel-team.pages.debian.net/kernel-handbook/ch-versions.html
I don't know what I'm talking about, but it looks like "trunk" pack
have a bad BIOS, and wish to boot with more than one connected
> >>> display.
> >>> https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the
> >>> issue, which
> >>> has just been announced fixed. But, it appears the fix may only be
> >
>> display.
>>> https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue,
>>> which
>>> has just been announced fixed. But, it appears the fix may only be landing
>>> in
>>> kernel 5.17rc3.
...
> # aptitude search linux-image
...
> p lin
the issue,
>> which
>> has just been announced fixed. But, it appears the fix may only be landing in
>> kernel 5.17rc3.
>> I tried to get the latest available kernel that is packaged by Debian people
>> by
>> reading on
>> https://wiki.debian.org/HowToU
e,
> > which
> > has just been announced fixed. But, it appears the fix may only be landing
> > in
> > kernel 5.17rc3.
> >
> > I tried to get the latest available kernel that is packaged by Debian
> > people by
> > reading on
> >
> &g
he fix may only be landing in
> kernel 5.17rc3.
>
> I tried to get the latest available kernel that is packaged by Debian people
> by
> reading on
>
> https://wiki.debian.org/HowToUpgradeKernel
> https://wiki.debian.org/DebianExperimental
>
> I put
&g
...if you have a bad BIOS, and wish to boot with more than one connected
display.
https://gitlab.freedesktop.org/drm/intel/-/issues/4762 explains the issue, which
has just been announced fixed. But, it appears the fix may only be landing in
kernel 5.17rc3.
I tried to get the latest available
ny to display (perhaps > ~100).
> It says: "Your keyword was too generic.
> Please consider using a longer keyword or more keywords."
> So changing your search to linux-image-5.10.0 gives 51 matches,
> and linux-image-5.10.0 amd64 cuts it down to 18.
>
>> B
t;
So changing your search to linux-image-5.10.0 gives 51 matches,
and linux-image-5.10.0 amd64 cuts it down to 18.
> But search for ‘kernel-image’ shows results on the website.
Sure, but they all end in -di, which stands for debian-installer,
and if you click through to one of them,
-amd64
...
--8<---cut here---end--->8---
But on ‘packages.debian.org’ search for ‘linux-image’ in stable gives
zero result. But search for ‘kernel-image’ shows results on the
website. But ‘apt search kernel-image’ shows zero results on CLI.
I am using
it into swapping, which indeed is not ideal..
I am modifying my code to batch this procedure to lower the gargantuan
memory requirements of my image registration task, but in the meantime, for
processes with large memory requirements that may occasionally need to
swap, I found this kernel tuning at least
On 28.01.22 22:55, Tixy wrote:
On Fri, 2022-01-28 at 17:31 +0100, Marco Möller wrote:
On 28.01.22 11:15, Steven J. West wrote:
Comparing the Ubuntu and Debian kernel parameters using sudo sysctl
-a
showed two key differences in virtual memory (vm) management
parameters.
* Ubuntu:
o
community (thanks!) you should probably send this either to
debian-kernel or file it as a bug against the source package 'linux'.
(reportbug should do this by default if you point it to any linux-image
package you have installed)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
lowed down/essentially froze.
>
> After much debugging, I have traced this to the vm.watermark_boost_factor
> kernel parameter:
>
> Comparing the Ubuntu and Debian kernel parameters using sudo sysctl -a
> showed two key differences in virtual memory (vm) management parame
On Fri, 2022-01-28 at 17:31 +0100, Marco Möller wrote:
> On 28.01.22 11:15, Steven J. West wrote:
> > Comparing the Ubuntu and Debian kernel parameters using sudo sysctl
> > -a
> > showed two key differences in virtual memory (vm) management
> > parameters.
>
On 28.01.22 11:15, Steven J. West wrote:
Comparing the Ubuntu and Debian kernel parameters using sudo sysctl -a
showed two key differences in virtual memory (vm) management parameters.
* Ubuntu:
o vm.swappiness=60
o vm.watermark_boost_factor=0
* Debian:
o vm.swappiness=10
on Debian, whenever SWAP was needed, the system
processing significantly slowed down/essentially froze.
After much debugging, I have traced this to the vm.watermark_boost_factor
kernel parameter:
Comparing the Ubuntu and Debian kernel parameters using sudo sysctl -a
showed two key differences
ation of $50 billion as of September 2021 comes
> > > here for help on upgrading the kernel on an old Debian system?
> >
> > Many questions on this list originate from businesses using Debian
> > internally.
> >
> > Are you suggesting this shouldn't be al
Bonjour,
Je t'ai répondu hier sur un autre fil. Avec la bonne version des
pilotes, tu aurais un peu plus de chance ;)
Au sujet des fils de discussion, répondre sur un fil en changeant le
sujet ne crée pas un nouveau fil de discussion.
Des logiciels comme Thunderbird, qui se basent sur
Désolé, mais à la lecture de tes réponses, je pense sincèrement que la
solution la plus simple et fonctionnelle pour toi c'est de réinstaller
un Debian amd64 (un vrai, pas un multiarch comme tu as) à partir d'un
media incluant les firmwares, avec de préférence le bureau KDE Plasma
(pas Trinity)
I found that this is a bug of kernel module "rtl8723ae"
and it also happens on kernel 5.10
i wasn't able to pin it out because i updated packages right after i
installed it
i was able to find related thread on askubuntu
https://askubuntu.com/questions/846830/irq-from-realtek-wifi-are-l
On Monday 03 January 2022 10:43:43 didier gaumet wrote:
> Le dimanche 02 janvier 2022 à 23:23 +0100, ajh-valmer a écrit :
> > (Xorg ne semble pas se lancer).
> > Ma carte vidéo est une Nvidia geforce GE 6150 nforce 430.
> > Quel est le mode opératoire avec "xserver-xorg-video-nouveau" ?
> > je
470.94 du site Nvidia :
https://www.nvidia.fr/Download/driverResults.aspx/184177/fr
Comme le paquet nvidia-legacy-340-driver :
https://packages.debian.org/fr/sid/nvidia-legacy-340xx-alternative est
encore en SID, tu peux peut-être t'en servir avec le kernel 5.10. Sinon,
tu peux aussi essayer le
On Sat 18 Dec 2021 at 12:36:49 (+0100), Andrei POPESCU wrote:
> On Jo, 16 dec 21, 09:53:33, David Wright wrote:
> >
> > Anyone think it ironic that a multinational IT company with a
> > market capitalisation of $50 billion as of September 2021 comes
> > here for h
On Fri, Dec 31, 2021, 4:27 PM _ djdisodo wrote:
> note that i'm using debian sid and xfce4
>
> it shows full of red bars on htop on one of the core between two(i
> have atom n455 cpu)
> iirc red bars means kernel threads
>
> i've tested using debian's boot menu so only th
note that i'm using debian sid and xfce4
it shows full of red bars on htop on one of the core between two(i
have atom n455 cpu)
iirc red bars means kernel threads
i've tested using debian's boot menu so only thing changed is kernel version
it was fine on kernel 5.10 it's happening on kernel 5.14
io Nvidia.
> Si je tente de le lancer, refus car le système dit que je dois
> désinstaller
> un module nvidia, ce que je fais, et le message revient.
>
> - Au boot, j'ai ce message : "Failed to start kernel module" (Quid
> ?).
>
> Pour moi, le passage à Bullseye est
a monter à 1024x1024.
Avant ça marchait avec le pilote proprio Nvidia.
Si je tente de le lancer, refus car le système dit que je dois désinstaller
un module nvidia, ce que je fais, et le message revient.
- Au boot, j'ai ce message : "Failed to start kernel module" (Quid ?).
Pour moi, le passage à Bullseye est pas fini et problèmatique...
Help !
A. Valmer
On Fri, 17 Dec 2021, Balasubramanian Ravuthan wrote:
Hi Dan,
Thanks for your reply. We need few more information.
1. Debian 10 Buster is not released with Linux Kernel 5.10 ; That means We
cant upgrade Kernel 5.10 with Debian 10? - Please confirm.
As Dan says, it's in backports. I've
On Sat, Dec 18, 2021, 04:37 Andrei POPESCU wrote:
> Free(dom) Software was never meant to exclude comercial use or
> developers earning a living (or a fortune) from it.
>
>
> Agreed,.Andrei!
>
>
On Jo, 16 dec 21, 09:53:33, David Wright wrote:
>
> Anyone think it ironic that a multinational IT company with a
> market capitalisation of $50 billion as of September 2021 comes
> here for help on upgrading the kernel on an old Debian system?
Many questions on this list or
On Jo, 16 dec 21, 16:12:37, to...@tuxteam.de wrote:
> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> > Hi Team,
> >
> > We are looking support from you on the Linux Kernel upgrade on Debian
> > 10. Please help on this.
>
> Thi
On Mi, 15 dec 21, 10:33:05, David wrote:
> On Wed, 15 Dec 2021 at 03:18, Kiyanovski, Arthur wrote:
>
> > TL;DR - How do I get the Linux headers or source code for kernel
> > 3.16.0-4-amd64 Debian 8.0?
>
> The version number of a Debian kernel package is not the sam
Hi,
Balasubramanian Ravuthan wrote:
> 1. Debian 10 Buster is not released with Linux Kernel 5.10 ; That means We
>cant upgrade Kernel 5.10 with Debian 10? - Please confirm.
No.
There are kernel source packages of 5.10 in backports
https://packages.debian.org/buster-backports/linux-
Hi Dan,
Thanks for your reply. We need few more information.
1. Debian 10 Buster is not released with Linux Kernel 5.10 ; That means We
cant upgrade Kernel 5.10 with Debian 10? - Please confirm.
2.
3. In order to upgrade Linux Kernel to 5.10 means we have to install Debian
11
On 12/16/21, David Wright wrote:
> On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
>> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
>> > Hi Team,
>> >
>> > We are looking support from you on the Linux Kernel upg
Balasubramanian Ravuthan wrote:
>
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
>
> We are currently using Debian10 Buster Linux Kernel 4.19 version and trying
> to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact
>
On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> > Hi Team,
> >
> > We are looking support from you on the Linux Kernel upgrade on Debian
> > 10. Please help on this.
On 2021-12-16 16:04 UTC+0100, Balasubramanian Ravuthan wrote:
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
>
> We are currently using Debian10 Buster Linux Kernel 4.19 version and
> trying to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is
Hi Debian Team,
We are looking support from you on the Linux Kernel upgrade on Debian 10.
We are currently using Debian10 Buster Linux Kernel 4.19 version and trying to
upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact on
this upgrading.
In other words, what
On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> Hi Team,
>
> We are looking support from you on the Linux Kernel upgrade on Debian 10.
> Please help on this.
This is a user's list, not a support channel.
If you have concrete questions, you can po
401 - 500 of 45262 matches
Mail list logo
