Difference between revisions of "Talk:ASUS Eee PC 901"

From ArchWiki
Jump to: navigation, search
(What about the 1000/1000H?)
(Remove closed discussions.)
 
(17 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== Hardware-Overview ==
+
== Bluetooth (de)activation on 2.6.32 ==
Because it doesn't belong to the necessary parts of the articel (every 901-model should be the same) I would suggest removing it or for the sake of completness of the articel moving it at the end of the articel. If noone objects I will move it at the end in the next few days. -- [[User:Rorschach|Rorschach]]
+
  
== Stock-Kernel VS. recompiled one ==
+
Hi all, I'm writing in talk because I just tried kernel 2.6.32 on the EEE 901 and I have something to report. I'm actually not using archlinux, I just found this wiki very helpful for my setup, so feel free to ignore this comment (and even delete it) if the situation here doesn't apply to you.
What dependencies do people supposedly need to recompile the stock kernel for? (section Option 1: Compile and customize the stock kernel) I didn't recompile my kernel on my 901 and everything I can think of works fine. I think this section should be changed or clarified to explain why its recommended to recompile.
+
  
--[[User:Chori|Chori]] 13:29, 23 September 2008 (EDT)
+
In my case, bluetooth was toggled via an rfkill interface, pretty much like wireless, except that rfkill[bluetooth] = rfkill[wlan+1]:
There are some patches applied to the kernel source:  in particular, to the acpi driver, to the mouse driver, to the rt2860sta driver, to improve them, fix bugs, and add functionality.  It's true that you can run ArchLinux on the EEE 901 with just the stock kernel;  but it's not optimized for it, and many users have experienced problems.  Your point is well-taken, however, I'll clarify that section.
+
  echo 1|0 > /sys/devices/platform/eeepc/rfkill/rfkill1/state
 +
The problem that I found is that the numbers of the rfkill interfaces sometimes change, therefore I'm using the following script (to be run as root) for bt toggling:
  
== What about the 1000/1000H? ==
+
#!/bin/bash
 +
 +
# enumerate rfkill devices
 +
for rfkillDir in /sys/devices/platform/eeepc/rfkill/rfkill*
 +
do
 +
# check for bluetooth device
 +
if grep -q 'bluetooth' "$rfkillDir/name"
 +
then
 +
echo "Found bluetooth in $rfkillDir"
 +
read state < "$rfkillDir/state"
 +
if [ "$state" = "0" ]
 +
then
 +
echo "State was OFF. Turning ON"
 +
echo 1 > "$rfkillDir/state"
 +
else
 +
        echo "State was ON. Turning OFF"
 +
                        echo 0 > "$rfkillDir/state"
 +
fi
 +
fi
 +
done
  
In all the article only the 901 model is commented. In my opinion, as all the things also apply to the 1000/1000H models (I guess) it should be corrected, for example, writing 901/1000/1000H where 901 is.
+
I'm sorry if this is OT and if it doesn't help you, I just thought that it might. --[[User:IngFrancesco|IngFrancesco]] 08:11, 29 April 2010 (EDT)
 
+
--[[User:Chori|Chori]] 16:08, 9 October 2008 (EDT)
+
There are some subtle differences in the hardware between the 901 and 1000 models.  If someone wants to take on highlighting the 1000(H) specific idiosyncrasies, I'd be happy to expand the scope of this wiki page.
+
 
+
Afaik just the bigger display is the difference but I have a 1000H so if you tell me what you think should be different, I'll check it. I could follow this articel without any problems with my 1000H. --[[User:Rorschach|Rorschach]]
+
 
+
The hardware differences might be more subtle than just the screen size. I just got a 1000 (not H nor HA) and started a new thread on the forum for this: http://bbs.archlinux.org/viewtopic.php?pid=476341
+
We could also merge the 4 pages on EeePCs into one big, or one generic and smaller ones for specific details on each models. What do you think?
+
--[[User:big_gie|big_gie]]
+
 
+
I have created a new wiki entry for the 1000: [[Asus_Eee_PC_1000]]. I also created a package for ACPI events which should supports all the different models. You can find [http://aur.archlinux.org/packages.php?ID=23318|acpi-eeepc-generic in AUR]. Can anybody test this for me on other models then the 1000? Thank you! :)
+
--[[User:big_gie|big_gie]]
+
 
+
== Different kernels ==
+
Any chance of a summary of the kernels available from: http://robertek.brevnov.net/files/linux/arch eg the git ones?
+
 
+
And why does searching the wiki for 901 result in zero page title matches and zero page text matches?!?
+

Latest revision as of 07:06, 2 May 2013

Bluetooth (de)activation on 2.6.32

Hi all, I'm writing in talk because I just tried kernel 2.6.32 on the EEE 901 and I have something to report. I'm actually not using archlinux, I just found this wiki very helpful for my setup, so feel free to ignore this comment (and even delete it) if the situation here doesn't apply to you.

In my case, bluetooth was toggled via an rfkill interface, pretty much like wireless, except that rfkill[bluetooth] = rfkill[wlan+1]:

 echo 1|0 > /sys/devices/platform/eeepc/rfkill/rfkill1/state

The problem that I found is that the numbers of the rfkill interfaces sometimes change, therefore I'm using the following script (to be run as root) for bt toggling:

#!/bin/bash

# enumerate rfkill devices
for rfkillDir in /sys/devices/platform/eeepc/rfkill/rfkill*
do
	# check for bluetooth device
	if grep -q 'bluetooth' "$rfkillDir/name"
	then
		echo "Found bluetooth in $rfkillDir"
		read state < "$rfkillDir/state"
		if [ "$state" = "0" ]
		then
			echo "State was OFF. Turning ON"
			echo 1 > "$rfkillDir/state"
		else
		        echo "State was ON. Turning OFF"
                        echo 0 > "$rfkillDir/state"
		fi
	fi
done

I'm sorry if this is OT and if it doesn't help you, I just thought that it might. --IngFrancesco 08:11, 29 April 2010 (EDT)