Puppy Linux Discussion Forum

@hundido

the picture you have taken from the "First shutdown: choose partition" to create a pupsave shows your sdb2/vfat with 9 M - 1M free! So no wonder - that is far too low for a savefile, resulting in the paradox -82KB size of the savefile in the "Final Sanity Check".

Follow the advice from @williwaw : <parted<print all> and post the output.

(If you use Gparted you should select sdb in the entry screen, then click OK and post the output of the following screen.)

Which leads to the question - how did you create the booting usb-stick? Looks like you dd'ed the iso or used a program which does it?

@williwaw Thanks for the line code. Here's what happened:

# xrandr -q | grep connected
xrandr: Failed to get size of gamma for output default
default connected 1024x768+0+0 0mm x 0mm
# xrandr --output DFP1 --gamma 2.0:1.0:0.5
xrandr: Failed to get size of gamma for output default
warning: output DFP1 not found; ignoring
xrandr: Need crtc to set gamma on.
#

I'm currently using the Slacko stick. I don't really understand what crtc is or how to get it.

# parted 
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all                                                        
Model: ATA ADATA SU760 (scsi)
Disk /dev/sda: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1024GB  1024GB  primary


Model: SanDisk USB Flash Drive (scsi)
Disk /dev/sdb: 61.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      90.1kB  9527kB  9437kB  primary  fat16        esp


Model: Unknown (unknown)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  538MB   537MB   fat32        EFI System Partition  boot, esp
 2      538MB   1024GB  1024GB  ext4


Model: Unknown (unknown)
Disk /dev/nvme1n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1024GB  1024GB  primary


(parted) ^C                 

@one I used another computer with balena etcher on it to create a slacko usb and a fossapup usb.

When both my fossapup stick and slacko stick are in the computer, no matter which one I select in the boot menu, it boots into fossapup. Is that supposed to happen?

Here's the same things from the fossapup system:

root# xrandr -q | grep connected
xrandr: Failed to get size of gamma for output default
default connected 1024x768+0+0 0mm x 0mm
root# xrandr --output DFP1 --gamma 2.0:1.0.:0.5
xrandr: --gamma: invalid argument '2.0:1.0.:0.5'
Try 'xrandr --help' for more information.
root# xrandr --output DPF1 --gamma 2.0:1.0:0.5
xrandr: Failed to get size of gamma for output default
warning: output DPF1 not found; ignoring
xrandr: Need crtc to set gamma on.
root# ^C
root# 

and for parted, wtth both usb sticks plugged in:

root# parted
GNU Parted 3.3
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
Model: ATA ADATA SU760 (scsi)
Disk /dev/sda: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1024GB  1024GB  primary


Model: AI Mass Storage (scsi)
Disk /dev/sdb: 62.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      90.1kB  9527kB  9437kB  primary  fat16        esp


Model: SanDisk USB Flash Drive (scsi)
Disk /dev/sdc: 61.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      90.1kB  9527kB  9437kB  primary  fat16        esp


Model: SPCC M.2 PCIe SSD (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  538MB   537MB   fat32        EFI System Partition  boot, esp
 2      538MB   1024GB  1024GB  ext4


Model: T-CREATE TM8FPE001T (nvme)
Disk /dev/nvme1n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1024GB  1024GB  primary


(parted)  

Should I try to recreate one of the puppy usb sticks to see if I can get persistence? If so, what should I do differently this time?

hundido wrote: ↑Thu Jun 17, 2021 6:33 pm

When both my fossapup stick and slacko stick are in the computer, no matter which one I select in the boot menu, it boots into fossapup. Is that supposed to happen? No

Should I try to recreate one of the puppy usb sticks to see if I can get persistence? If so, what should I do differently this time?

would you consider trying to recreate a fossa install on the slacko stick? it would be a fresh install and will remove slacko. if so, boot into fossa. then insert the slacko stick and Identify it as sd? (a,b,c,d or e... etc). a, b, c... etc identifies the stick. ignore the following numbers such as sdb1 or 2, as these identify partitions on the stick (which will be repartitioned) you should see a new icon popup in the lower left of the screen shortly after inserting the slacko stick

What we want to make sure of, is to choose the correct usb stick when installing fossa using the installer in the fossa you have currently working without persistence. this will be much easier for all, than trying to troubleshoot an etcher install done from a different computer with a different OS.

Take a look at the fossa installer, and someone more familer with the installer will respond soon I think.

would you consider trying to recreate a fossa install on the slacko stick?

Yes, I think that's a great idea. Thank you.

Looking at the installer, and starting to read the help pages. What a many featured program! Should I start with Frugalpup, Bootflash, or Installer?

root# xrandr -q | grep connected
xrandr: Failed to get size of gamma for output default

xrandr is installed and working, but it is failing to see your asus eyecare monitor. without identifying it properly, there is no identifier to include in the second command to see if xrander can make an adjustment in gamma.

I remember reading that with most monitors, gamma can be adjusted, (which is supposedly possible in redshift), but the results were not as nice as being able to adjust the screen brightness at the hardware level.

perhaps a different approach, since the common backend tools, (sct and xrander) don't seem to be usable with the asus, is to google "asus + eyecare + linux" or some such to see what others have done to supplement the monitor controls with os tweaks.

Looking at the installer, and starting to read the help pages. What a many featured program! Should I start with Frugalpup, Bootflash, or Installer?

I do not use fossapup, so I will defer to others expertise, but if no one responds here in the beginner thread. you could ask in viewforum.php?f=146

an other alternative to using an installer is manually building a frugal install on your usb stick such as shown
viewtopic.php?f=155&t=2770

@hundido :-

What you DO need to do, in this instance, is to start a NEW thread.......specifically for the installation/save-file issue.

This is exactly what used to happen over at the old forum. A thread gets started on one subject; this is what appears on the index page. Halfway through, the thread then "morphs" into discussion of something completely unrelated.......and because the thread title still refers to the original subject matter, no 'fresh eyes' come to the table (unless they take an interest in the original subject).

Since this is Fossapup64 we're talking about, I would start a new thread in the Fossapup section. That way, you will get far more attention from those most familiar with installing/running/using the Puppy in question.

You will also find that there is a small "core" of members who tend to specialise in helping beginners with all these kinds of issues. Bigpup is most definitely foremost among these, AND he spends a fair bit of time in the Fossapup section, since he is a great believer in always using the very newest of everything.....the more so, given that this is a pretty up-to-date computer we're talking about.

Just my tuppence-worth. Nobody has an issue with someone starting lots of different threads; one subject, one thread makes it a LOT easier to stay 'on-topic', and everybody knows what's being discussed that way. We all of us have different areas of interest, and any given member will have different sections of the forum that they like to spend more time in than others.....

Okay?

Mike.

One thread/one topic makes sense. I started a new thread about the installation/save-file issue in fossapup. Is there anything I should do to clean up this thread a little?

hundido wrote: ↑Fri Jun 18, 2021 12:03 am

One thread/one topic makes sense. I started a new thread about the installation/save-file issue in fossapup. Is there anything I should do to clean up this thread a little?

Nah, it'll be fine if it returns to being 'on topic' with discussion about the screen brightness issue. That's what you started this thread for, after all; we, er, just got a wee bit "side-tracked" along the way..!

Happens ALL the time here.....

Mike.

Hey everyone in thread, I now have a Fossapup64 usb and a slacko64-8.2.1 usb, both with persistence! I found the settings in the forum under user control panel to change the forum to a dark theme. That helps a lot while I'm learning how to fix this.

@mikewalsh I downloaded v3 of redshift that you're mirroring and extracted the package. But I can not figure out how to get it to install. I click the redshift-portable-64-v3.tar.gz and it takes me back to an extract box, but never gives me the option to add the pet.

Update: After being confused and clicking on it a whole lot, I noticed several setting sun icons on the bottom of the screen. I clicked on one of them, and I was able to set my monitor to 2400k!!! Success! Thank you! Is there a way to instal redshift v3 in the menu?

@hundido :-

TBH, I'm not sure whether Fred gave specific instructions in the original thread, but what I always do is this:-

• Extract the .tar.gz package.

• Once you've extracted it, you should have a file called, simply, "rshift-portable-64".

• Place this file in /root/Startup.

That's all you need to do. Every time you boot, Rshift-portable will automatically start up & sit in the notification area over to the right; it's a 'self-extracting' file, which unpacks itself into, and runs from /tmp for the session. The first run, it creates its config directory in /root, called .rshift (it's a 'hidden file', denoted by the ".". You show it by clicking on ROX's 'eye' symbol at the top of the ROX window.)

One tip; if you set it to run automatically from the right-click menu, the geo-locate feature is not always that accurate. If you're concerned about it showing your correct location - this is so that the red tint automatically comes on at sunset, and off again at sunrise - it CAN be 'adjusted.

Go into /root/.rshift. Open the text file marked 'geo_info'. The line starting "loc" gives your location using standard-type decimal co-ordinates. You can find this info quite easily on-line.....there's tons of sites that will provide accurate info for geographical location. Modify it to read exactly the same way; the first number is the (N)orth - longitude - co-ordinate. you need it to 4 decimal places. Then a comma (",")followed immediately by the (E)ast - latitude - co-ordinate. Don't leave a space either side of the comma, otherwise it won't be parsed correctly.

Any probs, give us a shout. It's quite straight-forward, once you've done it a couple of times.

Mike.

@hundido
Redshift-portable should be included already in FossaPup (at least for me it is), Menu > Desktop > Redshift. If so, there's no need to install it.
It executes /usr/bin/redshift-portable-64 (to have it autostart, copy it to /root/Startup, as Mike said already).

EDIT: on Slacko it's not installed by default, so follow Mike's instructions.

Fred

Go into /root/.rshift. Open the text file marked 'geo_info'. The line starting "loc" gives your location using standard-type decimal co-ordinates. You can find this info quite easily on-line.....there's tons of sites that will provide accurate info for geographical location. Modify it to read exactly the same way; the first number is the (N)orth - longitude - co-ordinate. you need it to 4 decimal places. Then a comma (",")followed immediately by the (E)ast - latitude - co-ordinate. Don't leave a space either side of the comma, otherwise it won't be parsed correctly.

Mike,
redshift-portable-64 works good in EasyOs. /root/.rshift does not seem to have geo_info, only BR_value and cir_temp.

I did find /root/.config/redshift.conf line 27, location provider is set to "manual"
one can set the lat long further down in lines 40 and 41

thanks for hosting the portable

Redshift is installed in Fossapup64, but it's not working on my computer.
What if I removed the installed redshift from Fossapup64, and then tried mikewalsh's instructions for portable redshift in Fossapup64? How do I remove the built in redshift?

Thank you for teaching me how to install portable redshift @mikewalsh , it's working really well in Slacko64-8.2.1.

I tried a bunch of other Puppies. 32s, 64s. I'm using Fred's portable Redshifts. Redshift won't work on my computer on any of them except Slacko64-8.2.1. Not working on Slacko64-7.0

I still can't figure this out, but it seems like an important data point.

I updated the title of the thread to reflect this discovery.

@hundido :-

Try one thing for me, would you? In Fossapup64, open a terminal, type

which redshift

.....and post the output for us, please? With the default redshift AND the 'portable', there ought to be more than one result returned.....though I'm not certain if the one in /tmp will show up with this command.

I've been looking through the Fossapup ISO, to find out what is in the main SFS. I can find 'redshiftgui.sh' in /usr/bin, but I can't find the redshift binary, and some of the locations in the shell script don't seem to exist. I can't help wondering if Phil 'borrowed' this whole thing from an older Puppy, because with Fossa he's returned to using bog-standard 'paths' for everything, rather than some of the previous Puppy 'fudges'.

I'm just curious what the "which" command will return for redshift...

Mike.

FossaPup64 has the executables /usr/bin/redshiftgui.sh and /usr/bin/redshift-portable-64 (in the adrv.sfs)

redshiftgui.sh does nothing, redshiftgui does not exist. Only redshift-portable-64 works.

redshift-portable-64 is a shell script that unzips the redshift files to a dir in /tmp/ which uses space (400k) in ram.
redshiftgui.sh and redshiftgui would not do that (unzip to ram.)

To run redshift, start redshift-portable-64 from the menu or from a terminal (console.)
An icon should appear in the jwm tray, bottom right of the screen.
Right click the redhshift icon in the tray and turn on "Auto mode"
It should just work, automatically getting your location.

It might not start automatically next time you boot.

@williams2 :-

Ah. That explains it. I never thought about investigating the contents of the adrv. Shows how observant I am.

Do I take it this is Fred's 'redshift-portable'? 'Cos it sounds like it works exactly the same; a self-extracting script, that unzips itself into /tmp....

Mike.

hundido wrote: ↑Fri Jul 23, 2021 5:23 am

I'm using Fred's portable Redshifts. Redshift won't work on my computer on any of them except Slacko64-8.2.1. Not working on Slacko64-7.0

wont work how? after it is installed, does it.....

1. show an icon in the lower right menu bar? if so,
2.does clicking on it bring up two sliders, if so,
3. do both sliders work? what specifically does not work?

Hey community,

I ended up making a USB with Fossapup64, Slacko7, and Slacko64-8.2.1. So new install of Fossapup.

@mikewalsh
On the fresh install with the redshift included in the install:

root# which redshift
root#

Once I left click the gui, which lets me toggle the bars but does nothing to the actual screen, I clicked Stop Redshift. I clicked Exit.
I tried

which redshift

again with no result.

Upon accessing portable redshift now stored on sda2:
I get the same icon in the lower left corner, where sliding the sliders does nothing.
with it open, I try:

which redshift

and again get no output.

@williams2 Thank you for your explanation. I tried clicking auto mode, which I hadn't done before because I need it always on. I then tried sliding the Redshift Day Color Temp Setting to 3172 with no effect on the display.

@williwaw
Slacko64-8.2.1: Works. Portable redshift brings up slider. It is permanently set to 2400.

Fossapup64: Both installed and portable redshift bring up icon. Icon brings up sliders. Sliding sliders does nothing to the color temp.

Slacko64-7.0: Portable Redshift brings up icon in tray. Clicking icon brings up slider. Slider has no effect on color temp.

hundido wrote:

On the fresh install with the redshift included in the install:

Code: Select all

root# which redshift
root#

The redshift binary is included in the "portable", but it's not existing in the PATH environment (e.g. /usr/bin), so that explains why "which redshift" doesn't give any output.

@fredx181 :-

Mm-hm. Yep. It sits in /tmp ONLY while it runs, so.....as you say, it ain't "in the $PATH".

Like I stated earlier, I hadn't realised Phil was using your 'portable', Fred. I've been using the 'standalone' version running from /root/Startup in Fossapup, right from day one..... I'd kind of assumed this was the official, 'standard' version, y'know?

Mike.

when run from a terminal in a os where rshift works, I am informed it it using "randr"

# ./rshift*
Verifying archive integrity... All good.
Uncompressing rshift-portable  100%  
redshift 1.11
Using method `randr'.

You could see if any error returns in fossa or in any other pup that it fails in.
You might also learn something when run in the slacko821 where it works.

right click on icon if redshift is running and exit
Go to the directory it was installed to with rox, right click > window > terminal here
run directly at the prompt with # ./rshift*

I lot of talk here is above my comprehension. I'm sure it I'll reread this stuff a few times as I learn what it means.

Copy/paste doesn't work in the terminal in Slacko64-8.2.1.
Trying to copy/paste with the mouse button highlights it but does nothing. Clicking the buttons did nothing, except eventually creating a copy of the string

~/Downloads$

that then made even the selection of the text look funny.

Clicking Ctrl+c made the characters

^c

and did not copy the text.

Opening the window from downloads, where I click redshift to start it, and typing

# ./redshift*

and nothing happened.

I clicked exit on the icon before doing that, which closed the icon, but the redshift is still on, which is nice. Did I do that correctly?

I'll reboot and try typing

# ./redshift*

in Fossapup64.

mikewalsh wrote: ↑Sat Jul 24, 2021 10:34 pm

@fredx181 :-

Mm-hm. Yep. It sits in /tmp ONLY while it runs, so.....as you say, it ain't "in the $PATH".

Like I stated earlier, I hadn't realised Phil was using your 'portable', Fred. I've been using the 'standalone' version running from /root/Startup in Fossapup, right from day one..... I'd kind of assumed this was the official, 'standard' version, y'know?

Mike.

Hi Mike, I see no difference between 'standalone' and 'portable', AFAIK I shared in the old forum only "rshift-portable-64" self-extracting script.
The one included in FossaPup64 (in /usr/bin) is exactly the same, but Phil has renamed it to "redshift-portable-64".

@hundido
First stop redshift from the icon right-click menu "Stop Redshift", then "Exit" from the icon right-click menu.
And run from terminal: /usr/bin/redshift-portable-64, the icon should appear again, try to adjust the sliders and/or do something else (e.g. set to "Auto") and post the output.
From this output we can possibly see what can be wrong.

Fred

@fredx181 In Slacko64-8.2.1, I typed

~$ /usr/bin/redshift-portable-64

about three times and keep seeing

bash: /usr/bin/redshift-portable-64: No such file or directory

I'll go back and do this in Fossapup64 and see what happens

hundido wrote:

about three times and keep seeing

Code: Select all

bash: /usr/bin/redshift-portable-64: No such file or directory

Yes, /usr/bin/redshift-portable-64 exists only in FossaPup, in Slacko you need to run the one you (probably) downloaded earlier (rshift-portable-64).

if redshift is running, I have to right click the icon, then "stop redshift", then right click again and "exit" to kill the icon.

in the terminal opened in the folder where redshift portable lives, run ./rshift* it should start redshift with a few lines of feedback

then, when I right click on the icon and "stop redshift" a line is added to the terminal output, in my case "using method 'randr'", yours might return "using method '????'"

redshift is a bit sparse on output, and not all programs are as verbose as others, but generally if you can run a command in the terminal, any output can help troubleshoot.

oops, cross posting with fred

@williwaw Typed

# ./rshift*

in fossapup64. Nothing happens. It just says

root#

again

@fredx181 I just booted into Fossapup64 and never started redshift to have to stop it.
started a terminal. Typed the code:

root# /usr/bin/redshift-portable-64
Verifying archive integrity... All good.
Uncompressing rshift-portable  100%  
redshift 1.11
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
^CSignal caught, cleaning up

@fredx181 Tried it again and reopened it moving slider this time:

root# /usr/bin/redshift-portable-64
Verifying archive integrity... All good.
Uncompressing rshift-portable  100%  
redshift 1.11
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
EXIT="Exit on click close-box"
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
^CSignal caught, cleaning up
root#