vividpup beta
Another happy VB(eta) user
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.
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.
- Attachments
-
- vividbetaFrugal.jpg
- Desktop Frugal - ZooGrandkids
- (170.04 KiB) Downloaded 1030 times
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
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
Re: Vivid
hi sszindian,sszindian wrote:
One question... what's the name of the default PDF reader? and where is it located?
Hope you take this one all the way!!!
>>>---Indian------>
vivid has evince pdf viewer .... it's located in /usr/bin and in menu>>document
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Full Vivid Beta
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.
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.
Last edited by davids45 on Thu 30 Apr 2015, 07:17, edited 1 time in total.
Just a quick live test.Looks good on this box as well.
Code: Select all
root# report-video
VIDEO REPORT: vividpup, version beta2
Chip description:
VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
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): nouveau
Loaded modules: dbe dri2 extmod fb glamoregl glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1920x1080 pixels (507x285 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
root#
Code: Select all
-Computer-
Processor : 8x AMD FX(tm)-8320 Eight-Core Processor
Memory : 8192MB (384MB used)
Machine Type : Physical machine
Operating System : vividpup - beta2
User Name : root (root)
Date/Time : Thu 30 Apr 2015 02:07:13 AM CDT
-Display-
Resolution : 1920x1080 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA ATI SB
Audio Adapter : HDA-Intel - HDA NVidia
Audio Adapter : PC-Speaker - pcsp
Code: Select all
-Version-
Kernel : Linux 3.19.5-vivid_PAE-32-pae (i686)
Version : #1 SMP Mon Apr 27 11:12:29 GMT-8 2015
C Library : GNU C Library version 2.19 (stable)
Distribution : vividpup - beta2
-Current Session-
Computer Name : puppypc899
User Name : root (root)
Home Directory : /root
Desktop Environment : Unknown (Window Manager: JWM)
-Misc-
Uptime : 18 minutes
Load Average : 0.40, 0.31, 0.24
- Attachments
-
- Vivid Beta.jpg
- (94.16 KiB) Downloaded 938 times
vividpup beta
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.
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.
- Attachments
-
- screenshot.jpg
- (73.41 KiB) Downloaded 879 times
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.
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.
Re: Full Vivid Beta
i'm getting a fail with full install as well ..... maybe kernel related ... try one of tahrs & read the readme http://ftp.nluug.nl/ibiblio/distributio ... r/kernels/davids45 wrote: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.
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Re: Vivid
the main reason for this is that CPU frequency is set to 'performance' as default ..... usually it's set to 'on demand' in other pups.sszindian wrote:without doubt the most-responsive of any of the new Puppy's I've tested to date!
>>>---Indian------>
menu>>system>>CPU frequency scaling tool ...set to 'performance' in other pups for extra speed
the new kernel will give a boost on some setups as well
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Re: Full Vivid Beta
I was intending to confirm but my full install is working without any apparent problems.666philb wrote:i'm getting a fail with full install as well ..... maybe kernel related ... try one of tahrs & read the readme http://ftp.nluug.nl/ibiblio/distributio ... r/kernels/davids45 wrote: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.
From my running Vivid Beta 2 frugal install in sdb8 I used the installer (Vivid files in a directory) to do a full install in sdb 13. Booting from legacy Grub in sda3 using the default menu.lst entry.
Been tweaking and rebooting.more tweaking and rebooting...rebooted 7 or 8 times with no delays and no problems.
I did start with sdb 13 already formatted to ext4 and did not install grub4dos.
HTH.
EDIT:Doing a complete poweroff now to see if any difference.
Rebooted and powered off this full install at least 10 times....zero problems.
Some variable must be causing the problems but not present on this old box.
Just for info purposes
Code: Select all
PUPMODE=2
#ATADRIVES is all internal ide/pata/sata drives, excluding optical, excluding usb...
ATADRIVES='sda sdb '
#ATAOPTICALDRIVES is list of non-usb optical drives...
ATAOPTICALDRIVES='sr0 '
PUP_HOME='/'
PDEV1='sdb13'
DEV1FS='ext4'
Code: Select all
root# report-video
VIDEO REPORT: vividpup, version beta2
Chip description:
VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
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: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
Code: Select all
root# free
total used free shared buffers
Mem: 2056452 467072 1589380 70180 11868
-/+ buffers: 455204 1601248
Swap: 2150396 0 2150396
root#
Code: Select all
-Computer-
Processor : 2x Intel(R) Pentium(R) 4 CPU 3.00GHz
Memory : 2056MB (174MB used)
Machine Type : Physical machine
Operating System : vividpup - beta2
User Name : root (root)
Date/Time : Thu 30 Apr 2015 04:50:01 PM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G x86/MMX/SSE2
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ICH4 - Intel ICH5
Audio Adapter : PC-Speaker - pcsp
Just for info purposes
Code: Select all
title Puppy Linux beta2 full install in sdb13
root (hd1,12)
kernel /boot/vmlinuz root=/dev/sdb13 pmedia=atahd
Latest Google Chrome works fine on Vivid Beta too.
- Attachments
-
- latest Chrome.jpg
- (12.28 KiB) Downloaded 713 times
cheers james CJames C wrote:Latest Google Chrome works fine on Vivid Beta too.
does cups still work after installing the .deb?
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Cups interface is showing up in Palemoon but nothing appearing in Chrome.666philb wrote:cheers james CJames C wrote:Latest Google Chrome works fine on Vivid Beta too.
does cups still work after installing the .deb?
Didn't install a ,deb. Downloaded and extracted manually if that could make a difference..No ink in printer though.
- Attachments
-
- cups.jpg
- (51.59 KiB) Downloaded 735 times
installing the deb breaks some cups permissions but there's supposed to be a fix
does cups work after installing the .deb?
does cups work after installing the .deb?
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
I'll reinstall Chrome with the deb in a minute but as a test cups is working at the moment with my self-extracted Chrome.Was able to print a test page.666philb wrote:installing the deb breaks some cups permissions but there's supposed to be a fix
does cups work after installing the .deb?
Back in a bit.
- Attachments
-
- printer.jpg
- (65.99 KiB) Downloaded 1450 times
Installed Chrome with the deb direct from Google. Reran cups. Printer detected. Successfully printed test page.
Still on the full install by the way.
Still on the full install by the way.
- Attachments
-
- working.jpg
- (71.97 KiB) Downloaded 1504 times
Full Vivid booting - now OK?
G'day James C,
Thanks for posting your Full Vivid has not had a booting issue - your post's psychic resonance seems to have also fixed my Full's odd booting .
Of course, now that I post it is OK, it will probably misbehave on next boot .
David S.
Thanks for posting your Full Vivid has not had a booting issue - your post's psychic resonance seems to have also fixed my Full's odd booting .
Of course, now that I post it is OK, it will probably misbehave on next boot .
David S.
new background.
- Attachments
-
- vividm2.jpg
- https://www.mediafire.com/folder/x4v77bi1p58ox/puppy2013
- (32.04 KiB) Downloaded 1252 times