Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: [EN] A strange problem with the nvidia driver  (Read 6045 times)

samu

  • Guest
[EN] A strange problem with the nvidia driver
« on: 2019/02/28, 20:41:32 »
Description:    Debian GNU/Linux buster/sid
Release:    unstable
Codename:    sid

Linux unix 4.20.13-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 4.20-25 (2019-02-27) x86_64 GNU/LinuxGraphics:  Device-1: NVIDIA G96 [GeForce 9500 GT]
Display: x11 server: X.Org 1.20.3nvidia-legacy-340xx-driver   340.107-3
Quote
dmesg -k -l err,warn
[    0.239348] mtrr: your CPUs had inconsistent variable MTRR settings
[    0.251976] acpi PNP0A08:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
[    1.526014] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000084F (\PMRG) (20181003/utaddress-213)
[    1.527161] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    9.312884] w83627ehf w83627ehf.656: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    9.442631] nvidia: loading out-of-tree module taints kernel.
[    9.442720] nvidia: module license 'NVIDIA' taints kernel.
[    9.442795] Disabling lock debugging due to kernel taint
[    9.442985] nvidia: Unknown symbol rm_p2p_init_mapping (err -2)
[    9.443071] nvidia: Unknown symbol rm_init_private_state (err -2)
[    9.443172] nvidia: Unknown symbol rm_is_supported_device (err -2)
[    9.443261] nvidia: Unknown symbol rm_gpu_ops_get_attached_uuids (err -2)
[    9.443350] nvidia: Unknown symbol rm_gpu_ops_get_gpu_arch (err -2)
[    9.443436] nvidia: Unknown symbol rm_gpu_ops_memory_alloc_sys (err -2)
[    9.443524] nvidia: Unknown symbol rm_get_vbios_version (err -2)
[    9.443614] nvidia: Unknown symbol nv_is_virtualized_system (err -2)
[    9.443709] nvidia: Unknown symbol rm_resume_smu (err -2)
[    9.443815] nvidia: Unknown symbol rm_power_management (err -2)
[    9.443914] nvidia: Unknown symbol rm_gvi_free_private_state (err -2)
[    9.444001] nvidia: Unknown symbol rm_gvi_isr (err -2)
[    9.444095] nvidia: Unknown symbol rm_free_private_state (err -2)
[    9.444182] nvidia: Unknown symbol rm_disable_gpu_state_persistence (err -2)
[    9.444269] nvidia: Unknown symbol rm_init_adapter (err -2)
[    9.444356] nvidia: Unknown symbol rm_ioctl (err -2)
[    9.444444] nvidia: Unknown symbol rm_gpu_ops_memory_free (err -2)
[    9.444540] nvidia: Unknown symbol rm_run_rc_callback (err -2)
[    9.444632] nvidia: Unknown symbol rm_gvi_get_firmware_version (err -2)
[    9.444720] nvidia: Unknown symbol rm_is_legacy_device (err -2)
[    9.444806] nvidia: Unknown symbol rm_release_api_lock (err -2)
[    9.444892] nvidia: Unknown symbol rm_gpu_ops_channel_destroy (err -2)
[    9.444981] nvidia: Unknown symbol rm_validate_mmap_request (err -2)
[    9.445072] nvidia: Unknown symbol rm_gpu_ops_memory_cpu_map (err -2)
[    9.445165] nvidia: Unknown symbol rm_gpu_ops_get_uvm_priv_region (err -2)
[    9.445251] nvidia: Unknown symbol rm_isr (err -2)
[    9.445338] nvidia: Unknown symbol rm_shutdown_rm (err -2)
[    9.445424] nvidia: Unknown symbol rm_acquire_api_lock (err -2)
[    9.445510] nvidia: Unknown symbol rm_is_legacy_arch (err -2)
[    9.445595] nvidia: Unknown symbol rm_gvi_bh (err -2)
[    9.445684] nvidia: Unknown symbol rm_p2p_get_pages (err -2)
[    9.445770] nvidia: Unknown symbol rm_i2c_remove_adapters (err -2)
[    9.445858] nvidia: Unknown symbol rm_gpu_ops_kill_channel (err -2)
[    9.445947] nvidia: Unknown symbol rm_gvi_resume (err -2)
[    9.446042] nvidia: Unknown symbol rm_gpu_ops_address_space_create (err -2)
[    9.446136] nvidia: Unknown symbol rm_gpu_ops_memory_alloc_fb (err -2)
[    9.446224] nvidia: Unknown symbol rm_gvi_attach_device (err -2)
[    9.446311] nvidia: Unknown symbol rm_suspend_smu (err -2)
[    9.446411] nvidia: Unknown symbol rm_write_registry_dword (err -2)
[    9.446498] nvidia: Unknown symbol rm_gvi_get_device_name (err -2)
[    9.446584] nvidia: Unknown symbol rm_shutdown_adapter (err -2)
[    9.446673] nvidia: Unknown symbol rm_get_gpu_uuid (err -2)
[    9.446761] nvidia: Unknown symbol rm_i2c_transfer (err -2)
[    9.446853] nvidia: Unknown symbol rm_write_registry_binary (err -2)
[    9.446941] nvidia: Unknown symbol rm_get_gpu_uuid_raw (err -2)
[    9.447028] nvidia: Unknown symbol rm_gpu_ops_copy_engine_allocate (err -2)
[    9.447115] nvidia: Unknown symbol rm_p2p_put_pages (err -2)
[    9.447201] nvidia: Unknown symbol rm_perform_version_check (err -2)
[    9.447288] nvidia: Unknown symbol rm_isr_bh (err -2)
[    9.447373] nvidia: Unknown symbol rm_gvi_suspend (err -2)
[    9.447458] nvidia: Unknown symbol rm_gpu_ops_address_space_destroy (err -2)
[    9.447560] nvidia: Unknown symbol rm_gvi_detach_device (err -2)
[    9.447671] nvidia: Unknown symbol rm_gpu_ops_check_ecc_error_slowpath (err -2)
[    9.447801] nvidia: Unknown symbol rm_gpu_ops_channel_translate_error (err -2)
[    9.447927] nvidia: Unknown symbol rm_purge_mmap_contexts (err -2)
[    9.448015] nvidia: Unknown symbol rm_p2p_destroy_mapping (err -2)
[    9.448111] nvidia: Unknown symbol rm_get_device_name (err -2)
[    9.448199] nvidia: Unknown symbol rm_shutdown_smu (err -2)
[    9.448284] nvidia: Unknown symbol rm_init_smu (err -2)
[    9.448369] nvidia: Unknown symbol rm_check_pci_config_space (err -2)
[    9.448469] nvidia: Unknown symbol rm_execute_work_item (err -2)
[    9.448556] nvidia: Unknown symbol rm_gpu_ops_destroy_session (err -2)
[    9.448647] nvidia: Unknown symbol rm_shutdown_gvi_device (err -2)
[    9.448742] nvidia: Unknown symbol rm_gpu_ops_channel_allocate (err -2)
[    9.448831] nvidia: Unknown symbol rm_i2c_is_smbus_capable (err -2)
[    9.448921] nvidia: Unknown symbol rm_gpu_ops_query_caps (err -2)
[    9.449013] nvidia: Unknown symbol rm_gpu_ops_address_space_create_mirrored (err -2)
[    9.449138] nvidia: Unknown symbol rm_system_event (err -2)
[    9.449224] nvidia: Unknown symbol rm_gpu_ops_service_device_interrupts_rm (err -2)
[    9.449350] nvidia: Unknown symbol rm_gpu_ops_create_session (err -2)
[    9.449439] nvidia: Unknown symbol pNVRM_ID (err -2)
[    9.449523] nvidia: Unknown symbol rm_free_unused_clients (err -2)
[    9.449609] nvidia: Unknown symbol rm_gvi_init_private_state (err -2)
[    9.449700] nvidia: Unknown symbol rm_unbind_lock (err -2)
[    9.449786] nvidia: Unknown symbol rm_gpu_ops_memory_cpu_ummap (err -2)
[    9.449876] nvidia: Unknown symbol rm_write_registry_string (err -2)
[    9.449964] nvidia: Unknown symbol rm_get_cpu_type (err -2)
[    9.450050] nvidia: Unknown symbol rm_init_gvi_device (err -2)
[    9.450141] nvidia: Unknown symbol rm_read_registry_dword (err -2)
[    9.450228] nvidia: Unknown symbol rm_init_rm (err -2)
[    9.450313] nvidia: Unknown symbol rm_disable_adapter (err -2)

I have no idea how to solve the problem  ???

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: A strange problem with the nvidia driver
« Reply #1 on: 2019/02/28, 21:18:26 »
I am not up to date with the legacy drivers/kernels

I am not sure if kernel 5.0.0-rc8 will help or even work period.

I would wait for towo and see what he has to say if anything, he don't own a nvidia card anymore.

I myself still run one, it's not legacy yet

Code: [Select]
Kernel: 5.0.0-rc8-siduction-amd64 x86_64
[GeForce GTX 970] vendor: eVga.com. driver: nvidia v: 418.43




Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: A strange problem with the nvidia driver
« Reply #2 on: 2019/02/28, 21:25:42 »
You really need nvidia for a GF9500? Take nouveau! It works with kernel 5.0rc8.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.363
    • Land of the Buckeye
Re: A strange problem with the nvidia driver
« Reply #3 on: 2019/02/28, 23:40:47 »
Says here that 340-107 is the current driver for the GF 9 series.  You might want to do a purge and reinstall of the nvidia legacy driver.

My GTX-1060 is working well with the nvidia-driver and the latest towo kernel.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: A strange problem with the nvidia driver
« Reply #4 on: 2019/03/01, 01:18:24 »
A reinstallation alone is of no use. nvidia-340 ist incompatible with kernel 5.0-rcx. Only an installation of a patched nvidia would be possible.

NVIDIA 340.107 - Linux 5.0-rc5: Failed to build kernel module
 
With regard to kernel compatibility it lives worry-free with nouveau.

Only patches for drivers of the last generations (like your 1060, dibl) are implemented by Nvidia itself, but by far not immediately.

samu

  • Guest
Re: A strange problem with the nvidia driver
« Reply #5 on: 2019/03/01, 18:16:47 »
I returned temporarily to nouveau.

samu

  • Guest
Re: A strange problem with the nvidia driver
« Reply #6 on: 2019/03/02, 13:46:45 »
I also use debian in unstable version and I can see that there is no problem with nvidia legacy.

Code: [Select]
4.19.0-3-amd64nvidia-legacy-340xx-driver (340.107-4)Graphics:
  Device-1: NVIDIA G96 [GeForce 9500 GT] driver: nvidia v: 340.107
  Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 1440x900~60Hz
  OpenGL: renderer: GeForce 9500 GT/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107
Where may be the problem in siduction?
« Last Edit: 2019/03/02, 13:50:43 by samu »

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: A strange problem with the nvidia driver
« Reply #7 on: 2019/03/02, 14:03:50 »
You see the different?

sid: 4.19
siduction: 4.20 or 5.0-rc8 (when you have activated experimental)

The cause of the problem is Nvidia.

« Last Edit: 2019/03/02, 14:06:51 by axt »

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: A strange problem with the nvidia driver
« Reply #8 on: 2019/03/02, 18:00:10 »
@samu

You could

Code: [Select]
apt update; apt install linux-image-4.19.3-towo.2-siduction-amd64 linux-headers-4.19.3-towo.2-siduction-amd64 nvidia-legacy-340xx --install-recommends --assume-yes
That should work for you.
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: A strange problem with the nvidia driver
« Reply #9 on: 2019/03/02, 19:20:01 »
No, not a kernel from november w/o security fixes!

Whatever, take a sid kernel 4.19, install the metapackages!

Code: [Select]
apt install linux-headers-amd64 linux-image-amd64

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: A strange problem with the nvidia driver
« Reply #10 on: 2019/03/02, 22:20:41 »
@axt

Unless he removed those, he should have them.

If you look at the manifest of every build, they come with the iso.

example, my personal build from today

Code: [Select]
linux-headers-4.20.13-towo.1-siduction-amd64 4.20-25
linux-headers-siduction-amd64                4.20-25
linux-image-4.20.13-towo.1-siduction-amd64   4.20-25
linux-image-siduction-amd64                  4.20-25

Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: A strange problem with the nvidia driver
« Reply #11 on: 2019/03/03, 00:20:59 »
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: A strange problem with the nvidia driver
« Reply #12 on: 2019/03/03, 06:33:51 »
Quote from: piper
Unless he removed those, he should have them.

I'm talking about sid kernels, not towo's siduction kernels.

You wanted him to install a lone siduction kernel from November. The current sid kernel he would get with the sid metapackages is from February.

sid kernel metapackages are of course not in the siduction images. Otherwise these kernels would be installed.

Legacy nvidia has been patched. For kernel 4.20 (changelog, bugreport #922479). For next night vanilla kernel 5.0 is expected (if rc9 isn't coming yet). Then the game starts again.

Nvidia users (current nvidia drivers have been patched for kernel 5.0 only last week also) have the agonizing choice:

Current siduction kernels with nouveau or older sid kernels with nvidia. I (not a gamer) prefer the first.


Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: A strange problem with the nvidia driver
« Reply #13 on: 2019/03/03, 06:47:00 »
Btw, also the current VBoxGuestAdditions (test build 6.0.5-129041, development snapshot 6.0.97-129040, both from February 26th) are not built against kernel 5.0(-rc8).

I find this even more annoying. Finally, VMs are also used to test new versions.

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: A strange problem with the nvidia driver
« Reply #14 on: 2019/03/03, 11:07:52 »
OK, wenn der Hammer nich passt ist das ein Problem des Nagel - interessante Sichtweise.
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)