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:
>
> You j
I thought they were coming closer after Brexit and all. They are going to
start importing all that chlorinated beef and chicken the EU wouldn't
allow. This will be cheaper in the stores than English beef. (it's an old
story) Maybe they will want to vote next to becoming part of the USA. I
doubt Ca
Thank you for all your answers, this pointed me to tools I was not aware
of and to options I was not aware of in tools I knew.
`lsof` seems able to give me a lot of info, but has so many options that
I haven't yet found a way to give me something more or less useful.
But at least I now know that i
This is probably related to needful dependencies not yet available, or
available somewhere else.
This problem is always sorted out by the passing of time. How much you want
to wait is subjective to you I would think.
Time is the revelator.
--
C.
> Why use 3 year old rsync?
If you can't answer this question, then you probably will be better
served with Debian testing, Debian unstable, or even some other
distribution than Debian stable.
Stefan
> Sent: Thursday, January 16, 2025 at 9:36 PM
> From: "Andy Smith"
> To: debian-user@lists.debian.org
> Subject: Re: A warning about rsync in stable: it became broken 3 days ago, is
> now fixed
>
> Hi,
>
> On Fri, Jan 17, 2025 at 03:27:26AM +0100, poc...@homemail.com wrote:
> > Actually the la
Hi,
On Fri, Jan 17, 2025 at 03:27:26AM +0100, poc...@homemail.com wrote:
> Actually the last patched debian rsync version is still vulnerable
> https://kb.cert.org/vuls/id/952657
>
> rsync 3.4.1 is the latest version that fixes the issues.
That page was last updated 15 January whereas the fixes
> Sent: Thursday, January 16, 2025 at 6:40 PM
> From: "David"
> To: "debian-user"
> Subject: A warning about rsync in stable: it became broken 3 days ago, is now
> fixed
>
> Hi,
>
> For anyone not subscribed to debian-security-announce mailing list:
>
> 1) You should subscribe to it :)
>
> 2)
I have Debian 12 installed on a server with NVIDIA ADA RTX4500 GPUs (used
for machine learning with Tensorflow via Docker images). When I upgrade
("sudo apt upgrade"), I get the message that a number of packages (all
related to Nvidia) have been "kept back".
I am not sure what to do: should I upgr
Hi,
For anyone not subscribed to debian-security-announce mailing list:
1) You should subscribe to it :)
2) rsync received a security update 3 days ago [1] with multiple fixes.
3) But that update also introduced a regression in the rsync -H option
(preserves hard links).
4) That regression
Hello Greg!
On 1/16/25 21:31, Greg Wooledge wrote:
> On Thu, Jan 16, 2025 at 20:27:17 +, Johannes Krottmayer wrote:
>> $ g++ -lvulkan -o test test.cpp
>
> If I recall correctly, the library options need to be *after* the object
> files that use them. Thus:
>
> g++ -o test test.cpp -lvu
On Thu, Jan 16, 2025 at 20:27:17 +, Johannes Krottmayer wrote:
> $ g++ -lvulkan -o test test.cpp
If I recall correctly, the library options need to be *after* the object
files that use them. Thus:
g++ -o test test.cpp -lvulkan
Hello,
I have encountered an issue when trying to compile and link against
libvulkan with the GNU C++ compiler and GNU ld. Get 'undefined
reference' errors on all library calls with:
$ g++ -lvulkan -o test test.cpp
The related package is installed on my system (also
the development package libvu
Roy J. Tellason, Sr. writes:
> I run [both uBlock-origin and NoScript], here. Noscript being the
> most recently added. It does make a nontrivial difference...
Likewise.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Wednesday 15 January 2025 09:49:15 pm Max Nikulin wrote:
>
> On 14/01/2025 17:11, Jean-François Bachelet wrote:
> > btw, you need to install noscripts from the extensions panel AND UBlock
> > origin or Adblock plus at least if you want to get rid of all ads and
> > javascripts code that have
This seems to have been it -- no crashes since the morning...
Thanks, folks -- will wait for
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089513 to get
closed...
Thanks kindly, and cheers!
On Thu, Jan 16, 2025 at 9:53 AM Rafał Lichwała wrote:
>
> See my post on "debian testing" mailing li
>>Now I heard of, that a NVME drive will only get to full speed, if UEFI is
>>activated in BIOS. Is this correct?
> No, at least for linux; I can't speak to windows.
+1
Stefan
Max Nikulin wrote:
>
> On 14/01/2025 17:11, Jean-François Bachelet wrote:
> > btw, you need to install noscripts from the extensions panel AND UBlock
> > origin or Adblock plus at least if you want to get rid of all ads and
> > javascripts code that have nothing to with the actual content of the
> New machines may not have "legacy/MBR" options to boot any more.
>
Mine is a used one, a Dell 5400, and luckily it can still use legacy boot.
> A straightforward new installation of Debian should create the ESP and
> appropriate means to install under UEFI. If you're installing Windows,
> then
> Be sure not to reboot after cloning while both source and target remain
> enabled.
I always shut down the device completely. then wait a few seaconds. disconnect
all drives (Lifefile usb drive and storage) and then start the machine again.
In the past I never had any issues doing so.
Cheers
On Thu, Jan 16, 2025 at 04:17:29PM +0100, Hans wrote:
> Hi folks,
>
> I got a new notebook with an NVME drive.
>
> As all my BIOS never needed UEFI, my installation dula boot of Windows and
> Debian are all without UEFI.
>
New machines may not have "legacy/MBR" options to boot any more.
> Th
Hans composed on 2025-01-16 16:57 (UTC+0100):
>> That depends on how you describe partitions in /etc/fstab. If you use
>> the device name, then almost certainly yes. If you use the label or
>> UUID, then no.
> Oh, that is cool, as I am using only UUID in fstab. Thus, just clone the
> drive
> wi
> Those are created at boot time, by udev.
I unde5rstand.
>
> That depends on how you describe partitions in /etc/fstab. If you use
> the device name, then almost certainly yes. If you use the label or
> UUID, then no.
>
Oh, that is cool, as I am using only UUID in fstab. Thus, just clone the d
Thanks Dan,
I disabled Secure Boot and sure enough, the driver was loaded.
I actually decided to make a clean install of Debian on this machine
and left Secure boot disabled.
I tried multiple times and was unable to get the driver to load. This
is strange however because it did work before.
I w
On Thu, 16 Jan 2025 16:17:29 +0100
Hans wrote:
> Another question, not really important: The device names, like
> "/dev/hdX", "/ dev/sdX" and now "/dev/nvmeX" - who is creating these?
> The kernel? Must /etc/ fstab be manually changed, when changing the
> kind of harddrive?
Those are created at
On Thu, Jan 16, 2025 at 04:17:29PM +0100, Hans wrote:
Now I heard of, that a NVME drive will only get to full speed, if UEFI is
activated in BIOS. Is this correct?
No, at least for linux; I can't speak to windows.
Another question, not really important: The device names, like "/dev/hdX", "/
d
On Thu, 16 Jan 2025 16:17:29 +0100
Hans wrote:
> I am asking, because if NOT, than it would spare me a lot of work, to
> create an UEFI partituion, rewrite the bootloaders, fstab,
> configurations and so on.
The Debian installer (the installer on the netinst CD, not the live CD)
will cheerfully
Hi folks,
I got a new notebook with an NVME drive.
As all my BIOS never needed UEFI, my installation dula boot of Windows and
Debian are all without UEFI.
Thus, it was easy for me, cloning debian to any other hardware in the past to
a ssd drive.
Now I heard of, that a NVME drive will only ge
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 16.01.2025
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, the conso
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 or
so..).
Che
On 2025-01-16 13:07, Greg Wooledge wrote:
On Thu, Jan 16, 2025 at 12:38:29 +0100, Jesper Dybdal wrote:
There is a syntax error (an erroneous ">" character) in
/usr/include/c++/12/type_traits
in Bookworm. So compiling any program that includes the header
fails:
echo "#include " >error.c
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.0-29 f
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
On Thu, Jan 16, 2025 at 12:38:29 +0100, Jesper Dybdal wrote:
> There is a syntax error (an erroneous ">" character) in
> /usr/include/c++/12/type_traits
> in Bookworm. So compiling any program that includes the header
> fails:
>
> echo "#include " >error.cpp
> g++ -c error.cpp
>
> Results
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
Hi Jesper,
On Thu, Jan 16, 2025 at 12:38:29PM +0100, Jesper Dybdal wrote:
> There is a syntax error (an erroneous ">" character) in
> /usr/include/c++/12/type_traits
> in Bookworm.
I do not experience this on my Debian 12.
> > In file included from /usr/include/c++/12/bits/char_traits.h:42,
On Thu, Jan 16, 2025 at 13:18:53 +0200, Anssi Saari wrote:
> Urs Thuermann writes:
> > mount | fgrep -vf <(awk '/^nodev/{print $2}' /proc/filesystems)
>
> Thanks. It has the benefit of not showing autofs, for example. But how
> to quote that for an alias?
The simplest way is *not* to use an alia
There is a syntax error (an erroneous ">" character) in
/usr/include/c++/12/type_traits
in Bookworm. So compiling any program that includes the
header fails:
echo "#include " >error.cpp
g++ -c error.cpp
Results in:
In file included from /usr/include/c++/12/bits/char_traits.h:42,
Urs Thuermann writes:
> Felix Miata writes:
>
>> I have the following in ~/.bashrc for making that easier:
>>
>> alias Mnt='mount | egrep -v "cgroup|rpc|ramfs|tmpfs|^sys|on /dev|on /proc|on
>> /sys|on /var" | sort '
>
> mount | fgrep -vf <(awk '/^nodev/{print $2}' /proc/filesystems)
Thanks. I
40 matches
Mail list logo
