Dpup Wheezy. Woof-CE built debian wheezy 7.2 packages used

[musher0]

I have hunted the scripts with "set -x" inside. In /etc/acpi several scripts had it.
Okay...removing "set -x" from those scripts removes a lot "noise" from /tmp/xerrs.log.

I will go through all scripts now with search functions.

Yes, similar to set -ex, the diagnostics mode. Excellent find!
That will certainly help. (Although that is one reason why WheezyPup is so stable: you conducted good diagnostics before the release.)

Bye for now.

musher0

[musher0]

Okay. I hunted most left over "set -x" debugging command included scripts. Not many....but at least those /etc/acpi scripts produce quite a lot verbose messages which accumulate to the xerrs.log. They are not errors, but disabling that "noise" cleans xerrs.log a lot.

I noticed that libpoppler was left out. It was due to my experimenting pdf readerless build. Using Firefox inbuild pdfreader. But....Cups...Abiword...LibreOffice....heaven knows what else needs it. You cant live without poppler...if you want to print.

I will create 3.5.2.7 version this evening and upload it.

Hi, pemasu.

Just upload the library. You are too dedicated! Your head is in the clouds because of your neighbors, remember?

m0

[musher0]

Besides, pfind says that poppler is there :

• /usr/include/poppler
  /usr/include/poppler/glib/poppler-action.h
  /usr/include/poppler/glib/poppler-annot.h
  /usr/include/poppler/glib/poppler-attachment.h
  /usr/include/poppler/glib/poppler-date.h
  /usr/include/poppler/glib/poppler-document.h
  /usr/include/poppler/glib/poppler-enums.h
  /usr/include/poppler/glib/poppler-features.h
  /usr/include/poppler/glib/poppler-form-field.h
  /usr/include/poppler/glib/poppler.h
  /usr/include/poppler/glib/poppler-layer.h
  /usr/include/poppler/glib/poppler-media.h
  /usr/include/poppler/glib/poppler-movie.h
  /usr/include/poppler/glib/poppler-page.h
  /usr/lib/libpoppler.a
  /usr/lib/libpoppler-glib.a
  /usr/lib/libpoppler-glib.so
  /usr/lib/libpoppler-glib.so.4
  /usr/lib/libpoppler-glib.so.5
  /usr/lib/libpoppler-glib.so.6
  /usr/lib/libpoppler-glib.so.8
  /usr/lib/libpoppler-glib.so.8.2.0
  /usr/lib/libpoppler.so
  /usr/lib/libpoppler.so.19
  /usr/lib/libpoppler.so.19.0.0
  /usr/lib/libpoppler.so.4
  /usr/lib/libpoppler.so.7
  /usr/lib/pkgconfig/poppler-cairo.pc
  /usr/lib/pkgconfig/poppler-glib.pc
  /usr/lib/pkgconfig/poppler.pc
  /usr/lib/pkgconfig/poppler-splash.pc
  /usr/share/gir-1.0/Poppler-0.18.gir
  /usr/share/gtk-doc/html/poppler
  /usr/share/vala-0.14/vapi/poppler-glib.deps
  /usr/share/vala-0.14/vapi/poppler-glib.vapi

[don570]

I compiled mhwaveedit 1.4.21 in wheezy so that it recognizes
ladspa effects

I added a useful config file.

http://www1.datafilehost.com/d/9c29fb40

and here are the locales

http://www1.datafilehost.com/d/716139e8

_________________________________________________

[pemasu]

Thanks don570. I uploaded them to the repo.

[anikin]

A quick question: the power applet in the tray that shows 'powersave', 'performance' and 'turbo'. What its official name, or is it part of laptop tools? Does it have a source and is it compilable?

Thank you in advance.

[pemasu]

It is called ppower. And it relies to the scripts in /etc/acpi. There is source for it.

http://www.smokey01.com/jemimah/saluki/ ... -01.tar.gz

[James C]

Temporarily have an internet connection so........live pfix=ram.....

# report-video
VIDEO REPORT: Dpup Wheezy, version 3.5.2.6

Chip description:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200G Series]
Display controller: Advanced Micro Devices [AMD] nee ATI Radeon Xpress Series (RS480)

Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Drivers requested to be loaded: radeon

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): radeon
Loaded modules: dbe dri dri2 exa extmod fb glx kbd mouse ramdac record

Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes

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

Booted to a prompt,ran xorgwizard and selected "radeon" with correct 1024x768 resolution.

-Computer-
Processor : AMD Athlon(tm) 64 Processor 3400+
Memory : 967MB (111MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Sun 12 May 2013 03:48:08 AM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ATIIXP - ATI IXP

Code: Select all

Multimedia audio controller		: Advanced Micro Devices [AMD] nee ATI IXP SB400 AC'97 Audio Controller 
VGA compatible controller		: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200G Series] 
Display controller		: Advanced Micro Devices [AMD] nee ATI Radeon Xpress Series 
Ethernet controller		: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express 

EDIT:

At the prompt after selecting xorgwizard I was given a choice between "modesetting", "radeon" and "vesa" drivers. Naturally I selected the correct "radeon".

EDIT 2:
Linked to Barry K's blog.

[pemasu]

Dpup Wheezy 3.5.2.7 has been uploaded.

Small fixes mostly. Less "noice" in /tmp/xerrs.log.
I compiled Evince for fast pdf viewing. It is now the default pdf reader.
Some finetuning for font outlook. In bad or good.

Download link : http://www.smokey01.com/pemasu/DpupWhee ... heezy3527/


If people compile useful applications, I can upload them to the repo from temporary host:
http://www.smokey01.com/pemasu/pet_packages-wheezy/

[OscarTalks]

Pemasu,
You may wish to consider adding my Linphone to the repo. It is smaller than the Debian version and has all the extra codecs added. The sign-in wizard works too.

http://www.murga-linux.com/puppy/viewtopic.php?t=79803

[OscarTalks]

I am trying to produce a .PET of the latest NVIDIA legacy driver 173.14.37 for Dpup Wheezy and it all seems to work OK. I am just a little unsure about the post-install and post-uninstall processes.

On my nvidia GeForce FX 5200 computer, the only driver that loads (without tinkering) is nouveau. The nvidia .pet includes the .conf file that disables nouveau (which must be done) so after installation on reboot there is no driver to produce a desktop.

I have to type "xorgwizard" from prompt then select the nvidia driver (and a resolution) and then type "xwin" to get my desktop with the working nvidia driver. Not a major problem, these instructions appear in the prompt dialog, and hopefully it is something you would only have to do once.

Uninstallation restores the nouveau driver and old xorg.conf file, but again requires typing "rmmod nvidia" in prompt screen (or does it?). There is no nv driver so no need to try to restore that.

I have put pop-up messages in which explain and guide the user through this, but maybe someone knows of a smoother way of doing things. Can we avoid reboots or the need to type in prompt screen?

I'm not certain the xorgwizard is completely recognising all the right combinations of disabling drivers and/or rebooting.

Is there some other way to test acceleration / FPS without glxgears?

Nvidia 173.14.37 k3.5.2.Wheezy .pet
download = http://www1.datafilehost.com/d/e4013200
md5sum = a7204548b94b327009f824a4debaf159

[pemasu]

Thank you OscarTalks. I have uploaded both of your posts suggested packages.

About pinstall.sh and postinstall.sh scripts. I think you get good idea what people have done before by downloading previous pets and check the contents. I suppose 01micko`s repos for Slacko is good library for studying. I dont have nvidia graphics so I cant recommend much.

I remember that Shinobar placed large postinstall script to the /root/Startup but I dont remember what it dit. Extracting those pets and checking would be the method I would use.

[Satori]

With the release of the 'official' debian 7 and your Dpup Wheezy use of it, I made the change-over for my personal production machines, which were using Dpup Squeeze.

There were no problems with installing the NVidia 319.17 drivers and all went well.

Chrome 26.0 is now able to run but I found that the youtube audio was extremely choppy and really annoying... after googling around, I found that the fix was to add a parameter
to the startup execution, of "--audio-buffer-size=2048". Apparently, this is a known problem for version 26, and now the sound is very smooth.

I see that there is no longer a cpu temperature on the system tray, and that the 'temptray' application from the repositories fails to start. For laptops, it's a neccessary tool.

I would like to see 'GTK-Youtube-Viewer" running under DPup Wheezy, but there seems to be a conflict that prevents it from starting.

The other applications I use, make heavy usage of OpenGL and the apps run pretty well. Altho one older app now fails with a GTK2.pm error, but the newer versions run ok.
I guess that's just progress for you.

Aside from the above minor wish list, I'm pretty happy with this distribution and feel confident that it will support the newer applications that will be coming down the line,
in the near future.

Thanks for your work.

[pemasu]

Thanks Satori. I add your find audio fix to the Chrome 26 postinstallation hack.
I tested google-chrome 26 and you were right. Hotel California sound was choppy. The fix was needed.

Gtk-youtube-viewer would be a bigger thing to get it working. It will need manual messing with perl .pm files. To add missing perl scripts to the package. I wont promise it soon, lol.

Here is working tempicon tray app as attachment. I have left some temp apps out to diminish memory usage. People with desktop comps usually dont need the temp info.

[pemasu]

gtk_youtube_viewer-3.0.2_precise.pet does work in Dpup Wheezy if you have devx sfs loaded. I havent tested it without devx sfs.

http://uploadingit.com/file/t2jhxvvneea ... recise.pet

[anikin]

Hi pemasu,
fresh, first run.
Boot is OK, quick setup ... and I notice that sda1 is mounted. That's exclusively winxp territory and it's never been intruded (mounted on boot) before. All my puppies are on sdc1. Once the quick setup is done, sda1 magically unmounts itself.

Thank you very much for ppower. I'd like two things with it: 1) remove turbo mode from source. 2) compile and install it in another puppy (with acpi scripts from wheezy). I almost figured out how the turbo mode is invoked.

[pemasu]

Boot is OK, quick setup ... and I notice that sda1 is mounted.

I believe it is due to new fail safe graphics feature. /usr/sbin/quickset has new feature to save pupdesk.flg file, starting from this row:

Code: Select all

 #130509 need to create pupdesk.flg before bring up gui window, with $XDRIVERSUCCESS stored in it, for xorgwizard-cli...

It might be that it creates that file somewhere from where to access it if hard reboot is needed. So the failed boot to desktop will be registered and at next boot the failsafe xorgwizard-cli will be launched without booting to the X and you can choose the graphics driver.

[anikin]

Well, I don't mind pupdesk.flg being created in a partition where puppy resides. But I do very much mind my other partitions being sniffed in the process.

[pemasu]

Anikin. you should post about the feature to Barry`s blog.

Here is the snapshot of the desktop when the sda1 is mounted and the failsafe file has been created.

I believe that the failsafe feature is still under progress. Feedback would be noted by Barry K surely.

http://i.imgur.com/xLmN8G7.jpg

[01micko]

Well, I don't mind pupdesk.flg being created in a partition where puppy resides. But I do very much mind my other partitions being sniffed in the process.

I tend to agree. It is a good idea but should ask the user if it's ok to make the file, especially for ntfs/fat. I won't be producing a pup with that enabled.
This is of course just my opinion and I will post to BK's blog.

Cheers