Arch on Eee PC

tfskelly · 2008-11-30 21:39:35

Hello,

I've read many posts on this subject, but haven't found a resolution yet. I have an eeePC 1000 and am brand new to ArchLinux. I am somewhere between beginner/intermediate in general Linux knowledge. I am having trouble getting arch to detect my network adapters - both wireless and wired. I just want my wired ethernet to work so I can run pacman without having to copy packages to a usb drive

These are the outputs of some of hw commands:

hwdetect --show-net

ifconfig
 (shows the loopback adapter, no ath0 or eth0)

lspci | grep net
01:00.0 Network Controller:RaLink Unknown device 0781
04:00.0 Ethernet controller: attansic technology corp.  Unknown Device 1026 (rev b0)

rc.conf lines:

MOD_AUTOLOAD="yes"
MODULES=(atl1e snd-mixer-oss snd-pcmoss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
eth0="DHCP
INTERFACES=(eth0)

I have tried toofishe's eee kernel but when I use it the modules listed in rc.conf aren't loaded. The error is:
FATAL: Module not found

for each of the modules listed in the rc.conf above.

Thanks!
KB

Onyros · 2008-12-01 01:56:28

Anyone managed to get the tap/sliding back on your EEEPC's after the latest Xorg update? I tried enabling every setting I had before on my xorg.conf to /etc/hal/fdi/policy/11-x11-synaptics.fdi, but it's still not working for me.

Who has the magic combination?

tfskelly · 2008-12-01 06:05:37

Got my problems with the network card in my eeepc 1000 solved. Followed the instructions at the Asus eeepc Wiki page here http://wiki.archlinux.org/index.php/Asus_Eee_PC#atl1e. Installing unrar and unzip were a little painful but got my eth0 working! Next challenge: wireless

faelar · 2008-12-02 23:02:33

Anyone managed to get the tap/sliding back on your EEEPC's after the latest Xorg update? I tried enabling every setting I had before on my xorg.conf to /etc/hal/fdi/policy/11-x11-synaptics.fdi, but it's still not working for me.
Who has the magic combination?

Maybe you should try to make set them with synclient ?

chillamba · 2008-12-03 20:50:37

Hi all.

Problem with wlan toggle Fn+F2 with toofishes kernel 2.6.27.6-3 solved!

Problem description:
after wlan switch off by "echo 1 > /sys/devices/platform/eeepc/wlan" ath5k modules unloaded, blue led is off, but pcie-card is not unplugged really.
dmesg shows "trying to reset device-failed" or "couldn't wake up MAC chip" and something like.
These messages are shown even after turning on wlan by "echo 0 > bla-bla-bla"
As result - wlan power couldn't be controlled from arch by means of shell or Fn+F2.

How to reproduce:
It can be reproduced only from the clear arch install on eee

Problem reason:
after unloading ath5k pci-e card is not unplugged, because of PCI-E Hotplug is set to Y instead of M (in kernel konfig).
I don't know why, but kernel can't control it.... so, pciehp module is the best solution.

Solution:
just recompile the kernel with:
CONFIG_HOTPLUG_PCI_PCIE=m
and add pciehp module to /etc/rc.conf

modified ighea's wlan.sh (as someone asked):

#! /bin/sh

source /etc/acpi/eee.conf

PWR=$(cat /sys/devices/platform/eeepc/wlan)

case $1 in
    poweron)
        if [ "$PWR" = "0" ]; then
            modprobe pciehp pciehp_force=1
            sleep 1
            echo 1 > /sys/devices/platform/eeepc/wlan
            sleep 2
            ifconfig wlan0 up
            # Loop to the eternity!!! bawwaawawa, well once should be enough. >)
            if ifconfig wlan0 > /dev/null
            then
                echo "Running network up command!"
                if [ -e /tmp/eeewlanfailcounter ]; then rm /tmp/eeewlanfailcounter;fi
                (sleep 1; $NETWORK_UP_COMMAND) &
            else
                FAILC=$(</tmp/eeewlanfailcounter) || FAILC=0
                echo "Current fail count is $FAILC"
                if [ $FAILC -gt 2 ];
                then
                    logger "Could not bring up WLAN."
                    echo "Could not bring up WLAN, sorry. See dmesg for more information!"
                    exit 1
                fi
                echo $(expr $FAILC + 1) > /tmp/eeewlanfailcounter
                /etc/acpi/wlan.sh poweroff
                /etc/acpi/wlan.sh poweron
            exit 1
            fi
        fi
        ;;


    poweroff)
        if [ "$PWR" = "1" ]; then
            logger "remove wlan interface"
            echo "Removing wlan interface and unloading modules"
            ifconfig wlan0 down
            sleep 1
            echo "Turning wlan device power off"
            echo 0 > /sys/devices/platform/eeepc/wlan
            sleep 1
            rmmod pciehp
            echo "Running network down command"
            (sleep 1; $NETWORK_DOWN_COMMAND) &
         fi
        ;;
esac

Last edited by chillamba (2008-12-08 13:05:38)

pooldoo · 2008-12-04 04:52:58

Onyros wrote:

Anyone managed to get the tap/sliding back on your EEEPC's after the latest Xorg update? I tried enabling every setting I had before on my xorg.conf to /etc/hal/fdi/policy/11-x11-synaptics.fdi, but it's still not working for me.
Who has the magic combination?

This worked for me.

http://bbs.archlinux.org/viewtopic.php? … 89#p456689

The only problem I'm still seeing is the cursor is moving way too slow. Any ideas on how to speed it up?

F-eeks · 2008-12-06 16:08:57

Hello,

I'm using the toolfishes kernel on my eeepc 701.

Since the last kernel update, the WiFi doesn't work any more. I removed the old ath* modules from my DAEMONS array and added ath5k, replaced "ath0" by "wlan0" in my Wicd configuration, and I did "ifconfig wlan0 up".

I can list all the available wifi networks, with wicd, wifi-radar or manually.
But when I try a connection to any of thoses networks, Wicd doesn't go after "Reconfiguring IP address". The problem is the same with Wifi-Radar, and with manual commands.

It seems to be a DHCP problem :

$ dhclient wlan0
...
wmaster0: unknown hardware address type 801
...
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
...
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
$

And :

$ dhcpcd wlan0
wlan0: dhcpcd 4.0.4 starting
wlan0: waiting for carrier
wlan0: timed out
$

Any idea on how get it working ?

EDIT :
I can connect manually using wpa_supplicant... Of course the dhcp commands where not working : there was no connection...
I don't no why wicd or wifi-radar cannot get an IP address ...
It's time for me to try netcfg

Last edited by F-eeks (2008-12-06 17:47:27)

Onyros · 2008-12-08 03:25:03

F-eeks wrote:

It's time for me to try netcfg

It sure is, mate

And, just to spare you some pain with it, at least with my EEEPC I had to reboot after configuring netcfg - an error related to wpa_supplicant, probably due to the fact I was using wicd before. I removed everything related to wicd, configured my wireless connection for netcfg usage, and then fought through problems with wpa_supplicant - couldn't even connect manually with it - until I resorted to brute force. Rebooting did the trick

toofishes · 2008-12-08 03:51:57

New kernel out- let me know if there is breakage, I sure didn't see any.

chillamba · 2008-12-08 09:44:22

Hello, toofishes.

Could your please describe the difference with 2.6.26-3 kernel or something like changes history?

The differences from the web git: http://code.toofishes.net/gitweb.cgi?p= … 25dae24e61

As I see, ath5k is added as module, but pcie hot plug is still added in the kernel (not module).
Could you please give dmesg output right after wi-fi switching off, waiting for 3-5 minutes (ath5k is slow) and then switching it on again?

I'm not sure, but think that problem with waking up MAC chip will appear

Last edited by chillamba (2008-12-08 09:57:31)

toofishes · 2008-12-08 12:37:07

The differences? Look at GIT. I'm not getting paid to do this.

I never turn wireless off, so it probably is "broken". If you truely need to unload modules to turn things off, this sounds broken. Can anyone propose a better solution?

chillamba · 2008-12-08 13:04:03

I have posted above, that wireless can be switched by "echo 1(0) > /sys/devices/platform/eeepc/wlan".

And, as I have found on several forums, many people are using your kernel and wireless switch doesn't work.

ath5k is not full ready now, according to http://linuxwireless.org/en/users/Drivers/ath5k and is really working in B mode only and I think the first reason of not-working wireless switch is that ath5k is very slow (in case of working with hardware)

Wi-Fi toggle is 100% working when pciehp module is used, istead of PCI-Express Hotplug functionality from the kernel... I don't know how to describe it in more details...

So, could you please compile your kernels with CONFIG_HOTPLUG_PCI_PCIE=m, instead of CONFIG_HOTPLUG_PCI_PCIE=y?
It will be easy for many users to switch on/off the wi-fi without kernel re-compilation, and just one thing you should do for yourself - to add pciehp to /etc/rc.conf

I'm using this way right now on your 2.6.26-3 kernel (recompiled), and nothing is broken during wireless switch, and, of course, after "rmmod pciehp"

In addition, many users are not really acquanted with kernel recompilation, and they want to have all working "from the box", even it is not Arch way

Last edited by chillamba (2008-12-08 20:07:55)

chillamba · 2008-12-08 13:30:24

F-eeks

To get the wicd working choose WEXT driver instead of madwifi and autochoose for DHCP

This works for me

Last edited by chillamba (2008-12-08 13:32:58)

zodmaner · 2008-12-08 13:58:42

Thanks for the update toofishes, will try out the new kernel as soon as I can.

Regarding the wireless issue. After some experimenting, it seems that wireless could be turn off with just

echo 0 > /sys/devices/platform/eeepc/wlan

(as root, of course), without having to unload any modules.

Turn on wireless using

echo 1 > /sys/devices/platform/eeepc/wlan

also works, but I'm having problem trying to brings up wlan0 interface again.

Running ifconfig wlan0 up after turning on wireless produces this error mesage in it.

SIOCSIFFLAGS: Input/output error

Also, the kernel.log have these messages:

ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: unable to reset hardware: -5
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: unable to reset hardware: -5
.
.
.

Any ideas guys?

Last edited by zodmaner (2008-12-08 14:00:47)

chillamba · 2008-12-08 15:05:23

zodmaner

Pleas look at my posts #1193 and #1186

toofishes
As you see, problem appears.
Could you please try my solution and recompile your kernel (or compile new kernels) with CONFIG_HOTPLUG_PCI_PCIE=m?
It is just to prevent this problem

Update: I mean that it is not neccessary, your have already done a good job, thanks a lot
Other way is to add my solution at the wiki page.

Problem appears because hardware is not deleted from system after it is turned off and is not back added after turning on .

Last edited by chillamba (2008-12-08 19:25:57)

zodmaner · 2008-12-08 15:32:39

chillamba wrote:

zodmaner
Pleas look at my posts #1193 and #1186
toofishes
As you see, problem appears.
Could you please try my solution and recompile your kernel (or compile new kernels) with CONFIG_HOTPLUG_PCI_PCIE=m?
It is just to prevent this problem

Problem appears because hardware is not deleted from system after it is turned off and is not back added after turning on .

Ah, I see now. Sorry for not reading your previous posts carefully enough.

I will try out your wlan.sh tonight (along with recompiling the kernel). Thanks for taking your time to look into this issue, chillamba.

saten · 2008-12-09 08:50:25

@chillamba:
i followed your instructions, here's my report

fn+f2
pciehp: PCI Express Hot Plug Controller Driver version: 0.4 unloaded

fn+f2 again
pciehp: HPC vendor_id 8086 device_id 2660 ss_vid 0 ss_did 0
hpdriver 0000:00:1c.0:pcie02: service driver hpdriver loaded
pciehp: HPC vendor_id 8086 device_id 2664 ss_vid 0 ss_did 0
hpdriver 0000:00:1c.2:pcie02: service driver hpdriver loaded
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
pciehp: Card present on Slot(3)
pciehp: Device 0000:01:00.0 already exists at 1:0, cannot hot-add
pciehp: Cannot add device 0x1:0
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
wlan0: deauthenticating by local choice (reason=3)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)
ath5k phy0: failed to wakeup the MAC Chip
ath5k phy0: can't reset hardware (-5)

a couple of minutes

fn+f2
pciehp: Card not present on Slot(3)
ath5k_pci 0000:01:00.0: PCI INT A disabled
hpdriver 0000:00:1c.2:pcie02: unloading service driver hpdriver
hpdriver 0000:00:1c.0:pcie02: unloading service driver hpdriver
pciehp: PCI Express Hot Plug Controller Driver version: 0.4 unloaded

fn+f2 again 
pciehp: HPC vendor_id 8086 device_id 2660 ss_vid 0 ss_did 0
hpdriver 0000:00:1c.0:pcie02: service driver hpdriver loaded
pciehp: HPC vendor_id 8086 device_id 2664 ss_vid 0 ss_did 0
hpdriver 0000:00:1c.2:pcie02: service driver hpdriver loaded
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
pciehp: Card present on Slot(3)
PCI: 0000:01:00.0 reg 10 64bit mmio: [0, ffff]
program_fw_provided_values: Could not get hotplug parameters
ath5k_pci 0000:01:00.0: enabling device (0000 -> 0002)
ath5k_pci 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ath5k_pci 0000:01:00.0: setting latency timer to 64
ath5k_pci 0000:01:00.0: registered as 'phy1'
phy1: Selected rate control algorithm 'pid'
ath5k phy1: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)

should I have modules autoloading ON for this to work at the first shot?

By the way, thanks for this solution This issue was quite annoying!

chillamba · 2008-12-09 09:56:18

saten,

As I have understood - all is working for you?
I repeat, that ath5k is too slow now, so you should wait 2-3 minutes after turning off wireless and only after this couple of minutes turn it on again.

no, there is no need to autoload modules.
just add pciehp to the modules section of /etc/rc.conf

saten · 2008-12-09 10:22:38

@chillamba: seems that it actually works, apart from that issue with reloading fast

chillamba · 2008-12-09 10:54:35

saten
I think we should inform ighea about this solution too

toofishes
So, what we will do?
Just add my solution at the wiki or add my solution in your kernels?

fatblueduck · 2008-12-12 08:47:33

I've got an eeepc701 and my wireless situation has changed with the new kernel update. I must now manually create essid each time I use wlan0 or wlan0 will not connect.

Thank You toofishes for the eee-kernel. I've been using it for almost a year now.

saten · 2008-12-13 22:52:37

Hi everyone,

After all I think it's better to wait for a better release of the ath5k and related stuff. In the mean time, chillamba's workaround will do fine.
I think ighea has disappeared

Sante

toofishes · 2008-12-14 22:59:44

I built the 2.6.27.9 kernel today, and pciehp is now a module. Enjoy!

saten · 2008-12-15 00:54:13

so, after a guy wrote on my blog about compat wireless drivers, i decided to give 'em a try.
i had to recompile toofishes 2.6.27.8 putting as modules a bunch of things, before i could got them compiled. apart from that, everything smooth. wireless working, maybe even ighea's version of wlan.sh could work with those. i can unload and reload the ath5k of compat wireless without problems.

@chillamba: would you like to give those a try?
@toofishes: i'm not able to include those drivers in the kernel by myself, so what if i just mail you what i have here so you can see what's different from your last try with compat wireless?

ps. it might be an impression, but looks like rx power is higher now.

toofishes · 2008-12-15 03:25:08

saten wrote:

so, after a guy wrote on my blog about compat wireless drivers, i decided to give 'em a try.
i had to recompile toofishes 2.6.27.8 putting as modules a bunch of things, before i could got them compiled. apart from that, everything smooth. wireless working, maybe even ighea's version of wlan.sh could work with those. i can unload and reload the ath5k of compat wireless without problems.
@chillamba: would you like to give those a try?
@toofishes: i'm not able to include those drivers in the kernel by myself, so what if i just mail you what i have here so you can see what's different from your last try with compat wireless?
ps. it might be an impression, but looks like rx power is higher now.

Since 2.6.28 is really close to release, I'm just going to wait for that rather than try compat-wireless again, unless someone can really prove that improvements can be had by building those drivers.

Arch Linux

#1176 2008-11-30 21:39:35

Re: Arch on Eee PC

#1177 2008-12-01 01:56:28

Re: Arch on Eee PC

#1178 2008-12-01 06:05:37

Re: Arch on Eee PC

#1179 2008-12-02 23:02:33

Re: Arch on Eee PC

#1180 2008-12-03 20:50:37

Re: Arch on Eee PC

#1181 2008-12-04 04:52:58

Re: Arch on Eee PC

#1182 2008-12-06 16:08:57

Re: Arch on Eee PC

#1183 2008-12-08 03:25:03

Re: Arch on Eee PC

#1184 2008-12-08 03:51:57

Re: Arch on Eee PC

#1185 2008-12-08 09:44:22

Re: Arch on Eee PC

#1186 2008-12-08 12:37:07

Re: Arch on Eee PC

#1187 2008-12-08 13:04:03

Re: Arch on Eee PC

#1188 2008-12-08 13:30:24

Re: Arch on Eee PC

#1189 2008-12-08 13:58:42

Re: Arch on Eee PC

#1190 2008-12-08 15:05:23

Re: Arch on Eee PC

#1191 2008-12-08 15:32:39

Re: Arch on Eee PC

#1192 2008-12-09 08:50:25

Re: Arch on Eee PC

#1193 2008-12-09 09:56:18

Re: Arch on Eee PC

#1194 2008-12-09 10:22:38

Re: Arch on Eee PC

#1195 2008-12-09 10:54:35

Re: Arch on Eee PC

#1196 2008-12-12 08:47:33

Re: Arch on Eee PC

#1197 2008-12-13 22:52:37

Re: Arch on Eee PC

#1198 2008-12-14 22:59:44

Re: Arch on Eee PC

#1199 2008-12-15 00:54:13

Re: Arch on Eee PC

#1200 2008-12-15 03:25:08

Re: Arch on Eee PC

Board footer