Moderator: Forum moderators
Did the
Code: Select all
apt install nvidia-tesla-kernel-dkmsThe nvidia driver seems to be compiled and installed.
How do you change from using the nouveau driver to the nvidia driver?
--------------------------------------------------
Had to also download and install the nvidia-settings program.
Code: Select all
apt install nvidia-settingsIf I can get the nvidia driver being used.
nvidia-settings should be what is used to make settings for the drivers operation.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
Start with apt install nvidia-driver. Then, wmexit followed by xorgwizard from the console. Set the driver to nvidia, apply, exit and xwin to start X.
First I made a save file with lots of free space in it.
Just to make sure there is room to install the nvidia software.
I did this, but it did not work.
Driver and all it's files seem to be installed.
When I run xorgwizard and select to use nvidia driver, set resolution, color depth.
Close xorgwizard.
Enter xwin it goes to a working desktop, but it is still using the nouveau driver.
---------------------------------------------------------------------------------------------------------------
During the install of the nvidia software, it gives this message.
.
I tried doing a reboot and it booted to the point of trying to start x server.
This does indicate that nouveau driver did get blacklisted and did not get loaded.
Entered xorgwizard and tried to make needed settings as before.
Closed xorgwizard,
Entered xwin.
Get messages about trying to start, but just hangs for a time, and ends back at needing to run xorgwizard.
Non of the driver options in xorgwizard will work.
Cannot get to a working desktop.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Try lsmod | grep nv. Maybe nouveau is not blacklisted and gets loaded instead of nvidia.
OK.
But at what point in the process should I do this?
Keep in mind that when the nouveau driver seems to be blacklisted.
Indicated by the boot process stops at having to run xorgwizard.
xorgwizard will not make any changes and whatever choices it does have are not working.
I am starting to wonder if this driver software is too setup for Debian OS.
Also during the download and install of the software.
A list of optional recommended software is given, but not downloaded and installed.
I guess they except you to copy or write down this list of software and later use apt to download and install it. 
One of them was the nvidia-settings program.
---------------------------------------------------------------------------------------------------------------------
The nvidia driver run packages, from nvidia web site, do not care what Linux OS you install into.
It does need the stuff needed to compile available in the Linux OS.
In the past, Puppy devx and kernel sources sfs's.
Does Bookworm Pup64 already have this or a way to install it?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Doesn't matter. Ensuring that nouveau is blacklisted is the first step towards isolating the problem.
Doing what the warning says when installing the nvidia driver software.
Simply reboot.
There are scripts that got installed to blacklist nouveau driver, that get run, IF you reboot after installing the nvidia driver stuff.
After doing a reboot and getting to the point of starting x server.
It stops at needing to run xorgwizard.
Entered
Code: Select all
lsmod | grep nvResults:
nvidia 56532992 0
drm 614400 1 nvidia
Again running xorgwizard if you input nvidia as driver, set resolution, set color depth.
Do xwin.
Hangs at trying to start x server, but ends up back at saying to run xorgwizard.
Now xorgwizard seems to have no affect.
None of the selected options for driver to use, will get it to start x server.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Start with apt install nvidia-driver. Then, wmexit followed by xorgwizard from the console. Set the driver to nvidia, apply, exit and xwin to start X
.
No affect when you run xorgwizard and select to use nvidia driver.
It does start x server, but it uses the nouveau driver and ends at a working desktop.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
The getnvidia program written for Puppy, had code that did a good job of blacklisting the nouveau driver, and xorgwizard working to choose nvidia driver.
Wonder if there is a clue in that programs code 
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Anyone been able to get this to work?
The stuff provided by apt seems to be too much compiled for Debian.
Just will not work in Bookworm Pup64.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@bigpup :-
Huh.
I fancy you're running into the same brick wall that I've found when asking about this stuff, mate. Either nobody knows, nobody's interested, or.....nobody cares.
I've never managed to elicit any help, either.
Mike. 
@bigpup
Just saw a link to this post on the vanilla section.
Have not used BW64 yet, so not sure if this would work
Have you tried adding modprobe.blacklist=nouveau to the boot entry (append line)? And/or remove the nouveau drivers from zdrv
That's how I do it when I update the kernel and have to recompile the driver, on fossa. As the getnvidia pet wouldn't work on pupmode 5
I have been able to get booted, not using the nouveau driver, and using the vesa driver.
Not that exact way you say to try.
I will give it a try and see what happens.
Have to work on this later tonight.
Thanks!
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
I also took a wack at this. Following various instructions across the forum. Same results you guys have.
I ended with an appeal to the BKW64 thread: @666philb had made things so easy for users with these adapters to step into FP64. I was curious, there, if there was a hidden utility replicating his work.
I continue to try efforts to arrive at some way to achieve a desktop.
Oh well.
Experimental Nvidia Driver Pet for Testing with BookwormPup64 10.0.3 k 6.1.55
This pet was created from the Linux X64 (AMD64/EM64T) Display Driver version 525.105.17
released on 2023.3.30. That can be viewed here https://www.nvidia.com/download/driverR ... 351/en-us/
Step1: Visit the above link & check on the "Supported Products" tab that your card is listed.
Step2: If it is supported backup the save file/folder of your working copy of BKW64 10.0.3
Step3: Download the pet [ nvidia-glx-525.105.17-k6.1.55-64.pet ] from the shared Google Drive link below.
Step4: In System/Boot Manager select "Modules" and blacklist the nouveau module.
Step5: Install the pet then reboot saving the session and confirm that the Nvidia driver is running.
Step6: If it is, launch + reload Synaptic then install "nvidia-settings version 525.125.06-1-deb12u1"
Accept any offers to install additional Debian packages and accelerators/codecs
Also accept the offer to clean-up the Nvidia install.
Step7: Reboot saving the session and test nvidia settings which should be on the System menu.
LINK TO PET: https://drive.google.com/drive/folders/ ... sp=sharing
Final Thoughts:
The pet is large at 597MB but I think that the clean-up eliminates the supported drivers that are not used.
This pet has only been tested with my own Geforce GTX 1050 Ti card.
Fingers crossed that it works for you.
Thanks for working on this! 
Your Nvidia driver pet works for me.
Bookworm Pup64 10.0.3
Frugal install and using old save folder from Bookworm Pup64 10.0.2
After doing the pet install and blacklisting nouveau driver.
On reboot.
It booted to having to run xorgwizard.
Set nvidia as the driver
Set resolution
Set color depth.
Closed xorgwizard.
Entered xwin.
Finished booting to working desktop using Nvidia driver.
When installing the "nvidia-settings version 525.125.06-1-deb12u1
Could find only this one "nvidia-settings version 525.125.06-1-deb1
Probably the same just having -deb1 and not -deb12u1 in the name of the file.
Anyway, the Nvidia settings program is installed and working.
Note:
If they change the kernel to a different one in the next update of Bookworm Pup64.
This driver is not going to work.
It will only work if kernel 6.1.55 is being used.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@bigpup
Thanks for testing this pet and your report of success albeit with a slightly different experience
to my own in that you needed to run xorgwizard.
With regard to installing nvidia-settings I should have mentioned that I refreshed Synaptic before
searching for the package(will edit post). A shot of my current state of play is attached.
Were you given the additional packages offer & clean-up offer?
I should also mention that I ran full ListDD system scans before and after the installs & was pleasantly
surprised that they both showed no missing deps.
I will get to your questions after I figure out why it is no longer booting.
After installing your Nvidia pet.
It did boot using the Nvidia driver the first time I rebooted and seemed to work.
After a power off shutdown.
The next day I booted and it went as far as needing to run xwin or xorgwizard.
Now no setting changes I can select in xorgwizard allows it to boot to desktop.
Tried all driver options including manual entry to use Nvidia.
Unclear why it worked on the first reboot, after installing the Nvidia driver, and now it will not boot completely to working desktop.
I am not having fun right now! 
Going to first try a fresh clean save and new install of the pet.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Personally, I haven't yet even looked at BookwormPup64. Like I stated a few months ago, there seems to be VERY LITTLE in the way of help/advice with this stuff coming from anyone in the community.
Even the creator of BookwormPup64 seems to be 'stumped' here. I guess that's fair comment; it's hard to be an "expert" on something you may never have used yourself.... 
Most Puppians are simply re-purposing old hardware.....which in probably 95 cases out of 100 comes with standard built-in Intel graphics. Those of us who have bought Nvidia cards, it's usually a conscious decision on our part to spend the extra cash, install said card and try to get it working.
In my own case, I'm 'stuffed' on TWO fronts here, 'cos I voluntarily installed a discrete Nvidia card in this desktop when it was new 3 years ago.......and when I replaced the laptop last year for the "newer" Dell Latitude, what should it come with but a mobile Nvidia GPU built-in. So for me, it's presently either nouveau OR 'official'. I don't have any other choices ATM.
Yes, I could remove the Nvidia card from the desktop and revert to using the CPU's on-die Intel HD graphics.....but that then means resetting around 15 Pups to use a different graphics driver, and remove all trace of the Nvidia stuff. From what I can see of it, when compiling/installing from GetNvidia, removal is a tedious manual process. NOT going there!
----------------------------------
Isn't the DKMS stuff supposed to automatically re-compile these drivers in Debian, at kernel upgrade time? I know I have managed to update the driver in Puppy by re-running GetNvidia with a newer .run file.....but I've never heard of anyone trying to un-install one. I suspect most Puppians in that boat simply wipe the 'save' and start over again from scratch....
This is WHY I've avoided these recent Debian-based builds. Not because I don't appreciate the sheer effort that's gone into them - technically, you can't fault them - but simply because there's so much about them that is TOO like the parent distro they're based on. I tried Dima's VanillaDPup, and all it would allow me to use was vesa; it wouldn't let me use nouveau! HUH??
I'm currently in the middle of an argument with somebody at Linux.org, who is adamant that nobody has any business trying to compile & install graphics drivers themselves.......that it's a task best left to the semi-mythical "experts" on the distro dev teams, and that you should always, always, ALWAYS use the "official" packages in the repos that somebody else has built. In his view, we're completely nuts for doing it the way we do via GetNvidia..!
I cannot convince the guy otherwise. 
Why am I not surprised?
(*shrug...*)
Mike.
you should always, always, ALWAYS use the "official" packages in the repos that somebody else has built.
I would agree if we had packages specifically compiled for Bookworm Pup64 and had a Bookworm Pup64 repository to put them in.
But this is Puppy Linux and the best repository of software we now have is this forums Additional Software section.
Specific topics like this one, trying to provide properly compiled software package.
Apt getting software from the Debian repositories is OK.
BUT IT IS NOT 100% always working software in Bookworm Pup64.
The Nvidia driver provided by apt install is one that does not work.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Before trying to use ETP's pet and now after installing the pet.
Booting from a cold power off to hot power on condition.
In all my attempts at getting this to work.
It always seems, when booting up, that something is controlling graphics, other than xorg.conf
I say this, because when it gets to trying to start Xserver.
If you run xorgwizard to make setting changes.
These changes seem to not be considered and used to run xserver.
Something else is being used.
If it is messed up.
Then xserver does not startup.
You get message to run xwin or xorgwizard.
-----------------------------------------------------------------------------------------------------------------------------------
Right now, with my boot up, from a cold power off state.
It gets to trying to start xserver and stops.
Message to run xwin or xorgwizard.
No changes to xorgwizard, seem to get it to continue booting to xserver running, and a working desktop.
It does boot OK, if no save is used, and does a clean first boot.
Uses the nouveau driver.
WELCOME TO LINUX SOFTWARE 
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
I did not have time yesterday to try a clean install of the Nvidia pet.
Going to try again soon.
First with Bookworm Pup64 10.0.3 booting up.
I am seeing a message that says something about something not being able to read.
Pops up fast and not easy to read message, before it is gone.
Not something I was seeing with Bookworm Pup64 10.0.2 booting.
Let me see if this could be a clue to solving the issue.
Update:
After several reboots this error message is no longer showing up.
Could have been something that fsck found and corrected.
fsck is being run on each boot by having pfix=fsck in the boot loader entry.
Now time to try the pat package again.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Fresh new save folder.
Fresh new install of the Nvidia 525.105.17.pet
I got this after installing the pet.
.
.
Clicked on restart PC now.
It rebooted to a working desktop with using the Nvidia driver.
Have tried several reboots and it seems to be working OK at this time.
Note:
When I had reboot issues.
I did make some setting changes using the Nvidia settings program, then did a reboot.
Maybe something the Nvidia settings program changed is the issue I had.
I do know to not let it make an xorg.conf file to use. That will mess up booting.
Do not think I did that. It is an option you have to select in the program.
Maybe not installing the exact Nvidia settings program ETP did, is an issue with using it to change settings.
Next step:
Get and install the exact same version of the Nvidia settings program ETP used.
Will report how that goes.
NOTE:
All the nvidia driver run packages I have gotten from the Nvida web site.
They always provided and installed the Nvidia settings program.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
ETP,
What are you using to build the pet with?
Nvidia driver package from Debian repo or the Nvidia driver run package from Nvida web site?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Never got an option to clean-up after install of the pet.
ETP where are you getting this?
Installing the Nvidia-settings program I got this:
.
.
Is this what you are talking about cleanup?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Hi bigpup,
Yes, plus the offer to install GLX stuff.
It is crucial that you install the package I specified. Here are the properties of that package:
Note that a Predepend is the nvidia-installer cleanup and any missing Recommends should also be offered and
should all be accepted.
With regard to Nvidia Settings itself once installed I would not advise changing any settings unless Flipping is
causing an issue with SSR but even then SSR can be set to turn it off purely during the recording.
Please see my previous post also:
The pet was created with the Nvidia run package in conjunction with the GetNvidia pet which acts as a sanity check and
offers to create a pet and/or sfs. It did not work just by itself and I had to prevent nouveau loading and force vesa mode
in order to create the pet which I then tested with a fresh install. To force vesa mode I first blacklisted nouveau within puppy then
rebooted (saving the session) . The boot was then interrupted in order to edit the kernel line on the fly to ensure total blacklisting.
The code inserted there was:
Code: Select all
nouveau.modeset=0The pet was created with the Nvidia run package in conjunction with the GetNvidia pet which acts as a sanity check and
offers to create a pet and/or sfs.
The Nvidia run package should have also provided the Nvidia-settings program.
I wonder why it did not get in the pet package?
--------------------------------------------------------------------------------------------------------------------------------------
I do now have installed all that you installed and the Nvidia driver is working OK.
-----------------------------------------------------------------------------------------------------------------------------------
About using the Nvidia-settings program and making settings with it.
Never had any issues before using with other Puppy version installs.
So should be able to do it with this install.
The Nvidia-settings program is now the controlling program to use. AND ONLY IT!
It configures a specific settings file used by the Nvidia driver.
This settings file is only file used to run the driver.
It is no longer controlled by any xorg settings.
Usually, just making changes in the settings program, are put into this file, as you make the change.
Just close the program when done.
Again if you select to let the Nvidia-settings program make a new xorg.conf file.
It will replace the Puppy one and it will brake booting.
So never select that option in the settings program.
Maybe the first time I used the Nvidia-settings program, I accidentally selected to make the xorg.conf file.
It is a button you click on.
Moving over the open window with the mouse cursor.
I could have accidentally pressed the selection button.
So time to finish the testing and make some setting changes using the Nvidia-settings program.
See what happens.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Looking at what is in your Nvidia driver pet.
It does seem to have the Nvidia-settings program in it under /usr/bin/
But it does not have a .desktop file in /usr/share/applications/
So no menu entry is made for it.
Example:
nvida-settings.desktop file you could add to your pet package.
Code: Select all
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=NVIDIA X Server Settings
Comment=Configure NVIDIA X Server Settings
Exec=/usr/bin/nvidia-settings
Icon=/usr/share/pixmaps/nvidia-settings.png
Categories=Settings;HardwareSettings;The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
So checking for nvidia-settings file.
It seems I have two of them installed.
one in /usr/lib/nvidia/current/
One in /usr/bin/
.
.
So maybe did not have to install the nvidia-settings using apt install.
It was already installed by your pet, but had no .desktop file to make a menu entry.
The menu entry that was made by installing nvida-settings by apt install.
Is pointing to the nvidia-settings in /usr/lib/nvidia/current/
Actually it is a symbolic link to a .desktop file located there.
This is what files are there:
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
I uninstalled the nvidia-settings program installed by apt install.
I made a nvidia-settings.desktop file and placed it in /usr/share/applications
Used this for the .desktop file contents:
Code: Select all
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=NVIDIA X Server Settings
Comment=Configure NVIDIA X Server Settings
Exec=/usr/bin/nvidia-settings
Icon=/usr/share/pixmaps/nvidia-settings.png
Categories=Settings;HardwareSettings;So the menu entry is pointing to the nvidia-settings program installed by your pet.
Click on the menu entry and the settings program starts up.
So the one in the pet is working.
Uninstalling the nvidia-settings installed by apt install.
I did not uninstall any of the additional software it also installed.
So not sure they are needed or not.
I guess I need to do a fresh install only using your pet.
Making a menu entry to use the nvidia-settings program it installs.
Never do anything with apt.
See how that works
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
2nd test of the Nvidia driver pet provided by ETP.
Booted Bookworm Pup64 10.0.3 with a fresh clean save folder.
Only has basic settings (WIFI setup, location, time, etc....) in the save.
Did these steps:
1. In System/Boot Manager select "Modules" and blacklist the nouveau module.
2. Install the pet.
LINK TO PET: https://drive.google.com/drive/folders/ ... sp=sharing
3. Added this nvidia-settings.desktop file to /usr/share/applications/ so there will be a menu entry to run the program from.
4. Reboot saving the session and confirm that the Nvidia driver is running.
On reboot it is all working OK.
Driver is being used and nvidia-settings program can be run by clicking on menu->System->Nvidia X Server Settings.
Can change settings in the nvidia-settings program and they work to control the driver.
So ETP, no need to install the nvidia-settings program with apt install. Your pet install has already installed it.
Your pet just needs to have in it the nvidia-settings.desktop file located in /usr/share/applications/
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected