(old)Puppy Linux Discussion Forum

Posted: **Sat 10 Mar 2012, 18:28**

DaveS,

Here is the difference.

Working:

[   29.080057] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   29.171261] tg3 0000:02:00.0: irq 46 for MSI/MSI-X
[   31.146755] wlan0: deauthenticating from 00:1e:2a:ec:f3:aa by local choice (reason=3)
[   31.146919] wlan0: authenticate with 00:1e:2a:ec:f3:aa (try 1)
[   31.149240] wlan0: authenticated
[   31.149724] wlan0: associate with 00:1e:2a:ec:f3:aa (try 1)
[   31.152542] wlan0: RX AssocResp from 00:1e:2a:ec:f3:aa (capab=0x401 status=0 aid=5)
[   31.152551] wlan0: associated

Not working:

Code: Select all

 29.270074] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   29.270101] b43-phy0 ERROR: Initial Values Firmware file-format error.
[   29.270106] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[   29.285105] tg3 0000:02:00.0: irq 46 for MSI/MSI-X
[   30.546705] b43-phy0 ERROR: Microcode not responding
[   30.546710] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[   30.723379] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   30.723405] b43-phy0 ERROR: Initial Values Firmware file-format error.
[   30.723410] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[   57.586726] b43-phy0 ERROR: Microcode not responding
[   57.586736] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

I have no idea why it would sometimes find the firmware and sometimes not.

What are you doing to make it work vs not work?

EDIT: The one thing I did change that might have affected this is I installed Mavothal's fixed udev pet. I'll roll it back for the next release and see if your problem goes away.

Posted: **Sat 10 Mar 2012, 18:34**

don570 wrote:
Pfind is included in the base system.
...but do all the features work?? Zigbert says yes.

_____________________________________

It should be fine. The rox command opens thunar unless you install rox.

Posted: **Sat 10 Mar 2012, 18:46**

I tested scribus compile again. First I sfs_loaded devx sfs. Then your both Python-2.7.2 pets. Then all the rest pet packaged needed dependencies. I cooked scribus again and I made a pet of whole lot, not stripping and splitting. I made your Python as dependency to pet.specs...with the rest needed of course.
Reboot with fresh install. Podofo only installed first...it is not in saluki or wary5 repo. The I installed the scribus...it did find your Python-2.7.2 pet and installed it. In console scribus and....

Code: Select all

# scribus
scribus: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file or directory

They exist in devx sfs, I copied just them....

Code: Select all

# scribus
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback
Failed to set default encoding to utf-8.

Failed to import warnings module. Something is probably broken with your Python.
Traceback (most recent call last):
  File "<string>", line 2, in <module>
ImportError: No module named warnings

Oh well...it seems that the devx sfs python stuff interferes the compiling. Can I just delete those libpython2.6 lib and symlink...before I configure scribus for compiling...and would it help....your Python pets does not have similar libpython2.7 lib and symlink.

Posted: **Sat 10 Mar 2012, 18:52**

pemasu wrote:I tested scribus compile again. First I sfs_loaded devx sfs. Then your both Python-2.7.2 pets. Then all the rest pet packaged needed dependencies. I cooked scribus again and I made a pet of whole lot, not stripping and splitting. I made your Python as dependency to pet.specs...with the rest needed of course.
Reboot with fresh install. Podofo only installed first...it is not in saluki or wary5 repo. The I installed the scribus...it did find your Python-2.7.2 pet and installed it. In console scribus and....
Code: Select all
# scribus
scribus: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file or directory
They exist in devx sfs, I copied just them....
Code: Select all
# scribus
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback
Failed to set default encoding to utf-8.

Failed to import warnings module. Something is probably broken with your Python.
Traceback (most recent call last):
  File "<string>", line 2, in <module>
ImportError: No module named warnings
Oh well...it seems that the devx sfs python stuff interferes...

It should be linking against libpython2.7.a.

Try deleting libpython2.6.so*. Or I guess just wait until I post the updated devx for saluki-015.

Posted: **Sat 10 Mar 2012, 18:55**

I would like to wait your updated devx sfs and you would get good reason to update. I will compile scribus when the python has been unified. Win-win-situation.

Posted: **Sat 10 Mar 2012, 19:12**

Tribler - not working for me

I youst intall a fresh saluki 14 for tryng trlibler.

Tested few times on fresh install.
I attach a sceewnshot of the insallation of tribler.

Any suggestion to make tribler working?

(Al the best to jamiah - saluki seems very nice and faster than puppy528 and macup528 that i'm using)
Hrdwr - eepc 1215p atom 12"

Posted: **Sat 10 Mar 2012, 19:20**

Geoffrey wrote:
Tman wrote: I have created an Nvidia pet in Saluki-13.
I tried this with a 8600 GT, it gave me twice the frame rate 40000 in 5 seconds than did my manual install of the driver, but it was unstable and crashed the system, I tried twice to get it too work, but gave up in preference to a manual installation.

Geoffery, were you running glxgears when it crashed or were you running something else? Did you try installing the driver in a fresh savefile?
Hmmm.. I don't know what the problem could be. I compiled it on an AMD Athlon dual-core, and am wondering if it matters what cpu one compiles it on. I will do some experimenting to see if I can figure out the problem.

Posted: **Sat 10 Mar 2012, 20:23**

Sage wrote:
I don't tell xorg what resolution to pick. Automatic desktop means it's luck of the draw.
Thanks for putting that straight. Curious that it's not a problem with others? Any chance of a cheat code workaround? Or is there an HW fix? Newish (ie newer than Cirrus Logic!) nV cards would seem to be an issue? Think I've read similar problems previously that were eventually circumvented?
[Wales 24 Italy 3]
[Ireland 32 Scotland 14]

sage,

here is step by step install of puppy on old hardware including workaround pfix=nox

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

Posted: **Sat 10 Mar 2012, 20:59**

I installed Saluki 14 on a Pentium-4 about half and hour ago (no Nvidia card on this one).

The clock is an hour ahead, how to I change the time in xfce?

Unfortunately, I am still getting the following error message in Midori:

Code: Select all

MozPlugger: Error: Failed to execute m4.
Mozplugger: M4 parsing of config generated error

This error is repeatable with the following steps:
1) type midori in the console
2) in Midori's address bar, type murga linux forum and press enter
3) click on the appropriate link that takes you to the murga forum. For me, it was the 2nd link.

Installing Pemasu's mozplugger pet still doesn't resolve the issue. (thanks for trying, Pemasu)

On the positive side, Midori 0.4.4 does seem to be more stable; it hasn't crashed on me so far, and I just discovered that it handles HTML5..nice!!

Posted: **Sat 10 Mar 2012, 21:31**

firak wrote:Tribler - not working for me

I youst intall a fresh saluki 14 for tryng trlibler.

Tested few times on fresh install.
I attach a sceewnshot of the insallation of tribler.

Any suggestion to make tribler working?

(Al the best to jamiah - saluki seems very nice and faster than puppy528 and macup528 that i'm using)
Hrdwr - eepc 1215p atom 12"

I fixed a problem with the python pet. Please uninstall Python then install the new version from the PPM.

Posted: **Sat 10 Mar 2012, 21:34**

Tman wrote:I installed Saluki 14 on a Pentium-4 about half and hour ago (no Nvidia card on this one).

The clock is an hour ahead, how to I change the time in xfce?

Unfortunately, I am still getting the following error message in Midori:
Code: Select all
MozPlugger: Error: Failed to execute m4.
Mozplugger: M4 parsing of config generated error
This error is repeatable with the following steps:
1) type midori in the console
2) in Midori's address bar, type murga linux forum and press enter
3) click on the appropriate link that takes you to the murga forum. For me, it was the 2nd link.

Installing Pemasu's mozplugger pet still doesn't resolve the issue. (thanks for trying, Pemasu)

On the positive side, Midori 0.4.4 does seem to be more stable; it hasn't crashed on me so far, and I just discovered that it handles HTML5..nice!!

Do you get this with pfix=ram. I can't reproduce it. What happens if you run m4 in the terminal?

Posted: **Sat 10 Mar 2012, 21:52**

jemimah wrote: Do you get this with pfix=ram. I can't reproduce it. What happens if you run m4 in the terminal?

Yes, it happens for me in pfix=ram mode as well.
My frugals pups are installed in a linux partition, not an ntfs partition. This one is using a .2fs saved file.

When I type m4 in the terminal, I get

Code: Select all

bash: m4: command not found.

Nevermind about the clock settings..I figured out how to change the time.

I should add that when I ran the benchmark test on the following site, Saluki froze and I could not even quit using CTRL-ALT-BACKSPACE..
http://peacekeeper.futuremark.com/

Posted: **Sat 10 Mar 2012, 22:18**

Tman wrote: I should add that when I ran the benchmark test on the following site, Saluki froze and I could not even quit using CTRL-ALT-BACKSPACE..
http://peacekeeper.futuremark.com/

Here's firefox 11 beta7 running in Saluki

Posted: **Sat 10 Mar 2012, 22:34**

Thanks Billtoo,

I should have mentioned that I was trying to do the browser benchmark test in Midori.

I have now deleted Saluki frugal install and created a full-install on an ext3 filesystem. The benchmark still froze, but I could eventually get out of it this time.

Posted: **Sat 10 Mar 2012, 22:43**

With the understanding that hardware plays a big part in the Peacekeeper score, and because I'm bored, SeaMonkey 2.72/Saluki 014 on the old p4.

Posted: **Sat 10 Mar 2012, 22:45**

Maybe it froze for me becuase my glxgears numbers are so low.

Code: Select all

371 frames in 5.0 seconds = 74.057 FPS
375 frames in 5.0 seconds = 75.000 FPS
375 frames in 5.0 seconds = 75.000 FPS
375 frames in 5.0 seconds = 74.998 FPS

I will search the repo for an xorg-high or mesa pet and try again if I find it.

Posted: **Sat 10 Mar 2012, 22:51**

Or benchmark with something else than Midori.

Posted: **Sat 10 Mar 2012, 22:56**

Firefox 7.0.1 benchmarks fine in Saluki without additional video drivers.
I wanted to do the test in Midori becuase I wanted to compare the results with other browsers...ah well.

Posted: **Sat 10 Mar 2012, 22:59**

Tman wrote:
Geoffrey wrote:
Tman wrote: I have created an Nvidia pet in Saluki-13.
I tried this with a 8600 GT, it gave me twice the frame rate 40000 in 5 seconds than did my manual install of the driver, but it was unstable and crashed the system, I tried twice to get it too work, but gave up in preference to a manual installation.
Geoffery, were you running glxgears when it crashed or were you running something else? Did you try installing the driver in a fresh savefile?
Hmmm.. I don't know what the problem could be. I compiled it on an AMD Athlon dual-core, and am wondering if it matters what cpu one compiles it on. I will do some experimenting to see if I can figure out the problem.

Tman,

Yeah, it was a fresh install, glxgears wasn't running at the time, I have compiz and cairo dock working, when it froze I was moving a compiz wobbly window and turning the power off was the only option left for me.

I'm now using NVIDIA-Linux-x86-209.10.run, I will have to try 209.20 manually installed, a friend of mine tried the pet, but his experience with it was a slower frame rate than he previously had

,
a manual install of NVIDIA-Linux-x86-209.20.run yield a frame rate better than Ubuntu could offer while running WoW in Wine 1.4, strange.

Oh the difference when I do a install is I don't select nvidia in the xorgwizard choose, but when I installed the pet package I did, normally
I just probe select the res and xwin, this could be a factor, I'll test it some more, this time keeping a record of outcomes to compare.

Posted: **Sat 10 Mar 2012, 23:07**

Just tried Peacekeeper in Midori ...... got about halfway through before Saluki froze up. Running the Nvidia driver and fairly good numbers from glxgears.
Just for comparison purposes, just ran Peacekepper on Windows 7 and Chrome ....scored 2600.

(old)Puppy Linux Discussion Forum

Saluki

Tribler - not working for me

Re: Tribler - not working for me