You are not logged in.
It appears that Asus it trying to make amends...
http://www.engadget.com/2007/11/26/asus … h-the-gpl/
Actual ACPI source is here:
ftp.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar
Offline
[ 1253.828000] Asus EEEPC HOTKEY
[ 1253.828000] [eeepc hotk] Hotkey init flags 0x41.
[ 1253.828000] [eeepc hotk] Get control methods supported : 0x101711
Alive and running in Ubuntu
.
Offline
Now that looks like great news, does it mean it paves the way for people or a group of people to create other Linux install CDs for the Eee that will give you out-of-the-box setups that work as well as the original OS that Asus provide?
Offline
^^ The missing element is the native Wifi driver. Then it should pretty much be possible.
Offline
Ok...I have to make this pointless post without any positive addition to the thread. YAY!!!!!! ASUS is now on my good side again...I can live without the wireless driver for a little longer.
Last edited by JazzplayerL9 (2007-11-26 7:32:23 pm)
Offline
I'd say this info is front page worthy (of this site), the fact Asus didn't originally post the complete sources hasn't gone down well in some circles and having a prominent post on the front page would help alleviate the worries about Asus' intentions.
Well, when they get round to posting the wifi driver source!
*sigh* I'm getting seriously fed up of weeks of reading about everyone's experiences with using their Eee's, looking at pictures & youtube clips doesn't cut it, *evil eyes at Nexus13*
Last edited by Haku (2007-11-26 7:59:22 pm)
Offline
quagga wrote:
[ 1253.828000] Asus EEEPC HOTKEY
[ 1253.828000] [eeepc hotk] Hotkey init flags 0x41.
[ 1253.828000] [eeepc hotk] Get control methods supported : 0x101711
Alive and running in Ubuntu.
How did you go about doing that?
Offline
quagga wrote:
[ 1253.828000] Asus EEEPC HOTKEY
[ 1253.828000] [eeepc hotk] Hotkey init flags 0x41.
[ 1253.828000] [eeepc hotk] Get control methods supported : 0x101711
Alive and running in Ubuntu.
I don't have yet EEEPC right now and probably I can get one in Sydney this weekend. I am just wondering what is the kernel version of the Ubuntu that you install in your EEEPC? Do you compile from src or use the precompiled one. Reason, I am asking this is I am stuck with Asus M3N laptop and I can't boot my laptop after installing ubuntu 7.10. ACPI module problem. I thought of replacing with ACPI module with module posted here.
Thanks.
Offline
I'm using the default Ubuntu Gutsy kernel (I think it is 2.6.22-generic14 or something similar).
Anyway, the makefile is hard coded to use 2.6.21-eeepc so I first edited that, replacing 2.6.21-eeepc with `uname -r`. That should have done it but it didn't so I manually parsed the Makefile and executed the second command.
Namely I:
cd /lib/modules/<yourkernelversion>/build
make -C <path to where your asus_acpi folder is - mine was in my home dir> modules
This made a new asus_acpi.ko. I then did a locate asus_acpi.ko and used sudo to mv my new module over the old module.
Finally, depmod -ae and modprobe asus_acpi.
@NS, most of the code in this module looks eee specific but I guess you could give it a try. ACPI issues with asus often times are caused by busted DSDT's. I once had to fight a good bit with them with a motherboard.
Offline
quagga: Exellent! can you report what you've done in the "Alternative Dists" forum?
Are you able to confirm what this has fixed? i.e. do all hotkeys now work?
Thanks.
Offline
I only used it briefly. I had to go do the whole work thing heh. It created /proc/asus so I imagine you can enable/disable things like the camera via echoing 1's and 0's to objects in there.
Most of the hotkeys seemed to do something. I really didn't have much time to try it all out.
Offline
wow, that is great news quagga!!
I'm running Ubuntu quite happily although the only things missing is the ACPI and the wifi... I'll wait paitiently for your excellant work!
Offline
Regarding the wifi-drivers, some frequency-regulation-authorities (e.g.FCC) require the wifi-hardware-companies to make changes of the transmit-power and -frequency difficult. That is one of the reasons for the lack of open-source-drivers.
The split between the kernel-module and a kernel-independent userspace-firmware module is a sufficient compromise, giving the user the option to compile the driver for any distribution or kernel.
Offline
stupid question but is this the actual OS of the EEE? I was thinking of downloading and running on a virtual machine for a bit (I'm bored ok?
) while I wait for my machine ![]()
Offline
Ok got the driver loaded. Doesn't seem to do anything tho besides dmesg showing its loaded. XEV doesnt show anything either.
Offline
I managed to rebuild it and load it in Xubuntu. I have mapped the keys in keytouch. If someone wants the keymap, it's here:
<keyboard>
<file-info>
<syntax-version>1.1</syntax-version>
<last-change format="%d-%m-%Y">27-11-2007</last-change>
<author>Erik Lindberg</author>
</file-info>
<keyboard-info>
<keyboard-name>
<manufacturer>Asus</manufacturer>
<model>EeePC 701</model>
</keyboard-name>
</keyboard-info>
<key-list>
<key key-type="acpi-hotkey">
<name>Fn-F2</name>
<event-descr>hotkey ATKD 00000011</event-descr>
<keycode>CONNECT</keycode>
<default-action action-type="plugin">
<plugin-name>Amixer</plugin-name>
<plugin-function>Mute</plugin-function>
</default-action>
</key>
<key key-type="acpi-hotkey">
<name>Fn-F5</name>
<event-descr>hotkey ATKD 00000030</event-descr>
<keycode>SETUP</keycode>
<default-action action-type="plugin">
<plugin-name>Amixer</plugin-name>
<plugin-function>Mute</plugin-function>
</default-action>
</key>
<key key-type="acpi-hotkey">
<name>Fn-F6</name>
<event-descr>hotkey ATKD 00000012</event-descr>
<keycode>CYCLEWINDOWS</keycode>
<default-action action-type="plugin">
<plugin-name>Amixer</plugin-name>
<plugin-function>Mute</plugin-function>
</default-action>
</key>
<key key-type="acpi-hotkey">
<name>Fn-F7</name>
<event-descr>hotkey ATKD 00000013</event-descr>
<keycode>MUTE</keycode>
<default-action action-type="plugin">
<plugin-name>Amixer</plugin-name>
<plugin-function>Mute</plugin-function>
</default-action>
</key>
<key key-type="acpi-hotkey">
<name>Fn-F8</name>
<event-descr>hotkey ATKD 00000014</event-descr>
<keycode>VOLUMEDOWN</keycode>
<default-action action-type="plugin">
<plugin-name>Amixer</plugin-name>
<plugin-function></plugin-function>
</default-action>
</key>
<key key-type="acpi-hotkey">
<name>Fn-F9</name>
<event-descr>hotkey ATKD 00000014</event-descr>
<keycode>VOLUMEUP</keycode>
<default-action action-type="plugin">
<plugin-name>Amixer</plugin-name>
<plugin-function></plugin-function>
</default-action>
</key>
</key-list>
</keyboard>Save it as EeePC.Asus and import it in keytouch and then you can assign functions to the keys. I just put some random functions as default, since I didn't know how have no default function.
Since brightness and sleep key works anyway, I didn't map those.
Offline
Shades: does it enable the wifi on/off buttons to work correctly in ubuntu. i.e. when you switch off wireless and switch it back on, does ubuntu process the event to allow wireless re-connection?
Offline
ma10 wrote:
It appears that Asus it trying to make amends...
http://www.engadget.com/2007/11/26/asus … h-the-gpl/
Actual ACPI source is here:
ftp.asus.com/pub/ASUS/EeePC/701/ASUS_ACPI_071126.rar
I'd like to buy the XP model when it comes out. I'd like to run the native Xandros on SDHC. How hard would it be to install the Xandros code to SDHC and boot from it? I'd like to keep XP on SDHC. That way I don't need to purchase XP, but could get a cheaper version from the EEE licensing price. Also I wouldn't need to shrink it down or worry about drivers if Asus will already do it. Would it be difficult for a Linux newbie to install the Xandros code to SDHC for dual boot?
Offline
i'm not a noob, but I'm a lil' lost. what exactly is ACPI and what's its significance to the EEE PC?
Offline
Advanced Configuration and Power Interface- required to control aspects of the device.
Offline
quagga wrote:
[ 1253.828000] Asus EEEPC HOTKEY
[ 1253.828000] [eeepc hotk] Hotkey init flags 0x41.
[ 1253.828000] [eeepc hotk] Get control methods supported : 0x101711
Alive and running in Ubuntu.
I'm an absolute newb to be honest. I got a Cd in a magazine i bought the other day (linux project i think its called), and it has Xubuntu 7 on it, are you excited because it means that it will now work on the eee?
Offline
The short simple version. The keys that are activated by holding down the blue Fn key will work as expected when this module is loaded into another flavor of linux.
Offline
streetUK wrote:
quagga wrote:
[ 1253.828000] Asus EEEPC HOTKEY
[ 1253.828000] [eeepc hotk] Hotkey init flags 0x41.
[ 1253.828000] [eeepc hotk] Get control methods supported : 0x101711
Alive and running in Ubuntu.
I'm an absolute newb to be honest. I got a Cd in a magazine i bought the other day (linux project i think its called), and it has Xubuntu 7 on it, are you excited because it means that it will now work on the eee?
Well I've been using Xubuntu on the eee since the day I got it. Last night I reinstalled full Ubuntu on JFS. That takes a little time for me as I have to fire up synaptic afterwards and remove a gig or so of junk I'll never use (openoffice, firefox, cd-rippers aren't really useful on a device without a cdrom ...). So I finished that up last night. Just have to get ndiswrapper back up and running.
@ darrlyimg, the hotkeys will have the bios disconnect the card. This effectively disables the card. To get it to work again however, the only way I've been able to get that to work is to re-enable the card and reboot. Removing and reinserting ndiswrapper didn't seem to work.
Offline
I haven't enabled the wlan turn on and off yet. I guess you need to find a working script from the original xandros or something. I don't really need the ability to turn it off. I guess I should fix it before I fly home for christmas.
Offline
Hey Quagga,
Can you elaborate on your instructions, or translate them into newbspeak?
For example:
Did you only have to replace 2.6.21-eeepc with `uname -r` in the KERNEL_VERSION line? and are the `s required as well?
What does "That should have done it but it didn't so I manually parsed the Makefile and executed the second command. " mean?
When I run "make -C <path to where your asus_acpi folder is - mine was in my home dir> modules", it tells me "No rule to make target "Modules". Stop" I guess I misunderstood what you meant there.
I understand the rest, but since the make didnt work for me, I'm kind of stuck. Would appreciate any advice.
Thanks
ps By the way, your other post-install scripts for Ubuntu are super cool, thanks a lot for those as well.
Offline