Puppy Linux Discussion Forum

[tempestuous]

[dinky]

Hi Dougal, internal flash on the eeepc 701 seems to be consistent... I'll let you know about the other things. I'll try and post the kernel config file here so you can also look at it. I put a post on your 'updated hotpup' thread about the hotpupx version... problems with Puppy 4.1, are you able to fix them?

@tempestuous
great work! No issues at all in Puppy 4.1 with the wireless network for wep, haven't tried anything else. Didn't have to do anything in the bios. for the record, I like your post regaring the shutdown problem. Used your edit, and no further problems. Cheers!
_dinky

[Dpup]

Puppy 4.1 Standard USB flash install wifi connect on boot consistently fails on ASUS Eee with modified madwifi for Puppy 4.1 and ASUS Eee to WPA2 TKIP wireless router.

/tmp/bootsysinit.log error "wireless scan with iwlist failed (no networks found)... skipping interface".

And if I manually scan, it agrees no networks found...

But if I just load the profile from the first boot after installing the modified madwifi where it found the WPA2 network and just use it, the connection will consistently be made and works fine.

Have fresh reinstalled to USB flash several times with identical results on two different ASUS Eee 4G's, one with XP, other with Xandros Linux.

If I do not install the modified madwifi and use ZyXEL or Airlink 101 external USB wifi the connect on boot works fine.

Pupeee b4 consistently will connect on boot using the ASUS Eee internal wifi on both Eee's.

Thanks for any suggestions, tweaks to resolve this problem for Puppy 4.1 on ASUS Eee 4G internal wifi connect on boot.

Dpup

[tempestuous]

We discovered that the most recent version 1022.0904 of the rtl8187se wifi driver fails under Puppy 4.1.
So I just reverted to the older version 1016.0716 of the rtl8187se wifi driver in this earlier post -
http://www.murga-linux.com/puppy/viewtopic.php?p=237747#237747

[magerlab]

i put the lines to unload snd-hda-intel to rc.shutdown
now have no problem with powerpoff but icon of absvolume disappear( but volume fader works) and sgmixer do not start ( can not open dev/mixer it says in console)
sound works and alsamixer also works

i even set up a very good mic boost and can record from another corner of the room and the quality is good enough
is it possible to fix this problem?

also i did not understand how to use the fan eee module
do i need to put it into rc.local
and does it need to be set up anyhow or just keep the defaults?

[tempestuous]

[jakfish]

BIOS in the 900 (I can't vouch for the 700 series) is natively set to turn on the fan at 54C. The rub is, BIOS won't turn off the fan until the temperature returns to somewhere in in the mid-40Cs, meaning that once on, the fan stays on (the native fan speed is 40% and will increase accordingly depending on further temperature rise).

Over at forum.eee.user, there are many threads posted by users far more learned than me who aver that the eee can go much higher in temperature, 60C-70C without fan usage. There are some users who have disconnected the fan outright (I did that for a while until Tempestuous rescued eee users around the world by compiling eee.ko for Puppy 4.1)

If folks are interested in further research, I would go to forum.eee.user and search out "F J Walter" 's posts. He really knows his stuff about fan usage, and he doesn't turn his fan on until the eee hits 63C

I'm a little more cautious. For me, running the eee, on battery, at 630mhz with moderate-to-heavy surfing, and toggling off the wifi when not needed, gives a temperature b/w 49C and 55C (it depends on where you're surfing, videos, etc.) and I manually turn my fan off.

If it rose to 60C, I would turn on the fan, for no particular reason other than worry, but I've never come close to 60C.

If you bump up the CPU speed to 900mhz in BIOS, that will significantly crank up the temperature, and I see very little difference, performance-wise, between the two speeds.

If eee users wanted to keep fan usage safely down, but needed 900mhz speed, CPU Frequency/Scaling would be the way go (there's a great thread here about it, and I've used it successfully with the eee 900).

Jake

[tempestuous]

Good information jakfish.
It seems that by default the embedded controller activates the fan more than is really necessary.
From the details provided here it should be possible for someone to write a script which would check the CPU temperature at regular intervals and change the fan speed accordingly. Something like:

If temp < 60C leave fan off
If temp between 60C and 64C set fan 40%
If temp between 65C and 69C set fan 80%
If temp > 70C set fan 100%

[magerlab]

thank you for the answers on the fan module

back to mixer and absvolume
is there a way to make it work some how?
( anyway it's just optional...)

[Dougal]

[mysticmarks]

I was curious if you've been able to test MU's new kernel disk. I would love it if you could create a pet of the modified ath_pci module for the atheros 5007 card based on this new kernel.

[tempestuous]

I just sent MU a message about where to get the source code for the Eee-compatible wifi driver ...
but it would first be worth trying the standard ath5k driver.
This driver was unreliable in the 2.6.25 kernel, but it's supposed to be good in the 2.6.27 kernel, and (in theory) it supports the AR5007EG wifi chipset.

[Dougal]

[MU]

ok, compiled this "madwifi-hal" with Kernel 2.6.27.
Mark

[raffy]