Puppy Linux Discussion Forum

[davids45]

G'day 666philb,

Running a Frugal without problem.

Wine and Seamonkey as symlinks, games and extra file managers from sfs, pwidgets and taskbar-CPUtemps from pets all good.

Will do a Full soon.

David S.

[slavvo67]

Well, I did a few adjustments:

MPlayer install through PPM - Check. All good.

HandBrakeCLI install through PPM - Check. All good.

Libre Writer amended to not auto-save. - Check. No more unexpected saves.

Libre Writer amended to not auto-update. - Check. No annoying pop-ups to update.

No noticeable flaws. Looks like Puppy's future continues to get brighter.

Thanks 666PhilB!

Slavvo67

[666philb]

[davids45]

G'day 666philb,

Installed Vivid Beta as a Full to sdb6 from my Frugal Vivid (on sda7) via the Universal Installer using the 'Directory' option (at /home/vividpup) to locate the install files for the UI to use.

First install attempt failed to wipe and copy files to sdb6 as sdb6 may have been already mounted - the UI did not report any problem and seemed to be doing the expected copying of files. I manually wiped sdb6 of its old files from a previous Pup and then from the Vivid Frugal, the Full install went as expected.

First booting of the Full Vivid produced a fail, an immediate screen of text lines suggesting some sort of internal panic, and a hung computer.
Being a slow learner/ fast optimist, I pressed the on/off button for ~5 seconds and chose Vivid again from the grub list and this time it booted and ran as well as my Frugal Vivid.

Next day (this morning), first boot of the Full Vivid and again the instant screen of text and a hung computer. And again, second boot attempt and Vivid is running without problem.

So it may be this desktop, or a bug in the UI when operated this way, or something to do with Vivid in the Full situation, or ...

Will persevere .

David S

Update: this afternoon, same Vivid hang at cold boot but I saw there was a brief red text message about "performing" something on sdb6 then text scrolled off-screen and the computer hung. Re-start and Vivid boots OK.

UpdatedUpdate: after using a few other Pups on this desktop, I went back to my Vivid Frugal (did not want to try the Full) and noticed the red text crashing the Full seems to be a file check of the partition at kernel-loading time.
My Frugal Vivid on sda7 began by checking the Full Vivid on sdb6?? No other Frugal Pup has gone looking for its Full equivalent this way or if one has, it has not reported finding anything to check..
This Full check by the booting Frugal was pretty quick - just a few dots - and then it did the menu-list-requested fsck check on the sda7 partition which took a l-o-n-g time compared to other Frugal Pups - sda7 has all my Frugals and I let Vivid have the entire partition for its Save file if needed.
Anyway, the Vivid Frugal is presently OK.

[James C]

Just a quick live test.Looks good on this box as well.

[Billtoo]

Installed with the puppy installer to a 16gb usb 3.0 flash drive,running
on a macmini:

root# report-video
VIDEO REPORT: vividpup, version beta2

Chip description:
VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1920x1080
Depth (bits, or planes): 24
Modules requested to be loaded: dbe

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): intel
Loaded modules: dbe dri2 extmod glx kbd mouse present

Actual rendering on monitor:
Resolution: 1920x1080 pixels (507x285 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video
root#

No problems so far.

[Satori]

My usual method of running puppies is to use two partitions, the first contains the grub-boot and associated puppy files
while the second contains data and third party programs, which includes the savefile in a separate directory.

dpup wheezy's grub section is:

title dPup 3.5.2.11 ==> (sda3)
root (hd0,0)
kernel /puppy/dpup/vmlinuz pmedia=atahd pfix=fsck pdevl=sda3 psubdir=puppy/dpup psubok=TRUE
initrd /puppy/dpup/initrd.gz

other puppies boot much the same way.

However Vivid fails to boot properly unless it's .SFS files are also within the same directory with the savefile.

title Vivid Beta ==> (sda3)
root (hd0,1)
kernel /Vivid/vmlinuz pmedia=atahd pfix=fsck pdevl=sda3 psubdir=puppy/vivid psubok=TRUE
initrd /Vivid/initrd.gz

Note that each puppy directory also has a SAVEMARK that points to SDA3.

Otherwise, Vivid looks to be nice puppy.

Further testing shows that the following works, without needing vivid's .SFS files to be in the savefile directory:

title Vivid Beta ==> (sda3)
root (hd0,0)
kernel /puppy/vivid/vmlinuz pmedia=atahd pfix=fsck pdevl=sda3 psubdir=puppy/vivid psubok=TRUE
initrd /puppy/vivid/initrd.gz

Note that the dir names for both vivid boot and savefile are the same.

[666philb]

[666philb]

[James C]

[James C]

Rebooted and powered off this full install at least 10 times....zero problems.

[James C]

Latest Google Chrome works fine on Vivid Beta too.

[666philb]

[James C]

[666philb]

installing the deb breaks some cups permissions but there's supposed to be a fix
does cups work after installing the .deb?