Trevor wrote:
> Alan Jenkins wrote:
>> On 8/11/09, Alan Jenkins <[email protected]> wrote:
>>> On 8/11/09, Trevor <[email protected]> wrote:
>>>> Alan Jenkins wrote:
>>>>> On 2.6.30, eeepc-laptop is intended to replace
>>>>> the force-loading of pciehp. It would be good to know why it doesn't
>>>>> work on the 900A when it works on other machines. Maybe we can fix
>>>>> it.
>>>> I don't have any idea why, but it's definitely not working here. I'm
>>>> happy to help however I can
>>>>
>>>>> Does dmesg show any errors during the initialisation of eeepc-laptop?
>>>>>
>>>>> I would be interested in the full output of dmesg and acpidump.
>>>>>
>>>>> Regards
>>>>> Alan
>>>> I don't see anything out-of-place in dmesg, but I've never seen the
>>>> successful version, so my eyes are likely not the best to look at it.
>>>> full output of dmesg is attached,
>>> [ 10.405347] eeepc: Eee PC Hotkey Driver
>>> [ 10.406016] eeepc: Hotkey init flags 0x41
>>> [ 10.406214] eeepc: Get control methods supported: 0x181701
>>> [ 10.406403] input: Asus EeePC extra buttons as
>>> /devices/virtual/input/input1
>>>
>>> Thanks. I don't see any problem here.
>>>
>>>> how would I get you the acpidump?
>>> Simples :-). It'll be 100k+ so I guess it's best to send off-list (or
>>> use pastebin etc).
>>>
>>> sudo apt-get install acpidump
>>> sudo acpidump > acpidump.out
>>>
>>>
>>> Also, can you please run a test for me? It should help confirm that
>>> the problem is what it looks like. Without pciehp loaded, what is the
>>> result of
>>>
>>> cat /sys/bus/pci/slots/eeepc-wifi/adaptor
>>>
>>> both after you disable the wifi, and then after you enable it again.
>>
>> Sorry, thats "adapter" with an e... and it won't help.
>>
>> Let's check what happens to the network interface instead. Does the
>> directory "/sys/class/net/wlan0" still exist when you disable the
>> wireless (without pciehp loaded)?
>>
>> Thanks
>> Alan
>
> Here's my command record for your test:
>
> tre...@myri:~$ #verify that pciehp isn't loaded
> tre...@myri:~$ lsmod | grep pciehp
> tre...@myri:~$ #wlan up and working off of boot-up
> tre...@myri:~$ cd /sys/class/net/wlan0
> tre...@myri:/sys/class/net/wlan0$ ls
> address device flags link_mode power type
> addr_len dev_id ifalias mtu statistics uevent
> broadcast dormant ifindex operstate subsystem
> carrier features iflink phy80211 tx_queue_len
> tre...@myri:/sys/class/net/wlan0$ cd
> tre...@myri:~$ #wlan off
> tre...@myri:~$ sudo /etc/acpi/actions/wireless.sh off
> Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
> Detected WLAN module ath5k on wlan0
> There is already a pid file /var/run/dhclient.wlan0.pid with pid 2638
> killed old client process, removed PID file
> Internet Systems Consortium DHCP Client V3.1.2p1
> Copyright 2004-2009 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Listening on LPF/wlan0/00:15:af:c9:9f:d9
> Sending on LPF/wlan0/00:15:af:c9:9f:d9
> Sending on Socket/fallback
> DHCPRELEASE on wlan0 to 192.168.0.1 port 67
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device wlan0 ; Invalid argument.
> tre...@myri:~$ cd /sys/class/net/wlan0
> bash: cd: /sys/class/net/wlan0: No such file or directory
> tre...@myri:~$ #wlan back on
> tre...@myri:~$ sudo /etc/acpi/actions/wireless.sh on
> Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
> Detected WLAN module ath5k on wlan0
> wlan0: ERROR while getting interface flags: No such device
> Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
> Detected WLAN module ath5k on wlan0
> Internet Systems Consortium DHCP Client V3.1.2p1
> Copyright 2004-2009 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Bind socket to interface: No such device
> tre...@myri:~$ cd /sys/class/net/wlan0
> bash: cd: /sys/class/net/wlan0: No such file or directory
> tre...@myri:~$
>
Oops. Looking at wireless.sh, this doesn't tell me anything either.
> ACPI dump is coming off-list - anyone who wants a copy for themselves,
> just let me know.
>
> Thanks for all the help,
>
> Trevor
Great, that shows the exact problem I was expecting.
Here's a test patch for 2.6.30 (attached).
Regards
Alan
diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c
index 353a898..eb9ce03 100644
--- a/drivers/platform/x86/eeepc-laptop.c
+++ b/drivers/platform/x86/eeepc-laptop.c
@@ -680,6 +680,7 @@ static int eeepc_hotk_add(struct acpi_device *device)
if (ACPI_FAILURE(status))
printk(EEEPC_ERR "Error installing notify handler\n");
+ eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P5");
eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P6");
eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P7");
@@ -748,6 +749,7 @@ static int eeepc_hotk_add(struct acpi_device *device)
wlan_fail:
if (ehotk->eeepc_wlan_rfkill)
rfkill_free(ehotk->eeepc_wlan_rfkill);
+ eeepc_unregister_rfkill_notifier("\\_SB.PCI0.P0P5");
eeepc_unregister_rfkill_notifier("\\_SB.PCI0.P0P6");
eeepc_unregister_rfkill_notifier("\\_SB.PCI0.P0P7");
ehotk_fail:
@@ -768,6 +770,7 @@ static int eeepc_hotk_remove(struct acpi_device *device, int type)
if (ACPI_FAILURE(status))
printk(EEEPC_ERR "Error removing notify handler\n");
+ eeepc_unregister_rfkill_notifier("\\_SB.PCI0.P0P5");
eeepc_unregister_rfkill_notifier("\\_SB.PCI0.P0P6");
eeepc_unregister_rfkill_notifier("\\_SB.PCI0.P0P7");
_______________________________________________
Debian-eeepc-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
