PorteuX and using a different kernel

[Rava]

For now, trying PorteuX failed. I want to use my standard outdated Porteus kernel, since that is the most recent kernel version I was able to compile the NVidia-driver I need for.
010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm
The name of the diver module gives both infos:
NV driver version 340.108
for kernel 5.4.30-porteus
I also used a Porteus initrd in my attempt to boot PorteuX. To be more verbose, this one:

Code: Select all

guest@porteus:/$ cat /etc/porteus/initrd.ver 
initrd.xz:20220928

[porteux]

@Rava, can you upload your kernel and Nvidia driver so we can test? And what is your video card?

Finally, I do not recommend using Porteus initrd on PorteuX.

EDIT: there is a way to patch the 340.xx driver to work on newer kernels up to 6.3.x so far: https://www.if-not-true-then-false.com/ ... a-patcher/

Basically put your .run in a given folder and download the magic script to the same folder:

Code: Select all

wget -O inttf-nvidia-patcher.sh https://nvidia.if-not-true-then-false.com/patcher/inttf-nvidia-patcher.sh

Now run:

Code: Select all

sh ./inttf-nvidia-patcher.sh -v 340.108

It will generate a patched .run that you can use to install the driver.

[Rava]

^
Okay, then first I try my kernel but with the PorteuX initrd.

If that fails, I give you the URLs to my kernel and my NVidia driver. (It should already posted somewhere on the forum. The nvidia driver file is 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm - and the kernel version is 5.4.30. I do use the vmlinuz (v.5.4.30) but also the 000-kernel.xzm for my kernel as well.)

[beny]

Hi Rava of you have the old Nvidia script you can build your driver with the kernel that you like, or am i wrong, porteus or porteux are the same Just the current branch Is different GCC and mesa and glibc and llvm are the last version.....

[Rava]

Hi Rava of you have the old Nvidia script you can build your driver with the kernel that you like, or am i wrong, porteus or porteux are the same Just the current branch Is different GCC and mesa and glibc and llvm are the last version.....

I know, but… no one was ever able to create working driver, and I looked, for the nvidia-340 version. For some reason I was the one who was able to compile the nvidia-340.108 for kernel 5.4.30 (the most recent kernel to use the vanilla NV code as I am aware of) - and I am not even that knowledgeable when it comes to NV drivers.

Now there are patches, donald told me about these, but so far I was not able to get the most recent patches and the original code for nvidia-340.108 together to try the result on newer kernels.

(it must be nvidia-340 - it can be a newer sub-version, but last I checked NV did no longer actively support its nvidia-340 branch - therefore the 3rd party patches)

[porteux]

@Rava, try this Nvidia driver using PorteuX 0.5 stable or current (but for now don't change anything at all): https://www.mediafire.com/file/qttoddvc ... el-6.2.run

[Rava]

@Rava, try this Nvidia driver using PorteuX 0.5 stable or current (but for now don't change anything at all): https://www.mediafire.com/file/qttoddvc ... el-6.2.run

Do you have an equivalent for Porteus 05-devel and the crippled-sources module for PorteuX?
Because both are needed for a .run file bing able to create the NV driver files.

Added in 4 minutes 41 seconds:
Is the md5sum correct?

Code: Select all

6796a20a72e3c59fa0e1fe1bbe2b53a2  NVIDIA-Linux-x86_64-340.108-patched-kernel-6.2.run

[porteux]

All available in the PorteuX app store.

[Rava]

All available in the PorteuX app store.

I presume you mean this: https://github.com/porteux/porteux/releases ?

[porteux]

No, the app store is an application inside PorteuX.

But you can download devel and crippled from the GitHub page as well.

[Rava]

No, the app store is an application inside PorteuX.

Got it.

But you can download devel and crippled from the GitHub page as well.

Good, since then I could set up a vanilla PorteuX for booting, but included the 05-devel and crippled-sources modules from the get-go since all want to do in that session is create the NV driver.
At least I presume chances are slim that a real vanilla PorteuX would boot succeeds but when adding just 05-devel and crippled-sources modules the boot would fail.

Added in 2 minutes 29 seconds:
I forgot to ask:

@Rava, try this Nvidia driver using PorteuX 0.5 stable or current (but for now don't change anything at all): https://www.mediafire.com/file/qttoddvc ... el-6.2.run

I presume both PorteuX 0.5 stable or current use the same kernel version?

Added in 8 minutes 29 seconds:
And last question for now before I set it all up for a test run:
When I want to use 003-xfce-4.16-current-20230710.xzm I presume I remove the 003-xfce.xzm from the exploded porteux-v0.5-xfce-4.18-current-x86_64.iso and put 003-xfce-4.16-current-20230710.xzm in its place?
With Porteus (and PorteuX) I don't boot from ISOs but use the extracted into folders variant.

[porteux]

Yes, both stable and current use the same kernel.

Yeah, you shouldn't have more than one DE module loading at the same time in any scenario.