Puppy Linux Discussion Forum

Hi @step !

Thank you for answering !
It took me a few days to get back from work and find a little time to test the patch .

I confirm that the patch works . Desktop-wallpaper works before and after installing Nvidia proprietary modules .
I still got no screen when I get out to prompt.
The fact that I can't unload devx is solved when remastering , when not choosing the devx sfs .
The remaster does not include devx and Nvidia modules are working .

Try adding nvidia_drm.modeset=1 to your boot command line.

v903 ISO file booting in various environments have been tested and are reported.

Results are here

jamesbond wrote: ↑Sun Aug 25, 2024 12:28 am

Try adding nvidia_drm.modeset=1 to your boot command line.

Thank you @jamesbond

Adding nvidia_drm.modeset=1 to the boot command line solved the issue . We got screen on prompt now .

I also noted that scripts put in the /root/Startup directory don't work when we get to desktop .

Gobbi wrote: ↑Sun Aug 25, 2024 11:29 am

I also noted that scripts put in the /root/Startup directory don't work when we get to desktop .

They should, as long as their executable mode is enabled (chmod a+x or rox right-click and select "Permissions").

I have 2 desktop PCs with old nvidia cards with the each being a decade older.

Do we have a v903 recommendation, somewhere, on steps to have reasonable success to get the cards active starting with the new pristine OOTB v903? Or a thread dedicated to use of the new v903 for simple video activation?

Curious

This post centers around a method to boot, pristine, into a desktop with your nvidia card

The instruction seek the following: Here's where I am not sure if v903 has the same or similar utilities to use,. once, booting into the Fatdog desktop. This is only done once for a v903 on its pristine boot. Thereafter, the steps are unnecessary.

I am going to go out on a limb and use something similar to these instructions I found for another linux distro, since no recommendation for this 903 version, thus far. These are instructions I found, by EarthlingKira, that is consistent with pristine ISO booting.

The beauty, assuming I can get similar to work, is that this is done on a pristine boot of the ISO file

The difference from those instructions is that @jamesbond's boot menu stanza addition is to be added to the linux line.

Question: Should the 'blacklist' found in those instructions be used for v903?

Those unwilling to look at the link, I offer this summary substituting v903 parameters versus the Neon parms to start the PC using the nvidia driver upon desktop:

1. Boot Ventoy and launch v903

2. AT v903's GRUB2 menu, use the 'default' menu stanza "For problematic nvidia ..."

3. Hit tab-key to edit the stanza

4. ON the linux line, add "nvidia_drm.modeset=1" and "pfix=nox"

5. allow v903 to boot with these changes to console
   Here's where I am not sure if v903 has the same or similar utilities to use once at console

6. run "pkcon update" (??? for Fatdog package manager)

7. "ubuntu-drivers autoinstall" (??? for Fatdog package installation required?)

8. "modprobe nvidia" and "modprobe nvidia-drm"

Start the desktop as it will be using the nvidia driver. And, expect that by saving your session at shutdown/reboot, there will be no need to repeat these steps.

Before I venture off to screw things up, please share if you foresee this will work.

Question

• Does FATDOG have the same utitlities?

Help
My instructions dont work. Clues anyone? I suspect the console steps is the culprit as Fatdog may have alternates to allow desktop using an nvidia driver.
Or, maybe this is simpler than I am making it as much may already be present for this in Fatdog.

Any guidance is appreciated for "FATDOG steps" to pristine booting to desktop using the kernel nvidia drivers. Or any ideas for correcting these steps for successful setup.

Edit: For my 2 PCs, it was simpler that I thought. It appears that merely adding @jamesbond's addition to the boot stanza and nothing more is needed for a pristine boot directly to desktop with proper nvidia driver running.

I will attempt new, simple instructions with pics in a new thread for new FD users with nvidia cards. I know its only a simple step to do so when booting the ISO file from pristine, but, my idea is to remove any guesswork altogether and remove/reduce the need from members to guide users to activate their video adapter.

THANKS @jamesbond

In this pristine boot and use (no shutdown at this point) I am not getting audio via the TV's speakers. I have tried several approaches on this pristine desk via the Control Panel, but unable to change audio direction from the PC's internal speakers to the HDMI port via the nVidia adapter.

# qpwgraph 
pw_context_connect: Can't connect context.
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
pw_context_connect: Can't connect context.
pw_context_connect: Can't connect context.
pw_context_connect: Can't connect context.
pw_context_connect: Can't connect context.
pw_context_connect: Can't connect context.
pw_context_connect: Can't connect context.
^C
# echo "QPWGRAPH gui does not display"
QPWGRAPH gui does not display
# qpwgraph --version
qpwgraph 0.7.3
Qt: 5.15.8
libpipewire: 1.1.83 (headers: 1.1.83)
# 

Does this help diagnose the environment?

step wrote: ↑Sun Aug 25, 2024 1:35 pm

They should, as long as their executable mode is enabled (chmod a+x or rox right-click and select "Permissions").

You are right @step
Those files I put in /root/Startup directory were files from /usr/share/audio directory . When I put actually executable scripts , they do work .

Clarity wrote: ↑Wed Aug 28, 2024 6:35 am

xscreenshot-20240828T022931.pngxscreenshot-20240828T032001.png

@Clarity grep SAVEFILE_DEVICE /etc/BOOTSTATE

@Gobbi one way to play a sound when the Desktop has finished loading is to write a small file in your Startup folder and set it executable, for instance, file ~/Startup/bark, content rox /usr/share/audio/bark.au. I like to use rox, but you could use other commands instead, such as xdg-open, aplay, defaultmediaplayer, vlc, and more.

Thank you @step

Due to 2 things:

1. Pristine boot

2. Swap partition ignore on Pristine boot

This led to cache filling the available space and nowhere for relief.

Resolution

1. Exit desktop

2. turn on swap to use the swap partition

3. Restart desktop

And, of course, I did also empty caches once on desktop.

@Clarity, I'm glad you sorted it out. Thanks for letting us know.

The only thing I can find in v903 that I feel needs some help is; with today's world of peoples, we will see much as time advances with nvidia adapters as the main video adapter in both old and newer desktops.

Going forward, many/most desktop users will be users with large monitors and/or TVs connected to the desktops via HDMI. There is good reason(s) for this.

Problem
Audio is not be channelled thru the adapter along with video signalling. This leads to multiple efforts for user to figure out how and what tools are necessary to redirect audio to the TV.

Resolution
Have Pipewire channel the audio, as well, to the TV OOTB, initially, rather than the current other way around.

Reason
You want your user community to hit the ground running with audio-video with the decade-old HDMI use of today ...

This is universally adaptable to 'all' OOTB where HDMI/DP is used, no matter the adapter manufacturer.
Hope this is helpful

To help in understanding, I present the following from one of the test PCs I use for which there is no audio,OOTB

:

@Clarity, Fatdog64 has multiple sound servers. They are:
1. OSS (server-less)
2. ALSA (server-less)
3. Aloopd
4. JACK
5. PulseAudio
6. Pipewire

1,2,3,4 is built-in the base, and 5,6 are available in gslapt repo.

There are a few things that people should know about this.
1. Each sound server has different ways to specify the "default" soundcard
2. Not all of the sound servers work well with one another.
3. Not all of the apps in Fatdog are built to work with all of them.

So to answer your question of how to do the setup "OOTB" is really difficult, because your OOTB isn't always the same other people's OOTB (example, you want Pipewire to be included OOTB, but currently it is not).

For example:
1. The default soundcard for OSS can only be changed by editing kernel boot line or /etc/modprobe.d/alsa.conf, and you will have to restart for it to take effect.
2. The default soundcard for ALSA is set in /etc/asound.conf or $HOME/.asoundrc, but any changes requires the running app to be restarted
3. Aloopd does not have a default soundcard. You must tell it which output you want to use.
4. JACK's default soundcard can be specified on the command line, or, if you use qjackctl to start it, you can configure it on the GUI.
5. PulseAudio's default soundcard can be specified in it's configuration or changed using pacmd command.
6. Pipewire does not have default sink, you need to connect the graph to configure which output is used by which application.

fatdog-default-soundcard.sh takes some of the guesswork out of the equation when setting the "default soundcard", but it cannot handle all the possible permutations. Only the most common ones. It originally was meant only to configure ALSA (2), but now it has been extended to handle aloopd (3) and (to a much lesser extent) JACK (4) as well.

It does not handle PulseAudio as it has its own tool to manage so there is no point in replicating the functionality; same with Pipewire (which has qpwgraph).