Slacko Puppy 5.3.1
I just updated my frugal slacko 5.3 install to slacko 5.3.1.
The update went fine and the reboot caused no problems.
But...
I then figured I would try booting with pfix=ram and creating a encrypted save file.
What I saw that was different was that I saw the word Pausing a number of times, before it was once, and it loaded my existing pupsave file.
That is not supposed to happen when booting with a pfix=ram parameter.
I renamed my existing pupsave file so it would not be picked up and tried again with pfix=ram.
This time, it loaded like a fresh boot with no pupsave.
I set up, selected reboot, and chose to make a encrypted pupsave in my subdirectory.
I got a message that the file was being created, but no message that my settings were being saved.
Also, on rebooting, no encrypted pupsave file existed.
This is a major problem and needs verification of both not using an existing pupsave when the pfix=ram parameter is given and also the problem of a encrypted pupsave file not being created when chosen.
I do not know how much was changed with this update, but I am going back to the original slacko 5.3 main.
The update went fine and the reboot caused no problems.
But...
I then figured I would try booting with pfix=ram and creating a encrypted save file.
What I saw that was different was that I saw the word Pausing a number of times, before it was once, and it loaded my existing pupsave file.
That is not supposed to happen when booting with a pfix=ram parameter.
I renamed my existing pupsave file so it would not be picked up and tried again with pfix=ram.
This time, it loaded like a fresh boot with no pupsave.
I set up, selected reboot, and chose to make a encrypted pupsave in my subdirectory.
I got a message that the file was being created, but no message that my settings were being saved.
Also, on rebooting, no encrypted pupsave file existed.
This is a major problem and needs verification of both not using an existing pupsave when the pfix=ram parameter is given and also the problem of a encrypted pupsave file not being created when chosen.
I do not know how much was changed with this update, but I am going back to the original slacko 5.3 main.
gerry, this is direct from slackware http://slackware.cs.utah.edu/pub/slackw ... i486-2.txzgerry wrote:Thinkpad T60p. I can only get one video resolution, 1680x1050. This is because this computer is using the radeon driver, but actually needs radeonhd (as far as I can find out). Any one know where to get it?
Let me know if it works
Puppy Linux Blog - contact me for access
The proper command is puppy pfix=ramThis is a major problem and needs verification of both not using an existing pupsave when the pfix=ram parameter is given
By chance the problem?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
What resolution do you want?gerry wrote:Thinkpad T60p. I can only get one video resolution, 1680x1050. This is because this computer is using the radeon driver, but actually needs radeonhd (as far as I can find out). Any one know where to get it?
How are you trying to change it?
Could you run this command in the console and post its output.
xrandr
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
bigpup,
The case where you do not use puppy with the parameter is in a temporary edit of the menu.lst entry of the kernel line.
I realize that puppy pfix=ram should be used when booting from CD.
When I reverted to the original puppy_slack_5.3.sfs file and added the patch to it using SFSedit, and rebooted, all was right with the world and I could make a encrypted pupsave file with my settings saved.
As a matter of fact, that encrypted file is in use as I type this.
If you have the time and inclination, try my test for yourself.
The case where you do not use puppy with the parameter is in a temporary edit of the menu.lst entry of the kernel line.
I realize that puppy pfix=ram should be used when booting from CD.
When I reverted to the original puppy_slack_5.3.sfs file and added the patch to it using SFSedit, and rebooted, all was right with the world and I could make a encrypted pupsave file with my settings saved.
As a matter of fact, that encrypted file is in use as I type this.
If you have the time and inclination, try my test for yourself.
I don't know how to post the result.
But to answer your questions:
Present resolution is 1680x1050
Range is from 1680x1050 down to 640x480
I'm trying to change it using xorgwizard. How else to do it. Never occurred to me that xorgwizard wouldn't do it. I'll have a look at xorg.conf.
I'd like to try 1280x800
But to answer your questions:
Present resolution is 1680x1050
Range is from 1680x1050 down to 640x480
I'm trying to change it using xorgwizard. How else to do it. Never occurred to me that xorgwizard wouldn't do it. I'll have a look at xorg.conf.
I'd like to try 1280x800
8-bit
I gather you did a cheat frugal? Did you swap the initrd.gz too? I can not reproduce your problem. I have no problem with heavy or light encryption on 3 machines.
I gather you did a cheat frugal? Did you swap the initrd.gz too? I can not reproduce your problem. I have no problem with heavy or light encryption on 3 machines.
Puppy Linux Blog - contact me for access
01micko,
I did swap out both the initrd.gz and the slacko SFS file before booting.
But I will try it again without a pupsave in a fresh directory to make sure that the existing pupsave did not mess things up.
Edited:
It must have been the slacosave file that I already had that messed things up.
I created a new frugal install and this time, everything worked.
So I would call it a false alarm.
Sorry if I alarmed anyone.
I did swap out both the initrd.gz and the slacko SFS file before booting.
But I will try it again without a pupsave in a fresh directory to make sure that the existing pupsave did not mess things up.
Edited:
It must have been the slacosave file that I already had that messed things up.
I created a new frugal install and this time, everything worked.
So I would call it a false alarm.
Sorry if I alarmed anyone.
Slacko Puppy 5.3
I did a manual frugal install of the 5.3.0.2 iso to my acer laptop.
I copied my 5.3.0.2 save file from my emachines laptop to the directory.
I used SNS to set up the wireless network connection.
Thu 17 Nov 2011 Operating System: Slacko Puppy-5.3.0.2 Linux 2.6.39.4
0.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series]
oem: ATI ATOMBIOS product: PARK 01.00
X Server: Xorg Driver: radeon
X.Org version: 1.9.5
dimensions: 1600x900 pixels (423x238 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.10.2
Intel(R) Core(TM) i5 CPU M 430
Core 0: 1199 1: 1199 2: 1199 3: 1199 MHz
# glxgears
2559 frames in 5.0 seconds = 511.772 FPS
2526 frames in 5.0 seconds = 505.118 FPS
2601 frames in 5.0 seconds = 520.079 FPS
Ethernet controller Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe
Network controller Atheros Communications Inc. AR928X Wireless Network Adapter
It's working well.
I copied my 5.3.0.2 save file from my emachines laptop to the directory.
I used SNS to set up the wireless network connection.
Thu 17 Nov 2011 Operating System: Slacko Puppy-5.3.0.2 Linux 2.6.39.4
0.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series]
oem: ATI ATOMBIOS product: PARK 01.00
X Server: Xorg Driver: radeon
X.Org version: 1.9.5
dimensions: 1600x900 pixels (423x238 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.10.2
Intel(R) Core(TM) i5 CPU M 430
Core 0: 1199 1: 1199 2: 1199 3: 1199 MHz
# glxgears
2559 frames in 5.0 seconds = 511.772 FPS
2526 frames in 5.0 seconds = 505.118 FPS
2601 frames in 5.0 seconds = 520.079 FPS
Ethernet controller Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe
Network controller Atheros Communications Inc. AR928X Wireless Network Adapter
It's working well.
- Attachments
-
- slackoscrn.jpg
- (121.78 KiB) Downloaded 1198 times
Delta patch 5.3.0.1 applied to 5.3Main then installed a frugal manually to ext4 pfix=ram on Pentium M Dell latitude D610.
mesa downloaded from slickpet. gears shows jerking halting even in small size window. although, it will play a movie. phony gz on report.
--------
after couple reboots gears is not as jerky. pic is small then expanded full screen.
mesa downloaded from slickpet. gears shows jerking halting even in small size window. although, it will play a movie. phony gz on report.
--------
after couple reboots gears is not as jerky. pic is small then expanded full screen.
- Attachments
-
- gears.png
- (11.93 KiB) Downloaded 374 times
-
- hardinfo_report.html.gz
- (58.08 KiB) Downloaded 250 times
Ok, so this is basically sorted, but I did have a minor glitch myself, rather annoying. I upgraded a frugal on sda6. All went fine but on reboot I got the "PAUSING" messages then a list of all the slackosaves on sda6! (About 10 in my case). That's not supposed to happen. The work-around was to add pdev1=sda6 on the kernel line.8-bit wrote:I just updated my frugal slacko 5.3 install to slacko 5.3.1.
The update went fine and the reboot caused no problems.
But...
I then figured I would try booting with pfix=ram and creating a encrypted save file.
What I saw that was different was that I saw the word Pausing a number of times, before it was once, and it loaded my existing pupsave file.
That is not supposed to happen when booting with a pfix=ram parameter.
I renamed my existing pupsave file so it would not be picked up and tried again with pfix=ram.
This time, it loaded like a fresh boot with no pupsave.
I set up, selected reboot, and chose to make a encrypted pupsave in my subdirectory.
I got a message that the file was being created, but no message that my settings were being saved.
Also, on rebooting, no encrypted pupsave file existed.
This is a major problem and needs verification of both not using an existing pupsave when the pfix=ram parameter is given and also the problem of a encrypted pupsave file not being created when chosen.
I do not know how much was changed with this update, but I am going back to the original slacko 5.3 main.
The reason it happens is that in the upgrade something gets lost in the translation, somewhere. The evidence of this is in /etc/rc.d/PUPSTATE.
The PDEV1 variable is empty..
Code: Select all
PDEV1=''
Code: Select all
PDEV1='sda6'
Manually inserting the PDEV var does not work.(as I didn't think it would, the problem occurs earlier and the value is the result)
Intriguing.
Puppy Linux Blog - contact me for access
I also missed grub4dos-config update (1.7.1), will be in.
Also, the update of the internet connection wizard with the hostname box was missed, fixed.
We need some packages folks. I am onto openshot and samba (hopefully, with gcmartin's help)
Openshot 1.4 does run from the slacky repo, misses deps though, notably python, ..plus anything with a .csh extension in /etc/profile.d needs deleting, fix will be to pet up openshot and remove those in the pinstall.sh..edit, better idea, I'll patch petget to remove them.. rm -f /etc/profile.d/*.csh
We probably need some updated music apps, maybe aqualung, deadbeef , .. some one want to package blender? Anyone try gtk-recordmydesktop?.. it's in Slacky repo, needs python, which often isn't listed as a dep as it's in the devx, but probably needs python modules too, such as py-gtk, py-cairo etc, when you run it and get errors check them, they are useful
Anyone? (how can you resist that smiley eh?)
Shooting for 5.3.1 on Sunday/Monday
Also, the update of the internet connection wizard with the hostname box was missed, fixed.
We need some packages folks. I am onto openshot and samba (hopefully, with gcmartin's help)
Openshot 1.4 does run from the slacky repo, misses deps though, notably python, ..plus anything with a .csh extension in /etc/profile.d needs deleting, fix will be to pet up openshot and remove those in the pinstall.sh..edit, better idea, I'll patch petget to remove them.. rm -f /etc/profile.d/*.csh
We probably need some updated music apps, maybe aqualung, deadbeef , .. some one want to package blender? Anyone try gtk-recordmydesktop?.. it's in Slacky repo, needs python, which often isn't listed as a dep as it's in the devx, but probably needs python modules too, such as py-gtk, py-cairo etc, when you run it and get errors check them, they are useful
Anyone? (how can you resist that smiley eh?)
Shooting for 5.3.1 on Sunday/Monday
Puppy Linux Blog - contact me for access
I figured you knew what you were doing, but not knowing how you booted, I would mention the obvious. It is never the easy answer!8-bit wrote:bigpup,
The case where you do not use puppy with the parameter is in a temporary edit of the menu.lst entry of the kernel line.
I realize that puppy pfix=ram should be used when booting from CD.
I have seen times when install programs seem to be seeing old deleted files and using them. Or, somehow the old deleted files cause corruption of a similar named file when installing. Deleting a file only deletes the name, but the data is still there, just not identified. The data should be able to be written over. Key word should.
I also remember a story I read, of an interview, with one of the people who are credited with inventing the modern computer.
They asked, "Why have a reset switch?"
The answer, "That was the easy fix when the thing looked up all the time".
Last edited by bigpup on Fri 18 Nov 2011, 19:22, edited 3 times in total.
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
Here's an improved screenshot taking GUI.
This one shows a progress bar and works with either rgbPaint, mtPaint or scrot.
This one shows a progress bar and works with either rgbPaint, mtPaint or scrot.
Code: Select all
#!/bin/sh
# the base arguments for Yad
YAD_BASE_ARGS="--title=Screenshot --window-icon=/usr/local/lib/X11/pixmaps/x24.png --image=/usr/local/lib/X11/pixmaps/x24.png"
# the maximum time to wait before the screenshot is taken
MAX_PAUSE=120
# the default time to wait before the screenshot is taken
DEFAULT_PAUSE=10
# the minimum number of seconds to wait that requires a progress bar
MIN_BAR_SECONDS=5
# let the user choose the number of seconds to wait before the screenshot is taken
seconds="$(yad $YAD_BASE_ARGS --scale --value=$DEFAULT_PAUSE --max-value=$MAX_PAUSE --mark='10 seconds:10' --mark='30 seconds:30' --mark='1 minute:60' --mark='2 minutes:120' --text='Choose the number of seconds to wait before the screenshot is taken.')"
[ $? -ne 0 ] && exit 0
# pause for the chosen interval
if [ $MIN_BAR_SECONDS -le $seconds ]
then
(for i in `seq $seconds`
do
echo "$i * 100 / $seconds" | bc
sleep 1
done) | yad $YAD_BASE_ARGS --text="Pausing for $seconds seconds ... " --progress --auto-close
else
sleep $seconds
fi
# check whether mtPaint or rgbPaint is present
for i in mtpaint rgbpaint
do
if [ -n "$(which $i)" ]
then
$i -s &
exit 0
fi
done
# otherwise, try scrot
if [ -n "$(which scrot)" ]
then
file="$(mktemp -u).png"
scrot -q 100 $file
defaultimageeditor $file
rm -f $file
exit 0
else
yad $YAD_BASE_ARGS --button=gtk-ok:0 --text="Error: could not capture the screen; install either mtPaint, rgbPaint or scrot."
fi
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
what bothers me is that this pop up that usually happens to sites that has ssl
i guess its about the dates.how can i let it not pop out?
i guess its about the dates.how can i let it not pop out?
- Attachments
-
- paypal.png
- (22.88 KiB) Downloaded 408 times
This is one solution.enhu wrote:what bothers me is that this pop up that usually happens to sites that has ssl
i guess its about the dates.how can i let it not pop out?
In your picture it does say current time is 06/01/2004 05:24 AM.Dave, just so you know, I've figured out my problem with the expired or not yet valid security certificates: the date on my computer was set wrong and it thought I was years in the past! Once I fixed the date and time, all of these problems vanished.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)