Dpup Wheezy. Woof-CE built debian wheezy 7.2 packages used
Hi.
Hopefully, this is not a repeat of someone else's post.
I get a long description of my video card at the top of my xerrs.log file (see attached). Why is it there? Is it an error?
Also, it seems that I am running a 64-bit WheezyPup on a 32-bit machine? How is this possible?
xerrs.log, generally, is scraping up a lot of non-errors as well as errors.
For example, errors concerning older gtk themes that work perfectly.
Which makes you want to debug your Puppy, of course, even if some things do not need to be de-bugged.
Obviously, one could save a lot of time NOT trying to debug NON-errors.
Also obvious: a big error file is not good for Puppy's reputation among new users.
Not to mention that some Puppy-ists with not enough knowledge about Puppy will jump on your code and on your back saying "haha, you committed errors", when maybe there are none.
So, this xerrs.log thing is a human relations and image thing as well as a technical thing. In any case...
I'd be grateful for any clarification. Thanks in advance.
musher0
PS. There is no need to answer the part about the presence in xerrs.log of the report-video in French. I asked don570 already, since he is the author.
Hopefully, this is not a repeat of someone else's post.
I get a long description of my video card at the top of my xerrs.log file (see attached). Why is it there? Is it an error?
Also, it seems that I am running a 64-bit WheezyPup on a 32-bit machine? How is this possible?
xerrs.log, generally, is scraping up a lot of non-errors as well as errors.
For example, errors concerning older gtk themes that work perfectly.
Which makes you want to debug your Puppy, of course, even if some things do not need to be de-bugged.
Obviously, one could save a lot of time NOT trying to debug NON-errors.
Also obvious: a big error file is not good for Puppy's reputation among new users.
Not to mention that some Puppy-ists with not enough knowledge about Puppy will jump on your code and on your back saying "haha, you committed errors", when maybe there are none.
So, this xerrs.log thing is a human relations and image thing as well as a technical thing. In any case...
I'd be grateful for any clarification. Thanks in advance.
musher0
PS. There is no need to answer the part about the presence in xerrs.log of the report-video in French. I asked don570 already, since he is the author.
- Attachments
-
- xerrs.log.zip
- (2.12 KiB) Downloaded 240 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I get the usual xerrs.log report about xorg and graphics. I havent hacked any of woof2 scripts to provide more reports. The kernel has the usual verbosity lowering patch and so on...I get a long description of my video card at the top of my xerrs.log file (see attached). Why is it there? Is it an error?
Because Dpup Wheezy is 32 bit build. So it do run fine in 32-bit machine.Also, am I running a 64-bit WheezyPup on a 32-bit machine? How is this possible?
None of that is my doing. I havent added any extra error reporting. It comes to individual apps and scripts how they do suppress the verbose reporting.It seems that xerrs.log, generally, is scraping up a lot of non-errors as well as errors. Which makes you want to debug your Puppy, of course, even if some things do not need to be de-bugged.
I concur. Do you have a suggestion how to accomplish this. I am more or less stressed if some repetitive error pollutes the xerrs.log so that it growths to several Mb`s in size.Obviously, one could save a lot of time NOT trying to debug NON-errors.
Also obvious: a big error file is not good for Puppy's reputation among new users.
I have now uptime over 6 hours and xerrs.log is 5438 bytes....not kilobytes or megabytes. So....I am not stressed.
And thank you of the feedback. It sounds like you got the Dpup Wheezy booting to the desktop.
My neighbor had hell of the party last night lasting to the 9.00 am. I have slept 3 hours last night (not participating but listening the tremendous noice). I dont have my usual tolerance today....so forget what I post today.....I am also filling tax papers even though my head is full of smoke and haze.
Hi pemasu, here's some more stress to you, have a look at it at your convenience.
Fresh boot, pfix=ram, upgarded flash via flashget, below is my xerrs log: strange that it's trying to open "libvdpau_nvidia.so" - this eeepc doesn't have nvidia, it's Intel based. Why icewm menu is being updated? Why there's an icewm folder in the root directory, I'm quite happy with jwm.
Fresh boot, pfix=ram, upgarded flash via flashget, below is my xerrs log: strange that it's trying to open "libvdpau_nvidia.so" - this eeepc doesn't have nvidia, it's Intel based. Why icewm menu is being updated? Why there's an icewm folder in the root directory, I'm quite happy with jwm.
Code: Select all
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian
Current Operating System: Linux puppypc14648 3.5.2-dpup #1 SMP Mon Aug 20 20:32:41 AST 2012 i686
Kernel command line: video=640x480 psubdir=Wheezy3526 pmedia=usbflash pfix=ram nosmp
Build Date: 17 April 2013 11:13:16AM
xorg-server 2:1.12.4-6 (Julien Cristau <jcristau@debian.org>)
Current version of pixman: 0.26.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat May 11 13:31:39 2013
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module fbcon not found.
ls: cannot access /root/.pup_event: No such file or directory
/usr/bin/jwm
cat: /root/.packages/user-installed-packages: No such file or directory
/usr/sbin/quicksetup: line 878: 11751 Terminated yaf-splash -bg orange -fg black -placement center -close never -fontsize large -icon /usr/share/doc/puppylogo96.png -text "$WELCOMEMSG"
/usr/sbin/quicksetup: line 1512: 13362 Terminated yaf-splash -bg orange -close never -fontsize large -text "$(gettext 'Processing, please wait...')"
/usr/sbin/delayedrun: line 193: welcome1stboot: command not found
Playing Sparc Audio '/usr/share/audio/2barks.au' : Mu-Law, Rate 8000 Hz, Mono
killall: acpid: no process killed
++ cat /etc/acpi/turbo-brightness
+ BRIGHT=9
+ echo 9
/etc/acpi/turbo.sh: line 6: /sys/class/backlight/acpi_video0/brightness: No such file or directory
+ which acpitool
/usr/bin/acpitool
+ [[ 0 != 0 ]]
+ cpufreq-set -g performance -c0
+ cpufreq-set -g performance -c1
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
+ cpufreq-set -g performance -c2
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
+ cpufreq-set -g performance -c3
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
+ echo turbo
EXIT="Exit on timeout"
VIDEO REPORT: Dpup Wheezy, version 3.5.2.6 Chip description: VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Requested by /etc/X11/xorg.conf: Resolution (widthxheight, in pixels): 1024x600 Depth (bits, or planes): 24 Modules requested to be loaded: synaptics dbe Probing Xorg startup log file (/var/log/Xorg.0.log): Driver loaded (and currently in use): intel Loaded modules: dbe dri dri2 extmod fb fbdevhw glx kbd mouse record synaptics Actual rendering on monitor: Resolution: 1024x600 pixels (270x158 millimeters) Depth: 24 planes ...the above also recorded in /tmp/report-video
+ gtkdialog-splash -timeout 3 -placement top -bg lightblue -text 'Switching to Low Power Mode'
EXIT="Exit on timeout"
++ cat /etc/acpi/powersave-brightness
+ BRIGHT=9
+ echo 9
/etc/acpi/powersave.sh: line 7: /sys/class/backlight/acpi_video0/brightness: No such file or directory
++ tr -d :
++ cut -f3 '-d '
++ tail -n 1
++ grep 'analyzing CPU'
++ cpufreq-info
+ CPUS=0
++ eval echo '{0..0}'
+++ echo 0
+ for i in '$(eval echo {0..${CPUS}})'
+ cpufreq-set -g powersave -c0
+ echo powersave
cat: /sys/class/power_supply/BAT0/model_name: No such file or directory
/usr/sbin/petget: line 350: kill: (16411) - No such process
(firefox:23799): GLib-GIO-WARNING **: Failed to execute child process "update-desktop-database" (No such file or directory)
x="1"
y="2"
EXIT="done"
EXIT="OK"
[H[2JEXIT="ok"
http://fpdownload.macromedia.com/get/flashplayer/pdc/11.2.202.280/install_flash_player_11_linux.i386.tar.gz
NEWVERSION=11.2.202.280
/usr/sbin/getflash: line 39: 5215 Terminated LANG=$LANG_USER gtkdialog-splash -fontsize "large" -icon $MYICON --placement center -bg $BGCOLOR -timeout $TIMEOUT -close never -text "$@"
Generating /root/.icewm/menu...
Generating /root/.jwmrc...
/usr/sbin/getflash: line 39: 5701 Terminated LANG=$LANG_USER gtkdialog-splash -fontsize "large" -icon $MYICON --placement center -bg $BGCOLOR -timeout $TIMEOUT -close never -text "$@" (wd: /usr/lib/mozilla/plugins)
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Thanks pemasu for taking the time for feedback and info. (For the other problem: will some aspirin work?)
Yes, I boot to the desktop, and everything else is fine in WheezyPup. As I said previously, WheezyPup 3.5.2.5 is the most stable Puppy since Puppy 4.31 adn dpup 4.84, IMO.
Thanks anikin for re-assuring me that there is "more than one person in the bathtub" ! The more we are in the bathtub, the less we are likely to drown! (Sarcastic proverb in my country)
I get mostly the same thing as you in my xerrs.log.
Three cheers for errors real and imagined !
musher0
Yes, I boot to the desktop, and everything else is fine in WheezyPup. As I said previously, WheezyPup 3.5.2.5 is the most stable Puppy since Puppy 4.31 adn dpup 4.84, IMO.
Thanks anikin for re-assuring me that there is "more than one person in the bathtub" ! The more we are in the bathtub, the less we are likely to drown! (Sarcastic proverb in my country)
I get mostly the same thing as you in my xerrs.log.
Three cheers for errors real and imagined !
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hello, again.
(excerpt from my grub4dos)
With this little extra command, the xerrs.log starts at 3883 bytes instead of the double.
Thanks again for your orientation.
musher0
One suggestion is to insert the word "quiet" just after vmlinuz in the boot command. Like this:pemasu wrote:(...) Do you have a suggestion how to accomplish this. I am more or less stressed if some repetitive error pollutes the xerrs.log so that it growths to several Mb`s in size.
I have now uptime over 6 hours and xerrs.log is 5438 bytes....not kilobytes or megabytes. So....I am not stressed.
Code: Select all
title Wheezy 3.5.2.5
root (hd1,1)
kernel (hd1,1)/wheezypup/lancement/vmlinuz quiet pmedia=satahd root=/dev/ram0 pdev1=sda2 psubdir=wheezypup psave=chr130213.2fs max_loop=14 ramdisk_size=192000
initrd (hd1,1)/wheezypup/lancement/initrd.gz
boot
With this little extra command, the xerrs.log starts at 3883 bytes instead of the double.
Thanks again for your orientation.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
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.
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.
Yes, similar to set -ex, the diagnostics mode. Excellent find!pemasu wrote: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.
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
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hi, pemasu.pemasu wrote: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.
Just upload the library. You are too dedicated! Your head is in the clouds because of your neighbors, remember?
m0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
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
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
mhwaveedit 1.4.21
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
_________________________________________________
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
_________________________________________________
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
http://www.smokey01.com/jemimah/saluki/ ... -01.tar.gz
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
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.
# 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
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.
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/
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
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
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
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
Oscar in England