On Sun 23 Mar 2025 at 01:12:29 (-0400), Felix Miata wrote:
> songbird composed on 2025-03-22 08:16 (UTC-0400):
> > Felix Miata wrote:
> >> I'm not sure the subject is asking the right question, but determining
> >> available
> >> versions of any Debian package has always vexed me. In opensuse, it'
On Sun, 23 Mar 2025 15:25:31 -0400
Felix Miata wrote:
> 0 upgraded, 48 newly installed, 0 to remove and 1 not upgraded.
> Need to get 6,874 kB of archives.
> After this operation, 23.0 MB of additional disk space will be used.
> Do you want to continue? [Y/n] n
> Abort.
> #
> :~(
Yes, I'm gettin
Marco Möller wrote:
> Often during boot, not always though, and never after KDE Plasma already
> began to start, I observe a kernel panic. The system is Debian stable
> "bookworm", but using kernel 6.12.12 from backports. I know, this is not
> the officially recommended wa
Often during boot, not always though, and never after KDE Plasma already
began to start, I observe a kernel panic. The system is Debian stable
"bookworm", but using kernel 6.12.12 from backports. I know, this is not
the officially recommended way to use Debian stable. But as this
David Wright composed on 2025-03-23 13:27 (UTC-0500):
> On Sun 23 Mar 2025 at 01:12:29 (-0400), Felix Miata wrote:
>> Looks perfect, but for 43 things:
>> # rmadison linux-image
>> Command 'rmadison' not found, but can be installed with:
>> apt install devscripts
>> # apt-get install devscripts
>
Felix Miata wrote:
> songbird composed on 2025-03-22 08:16 (UTC-0400):
...
>> i'm not able to dig into this further (way behind on this list)
>> but rmadison works ok for something like that:
...
> Looks perfect, but for 43 things:
> # rmadison linux-image
> Command 'rmadison' not found, but ca
songbird composed on 2025-03-22 08:16 (UTC-0400):
> Felix Miata wrote:
>> I'm not sure the subject is asking the right question, but determining
>> available
>> versions of any Debian package has always vexed me. In opensuse, it's pretty
>> simple
>> from shell prompt to get a list of packages
Felix Miata wrote:
> I'm not sure the subject is asking the right question, but determining
> available
> versions of any Debian package has always vexed me. In opensuse, it's pretty
> simple
> from shell prompt to get a list of packages available in currently configured
> repos,
> one line each
On 2025-02-27 15:59, Gary Dale wrote:
On 2025-02-14 22:00, Michael Stone wrote:
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
All 3 systems have the linux-image-amd64 metapackage installed.
What does apt show -a linux-image-amd64 | grep -e Version -e Sources
-e Depends
return o
> > > On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
> > > > All 3 systems have the linux-image-amd64 metapackage installed.
On Sat 15 Mar 2025 at 10:44:40 (-0400), Gary Dale wrote:
> After today's upgrades, I note that RM1 showed these autoremove
> messages "Removing linux-headers-6.1
On 12.03.2025 04:12, Alex King wrote:
Yes, I can tell you more. The hardware as you guessed is not actually
new, it is recycled equipment that is new to me and newly installed
with Debian.
...
*-scsi
description: SCSI storage controller
product: S
Le 12/03/2025 à 13:54, didier gaumet a écrit :
[...]
But however, your current kernel 6.1 from Bullseye Backports does seem
affected by a bug?
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=linux-
image-6.1.0-0.deb11.21-amd64;dist=unstable
=> But however, your current kernel 6.1 f
providing
an upgraded backported kernel
Perhaps (mere supposition) you could create a bug against the
linux-image-amd64 Bullseye package, asking it being modified to depend
upon linux-image-6.1.0-0.deb11.31-amd64-unsigned?
And, yes it seems safe to install
linux-image-6.1.0-0.deb11.31-amd64
to a linux 6.1 available in Bullseye
> Backports, to install it should probably suffice?
As indicated in OP, that is the most recent properly working kernel installed:
[quote]
Latest available backport kernel: bullseye-backports 6.1.90-1 from 2024-05
works as expected.
[/quote]
And it'
Hello,
- in order to list all installable versions of a package, I find apt
policy useful. Here for an amd64 kernel:
didier@hp-notebook14:~$ LANG=en-us.UTF8; apt policy linux-image-amd64
linux-image-amd64:
Installed: 6.1.129-1
Candidate: 6.1.129-1
Version table:
6.12.12-1~bpo12+1
ch package directories" section, enter the
following:
Keyword kernel-image amd64
Search on Descriptions
Distributionoldstable
And click "Search", I see:
https://packages.debian.org/search?keywords=kernel-image+amd64&searchon=all&suite=
rg/distrib/packages omits old-stable. Is
there
an alternative that does not?
What's the (best?) way to determine which kernel(s) are available from which
source(s) when full-upgrade stops providing new kernels? The ultimate question:
Is my GPU supposed to be supported by a current
On 3/11/25 18:12, Alex King wrote:
Yes, I can tell you more. The hardware as you guessed is not actually
new, it is recycled equipment that is new to me and newly installed
with Debian.
The machine is a Cisco MCS server, possibly a Cisco MCS7800 series.
(I'm not where the server is physi
se servers, it has an uncommon display
chipset (MGA G200EV) which the kernel doesn't handle correctly at boot.
Hence also the installer doesn't display. I installed this machine by
booting off a Debian 12 live image, then using parted to partition the
disk and debootstrap to ins
blk output.
root@fj2:/home/installer# lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sdb 8:16 02T 0 disk
The problem is below the partition table; the kernel does not know the
actual size of the disk.
This could be for any number of reasons, including controller and drive
Le 3/11/25 à 09:17, Alexander V. Makartsev a écrit :
Can you tell us more information about hardware setup?
Could RAID setup play a role?
Best,
--
yassine -- sysadm
http://about.me/ychaouche
Looking for side gigs.
On 3/11/25 06:26, to...@tuxteam.de wrote:
On Tue, Mar 11, 2025 at 08:13:16PM +1300, Alex King wrote:
Hi,
hi
I've installed a large disk in a new machine and loaded Debian (bookworm) on
it, but it's showing as limited to 2TB when the disk should be larger.
How can I get Debian to use the fu
Le Tue, 11 Mar 2025 20:13:16 +1300,
Alex King a écrit :
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
Try to remove protective MBR.
512 bytes = 2 TiB - 1024 bytes.
Only smartctl, which does not depend on the kernel's size assessment,
reports a capacity of 8 TB + 1.563222016 GB.
So 2 TiB is obviously a misperception of the overall disk size by the
kernel. Linux hands this size to user space by ioctl(BLKGETSIZE) or
ioct
On Tue, Mar 11, 2025 at 6:26 AM wrote:
> On Tue, Mar 11, 2025 at 08:13:16PM +1300, Alex King wrote:
> > Hi,
>
> hi
>
> > I've installed a large disk in a new machine and loaded Debian
> (bookworm) on
> > it, but it's showing as limited to 2TB when the disk should be larger.
>
I have a 16TB drive
Timothy M Butterworth (HE12025-03-11):
> I have a 16TB drive that is working properly. I reformatted the drive to
> the ext4 file system with default settings and it works great. Try to
Good for you.
> reformat the drive especially if the current format is FAT.
We have both the kernel
bytes [8.00 TB]
> Sector Sizes: 512 bytes logical, 4096 bytes physical
> root@fj2:/home/installer# cat /proc/partitions
> major minor #blocks name
> [...]
> 8 16 2147483647 sdb
Observation:
2147483647 = 2 exp 31 - 1
This could mean that the kernel bonks at a 31-bit
On Tue, Mar 11, 2025 at 11:40:29AM +0100, Nicolas George wrote:
> to...@tuxteam.de (HE12025-03-11):
> > It seems that the combination of MBR partition table and 512 byte blocks
> > limits you to partition sizes (and offsets) of roughly 2T, so it might
> > be this what's biting you:
>
> Highly doub
to...@tuxteam.de (HE12025-03-11):
> It seems that the combination of MBR partition table and 512 byte blocks
> limits you to partition sizes (and offsets) of roughly 2T, so it might
> be this what's biting you:
Highly doubtful considering these informations:
>> 8 16 2147483647 sdb
>> Fou
On Tue, Mar 11, 2025 at 08:13:16PM +1300, Alex King wrote:
> Hi,
hi
> I've installed a large disk in a new machine and loaded Debian (bookworm) on
> it, but it's showing as limited to 2TB when the disk should be larger.
>
> How can I get Debian to use the full 8TB on this disk?
It seems that th
Hi,
correction of the usual copy+paste error:
I wrote:
> 8001563222016 / 512 / 4294967296 = 7.277379356324673
The result stems from a different calculation with 2 exp 31.
With 2 exp 32 it is 3.638689678162337 .
Have a nice day :)
Thomas
On 11.03.2025 13:49, Yassine Chaouche wrote:
Le 3/11/25 à 09:17, Alexander V. Makartsev a écrit :
Can you tell us more information about hardware setup?
Could RAID setup play a role?
I don't think so, because of the way RAID controllers work, they
basically hide the real hardware HDDs behind
On 11.03.2025 12:13, Alex King wrote:
Hi,
I've installed a large disk in a new machine and loaded Debian
(bookworm) on it, but it's showing as limited to 2TB when the disk
should be larger.
How can I get Debian to use the full 8TB on this disk?
Can you tell us more information about hardwa
s: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Tue Mar 11 21:06:13 2025 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
However it's showing in the kernel as 2TB:
root@fj2:/home/insta
On 2025-02-14 22:00, Michael Stone wrote:
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
All 3 systems have the linux-image-amd64 metapackage installed.
What does apt show -a linux-image-amd64 | grep -e Version -e Sources
-e Depends
return on each system?
If you
apt update
on ea
updated but the other half keeps the old content,
which is bad when scrolling or using tmux/vim or such.
I compared it with a previous working version of the VM and I noticed
that the kernel changed from 6.1.0-21-amd64 to 6.1.0-31-amd64, and
there is one probably related change in dmesg. In the working
On 14/02/2025 21:49, Gary Dale wrote:
On 2025-02-09 11:46, Max Nikulin wrote:
I recommend to compare
apt policy linux-image-amd64
and
apt policy
I can't see any differences between them on the various systems.
If it is true and the latest kernel is installed on all systems
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
All 3 systems have the linux-image-amd64 metapackage installed.
What does
apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends
return on each system?
If you
apt update
on each system, are there any error messages?
On 2025-02-09 11:46, Max Nikulin wrote:
On 09/02/2025 00:05, Gary Dale wrote:
VM1: /etc/apt/sources.list
I recommend to compare
apt policy linux-image-amd64
and
apt policy
I can't see any differences between them on the various systems.
On 2025-02-09 09:01, Greg Wooledge wrote:
On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote:
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
I have a few systems running Debian/Stable (Bookworm). However the kernel
version isn't always the same for some reason. After
On 2025-02-09 06:22, Henrik Ahlgren wrote:
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
I have a few systems running Debian/Stable (Bookworm). However the kernel version isn't always the same for some reason. After this morning's update, I noticed that 2 of the 3 systems up
Good news! I got partly success with this issue. Now volume upand down is
workiing in KDE, but still NOT screen brightness.
What did I do?
I first created a new user and then could see, volume is working. After that I
moved some directories from my old user away.
First ~/.local - no success.
t
Hi Nicolas,
I do not think it is so easy!
But let me go further into details. I am running plasma5 from Debian/stable,
but also XFCE is installed as well as LXQT and some parts of GNOME.
The GNOME parts are installed, because these are dependencies of some
applications, which are GNOME relate
Hans (12025-02-10):
> All keys are working.
>
> For example:
>
> xxd /dev/input/event12
> (This example is for FN+screen_brightness_up and
> FN+screen_brightness_down.)
Then your problem is easy. If some keys did not generate events, getting
them to work might have been a nightmare or impos
Yes, did so.
All keys are working.
For example:
xxd /dev/input/event12
: 2644 aa67 4336 0900 &D.gC6..
0010: 0100 e000 0100 2644 aa67 &D.g
0020: 4336 0900 C6..
0030: 2644
Hans (12025-02-10):
> However, it is clear, the functions like screen brightness etc. stop working,
> as soon as the kernel loads.
That is not surprising. Before the kernel loads, the key are handled by
the firmware and control the computer. After the kernel loads, the keys
are handled
Still hasseling with this problem
I am now believing, that the reason of the problem is either a BIOS issue or a
kernel issue.
Tested several things and I the issue appears as soon as the kernel is
started. In the internet I found informations, that if the BIOS does not see
Windows, it
On 09/02/2025 00:05, Gary Dale wrote:
VM1: /etc/apt/sources.list
I recommend to compare
apt policy linux-image-amd64
and
apt policy
Dis you install the package "linux-image-amd64" ? If yes, the it should always
update to the newest kernel.
(Same for package "linux-headers-amd64")
Hans
On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote:
> On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
> > I have a few systems running Debian/Stable (Bookworm). However the kernel
> > version isn't always the same for some reason. After this morning's upda
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
>
> I have a few systems running Debian/Stable (Bookworm). However the kernel
> version isn't always the same for some reason. After this morning's update, I
> noticed that 2 of the 3 systems upgraded the kernel but to
I have a few systems running Debian/Stable (Bookworm). However the
kernel version isn't always the same for some reason. After this
morning's update, I noticed that 2 of the 3 systems upgraded the kernel
but to different versions. This is shown by running uname -a.
The first is a
On 2025-02-01 12:39, Andrew M.A. Cater wrote:
On Sat, Feb 01, 2025 at 10:07:49AM -0700, g...@extremeground.com wrote:
On 2025-02-01 09:29, g...@extremeground.com wrote:
BTW: the same happens with the previous kernel. Also, this is a
Debian/Buster server running on AMD64 hardware. I've f
On Sat, Feb 01, 2025 at 10:07:49AM -0700, g...@extremeground.com wrote:
> On 2025-02-01 09:29, g...@extremeground.com wrote:
>
> BTW: the same happens with the previous kernel. Also, this is a
> Debian/Buster server running on AMD64 hardware. I've fsck'd the partition
&
On 2025-02-01 11:29, g...@extremeground.com wrote:
I get the message right after the boot sequence declares the / drive
clean. The subject message repeats 3 times then the system boot stops.
It still responds to the keyboard but there is no system to log into.
When I go into the system in a ch
em back up. :(
Any advice?
Thanks.
BTW: the same happens with the previous kernel. Also, this is a
Debian/Buster server running on AMD64 hardware. I've fsck'd the
partition and it's fine.
I rebooted today after installing the latest updates - which included a
new linux-image.
I get the message right after the boot sequence declares the / drive
clean. The subject message repeats 3 times then the system boot stops.
It still responds to the keyboard but there is no system to log into.
When I go into the system in a chroot after booting with systemrescue, I
find that j
uch a combination running with Debian 12? Are there any
troubles with the default kernel? Or, is a newer kernel required to run
this combination (9950X/X870-E)?
X870 + Ryzen 7 9700X work fine with the current Debian 12.9 kernel.
However in my case the motherboard is MSI PRO X870-P WIFI, which uses
Re
On 1/23/25 00:14, didier gaumet wrote:
Le 22/01/2025 à 23:41, Marco Möller a écrit :
On 1/22/25 23:23, didier gaumet wrote:
Debian provides realtime kernels in its repositories. For an AMD64 PC
and Debian 12 Bookworm (without backports), the last LTS realtime
kernel package is:
linux-image
Le 22/01/2025 à 23:41, Marco Möller a écrit :
On 1/22/25 23:23, didier gaumet wrote:
Debian provides realtime kernels in its repositories. For an AMD64 PC
and Debian 12 Bookworm (without backports), the last LTS realtime
kernel package is:
linux-image-6.1.0-29-rt-amd64
Do I understand
On 1/22/25 23:12, Michael Stone wrote:
On Wed, Jan 22, 2025 at 11:07:57PM +0100, Marco Möller wrote:
You mean, linux-image-amd64 in bookworm-backports, which currently
draws in linux-image-6.12.9+bpo-amd64 (= 6.12.9-1~bpo12+1), can be
expected to NOT draw in some 6.13 like 6.13~rc7+1~exp1 curr
On 1/22/25 23:23, didier gaumet wrote:
Debian provides
realtime kernels in its repositories. For an AMD64 PC and Debian 12
Bookworm (without backports), the last LTS realtime kernel package is:
linux-image-6.1.0-29-rt-amd64
Do I understand correctly, that the rt-kernels like the one you
Le 22/01/2025 à 23:23, didier gaumet a écrit :
[...)
DAW usage and I don not think he was not using backports)
[...)
I did not take time to read myself before posting, sorry:
"I do not think he was using backports"
is more correct ;-)
Le 22/01/2025 à 21:48, Marco Möller a écrit :
On 1/22/25 01:12, Greg Wooledge wrote:
It's not yet clear to me whether you're trying to use a backported
kernel because
you *need* it, or because it has a higher number and you think higher
numbers are better.
I would like to optimize
On Wed, Jan 22, 2025 at 11:07:57PM +0100, Marco Möller wrote:
You mean, linux-image-amd64 in bookworm-backports, which currently
draws in linux-image-6.12.9+bpo-amd64 (= 6.12.9-1~bpo12+1), can be
expected to NOT draw in some 6.13 like 6.13~rc7+1~exp1 currently
already having appeared in the ex
On 1/22/25 22:32, Michael Stone wrote:
I think the problem here is a misunderstanding of how backports work:
they're not "the latest kernel", they're "the latest kernel from debian
testing". You're not going to see a kernel in backports that's not going
now. I will accept this and go for the
repetitive manual way then.
I think the problem here is a misunderstanding of how backports work:
they're not "the latest kernel", they're "the latest kernel from debian
testing". You're not going to see a kernel in b
On 1/22/25 01:12, Greg Wooledge wrote:
It's not yet clear to me whether you're trying to use a backported kernel
because
you *need* it, or because it has a higher number and you think higher
numbers are better.
I would like to optimize my laptop for creative audio usage (tracking
>
> I want to install the currently highest version of kernel 6.12 from
> bookworm-backports to my Bookworm. Upon some "apt update && apt upgrade" I
> want this kernel to become upgraded whenever in backports becomes available
> a higher version of kernel 6.12, like having
e any
troubles with the default kernel? Or, is a newer kernel required to run
this combination (9950X/X870-E)?
Thanks in advance!
On 22/01/2025 03:17, Marco Möller wrote:
Could you please share with me, or point me to, a howto or receipt for
applying all upgrades to future kernel 6.12.x versions to appear in
Bookworm Backports when doing "apt update && apt upgrade", but to not
leave the 6.12 (upstream L
; I want to install the currently highest version of kernel 6.12 from
> bookworm-backports to my Bookworm.
The fundamental question is why you want to do this. Is your hardware
not supported by the bookworm kernel? Do you *need* this backported
kernel?
Backports are a set of packages that a
On 1/22/25 00:10, George at Clug wrote:
I apologise, but I do not understand what it is you want to achieve or what it
is that you are asking.
Can you please give more explanation?
I want to install the currently highest version of kernel 6.12 from
bookworm-backports to my Bookworm. Upon
Marco,
I apologise, but I do not understand what it is you want to achieve or what it
is that you are asking.
Can you please give more explanation?
You said: "not leave the 6.12 (upstream LTS) branch and not upgrade to some
higher kernel version like 6.13 when they would also become avai
On 1/21/25 21:39, Andrew M.A. Cater wrote:
On Tue, Jan 21, 2025 at 09:17:52PM +0100, Marco Möller wrote:
Hello community!
Could you please share with me, or point me to, a howto or receipt for
applying all upgrades to future kernel 6.12.x versions to appear in Bookworm
Backports when doing &quo
On Tue, Jan 21, 2025 at 09:17:52PM +0100, Marco Möller wrote:
> Hello community!
> Could you please share with me, or point me to, a howto or receipt for
> applying all upgrades to future kernel 6.12.x versions to appear in Bookworm
> Backports when doing "apt update &&
Hello community!
Could you please share with me, or point me to, a howto or receipt for
applying all upgrades to future kernel 6.12.x versions to appear in
Bookworm Backports when doing "apt update && apt upgrade", but to not
leave the 6.12 (upstream LTS) branch and not upgr
;> resulting in loss
>> of about 2/3 in graphics performance testing with glmark2.
> Thanks for reminding me about new xe driver, but unfortunately I wasn't
> able to get it working.
> I've tried 6.11 kernel from backports, but it look like "xe" module is
> abs
s for reminding me about new xe driver, but unfortunately I wasn't
able to get it working.
I've tried 6.11 kernel from backports, but it look like "xe" module is
absent and only "i915" available.
$ uname -a
Linux hostname 6.11.10+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debi
On 19.01.2025 01:53, Charles Curley wrote:
On Sat, 18 Jan 2025 23:52:31 +0500
"Alexander V. Makartsev" wrote:
Things I've tried so far:
1. Updated Intel graphics firmware to latest version available on
git.kernel.org
I suggest you try the most recent backported kernel and
Alexander V. Makartsev composed on 2025-01-18 23:52 (UTC+0500):
> I have stability issues (freezing) on my laptop running Debian 12
> (current stable), and, according to logs, the culprit is kernel module i915.
> My kernel version:
> $ uname -a
> Linux hostname 6.1.0-
graphics
bookworm-backports (kernel): Binary firmware for Intel iGPUs and IPUs
[non-free-firmware]
20240709-2~bpo12+1: all
If not I would hope this would solve the issue, though I do expect that you
have already install these packages.
"Intel's Alder Lake-P GT1 processor was released o
On Sat, 18 Jan 2025 23:52:31 +0500
"Alexander V. Makartsev" wrote:
> Things I've tried so far:
> 1. Updated Intel graphics firmware to latest version available on
> git.kernel.org
I suggest you try the most recent backported kernel and firmware.
https://backports.debi
Hello, Debian users.
I have stability issues (freezing) on my laptop running Debian 12
(current stable), and, according to logs, the culprit is kernel module i915.
My kernel version:
$ uname -a
Linux hostname 6.1.0-30-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.124-1
(2025-01-12) x86_64 GNU
Apropos this, can anybody point to docs on what the user-facing
differences are between using Nvidia' proprietary driver, and their
slowe drift towards the open driver:
https://packages.debian.org/sid/nvidia-open-kernel-source ?
Cheers!
On Fri, Jan 17, 2025 at 1:05 AM Steve Litt wrote:
&g
ng" mailing list:
>
> https://lists.debian.org/debian-testing/2025/01/msg1.html
>
> Nvidia drivers have problem with kernel 6.12.* (which is now current
> kernel version in Trixie)
>
> Downgrade to the last available 6.11.* and it works fine.
>
> Regards,
> R
See my post on "debian testing" mailing list:
https://lists.debian.org/debian-testing/2025/01/msg1.html
Nvidia drivers have problem with kernel 6.12.* (which is now current
kernel version in Trixie)
Downgrade to the last available 6.11.* and it works fine.
Regards,
Rafal
On
As far as I know there are some problems with the 6.12 kernel and nvidia
drivers. I read by chance this post:
https://kenhys.hatenablog.jp/entry/2025/01/13/172405
a couple of days later I installed trixie on a machine mounting a
GTX750Ti and actually the login manager didn't started
Hello Nmanca,
Sorry, I don't quite follow... The hardware is a GTX 1080 Ti. Are
you saying that nvidia 535.216.03 from testing is known not to work
with this model? Recompling the same -- using dkms -- for the 6.1
kernel has booted OK, and so daf has not crashed... (like 2 hours
Hallo,
I saw you loaded nvidia driver. in Trixie they do not work (v. 535 on a
GTX750Ti), after downloading the kernel to 6.1.0-29 (from stable), X
loaded with no problems. Maybe it's related to that?
Cheers!
On 16/01/2025 13:32, Boyan Penkov wrote:
Confirming that downgrading to 6.1
Confirming that downgrading to 6.1.0-29 from Bookworm makes this go away...
Cheers!
On Thu, Jan 16, 2025 at 7:19 AM Boyan Penkov wrote:
>
> Hello,
>
> Anybody seeing the attached page fault in dmesg on the Trixie kernel?
>
> Cheers!
>
> --
> Boyan Penkov
--
Boyan Penkov
Hello,
Anybody seeing the attached page fault in dmesg on the Trixie kernel?
Cheers!
--
Boyan Penkov
[ 2059.005772] BUG: unable to handle page fault for address: e5a98000
[ 2059.005779] #PF: supervisor read access in kernel mode
[ 2059.005782] #PF: error_code(0x) - not-present page
I just want to be able to use my PS4 controllers. I saw that they have gyro,
and it should be supported in the module, but dolphin doesn't seem to
understand it.
On January 12, 2025 9:07:23 AM EST, "tv.debian"
wrote:
>On 12/01/2025 03:54, nsrxnst wrote:
>> does the sto
On 2025-01-12 14:07, tv.debian wrote:
On 12/01/2025 03:54, nsrxnst wrote:
does the stock kernel come with this driver? if not, how can I get it?
Hello,
If you are asking about the controller, Debian kernels are built with
"CONFIG_HID_SONY=m", so the "hid-playstation.ko"
On 12/01/2025 03:54, nsrxnst wrote:
does the stock kernel come with this driver? if not, how can I get it?
Hello,
If you are asking about the controller, Debian kernels are built with
"CONFIG_HID_SONY=m", so the "hid-playstation.ko" should be available for
yo
does the stock kernel come with this driver? if not, how can I get it?
Hi,
The debian kernel compile problem has been solved.The details can be
found under the title.
Thank you for your help, regards you ti
are new to kernel compiling maybe you don't know that you can
optimize the kernel for your specific CPU architecture, if you are
using
the GCC compiler:
first make a backup copy of the Makefile:
$ cd linux-source-6.1
$ cp arch/x86/Makefile arch/x86/Makefile.backup
then edit "arch/x86/M
odule:
Cleaning build area...
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.1.119-
fah105..(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.119-fah105 (x86_64)
Consult /var/lib/dkms/nvidia-current/535.183.01/build/make.log for more
information.
> Sent: Saturday, January 04, 2025 at 7:12 PM
> From: "Jeffrey Walton"
> To: poc...@homemail.com
> Cc: "debian-user"
> Subject: Re: debian kernel compiler
>
> On Sat, Jan 4, 2025 at 4:17 PM wrote:
> >
> > > Sent: Saturday, January 0
1 - 100 of 15096 matches
Mail list logo
