Natty kernel with backported eeepc-wmi fixes has been shipped:
https://launchpad.net/ubuntu/+source/linux/2.6.38-8.40
linux (2.6.38-8.40) natty; urgency=low
[ Brad Figg ]
* [Config] Set CONFIG_NR_CPUS=256 for amd64 generic
- LP: #737124
[ Henrik Rydberg ]
* SAUCE: HID: hid-ntrig:
O the up-to-date ubuntu I've repeated #29 and after that
insmod: error inserting '/tmp/eeepc-wmi/eeepc-wmi.ko': -1 Unknown symbol in
module
uname -r : 2.6.35-27-generic
netbook eee1015 pem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
O the up-to-date ubuntu I've repeated #29 and after that
insmod: error inserting '/tmp/eeepc-wmi/eeepc-wmi.ko': -1 Unknown symbol
in module
uname -r : 2.6.35-27-generic
Please try the following steps to build and install the eeepc-wmi.ko
revision mentioned in #30 (which is basicly the same
ok i've solved my problem
using modprobe led-class
so wifi switched on/off but led always on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662365
Title:
eeepc_wmi: Unknown key 88 pressed when
@Constantine:
so wifi switched on/off but led always on
If your Eee PC has built-in bluetooth, please don't forget that the
corresponding LED will stay on unless both WiFi and bluetooth are
disabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@PrebenR:
How can I test to see if it works?
Edit /etc/default/grub to remove acpi_osi=Linux acpi_backlight=vendor
from the kernel command line, run
sudo update-grub
Ensure that eeepc-wmi is not blacklisted, reboot, then follow the steps
mentioned in
** Changed in: linux
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662365
Title:
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on Asus
EEE1005HA
Adjusting the bug status because the issue is fixed upstream.
@Ubuntu kernel team:
Please apply the upstream fixes for eeepc-wmi up to the changeset
eeepc-wmi: reorder device ids
http://git.kernel.org/?p=linux/kernel/git/next/linux-
next.git;a=history;f=drivers/platform/x86/eeepc-wmi.c
from
I wasn't aware of https://lists.ubuntu.com/archives/kernel-
team/2011-February/014508.html while writing my last comment, my
apologies for the uprising. Nevertheless, I'd hate if eeepc-wmi has to
hit the way of SRU, but let us hope for the best for now.
--
You received this bug notification
How can I test to see if it works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662365
Title:
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on Asus
EEE1005HA
--
ubuntu-bugs mailing
A fixed version of eeepc-wmi is now in linux-next.
It's also available directly from http://git.iksaif.net/?p=acpi4asus.git
To build eeepc-wmi.ko for an older kernel:
$ mkdir /tmp/eeepc-wmi
$ cd /tmp/eeepc-wmi
$ wget
acpi_osi option is ignored on 1000H with 2.6.37 kernels
and the newest BIOS (2204) I refer to.
This is not more true for 2.6.38-1.28 Natty kernel, the acpi_osi=Linux
workaround is available again and unfortunately temporarily necessary,
as backlight adjustment is broken by
I can help out, if you tell me what to do. I did a new reinstall of
Ubuntu 10.10 as I change HDD on my 1000H and now I cannot get the
wireless to work at all. Even with acpi_osi. Maybe I forgot to install
the eee package. I'll check later
--
You received this bug notification because you are a
@Ilja
Why should somebody using Ubuntu suffer because of Windows 7? I don't
get this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662365
Title:
eeepc_wmi: Unknown key 88 pressed when pressing
@Corentin
Could you proved a link to a subscription page for : platform-
driver-...@vger.kernel.org ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662365
Title:
eeepc_wmi: Unknown key 88 pressed
@PrebenR
Windows 7 support changed how the BIOS behaves, and eeepc-laptop/eeepc-wmi
drivers directly depends on the BIOS.
You don't need to subscribe to platform-driver-x86 to send a mail, but if you
want to, all you need is here: http://vger.kernel.org/majordomo-info.html.
Anyway, I should get
Thanks!
Just curious: So you mean if I upgraded my firmware then BIOS would
change because of Window 7 support? I think I already did upgrade it to
the latest version some 7-8 months back. Or is it a change in newer
models eee 1000 ?
Anyway please let me know if you need me to test anything.
@PrebenR
Currently I'm struggling to get the wireless to work at all.
This is very off-topic here, but you should probably blacklist rt2800pci
once you use Maverick, as it fights with rt2860sta for your hardware. On
Natty, rt2800pci has matured and works fine. You could choose freely
between
Is finding a workaround (until problem is fixed) spam now?
I need my wireless working, but for some reason nothing works now after
I reinstalled. Thanks for your tip, but it still didn't work. I'll
search other forums for a solution though...
--
You received this bug notification because you
@ Ilja
Thanks, finally I got it working. Had to add rt2800lib to blacklist as
well (ref:https://wiki.archlinux.org/index.php/Asus_Eee_PC_1000HE#WiFi).
Now it works as before with the 2.6.35 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
First, please CC me for any eeepc-laptop/asus-laptop/eeepc-wmi
bugreport, because I wasn't aware of this issue until today.
I'd be glad to fix this issue, but I don't have the hardware. Could
someone (with access to a 1000h) report the issue to platform-
driver-...@vger.kernel.org mailing list ?
First, please CC me for any eeepc-laptop/asus-laptop/eeepc-wmi
bugreport
Done for this one.
I'd be glad to fix this issue, but I don't have the hardware.
Would it be possible for you to buy a second-hand 1000H from a donation
to http://dev.iksaif.net/projects/acpi4asus? If yes, could you
I'd be glad to fix this issue, but I don't have the hardware.
Would it be possible for you to buy a second-hand 1000H from a donation to
http://dev.iksaif.net/projects/acpi4asus? If yes, could you please
quantify the required costs?
A second hand 1000h seems to cost 200 euros, currently
I'd be glad to fix this issue, but I don't have the hardware.
Would it be possible for you to buy a second-hand 1000H from a donation to
http://dev.iksaif.net/projects/acpi4asus? If yes, could you please
quantify the required costs?
A second hand 1000h seems to cost 200 euros, currently
currently the total of donation (mainly from flattr) is 5 euros...
This should be fixed by now.
It's why we should first try to find someone on platform-x86
who have the hardware, and is able to fix the bug.
I trust your words I'd be glad to fix this issue, so this would be
only a
It turns out to be that the (only?) proper way to disable wireless on
1000H is to disconnect the wireless card logically from the PCI bus:
# echo 1 /sys/bus/pci/devices/:01:00.0/remove
This doesn't change the status of the wireless LED, but reliably
disables the device without causing any
I don't understand. The wireless has worked fine before. Both led goes
on and off and so does the device. Why can't you make this work in the
new kernels/system? Cannot have a system where one have to disable
wireless connection before one can turn off the wireless device. This
doesn't make sense.
@PrebenR:
The wireless has worked fine before.
On Lucid: yes, but 'pciehp.pciehp_force=1' boot option was required.
Why can't you make this work in the new kernels/system?
Because newest kernels switched from eeepc_laptop to eeepc_wmi driver
for Windows7-capable Eee PC laptops. The latter
The real problem is not the unknown key message but the fact that
Fn+F2 sort of works, turning the wireless led on and off on Asus Eee PC
1000H and fatally confusing rt2800pci:
1. disable wireless via network-manager
2. press Fn+F2 (led goes off)
3. press Fn+F2 again (led goes on)
4. try to
dmesg output when pressing Fn+F2 twice and reenabling wireless in
network-manager (I replaced the hwaddress of the access point with
xx:xx:xx:xx:xx:xx) on Asus Eee PC 1000H.
** Attachment added: dmesg output
Here is the DSDT.dsl with acpi_osi=Linux in grub
** Attachment added: DSDT.dsl
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/662365/+attachment/1750588/+files/DSDT.dsl
--
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on Asus EEE1005HA
https://bugs.launchpad.net/bugs/662365
Hi
I tested the kernel linked above. It removed the complaints about
unknown key, but wireless is not turned on. The kernel modules are not
loaded etc... Does this mean there is another problem, or is it still
related to this error?
--
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on
After adding acpi_osi=Linux in grub, the default ubuntu kernel again
works and wireless is working. If I do the same with the patched kernel
above, it doesn't work. So apart from no error messages the patched
kernel is a regression for me.
System. asus eee 1000H
--
eeepc_wmi: Unknown key 88
Hi PrebenR,
Can you attach the DSDT so that I can try to know what happen..
Here is the step by step for get DSDT from BIOS.
# sudo cp /sys/firmware/acpi/tables/DSDT .
# sudo iasl -d ./DSDT # sudo apt-get install iasl if iasl is not installed.
Then please attach DSDT.dsl
--
eeepc_wmi:
Hi,
Could you please to try the kernel at
http://people.canonical.com/~ikepanhc/lp/662365/ and see if it fix the
problem.
--
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on Asus EEE1005HA
https://bugs.launchpad.net/bugs/662365
You received this bug notification because you are a member
@Ike, I've already started a small patch for this upstream which is
under discussion with some wmi developers.
** Also affects: linux
Importance: Undecided
Status: New
** Changed in: linux
Status: New = In Progress
** Changed in: linux
Assignee: (unassigned) = Gary M
I have EEE1101HA and I experience some problems with functional buttons
as well.
I have set acpi_osi=Linux in grub and that helped with some buttons
(wlan, brightness and most probably suspend - I have not checked if
suspend was not working before).
Power button produces unknown key 57. Other
--
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on Asus EEE1005HA
https://bugs.launchpad.net/bugs/662365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I will see what I can do
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ike Panhc (ikepanhc)
** Changed in: linux (Ubuntu)
Status: New = In Progress
--
eeepc_wmi: Unknown key 88 pressed when pressing Fn+F2 on Asus EEE1005HA
https://bugs.launchpad.net/bugs/662365
You
39 matches
Mail list logo
