Hi,
On Fri, Aug 22, 2025 at 07:12:39PM -0400, Alex McKeever wrote:
> I wonder if someone over at Debian Ports would be up to the task of
> making [i386] net installation images available?
Everyone at Debian that has the ability has already made clear over a
period of years that they don't think i
Jeff,
Yes I mean i386/i686. As of the latest release of Debian (and by extension
Devuan) x86-32 as a whole appears to be no longer available. I mean I’m glad
they supported it for far longer than Ubuntu did, but I guess it’s suffering
the same fate as PowerPC and other niche architectures now
Updating the firmware on the bluetooth speaker has resolved this
problem; reconnecting to it from Debian trixie on the laptop now
succeeds as expected.
On Fri, 22 Aug 2025 at 10:59, James Addison wrote:
>
> Hello Debianites,
>
> I've recently updated my X1 Yoga laptop to Debian trixie from
> book
M
Hi Jan,
On 2025-08-19 at 04:55 -07, Jan Claeys wrote...
> On Fri, 2025-08-15 at 20:55 -0700, Ken Mankoff wrote:
> It sounds like both of these messages are related to 'inotify' (and/or
> one of the other kernel APIs for watching for file changes like
> 'fanotify').
>
> [...]
>
> If you want to se
Hi Greg,
On 2025-08-19 at 04:34 -07, Greg Wooledge wrote...
> On Mon, Aug 18, 2025 at 21:52:30 -0700, Ken Mankoff wrote:
>> $ cat /proc/sys/fs/file-max
>> 100
>>
> That number actually looks suspiciously low *and* artificial, though I
> agree that it appears you're not bumping into that limi
On Fri, Aug 22, 2025 at 2:35 PM Alex McKeever
wrote:
> Would someone mind adding x86 (32 bit) images to Debian Ports? Apparently
> they finally dropped x86-32 recently.
When you say, x86-32, do you mean i386/i686 or x32?
I'm wondering if this wiki page needs updating: <
https://wiki.debian.org
Would someone mind adding x86 (32 bit) images to Debian Ports? Apparently they
finally dropped x86-32 recently.
Sent from my iPad
> On Aug 20, 2025, at 6:31 PM, John Paul Adrian Glaubitz
> wrote:
>
> Hello,
>
> I just created updated Debian Ports installation images based on
> kernel 6.12.3
Hi,
Steve McIntyre wrote:
> the UEFI spec also
> requires that implementations support MBR-partitioned disks for the
> ESP. [...]
> While UEFI implementations can be buggy, I don't think I've seen one
> yet that doesn't cope with this section.
Isn't such a bug in some old EFI the reason why the
On 7/30/25 14:42, to...@tuxteam.de wrote:
On Wed, Jul 30, 2025 at 01:47:53PM +0200, Greg wrote:
Hi there,
I have a "server" running 24/7 with a lot of RAM. I would like to speed up
disk system by giving much higher priority to reads and delaying writes.
YES, I KNOW THE RISK!
As I understand,
mrma...@earthlink.net wrote:
>
>I'm coming up short finding the authority on this, but I'm pretty sure there
>is no
>such thing as booting from an ESP that isn't on a GPT-partitioned disk, with
>correct type assigned. I think the ESP type is technically at least a 4byte
>value
>not supported by M
On 8/22/25 13:37, Sharon Kimble wrote:
I've now done a bare-back installation of debian 13, and I can now run chat
okay, but when I run it from the commandline it shows these errors;-
Failed to load libllamamodel-mainline-cuda.so: dlopen: libcuda.so.1: cannot
open shared object file: N
Hi Sharon,
Sharon Kimble writes:
> I've now done a bare-back installation of debian 13, and I can now run
> chat okay, but when I run it from the commandline it shows these
> errors;-
>
>
> Failed to load libllamamodel-mainline-cuda.so: dlopen: libcuda.so.1: cannot
> open shared object f
Try installing the modules using yum install for each module
If that doesn't work you will have to go searching for the necessary
deb files on various sites and use dpkg -i
Another way is to install a windows VM and run GPT4All inside that.
FYI I tried going the full debian route but failed
On 22/8/25 19:37, Sharon Kimble wrote:
I've now done a bare-back installation of debian 13, and I can now run chat
okay, but when I run it from the commandline it shows these errors;-
Failed to load libllamamodel-mainline-cuda.so: dlopen: libcuda.so.1: cannot
open shared object file:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've now done a bare-back installation of debian 13, and I can now run chat
okay, but when I run it from the commandline it shows these errors;-
Failed to load libllamamodel-mainline-cuda.so: dlopen: libcuda.so.1: cannot
open shared object
On Fri, Aug 22, 2025 at 08:47:05 +0100, Donald MacKinnon wrote:
> About three months ago I sent an apology for inadvertently mixing
> distributions.
> I'm assuming that you have not received that apology.
> Anyway the security problem remains - obviously I'm having difficulty using
> Debian in the
Hello Debianites,
I've recently updated my X1 Yoga laptop to Debian trixie from
bookworm, and currently I use the GNOME desktop environment.
In bookworm I was able to pair with some bluetooth speakers I have at
home, and could reconnect to those after a reboot of the laptop. This
would wake the
I am not sure who the maintainer for the Cisco VIC drivers is. But the
ones that come with Debian 12 don't support SR-IOV. It is quite old
I was wondering who can I reach out to get them updated, so they have
SR-IOV moving forward? I know they support SR-IOV in the newer version
because Cisco L
Hello
About three months ago I sent an apology for inadvertently mixing
distributions.
I'm assuming that you have not received that apology.
Anyway the security problem remains - obviously I'm having difficulty
using Debian in the usual manner.
I can assure you that I haven't tried to interfe
20 matches
Mail list logo
