slacko 5.3.3, final
In looking over some of this thread's messages and the latest version, it appears that FirstRUN has changed.
Could any of what's occurring be related in any way to the FirstRUN changes? I only say this because for me, it seems to be the one single change in SLACKO from 5.3.1. Excepting for some of the under-the-cover items in shutdown processing, maybe the system's start (FirstRUN) contributes to ending issues...maybe also "totally unrelated". Please remember I am only looking at the system from an external view of subsystem operations...not the internals.
Just thoughts
Could any of what's occurring be related in any way to the FirstRUN changes? I only say this because for me, it seems to be the one single change in SLACKO from 5.3.1. Excepting for some of the under-the-cover items in shutdown processing, maybe the system's start (FirstRUN) contributes to ending issues...maybe also "totally unrelated". Please remember I am only looking at the system from an external view of subsystem operations...not the internals.
Just thoughts
woops!rhadon wrote:That's hard to believe, see attachment.The thing is, Barry, and therefore the puppy scripts don't know about the new feature.![]()
![Embarassed :oops:](./images/smilies/icon_redface.gif)
EDIT: so I tested:
saving encrpted to 2fs is fine
3fs is broken from gui AND console
![Confused :?](./images/smilies/icon_confused.gif)
Code: Select all
/usr/sbin/shutdownconfig: line 235: 15771 Terminated yaf-splash -bg orange -close never -fontsize large -text "$T_waitprobing"
sda13,ext3,/slacko5.3.2.6/slackosave.2fs
131072+0 records in
131072+0 records out
134217728 bytes (134 MB) copied, 0.350947 s, 382 MB/s
/usr/bin/pupdialog: line 259: 19937 Terminated /tmp/pupdialog_exec --center --class="module16" --program=PUP${$}DLG > /tmp/pupdialog_retvals${$}
/usr/bin/pupdialog: line 266: TAGPREFIXFIX_: command not found
![Confused :?](./images/smilies/icon_confused.gif)
![Confused :?](./images/smilies/icon_confused.gif)
![Confused :?](./images/smilies/icon_confused.gif)
Puppy Linux Blog - contact me for access
Very strange.01micko wrote:3fs is broken from gui AND console with a similar error from GUI as with the ntfs issue:
![Shocked :shock:](./images/smilies/icon_eek.gif)
Running e2fsck, I get
Code: Select all
# e2fsck slackosave_cryptx.3fs
e2fsck 1.41.14 (22-Dec-2010)
slackosave_cryptx.3fs has unsupported feature(s): compression FEATURE_I5 FEATURE_I12 FEATURE_I13 FEATURE_I16 FEATURE_I17 FEATURE_I20 FEATURE_I21 FEATURE_I26 FEATURE_I28 FEATURE_I29 FEATURE_R2
e2fsck: Get a newer version of e2fsck!
Code: Select all
# e2fsck slackosave_crypta.3fs
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open slackosave_crypta.3fs
The superblock could not be read or does not describe a correct ext2
filesystem....
![Wink :wink:](./images/smilies/icon_wink.gif)
Cheers
Rolf
Ich verwende "frugal", und das ist gut so. :wink:
Raspberry Pi without Puppy? No, thanks.
Raspberry Pi without Puppy? No, thanks.
Peter,peebee wrote: have just tried to make a new system with a new savefile and after the reboot I get no background and no icons - see attached.
Very strange.
Cheers
Peter
try it again, with creating the savefile after first reboot and see if it is ok then.
Mick,
I have had the same problem as peter with your latest pae, if creating the savefile after a frugal install, but before reboot, no icons or background, however it was ok if I created the savefile after, ie using the frugal system to create the savefile and not the cd's system.
However, if I created the savefile before rebooting and rebooted, leaving the cd in, so it started up on the cd again it was ok.
Have no idea why, and it's with the pae only, using the 'straight' build it doesn't happen!
scsijon
and this is my 'new' acer with intel video.
Puppy Linux Blog - contact me for access
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Did a pristine boot from 5.3.2.6 (supports up to 4G RAM) version
- had to try it
Everything set up fine
Added one piece of software - the mesa driver from slickpet
rebooted x and got black screen of death
I rebooted back into Saluki as I was in the middle of something
Does that mean the mesa driver has to be compiled for the specific kernel?![Confused :?](./images/smilies/icon_confused.gif)
- had to try it
![Smile :)](./images/smilies/icon_smile.gif)
Everything set up fine
![Cool 8)](./images/smilies/icon_cool.gif)
Added one piece of software - the mesa driver from slickpet
rebooted x and got black screen of death
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
I rebooted back into Saluki as I was in the middle of something
Does that mean the mesa driver has to be compiled for the specific kernel?
![Confused :?](./images/smilies/icon_confused.gif)
Ati/Amd radeon Lob?
Yeah i switched on modesetting for KMS, it was actually to test a bugfix for woof. I'll switch it off for next time.
Boot pfix=nox (either edit menu.lst on the fly with the "e" button or at the prompt if booting off CD.)
When pup is booted he leaves you at the dreary command prompt.
Type:
Should be ok then.
Yeah i switched on modesetting for KMS, it was actually to test a bugfix for woof. I'll switch it off for next time.
Boot pfix=nox (either edit menu.lst on the fly with the "e" button or at the prompt if booting off CD.)
When pup is booted he leaves you at the dreary command prompt.
Type:
Code: Select all
echo "options radeon modeset=0" > /etc/modules.d/radeon.conf
reboot
Puppy Linux Blog - contact me for access
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Yep01micko wrote:Ati/Amd radeon Lob?
Yeah i switched on modesetting for KMS, it was actually to test a bugfix for woof. I'll switch it off for next time.
this is the radeon details
![Smile :)](./images/smilies/icon_smile.gif)
Code: Select all
Chip description:
0.0 VGA compatible controller
ATI Technologies Inc RV710 [Radeon HD 4350]
oem: ATI ATOMBIOS
product: RV710 01.00
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Tried 5.3.2.6 and if I input the 3 drop-down settings for London UK on that initial welcome set-up thing and click "OK" the video just freaks out and I have to force shut-down.
Country = en Great Britain
Time Zone = Europe/London or GMT +0 (London/Dublin...)
Keyboard = en UK
Seems to be a combination of the three on that window. If I accept other wrong settings (such as the ones that are there when it opens) and then select the correct ones later from menu options I can get everything as it should be.
Same thing happened when I tried Racy 5.2.2.8 yesterday though I didn't persist for quite so long.
Happened the same on 2 different (older I must admit) desktops.
Country = en Great Britain
Time Zone = Europe/London or GMT +0 (London/Dublin...)
Keyboard = en UK
Seems to be a combination of the three on that window. If I accept other wrong settings (such as the ones that are there when it opens) and then select the correct ones later from menu options I can get everything as it should be.
Same thing happened when I tried Racy 5.2.2.8 yesterday though I didn't persist for quite so long.
Happened the same on 2 different (older I must admit) desktops.
I 'm out of luck with this .iso I downloaded from the link
in the first page I boot with pfix=ram on a Acer D255
which seems to be a 64bit cpu? Slacko 5324 work good
I use it now to write this. 5326 totally fail to boot.
It says a lot of things in RED color.
like this: /lib/keymap/pu*.gz No such file or directory
It also report: puppy_slacko_5.3.2.6.sfs not found
and it says: input:AT Translated Set 2 keymap as /xxxxx and so on
I don't get a word of that and I hastely tried to write it from screen
Edit another thing seems to be that even on Slacko 5324 /mnt/home/ is on this place
/initrd/mnt/dev_save/
I boot with grub4dos on NTFS using this menu.lst
title Slacko5326 1024x768 JWM. nolapic rootnoverify (hd0,1)
rootnoverify (hd0,1)
kernel /slacko5326/vmlinuz pmedia=hdscsi psubdir=slacko5326 puppy i915.modeset=1 pfix=fsck
initrd /slacko5326/initrd.gz
title Slacko-5324 B5 1024x768 JWM. nolapic rootnoverify (hd0,1)
find --set-root --ignore-floppies --ignore-cd /slacko5324/initrd.gz
kernel /slacko5324/vmlinuz psubdir=slacko5324 puppy i915.modeset=1 pfix=fsck
initrd /slacko5324/initrd.gz
I've tested both versions of rootnoverify (hd0,1)
find --set-root --ignore-floppies --ignore-cd /slacko5324/initrd.gz
Does that mean I ahve done something very wrong?
I don't remember that Lucid behave like that?
___
So if I get it this is the latest version of Slacko and the one that will become the official Puppy when some bugs is ironed out?
in the first page I boot with pfix=ram on a Acer D255
which seems to be a 64bit cpu? Slacko 5324 work good
I use it now to write this. 5326 totally fail to boot.
It says a lot of things in RED color.
like this: /lib/keymap/pu*.gz No such file or directory
It also report: puppy_slacko_5.3.2.6.sfs not found
and it says: input:AT Translated Set 2 keymap as /xxxxx and so on
I don't get a word of that and I hastely tried to write it from screen
Edit another thing seems to be that even on Slacko 5324 /mnt/home/ is on this place
/initrd/mnt/dev_save/
I boot with grub4dos on NTFS using this menu.lst
title Slacko5326 1024x768 JWM. nolapic rootnoverify (hd0,1)
rootnoverify (hd0,1)
kernel /slacko5326/vmlinuz pmedia=hdscsi psubdir=slacko5326 puppy i915.modeset=1 pfix=fsck
initrd /slacko5326/initrd.gz
title Slacko-5324 B5 1024x768 JWM. nolapic rootnoverify (hd0,1)
find --set-root --ignore-floppies --ignore-cd /slacko5324/initrd.gz
kernel /slacko5324/vmlinuz psubdir=slacko5324 puppy i915.modeset=1 pfix=fsck
initrd /slacko5324/initrd.gz
I've tested both versions of rootnoverify (hd0,1)
find --set-root --ignore-floppies --ignore-cd /slacko5324/initrd.gz
Does that mean I ahve done something very wrong?
I don't remember that Lucid behave like that?
___
So if I get it this is the latest version of Slacko and the one that will become the official Puppy when some bugs is ironed out?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Another problem with 5324 hope it is okay I take it up here
I don't trust it is solved in 5326 so it can be relevant.
When I do SFS-Load then it gives this report see screen cap attached.
Do you want to move xxxx from /mnt/home to /initrd/mnt/dev_save/
Thanks BigPup I am willing to try anything you recommend![Smile :)](./images/smilies/icon_smile.gif)
I don't trust it is solved in 5326 so it can be relevant.
When I do SFS-Load then it gives this report see screen cap attached.
Do you want to move xxxx from /mnt/home to /initrd/mnt/dev_save/
Thanks BigPup I am willing to try anything you recommend
![Smile :)](./images/smilies/icon_smile.gif)
- Attachments
-
- sfs-load-fails.jpg
- Says I am in the wrong place
- (38.96 KiB) Downloaded 515 times
Last edited by nooby on Tue 28 Feb 2012, 18:37, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Nooby,
That Grub4dos menu.lst entry for 5326 does not look like a good entry for Grub4dos. It looks like one used by Grub.
Look at the difference, in the entry below it, that works for 5324.
If you run "Grub4dos bootloader config", it should give you a working entry. May still need to add the puppy i915.modeset=1 pfix=fsck to the kernel line.
That Grub4dos menu.lst entry for 5326 does not look like a good entry for Grub4dos. It looks like one used by Grub.
Look at the difference, in the entry below it, that works for 5324.
If you run "Grub4dos bootloader config", it should give you a working entry. May still need to add the puppy i915.modeset=1 pfix=fsck to the kernel line.
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![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
If you run "Grub4dos bootloader config"
That would destroy all the working entries I already have now.
So that may work on slacko but destroy al lthe Ubuntu special
versions I do have.
How can I test it without getting things messed up? Make a backuup of menulist but a bad things about that program is that it wants to
add a mbr too and I already have such most likely?
So that would not be good at all. Any less damaging suggestion?
It could work if I install on a usb flash or something? Not on the hard drive.
That way it would search all drives and add what it see as proper code for all OS
The easiest would be to ask somebody that already have done the thing you suggest
They would already know ![Smile :)](./images/smilies/icon_smile.gif)
ICPUG who cares a lot about frugal install if I get him he suggest
this for slacko531
title Slacko Puppy Linux 5.3.1
kernel (hd1,0)/slacko531/vmlinuz PMEDIA=idehd PDEV1=sdb1 psubdir=slacko531
initrd (hd1,0)/slacko531/initrd.gz
so I will test that one and see if something differs I get back
That would destroy all the working entries I already have now.
So that may work on slacko but destroy al lthe Ubuntu special
versions I do have.
How can I test it without getting things messed up? Make a backuup of menulist but a bad things about that program is that it wants to
add a mbr too and I already have such most likely?
So that would not be good at all. Any less damaging suggestion?
It could work if I install on a usb flash or something? Not on the hard drive.
That way it would search all drives and add what it see as proper code for all OS
The easiest would be to ask somebody that already have done the thing you suggest
![Smile :)](./images/smilies/icon_smile.gif)
![Smile :)](./images/smilies/icon_smile.gif)
ICPUG who cares a lot about frugal install if I get him he suggest
this for slacko531
title Slacko Puppy Linux 5.3.1
kernel (hd1,0)/slacko531/vmlinuz PMEDIA=idehd PDEV1=sdb1 psubdir=slacko531
initrd (hd1,0)/slacko531/initrd.gz
so I will test that one and see if something differs I get back
Last edited by nooby on Fri 02 Mar 2012, 13:38, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
If Slacko 5326, is on partition sda1, of the hard drive and is installed to /slacko5326.
Do a manual edit of the menu.lst
Make a copy entry of the one for 5324 that works and change any place it says 5324 to 5326.
I am assuming a lot by saying this.
I see, you do use some added options, to the kernel line, that just running "Grug4dos bootloader config" will not add to an entry.
It still should find, any operating systems on the computer, and make entries for booting them.
I use it all the time. Let it write to the MBR, of the hard drive, and it places the other files on the first partition. That is where it puts the menu.lst.
It will replace other boot loaders. You know your setup and what you want.
Do a manual edit of the menu.lst
Make a copy entry of the one for 5324 that works and change any place it says 5324 to 5326.
I am assuming a lot by saying this.
I see, you do use some added options, to the kernel line, that just running "Grug4dos bootloader config" will not add to an entry.
It still should find, any operating systems on the computer, and make entries for booting them.
I use it all the time. Let it write to the MBR, of the hard drive, and it places the other files on the first partition. That is where it puts the menu.lst.
It will replace other boot loaders. You know your setup and what you want.
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![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
BigPup don't take this personally now but I would not do this
unless I have no other means and the easiest thing is to ask
somebody that have already done this and ICPUG had.
So thanks to you I looked for that info and found it and it worked.
So a big thanks to you and to ICPUG for leading me in the right direction.
I am using 5326 now and have not had time to test anything else
but it looks like it is okay. So a very happy Nooby. Sorry to derail the thread.
Will be interesting to see of the initrd/mnt/dev_save is still seens
as /mnt/home
What idea do you have about that one?
Edit. Sadly after making a savefile and rebooting it failed to show
icons and clicking on them seems to fail too but menu worked
so seems a problematic version. Am I alone having these problems?
I am using a Acer D255 Netbook
unless I have no other means and the easiest thing is to ask
somebody that have already done this and ICPUG had.
So thanks to you I looked for that info and found it and it worked.
So a big thanks to you and to ICPUG for leading me in the right direction.
I am using 5326 now and have not had time to test anything else
but it looks like it is okay. So a very happy Nooby. Sorry to derail the thread.
Will be interesting to see of the initrd/mnt/dev_save is still seens
as /mnt/home
What idea do you have about that one?
Edit. Sadly after making a savefile and rebooting it failed to show
icons and clicking on them seems to fail too but menu worked
so seems a problematic version. Am I alone having these problems?
I am using a Acer D255 Netbook
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Hi nooby
see page 3 -
http://www.murga-linux.com/puppy/viewto ... 9&start=31
where mick tells you how to cure the missing icons etc problem which occurs because you like me have an ntfs formatted hard disk.
cheers
peebee
see page 3 -
http://www.murga-linux.com/puppy/viewto ... 9&start=31
where mick tells you how to cure the missing icons etc problem which occurs because you like me have an ntfs formatted hard disk.
cheers
peebee
![Image](http://e-nautia.com/peebee/disk/share/logo.png)
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Thanks. I where too caught up trying out a work around
so I reused an old slacko save file and that allowed me to
keep the icons and I am using that one now.
I fail to find a Geeqie picture viewer that works with Slacko though.
Maybe someone has made a pet or sfs that has not gone into the
repo?
The one I had on my HD did not work. It miss a vital lib.
Late at night here so I look into it tomorrow.
Thanks for linking to page three. I had a vague feeling that
there where something like that but I had forgot about it.
anyway I have put so many hours into this save file so I want
to keep it until the next big update at least.
Much appreciated that you cared.
so I reused an old slacko save file and that allowed me to
keep the icons and I am using that one now.
I fail to find a Geeqie picture viewer that works with Slacko though.
Maybe someone has made a pet or sfs that has not gone into the
repo?
The one I had on my HD did not work. It miss a vital lib.
Late at night here so I look into it tomorrow.
Thanks for linking to page three. I had a vague feeling that
there where something like that but I had forgot about it.
anyway I have put so many hours into this save file so I want
to keep it until the next big update at least.
Much appreciated that you cared.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Nooby,
Good to see you got it working.
Your equipment seems to need specialized settings,
so you understand most, what you need.
Good to know it was a bad menu.lst entry, keeping Slacko from booting.
Keep in mind, this version of Slacko is in Beta. It will and should have problems.
I would be very interested in what you would get, if you did just run "Grub4dos bootloader config" and let it do it's normal install and menu.lst setup.
Good to see you got it working.
Your equipment seems to need specialized settings,
so you understand most, what you need.
Good to know it was a bad menu.lst entry, keeping Slacko from booting.
Keep in mind, this version of Slacko is in Beta. It will and should have problems.
I would be very interested in what you would get, if you did just run "Grub4dos bootloader config" and let it do it's normal install and menu.lst setup.
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![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
![Shocked :shock:](./images/smilies/icon_eek.gif)
YaPI(any iso installer)
Grub4dos bootloader config
The Grub4dos config makes a backup of the existing menu.lst. You can manually edit the menu.lst looking up the new and the old.nooby wrote:If you run "Grub4dos bootloader config"
That would destroy all the working entries I already have now.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Yes but I am a pessimistic person. I don't trust back ups.
If something can go wrong it sure will sooner or later.
So why fix something that do work. The work around do work.
But I do have 4GB Flash memory and if one do
Grub4dos bootloader config on one of them then
it will include a menu.lst that list of what is on the HD too?
IIRC that is.
So now when ICPUG has taught me the better way
should I apply that to every OS then ?
If something can go wrong it sure will sooner or later.
So why fix something that do work. The work around do work.
But I do have 4GB Flash memory and if one do
Grub4dos bootloader config on one of them then
it will include a menu.lst that list of what is on the HD too?
IIRC that is.
So now when ICPUG has taught me the better way
should I apply that to every OS then ?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though