Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 17 Apr 2014, 20:08
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
Eee Atom CPU control - testing
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 8 of 10 [137 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10 Next
Author Message
prehistoric


Joined: 23 Oct 2007
Posts: 1254

PostPosted: Thu 08 Oct 2009, 10:32    Post subject: re: kernel modules and stack trace on boot  

@tempestuous,

I apologize if this post is verbose, but I'm trying to avoid misunderstanding. I went back and downloaded those pets just before I ran this yesterday to get that depmod_FULL change you mention. I'm holding the installation which showed the problem on an SD card, so I can slip it in and exactly reproduce things. I'm hoping this will keep it from being contaminated by separate experiments.

First, results of modinfo:
Code:
:# modinfo eee
filename:       /lib/modules/2.6.30.5/kernel/drivers/acpi/eee.ko
description:    Support for eeePC-specific functionality.
author:         Andrew Tipton
license:        GPL
depends:        i2c-core
vermagic:       2.6.30.5 SMP mod_unload modversions 486

# modinfo eeepc_laptop
filename      /lib/modules/2.6.30.5/kernel/drivers/platform/x86/eeepc-laptop.ko
license:        GPL
description:    Eee PC Hotkey Driver
author:         Corentin Chary, Eric Cooper
alias:          acpi*:ASUS010:*
depends:        hwmon,rfkill
vermagic:       2.6.30.5 SMP mod_unload modversions 486
#
Here's my complete lsmod output:
Code:
# lsmod
Module                  Size  Used by
parport_pc             29828  0
lp                      9476  0
parport                34508  2 parport_pc,lp
snd_pcm_oss            37440  0
snd_seq_dummy           2608  0
snd_seq_oss            27648  0
snd_seq_midi_event      6892  1 snd_seq_oss
snd_seq                48464  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          6968  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_mixer_oss          15820  1 snd_pcm_oss
eee                     5188  1
i2c_core               23776  1 eee
iptable_mangle          2380  0
iptable_nat             4684  0
nf_nat                 17888  1 iptable_nat
ipt_REJECT              2828  1
nf_conntrack_ftp        7120  0
nf_conntrack_irc        5136  0
iptable_filter          2348  1
xt_state                1836  4
nf_conntrack_ipv4      13336  7 iptable_nat,nf_nat
nf_conntrack           63764  6 iptable_nat,nf_nat,nf_conntrack_ftp,nf_conntrack       _irc,xt_state,nf_conntrack_ipv4
nf_defrag_ipv4          1708  1 nf_conntrack_ipv4
ip_tables              11228  3 iptable_mangle,iptable_nat,iptable_filter
fan                     4048  0
arc4                    1612  2
ecb                     2508  2
ath5k                 117296  0
mac80211              166056  1 ath5k
led_class               4112  1 ath5k
serio_raw               5168  0
cfg80211               64972  2 ath5k,mac80211
pcspkr                  2284  0
snd_hda_codec_realtek   193584  1
atl1e                  30688  0
snd_hda_intel          24232  0
snd_hda_codec          64620  2 snd_hda_codec_realtek,snd_hda_intel
snd_pcm                72496  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              20340  2 snd_seq,snd_pcm
snd                    56516  10 snd_pcm_oss,snd_seq_oss,snd_seq,snd_seq_device,       snd_mixer_oss,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_pcm,snd_time       r
soundcore               6912  1 snd
snd_page_alloc          8852  2 snd_hda_intel,snd_pcm
shpchp                 31616  0
pci_hotplug            28140  1 shpchp
intel_agp              25788  1
agpgart                34188  2 intel_agp
video                  18560  0
output                  2796  1 video
battery                10032  0
thermal                12712  0
evdev                   9472  0
eeepc_laptop           11680  0
rfkill                 10672  2 eeepc_laptop
button                  5148  0
hwmon                   2344  1 eeepc_laptop
processor              34592  1
ac                      3952  0
fuse                   53800  0
aufs                  137092  1
nls_iso8859_1           3724  1
nls_cp437               5356  1
usbhid                 26112  0
usb_storage            51584  1
squashfs               22928  2
uhci_hcd               21564  0
ehci_hcd               32856  0
usbcore               138160  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
#


Modification of rc.local
Code:
# cat /etc/rc.d/rc.local
#this file called from rc.sysinit
#you can edit this file
#When firewall is installed, will append lines to this file...

if [ -x /etc/rc.d/rc.firewall ]; then
  /etc/rc.d/rc.firewall start
fi
modprobe eee
/usr/sbin/eee-fan-ctrl.sh &
#


Does that cover all the questions?
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7547
Location: qld

PostPosted: Thu 08 Oct 2009, 23:24    Post subject:  

Ok, sorry for getting a little off topic here.. but my pain with the p4-clockmod module does not exist, that is because the module is non-existent in 430-small.iso...(a bug reported in 430-small) (thanks anyway dawnsboy). The current compile of SHE is just not working on Puppy with the Eee-pc-701SD.

Back to the gui, which is the point here.. where are the other Celeron testers? I suppose this is an Atom thread so some are scared off. I will start a new thread to see if some folks with Celerons want to run some commands so I get a better picture. I may provide a minor upgrade in the meantime, with a few refinements.

Cheers.

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Fri 09 Oct 2009, 02:18    Post subject:  

prehistoric, the result from your "modinfo eee" command confirms that the eee module is loaded on your system.
So the fan control script should not complain about the /proc/eee directory being missing.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7547
Location: qld

PostPosted: Fri 09 Oct 2009, 03:30    Post subject:  

Ok testers,

Here is 0.4
Changelog
-changed "OK" button to close
-added a splash which shows up for a few seconds letting the user know something is happening
-changed the pinstall script to detect "stepping :6" (older Celerons) and will install the appropriate invoking script to /usr/bin... newer Celerons will use the atom GUI now (*rhadon's and my 701SD)

To Do
-there is no built in mechanism to detect what mode the machine is in at boot.
-it seems later Celerons are in "Normal" mode at boot, older Celerons "Powersave" and I'm not sure about Atoms.

I'm making a new thread for Celeron users, no older Celeron users have posted here so I'm just relying on tempestuous info and google.
Please offer any feedback

Enjoy

SEE NEWER POST V-0.5

_________________
Woof Mailing List | keep the faith Cool |

Last edited by 01micko on Sat 10 Oct 2009, 08:25; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
prehistoric


Joined: 23 Oct 2007
Posts: 1254

PostPosted: Fri 09 Oct 2009, 04:40    Post subject: fan control bug  

Quote:
prehistoric, the result from your "modinfo eee" command confirms that the eee module is loaded on your system.
So the fan control script should not complain about the /proc/eee directory being missing.

I agree, but I'm still getting the error reported earlier. I'm going to do a new installation on another SD card to test the 0.4 script in case this install has been corrupted during testing. We'll see what happens.
Back to top
View user's profile Send private message 
rhadon


Joined: 27 Mar 2008
Posts: 1291
Location: Germany

PostPosted: Fri 09 Oct 2009, 11:57    Post subject:  

@ 01micko

Please, can you tell me which scripts I must delete manually to uninstall your eee-cpucontrol-03.pet? I can't find it in PPM.

Don't know what was going wrong, sometimes at shutdown the screen freezes and shows a lot of small squares in different grey colours and the only chance to go out is the poweroff button. Posted first by aarf here. I know you've read this post. Perhaps this was the reason.

Or can I just install the newer one over the old one?

~ Rolf

_________________
Ich verwende "frugal", und das ist gut so. Wink
Raspberry Pi without Puppy? No, thanks.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7547
Location: qld

PostPosted: Fri 09 Oct 2009, 17:32    Post subject:  

rhadon wrote:
@ 01micko

Please, can you tell me which scripts I must delete manually to uninstall your eee-cpucontrol-03.pet? I can't find it in PPM.

Don't know what was going wrong, sometimes at shutdown the screen freezes and shows a lot of small squares in different grey colours and the only chance to go out is the poweroff button. Posted first by aarf here. I know you've read this post. Perhaps this was the reason.

Or can I just install the newer one over the old one?

~ Rolf


This one is safe to install over the top.

Rolf, you will have a 3 button gui now Wink , I had the same problem with my late model Celeron, had to hard poweroff.

Cheers, Mick

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
dawnsboy


Joined: 03 Dec 2008
Posts: 248
Location: Indiana - Republic of New Canada

PostPosted: Fri 09 Oct 2009, 19:51    Post subject:  

@01micko

I downloaded and installed eee-cpucontrol-04.pet on my 701 4G, Intel Celeron 900MHz, 100MHz FSB Eeepc. It works quite well on Puppy Linux 4.3 k-2.6.25.16. Thank you.

cat /proc/eee/fsb echoes 70 24 1 in power save mode and 100 24 1 in performance mode. I believe that this version should work very well on all of the 701/900's that have a 100MHz FSB.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7547
Location: qld

PostPosted: Fri 09 Oct 2009, 19:59    Post subject:  

Thanks for report dawnsboy, that's the one I was looking for Wink One thing, when you boot your machine is the fsb 70 or the last chosen mode?

Cheers

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
dawnsboy


Joined: 03 Dec 2008
Posts: 248
Location: Indiana - Republic of New Canada

PostPosted: Fri 09 Oct 2009, 20:05    Post subject:  

@01micko

You are welcome. My machine reboots to default mode.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7547
Location: qld

PostPosted: Fri 09 Oct 2009, 20:07    Post subject:  

Thanks for prompt response dawnsboy. It looks as if all eeepcs boot into default mode. That being the case, the gui should reflect that. If it isn't I can fix it.

Cheers

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
cthisbear

Joined: 29 Jan 2006
Posts: 3251
Location: Sydney Australia

PostPosted: Fri 09 Oct 2009, 20:10    Post subject:  

01micko"

PM to you again in Puppy.

Chris.
Back to top
View user's profile Send private message 
dawnsboy


Joined: 03 Dec 2008
Posts: 248
Location: Indiana - Republic of New Canada

PostPosted: Fri 09 Oct 2009, 20:10    Post subject:  

The gui does reflect that on this machine. Well done.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5139
Location: Australia

PostPosted: Fri 09 Oct 2009, 22:33    Post subject:  

prehistoric,
Your problem might be that the eee module takes time to fully load, and the fan control script needs to wait a bit.
Please try adding "sleep 5" between the two commands; open /etc/rc.d/rc.local in Geany, and modify it to look like this -
Code:
modprobe eee
sleep 5
/usr/sbin/eee-fan-ctrl.sh &

If this solves the error message after bootup, you can reduce the sleep value (4,3,2,1) to minimise the wait.
Back to top
View user's profile Send private message 
prehistoric


Joined: 23 Oct 2007
Posts: 1254

PostPosted: Sat 10 Oct 2009, 03:15    Post subject: /proc/eee  

@tempestuous,

Tried a "sleep 10" with no luck. Time to go back and make sure I'm testing what I intend. I would have done this today, if other tasks had not intervened.

-------

Latin motto for Puppy:
Quote:
Quanti canicula ille in fenestra
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 8 of 10 [137 Posts]   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1024s ][ Queries: 13 (0.0236s) ][ GZIP on ]