(old)Puppy Linux Discussion Forum

Artsown. Rerwin created first test pet. It has solution to turn off wireless automatic power saving property...if the solution works. Install the pet and reboot. Of course disable your solutions first. Please, post feedback here.

Also pdiag tarball posted here might help. If it works or not.

Pemasu, on sqeeze I removed the line that does my fix, then installed the
Pet and rebooted. Frisbee took a long time to connect and wlan0 power
management was ON instead of OFF. Second reboot the same. On the
third, Frisbee couldn't establish a connection, presumably because pwr
mgmt is ON instead of OFF.

Remember that on squeeze I had to move my fix to later in the startup
sequence than usual, I placed it after the sleep 5 line in Frisbee_tray
in the /root/startup group.

Sorry, I forgot the tarball and I'm not in sqeeze right now. Let me know
if you or rerwin need it.

Also, I wonder is his Pet is ok to try on Slacko 5.4? It might be interesting
to see if it works there but not on squeeze.

Art

Artsown. It would help if you test this pet in all problematic puppy distros. This pet is just first trial to find generic solution. And pdiag or pmodemdiag tar balls would help. Pdiag is more sophisticated, if you copy it from squeeze puppy.

In console: which pdiag and you find out where it is.

Pemasu, here's the result of pmodemdiag in squeeze. The console reported there is no pdiag.

Pemasu, here's the pmodemdiag result fpr Slacko 5.4 which also
starts up with power management ON for wlan0 and which also
has no pdiag.

Pemasu, here's pmodemdiag result for Precise 5.4.3
Precise also start up with pwr mgnt ON and the Pet
installed.

Artsown. Yes, the syntax in the /etc/network/if-up.d/wifi_disable_power_management file: does not reach wlan0

If I run that command in console, I get error.

If I run in console: iwconfig wlan0 power off, power management will be disabled in my wireless chip.

Heh. Next trial for rt2500pci wlan power sawing disabling.

I created a new Startup script that tests for a certain message ("wlan0: RX AssocResp from 00:12:17:49:03:56 (capab=0x411 status=0 aid=3)") to obtain the interface ID. That may not be the only message associated with the problem -- or it may be only a coincidence. But I have to start somewhere.

If users with different problematic drivers need the fix, I would need to see their pmodemdiag to look for signature messages, if any. If a message test is not adequate, we could put the script in the "firmware tarball/directory" for particular drivers. But let's try the easier approach first, in case it is sufficient.

Here is this version for Artsown to test. The script was quite hitech to me. I hope it works.

pemasu, the tarball was done in Slacko 5.4. Power management
on wlan0 is ON after installing the pet and rebooting.

Aty

Artsown. Oh well. I believe Rerwin follows this thread and sees the result. The right syntax is still under development...as some sites announces...lol

pemasu, I don't understand the logic of testing to see if wlan0 power
management is ON or OFF. It's ON by default on all Pups I've looked
at lately, including 5.2.8 Lucid on a 2.X kernel which has never given me
any wireless problem. The wireless bug began to appear when 3.X
kernel use started. Racy 5.3.9 with 3.0.25 kernel has the bug. Slacko
5.3.1 on a 2.X kernel does not have the problem but 5.3.3 on 3.1.10
kernel does.

Art

Artsown. These scripts try to determine the need to power off the wlan. And it should power it off. The purpose is trying to find a little more clever generic script to power off wlan power saving feature.

It just looks like these scripts just does not achieve the goal

But...even though you told the power saving is on...the kernel messages tell this:
Feb 5 19:19:23 puppypc10806 user.notice wifi_disable_power_saving: wlan0: power saving disabled to stabilize connections

Are you sure the iwconfig tells that Power Management is On ?

Pemasu, yes I'm sure. In fact, Slacko lost connection, presumably
due to have it ON. But I'll try it again to make double sure.

Art

Pemasu, tried it again and same thing. Wlan0 power management is
ON at startup with the second pet installed.

Art

Zigbert has fixed the bug in pburn that caused a pipe error
when using pburn in Exprimo

http://murga-linux.com/puppy/viewtopic. ... 520#682520

______________________________________________________

I have made the report-system version 2.9 compatible with Exprimo
and Wheezy.

The problem was incompatibility with command which works in most distros by Barry Kauler.

http://murga-linux.com/puppy/viewtopic. ... 787#682787

_______________________________________

Pemasu, I'd like to get your opinion on something. As I posted earlier in
this thread, your exprimo was unusual in that the usual fix for the
wireless bug didn't work. I had to place a fix in the startup group so
that power mgnt is turned off after X starts and not before. People have
written instructions to place the fix in /etc/rc.local which occurs before
X starts ... and this is what did not work in your exprimo.

What I did recently is create a text file having the single line:
iwconfig wlan0 power off
and then use permissions to make the file a executeable script which
I place in /root/startup This has worked on all pups tested so far. In
any event it's a improvement over the past instructions.

My question has to do with the best way of making this temporary fix
public. I don't want to advise people to download a script from me since
I'm not one of the so-called trusted sources (the malicious code issue).
So I'm inclined to write a instruction that even newbies should be able to
follow. It would be simpler for people though if someone like yourself
would create a pet that automatically copies the script to /root/startup
and also executes the script. Users would be advised to install the pet
prior to attempting to connect the first time and prior to any kind of
installation ... and that's all certain wireless users would have to do.

Art

Hello,
always happy of this Puppy, and always a newbie question.

Got now openbox and like to install "tint2_with_menu".
So I downloaded it (strangely the link is tint2_with_menu-0.11.gz, so I rename it tint2_with_menu-0.11.pet and that's right.

So, I go to ~/.config/tint2/ and open : tint2rc
write the line : wm_menu = 1 in place of
wm_menu = 0

but don't work.
what I did wrong ?

thanks to read me !

Been running 5.X.3.6.2.1 on this old P4 for quite a while with no problems.

# report-video
Report Video 1.4 - Sun 17 Feb 2013 on Dpup Exprimo 5.X.3.6.2.1 - Linux 3.6.2-dpup i686

Chip description:
2.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
oem: Intel(r)865G Graphics Chip Accelerated VGA BIOS
product: Intel(r)865G Graphics Controller Hardware Version 0.0

X Server: Xorg Driver used: intel

X.Org version: 1.7.7
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 16 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#


-Computer-
Processor : Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory : 2592MB (201MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Sun 17 Feb 2013 02:22:51 AM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH4 - Intel ICH5

Since Precise 372 doesn't like this box http://www.murga-linux.com/puppy/viewto ... 863#685863 I decided to try Exprimo 5.X.3.6.2.1. Working fine.
Internet and sound good on initial boot......booted to an incorrect 1400x1050 display but xorgwizard made it easy to get to the correct 1440x900 resolution.

# report-video
Report Video 1.4 - Tue 19 Feb 2013 on Dpup Exprimo 5.X.3.6.2.1 - Linux 3.6.2-dpup i686

Chip description:
d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev

X Server: Xorg Driver used: nv

X.Org version: 1.7.7
dimensions: 1440x900 pixels (402x251 millimeters)
depth of root window: 24 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#

-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 3373MB (207MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue 19 Feb 2013 03:39:36 AM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA NVidia