[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2011-12-25 Thread Launchpad Bug Tracker
[Expired for udev (Ubuntu) because there has been no activity for 60 days.] ** Changed in: udev (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/537763

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2011-10-26 Thread Martin Pitt
If it's still an issue in oneiric, can you please follow the fixing broken keys section in /usr/share/doc/udev/README.keymap.txt.gz and add the info here? Thanks! ** Changed in: udev (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-11-09 Thread e X t 7 3
Hi everyone Almost all the keys Fn and special work under my Ubuntu 10.04 + kernel - http://forum.ubuntu.pl/showpost.php?p=785500postcount=1086 - for different machines + wifi drivers and ndiswrapper, and this script - http://dl.dropbox.com/u/2936246/splash-nvidia- ati.tar.bz2 (also in that

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-10-12 Thread stefaca
on my 1201n FN+F8 work only with nouveau drivers. after installing nVidia drivers FN+F8 is unusable will ubuntu solve this somewhere in the future? -- Asus Eee PC 1201n: Function Keys https://bugs.launchpad.net/bugs/537763 You received this bug notification because you are a member of Ubuntu

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-06-08 Thread Jamie Furness
There are currently multiple issues here: 1) acpi_osi=Linux is required otherwise the eeepc-laptop.ko module isn't loaded. Is this why the bug is marked as affecting udev? I know nothing what-so-ever about udev. 2) Various keymapping are missing from the eeepc-laptop.ko module. Some of these

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-06-07 Thread Jamie Furness
To expand slightly on the details SKid(Sven) posted, here is some tests done using Ubuntu 10.04, with and without acpi_osi=Linux. http://spreadsheets.google.com/ccc?key=0Ap2XdAnh9KHQdFB2VWdiRkxpT2N3QVpuNFQ2VEpMVUEhl=en It looks like when adding acpi_osi=Linux to the boot parameters, the results

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-06-04 Thread Hew McLachlan
Volume function keys are working again with maverick alpha 1 on my 1005HA, but wireless still does not. ** Changed in: udev (Ubuntu) Status: New = Confirmed -- Asus Eee PC 1201n: Function Keys https://bugs.launchpad.net/bugs/537763 You received this bug notification because you are a

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-06-04 Thread Hew McLachlan
While function keys such as Fn+F2 still don't work, a workaround is to enable/disable this in the BIOS. ** Tags added: regression-release ** Description changed: Hello at all, I have the current Ubuntu 9.10 (Kernel 2.6.31.20). I have also a new Eee PC 1201N (that new one with dual core

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-17 Thread SKid(Sven)
Hello at all, well I just put the current status into one single table (see attachment) in order to have it more handy. Today evening I had very much bad luck with 10.4, which drives me to decide to no longer support 10.4 with my tests, because it behaves so unstable that really costs me too

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-12 Thread Luca Aluffi
Guys, some days ago I discovered that the key FN-F8 (switch display) works... but just with NOUVEAU drivers. The matter comes when using NVIDIA: indeed, it stops to work. Since the NVIDIA's configuration panels works and the card detectc the discrete display (from hdmi, in my case), I suppose

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-12 Thread Luca Aluffi
Uh... forgotten... Multimedia keys FN-Arrows works fine, but just when there is a multimedia application running: I guess it makes sense, so we should be fine with that. -- Asus Eee PC 1201n: Function Keys https://bugs.launchpad.net/bugs/537763 You received this bug notification because you are

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-12 Thread Muriel de Souza Godoi
Adding acpi=Linux acpi_backlight=vendor parameter makes no changes here. Backlight Function keys are still working, but without notification. Fn+F7 (Turn off the backlight) doesn't work in both cases. My netbook model: Assus EEEPc 1008ha -- Asus Eee PC 1201n: Function Keys

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-11 Thread SKid(Sven)
Hello at all, well, I just have one simple question. As the original poster, I would like to check the above statements about the acpi_osi parameter against my original bug entry. Yes, my original post was against Ubuntu 9.10 now I installed 10.4 (Netbook Edition) in the expectation, that

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-11 Thread pablomme
@SKid: these parameters go in /etc/default/grub. Simply do: - Press Alt+F2, enter gksudo gedit /etc/default/grub and press enter - Change the line that reads GRUB_CMDLINE_LINUX= to GRUB_CMDLINE_LINUX=acpi_osi=Linux acpi_backlight=vendor - Save and exit - Press Alt+F2, enter gksudo

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-08 Thread James Babiak
Luca, Thanks. Confirmed the acpi_osi=Linux worked for me too. -- Asus Eee PC 1201n: Function Keys https://bugs.launchpad.net/bugs/537763 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-04 Thread SKid(Sven)
Ah, hello, I didn't had much time in the last weeks, @Nicolas Albert: Ah, sorry, yes, of cause, your name is Nicolas. Sorry! And, yes, you didn't write anything about WIFI in general... I can't remember, what I thought in that moment!? Maybe partial amnesia? %-) Well, just another

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-05-01 Thread Urock
acpi_osi=Linux fixed the problem for me too Asus Eee PC 1201N with Lucid 32bit however before I added acpi_osi=Linux the fn5fn6 brightness keys worked and the notification worked as well But after adding acpi_osi=Linux the brightness keys still functionally work however the notification does

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-04-30 Thread Brian harkness
Hey, thanks for the acpi_osi=Linux comment. I just ran sudo dpkg-reconfigure grub-pc and added it to the second prompt before quiet splash so that it read acpi_osi=Linux quiet splash The thing I wanted the most were the volume controls and this fixed it in Lucid (Kubuntu) -- Asus Eee PC 1201n:

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-04-23 Thread Luca Aluffi
Adding acpi_osi=Linux to the grub's kernel boot parameters list helps, and most of the keys are taken into account. Even multimedia keys. fn-SPACE belongs to the Super Hybrid Engine throttle control, which does not exist on the linux side. fn-V could work if bound to an application for the

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-04-08 Thread James Babiak
I installed 10.04 Lucid Lynx last night on my 1201N. For the most part, everything is working. However I too am experiencing issues with certain function keys no longer working. The same results as the other two posts. These keys DID function in 9.10, so it's something specific to the upgrade.

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-04-02 Thread Muriel de Souza Godoi
I can confirm almost the same at my Asus EEEPC 1008HA Brightness, sleep and WIFI works fine. But Mute and volume keys doesn't Mute: Fn + F10 Volume Down: Fn + F11 Volume UP: Fn + F12 They used to work fine on Karmic in the same hardware. No logs in the dmesg, and no output in showkeys -s

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-27 Thread Luca Aluffi
Hi! Just ended the installation of ubuntu 10.04 for my new netbook and falled into the same problem. My computer is ASUS 1201NL, which is an underpowered version of the 1201N. Anyway the motherboard, NVIDIA ION, is the same so I would like not to open a new thread, since I feel that the root of

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-22 Thread SKid(Sven)
Hello Albert, If you have the same model as me (1201N) the world is not that bad... Regarding the WIFI I downloaded the Realtek driver. But I had to take care about the path I placed the sources in order to compile them. As usuall, no spaces should be in the path. But that's common to most makes.

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-22 Thread Nicolas Albert
My first name is Nicolas ;) I didn't say that wifi doesn't work. I compiled realtek driver too. I said wireless switch (wifi+bluetooth) doesn't work, Fn+F2 doesn't product any X key event. -- Asus Eee PC 1201n: Function Keys https://bugs.launchpad.net/bugs/537763 You received this bug

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-22 Thread Gary M
** Tags added: hw-specific -- Asus Eee PC 1201n: Function Keys https://bugs.launchpad.net/bugs/537763 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

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-20 Thread Nicolas Albert
I installed Ubuntu 9.10 - lucid lynx - and there is many regression until the first message : * Fn+F2 - wireless switch - doesn't work, no event with xev * Fn+F10/F11/F12 - sound mute/decrease/increase - doesn't, no event with xev Other function keys are like the first message.

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-13 Thread SKid(Sven)
Hello, trhanks for your fast response. I added the requested information via apport as you can see above. If you would like to know the key codes of the funtion keys, you could point me to some tools which could tell me the codes? Maybe I could use such tool to get the codes and post them here?

[Bug 537763] Re: Asus Eee PC 1201n: Function Keys

2010-03-12 Thread Philip Muškovac
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 537763 This will help us to find and resolve the problem. Bear in mind that you may need