Page 3 of 3
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 11:06
by Karmi
beny wrote: ↑19 Sep 2022, 19:00
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
Thanks for the info, but the 515.57 Nvidia driver made by ncmprhnsbl is working on two different computers wid two different GPUs, so I'm sticking wid it since I've had no problems on either...
well, other than the weird double-boot mentioned on 27 Aug 2022, 09:55 to get it accepted.
Tested Nobara Linux 36 yesterday -
new Distro focused on gaming - and it recommended using the 515.65.01 driver, which was provided by the GUI dnfdragora software manager. Worked well wid my GeForce GTX 1660 card.
Basically, if a Nvidia driver works after installing it I use it, especially if the
inxi -F command verifies the driver installed.
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 13:18
by Rava
Karmi wrote: ↑20 Sep 2022, 11:06
Basically, if a Nvidia driver works after installing it I use it, especially if the inxi -F command verifies the driver installed.
Code: Select all
root@porteus:/# inxi -F
-su: inxi: command not found
Is inxi only part of newer NVidia drivers or is it a separate package?
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 13:36
by Karmi
Rava wrote: ↑20 Sep 2022, 13:18
Karmi wrote: ↑20 Sep 2022, 11:06
Basically, if a Nvidia driver works after installing it I use it, especially if the inxi -F command verifies the driver installed.
Code: Select all
root@porteus:/# inxi -F
-su: inxi: command not found
Is inxi only part of newer NVidia drivers or is it a separate package?
I use the
inxi-3.3.12_1-noarch-1.xzm module for Porteus...I forget where I got it.
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 13:48
by Rava
Code: Select all
root@porteus:/Porteus_modules# activate inxi-3.3.12_1-noarch-1.xzm
Updating shared library links: /sbin/ldconfig
root@porteus:/Porteus_modules# inxi -F
/usr/bin/env: ‘perl’: No such file or directory
inxi seems quite the bothersome program, LOL.
Added in 2 minutes 6 seconds:
The inxi-3.3.12_1-noarch-1.xzm module is a mere 296.00 KB - but needs at least 15.70 MB of perl-5.34.0-x86_64-2_slack15.0.xzm
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 13:53
by Karmi
Rava wrote: ↑20 Sep 2022, 13:50
Code: Select all
root@porteus:/Porteus_modules# activate inxi-3.3.12_1-noarch-1.xzm
Updating shared library links: /sbin/ldconfig
root@porteus:/Porteus_modules# inxi -F
/usr/bin/env: ‘perl’: No such file or directory
inxi seems quite the bothersome program, LOL.
Added in 2 minutes 6 seconds:
The inxi-3.3.12_1-noarch-1.xzm module is a mere 296.00 KB - but needs at least 15.70 MB of perl-5.34.0-x86_64-2_slack15.0.xzm
I forgot - check this thread:
useful commands , anyone to add
See #35 by ncmprhnsbl » 04 Jul 2022, 23:25 where he tells what needs added for inxi to work.
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 13:55
by Rava
after activating perl-5.34.0-x86_64-2_slack15.0.xzm inxi -F gives me this in the "Graphics" area:
Code: Select all
Graphics:
Device-1: NVIDIA GT216M [GeForce GT 330M] driver: nvidia v: 340.108
Device-2: Chicony USB 2.0 Camera type: USB driver: uvcvideo
Display: server: X.org 1.20.14 driver: loaded: nvidia
resolution: <missing: xdpyinfo>
OpenGL: renderer: GeForce GT 330M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108
Not sure what to make of that… but it seems to work.
Is xdpyinfo also a perl script?
By the name part of "py" it could be a python script…
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 14:00
by Karmi
Rava wrote: ↑20 Sep 2022, 13:55
xdpyinfo
I have no idea what "xdpyinfo" is or even a "perl script" is!?
That's how much I know. I hammer away until I can get something to work or a board member gives me the answer.
UPDATE: It does show you wid the nvidia v: 340.108 driver tho.The rest is Greek to me...
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 14:18
by Karmi
Rava wrote: ↑20 Sep 2022, 13:55
after activating perl-5.34.0-x86_64-2_slack15.0.xzm inxi -F gives me this in the "Graphics" area:
Code: Select all
Graphics:
Device-1: NVIDIA GT216M [GeForce GT 330M] driver: nvidia v: 340.108
Device-2: Chicony USB 2.0 Camera type: USB driver: uvcvideo
Display: server: X.org 1.20.14 driver: loaded: nvidia
resolution: <missing: xdpyinfo>
OpenGL: renderer: GeForce GT 330M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108
Not sure what to make of that… but it seems to work.
Is xdpyinfo also a perl script?
By the name part of "py" it could be a python script…
I checked my Fedora OS and it shows 1920 x 1080 in that "resolution" area. Will do a test and see what the nouveau driver will say.
UPDATE: Clean install wid just the nouveau driver, and inxi -F shows same
resolution: <missing: xdpyinfo> info. Nvidia drivers look OK to me...
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 14:47
by mmortal03
Karmi wrote: ↑20 Sep 2022, 14:00
Rava wrote: ↑20 Sep 2022, 13:55
xdpyinfo
I have no idea what "xdpyinfo" is or even a "perl script" is!?
That's how much I know. I hammer away until I can get something to work or a board member gives me the answer.
UPDATE: It does show you wid the nvidia v: 340.108 driver tho.The rest is Greek to me...
This is a way, lol:
su
slackpkg update
slackpkg install inxi
slackpkg install perl
slackpkg install xdpyinfo
Another way:
su
#so you won't be prompted for your root password each time
getpkg inxi perl xdpyinfo
#when prompted, I selected the second perl option, and used directory /tmp
You can then copy the resulting xzm files from /tmp to your modules folder and activate them.
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 16:47
by Karmi
mmortal03 wrote: ↑20 Sep 2022, 14:47
Karmi wrote: ↑20 Sep 2022, 14:00
Rava wrote: ↑20 Sep 2022, 13:55
xdpyinfo
I have no idea what "xdpyinfo" is or even a "perl script" is!?
That's how much I know. I hammer away until I can get something to work or a board member gives me the answer.
UPDATE: It does show you wid the nvidia v: 340.108 driver tho.The rest is Greek to me...
This is a way, lol:
su
slackpkg update
slackpkg install inxi
slackpkg install perl
slackpkg install xdpyinfo
Another way:
su
#so you won't be prompted for your root password each time
getpkg inxi perl xdpyinfo
#when prompted, I selected the second perl option, and used directory /tmp
You can then copy the resulting xzm files from /tmp to your modules folder and activate them.
See, Rava, just keep hammering away until a Porteus board member gives you the answer!
Thanks for the answer, mmortal03!
OK...the
getpkg xdpyinfo method worked! BTW, I won’t use an OS that doesn’t allow me to be a
Full-time Root user on my own computers, i.e., no su or sudo for humble me!
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: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2
v: 4.6.0 NVIDIA 515.57
OK...no more
resolution: <missing: xdpyinfo> for me!
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 16:54
by Ed_P
Karmi wrote: ↑20 Sep 2022, 14:00
I hammer away until I can get something to work or a board member gives me the answer.
ext4 or xfs? Nvidia module/s?
Posted: 20 Sep 2022, 18:03
by Rava
getpkg xdpyinfo did the trick for me.
Code: Select all
Device-1: NVIDIA GT216M [GeForce GT 330M] driver: nvidia v: 340.108
Device-2: Chicony USB 2.0 Camera type: USB driver: uvcvideo
Display: server: X.Org 1.20.14 driver: loaded: nvidia
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 330M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108
And it's a binary, and comes with a man page.
Code: Select all
/usr/bin/xdpyinfo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, stripped
Code: Select all
XDPYINFO(1) General Commands Manual XDPYINFO(1)
NAME
xdpyinfo - display information utility for X
SYNOPSIS
xdpyinfo [-display displayname] [-queryExtensions] [-ext extension-
name] [-version]
DESCRIPTION
Xdpyinfo is a utility for displaying information about an X server. It
is used to examine the capabilities of a server, the predefined values
for various parameters used in communicating between clients and the
server, and the different types of screens and visuals that are avail‐
able.
By default, numeric information (opcode, base event, base error) about
protocol extensions is not displayed. This information can be obtained
with the -queryExtensions option. Use of this option on servers that
dynamically load extensions will likely cause all possible extensions
to be loaded, which can be slow and can consume significant server re‐
sources.
And now I have to write me a script that reminds me I need these activated if I see the need in using inxi (or activates all three [with testing if one or more modules are already activated] - when I feel like coding it. [*])
Code: Select all
inxi-3.3.12_1-noarch-1.xzm
perl-5.34.0-x86_64-2_slack15.0.xzm
xdpyinfo-1.3.2-x86_64-4.xzm
______________
[*] which currently I am not. </lazy>