Wary 0.9.2 (092) feedback
I am using playdayz Go Open Office 3.2.1 and it seems to be working fine.
I'll attach a full hardinfo report to see if anyone can spot any clues, but basically I am running an AMD X2 proccessor with an nforce chipset.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Oh yes, I compiled the very latest nvidia driver too, the one at the repo didn't work for me and was not recommended in the wizard.
See this post for the driver.
Cheers
I'll attach a full hardinfo report to see if anyone can spot any clues, but basically I am running an AMD X2 proccessor with an nforce chipset.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Oh yes, I compiled the very latest nvidia driver too, the one at the repo didn't work for me and was not recommended in the wizard.
See this post for the driver.
Cheers
- Attachments
-
- hardinfo_report.htm.gz
- (7.38 KiB) Downloaded 210 times
Puppy Linux Blog - contact me for access
OpenOffice crash on clean install but not on upgrade
I have done some more testing of the OpenOffice crash. Although OO crashes Wary on a clean install it does not crash on an upgrade using warysave.2fs from Wary 070.
Re: OpenOffice crash on clean install but not on upgrade
So it might be something to do with the way it creates (or not) its .config file. Will grab a .config from a working install and try it.Terryphi wrote:I have done some more testing of the OpenOffice crash. Although OO crashes Wary on a clean install it does not crash on an upgrade using warysave.2fs from Wary 070.
Spup Frugal HD and USB
Root forever!
Root forever!
Re: OpenOffice crash on clean install but not on upgrade
Nope! Still no go.....DaveS wrote:So it might be something to do with the way it creates (or not) its .config file. Will grab a .config from a working install and try it.Terryphi wrote:I have done some more testing of the OpenOffice crash. Although OO crashes Wary on a clean install it does not crash on an upgrade using warysave.2fs from Wary 070.
Spup Frugal HD and USB
Root forever!
Root forever!
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
It is now gone for puppies that are built from PET packages, which is Wary and Puppy 4.x (and earlier). PETs are usually already stripped to the basics, whereas packages from Debian and Ubuntu etc. usually have lots of fat that can be trimmed.L18L wrote:trim the fat button exists no more at all
In Wary, you will in the 'puppy-wary5' repo that there are lots of _DOC, _NLS and _DEV PET packages, which are the already-separated components of the original packages.
[url]https://bkhome.org/news/[/url]
That error is not the problem. I get it but OO continues to load successfully using my warysave.2fs from Wary 070.tronkel wrote:Both OpenOffice and LibreOffice crash on my system. Video card is ATI Radeon 3450.
Starting from a terminal, output is:
domainname: applet not found.
Have googled around for this but haven't found much. Sounds like a java problem though.
I think you may be close to the answer with Java. I had Java unchecked in my 070 warysave file so perhaps on upgrade OO did not look for it and therefore did not cause a crash.
I was about to try that having convinced myself that the lack of Java in 092 was the cause of the problem. Expletive!DaveS wrote:Tried it with java installed. No better....
I don't think it is a kernel issue if I can run OO with an old warysave. I'll try to figure out what I have in it that makes the difference. Library or library version maybe?
Yep, same here. Tried it with Java jre1.6.0_22. Definitely installed correctly for system-wide access using /etc/profile.
Also, I've been rummaging around in /initrd and finding all sorts of spurious .wh files and folders. Remember these critters from the past? They cause all sorts of problems.
Barry has been seeing problems with the layered file system recently and these "whiteout files" are perhaps connected with this.
But the likeliest source of the problem is the k2.6.34.6 kernel.
Maybe a kernel compile option is the way to go here.
More googling required.
Also, I've been rummaging around in /initrd and finding all sorts of spurious .wh files and folders. Remember these critters from the past? They cause all sorts of problems.
Barry has been seeing problems with the layered file system recently and these "whiteout files" are perhaps connected with this.
But the likeliest source of the problem is the k2.6.34.6 kernel.
Maybe a kernel compile option is the way to go here.
More googling required.
Life is too short to spend it in front of a computer
More thoughts on OO crashing.
As far as I remember, the 2.6.34 kernel version was the first to include built-in proprietary modules for both ATI and NVIDIA cards. Or did that actually start with 2.6.33? Anyway, I remember having serious video problems with a version of real Ubuntu Lucid using the 2.6.33 kernel. This problem then finally went away with k2.6.35. This might mean that the 2.6.34 kernel has a fundamental problem with these two included proprietary video modules.
So what's the best solution for Wary? k2.6.35 might be too new for older hardware. So how about going back to k2.6.32 for Wary 5. This seems to work well in Lucid for example, which shows no problem with Open/Libre/Office
As far as I remember, the 2.6.34 kernel version was the first to include built-in proprietary modules for both ATI and NVIDIA cards. Or did that actually start with 2.6.33? Anyway, I remember having serious video problems with a version of real Ubuntu Lucid using the 2.6.33 kernel. This problem then finally went away with k2.6.35. This might mean that the 2.6.34 kernel has a fundamental problem with these two included proprietary video modules.
So what's the best solution for Wary? k2.6.35 might be too new for older hardware. So how about going back to k2.6.32 for Wary 5. This seems to work well in Lucid for example, which shows no problem with Open/Libre/Office
Life is too short to spend it in front of a computer
Quirky works very well including OpenOffice with the '33 kernel.tronkel wrote:More thoughts on OO crashing.
As far as I remember, the 2.6.34 kernel version was the first to include built-in proprietary modules for both ATI and NVIDIA cards. Or did that actually start with 2.6.33? Anyway, I remember having serious video problems with a version of real Ubuntu Lucid using the 2.6.33 kernel. This problem then finally went away with k2.6.35. This might mean that the 2.6.34 kernel has a fundamental problem with these two included proprietary video modules.
So what's the best solution for Wary? k2.6.35 might be too new for older hardware. So how about going back to k2.6.32 for Wary 5. This seems to work well in Lucid for example, which shows no problem with Open/Libre/Office
Spup Frugal HD and USB
Root forever!
Root forever!
OO works with kernel 2.6.35.7!
Following my success with OO on Wary 092 I have revisited a clean install of Wary 090 kernel 2.6.35.7. Guess what? Add java-jre-6u20.pet before trying the OO sfs and then it does not crash. Yippee!
Wary 0.9.2 (092) feedback
I set up wary 092 kernel 2.6.34.6 on another 4gb usb drive and
installed the devx,kernel source sfs,and NVIDIA-Linux-x86-260.19.12.run file.
I compiled dbus-1.4.0.tar.gz and dbus-glib-0.88.tar.gz, then I compiled
seamonkey-2.0.9.source.tar.bz2 and a few other applications.
This is another pc that is not in the target group for Wary but it's
working well.
BIOS
Date 09/15/2009
Vendor American Megatrends Inc. (www.ami.com)
Version P01-A4
Board
Name RS780
Vendor Gateway
The drive icons don't line up properly when a new usb drive is
inserted, the new drive shows up in the lower left corner and overwrites the
drive icon that is already there.
Having fun, thanks
installed the devx,kernel source sfs,and NVIDIA-Linux-x86-260.19.12.run file.
I compiled dbus-1.4.0.tar.gz and dbus-glib-0.88.tar.gz, then I compiled
seamonkey-2.0.9.source.tar.bz2 and a few other applications.
This is another pc that is not in the target group for Wary but it's
working well.
BIOS
Date 09/15/2009
Vendor American Megatrends Inc. (www.ami.com)
Version P01-A4
Board
Name RS780
Vendor Gateway
The drive icons don't line up properly when a new usb drive is
inserted, the new drive shows up in the lower left corner and overwrites the
drive icon that is already there.
Having fun, thanks
- Attachments
-
- wary092scrn.jpg
- (185.54 KiB) Downloaded 342 times
Wary has been very stable and I've had no problem with LibreOffice crashing using LibreOffice_3.3.0_beta2.sfs4.sfs available here.
As indicated above, it may be the video card.
However, my printer will not print from Wary. Although it appears to install properly, it will not print from any application.
Jim
System: BFG NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart C5280 All-in-One
As indicated above, it may be the video card.
However, my printer will not print from Wary. Although it appears to install properly, it will not print from any application.
Jim
System: BFG NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart C5280 All-in-One
Agere modem driver problem - links ignored
It appears that depmod in kernel 2.6.34.5 ignores links within the module directory structure. Neither relative nor absolute links seem to work. The agrmodem variant that is found by depmod is the first in the output of an "ls" command, sorted alphanumerically.
Since this is how the kernel wants to operate, I don't think we should modify depmod to respect links to modules. My next idea is to dynamically rename the two agr modules to and from .ko and something else so that they don't look like modules. I was trying to avoid changing modules, which would result in their being copied to the pup_rw layer of the layered file system. Maybe that cannot be avoided.
I think that effect would be minimized if the 11c11040 variant is the default, and the changes would be made only for the 048 and 06 variants, each of which supports only two hardware IDs. (But, to extend this idea to the Intel 537 modules, two of them would be moved up to pup_rw, and they are huge. But only one if there is no "default" to change.)
I see that the full depmod command allows arguments specifying module names. That would be much faster than a full run, if I specify only the two agr modules.
In the meantime, peebee, go ahead and rename the 048 and 06 variants, by removing the ".ko" suffixes.
Richard
Since this is how the kernel wants to operate, I don't think we should modify depmod to respect links to modules. My next idea is to dynamically rename the two agr modules to and from .ko and something else so that they don't look like modules. I was trying to avoid changing modules, which would result in their being copied to the pup_rw layer of the layered file system. Maybe that cannot be avoided.
I think that effect would be minimized if the 11c11040 variant is the default, and the changes would be made only for the 048 and 06 variants, each of which supports only two hardware IDs. (But, to extend this idea to the Intel 537 modules, two of them would be moved up to pup_rw, and they are huge. But only one if there is no "default" to change.)
I see that the full depmod command allows arguments specifying module names. That would be much faster than a full run, if I specify only the two agr modules.
In the meantime, peebee, go ahead and rename the 048 and 06 variants, by removing the ".ko" suffixes.
Richard
What driver package are you using? I installed my Photosmart c4680 using the hpijs-3.10.6-dynppd.pet from here and it worked fine.Jim1911 wrote:However, my printer will not print from Wary. Although it appears to install properly, it will not print from any application.