Would it be possible to force cpu scaling below usual limits in Linux ?

[n0cmonkey]

Did it work?

 

[The Linuxator]

No

 

[The Linuxator]

I have an idea is it possible to embed this code in a symlink that is used by default in the system ? so that way while that symlink is executing a regular task at bootup it will enable the trackpoint on it's way ?

So for example what if I copy this code that you wrote and put it into the Netwrokmanager file in etc/init.d we already know that it's working or else I wouldn't be typing this .

 

[n0cmonkey]

Originally posted by: The Linuxator
I have an idea is it possible to embed this code in a symlink that is used by default in the system ? so that way while that symlink is executing a regular task at bootup it will enable the trackpoint on it's way ?

Uh, what? You can add the script code to another one of the startup scripts, but that's the wrong way to do things.

Anything about this in the logs?

Before you echo the values you posted into the files you posted, do those files exist? If not, my script is broken. You can try the following instead:

 

[The Linuxator]

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
I have an idea is it possible to embed this code in a symlink that is used by default in the system ? so that way while that symlink is executing a regular task at bootup it will enable the trackpoint on it's way ?

Uh, what? You can add the script code to another one of the startup scripts, but that's the wrong way to do things.

Anything about this in the logs?

Before you echo the values you posted into the files you posted, do those files exist? If not, my script is broken. You can try the following instead:

Ya the problem is I don't understand how loops are made in bash otherwise I would have spotted any issues, I 'll try the code without the loops (like what you have) and see if that is the issue.

 

[n0cmonkey]

Originally posted by: The Linuxator

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
I have an idea is it possible to embed this code in a symlink that is used by default in the system ? so that way while that symlink is executing a regular task at bootup it will enable the trackpoint on it's way ?

Uh, what? You can add the script code to another one of the startup scripts, but that's the wrong way to do things.

Anything about this in the logs?

Before you echo the values you posted into the files you posted, do those files exist? If not, my script is broken. You can try the following instead:

Ya the problem is I don't understand how loops are made in bash otherwise I would have spotted any issues, I 'll try the code without the loops (like what you have) and see if that is the issue.

If those files are made on the fly, my if statements would fail and (if you copied them close to how I have them) write to a logfile. Without the if statements they should succeed a bit better. Hopefully.

 

[The Linuxator]

OK still no go, I don't know why.

I am afraid I am gonna have to do it the dirty way, untill I can figure it out.

 

[n0cmonkey]

Anything in the logs with a hint as to why it's failing?

 

[The Linuxator]

Originally posted by: n0cmonkey
Anything in the logs with a hint as to why it's failing?

Well here is the no brainer the logs aren't showing, remeber that I specefied a location in my home directory in case anything fails , well it's not failing as I see no file, either that or the code isn't constructed right.
But what boggles my mind is that even after we reduced the code to 4 lines with no loops just simple commands it still didn't work.
Right now I have placed the trackpoint code t in the wine shell script and right now it works flawlessly.
Here is the code for the wine shell script perhaps there is something you are forgetting so take a look at how it's constructed in general, perhaps in my system something else must be added :

 

[n0cmonkey]

Hmmm, maybe the Linux init requires all of the intelligence built into the script (the start/stop stuff)... God I hate sysV init. What trash. :|

This might work:

 

[n0cmonkey]

BTW, this is just a script. So you can run it like any other script.
something like: /etc/init.d/trackpoint_script.sh start

 

[The Linuxator]

Originally posted by: n0cmonkey
BTW, this is just a script. So you can run it like any other script.
something like: /etc/init.d/trackpoint_script.sh start

So there was no need for those lame reboots ?

 

[n0cmonkey]

Originally posted by: The Linuxator

Originally posted by: n0cmonkey
BTW, this is just a script. So you can run it like any other script.
something like: /etc/init.d/trackpoint_script.sh start

So there was no need for those lame reboots ?

Maybe, maybe not. Testing it one way is fine, but a reboot gives it a real world type test.

The previous scripts were dumber, and didn't allow you to "turn them off." This one should (although I have no idea if 0 is off in both cases ).

You'll still need the symlink, but I don't think it'll break unless you change the file in /etc/init.d or delete the symlink.

 

[The Linuxator]

Originally posted by: n0cmonkey

Originally posted by: The Linuxator

Originally posted by: n0cmonkey
BTW, this is just a script. So you can run it like any other script.
something like: /etc/init.d/trackpoint_script.sh start

So there was no need for those lame reboots ?

Maybe, maybe not. Testing it one way is fine, but a reboot gives it a real world type test.

The previous scripts were dumber, and didn't allow you to "turn them off." This one should (although I have no idea if 0 is off in both cases ).

You'll still need the symlink, but I don't think it'll break unless you change the file in /etc/init.d or delete the symlink.

Ok here is onething I should have asked since the begening but delayed a little untill I see how to make symlinks.

But why are the driver's values in /etc/devices/platform/i8042/srio0/ unchangable permenantly, I understand there must some protection inorder to avoid errors or mishandling of such data, but isn't there a way to disable that protection change the value to 1 instead of zero and then reneable such protection, as I never need my trackpoint's select function to be disabled and I see no point in enabling it again and again through a script file every boot up , makes sense to you ? I have enabled write and execution permession for my account and root account yet I can't modify it , it seems that the files in /sys aren't your normal files, eh ?