Bug#1064927: Incompatible build for libproxy1v5

2024-02-27 Thread Jannick Loch

Package: libproxy1v5
Version: 0.5.4-1

During my peroid update routine, I notice that the AMD64-Build
for libproxy1v5 is incompatible with the gnome and gnome-core package 
and force apt to remove them. This can lead to system instability and i 
can't reinstall this packages anymore




I am using Debian GNU/Linux SID and the Kernel 6.6.15-amd64.



Bug#1042510: Not able to upgrade binutils-x86-64-linux-gnu

2023-07-29 Thread Jannick Loch

Package: binutils-x86-64-linux-gnu
Version: 2.40.90.20230729-1

During my period update routine, I notice that i am not able to upgrade the 
package binutils-x86-64-linux-gnu without removing essential packages for my 
system.
the package wants some version of libgprofng, but if i try to install some 
similar package calling libgprofng0, apt wants also to remove some essential 
packages.

I am using Debian GNU/Linux SID and the Kernel 6.4.0-1-amd64


Bug#1032466: Performance problems with nvidia-driver version 525.89.02-1

2023-03-25 Thread Jannick Loch

On Tue, 21 Mar 2023 14:23:04 +0100 Andreas Beckmann  wrote:
> Control: tag -1 moreinfo
>
> On 07/03/2023 15.49, Jannick Loch wrote:
> > Package: nvidia-driver
> > Version: 525.89.02-1
> >
> > The first Problem is, when i enable Vsync at any game, the framerate
> > wont sync to my monitor refreshrate, it stuck at 60hz.
> > And the other Problem is, when i install the Extension Dash to 
Dock, all

> > games say that they has more than 60hz, but i can see with my eyes and
> > with a tool, that my monitor shows only 60 hz.
>
> Please try the 530 driver from experimental.
>
>
> Andreas
>

>


With the 530 Driver, i can say that the bug with dash to dock has solved 
for me, but i still experience the vsync bug that all games run with 
60hz only instead of 165hz from my monitor. I have an RTX3060ti.




Bug#1033288: Build Problems with nvidia-fs-dkms on kernel version 6.1.20

2023-03-21 Thread Jannick Loch

Package: nvidia-fs-dkms
Version: 2.13.5~11.8.0-2

Durimng my update routine, i notice that i have problems with building the 
nvidia-fs module on the newest linux kernel package
6.1.20. Dkms said that there was an BUILD_EXCLUSIVE directive which does not 
match this kernel/arch/config. If i remove this directive by comment it out,
i get following error log in make.log:
DKMS make.log for nvidia-fs-2.13 for kernel 6.1.0-7-amd64 (x86_64)
Di 21. Mär 16:37:07 CET 2023
./configure 6.1.0-7-amd64
Picking NVIDIA driver sources from 
NVIDIA_SRC_DIR=/usr/src/nvidia-current-525.89.02/nvidia-peermem. If that does 
not meet your expectation, you might have a stale driver still around and that 
might cause problems.
chmod +x ./create_nv.symvers.sh
./create_nv.symvers.sh 6.1.0-7-amd64
Getting symbol versions from 
/lib/modules/6.1.0-7-amd64/updates/dkms/nvidia-current.ko ...
Created: /var/lib/dkms/nvidia-fs/2.13/build/nv.symvers
cat nv.symvers >> Module.symvers
checking if uaccess.h access_ok has 3 parameters... no
checking if uaccess.h access_ok has 2 parameters... yes
Checking if blkdev.h has blk_rq_payload_bytes... yes
Checking if fs.h has call_read_iter and call_write_iter... yes
Checking if fs.h has filemap_range_has_page... no
Checking if kiocb structue has ki_complete field... yes
Checking if vm_fault_t exist in mm_types.h... yes
Checking if IOCB_HIPRI flag exists in fs.h... yes
Checking if enum PCIE_SPEED_32_0GT exists in pci.h... yes
Checking if atomic64_t counter is of type long... no
Checking if RQF_COPY_USER is present or not... no
Checking if dma_drain_size and dma_drain_needed are present in struct 
request_queue... no
Checking if struct proc_ops is present or not ... yes
Checking if split is present in vm_operations_struct or not ... no
Checking if mremap in vm_operations_struct has one parameter... yes
Checking if mremap in vm_operations_struct has two parameters... no
Checking if symbol module_mutex is present... no
Checking if blk-integrity.h is present... yes
KCPPFLAGS="-DCONFIG_NVFS_STATS=y -DGDS_VERSION=1.4.0.29 
-DNVFS_ENABLE_KERN_RDMA_SUPPORT -DNVFS_BATCH_SUPPORT=y" CONFIG_NVFS_BATCH_SUPPORT=y 
CONFIG_NVFS_STATS=y make -j4 -C /lib/modules/6.1.0-7-amd64/build  M=$PWD modules
make[1]: warning: -j4 forced in submake: resetting jobserver mode.
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-7-amd64“ wird betreten
  CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.o
  CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-dma.o
  CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.o
  CC [M]  /var/lib/dkms/nvidia-fs/2.13/build/nvfs-pci.o
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c:853:5: error: conflicting types 
for ‘rw_verify_area’; have ‘int(int,  struct file *, char *, const loff_t *, 
size_t)’ {aka ‘int(int,  struct file *, char *, const long long int *, long 
unsigned int)’}
  853 | int rw_verify_area(int read_write, struct file *file,
  | ^~
In file included from 
/usr/src/linux-headers-6.1.0-7-common/include/linux/huge_mm.h:8,
 from 
/usr/src/linux-headers-6.1.0-7-common/include/linux/mm.h:743,
 from /var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c:34:
/usr/src/linux-headers-6.1.0-7-common/include/linux/fs.h:3200:5: note: previous 
declaration of ‘rw_verify_area’ with type ‘int(int,  struct file *, const 
loff_t *, size_t)’ {aka ‘int(int,  struct file *, const long long int *, long 
unsigned int)’}
 3200 | int rw_verify_area(int, struct file *, const loff_t *, size_t);
  | ^~
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c: In function ‘nvfs_direct_io’:
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.c:932:44: error: assignment to 
‘void (*)(struct kiocb *, long int)’ from incompatible pointer type ‘void 
(*)(struct kiocb *, long int,  long int)’ [-Werror=incompatible-pointer-types]
  932 | nvfsio->common.ki_complete = nvfs_io_complete;
  |^
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.c: In function 
‘nvfs_mgroup_mmap_internal’:
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.c:618:67: error: implicit 
declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? 
[-Werror=implicit-function-declaration]
  618 | base_index = NVFS_MIN_BASE_INDEX + (unsigned 
long)prandom_u32();
  |   
^~~
  |   
prandom_u32_max
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.1.0-7-common/scripts/Makefile.build:255: 
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-core.o] Fehler 1
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.1.0-7-common/scripts/Makefile.build:255: 
/var/lib/dkms/nvidia-fs/2.13/build/nvfs-mmap.o] Fehler 1
make[1]: *** [/usr/src/linux-headers-6.1.0-7-common/Makefile:2037: 

Bug#1033238: Addition

2023-03-20 Thread Jannick Loch
I totally forgot that this kind of package has to be approved by the 
ftp-master team. The bus is closed


-done



Bug#1033237: Wrong Package

2023-03-20 Thread Jannick Loch
I must admit that i had the nvidia-driver package in my clipboard and 
this bug relates to the debian


kernel team, not the nvidia team. This bug can be closed



Bug#1033238: Missing Image for linux-image-6.1.0-7-amd64

2023-03-20 Thread Jannick Loch

Package: linux-image-amd64
Version: 6.1.0-7

Durimg my update routine, i notice that the build for amd64 is missing, so that 
i would broke my installation when i want to
upgrade my system. I dont know whether the package still needs time to build.



I am using Debian GNU/Linux SID with X11 and the Kernel 6.1.15


Bug#1033237: Missing Image for linux-image-6.1.0-7-amd64

2023-03-20 Thread Jannick Loch

Package: nvidia-driver
Version: 6.1.0-7

Durimg my update routine, i notice that the build for amd64 is missing, so that 
i would broke my installation when i want to
upgrade my system. I dont know whether the package still needs time to build.

I am using Debian GNU/Linux SID with X11 and the Kernel 6.1.15


Bug#1032466: Additional Information

2023-03-12 Thread Jannick Loch
In addition to that, i have the same problem with the latest linux 
kernel 6.1.15-1.




Bug#1032466: Performance problems with nvidia-driver version 525.89.02-1

2023-03-07 Thread Jannick Loch

Package: nvidia-driver
Version: 525.89.02-1

The first Problem is, when i enable Vsync at any game, the framerate wont sync 
to my monitor refreshrate, it stuck at 60hz.
And the other Problem is, when i install the Extension Dash to Dock, all games 
say that they has more than 60hz, but i can see with my eyes and with a tool, 
that my monitor shows only 60 hz.


I am using Debian GNU/Linux SID with X11 and the Kernel 6.1.12-1.


Bug#1017601: Additional Infos

2022-08-18 Thread Jannick Loch

The Packages with the unsatisfiable dependencies are:

*libgnome-desktop-4-1*

*libgnome-rr-4-1*

*libgnome-desktop-3-19*

*libgnome-bg-4-1***


Bug#1017601: Missing dependencies for meta-package gnome

2022-08-18 Thread Jannick Loch

Package: gnome-desktop
Version*: ***43~alpha-3


During my peroid update routine, I notice that i have unsatisfiable 
dependencies that doesn't fit with the


binarie package gnome-desktop3-data. It semms that the following 
packages are out of date, so that i can't upgrade my system anymore 
without remove important packages.


I am using Debian GNU/Linux SID and the Kernel 5.18.0-4-amd64.


Bug#1014972: Missing build for libllvm14

2022-07-15 Thread Jannick Loch

Package: libllvm14
Version: 1:14.0.6-1

During my period update routine, I notice that the I386-Build
for libllvm14 is missing and i can't upgrade relevant system packages 
anymore.



I am using Debian GNU/Linux SID and the Kernel 5.18.0-2-amd64.



Bug#1012882: Missing build for gcc-12 amd64

2022-06-16 Thread Jannick Loch

Package: gcc-12
Version: 12.1.0-3

During my period update routine, I notice that the AMD64-Build
for gcc-12 is missing and i can't upgrade my system packages anymore.


I am using Debian GNU/Linux SID and the Kernel 5.18.0-1.