Daniel Rodriguez writes:
> The solution of the post to this issue is to update the kernel from
> 6.1.0-13 -> 6.1.0.18; however, my kernel is a later version:
> 6.1.0-21-amd64, so I am stuck for solving this issue. Do you have any
> idea about what may be happening and/or how
magic bytes at the start
> Error! Bad return status for module build on kernel: 6.1.0-21-amd64
> (x86_64)
> Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more
> information.
> dpkg: error processing package nvidia-kernel-dkms (--configure):
> installed nvidia-
Hi,
a while ago I reported a bug against the kernel (Bug#1070717). But the bug
isn't limited to that kernel version and not even to the Debian kernel. The
same even happens when I e.g. compile Linux 9.3 from sources, using the config
from Debian's 6.6.15 - the latest version I tried
many java dev ecosystem (such as big data stacks) are in debian 11.
it's hard to upgrade to 12 at this time.
Thanks.
Keep in mind that Debian 11 will be out of oldstable in about a year,
with the release of 13/Trixie; and it will be out of security support
in a few weeks, with the transition
On 9 Jun 2024 07:41 +0800, from j...@tls-mail.com (Jeff Peng):
> debian 11 installed.
Keep in mind that Debian 11 will be out of oldstable in about a year,
with the release of 13/Trixie; and it will be out of security support
in a few weeks, with the transition to long-term support. Depending on
On Sun, Jun 09, 2024 at 06:58:21AM +0200, to...@tuxteam.de wrote:
> On Sun, Jun 09, 2024 at 07:41:58AM +0800, Jeff Peng wrote:
> > Hello
> >
> > I am using the VMs from big providers such as AWS and Azure.
>
> I'd ask AWS/Azure support for that.
Yes, talking _with_ your vendor is the way to go.
On Sun, Jun 09, 2024 at 07:41:58AM +0800, Jeff Peng wrote:
> Hello
>
> I am using the VMs from big providers such as AWS and Azure.
I'd ask AWS/Azure support for that. They do knowi their infrastructure
best, we hope, and, after all, they are taking money for their service.
Cheers
--
t
configuration.
Do I need to update some kernel config for the VMs? such as
socket_buffer, max_fd etc. what's the suggested options for this kind
of VM?
Thanks.
If your applications work correctly and with acceptable response time
then don't change anything.
Jeremy
kernel config for the VMs? such as
socket_buffer, max_fd etc. what's the suggested options for this kind of
VM?
Thanks.
On Mon, Jun 3, 2024 at 8:52 PM wrote:
> On 6/3/24 09:40, Tom Browder wrote:
> > I keep getting emails concerning the serious kernel vulnerability in
> > kernels 5.14 through 6.6.
> >
> > I have not seen any updates and uname -a shows: 6.1.0-13-amd64
> On 6/3/24 0
metapackage, which means
you will not be offered new kernel versions automatically. This isn't
technically "wrong", but it's not (or should not be) a common choice.
eben@cerberus:~$ apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: 6.1.90-1
Candidate: 6.1.90-1
Excellent,
which means
you will not be offered new kernel versions automatically. This isn't
technically "wrong", but it's not (or should not be) a common choice.
On 6/3/24 09:40, Tom Browder wrote:
I keep getting emails concerning the serious kernel vulnerability in
kernels 5.14 through 6.6.
I have not seen any updates and uname -a shows: 6.1.0-13-amd64
On 6/3/24 09:40, Tom Browder wrote:
I keep getting emails concerning the serious kernel
On 3 Jun 2024 11:29 -0500, from tom.brow...@gmail.com (Tom Browder):
> Thanks for your concern and help.
You're welcome. Glad you got it sorted.
--
Michael Kjörling https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
On Mon, Jun 3, 2024 at 09:15 Michael Kjörling <2695bd53d...@ewoof.net>
wrote:
> On 3 Jun 2024 08:40 -0500, from tom.brow...@gmail.com (Tom Browder):
> > I keep getting emails concerning the serious kernel vulnerability in
> > kernels 5.14 through 6.6.
> >
> > I ha
also double-checked, and 6.1.0-13 is indeed the ABI version
immediately preceding the kernel bugs incident. The kernels affected
by that in mainline Debian were 6.1.0-14/6.1.64* and 6.1.0-15/6.1.66*;
the latter by unrelated bug #1057967 which may or may not affect you.
This further reinforces my belief
, Michael.
My system is a remote host, and I'm in the process of a reinstall on one.
If I correctly read the links you sent, the latest kernel has that CVE
covered.
But another remote host seems to have the same problem. Each host comes
from a different provider and had slightly different default
On 3 Jun 2024 08:40 -0500, from tom.brow...@gmail.com (Tom Browder):
> I keep getting emails concerning the serious kernel vulnerability in
> kernels 5.14 through 6.6.
>
> I have not seen any updates and uname -a shows: 6.1.0-13-amd64
Something's broken on your end.
Bookworm is curr
I keep getting emails concerning the serious kernel vulnerability in
kernels 5.14 through 6.6.
I have not seen any updates and uname -a shows: 6.1.0-13-amd64
Anyone concerned?
-Tom
On 5/31/24 10:04, Evgeny Kapun wrote:
After I upgraded my system, my integrated sound card (Intel HDA) stopped
working properly. The sound plays, but it is severely distorted.
If I boot the same system with an older kernel, it works. Currently, I am
using kernel 6.6.13+bpo-amd64, because newer
After I upgraded my system, my integrated sound card (Intel HDA) stopped
working properly. The sound plays, but it is severely distorted.
If I boot the same system with an older kernel, it works. Currently, I
am using kernel 6.6.13+bpo-amd64, because newer versions that I tried
don't work
Le lundi 27 mai 2024 à 19:32 +0200, Sébastien Villemot a écrit :
> I recently bought a ThinkPad X13 Gen5 (benefiting from the discount
> generously offered by Lenovo to Debian Developers).
> However, I still can’t get the touchpad to work. It is apparently not
> recognized by the k
On Mon, 27 May 2024 at 17:39, Sébastien Villemot wrote:
> I recently bought a ThinkPad X13 Gen5 (benefiting from the discount
> generously offered by Lenovo to Debian Developers).
>
> The laptop runs Debian Bookworm, and I got almost all the hardware to
> work by using mor
Hi,
I recently bought a ThinkPad X13 Gen5 (benefiting from the discount
generously offered by Lenovo to Debian Developers).
The laptop runs Debian Bookworm, and I got almost all the hardware to
work by using more recent kernel and firmware files (see Debian bug
reports #1070647, #1070648
On 17 May 2024 00:12 +0700, from maniku...@gmail.com (Max Nikulin):
> Be realistic, to get the bug fixed, there should be affected persons
> motivated enough to try vanilla kernel or even to build custom kernels with
> provided patches. Developers time is limited and expensive resourc
On 16/05/2024 22:53, piorunz wrote:
https://bugzilla.kernel.org/ will they be interested in Debian specific
error? I don't use vanilla kernel so maybe it's Debian only problem.
If you *find* a similar report there then it is likely an upstream
issue. (Developers of specific driver may use
On 16/05/2024 12:35, Max Nikulin wrote:
On 16/05/2024 17:35, piorunz wrote:
As much as I would like to try vanilla kernel, I don't want to break my
system. I use Debian Stable, don't know if things would just work with
vanilla kernel.
You may try bookworm-backports kernel 6.6.13+bpo-amd64
On 16/05/2024 17:35, piorunz wrote:
As much as I would like to try vanilla kernel, I don't want to break my
system. I use Debian Stable, don't know if things would just work with
vanilla kernel.
You may try bookworm-backports kernel 6.6.13+bpo-amd64
You may check https://bugzilla.kernel.org
scenario with the vanilla kernel.org kernels of the same
versions; confirming that the issue exists with the vanilla 6.1.90
kernel _and_ that the issue goes away when booting the vanilla kernel
of whatever exact version your earlier package is (I'm guessing
6.1.85), both when built with the same
ср, 15 мая 2024 г. в 16:55, Hans :
> Dear developers,
Users.
> in April 2024 the security hole CVE-2023-6546 was discovered in linux-image,
> and I believe, it is fixed in kernel 6.1.0 (from debian/stable) as soon after
> this a new kernel was released.
https://security-tracke
On 15 May 2024 20:40 +0100, from pior...@gmx.com (piorunz):
> I have reported a regression in latest Linux kernel in Debian Stable:
>
> segfault at amdgpu_dm_atomic_commit_tail
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080
You made this bug report less than 48 hours
Hello,
I have reported a regression in latest Linux kernel in Debian Stable:
segfault at amdgpu_dm_atomic_commit_tail
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080
It throws a lot of errors related to AMD GPU every day. I also
experienced full desktop hang, where I had to restart
On 2024-05-15 at 03:05, Hans wrote:
> Dear developers,
As usual, most of us here are not Debian developers, even if some of us
may be software developers.
> in April 2024 the security hole CVE-2023-6546 was discovered in linux-image,
> and I believe, it
> is fixed in kernel 6.1.0
Dear developers,
in April 2024 the security hole CVE-2023-6546 was discovered in linux-image,
and I believe, it
is fixed in kernel 6.1.0 (from debian/stable) as soon after this a new kernel
was released.
However, there is no new kernel 6.5.0-*-bpo released at that time, so my
question
On 16/04/2024 16:17, Michael Kjörling wrote:
I have a handful of Debian 12 systems that I want to configure such
that they reboot automatically in case of a problem.
[...]
That leaves kernel-level issues.
I have not tried it, but I have seen some systemd options related to
configuration
On 16/04/24 at 11:17, Michael Kjörling wrote:
Do I need to set some more settings to ensure that the system will
automatically reboot on a panic? If so, what?
Hi,
In the Linux kernel source are available two options to reboot on panic:
config BOOTPARAM_SOFTLOCKUP_PANIC
bool "
On 16 Apr 2024 11:42 +0200, from geo...@nsup.org (Nicolas George):
>> Are you saying that the settings themselves are reasonable for the
>> purpose, and that this particular crash just happened to be such a one
>> that no software running on the system in question can reasonably help
>> with that
Michael Kjörling (12024-04-16):
> Are you saying that the settings themselves are reasonable for the
> purpose, and that this particular crash just happened to be such a one
> that no software running on the system in question can reasonably help
> with that scenario?
No, unfortunately I do not
On 16 Apr 2024 11:22 +0200, from geo...@nsup.org (Nicolas George):
>> Do I need to set some more settings to ensure that the system will
>> automatically reboot on a panic? If so, what?
>
> If the crash was bad enough to freeze the kernel before it could
> trigger the reb
Michael Kjörling (12024-04-16):
> However, this morning I woke up to one of those systems showing a
> kernel crash dump and being frozen. Unfortunately the first part of
> the crash dump had scrolled past so I couldn't tell what class of
> problem caused the crash.
>
> Do I nee
scripts check for. That leaves kernel-level
issues.
To try to configure this, I have created a file
/etc/sysctl.d/local.conf (owned by root:root, mode 0644).
# cat /etc/sysctl.d/local.conf
kernel.panic = 120
kernel.panic_on_oops = 1
kernel.panic_on_stackoverflow = 1
kernel.panic_on_io_nmi = 1
Hola,
Lo acabo de leer y creo que es convieniente tener este tipo de hitos en
el radar, aunque no creo que el uso de ext2 actualmente esté muy
extendido, sí puede afectar en situaciones específicas:
La nota, en español y un buen artículo técnico en inglés, con opciones
y alternativas al uso
log:Mar 15 05:06:18 strange kernel: [2740248.159942]
> finger[1987858]: segfault at 1c ip 55b1c20baad5 sp
I had similar problems in my Raspberry Pi running native Debian arm64,
I have filed this bug about it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018879
/ralph
I use tmux on my server. tmux creates multiple pttys. When I run
finger, I see an error like this:
$ finger
finger: /dev//pts/6: No such file or directory
and in the log, I see:
/var/log/syslog:Mar 15 05:06:18 strange kernel: [2740248.159942]
finger[1987858]: segfault at 1c ip
This is a post meant to help anyone who finds his/her system unbootable
- as I did - after updating to the latest version of the testing stream
which comes with a 6.6.13-amd64 kernel.
When I updated last week, my system refused to boot. Checking revealed
that the system-load-modules service
to install
a 5.10 kernel instead of 6.1 even though backports is included in sources.list?
I'm using sources as shown on
https://gist.github.com/gustavorv86/d60a25ad5f70b0dfc382670d3dc6da8d
except omitting the deb-src lines.
--
Evolution as taught in public schools is, like religion,
based
On Sat, Feb 10, 2024 at 01:21:55PM +, Schwibinger Michael wrote:
> Yes.
>
>
> I found out
> I do use an old kernel.
>
> Can LINUX update a kernel?
>
Hi Sophie,
Yes, of course. As root/sudo user, apt-get update ; apt-get dist-upgrade
But you still don't give any
Tim Janssen wrote:
> I use debian server on my NUC to run a low powered home server. It freezes
> every 2-3 days what looks to be a kernel bug. From a lot of testing it only
> occurs when the ethernet cable is inserted and it seems it has to do
> something with low power mo
Dear Sir/Madam,
I use debian server on my NUC to run a low powered home server. It freezes
every 2-3 days what looks to be a kernel bug. From a lot of testing it only
occurs when the ethernet cable is inserted and it seems it has to do
something with low power mode (c-states). These issues have
On 05/02/2024 17:40, Dmitry wrote:
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during
Linux installation.
That advice may be standard for distributions that do not provide signed
shim and grub. Likely it is applicable for Arch
On Mon, 2024-02-05 at 17:40 +0700, Dmitry wrote:
>
> But secure boot is usually turned off. It is a standard advice during
> Linux
> installation.
>
Will probably be increasingly common though, I've got a Microsoft
Surface Laptop that works fine with Debian, but if you switch off
secure boot,
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during Linux
installation.
sudo -i
Thank you!
I am unsure what UUID you mean.
At Manjaro:
grubx64.efi is at the sdb1 - EFI vfat /dev/sdb1
grub.cfg is at the sdb2 - crypto_LUKS /dev/sdb2
grubx64.efi contains data UUID=""a8...b7" of /dev/sdb2 which is
TYPE="crypto_LUKS".
`blkid` output:
/dev/sdb2: UUID="a8...b7"
On 03/02/2024 22:32, Dmitry wrote:
2. sudo bash
sudo -i
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
I am unsure what UUID you mean.
Summary: GRUB installation not only involves configuration of text
files, but
also it
WRT non-removable media, only
one
bootloader per machine is required, and pretty well stuck to having only one
active, or at all, no matter how many FOSS operating systems or media I have
installed. The Grubs I have used are not picky about whose kernel or initrd they
are called to load. With o
, there was a bug in an older version of xen that caused a
kernel oops if wifi networking was started. So I wanted to start vanilla
debian and I don't dare touch the NVRAM again (or the bios) until I
absolutely have to.
I don't remember for certain now but I might be booting using
bootx86.efi (which
entre le SMB de syno
et le noyau*6.1.0-17*, car avec le noyau *6.1.0-10* pas de soucis.
Apriori tester de ton côté le SMB, amènera certainement un "crash
kernel" je pense.
Par contre sur le syno, la version de samba est (un peu ancienne) :
Version 4.15.9
Synology Build 42934, Jul 5
Main question is resolved.
GRUB knows how to reach grub.cfg because grubx64.efi binary has the UUID and
path to grub configurations.
1. sudo blkid;
2. sudo bash
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
Summary: GRUB
bonjour
Pas de pb constaté pour ma part. Peut-être que le fautif serait le serveur?
Pour ma part :
erwann@inspiron:~$ uname -a
Linux inspiron *6.1.0-17-amd64* #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1
(2023-12-30) x86_64 GNU/Linux
erwann@inspiron:~$ grep synology /etc/fstab
On 03/02/2024 02:15, Tim Woodall wrote:
$ cat /boot/efi/EFI/XEN/xen.cfg
[...]
I'd be interested if there's a way to tell grubx64.efi to look for a
particular partition UUID.
An example of such grub.cfg from EFI/debian has been posted already in
this thread
On 03/02/2024 02:51, Thomas Schmitt wrote:
Max Nikulin wrote:
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi)
to the ESP partition on the USB stick.
The /EFI/boot directory of a bootable Debian ISO usually does not contain
the full GRUB equipment for EFI. Important parts of
J'ai tenté les trois options de montage mais pas mieux.
Le log du crash noyau est quasi identique.
Ça semble venir du noyau 6.1.0-17.
Car avec le noyau 6.1.0-10, pas de problèmes
Je vais rester sur le noyau précédent...
Cdlt
On 01/02/2024 10:11, Michel Verdier wrote:
Le 31 janvier 2024
On 02/02/24 at 15:12, Dmitry wrote:
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
Nope, maybe you gave a quick read, the release notes of the current
release ¹ are exhaustive. If
.> I need to prepare that system for booting.
>...> 1. Install Kernel.
>...> 2. Install GRUB and Configure.
>...> 3. Add changes to UEFI to start booting.
dd-ing a bootable Debian ISO will not do what you describe.
Assumed the ISO is prepared for booting from USB stick
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
$ cat /boot/efi/EFI/XEN/xen.cfg
[global]
default=debian
[debian]
options=console=vga smt=true
kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
ramdisk=initrd.img
menuentry "Xen EFI
On Sat, Feb 03, 2024 at 01:17:05AM +0700, Dmitry wrote:
> > Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
> ESP partition on the USB stick.
>
> As I understand right now `dd` command applied to a device will copy all
> information including partitions table. Thus:
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Yep. `dd` copy partitions table. Amazing.
```
dd will simply recreate the old partition scheme, as it is a bitwise copy &
applies no 'intelligence' to the operation.
```
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
As I understand right now `dd` command applied to a device will copy all
information including partitions table. Thus:
dd if=debian-xx.iso of=/dev/sdb bs=4M status=progress; sync
Would
On Fri 02 Feb 2024 at 21:12:30 (+0700), Dmitry wrote:
> Going to read carefully.
>
> https://www.debian.org/releases/buster/amd64/ch04s03.en.html
>
> Interesting that Buster has more documentation than current release.
It appears the balance has now been spun off into a wiki page, at
On 02/02/2024 21:06, Dmitry wrote:
Need additional research what to do with a FlashStick with several
partitions to make a LiveCD from it.
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
> Do you want to install the OS on it?
Eventually no, I do not want OS on the Flash Stick.
The Flash Stick is only a testing place. I want OS at the SSD.
Now I am wondering how to prepare the Flash Stick to write LiveImage on it.
Because I already created a GPT table on that Flash and use
Am 02.02.2024 schrieb Dmitry :
> I want OS at the SSD.
Then the ESP should be on that SSD too.
Max Nikulin schrieb:
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot without modification of boot entries in NVRAM.
Yes, UEFI can (and must be able) to boot from a device without a boot
entry in the UEFI.
On 02/02/2024 01:46, Dmitry wrote:
3. Now I want to boot using that Flash.
1. ESP is a partition that stores GRUB Binary. /boot/EFI/Name/grub64.eif
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
> $ cat /boot/efi/EFI/XEN/xen.cfg
> [global]
> default=debian
>
> [debian]
> options=console=vga smt=true
> kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
> ramdisk=initrd.img
>
>
> menuentry "
debian/grub.cfg
search.fs_uuid 5b8b669d-xyz root hd0,gpt2 #boot partition
set prefix=($root)'/grub'
configfile $prefix/grub.cfg
root@ryz:/boot/efi/EFI#
If that information is loaded, the kernel can be loaded from the boot
partition.
Are you sure that file does anything? I don't have one
drwxr-xr-x
ftp://einstein/local stretch main
EOFX
echo link_in_boot = Yes >/etc/kernel-img.conf
apt-get update
apt-get -y upgrade
apt-get -y install sysvinit-core
apt-get -y install openssh-server
apt-get -y install ifupdown
apt-get -y install grub-efi-amd64
apt-get -y install mdadm
apt-get -y instal
root hd0,gpt2 #boot partition
set prefix=($root)'/grub'
configfile $prefix/grub.cfg
root@ryz:/boot/efi/EFI#
If that information is loaded, the kernel can be loaded from the boot
partition.
--
Gruß
Marco
Spam und Werbung bitte an ichschickerekl...@cartoonies.org
Hi Tim. The community is so kind.
So.
> I'm not exactly sure what you're doing.
Understand how GRUB works, to boot myself.
1. Trying to install Debian on the Flash.
2. Use it by the Debootstrap.
3. Now I want to boot using that Flash.
Looks like a caught the thread.
1. ESP is a partition
you want an encrypted system?
> > Do you need a special configuration here or is the default just
> > fine?
>
> Need just working one. But I am confusing about how GRUB would get a
> plenty of things related to filesystem, kernel location and so on.
That is being done
EFI/Majaro/grub64x.efi - binary to start by UEFI.
/boot/grub/grub.cfg - shell (?) script with configurations.
/boot/vimlinuz.* - the kernel.
And if call a `lsblk`.
Only a /boot/efi with a binary is a separate partiton.
Things become more clear.
On Thu, 1 Feb 2024, Dmitry wrote:
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI
n here or is the default just fine?
Need just working one. But I am confusing about how GRUB would get a
plenty of things related to filesystem, kernel location and so on.
> If you create a separate boot partition (do you really need it?), it
must be mounted at /boot.
Here where the mess starts.
also
https://www.rodsbooks.com/gdisk/advice.html#esp_sizing
https://fedoraproject.org/wiki/Changes/BiggerESP
2. Need to configure GRUB to select appropriate kernel and ramdisk.
Do you need a special configuration here or is the default just fine?
EFI/debian/grub.cfg on the EFI System Partitio
point two (Install GRUB) I a little bit confused.
>
> 1. Need to create ESP
Do that before the install with gdisk.
> and put GRUB there.
That is done automatically if it is mounted at /boot/efi.
> 2. Need to configure GRUB to select appropriate kernel and ramdisk.
Do you need a speci
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to start booting.
And at the point
Le 31 janvier 2024 testeur a écrit :
> voici les droits du montage :
>
> ├─/mnt/xxx /etc/autoxxx.smb
>autofs
> rw,relatime,fd=12,pgrp=1561,timeout=30,minproto=5,maxproto=5,indirect,pipe_ino=22915
> │ └─/mnt/xxx/conf
>
actuel de debian 12 : Linux vfpm 6.1.0-17-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
Dans syslog, j'obtiens des erreurs au niveau du kernel.
2024-01-29T21:20:24.524146+01:00 vfpm kernel: [ 7967.200355] BUG: kernel
NULL pointer dereference, address: 00
Hi Sven,
Sven Joachim writes:
> On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
>
>> (Please keep me in CC as I'm not subscribed to the users ML.)
>>
>> Hi,
>>
>> TL;DR I've been experience stuck file system operations on cifs mount on
>> latest stable ke
On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
> (Please keep me in CC as I'm not subscribed to the users ML.)
>
> Hi,
>
> TL;DR I've been experience stuck file system operations on cifs mount on
> latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
> like t
(Please keep me in CC as I'm not subscribed to the users ML.)
Hi,
TL;DR I've been experience stuck file system operations on cifs mount on
latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
like to see if other people are seeing similar issue before actually
filing a bug
On 2024-01-10, Herb Garcia wrote:
> Does this method also create the modules?
>> make menuconfig
this one permits you to change kernel parameters if needed
>> make bindeb-pkg
this one compiles kernel and produces
linux-headers-*.deb
linux-image-*.deb
linux-image contains kern
Does this method also create the modules?
-Herb
On Tue, 2024-01-09 at 13:17 +0100, Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
On 2024-01-09, HP Garcia wrote:
> What dependencies did you install?
All are installed with those commands, thanks Debian :)
apt build-dep linux
apt install build-essential libncurses-dev
(last one for running menuconfig with ncurses)
What dependencies did you install?
~Herb
On Tue, Jan 9, 2024, 7:23 AM Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
> >
On 2024-01-08, Herb Garcia wrote:
> I was able to compile Linux kernel 6.1.X.
>
> When I tried compiling kernel 6.5.x and ran into issues.
>
> I download the required dependencies as required per
> https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
To compile 6
I was able to compile Linux kernel 6.1.X.
When I tried compiling kernel 6.5.x and ran into issues.
I download the required dependencies as required per
https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
I'm just looking to see if I missed any steps. Here is the list of
commands
Hi,
I update my packages on Debian Bookworm, and one of them was the Linux kernel:
6.1.0-15 --> 6.1.66-1
I see that file /run/reboot-required exists, but I miss file
/run/reboot-required.pkgs
Has Debian removed in Bookworm naming the packages, which require a reboot, or
will the linux-im
Hi Greg
> Sent: Tuesday, December 12, 2023 at 2:43 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: From which kernel should I upgrade my installed Debian to
> linux-image-6.1.0-15-amd64?
>
> On Mon, Dec 11, 2023 at 07:38:02PM +0100, St
1 - 100 of 45229 matches
Mail list logo
