You are not logged in.
Hey guys. I just wanted to say thank you for your hard work getting Arch working on the 901. I just got mine and finished installing and getting everything working and it is great.
A few notes that I think other people have already covered:
-the internal mic seems to work only with the version of alsa modules included in the 'zen-eee901-git' kernel.
-I had to rebuild the init file to get LVM2 to work right. To do so I issued:
mkinitcpio -c /etc/mkinitcpio.conf -k 2.6.27-rc7-zen3eee -g /boot/zeneee-git
otherwise when zen-eee901-git installed it build the init file without the proper hookes. I don't know why.
everything else was more or less a breeze. I really appreciate it.
edited for spelling...
Yes that is correct, it is because it differs from stock kernel, so we create /etc/mkinitcpio-zenee.conf (mkinitcpio-zeneee-git.conf) just edit that and update the package, it should be working now. We had issues by rewrtiting the /etc file but it should work ok now.
Offline
I'm using the zeneee kernel, do you recommend using the git one?
Offline
I'm using the zeneee kernel, do you recommend using the git one?
You can try that, I dont have any problem using eee module. than do and post:
dmesg | tail
lsmod | grep eee
ls -l /proc/eee
Offline
[sa@eeepc ~]$ dmesg | tail
0x1300 = 00073200
hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x01570900
RX DESC f2801000 size = 2048
<-- RTMPAllocTxRxRingMemory, Status=0
1. Phy Mode = 0
2. Phy Mode = 0
3. Phy Mode = 0
MCS Set = 00 00 00 00 00
<==== RTMPInitialize, Status=0
0x1300 = 000a4200
[sa@eeepc ~]$ lsmod | grep eee
[sa@eeepc ~]$ ls -l /proc/eee
ls: cannot access /proc/eee: No such file or directory
Offline
Hi
have same problem as freigeist - segfault on modprobe eee with both - stable and git kernels
ATL1E 0000:03:00.0: ATL1E: eth0 NIC Link is Up<100 Mbps Full Duplex>
ATL1E 0000:03:00.0: ATL1E: eth0 NIC Link is Up<100 Mbps Full Duplex>
BUG: unable to handle kernel NULL pointer dereference at 0000000c
IP: [<c02a1aae>] i2c_smbus_xfer+0x26/0x4b5
*pde = 00000000
Oops: 0000 [#1] PREEMPT SMP
Modules linked in: eee(+) reiserfs snd_pcm_oss snd_mixer_oss btusb bluetooth rt2860sta snd_hda_intel atl1e snd_pcm snd_timer snd_page_alloc pci_hotplug
Pid: 3343, comm: modprobe Not tainted (2.6.27-rc7-zen3eee #16)
EIP: 0060:[<c02a1aae>] EFLAGS: 00010282 CPU: 0
EIP is at i2c_smbus_xfer+0x26/0x4b5
EAX: 00000001 EBX: 00000000 ECX: 00000000 EDX: 00000069
ESI: 00000000 EDI: 00000069 EBP: f6c4d000 ESP: f6c4de80
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 3343, ti=f6c4d000 task=f788f960 task.ti=f6c4d000)
Stack: c16e3f40 01000202 00000000 00000001 00000010 f8e23fc0 c013bb78 00000c24
c1fa53e0 c03fbc80 00000700 00000003 f6c4df78 00000000 00000000 09ff4688
f8d5bdfc f8d5beec 00000001 00000000 00000000 f8d5b000 f8d5bcbc f8d5bc24
Call Trace:
[<c013bb78>] load_module+0x1367/0x1501
[<c02a207f>] i2c_smbus_read_block_data+0x26/0x52
[<c0150c68>] mmap_region+0x367/0x447
[<f8e23182>] init_module+0x2c/0x4b [eee]
[<c010113f>] do_one_initcall+0x52/0x142
[<f8e23156>] init_module+0x0/0x4b [eee]
[<c013be4f>] sys_init_module+0x87/0x174
[<c0102f3d>] sysenter_do_call+0x12/0x25
=======================
Code: 5b 5e 5f 5d c3 55 83 e1 14 57 89 d7 56 53 83 ec 6c 89 44 24 08 8a 84 24 80 00 00 00 8b 5c 24 08 8b b4 24 84 00 00 00 88 44 24 07 <8b> 43 0c 89 f5 83 78 04 00 0f b7 c1 89 04 24 74 47 83 c3 20 89
EIP: [<c02a1aae>] i2c_smbus_xfer+0x26/0x4b5 SS:ESP 0068:f6c4de80
---[ end trace 8cc1ee50d8339900 ]---
bash-3.2# lsmod
Module Size Used by
eee 4520 1
reiserfs 172980 1
snd_pcm_oss 30048 0
snd_mixer_oss 12096 1 snd_pcm_oss
btusb 10136 0
bluetooth 43808 1 btusb
rt2860sta 353600 1
snd_hda_intel 215024 2
atl1e 27668 0
snd_pcm 49924 2 snd_pcm_oss,snd_hda_intel
snd_timer 16392 1 snd_pcm
snd_page_alloc 6920 2 snd_hda_intel,snd_pcm
pci_hotplug 11212 0
bash-3.2# uname -a
Linux e-max 2.6.27-rc7-zen3eee #16 SMP PREEMPT Mon Sep 29 10:59:47 CEST 2008 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
Offline
Hmm seems like some regression or colision with other modules, for example I dont use reiserfs.
Offline
So guys I have made new rewritten acpi scripts. Now it is handled like the stock acpi does, so it is more easyer to debug through logger. I get rid of all the events and write one script that handle all of them, like the handler.sh does.
It is not in the repo now, because it needs to be more tested.
http://robertek.brevnov.net/files/linux … pkg.tar.gz
CHANGELOG:
* merge all the events in one script, eee-handler.sh
* every undefined event is sent to logger
* powersave for intel 3945 wifi cards (in the future will be extended)
* display switch doesnt work good, will be rewriten or reverted to old script (and add a dependency for bc)
* added dependency to htop (default ap button)
* experimental fsb script, will be rewriten to be more roburst (chori going to work on that)
So please test and post suggestions.
Offline
i remove all modules and try new version acpi-eee901--12-1.
same segmentation fault
BUG: unable to handle kernel NULL pointer dereference at 0000000c
IP: [<c02a1aae>] i2c_smbus_xfer+0x26/0x4b5
*pde = 00000000
Oops: 0000 [#1] PREEMPT SMP
Modules linked in: eee(+)
Pid: 3312, comm: modprobe Not tainted (2.6.27-rc7-zen3eee #16)
EIP: 0060:[<c02a1aae>] EFLAGS: 00010282 CPU: 0
EIP is at i2c_smbus_xfer+0x26/0x4b5
EAX: 00000001 EBX: 00000000 ECX: 00000000 EDX: 00000069
ESI: 00000000 EDI: 00000069 EBP: f70f4000 ESP: f70f4e80
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 3312, ti=f70f4000 task=f70d72a0 task.ti=f70f4000)
Stack: c013bb78 01000202 00000000 00000001 00000010 f8cf6fc0 c013bb78 00000c24
c018878e f7046180 f74d5a38 00000003 f70f4f78 f7046180 f74d5a38 09173688
f8cf3dfc f8cf3eec f7b16a00 00000000 00000000 f8cf3000 f8cf3cbc f8cf3c24
Call Trace:
[<c013bb78>] load_module+0x1367/0x1501
[<c013bb78>] load_module+0x1367/0x1501
[<c018878e>] proc_bash-3.2# uname -a
Linux e-max 2.6.27-rc7-zen3eee #16 SMP PREEMPT Mon Sep 29 10:59:47 CEST 2008 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
reg_open+0xe9/0xf3bash-3.2# uname -a
Linux e-max 2.6.27-rc7-zen3eee #16 SMP PREEMPT Mon Sep 29 10:59:47 CEST 2008 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
bash-3.2# uname -a
Linux e-max 2.6.27-rc7-zen3eee #16 SMP PREEMPT Mon Sep 29 10:59:47 CEST 2008 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
[<c02a207f>] i2c_smbus_read_block_data+0x26/0x52
[<c0150c68>] mmap_region+0x367/0x447
[<f8cf6182>] init_module+0x2c/0x4b [eee]
[<c010113f>] do_one_initcall+0x52/0x142
[<f8cf6156>] init_module+0x0/0x4b [eee]
[<c013be4f>] sys_init_module+0x87/0x174
[<c0102f3d>] sysenter_do_call+0x12/0x25
=======================
Code: 5b 5e 5f 5d c3 55 83 e1 14 57 89 d7 56 53 83 ec 6c 89 44 24 08 8a 84 24 80 00 00 00 8b 5c 24 08 8b b4 24 84 00 00 00 88 44 24 07 <8b> 43 0c 89 f5 83 78 04 00 0f b7 c1 89 04 24 74 47 83 c3 20 89
EIP: [<c02a1aae>] i2c_smbus_xfer+0x26/0x4b5 SS:ESP 0068:f70f4e80
---[ end trace 7a2c19727015c947 ]---
bash-3.2# lsmod
Module Size Used by
eee 4520 1
bash-3.2#
bash-3.2# pacman -Qs acpi-eee901
local/acpi-eee901 12-1 (eee)
ACPI scripts and AsusOSD for the Asus Eee PC 901
bash-3.2# uname -a
Linux e-max 2.6.27-rc7-zen3eee #16 SMP PREEMPT Mon Sep 29 10:59:47 CEST 2008 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
Offline
I got error with pciehp for git kernel too
pci_hotplug: PCI Hot Plug PCI Core version 0.5
pciehp: Unknown parameter 'pciehp_slot_with_bus'
with stable eee kernel it's work well
Offline
I got error with pciehp for git kernel too
pci_hotplug: PCI Hot Plug PCI Core version 0.5 pciehp: Unknown parameter 'pciehp_slot_with_bus'
with stable eee kernel it's work well
As it says in this thread, couple of pages back, the slot_with_bus doesn't work with .27 kernels atm, so don't use it. You don't need it anyway because the wifi toggle works anyway
Offline
Thank you! Seems I miss it .
Offline
Hi all, I've found this thread and the wiki extremly helpful in getting my 901 to work properly with Arch, thanks a lot for all your work with this. There is just one problem I have now and I'm not sure if it's a hardware problem or something I've configured wrong - my battery just dies when the battery status (standard gnome/xfce battery monitor) still reads 6 - 10% life left. I've had the laptop about 6 weeks and this has only started to be a problem for a week or so. I've always run the battery down fully then charged fully so don't think I've done anything to damage the battery. Does anyone else have this problem, or know what might be causing it?
Thanks again.
Offline
Actually, these new batteries shouldn't be drained all the way to the end. This lithium technology doesn't like it in the long run.
Offline
Actually, these new batteries shouldn't be drained all the way to the end. This lithium technology doesn't like it in the long run.
Really?! I had no idea. I'd set an auto shutdown when battery charge was at 1% which worked fine for weeks, then suddenly it started just cutting out without warning. Now I'll have to set it to shutdown at 15% or something, seems like a waste to me - one of the things that attracted me to the 901 was the battery life.
Offline
Hi guys!
I need urgent help with the acpi module!
Today my eeepc almost melted! For some reason it didn't suspend when I closed the lid, I didn't notice it and I put it in its bag... about 50 minutes later I took it out and it was burning hot! I opened the lid and it was on! I started conky and it showed 68C for the cpu! ... I immediatly shut it down!
When it was cooler I turned it on again and started looking for the reason why it didn't suspend when I closed the lid. I remembered I had updated the acpi-eee901 package yesterday, so I tried other things that depend on the acpi module and they aren't working! the only thing that works is brightness switch!
here goes my /etc/acpi/eee.conf
## acpi-eee configuration file
#### Fallback user to be used for X session if autodetection fails
XUSER=sa
#### X virtual console number, leave as is if you dont know.
X_CONSOLE_NUMBER=7
#### Power button settings ####
# Set command for power button, defaults to shutdown.
#
POWER_BUTTON_COMMAND="/sbin/shutdown -t3 -h now"
#### AP-button application/task manager launcher (Fn-F6) ####
#
#AP_COMMAND="/opt/kde/bin/ksysguard --showprocesses"
AP_COMMAND="terminal -e htop"
#AP_COMMAND="/usr/bin/gnome-terminal"
#### Display toggle (Fn-F5) ####
# Set orientation of external monitor, defaults to clone mode
# For more info see http://kapsi.fi/~ighea/eee/xorg.conf
# Modes: (clone, left-of, above, below, right-of)
#
OUTPUT_DISPLAY_MODE=clone
#OUTPUT_DISPLAY_MODE=right-of
#OUTPUT_DISPLAY_MODE=below
#### Lid events ####
#
# Scripts ALWAYS tries to TURN OFF the screen (DPMS) when lid is
# closed and back on when lid is opened.
#
# Set this to "yes" to run ON_*_LID_CLOSE_ACTION commands on lid events.
COMMAND_ON_LID_CLOSE=yes
# Examples:
# Suspend to ram when lid is closed
ON_AC_LID_CLOSE_ACTION="/etc/acpi/suspend2ram.sh"
ON_BATTERY_LID_CLOSE_ACTION="/etc/acpi/suspend2ram.sh"
# When on AC do nothing (this will still turn the screen off)
# and on battery shutdown the computer.
# ON_AC_LID_CLOSE_ACTION=""
# ON_BATTERY_LID_CLOSE_ACTION="/sbin/halt"
# The SUSPEND_SCRIPT variable is now obsolete but supported for backward compatibility.
#### WLAN-toggling (Fn-F2) ####
#
# Optional command to be executed after wireless is turned on
NETWORK_UP_COMMAND="/sbin/ifconfig ra0 up"
# and off
NETWORK_DOWN_COMMAND="/sbin/ifconfig ra0 down"
#### Power source ####
# Commands to run when AC power source is plugged in or unplugged
#
AC_PLUGGED_COMMAND=""
AC_UNPLUGGED_COMMAND=""
#### asusosd screen position. #####
#
# Asusosd must be restarted changes to take effect.
# Value can be either integer or text "center" as shown below.
# If none is set, default position (2,2) will be used.
##ASUSOSD_XPOS=200
ASUSOSD_XPOS=center
#ASUSOSD_YPOS=350
ASUSOSD_YPOS=center
#### Top function buttons. ####
BUTTON_BLANK="xset dpms force suspend"
#BUTTON_RESOLUTION=""
#BUTTON_USER1=""
#BUTTON_USER2=""
By the way is there anything I can do to verify if any component was damaged?
Offline
Hi guys!
I need urgent help with the acpi module!
Today my eeepc almost melted! For some reason it didn't suspend when I closed the lid, I didn't notice it and I put it in its bag... about 50 minutes later I took it out and it was burning hot! I opened the lid and it was on! I started conky and it showed 68C for the cpu! ... I immediatly shut it down!
When it was cooler I turned it on again and started looking for the reason why it didn't suspend when I closed the lid. I remembered I had updated the acpi-eee901 package yesterday, so I tried other things that depend on the acpi module and they aren't working! the only thing that works is brightness switch!
here goes my /etc/acpi/eee.conf
## acpi-eee configuration file #### Fallback user to be used for X session if autodetection fails XUSER=sa #### X virtual console number, leave as is if you dont know. X_CONSOLE_NUMBER=7 #### Power button settings #### # Set command for power button, defaults to shutdown. # POWER_BUTTON_COMMAND="/sbin/shutdown -t3 -h now" #### AP-button application/task manager launcher (Fn-F6) #### # #AP_COMMAND="/opt/kde/bin/ksysguard --showprocesses" AP_COMMAND="terminal -e htop" #AP_COMMAND="/usr/bin/gnome-terminal" #### Display toggle (Fn-F5) #### # Set orientation of external monitor, defaults to clone mode # For more info see http://kapsi.fi/~ighea/eee/xorg.conf # Modes: (clone, left-of, above, below, right-of) # OUTPUT_DISPLAY_MODE=clone #OUTPUT_DISPLAY_MODE=right-of #OUTPUT_DISPLAY_MODE=below #### Lid events #### # # Scripts ALWAYS tries to TURN OFF the screen (DPMS) when lid is # closed and back on when lid is opened. # # Set this to "yes" to run ON_*_LID_CLOSE_ACTION commands on lid events. COMMAND_ON_LID_CLOSE=yes # Examples: # Suspend to ram when lid is closed ON_AC_LID_CLOSE_ACTION="/etc/acpi/suspend2ram.sh" ON_BATTERY_LID_CLOSE_ACTION="/etc/acpi/suspend2ram.sh" # When on AC do nothing (this will still turn the screen off) # and on battery shutdown the computer. # ON_AC_LID_CLOSE_ACTION="" # ON_BATTERY_LID_CLOSE_ACTION="/sbin/halt" # The SUSPEND_SCRIPT variable is now obsolete but supported for backward compatibility. #### WLAN-toggling (Fn-F2) #### # # Optional command to be executed after wireless is turned on NETWORK_UP_COMMAND="/sbin/ifconfig ra0 up" # and off NETWORK_DOWN_COMMAND="/sbin/ifconfig ra0 down" #### Power source #### # Commands to run when AC power source is plugged in or unplugged # AC_PLUGGED_COMMAND="" AC_UNPLUGGED_COMMAND="" #### asusosd screen position. ##### # # Asusosd must be restarted changes to take effect. # Value can be either integer or text "center" as shown below. # If none is set, default position (2,2) will be used. ##ASUSOSD_XPOS=200 ASUSOSD_XPOS=center #ASUSOSD_YPOS=350 ASUSOSD_YPOS=center #### Top function buttons. #### BUTTON_BLANK="xset dpms force suspend" #BUTTON_RESOLUTION="" #BUTTON_USER1="" #BUTTON_USER2=""
By the way is there anything I can do to verify if any component was damaged?
Change /etc/acpi/suspend2ram.sh to /etc/acpi/eee/suspend2ram.sh
Dont be worry, I have done that also, and kept accidently my eee in its bag for few hours and then remove and was suprised:) Intel cpus has termal trotling. And my last notebook with P3 goes to 75'C while compiling kernel.
Offline
ok it's suspending now, but the rest stil isn't working (volume and wifi). Everything worked before the update... don't know why is not working now...
By the way the acpid module fails to load ad boot-up, and I can't start it manually either.
[sa@eeepc ~]$ /etc/rc.d/acpid stop
:: Stopping acpid [FAIL]
[sa@eeepc ~]$ /etc/rc.d/acpid start
:: Starting acpid [FAIL]
[sa@eeepc ~]$ /etc/rc.d/acpid restart
:: Stopping acpid [FAIL]
:: Starting acpid [FAIL]
Offline
inf wrote:Actually, these new batteries shouldn't be drained all the way to the end. This lithium technology doesn't like it in the long run.
Really?! I had no idea. I'd set an auto shutdown when battery charge was at 1% which worked fine for weeks, then suddenly it started just cutting out without warning. Now I'll have to set it to shutdown at 15% or something, seems like a waste to me - one of the things that attracted me to the 901 was the battery life.
Hi Bones.
I'm not sure why your gnome app isn't working. I would check the output of
$ cat /proc/acpi/battery/BAT0/info
are the values for design capacity and last full capacity equal?
I'm sure you chose the gnome app so you have a visual indicator for the battery level, but if you don't mind using the cli this script should work for you.
$ cat ~/bin/suspend.sh
#!/bin/bash
battery='-';
bat_dir="/proc/acpi/battery/BAT0";
if [ -d "$bat_dir" ]; then
remaining="$(awk '/remaining capacity/ {print $3}' <${bat_dir}/state)"
total="$(awk '/last full capacity/ {print $4}' <${bat_dir}/info)"
battery_level="$((remaining *100 /total))"
battery="${battery_level}"
fi
if (( "${battery}" <= 5 )); then
/usr/sbin/pm-suspend
fi
echo "${battery}"
I cron this script for every five minutes.
$ crontab -l
#
# DO NOT EDIT THIS FILE MANUALLY!! USE crontab -e INSTEAD.
#
# <minute> <hour> <day> <month> <dow> <command>
01 * * * * /usr/sbin/run-cron /etc/cron.hourly
02 00 * * * /usr/sbin/run-cron /etc/cron.daily
22 00 * * 0 /usr/sbin/run-cron /etc/cron.weekly
42 00 1 * * /usr/sbin/run-cron /etc/cron.monthly
*/5 * * * * $HOME/bin/suspend.sh
-steve
Offline
Hi Steve, thanks for the reply, I'll try cat /proc/acpi/battery/BAT0/info as soon as I can and post result. If your cron script works for me I'll be absolutely sorted. Cheers
Offline
Hi Steve, thanks for the reply, I'll try cat /proc/acpi/battery/BAT0/info as soon as I can and post result. If your cron script works for me I'll be absolutely sorted. Cheers
Furthermore you can run the script at any time to find out the percentage of the battery which is remaining.
$ ~/bin/suspend.sh
100
Offline
Hi Steve, I haven't tried the script yet but the results of the cat /proc/acpi/battery/BAT0/info are below. The design capacity and last full capacity are far from equal, do I have a broken battery?
Thanks, bones.
present: yes
design capacity: 6580 mAh
last full capacity: 4683 mAh
battery technology: rechargeable
design voltage: 8400 mV
design capacity warning: 187 mAh
design capacity low: 187 mAh
capacity granularity 1: 65 mAh
capacity granularity 2: 65 mAh
model number: 901
serial number:
battery type: LION
OEM info: ASUS
Offline
Assuming you have left the AC connected to the laptop for an extended period of time, then it would be my opinion that yes a portion of your battery is not functioning.
-steve
Offline
Assuming you have left the AC connected to the laptop for an extended period of time, then it would be my opinion that yes a portion of your battery is not functioning.
-steve
Yeah it was on AC until the light stopped blinking. I'll try to leave it plugged in for a further hour next time (hopfully the blinking/not blinking indicator is faulty and not the battery ). Thanks for your help steve.
Offline
Yeah it was on AC until the light stopped blinking. I'll try to leave it plugged in for a further hour next time (hopfully the blinking/not blinking indicator is faulty and not the battery ). Thanks for your help steve.
Hi, the fact that the LED stops blinking only shows, that batterylevel is over 90%! not that the battery is fully charged!
slappinjohn
Offline
I just uploaded a new version of the zen-eee901 STABLE kernel to the Robertek repository: http://robertek.brevnov.net/files/linux … pkg.tar.gz
Changes:
-- added a patch to the ALSA module to improve/fix microphone issues with the 2.6.26 kernel and the EEE 901 ( http://ftp.takhis.net/arch/eeepc-alsa-fix.patch ) -- thanks, @reverie;
-- upgraded the Atheros atl1e ethernet driver to version 1.0.1.0 (previous version was 1.0.0.4), which reportedly fixes the problem of intermittently assigning bogus MAC addresses to the card ( http://jan.ucc.nau.edu/wal2/atheros_attansic.html )
Last edited by chori (2008-10-09 19:55:06)
Offline