Page 2 of 3
Posted: Tue 21 Sep 2010, 18:48
by nooby
Edit I reacted to this text from you
normally with Frugal installs, I can have several 'save files in the same directory, and during the boot process, I get a menu option to choose which I want to use. This seems to be absent in this release?
I have downloaded and tested 1.3 with a menu.lst
that looks like this
title Quirky 1.3 RC Linux
root (hd0,1)
kernel /qrky-130/vmlinuz psubdir=qrky-130 PKEYS=se vga=normal pfix=fsck
initrd /qrky-130/initrd.gz
boot
title Quirky 1.0 Linux
root (hd0,1)
kernel /quirky/vmlinuz psubdir=quirky pfix=fsck
initrd /quirky/initrd.gz
boot
I am in qrky-130 now and it did load the qrky-130-pupsave file so did it really work like you say? Okay at your machine but how is that one different from mine?
pwallpaper segfaulting
Posted: Tue 21 Sep 2010, 21:40
by duke93535
AlI I did was delete the folder /root/.config/cwallpaper and added a new folder (directory) wallpaper at /root/.config, then it started working. Restarting pwallpaper rebuilt the two folders contents and all is OK.
duke
Posted: Tue 21 Sep 2010, 21:52
by Brown Mouse
I updated to 1.3 using the existing save file but I don't see any new desktop backgrounds??Is there a way to retrieve them?
Posted: Tue 21 Sep 2010, 22:08
by duke93535
I only see one change and that is replacing the default.jpg with the numbers 1.3 on it.
duke
Posted: Tue 21 Sep 2010, 22:41
by Brown Mouse
duke93535 wrote:I only see one change and that is replacing the default.jpg with the numbers 1.3 on it.
duke
Your lucky then,mine still says 1.2
Posted: Tue 21 Sep 2010, 22:50
by BarryK
CHLee wrote:1. In console mode, run xwin have below waring:
xwin
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
2. osmo personal organizer, Segmentation fault:
osmo
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
Failed to load x11 FrontEnd module.
Segmentation fault
3. pmusic, can not play mp3 file:
pmusic
/usr/local/pmusic/presets/Classic: line 15: [: =: unary operator expected
killall: cdda2wav: no process killed
/usr/local/pmusic/func: line 803: id3info: command not found
grep: 1: No such file or directory
/usr/local/pmusic/func_progressbar: line 19: [: =: unary operator expected
killall: cdda2wav: no process killed
killall: cdda2wav: no process killed
grep: invalid option -- ' '
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Thanks!
I have just tested Osmo and Pmusic in a new installation (frugal) of Quirky 1.3RC, they both work, and Pmusic plays an mp3.
One thing, id3info is missing from Quirky.
That grep fault you get, that is strange. The other fault reports, yeah well, that is how zigbert writes scripts -- that spit out error reports yet they are non-fatal and the script still works. Ideally, the script should be written such that things like "[: =: unary operator expected" do not get printed out -- it is possible to write scripts to avoid error reports like that. Or, if a non-fatal error message cannot be avoided, then put "2>/dev/null" in the script so that the user doesn't see it (and report it as a bug).
Posted: Tue 21 Sep 2010, 22:57
by BarryK
DaveS wrote:Odd one this.... normally with Frugal installs, I can have several 'save files in the same directory, and during the boot process, I get a menu option to choose which I want to use. This seems to be absent in this release?
This is the kind of stuff that needs sorting out with the new init script, the algorithm it uses to find files.
Do you mean that you have Q 1.3RC installed in a directory, say "quirky130", with more than one save-file inside it? Or, save-files elsewhere?
Posted: Tue 21 Sep 2010, 23:08
by BarryK
BarryK wrote:DaveS wrote:Odd one this.... normally with Frugal installs, I can have several 'save files in the same directory, and during the boot process, I get a menu option to choose which I want to use. This seems to be absent in this release?
This is the kind of stuff that needs sorting out with the new init script, the algorithm it uses to find files.
Do you mean that you have Q 1.3RC installed in a directory, say "quirky130", with more than one save-file inside it? Or, save-files elsewhere?
Ah yes, I see. In a frugal installation, I created a second pup-save in the install-directory, rebooted and it didn't ask, just used one of them.
It should have asked. Ok, I will examine the 'init' script, see if I can fix that.
Posted: Tue 21 Sep 2010, 23:15
by rcrsn51
Can anyone confirm my observation that pfix=nocopy seems to be the new default with a frugal install? ie. the sfs file is NOT being loaded into RAM unless you use the boot argument pfix=copy.
Posted: Wed 22 Sep 2010, 00:04
by Billtoo
BarryK wrote:
Ah yes, I see. In a frugal installation, I created a second pup-save in the install-directory, rebooted and it didn't ask, just used one of them.
.
I'm running live with a save file and it asks which one of the 3 on hard disk to use.
Posted: Wed 22 Sep 2010, 00:35
by duke93535
Brown Mouse,
Your lucky then,mine still says 1.2
What you’re running into is because of upgrading and the layered system. For example there are two default.jpg with the same name and one is in your save file and the other is in your new puppy.sfs. The one in the qrkysave file overrules the one in the puppy.sfs.
If you delete the one in /usr/share/backgrounds/default.jpg and then delete the .wh.default.jpg (whiteout files are hidden, so you need to hit the eye to see) file in /initrd/pup_rw/usr/share/backgrounds then the new one will be installed on a reboot
duke
Gparted
Posted: Wed 22 Sep 2010, 05:05
by duke93535
Gparted does not work correctly, with resizing and formating. I went back to gparted 0.5.1 and used Quirky 1.2 parted libraries.
duke
PPM bug with furugal install on flash
Posted: Wed 22 Sep 2010, 06:03
by shinobar
Puppy Package Manager(PPM) of recent woof has 2 big problem with frugal install on flash.
PROBLEM
Assume furugal install with pupsave on flash device, using recent PPM.
1. Install, say somepackege-1.0.pet, unistall it, then again install the same package or the same package updated, say somepackage-1.1.pet .
The files somepackage must recover in most case.
But recent PPM with frugal install, the PPM shows no error but the files disappear.
In case uninstall, then reboot PC, and re-install the package, the files recover with no problem.
2. Installing some packages which has files under '/mnt/home', the PPM shows no error but the files under '/mnt/home' disappear.
REASON
There is a bug at the code add on 26 Apr 2010 and later, for boot from flash, bypass tmpfs top layer, install direct to pup_save file.
SOLUTION
http://murga-linux.com/puppy/viewtopic. ... 934#452934
Right click 'Connect' icon
Posted: Wed 22 Sep 2010, 06:18
by shinobar
Automatic LAN connection if eth0 and DHCP available.
In this case, right click the 'Connect' icon on the desktop, or the tray icon.
It has the menu items 'Autoconnect'/'Disconnect', but it does not but launches connection wizard in this case.
http://murga-linux.com/puppy/viewtopic. ... 017#444017
Posted: Wed 22 Sep 2010, 08:31
by Brown Mouse
duke93535 wrote:Brown Mouse,
Your lucky then,mine still says 1.2
What you’re running into is because of upgrading and the layered system. For example there are two default.jpg with the same name and one is in your save file and the other is in your new puppy.sfs. The one in the qrkysave file overrules the one in the puppy.sfs.
If you delete the one in /usr/share/backgrounds/default.jpg and then delete the .wh.default.jpg (whiteout files are hidden, so you need to hit the eye to see) file in /initrd/pup_rw/usr/share/backgrounds then the new one will be installed on a reboot
duke
Thanks duke93535,that worked a treat
Posted: Wed 22 Sep 2010, 08:39
by Brown Mouse
Still unable to download anything from Puppy-Quirky repo from ppm with any selected URL.(except for the package Barry mentioned earlier 'ffplay')
I get'error,failed to download******'
Menu nesting
Posted: Wed 22 Sep 2010, 09:43
by shinobar
Lobster wrote:Some Puppys have 3 levels of menu - Quirky Puppy has two
On a small screen (such as on my Eeepc) 3 levels are not viewable
Quirky has 2 - works better - you can get to all components
Are you aware that there are 3 types of menu nesting?
- Qrky-1.3 has 2 levels, same as Wary, Puppy 4.x.
- LupQ-509(Quiqset edition) has 3 levels, same as Fatdog64.
- Lupu-511 is quite different, say 2.5 levels.
I tested these 3 puppies with 640x480 screen size.
No problem on Qrky-1.3 and LupQ-509, no matter with 2 or 3 level.
The only problem occurs on Lupu-511. Maybe comes from its specific menu style. See the attached.
http://murga-linux.com/puppy/viewtopic. ... 348#442348
Posted: Wed 22 Sep 2010, 11:00
by Karl Godt
COPY this to the geany text editor
Code: Select all
[Desktop Entry]
Encoding=UTF-8
Name=PupDial modem dialup
Icon=mini-connect.xpm
Comment=PupDial modem dialup
Exec=pupdial
Terminal=false
Type=Application
Categories=Network;Dialup;
GenericName=PupDial
and save it as /usr/share/applications/pupdial.desktop
run fixmenus & restart jwm or restart x server
Categories=Network;Dialup; provides submenus at some puppies and some not even when /etc/xdg/menus and /usr/share/desktop-directories seem to be identical
Posted: Wed 22 Sep 2010, 23:42
by BarryK
Quirky 1.3-final is released. New forum feedback thread:
http://murga-linux.com/puppy/viewtopic.php?t=60163
modprobe and module .conf
Posted: Thu 23 Sep 2010, 13:08
by Karl Godt
Congratulations !
puppy.sfs runs really fine on my hardware (1.05 G AMD CPU 384 M RAM NVidia Card Generic CRT Monitor 3 IDE HD 350 W PowerSupply )
Like all the other Puppies !!
Nathan Wallpaper Settler is the one that indicates rc from official release
Something about modprobe.conf : While I was trying to get an older serial mouse to work (it`s from logitech .. so need to search for a driver I guess) I stumbled over
/etc/modules.conf :
#I left this file here for old-times sake. 2.6 kernel uses modprobe.conf.
# Note, the script /etc/rc.d/rc.sysinit*
# calls script /etc/rc.d/rc.modules*
# to load the modules.
# modprobe* references this config file, modules.conf.
#v432 rerwin: This file is still used by Conexant-modems to retain major-number selections for the experimen
I could have posted it at the new thread but there is some graphics process going on atm
