Launchpad has imported 41 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=451182.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: mandriva
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/232170
Title:
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with
Ubuntu
did this problem hit again with Lucid 10.04?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/518007
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification
This was fixed by two upstream commits which came through the stable
process. Marking Fix Released. If you have any further issues it is
probabally best to file a new bug. Thanks for your support.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
EeePC Volume and
With the latest Netbook Remix based on Jaunty (all updates, latest
kernel) and rfkill_input loaded, I still have the broken Network Manager
behaviour...
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
Ben:
A bug report isn't really the best place to be asking general questions. Try
one of the other support options:
http://www.ubuntu.com/support/communitysupport . Good luck!
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
i'm sorry if it's a dumb question-- i'm running Andy's kernel with
rfkill_input loaded on my asus eee 900, and my wireless is turned on at
every system bootup: is there any way to prevent this, and make the
wireless driver obey the bios setting?
--
EeePC Volume and Wireless Hotkeys Do Not
So it seems that wireless toggle works on stock jaunty install with the
todays new eee-control. I am not sure what the dev to fix it - perhaps
he replaced the driver or something?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
Andy: I think I must have made a mistake before. I just did a fresh
install of Jaunty RC (and applied all system updates). After installing
your kernel packages, rebooting into the kernel (2.6.28-8 instead of the
current 2.6.28-11), and inserting the rfkill-input module, wifi toggle
works
Rumour has it that rfkill-input will eventually be folded inside of
rfkill at some point. One recommendation has been to build rfkill and
rfkill directly into the kernel until that happens (otherwise you'll
have to remember to edit /etc/modules one day to remove rfkill-input)...
--
EeePC Volume
Sitsofe: Good to know.
Unforunately, without it being addressed (either loaded at boot or
statically compiled in), this bug won't be resolved. Can this be fixed
for Jaunty? Karmic?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha
I've tried it with a fresh install (now updated to Jaunty RC), and now
just tried it with the Andy's kernel packages -- all have the same
effect:
No response to the wireless toggle normally,
Inserting the rfkill-input module, the pushing the wireless toggle causes the
wireless to toggle off
Whoa -- just tried it with a custom build of upstream 2.6.29.1 kernel.
After inserting the rfkill-input module, the wireless toggle works 100%
correctly (toggles off and on properly)!
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha
Inserting rfkill-input is necessary (I suppose some hal magic should
insert it automatically); but for now, inserting it manually is
required.
For the rest, I suppose your posted log is from a stock jaunty kernel.
The kernel from Andy should contain backport of the patches included in kernel
Will the patches from 2.6.29 in Andy's kernel make it into the regular
jaunty kernel? What happens when there is an update?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received
Troy:
Two things that it might be worth mentioning:
After you've done the toggling does
/usr/bin/sudo iwlist scan
report results?
The next thing is if so does restarting Network Manager
/etc/dbus/event.d/25NetworkManager restart
help?
If the first thing doesn't even work it sounds like the wifi
Troy, you said you did a fresh jaunty instal, did you patched your
kernel, or installed the one proposed by andy (see here above) ?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You
I have the same problem as your Troy on my 901 when using eee-control to
toggle wifi. The light goes on and off, but when it comes back on NM
reports device not ready - You ever figure anything out?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy
jdeslip: I'm still stuck in the same situation as well.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just did a fresh install (with all updates) of Jaunty beta to test this
on my Eee 901. Wifi toggle does not work out of the box, but modprobing
rfkill-input causes it to work (indicator light goes on and off
appropriately).
Unfortunately, when toggling the wifi back on, networkmanager always
Just adding a note that bug 182490 is also resolved with the patched
noted in
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/232170/comments/54
(commit 5740294ca3a9b113fe146f2826effb69ca50008d)
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04
Andy:
With your kernel build, wireless , sound, brightness and sleep keys work OK (
just as fine as the custom build I used) on my eeepc 701.
The only change I need to get everything working out of the box is to
add rfkill_input to /etc/modules (maybe some hal magic should do it for
me
Any chance a backport of the last Matthew Garrett's patch (mentioned here above
by Sitsofe) get in the Jaunty release ?
Or will we have to patch it our self and wait for Karmic ?
If there is something missing for this patch to get in, let me know what
it is...
--
EeePC Volume and Wireless
On Wed, Mar 04, 2009 at 09:07:01AM -, Olivier Samyn wrote:
Any chance a backport of the last Matthew Garrett's patch (mentioned here
above by Sitsofe) get in the Jaunty release ?
Or will we have to patch it our self and wait for Karmic ?
Is this patch the only thing required to make eepc
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
Status: Triaged = In Progress
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug
I have pulled that patch and applied it to the latest Jaunty kernel.
Could those with this hardware test the kernels at the URL below and
report back here, specifically whether the hotkeys etc work as expected.
The kernels are here:
http://people.ubuntu.com/~apw/lp232170-jaunty/
** Changed
Andy:
The last patch I referred to is for wifi only and has nothing to do with volume
keys. It is solely so that wifi works out of the box (hotplugging and all)
without having to add special options to the kernel command line.
Be careful though - the patch in its current state will break those
mjg59's no pciehp required patch appears to have gone into 2.6.29 (
http://git.eu.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5740294ca3a9b113fe146f2826effb69ca50008d
).
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS,
The right place to fix this is in the kernel; marking the acpi-support
task as 'invalid'.
** Changed in: acpi-support (Ubuntu)
Status: New = Invalid
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
Forcing pciehp will no longer be required for current eeepcs when
mjg59's patch goes into the mainline kernel (this also speeds up
resuming from suspend) - http://mjg59.livejournal.com/100587.html .
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS,
This last patch from mjg59 is the only missing part to get a working out of the
box eee 701.
Adding it to the kernel package should be really a nice.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
** Attachment added: eeepc-wireless-toggle.sh
http://launchpadlibrarian.net/21961061/eeepc-wireless-toggle.sh
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug
Ok! With the last jaunty I had to add pciehp.pciehp_force=1 to the kernel
options for the wireless to work with the ath5k driver. I also added the file
eee-wireless-toggle to /etc/acpi/events/ and eeepc-wireless-toggle.sh to
/etc/acpi/. Both files are attached. Also added
options rfkill
** Changed in: mandriva
Status: In Progress = Fix Released
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because you are a member of Ubuntu
Bugs,
I have version 2.0.99+git20080912-0ubuntu6. Is the relevant change not
in this version?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because you are a
pana: upgrade to evdev 2.1 to stop the trapping of the hotkeys.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because you are a member of Ubuntu
Bugs,
Since I don't see it answered before, I'd like to confirm that Adam's
change in eeepc-config for controlling the Bluetooth device works for me
with a EEE PC 901. Now if I could just map the relevant hotkey to toggle
wifi bluetooth I'd be a happy camper.
--
EeePC Volume and Wireless Hotkeys Do
Yes it solves the problem...
I think I now have a fully functional intrepid on my eeepc 701...
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because
I merged last Matthew's patch with previous one (making hot key and
rfkill working toegether).
It works well for me (except this nasty xorg bug that prevents rfkill
input capture but it's another problem...)
This new version allows me to start with rfkill default_state=0
(wireless disabled) and
Olivier:
I believe later versions of evdev will no longer grab the device by default -
http://who-t.blogspot.com/2008/11/evdev-21-is-out.html (so this may allow the
hotkeys to continue working when you use it).
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
Matthew Garrett posted some news about the eeepc wifi on his blog
=http://mjg59.livejournal.com/100587.html
And he propose a new patch I did not already tested:
= http://www.codon.org.uk/~mjg59/tmp/eeepc-laptop-hotplug.diff
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box
I plan to do some experimenting with this, but in
/etc/acpi/events/asus-eee-volume-up there is the line:
action=/etc/acpi/if-asus-eee.sh volupbtn.sh
however:
[EMAIL PROTECTED]:~$ /etc/acpi/if-asus-eee.sh
bash: /etc/acpi/if-asus-eee.sh: No such file or directory
--
EeePC Volume and Wireless
So, my experimentation bears fruit. I created a file (for test purposes, it's
clearly not a global solution):
[EMAIL PROTECTED]:/etc/acpi$ cat if-asus-eee.sh
#!/bin/bash
`dirname $0`/$1
which doesn't really test to see if it is an eeepc, it just runs the
command anyway. Now my volume (mute, vol
Clarification: the wireless button doesn't work, wireless itself appears
to.
Is there a way to see what signals hotkeys raise? It might just be that
it needs its own event file with a particular event= definition. I just
have no idea how to find out what that should be.
--
EeePC Volume and
Eythian:
You aren't going to be able to get the wireless hotkey working without support
within the kernel itself (support that is not in the released Intrepid kernel)
or some pretty nasty hacks (assuming it emits an ACPI event). You can try
monitoring the acpi log file to see whether this is
On an install of Intrepid, the volume keys are still invisible to X.
There is a package 'eeepc-acpi-scripts' that looks like it has
potential, but it conflicts with acpi-support, which is required by
ubuntu-desktop, and so it's uninstallable. This is with an eee 701. The
keys worked in Hardy with
** Bug watch added: Mandriva Linux #43332
http://qa.mandriva.com/show_bug.cgi?id=43332
** Also affects: mandriva via
http://qa.mandriva.com/show_bug.cgi?id=43332
Importance: Unknown
Status: Unknown
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
** Changed in: mandriva
Status: Unknown = In Progress
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because you are a member of Ubuntu
Bugs,
Adam: on the 1000, doing echo 0 |sudo tee /sys/devices/platform/eeepc/bt
doesn't seem to do anything.
Doing a cat eeepc/bt returns -19 every time, so it seems like it either is a
permissions problem or something else.
So far, with all the patches I've yet to see, wlan, bluetooth and volume
I can confirm the BT bug with my 901. A cat
/sys/devices/platform/eeepc/bt gives me -19 and I can`t change it to
0 or 1.
And I have anpther problem: Everytime I use the command with rfkill to
toggle my wifi card the whole machine just freezes. That is very
annoying...
Camera toggle works...
--
I also noticed some strange behavior just after boot; and the patch for
rfkill_input may solve it.
But there is another problem coming from the way key events are
processed: xorg evdev driver catch all input events and rfkill_input do
not see them anymore when under X.
If I switch in console
A quick note, in testing against linux-tip the Red Hat bugzilla patch
breaks the resume part of suspend to RAM on my EeePC 900...
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You
Oliver:
Turns out there is a kernel bug that stops rfkill hotkeys working for the first
five minutes after boot (!) so that may explain why the wifi hotkey was failing
for you. See http://lkml.org/lkml/2008/10/4/151 for details.
--
EeePC Volume and Wireless Hotkeys Do Not Function
Adding:
options rfkill default_state=0
in:
/etc/modprobe.d/options
Should disable the wifi transmitter at boot time (in fact when the
rfkill module loads).
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
As regards the Fedora patch, the the caveat that wifi will always be
enabled on boot would be a major regression for me.
I use my eeepc a lot on aircraft and in order to comply with the law, it
should not use wifi at all in the air. I should be able to ensure that
the machine will boot with
** Also affects: centos via
https://bugzilla.redhat.com/show_bug.cgi?id=451182
Importance: Unknown
Status: Unknown
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=451182
Importance: Unknown
Status: Unknown
--
EeePC Volume and Wireless Hotkeys Do
** Changed in: fedora
Status: Unknown = Fix Released
** Changed in: centos
Status: Unknown = Fix Released
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this
Bryce:
The unpatched eeepc module sends volume keys ass acpi events (which are
currently mismapped in Ubuntu). You can work around this by changing acpi
scripts. Matthew's patch send keys through the input layer doing away with ACPI
altogether. Two approaches to solving the problem but I'd say
Oliver:
Hmm. Does using
echo 0 /sys/class/rfkill/rfkill0/state
with the patch applied also fail to turn the wifi off?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug
Echoing 0/1 to /sys/class/rfkill/rfkill0/state works. Not the key itself.
Any advice if I should look in the eeepc-laptop module or in some keyboard
configuration stuff ?
That said it's fun to see that without the eeepc-laptop module loaded,
the FN+F2 key works out of the box. Other keys do not
Olivier:
Do you have another module loaded which is also trying to do hotkeys (e.g. a
hacked up asus-apci)?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug
I found the problem; but from latest xorg developments, it does not seem
to be easily solved:
http://lists.freedesktop.org/archives/xorg/2008-August/037728.html
In fact the wireless hotkey is working well when used in console mode,
but when xorg with evdev is launched, it prevents rfkill_input to
After some more tests, the display button works well, and emits
XF86Display event which is OK (except that if you do not bind this key
to some desktop events, it is used a volume up).
So, Mattew's patch is working well on a eeepc 701, given that you tweak a
little bit you modules:
- load pciehp
This has a task open against acpi-support, however are there actually
any changes needed to this package for this? Sounds like this problem
may be entirely a kernel issue?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
Any idea when/if Matthew Garrett's patch (re: Redhat bug 451182) will
make it in Intrepid's base kernel?
I'm in the midst of compiling it for my 900 now. I'll post a summary
with the results.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS,
Adam:
I don't know what the Ubuntu policy is to kernel patches is at the moment - it
apparently isn't frozen yet... -
https://wiki.ubuntu.com/IntrepidReleaseSchedule . Matthew's patch works well
for me except every now and then the wifi hotkey will not work (but the sound
ones will).
--
Following Sitsofe suggestion, I tried Matthew's patch on my eeepc 701.
At least, I get the volume keys working.
I still have issues with the wireless and display one; that needs some
investigations.
I also noticed that this patch activates the wifi card when loaded.
--
EeePC Volume and
Oliver:
The display one is going to be problematic. These days you are expected to
switch displays when X is running by using xrandr rather than poking the BIOS
behind X's back (so really the key should be passed to a running program that
then does the switch). You could argue that not having a
Current problems (still need further investigations):
- Display button make the volume to go up. Maybe a bad key configuration
somewhere.
- Wireless button does not do anything; wireless is turned on when the module
is loaded but nothing happens when I press the toggle off button. And yes, I'm
BTW, I've added bluetooth control (a very minor change) to eeepc-
laptop.ko, based upon more recent (and deprecated) eeepc-acpi.ko code to
my local clone of ubuntu-intrepid.git:
commit e3c8316f0a41fdea91ee1e087578119000f24a9f
Author: Adam McDaniel
Date: Mon Sep 22 16:53:06 2008 -0600
Fedora have a fix for the volume keys that works for my upstream kernel
too - https://bugzilla.redhat.com/show_bug.cgi?id=451182 . It also
enables support for the wifi hotkey too (with the caveat that wifi will
always been enabled on boot and that you have to use the
pciehp.pciehp_force=1 boot
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed = Triaged
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
Indeed, in addition to Adam Mc Daniel's comment, I note a regression in
Intrepid from Hardy/Gutsy in that none of the scripts on the internet
(see http://wiki.eeeuser.com/getting_ubuntu_8.04_to_work_perfectly) now
function to make the hotkeys work.
--
EeePC Volume and Wireless Hotkeys Do Not
I have a 701 4G Surf. I'm running the latest daily of Intrepid -
updated this morning. Confirming that hot-keys do not work.
F1 (Suspend) disables networking momentarily, and then restores it.
Here is what I catch in /var/log/messages ...
Sep 17 10:12:24 ray-laptop gnome-power-manager: (ray)
I meant to include that running the latest Intrepid, I am also running
the newest Kernel release
[EMAIL PROTECTED]:~$ uname -a
Linux ray-laptop 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686
GNU/Linux
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with
I can confirm that this bug still exists on Intrepid fully updated to 15
September 2008 on an EEE PC 701 4G.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug
Confirming what bedfojo results on my EeePC 900.
Also, another oddity experienced in Hardy still exists in Intrepid
related to ACPI hotkeys: Plugging in the AC adapter still triggers an
ACPI event similar to an 'E-Mail' hotkey; Evolution launches.
--
EeePC Volume and Wireless Hotkeys Do Not
Tested on EeePC 701 4G using the latest daily build of Intrepid.
Confirm findings as indicated by Paulo Albuquerque in his report.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You
Tested my EeePC 701 (4G) with Intrepid Alpha 5. The function keys are
still not working as expected:
Fn+F1 Standby Works
Fn+F2 WiFi-enable Does not work
Fn+F3/F4 Brightness controlWorks but with a lot of lag, not as responsive
as usual
Fn+F5
All hotkeys (sleep, wireless, brightness, volume) are not working in
Intrepid Ibex Alpha 4 (with latest updates, 2.6.27-1-generic).
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
** Bug watch added: Debian Bug tracker #459326
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459326
** Also affects: acpi-support (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459326
Importance: Unknown
Status: Unknown
--
EeePC Volume and Wireless Hotkeys Do
** Changed in: acpi-support (Debian)
Status: Unknown = Fix Released
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because you are a member of
** Summary changed:
- EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
8.04 Hardy
+ EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
** Tags added: 8.04 eeepc hardy hotkey intrepid
** Also affects:
84 matches
Mail list logo
