Slacko32/64 700 BETA 2
Is there a tool available to setup dual monitors?
It automatically recognises both monitors, like Fatdog which is great, but I need to be able to flip them. Shouldn't there be something in desktop tools like zarfy? Ah just remembered I think it has xrandr. I will check when I get home. I didn't notice in the menu though.
Cheers
It automatically recognises both monitors, like Fatdog which is great, but I need to be able to flip them. Shouldn't there be something in desktop tools like zarfy? Ah just remembered I think it has xrandr. I will check when I get home. I didn't notice in the menu though.
Cheers
I haven't downloaded this new slacko yet, I've done my testing using a special version of peebee's LxPupSc.
All my testing has been done non-uefi.
I've sucessfully booted from hd and usbhd and simulated cd uisng isobooter.
I always boot using grub4dos from a fat32 partition with my frugal puppies and data on an ext4 partition.
I've successufully used a savefolder, savefile, and savepartition (actually by accident).
The new init is not a clone of the old init.
The old init searchs all over the place by default, the new init does some searching, only if it can't be avoided.
It's designed to take full advantage of boot parameters to tell it where stuff is.
It's basic algorithm is to establish where the puppy...sfs is, and expect everything else to be there, unless otherwise specified.
Recommendtion
Specify the following boot parameters:
1. pmedia = atahd.....etc
2. pupsfs(pdev1 is an alias) = name, label or uuid of the partition containing the puppy..sfs
3. psubdir = /path/of/furgal/install
4. psave = name, label or uuid of partition to contain the save folder. If it's not the same as pupsfs.
If you want to have something on atahd and something on usbhd then specify pmedia=atahd
The "flash" part of pmedia simply adds 1 to the pupmode for "hd".
It does include support for multi session cd/dvd, but not yet tested.
Unfortunately reverting to the curent init, means also reverting sfs_load. The new ones both assume that the init only processes system sfs files, and sfs_load only processes extra sfs files.
It's definitely still a work in progress.
@James C,
I don't understand why it works for some but not for you, I will try to replicate.
gyro
All my testing has been done non-uefi.
I've sucessfully booted from hd and usbhd and simulated cd uisng isobooter.
I always boot using grub4dos from a fat32 partition with my frugal puppies and data on an ext4 partition.
I've successufully used a savefolder, savefile, and savepartition (actually by accident).
The new init is not a clone of the old init.
The old init searchs all over the place by default, the new init does some searching, only if it can't be avoided.
It's designed to take full advantage of boot parameters to tell it where stuff is.
It's basic algorithm is to establish where the puppy...sfs is, and expect everything else to be there, unless otherwise specified.
Recommendtion
Specify the following boot parameters:
1. pmedia = atahd.....etc
2. pupsfs(pdev1 is an alias) = name, label or uuid of the partition containing the puppy..sfs
3. psubdir = /path/of/furgal/install
4. psave = name, label or uuid of partition to contain the save folder. If it's not the same as pupsfs.
If you want to have something on atahd and something on usbhd then specify pmedia=atahd
The "flash" part of pmedia simply adds 1 to the pupmode for "hd".
It does include support for multi session cd/dvd, but not yet tested.
Unfortunately reverting to the curent init, means also reverting sfs_load. The new ones both assume that the init only processes system sfs files, and sfs_load only processes extra sfs files.
It's definitely still a work in progress.
@James C,
I don't understand why it works for some but not for you, I will try to replicate.
gyro
Ok, this test is not using this slacko, but the init scripts should be identical.
I did a manual frugal install on a usb hd, sdc1 fat32, sdc2 ext4.
Ran "Grub4dos boot loader config" on sdc.
Booted sdc. Successful boot to desktop.
This is the entry in menu.lst created by grub4dos:I later improved the kernel line to this:
The only probelm I had was was on first reboot, it thought that it was upgrading from version "".
I think this is a "DISTRO_SPECS" presence issue. I'll look into it.
As soon as I manage to download this slacko I'll do this test again.
gyro
I did a manual frugal install on a usb hd, sdc1 fat32, sdc2 ext4.
Ran "Grub4dos boot loader config" on sdc.
Booted sdc. Successful boot to desktop.
This is the entry in menu.lst created by grub4dos:
Code: Select all
title Puppy LxPupSc 16.08.992 (sdc2/lxpup)
uuid 7d78f855-bc32-4c1d-9d06-5bc6c7a9e01c
kernel /lxpup/vmlinuz psubdir=lxpup pmedia=atahd pfix=fsck
initrd /lxpup/initrd.gz
Code: Select all
kernel /lxpup/vmlinuz pupsfs=7d78f855-bc32 psubdir=lxpup pmedia=atahd pfix=fsckp
I think this is a "DISTRO_SPECS" presence issue. I'll look into it.
As soon as I manage to download this slacko I'll do this test again.
gyro
Testing slacko64 6.9.5.
Same test as for LxPupSc.
First boot to desktop, worked.
Reboot with savefolder, and subsequent reboots, worked.
Here is my grub4dos entry:None of these were uefi boots.
Challanges:
1. Major problems displaying application windows, e.g. geany.
Soloution: Add /etc/X11/xorg.conf.d/20-intel.conf file containing:I have the same problem with xenialpup.
2. My 2 monitors were back to front, (becomes quite annoying).
Solution: Add a small script in /root/Startup containing:
gyro
Same test as for LxPupSc.
First boot to desktop, worked.
Reboot with savefolder, and subsequent reboots, worked.
Here is my grub4dos entry:
Code: Select all
title Puppy slacko64 6.9.5 (sdc2/skacko64)
uuid 7d78f855-bc32-4c1d-9d06-5bc6c7a9e01c
kernel /skacko64/vmlinuz libata.noacpi=1 pupsfs=7d78f855-bc32 psubdir=skacko64 pmedia=atahd pfix=fsckp
initrd /skacko64/initrd.gz
Challanges:
1. Major problems displaying application windows, e.g. geany.
Soloution: Add /etc/X11/xorg.conf.d/20-intel.conf file containing:
Code: Select all
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
2. My 2 monitors were back to front, (becomes quite annoying).
Solution: Add a small script in /root/Startup containing:
Code: Select all
#!/bin/sh
xrandr --output HDMI1 --auto --output VGA1 --auto --right-of HDMI1
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
On my current Woof-CE puppies. pupsfs is device:path/puppysfsfilename.gyro wrote: 2. pupsfs(pdev1 is an alias) = name, label or uuid of the partition containing the puppy..sfs
3. psubdir = /path/of/furgal/install
4. psave = name, label or uuid of partition to contain the save folder. If it's not the same as pupsfs.
gyro
pdev1 is the device containing the savefile, which is not the same device. So pupsfs and pdev1 couldn't be an alias.
Existing puppies can load the puppy.sfs (also zdrv) explicitly and search pdev1:psubdir for the savefile.
psave was listed in the wiki, but didn't actually exist in the init script.
Hopefully I can work out an equivalent for the new init scheme.
Booted from LiveCD selecting the UEFI (FAT) entry for the DVD writer from the computer's boot device menu. Booted successfully in a desktop with the usual setup windows.
I still don't like the default theme having the taskbar at the top, tried to use it like that last time and found it too weird. Sharp loaded up the theme manager and changed the theme to Pop .
On the initial boot the filenames on a FAT16 memory stick were truncated in the ROX Filer windows but the NTFS and ext partitions were still long. Once I'd managed to reboot from the save I could see long filenames on the stick, however.
Wireless network setup with my trusty Netgear WN111v2 dongle using Frisbee proceeded without any issues. Usual Static IP setup. Downloaded Flash Player OK and did a spot of surfing on Firefox.
There is no maximum cache size set on Firefox so there's the potential for all of the save file space being eaten. Manually set this to 50MB.
Set frequency scaling to performance and chose to reboot. Set it to create a 1GB Ext4 save file in a subdirectory called PuppyFiles on sdb1, a 160GB NTFS formatted hard drive with my Windows XP install on.
Upon rebooting the machine proceeded to load off the CD only and arrived at a fresh start like you'd get with a pfix=ram start rather than loading any files off the hard drive. I checked sdb1/PuppyFiles and the save and sfs files I'd manually copied were there. I moved them to the sdb1 root directory and reboooted.
With the two SFS files and the save on the root directory of sdb1 Slacko did now load the SFS files from the hard drive on booting and successfully loaded the save file I'd created on the first boot.
It would appear that the routine that searches for existing Puppy files isn't looking in sub-directories.
I still don't like the default theme having the taskbar at the top, tried to use it like that last time and found it too weird. Sharp loaded up the theme manager and changed the theme to Pop .
On the initial boot the filenames on a FAT16 memory stick were truncated in the ROX Filer windows but the NTFS and ext partitions were still long. Once I'd managed to reboot from the save I could see long filenames on the stick, however.
Wireless network setup with my trusty Netgear WN111v2 dongle using Frisbee proceeded without any issues. Usual Static IP setup. Downloaded Flash Player OK and did a spot of surfing on Firefox.
There is no maximum cache size set on Firefox so there's the potential for all of the save file space being eaten. Manually set this to 50MB.
Set frequency scaling to performance and chose to reboot. Set it to create a 1GB Ext4 save file in a subdirectory called PuppyFiles on sdb1, a 160GB NTFS formatted hard drive with my Windows XP install on.
Upon rebooting the machine proceeded to load off the CD only and arrived at a fresh start like you'd get with a pfix=ram start rather than loading any files off the hard drive. I checked sdb1/PuppyFiles and the save and sfs files I'd manually copied were there. I moved them to the sdb1 root directory and reboooted.
With the two SFS files and the save on the root directory of sdb1 Slacko did now load the SFS files from the hard drive on booting and successfully loaded the save file I'd created on the first boot.
It would appear that the routine that searches for existing Puppy files isn't looking in sub-directories.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
This is the old init (Xenialpup 7.0.4):
https://github.com/puppylinux-woof-CE/w ... nitrd/init
This it the new init (Slacko 700 ALPHA):
https://github.com/puppylinux-woof-CE/w ... nitrd/init
https://github.com/puppylinux-woof-CE/w ... nitrd/init
This it the new init (Slacko 700 ALPHA):
https://github.com/puppylinux-woof-CE/w ... nitrd/init
fixed tray placement. See
https://github.com/puppylinux-woof-CE/w ... 7eec0d7222
This also fixes other missing icons - as the one in ppm search result box when no package is found
https://github.com/puppylinux-woof-CE/w ... 7eec0d7222
This also fixes other missing icons - as the one in ppm search result box when no package is found
In the old init, pdev1 is where it finds vmlinuz, (check the code).
It's meant to be the partition that contains the puppy...sfs file.
It could be set as a boot parameter, in which case it was just a partition name.
The savefolder was always found there, because the old init went looking everywhere for savefiles/folders and then discarded all the entries that were not on pdev1.
If pupsfs contains only a partition spec e.g. pupsfs=sdb2 then it is the same as specifying pdev1=sdb2.
To specify the partition for the savefolder use psave=sdb3, or psave=Work or psave=0db94719-cdf1
The new init expects to find files in PSUBDIR, so if puppy files exist on 2 partitions the PSUBDIR must exist on both partitions.
For a cd boot PSUBDIR is always empty, so files on another partition are assumed to be in the root directory of that partition.
Of course you can overide this using the boot parameters pupsys, adrv, ydrv, fdrv, zdrv, psave.
gyro
It's meant to be the partition that contains the puppy...sfs file.
It could be set as a boot parameter, in which case it was just a partition name.
The savefolder was always found there, because the old init went looking everywhere for savefiles/folders and then discarded all the entries that were not on pdev1.
If pupsfs contains only a partition spec e.g. pupsfs=sdb2 then it is the same as specifying pdev1=sdb2.
To specify the partition for the savefolder use psave=sdb3, or psave=Work or psave=0db94719-cdf1
The new init expects to find files in PSUBDIR, so if puppy files exist on 2 partitions the PSUBDIR must exist on both partitions.
For a cd boot PSUBDIR is always empty, so files on another partition are assumed to be in the root directory of that partition.
Of course you can overide this using the boot parameters pupsys, adrv, ydrv, fdrv, zdrv, psave.
gyro
My setup which I've used for years consists of: Legacy Grub installed to the mbr of sda (ssd on this box) ,uefi with secure boot turned off and 2 hard drives (for now).Individual folders.... pup01,pup20,pup20,etc for frugal installs with a prebuilt menu.lst.gyro wrote: @James C,
I don't understand why it works for some but not for you, I will try to replicate.
gyro
Only need to change the title when changing installs.
Code: Select all
title Puppy Slackoff 5.9.3-1 Frugal on sdb1
rootnoverify (hd1,0)
kernel /pup13/vmlinuz pfix=fsck pdev1=sdb1 pmedia=atahd psubdir=pup13
initrd /pup13/initrd.gz
title PuppEX Xenial frugal in sdb2 dir pup14
rootnoverify (hd1,0)
kernel /pup14/vmlinuz pmedia=atahd psubdir=pup14
initrd /pup14/initrd.gz
title Slacko64 6.9.5 frugal in sdb1
rootnoverify (hd1,0)
kernel /pup15/vmlinuz pmedia=atahd pfix=fsck pdev1=sdb1 psubdir=pup15
initrd /pup15/initrd.gz
title Librepup 6.0.2.2 Frugal
rootnoverify (hd1,0)
kernel /pup16/vmlinuz pfix=fsck pdev1=sdb1 pmedia=atahd psubdir=pup16
initrd /pup16/initrd.gz
title Empty frugal
rootnoverify (hd1,0)
kernel /pup17/vmlinuz pfix=fsck pdev1=sdb1 pmedia=atahd psubdir=pup17
initrd /pup17/initrd.gz
title Puppy Xenial 7.0.4 Frugal on sdb1
rootnoverify (hd1,0)
kernel /pup18/vmlinuz pfix=fsck pdev1=sdb1 pmedia=atahd psubdir=pup18
initrd /pup18/initrd.gz
Believe that billtoo reported a no boot also.
gyro wrote:@James C,
I notice most of your kernel lines have a pdev1=sdb1, but 1 shown doesn't.
If you use a kernel line that doesn't specify a pdev1 (or pupsfs) it will go looking on all partitions.
So what kernel line did you use?
Got error messages, what were they?
gyro
Used the one shown, only changed the title.
Error messages were something about ext4 errors on sdb7,sdb8 and sdb9 which are now occupied by AntiX, Trisquel and Devuan and not being able to find the slacko64 sfs on sdb9.
http://www.murga-linux.com/puppy/viewto ... 447#920447