ext4 or xfs? Nvidia module/s?

[ncmprhnsbl]

yeah, the blacklist nouveau is included in the 08-nvidia* modules (which is why you end up with the 640x480 framebuffer driver if the nvidia driver fails for some reason)
so, at least two possibilities:
1. that it's not possible to build the driver/kernel module without the correct hardware (it tells me explicitly that my hardware is not supported by 515 in the .run file build dialog)
2. that (if your using changes) there's something in your changes interfering.. to test this: hit TAB at the boot menu and remove the changes entry (using arrow keys and backspace) then enter. (this would be "slightly fresh" mode )

[Karmi]

yeah, the blacklist nouveau is included in the 08-nvidia* modules (which is why you end up with the 640x480 framebuffer driver if the nvidia driver fails for some reason)
so, at least two possibilities:
1. that it's not possible to build the driver/kernel module without the correct hardware (it tells me explicitly that my hardware is not supported by 515 in the .run file build dialog)
2. that (if your using changes) there's something in your changes interfering.. to test this: hit TAB at the boot menu and remove the changes entry (using arrow keys and backspace) then enter. (this would be "slightly fresh" mode )

OK...my power went out, so am on generator right now, but will give it a shot as soon as I can.

[Karmi]

yeah, the blacklist nouveau is included in the 08-nvidia* modules (which is why you end up with the 640x480 framebuffer driver if the nvidia driver fails for some reason)
so, at least two possibilities:
1. that it's not possible to build the driver/kernel module without the correct hardware (it tells me explicitly that my hardware is not supported by 515 in the .run file build dialog)
2. that (if your using changes) there's something in your changes interfering.. to test this: hit TAB at the boot menu and remove the changes entry (using arrow keys and backspace) then enter. (this would be "slightly fresh" mode )

OK...that didn't work. I have some Distros, like Sparky Linux Cinnamon (I believe is the latest one) that limited me to that 470 driver. Fedora 36 Cinnamon SPIN has me wid the 515.57 version (kernel 5.18.9-200) on the same computer. I let the OSes use what they want...so to speak. Yeah, Sparky is 470.129.06 wid a 5.18.0-2 kernel. I run Porteus 'n those two on the same computer using a 7-port switched USB Hub.

My main Porteus 5.0 Cinnamon (on a 128 GB SanDisk FIT USB) is running so smoothly 'n snappy on the nouveau driver that I'm not going to mess wid it. I set up a 32 GB one for these tests. Thanks!

[ncmprhnsbl]

ok, so i think it's safe to assume :
1. that it's not possible to build the driver/kernel module without the correct hardware
at some point , someone with the appropriate hardware might build it and share... i'll leave the module link up, in case someone else wants to experiment..
the good news is that nvidia have recently opensourced their driver, so hopefully this means the nouveau driver may gain some more improvements..

[Karmi]

ok, so i think it's safe to assume :
1. that it's not possible to build the driver/kernel module without the correct hardware
at some point , someone with the appropriate hardware might build it and share... i'll leave the module link up, in case someone else wants to experiment..
the good news is that nvidia have recently opensourced their driver, so hopefully this means the nouveau driver may gain some more improvements..

ncmprhnsbl - an update: Did your driver just work?

Code: Select all

Graphics:
  Device-1: NVIDIA driver: nvidia v: 515.57
  Display: x11 server: X.org 1.20.14 driver: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,nv,vesa
    resolution: <missing: xdpyinfo>
  OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.57

I had done some upgrading to my main computer, in the process had moved the Nvidia GeForce 1660 GTX Super to it, and moved a Nvidia GeForce GTX 1660 to this test computer.

Still testing...had moved modules 05-devel.xzm, 06-crippled_sources-5.18.8-64.bit.xzm, blacklist.xzm, and your 08-nvidia-515.57-k.5.18.8-porteus-v5.0-x86_64.xzm to the Porteus Modules folder. Rebooted and the graphics were something like 800x600 (terrible).

Then I deactivated the blacklist.xzm module and rebooted to what I am getting now - 1920x1080 (?). Maybe deactivating the blacklist.xzm module worked??

[Karmi]

ok, so i think it's safe to assume :
1. that it's not possible to build the driver/kernel module without the correct hardware
at some point , someone with the appropriate hardware might build it and share... i'll leave the module link up, in case someone else wants to experiment..
the good news is that nvidia have recently opensourced their driver, so hopefully this means the nouveau driver may gain some more improvements..

Another update on a different Porteus installation, but same test computer:

Before - this was w/o anything done to the Porteus installation:

Code: Select all

Graphics:
  Device-1: NVIDIA driver: nouveau v: kernel
  Display: x11 server: X.org 1.20.14 driver: loaded: modesetting
    unloaded: fbdev,vesa resolution: <missing: xdpyinfo>
  OpenGL: renderer: NV168 v: 4.3 Mesa 21.3.5

Then Added your 515 driver (got 800x600 after reboot):

Code: Select all

Graphics:
  Device-1: NVIDIA driver: N/A
  Display: x11 server: X.org 1.20.14 driver:
    loaded: nouveau,nv,vesa unloaded: fbdev,modesetting
    resolution: <missing: xdpyinfo>
  OpenGL: renderer: llvmpipe (LLVM 13.0.0 256 bits)
    v: 4.5 Mesa 21.3.5

Then added the 05-devel.xzm module and got this after reboot:

Code: Select all

Graphics:
  Device-1: NVIDIA driver: nvidia v: 515.57
  Display: x11 server: X.org 1.20.14 driver: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,nv,vesa
    resolution: <missing: xdpyinfo>
  OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.57

Resolution is great...is your module working?

[ncmprhnsbl]

Then added the 05-devel.xzm module and got this after reboot:

Resolution is great...is your module working?

strange... certainly looks like it.. try nvidia-settings to confirm..
no idea what's in 05-devel that would make a difference...

[Karmi]

strange... certainly looks like it.. try nvidia-settings to confirm..
no idea what's in 05-devel that would make a difference...

That's the only real "nvidia-settings" I could find...there was some "Desktop nvidia-settings" and other nvidia info. I did a double-check on the 05-devel after you said you had no clue on it, and restored original installation image. You were right. Wid just your 515 module added 'n activated 'n rebooted, it was back to the 800x600 (?) screen. I then did another reboot and got the 1920x1080 screen.



Lucky guess on the second reboot, but I do a lot of guessing when testing.

[Rava]

^
Strange that your nvidia-settings has no entry in your "X Screen 0" called "Open GL/GLX information" - mine does, and it displays the wanted

Code: Select all

GLX Information
Direct Rendering: Yes

in there. :weird:
Due to older hardware my driver is 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm

[Karmi]

^
Strange that your nvidia-settings has no entry in your "X Screen 0" called "Open GL/GLX information" - mine does, and it displays the wanted

Code: Select all

GLX Information
Direct Rendering: Yes

in there. :weird:
Due to older hardware my driver is 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm

Yeah, I don't know much about what the Nvidia drivers are supposed to do or say. Mainly just look for what driver version is listed...also what is listed as "driver" under "Graphics" after running inxi -F.

Both my Fedora 36 Cinnamon SPIN & Sparky 6.4 Cinnamon show the "Direct Rendering: Yes" under the "Graphics Information" > GLX tab. Porteus 5 Cinnamon is the same. The Fedora install has a Nvidia 515.65 driver 'n the Sparky install has a Nvidia 470 driver...all on the same GeForce GTX 1660 card.

On another test computer wid a GeForce GTX 1050 Ti card: Porteus 5 Cinnamon shows the same Nvidia 515 driver 'n same inxi -F "Graphics" info. Sparky won't boot on that computer for some reason!? Have been trying to figure out if I like Sparky 7 or Sparky 6.4 best...weird. Anyway, Fedora 36 Cinnamon SPIN is booting 'n shows same Nvidia 515.65 driver 'n same inxi -F "Graphics" info.

The Fedora & Porteus > Settings > System Info show the Nvidia GPU's changing from a 1660 to a 1050 when changing computers, but other info looks the same. Looks OK, but I dunno...

[Rava]

I don't know much about what the Nvidia drivers are supposed to do or say.

Nvidia is deliberate murky about the finer details.

the good news is that nvidia have recently opensourced their driver, so hopefully this means the nouveau driver may gain some more improvements..

Hopefully that enables me to create a 340.??? driver for a kernel newer than 5.4.30-porteus… especially neat it would be when I manage to create a driver for the official 5.0 x86-64 kernel - since that one most users will use by default.
And an OS like Porteus is especially suited for older hardware… e.g. using a slim DE like Openbox, XFCE or such.

[Karmi]

I don't know much about what the Nvidia drivers are supposed to do or say.

Nvidia is deliberate murky about the finer details.

the good news is that nvidia have recently opensourced their driver, so hopefully this means the nouveau driver may gain some more improvements..

Hopefully that enables me to create a 340.??? driver for a kernel newer than 5.4.30-porteus… especially neat it would be when I manage to create a driver for the official 5.0 x86-64 kernel - since that one most users will use by default.
And an OS like Porteus is especially suited for older hardware… e.g. using a slim DE like Openbox, XFCE or such.

Here's an update to my previous reply - Forgot I was testing Ubuntu 22.10 (Kinetic Kudu) Daily Build yesterday. When installing it I selected the add 3rd party software option 'n it automatically installed the Nvidia 515.65.01 driver, which was verified by inxi -F. That was on the GeForce GTX 1660 'n same for the GeForce GTX 1050 Ti...

[mmortal03]

Hopefully that enables me to create a 340.??? driver for a kernel newer than 5.4.30-porteus… especially neat it would be when I manage to create a driver for the official 5.0 x86-64 kernel - since that one most users will use by default.
And an OS like Porteus is especially suited for older hardware… e.g. using a slim DE like Openbox, XFCE or such.

Would it be possible to convert the nvidia-legacy-390xx-driver deb package to a module to use in Porteus? Like you said, Porteus is especially suited for older hardware.

I'd like to try out the nvidia legacy driver as an alternative to nouveau on my machine (has NVIDIA GF119M [GeForce 610M]) if someone can convert the legacy driver for testing. I have no idea how difficult this is for graphics drivers. I'm very new to Porteus and have never used Slackware before.

[beny]

hi karmi for the conversion you can use deb2xzm or alien but the nvidia driver are linked to the kernel version,also the name have to be the same,if i remember well it is a lot of time that i use noveau instead nvidia driver

[Rava]

Would it be possible to convert the nvidia-legacy-390xx-driver deb package to a module to use in Porteus

No, you have to compile the NVidia driver especially for the certain kernel you are using.
That is the reason why I have to use the 5.4.30-porteus kernel since that is the newest kernel I was able to compile the driver 340.108 for.
When you need the 390.??? driver, it must be compiled for the kernel you use (as long as that kernel is supported, if not you have to use an older kernel) If you plan on using a different kernel in the future, you again have to compile the nvidia driver for that different kernel.
At least with the NVidia legacy drivers as distributed as *run files containing the C source code these only work for the very kernel they are compiled under, and not work for any other kernel.

To be able to compile the driver, you need a certain boot configuration that blacklists the generic graphics driver and also includes the stripped kernel sources, as well as 05-devel. And of course the correct Nvidia-driver-390.???.run file (that is a self-extracting archive)

Somewhere there is a thread on https://forum.porteus.org with a script by blaze that tries to make creating such a driver more easy, but my experience with that script is that it also included stuff not related to the NVidia driver, so I had to extract the resulting module and remove files and folders from it.

That is the main reason why the name of my NVidia driver contains the kernel version as well:

Code: Select all

010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm

Maybe look into the thread (or threads) about me creating the 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm driver or similar drivers e.g. by donald - hopefully that gives you enough insight on how to compile your own nvidia driver module.