Siduction Forum

Siduction Forum => Software - Support => Topic started by: samu on 2019/02/28, 20:41:32

Title: A strange problem with the nvidia driver
Post by: samu 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  ???
Title: Re: A strange problem with the nvidia driver
Post by: piper 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




Title: Re: A strange problem with the nvidia driver
Post by: axt on 2019/02/28, 21:25:42
You really need nvidia for a GF9500? Take nouveau! It works with kernel 5.0rc8.
Title: Re: A strange problem with the nvidia driver
Post by: dibl on 2019/02/28, 23:40:47
Says here (https://www.nvidia.com/Download/driverResults.aspx/135161/en-us) 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.
Title: Re: A strange problem with the nvidia driver
Post by: axt 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  (https://devtalk.nvidia.com/default/topic/1047179/linux/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.
Title: Re: A strange problem with the nvidia driver
Post by: samu on 2019/03/01, 18:16:47
I returned temporarily to nouveau.
Title: Re: A strange problem with the nvidia driver
Post by: samu 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?
Title: Re: A strange problem with the nvidia driver
Post by: axt 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.

Title: Re: A strange problem with the nvidia driver
Post by: piper 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.
Title: Re: A strange problem with the nvidia driver
Post by: axt 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
Title: Re: A strange problem with the nvidia driver
Post by: piper 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

Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/03, 00:20:59
And you may now use a 4.20 kernel

https://forum.siduction.org/index.php?topic=7600.0;topicseen
Title: Re: A strange problem with the nvidia driver
Post by: axt 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 (https://metadata.ftp-master.debian.org/changelogs//non-free/n/nvidia-graphics-drivers-legacy-340xx/nvidia-graphics-drivers-legacy-340xx_340.107-4_changelog), bugreport #922479 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=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 (http://rglinuxtech.com/?p=2513) also) have the agonizing choice:

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

Title: Re: A strange problem with the nvidia driver
Post by: axt 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.
Title: Re: A strange problem with the nvidia driver
Post by: melmarker on 2019/03/03, 11:07:52
OK, wenn der Hammer nich passt ist das ein Problem des Nagel - interessante Sichtweise.
Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/03, 14:14:27
Now, here we go again

nouveau SUCKS for a lot of people and a lot of cards

I happen to own one of those cards, the intermediate freeze's and total lockups where only a hard reboot is a must every 5 minutes is not what I call a good experience. (it has got better, it doesn't happen every 5 minutes, but still happens) This was even before I attempted to start a game or something simple like firefox, konqueror.

Don't tell me to buy Intel, AMD, or use nouveau, because after all, linux is about choice, not what others preach and this is also the year 2019.

I chose nvidia because I was a ati guy before, but, in the late 90's, ati drivers sucked in linux, as years went by they got even worse for gaming. I am a father/grandfather who does not own a xbox/playstation and don't plan on it in the future, I also won't boot to windows.

A search engine shows (years 2018/2019) what I am saying here is spot on about nouveau.

The times I have been thanked on IRC for having people install the "dreaded nvidia drivers"  because their computers freeze and lockup is also proof.

I am all for free software, but, if the developers of "operating systems" can't get some things right, people will move on, maybe move right back to windows or a version of linux that supports proprietary drivers and don't shove the free ones that don't work as good as the proprietary ones down peoples throats .

In time, this will get worse with free drivers (gpu) (linux is on 3-4 % of the world, it doesn't matter)

I, myself would rather use proprietary drivers than going back to windows or buy a card like Intel that can't be used for gaming, the benchmarks (yes, benchmarks are useless) as of today AMD still don't cut it for "gaming" against nvidia and some modern games have problems that nvidia just doesn't have.

You go to any gaming site recently  (by the way 2028 is a long ways off,  you need to search what that means if you don't already know for graphics cards)

The battle between Nvidia and AMD continue, I know a lot of these guys and I trust the guys that own both cards (the most recent expensive)

Quote from: Enverex
Here is detailed explanation

As someone that recently used an AMD card and Nvidia card in the same machine, they aren't wrong.

There are still lots of "Oh, this doesn't work on Mesa yet" or "You need to try doing all these workarounds if you're on Mesa" issues on the open source AMD drivers which isn't an issue on Nvidia.

It's 95% the way there, but that 5% of issues with games simply doesn't exist on the Nvidia side of things. This will disappear in time, but to pretend it doesn't exist right now is misleading people (and me, which really pissed me off when I found all these issues that everyone was silent about on Reddit).

I'm referring purely to gaming here, nothing else.

Quote from: RussianNeuroMancer
With ATI, if you pass an invalid arg, or call a method at the wrong time, they will generate the correct error. This sadly leads to a situation where a developer uses an NVidia card for development, ships, and then it won't run on ATI or Intel cards. The upshot is that people incorrectly assume that ATI drivers suck. They don't. Nvidia drivers are the ones that suck!"

Quote from: UrbenLegend
The problem is that if you don't have an Nvidia gpu you have games that break now. Forget about 2028. That's all speculation. The fact is you still have games that need workarounds with AMD. There are some people who are willing to accept that but there also those that will not, which is why I think /u/RussianNeuroMancer's post is being needlessly elitist by assuming that everyone using Linux is masochistic enough to buy GPUs that may or may not run the games that they purchase.

I just can't buy a GPU that I am not even sure will work or not. It's a lot of money.

Everyone here is saying we should blindly support AMD even though functionality doesn't work. But that's like backing a Kickstarter.

In the final end, it's all about choice, in my own experience, in everything I have read/researched/followed in todays modern linux,  proprietary drivers will always win over free drivers, no ifs, ands, or buts about it.
Title: Re: A strange problem with the nvidia driver
Post by: unklarer on 2019/03/03, 15:49:18
@piper,

I'm not a gambler. I am a "normal" Linuxer.
With me there were always only ati cards. Coincidence.
That's why my main graphics card died yesterday.   :o

That's what I wanted to tell you for your valuable threads and thank you very much!   ;)
Title: Re: A strange problem with the nvidia driver
Post by: axt on 2019/03/03, 16:12:34
piper, have a cup of tea! ;-)

In another forum...I have been concerned for years about the problems of users with nvidia drivers (because you have to explain to them over and over again how to install them correctly).

I also used them myself for a lot of years (they have their advantages), but I have had to be annoyed again and again about their incompatibility to current kernels.

But current kernels are important to me. Really up-to-date. With nouveau they are possible. Of course you should know the limitations (https://axebase.net/blog/2018/12/09/falkon-chromium-freezes-glitches/).

Everyone has to know it for themselves. I don't missionize, I only advise.

...and Radeon...I use an old notebook with C2D at the customer's site. The Radeon HD5400 runs at full load under siduction default (the battery is empty in no time, the notebook gets hot). Reducing this with DPM doesn't really work so far. Not so great.
Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/04, 01:08:01
axt

Shit,  you just made me realize I forgot my fucking smileys in the above post, makes me sound like an arrogant bastard  ...  wait a minute ... I am   :P

Tea  that's a damn insult ! 

My wife is British, not me, real men drink beer and Jack Daniel's, not some shit drink that I would wash down with panther piss ;)

Nvidia drivers have to be one of the easiest drivers to install/remove, what makes it really messed up and confusing is debian's wiki on how to do it.

That page should be totally deleted, did you know if you follow that wiki to install nvidia drivers you can install siduction operating system faster, I shit you not, been there, did that, and have the t-shirt.

Quote
==========================
 install abort, close the terminal
==========================
O: siduction was successfully installed to hd.
O: Exiting after 2:35.
O: siduction-installer terminated
root@siduction:/home/siducer#

That's using cli-installer, and is this install kde - (201901291115)

Hell, back in the knoppix and kanotix they were easy also, I believe back then we used dmakms, kernel-source, and a xorg.conf, then it was just a matter of running sh./nvidia-linux -whatever.run

fglrx was a little harder to install till kano made his script ;), I was a proud owner of a 128Mb ATI Radeon 9800 Pro ALL IN WONDER which replaced my vga wonder ;) back then.

ATI Radeon 9800 Pro 15 years later, what can it play?!  :)

https://www.youtube.com/watch?v=mH9spMhAbS0

My rant is over :P

ψ-ψ-ψ-ψ-ψ-ψ-ψ-ψ-ψ-ψ-ψ

unklarer

Herzlichen Dank :)


Title: Re: A strange problem with the nvidia driver
Post by: tommy2 on 2019/03/04, 09:49:09
@piper, that's Jack on the rocks straight up for the best effect!  8)
Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/04, 12:23:17
@tommy2, In a rock glass (trinkglas)  yes, on the rocks no, ice = water =ruined :P





Title: Re: A strange problem with the nvidia driver
Post by: tommy2 on 2019/03/04, 14:08:31
@piper, that's for Sunday's single barrel sip-pen. ;D
Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/04, 16:22:41
@tommy2  :P
Title: Re: A strange problem with the nvidia driver
Post by: sunrat on 2019/03/06, 00:27:38
nouveau SUCKS for a lot of people and a lot of cards
At least you didn't say for everyone with every card.
Nvidia freezes my old system with GTX560Ti every couple of days, nouveau works well.  No gaming lately.
Nvidia works well on my newer system with GTX970.  Some games are OK at 4K but some I need to run at HD for decent frame rates.  Seems to work OK with nouveau but I haven't pushed it.
Both have 4k monitors but GTX560Ti only supports up to 2560 x 1440.

Back to my cup of green tea.  ;D
Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/06, 04:24:46
Damn Brits :P
Title: Re: A strange problem with the nvidia driver
Post by: sunrat on 2019/03/06, 14:03:21
Damn Brits :P
Who's a Brit? I come from a land down under.
I also occasionally enjoy a Jack, or a Canadian Club, or a Jameson. Multinational taste in whiskey!   ;) 8)
Title: Re: A strange problem with the nvidia driver
Post by: samu on 2019/03/07, 12:31:33
Hi. Thank you for your answers to the subject. Back to Nvidia....
Title: Re: A strange problem with the nvidia driver
Post by: piper on 2019/03/08, 23:02:09
Quote from:  sunrat
Who's a Brit? I come from a land down under.
I also occasionally enjoy a Jack, or a Canadian Club, or a Jameson. Multinational taste in whiskey!   ;) 8)

Oh my, oh dear, that is a major insult to you, my apologies !!! :P

For some reason I thought you were from England, my boo-boo

My son enjoys Jameson