slacko 5.3.3, final
Hi Mick
5.3.2.6 seemed to work fine using an updated 5.3.2.4 savefile...
however 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.
My disk is ntfs formatted. The savefile I created was ext2 no encryption.
Very strange.
Cheers
Peter
5.3.2.6 seemed to work fine using an updated 5.3.2.4 savefile...
however 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.
My disk is ntfs formatted. The savefile I created was ext2 no encryption.
Very strange.
Cheers
Peter
- Attachments
-
- capture10355.png
- (27.32 KiB) Downloaded 1305 times
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I'd be interested peebee if the same occurs on racy which uses roughly the same woof. What this is indicating is that the save didn't work at all.
Also, perhaps you could try again using shinobar's pupsaveconfig, which creates the save before shutdown. Barry has changed a fair bit in shutdown scripts lately.
To remedy the current situation run: restart X then reset your wallpaper.
Also, perhaps you could try again using shinobar's pupsaveconfig, which creates the save before shutdown. Barry has changed a fair bit in shutdown scripts lately.
To remedy the current situation run:
Code: Select all
gdk-pixbuf-query-loaders --update-cache
Puppy Linux Blog - contact me for access
Just tried shino's pupsaveconfig and this worked fine......01micko wrote:I'd be interested peebee if the same occurs on racy which uses roughly the same woof. What this is indicating is that the save didn't work at all.
Also, perhaps you could try again using shinobar's pupsaveconfig, which creates the save before shutdown. Barry has changed a fair bit in shutdown scripts lately.
To remedy the current situation run:restart X then reset your wallpaper.Code: Select all
gdk-pixbuf-query-loaders --update-cache
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
>>> Dell Studio XPS 1340
I got Broadcom >> b43 to work on previous slacko....9th post.
http://murga-linux.com/puppy/viewtopic. ... &start=240
Courtesy of pemasu >> his pet and grump's post.
This time >> nothing.
"""""""""""
I did the same steps in the above post nothing.
Rebooted again ...fresh boot...
pinched the previous files from older Slacko....lib/firmware/b43
renamed your b43....copied my older b43 to the same >> lib/firmware
Then in the network wizard unloaded the b43 module,
then reloaded it....but it fails to find wireless.
But Puppy barks first off this time....
no fiddling >>> ticking speaker for the Dell.
And a nice wallpaper.
I will now get out old baked bean tins and string...
bewdy mate.
Regards...Chris.
Hope your course is going well mate.
I got Broadcom >> b43 to work on previous slacko....9th post.
http://murga-linux.com/puppy/viewtopic. ... &start=240
Courtesy of pemasu >> his pet and grump's post.
This time >> nothing.
"""""""""""
I did the same steps in the above post nothing.
Rebooted again ...fresh boot...
pinched the previous files from older Slacko....lib/firmware/b43
renamed your b43....copied my older b43 to the same >> lib/firmware
Then in the network wizard unloaded the b43 module,
then reloaded it....but it fails to find wireless.
But Puppy barks first off this time....
no fiddling >>> ticking speaker for the Dell.
And a nice wallpaper.
I will now get out old baked bean tins and string...
bewdy mate.
Regards...Chris.
Hope your course is going well mate.
racy 5.2.2.7 worked OK - created a pupsave same parameters and successful reboot to working desktop....01micko wrote:I'd be interested peebee if the same occurs on racy which uses roughly the same woof. What this is indicating is that the save didn't work at all.
Also, perhaps you could try again using shinobar's pupsaveconfig, which creates the save before shutdown. Barry has changed a fair bit in shutdown scripts lately.
To remedy the current situation run:restart X then reset your wallpaper.Code: Select all
gdk-pixbuf-query-loaders --update-cache
see 5.2.2.8 is available - haven't tried that yet....waiting waiting waiting for download - sometime later - racy 5.2.2.8 also worked OK - again successfully created a pupsave same parameters and successful reboot to working desktop
Last edited by peebee on Sun 26 Feb 2012, 11:39, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Broadcom STA driver for slacko union-fs kernel
[update] 25-03-12
I've created a forum page for all of the Broadcom-STA wl drivers:
http://www.murga-linux.com/puppy/viewtopic.php?t=76495
[/update]
Cheers
peebee
I've created a forum page for all of the Broadcom-STA wl drivers:
http://www.murga-linux.com/puppy/viewtopic.php?t=76495
[/update]
Cheers
peebee
Last edited by peebee on Sun 25 Mar 2012, 19:58, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Some days ago I've had the same problem with Gparted as James C. It was with 5.3.2.4. I thought, it was because of playing with truecrypt before. I used Gparted with Lupu and it worked fine. After this I could also format my usb stick again with 5.3.2.4. Ext2. ext3, VFAT, no problem.
Now testing 5.3.2.6.
First surprise, I'm able to create an encrypted save file with 3fs.
Is it a bug or a feature? I would prefer the latter, but using it, I get the same problems as peebee, no background and no icons. This happens with .3fs heavy or light encrypted save files on an ext3 partition. Unencrypted save file .3fs works OK. Will check Racy later.
Compiz works fine. No need to patch radeon.conf or xorg.conf as before.
Cheers
Rolf
Now testing 5.3.2.6.
First surprise, I'm able to create an encrypted save file with 3fs.
Is it a bug or a feature? I would prefer the latter, but using it, I get the same problems as peebee, no background and no icons. This happens with .3fs heavy or light encrypted save files on an ext3 partition. Unencrypted save file .3fs works OK. Will check Racy later.
Compiz works fine. No need to patch radeon.conf or xorg.conf as before.
Cheers
Rolf
Ich verwende "frugal", und das ist gut so. :wink:
Raspberry Pi without Puppy? No, thanks.
Raspberry Pi without Puppy? No, thanks.
Rolf, the crypto thing is probably a new feature of the newer kernels, I bet racy works too, I suggest the solution I said to peebee to get back to a normal desktop. The thing is, Barry, and therefore the puppy scripts don't know about the new feature. Thanks for your enlightening post! We will make use of this new feature . Oh, glad compiz is fine for you too.
peebee, I can create a save file in ntfs that is just fine , just not using pupdialog! . If you drop to a prompt and shutdown/reboot the old way then all's well. I have sent a report to Barry and I captured a log of sorts which doesn't seem to mean a lot but I'll publish it anyway.
Ignore the disktype error, it's only a probe of the floppy controller, no floppy drive present.
Cheers!
peebee, I can create a save file in ntfs that is just fine , just not using pupdialog! . If you drop to a prompt and shutdown/reboot the old way then all's well. I have sent a report to Barry and I captured a log of sorts which doesn't seem to mean a lot but I'll publish it anyway.
Code: Select all
disktype: Data read failed at position 0: Input/output error
/usr/sbin/shutdownconfig: line 235: 12821 Terminated yaf-splash -bg orange -close never -fontsize large -text "$T_waitprobing"
sda1,ntfs,/test/slackosave.2fs
131072+0 records in
131072+0 records out
134217728 bytes (134 MB) copied, 10.508 s, 12.8 MB/s
/usr/bin/pupdialog: line 259: 14362 Terminated /tmp/pupdialog_exec --center --class="module16" --program=PUP${$}DLG > /tmp/pupdialog_retvals${$}
/usr/bin/pupdialog: line 266: TAGPREFIXFIX_: command not found
Cheers!
Puppy Linux Blog - contact me for access
For getting icons back, this works fine.01micko wrote:I suggest the solution I said to peebee to get back to a normal desktop
This does only work if I create manually a folder .pwidgets in /root/. Could have something to do with Compiz. I remember that I've had this problem some weeks ago, trying to run Slideshow from Nathan Wallpaper Setter. With Compiz, the same error, with a fresh save file without Compiz it worked. But not so important, just for info.restart X then reset your wallpaper.
That's hard to believe, see attachment.The thing is, Barry, and therefore the puppy scripts don't know about the new feature.
All in all, it's very interesting, also the internationalisation part.
Cheers
Rolf
- Attachments
-
- shutdown.jpg
- (64.83 KiB) Downloaded 2792 times
Ich verwende "frugal", und das ist gut so. :wink:
Raspberry Pi without Puppy? No, thanks.
Raspberry Pi without Puppy? No, thanks.
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! .. So I am the one unaware!!!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.
EDIT: so I tested:
saving encrpted to 2fs is fine
3fs is broken from gui AND console with a similar error from GUI as with the ntfs issue:
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
Puppy Linux Blog - contact me for access
Very strange. For me it seems to work fine after getting back icons and wallpaper. Just now I use a light encrypted 3.fs save file. Installed Compiz, works fine, also after rebooting.01micko wrote:3fs is broken from gui AND console with a similar error from GUI as with the ntfs issue:
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....
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?
- 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?
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
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