[opensuse-factory] eee-pc hotkey support not up to date..?
Hi, As i used this page: http://en.opensuse.org/OpenSUSE_on_the_EeePC#ath5k , to orientate myself to install opensuse 11.1 on eee-pc, i noticed that it is not up to date anymore.. Is it possible to get the hotkey support for 11.1/11.2 in some online repo? F1 to F9 are most important.... ;) many thnx if someone would look into this... (many eee-pc owners on the dutch pda- forum are very interested in opensuse on eee-pc..) -- Have a nice day, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEE-PC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 4.9" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Hi,
Is it possible to get the hotkey support for 11.1/11.2 in some online repo?
Update: F1: suspend/sleep, works. F2: no clue if it does: no visible sign, and the wireless is 'down'....(broken) F3/4: screen brightness, works. F5: ext monitor, not yet tested. F6: windows taskmanager? dunno what it is supposed to be in opensuse.. F7: mute, does not work. F8: volume down, does not work. F9: volume up, does not work. Are there any options to get at least the volume and networkswitch work? With evt some visibility on the networkswitch? The blue light is always on, exept in sleepmode... Light on/of would be a good indicator if network is switched... -- Have a nice day, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEE-PC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 4.9" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Oddball schreef:
Hi,
When i read the eeepc wiki page i get confused... There is all kind of 'old' stuf, so it is very difficult to 'know' what to use.. ;( Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't? I guess everybody that uses opensuse 11.1 on his/her eeepc, wants the hotkeys working, i most certainly do. How to accomplish that? RPM's are for 10.3, and scripts, well, together with tha allready working stuff? Hmmm. Sounds not good to me... Is there anybody that has the keys working on 901? I hope for 11.2 all is 'cool', and works without hassle... ;) -- Have a nice day, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEE-PC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 4.9" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, on 03/25/2009 01:33 PM Oddball wrote:
Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't?
At least the volume keys on the 901 generate ACPI events. You just need a script in /etc/acpi/events/ that catches those and execute something like aumix. I'll can tell you tonight what i have. I dont have my 901 with me. Stay tuned :) Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Henne Vogelsang wrote:
on 03/25/2009 01:33 PM Oddball wrote:
Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't?
At least the volume keys on the 901 generate ACPI events. You just need a script in /etc/acpi/events/ that catches those and execute something like aumix. I'll can tell you tonight what i have. I dont have my 901 with me. Stay tuned :)
Both gnome and kde normally automatically respond to those keys with volume changes. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Ludwig Nussel schreef:
Henne Vogelsang wrote:
on 03/25/2009 01:33 PM Oddball wrote:
Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't?
At least the volume keys on the 901 generate ACPI events. You just need a script in /etc/acpi/events/ that catches those and execute something like aumix. I'll can tell you tonight what i have. I dont have my 901 with me. Stay tuned :)
Both gnome and kde normally automatically respond to those keys with volume changes.
cu Ludwig
That is what i expected, but here it is not the caae.... I installed plain 11.1 dvd, and updated during the install, as the wifi worked imediately... After that i could log in, to find what i have now. A week ago i installed on the original 16GB ssd, but than the updatedid break my wifi, but i could it get to work. This time everything seems to be different... helas... -- Have a nice day, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEE-PC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 4.9" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Henne Vogelsang schreef:
Hi,
on 03/25/2009 01:33 PM Oddball wrote:
Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't?
At least the volume keys on the 901 generate ACPI events. You just need a script in /etc/acpi/events/ that catches those and execute something like aumix. I'll can tell you tonight what i have. I dont have my 901 with me. Stay tuned :)
Henne
i appreciate that very much..;) I also agree with ludwig that it should work out of the box, so it is at least strange, that it does not.... -- Have a nice day, Oddball, aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEE-PC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 4.9" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch 25 März 2009 13:33:44 schrieb Oddball:
When i read the eeepc wiki page i get confused... There is all kind of 'old' stuf, so it is very difficult to 'know' what to use.. ;( Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't? I guess everybody that uses opensuse 11.1 on his/her eeepc, wants the hotkeys working, i most certainly do. How to accomplish that?
The page has originally been written for openSUSE 11.0 and the eepc701. Later it has been extened by various people with information about openSUSE 11.1 and other eeepcs. Many points on this page are subjective and only the peronal optionion of one of the authors. Examples: Usage of tmps or disabling swap files (and therefore disabling hibernate).
RPM's are for 10.3, and scripts, well, together with tha allready working stuff? Hmmm.
Most RPMs can found for newer openSUSE versions, too, or are obsolete since openSUSE 11.1.
Sounds not good to me...
We shall remove the old eeepc page and replace it with more valueable information. Maybe it would be a good idea, to use different pages for each openSUSE version, because many things are really different. On the other hand it would be nice to have different pages for different classes of eepcs. And there are special topics like openSUSE on SSDs which are interesting for its own.
Is there anybody that has the keys working on 901?
The scripts on the wiki page is nearly correct, but it depends on the wlan drivers used and the name of the sound device. Both are different for my eepc 900a.
I hope for 11.2 all is 'cool', and works without hassle... ;)
Using the Kernel 2.6.29 from Kernel:Head repository shows, that all Fn-Keys, except monitor switching work out of the box for my eeep 900A. So there is hope for openSUSE 11.2. Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Herbert Graeber schreef:
Am Mittwoch 25 März 2009 13:33:44 schrieb Oddball:
When i read the eeepc wiki page i get confused... There is all kind of 'old' stuf, so it is very difficult to 'know' what to use.. ;( Many things are allready in the kernel, but what to do if fi some hotkeys work, and others don't? I guess everybody that uses opensuse 11.1 on his/her eeepc, wants the hotkeys working, i most certainly do. How to accomplish that?
The page has originally been written for openSUSE 11.0 and the eepc701. Later it has been extened by various people with information about openSUSE 11.1 and other eeepcs. Many points on this page are subjective and only the peronal optionion of one of the authors. Examples: Usage of tmps or disabling swap files (and therefore disabling hibernate).
RPM's are for 10.3, and scripts, well, together with tha allready working stuff? Hmmm.
Most RPMs can found for newer openSUSE versions, too, or are obsolete since openSUSE 11.1.
Sounds not good to me...
We shall remove the old eeepc page and replace it with more valueable information. Maybe it would be a good idea, to use different pages for each openSUSE version, because many things are really different. On the other hand it would be nice to have different pages for different classes of eepcs. And there are special topics like openSUSE on SSDs which are interesting for its own.
Yes that sounds good. Maybe like: opensuse at eee-pc. from there nice target links to models and opensuse version? Or maybe links to other pages, if it would become to large or cluthered..
Is there anybody that has the keys working on 901?
The scripts on the wiki page is nearly correct, but it depends on the wlan drivers used and the name of the sound device. Both are different for my eepc 900a.
I hope for 11.2 all is 'cool', and works without hassle... ;)
Using the Kernel 2.6.29 from Kernel:Head repository shows, that all Fn-Keys, except monitor switching work out of the box for my eeep 900A. So there is hope for openSUSE 11.2.
Herbert
My 11.1 >11.1Factory failed in a failing xserver, so init3 is my only option there now. Now i bit myself into the partitioner to shrink my 11.1 / and /home, and install 11.1 from dvd next to the halfbroken factory version, to be able to get to the nessesary logfiles... It worked, i just finished the install, and changed networkmanager to ifup, and updated fonts and solver. atm the second update before first login is happening. So now on a 64GB RunCore ssd, i have XP, 11.1Fac, and 11.1Standard. The bootloader mentions both installation and windows, so it should be possible to boot all of them 'out of the box' ... ;) -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.29-rc8-5-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.2 Alpha 0 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 1" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Sonntag 29 März 2009 16:50:16 schrieb Oddball:
Herbert Graeber schreef:
[...]
We shall remove the old eeepc page and replace it with more valueable information. Maybe it would be a good idea, to use different pages for each openSUSE version, because many things are really different. On the other hand it would be nice to have different pages for different classes of eepcs. And there are special topics like openSUSE on SSDs which are interesting for its own.
Yes that sounds good. Maybe like: opensuse at eee-pc. from there nice target links to models and opensuse version? Or maybe links to other pages, if it would become to large or cluthered..
I think users want to have a cook book like reciept, how to enable the features of their eeepc. So having a page per (group of) eeepc model would be fine. It is nice for the writers of theses pages, too, because they can concentrate on the model they own. But these pages should all be similar structured and will contain some duplicate stuff. To reduce this duplication we need some basic information on the eepc main page and some additional pages of special topics, for example about SSDs and partitioning them. We shall try to separate things, which are neccessary to make the eeepc work and other optional things, which are a matter of taste.
Is there anybody that has the keys working on 901?
The scripts on the wiki page is nearly correct, but it depends on the wlan drivers used and the name of the sound device. Both are different for my eepc 900a.
I hope for 11.2 all is 'cool', and works without hassle... ;)
Using the Kernel 2.6.29 from Kernel:Head repository shows, that all Fn-Keys, except monitor switching work out of the box for my eeep 900A. So there is hope for openSUSE 11.2.
Herbert
My 11.1 >11.1Factory failed in a failing xserver, so init3 is my only option there now. Now i bit myself into the partitioner to shrink my 11.1 / and /home, and install 11.1 from dvd next to the halfbroken factory version, to be able to get to the nessesary logfiles... It worked, i just finished the install, and changed networkmanager to ifup, and updated fonts and solver. atm the second update before first login is happening. So now on a 64GB RunCore ssd, i have XP, 11.1Fac, and 11.1Standard. The bootloader mentions both installation and windows, so it should be possible to boot all of them 'out of the box' ... ;)
I have gone another way. I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules. Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Herbert Graeber schreef:
Am Sonntag 29 März 2009 16:50:16 schrieb Oddball:
Herbert Graeber schreef:
[...]
We shall remove the old eeepc page and replace it with more valueable information. Maybe it would be a good idea, to use different pages for each openSUSE version, because many things are really different. On the other hand it would be nice to have different pages for different classes of eepcs. And there are special topics like openSUSE on SSDs which are interesting for its own.
[...]
I think users want to have a cook book like reciept, how to enable the features of their eeepc. So having a page per (group of) eeepc model would be fine. It is nice for the writers of theses pages, too, because they can concentrate on the model they own. But these pages should all be similar structured and will contain some duplicate stuff. To reduce this duplication we need some basic information on the eepc main page and some additional pages of special topics, for example about SSDs and partitioning them.
We shall try to separate things, which are neccessary to make the eeepc work and other optional things, which are a matter of taste.
[.....] I have gone another way.
I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules.
Herbert
I will try this kernel, if i can find it.. ;) I look forward to see these pages develop... -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.29-rc8-5-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.2 Alpha 0 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 1" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Herbert Graeber schreef:
I have gone another way.
I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules.
Herbert
Would you mind telling me the url of that repo? I could not find it... -- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 75.3" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Herbert Graeber schreef:
I have gone another way.
I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules.
Herbert
Would you mind telling me the url of that repo? I could not find it...
Never mind, found it.. -- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 75.3" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Herbert Graeber schreef:
I have gone another way.
I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules.
Herbert
I have the latest installed, next to the original one. But as it not is instructed by hardware detection, it doesn't know about fi rt2860ST, and so it seems it does not exist... How did you get everything working? -- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.1.3 (KDE 4.1.3) "release 75.3" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Dienstag 31 März 2009 17:32:36 schrieb Oddball:
Herbert Graeber schreef:
I have gone another way.
I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules.
Herbert
I have the latest installed, next to the original one. But as it not is instructed by hardware detection, it doesn't know about fi rt2860ST, and so it seems it does not exist... How did you get everything working?
If the rt2860ST driver is already contained in kernel 2.6.29, it should be detected. I your driver comes from an external module, you have to find a RPM built for 2.6.29, or you have to build the driver yourself. I had to enter yast network settings turn off NetworkManager, press OK, enter a second time and reactivate NetworkManager. After that the ath5k driver I needed for my eeePC works fine. Be careful with updating the kernel. From time to time the kernels from Kernel:HEAD do not work properly, but most of time time they work well. And maybe at some point one has to upgrade other supporting software, too. Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Herbert Graeber schreef:
Am Dienstag 31 März 2009 17:32:36 schrieb Oddball:
Herbert Graeber schreef:
I have gone another way.
I have installed openSUSE 11.1 and replaced to kernel only by the latest one from the Kernel:HEAD repository. Things that worked without problems, which havent with the original kernel: Hotkeys, except xrandr handling, WLAN inclusive rfkill support (no madwifi required anymore!). The only thing that I had to configure is the load of the pciehp and rfkill-input modules.
Herbert
I have the latest installed, next to the original one. But as it not is instructed by hardware detection, it doesn't know about fi rt2860ST, and so it seems it does not exist... How did you get everything working?
If the rt2860ST driver is already contained in kernel 2.6.29, it should be detected. I your driver comes from an external module, you have to find a RPM built for 2.6.29, or you have to build the driver yourself.
I had to enter yast network settings turn off NetworkManager, press OK, enter a second time and reactivate NetworkManager. After that the ath5k driver I needed for my eeePC works fine.
Be careful with updating the kernel. From time to time the kernels from Kernel:HEAD do not work properly, but most of time time they work well. And maybe at some point one has to upgrade other supporting software, too.
Herbert
rt2860ST is not onboard than helas... i would have had to configure it myself.. Henne has these if irc... I would like it more that the modules were seperate: called: eee-pc kernel modules, and that all needed would be included. And be maintained ofcourse.... So all one had to do was install these, and Hop! Ready to go. Hotkeys, camera, network, what would there be more? -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.29-rc8-5-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.2 Alpha 0 (x86_64) KDE: 4.2.1 (KDE 4.2.1) "release 1" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Herbert Graeber schreef:
If the rt2860ST driver is already contained in kernel 2.6.29, it should be detected. I your driver comes from an external module, you have to find a RPM built for 2.6.29, or you have to build the driver yourself.
I had to enter yast network settings turn off NetworkManager, press OK, enter a second time and reactivate NetworkManager. After that the ath5k driver I needed for my eeePC works fine.
Be careful with updating the kernel. From time to time the kernels from Kernel:HEAD do not work properly, but most of time time they work well. And maybe at some point one has to upgrade other supporting software, too.
Herbert
rt2860ST is not onboard than helas... i would have had to configure it myself.. Henne has these if irc... I would like it more that the modules were seperate: called: eee-pc kernel modules, and that all needed would be included. And be maintained ofcourse.... So all one had to do was install these, and Hop! Ready to go. Hotkeys, camera, network, what would there be more?
Rt2860 is not recognised, but the socalled 'userspace configuration module' is installed. Helas i do not know how to invoke it..:( Networkmanagement does not find it: EEEPC-901-ROB:/home/oddball # iwconfig lo no wireless extensions. eth0 no wireless extensions. EEEPC-901-ROB:/home/oddball # rcnetwork restart Shutting down network interfaces: eth0 device: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) done Shutting down service network . . . . . . . . . done Starting the NetworkManager done EEEPC-901-ROB:/home/oddball # iwconfig lo no wireless extensions. eth0 no wireless extensions. EEEPC-901-ROB:/home/oddball # dhcpcd ra0 err, ra0: ioctl SIOCGIFHWADDR: No such device EEEPC-901-ROB:/home/oddball # ifconfig ra0 ra0: error fetching interface information: Device not found EEEPC-901-ROB:/home/oddball # iwlist ra0 scan ra0 Interface doesn't support scanning. EEEPC-901-ROB:/home/oddball # ifconfig ra0 up ra0: unknown interface: Onjuist apparaat EEEPC-901-ROB:/home/oddball # iwlist ra0 scan ra0 Interface doesn't support scanning. EEEPC-901-ROB:/home/oddball # iwconfig ra0 essid linksys Error for wireless request "Set ESSID" (8B1A) : SET failed on device ra0 ; No such device. But the volume hotkeys work: up down, not mute. Network: can't verify.. Sleep: works. Screen brightness : works F6: nothing happens.. -- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.27.19-3.2-pae i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.2.1 (KDE 4.2.1) "release 106" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch 01 April 2009 19:34:32 schrieb Oddball:
Oddball schreef:
Herbert Graeber schreef:
If the rt2860ST driver is already contained in kernel 2.6.29, it should be detected. I your driver comes from an external module, you have to find a RPM built for 2.6.29, or you have to build the driver yourself.
I had to enter yast network settings turn off NetworkManager, press OK, enter a second time and reactivate NetworkManager. After that the ath5k driver I needed for my eeePC works fine.
Be careful with updating the kernel. From time to time the kernels from Kernel:HEAD do not work properly, but most of time time they work well. And maybe at some point one has to upgrade other supporting software, too.
Herbert
rt2860ST is not onboard than helas... i would have had to configure it myself.. Henne has these if irc... I would like it more that the modules were seperate: called: eee-pc kernel modules, and that all needed would be included. And be maintained ofcourse.... So all one had to do was install these, and Hop! Ready to go. Hotkeys, camera, network, what would there be more?
Rt2860 is not recognised, but the socalled 'userspace configuration module' is installed. Helas i do not know how to invoke it..:( Networkmanagement does not find it:
I have found another important thing I have done for my eeepc. WLAN modules are anebled/disabled by hotplugging them. But the BIOS doesn't tell this via ACPI. So one has to force the load of module pciehp. I do this with a /etc/modprobe.d/eeepc file: options pciehp pciehp_force=1 install eeepc-laptop /sbin/modprobe pciehp; /sbin/modprobe -i eeepc-laptop $CMDLINE_ARGS The reason for doing it this way is, that the cahnge to the system is isolated to one single file. It is easier to make a rpm when on can install an additional file, than modifying an existing one. Another reason is, that the first line of this file is needed anyway.
[...]
But the volume hotkeys work: up down, not mute.
You need a script for this with plain openSUSE 11.1. The new kernel generates the proper scan codes, which are recognized by KDE. Even a volume bar is shown. Nice, isn't it? :-)
Network: can't verify..
Hope I can help with this.
Sleep: works. Screen brightness : works
Does already for openSUSE 11.1 outnof the box
F6: nothing happens..
This one is used by ASUS for loading the system monitor (Same as Ctrl-ESC in KDE). I consider this free for arbitary use (Camera on/off?). I am trying to write a proper script for F5. But somehow the eepc behaves completely different wether the external Monitor is plugged in before booting, or after booting. Strange. Cheers Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Herbert Graeber schreef:
I have found another important thing I have done for my eeepc. WLAN modules are anebled/disabled by hotplugging them. But the BIOS doesn't tell this via ACPI. So one has to force the load of module pciehp. I do this with a /etc/modprobe.d/eeepc file:
options pciehp pciehp_force=1 install eeepc-laptop /sbin/modprobe pciehp; /sbin/modprobe -i eeepc-laptop $CMDLINE_ARGS
The reason for doing it this way is, that the cahnge to the system is isolated to one single file. It is easier to make a rpm when on can install an additional file, than modifying an existing one. Another reason is, that the first line of this file is needed anyway.
What should happen when creating this file is that the rt2860 would be loaded, so it could be detected, or do i understand this wrong here? I did create the file, but how to get it read? Because still no hw-info on rt2860, according to yast2 networksettings. Why does one kernel find the wifi, and another one does not? -- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.29-56-default i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.2.1 (KDE 4.2.1) "release 106" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball wrote:
Herbert Graeber schreef:
I have found another important thing I have done for my eeepc. WLAN modules are anebled/disabled by hotplugging them. But the BIOS doesn't tell this via ACPI. So one has to force the load of module pciehp. I do this with a /etc/modprobe.d/eeepc file:
options pciehp pciehp_force=1 install eeepc-laptop /sbin/modprobe pciehp; /sbin/modprobe -i eeepc-laptop $CMDLINE_ARGS
The reason for doing it this way is, that the cahnge to the system is isolated to one single file. It is easier to make a rpm when on can install an additional file, than modifying an existing one. Another reason is, that the first line of this file is needed anyway.
What should happen when creating this file is that the rt2860 would be loaded, so it could be detected, or do i understand this wrong here? I did create the file, but how to get it read? Because still no hw-info on rt2860, according to yast2 networksettings. Why does one kernel find the wifi, and another one does not?
Firmware update? I had a ralink device hardware detection problem due to lack of firmware in the past. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schrieb:
Herbert Graeber schreef:
I have found another important thing I have done for my eeepc. WLAN modules are anebled/disabled by hotplugging them. But the BIOS doesn't tell this via ACPI. So one has to force the load of module pciehp. I do this with a /etc/modprobe.d/eeepc file:
options pciehp pciehp_force=1 install eeepc-laptop /sbin/modprobe pciehp; /sbin/modprobe -i eeepc-laptop $CMDLINE_ARGS
The reason for doing it this way is, that the cahnge to the system is isolated to one single file. It is easier to make a rpm when on can install an additional file, than modifying an existing one. Another reason is, that the first line of this file is needed anyway.
What should happen when creating this file is that the rt2860 would be loaded, so it could be detected, or do i understand this wrong here? I did create the file, but how to get it read? Because still no hw-info on rt2860, according to yast2 networksettings. Why does one kernel find the wifi, and another one does not?
The wlan driver module will not be loaded when you boot the eeepc with wlan off, because the device is non-existent for the kernel, similar to an not plugged PCMCIA card. Without the pciehp module lodaed it will not be detected, when you activate WLAN useing the the hotkey. Even when you boot your eeepc with WLAN turned on, WLAN will work only after boot, not after turning it off and on again, or after suspend/hibernate. There are scripts which help to fix these issues, but force loading the pciehp module simpliy makes it work. Suspend and hibernate need no script at all and for the WLAN-hotkey, you need a script for kernels before 2.6.28 only, that simply switches WLAN on and of via /proc interface. Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 03 April 2009 08:13:16 am Herbert Graeber wrote: ...
but force loading the pciehp module simpliy makes it work. ...
Hi Herbert, have you tried to include module in: /etc/sysconfig/kernel MODULES_LOADED_ON_BOOT="" and add option line in the file named as module in: /etc/modprobe.d/ Would that work? I never had problem with laptop, so I never tried above. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schreef:
On Friday 03 April 2009 08:13:16 am Herbert Graeber wrote: ...
but force loading the pciehp module simpliy makes it work. ...
Hi Herbert,
have you tried to include module in: /etc/sysconfig/kernel MODULES_LOADED_ON_BOOT="" and add option line in the file named as module in: /etc/modprobe.d/
Would that work? I never had problem with laptop, so I never tried above.
That is nice, i have been thinking of that myself this afternoon.. But if i understand correctly:
There is just a kernel option which is likely incorrectly set, CONFIG_STAGING_EXCLUDE_BUILD=y which should be set to n to be able to load the driver..
-- Have a nice day ;) Oddball aka M9. OS: Linux 2.6.29-56-default i686 Huidige gebruiker: oddball@EEEPC-901-ROB Systeem: openSUSE 11.1 (i586) KDE: 4.2.2 (KDE 4.2.2) "release 110" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 03 April 2009 12:52:34 pm Oddball wrote:
Rajko M. schreef:
On Friday 03 April 2009 08:13:16 am Herbert Graeber wrote: ...
but force loading the pciehp module simpliy makes it work. ...
Hi Herbert,
have you tried to include module in: /etc/sysconfig/kernel MODULES_LOADED_ON_BOOT="" and add option line in the file named as module in: /etc/modprobe.d/
Would that work? I never had problem with laptop, so I never tried above.
That is nice, i have been thinking of that myself this afternoon..
But if i understand correctly:
There is just a kernel option which is likely incorrectly set, CONFIG_STAGING_EXCLUDE_BUILD=y which should be set to n
to be able to load the driver..
I don't know for Factory. The 11.1 has no such option defined at all and loads modules as requested. Try to see output of: grep CONFIG_STAGING_EXCLUDE_BUILD /boot/config-`uname -r` The `uname -r` will add version of currently running kernel behind config- . Watch for apostrophe type :-) or just copy and paste above command, it works fine with en-US locale. You can try command to see what it gives: uname -r It should be only version string for current kernel. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag 03 April 2009 19:41:47 schrieb Rajko M.:
On Friday 03 April 2009 08:13:16 am Herbert Graeber wrote: ...
but force loading the pciehp module simpliy makes it work. ...
Hi Herbert,
have you tried to include module in: /etc/sysconfig/kernel MODULES_LOADED_ON_BOOT="" and add option line in the file named as module in: /etc/modprobe.d/
Would that work? I never had problem with laptop, so I never tried above.
No, at least the options line in /etc/modprobe.d/eeepc is neccessary. The module loads without that, but it doesn't work without the pciehp_force option. Forcing the load vi MODULES_LOADED_ON_BOOT does work then, too, but I think loading pciehp together with eeepc-laptop is more elegant, because everything is in _one_ file. That's easier to install than modifing one _global_ configuration file. Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Dave Plater -
Henne Vogelsang -
Herbert Graeber -
Ludwig Nussel -
Oddball -
Rajko M.