Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The (loaded) module asus_eee stops eee-control-daemon from loading.
Blacklisting asus_eee did not work for me (eeebuntu based on 9.04, on an original 701), so I resorted to brute force with this in my /etc/rc.local file
The (loaded) module asus_eee stops eee-control-daemon from loading.
Blacklisting asus_eee did not work for me (eeebuntu based on 9.04, on an original 701), so I resorted to brute force with this in my /etc/rc.local file
eeeBu, if you cannot load the file in a read-write fashion, it's likely because it's a root-owned file, and you are trying to edit it as a regular user. rc.local is such a root owned file.
to load /etc/rc.local into gedit text editor as root, try:
Linux generally gives much more informative error messages than win, and will try to tell you what went wrong. You can see these messages only if you launch an application, by its name, in a terminal.
So, open a terminal and do
Code:
sudo /usr/bin/eee-control-daemon
What happens?
What does it say?
What are the errors reported (if any)?
Nope nothing, still the same. Ok so heres the lsmod from the terminal
Something is broken. You do not have any eee-specific modules loaded (eg eeepc_laptop)
Part of the trouble is that you are running ubuntu 9.10, and I wouldn't yet consider this "fit for the purpose". It's OK for "testing" though. [That's my personal opinion, and I do not need, or wish to start, a flamewar].
I am running "Kubuntu 8.04 (Long Term Support) as my workhorse on my vaio laptop, and 9.04 on my eee (because it does Global Satellite Positioning out of the box). 6.06 still runs my server, but it is not broken, runs minimal services on my LAN only, is firewalled, and I see no reason to upgrade it.
kubuntu 8.04 (with KDE 3.x) on the vaio is absolutely stable, works and never fails me. I like this.
ubuntu 9.04 (with gnome) on the eee701 is a bit unstable, but still useable, and fun for applications (like tangoGPS) that will not work with earlier versions.
I am not touching 9.10 until they have applied a load of fixes. Probably I will not "upgrade" until they offer the next LTS distro.
You have a choice here:
- Remember that the EEE(s) have weird hardware.
- Run the "latest & greatest" 'buntu (9.10) and you can expect faults.
- Run eeebuntu (9.04) and find it "just works", but the most recent releases of some applications will not be easily (one-click) available. They are installable if you do a bit of searching though.
Quote:
btw is this [lsmod] the equivalent of taskmanager in windows yeh?
Well, No.
It just tells you what kernel modules are loaded.
In KDE I can do <CTRL> <ESCAPE> and see in the GUI a list of all processes that are running, and then select the ones I want to kill.
Gnome doesn't offer me this. I have to do ps -Al in a terminal, find the PID of the errant process and then kill it from the command line
The bottom line is that if you want the most up-to-date software, install 9.10. If you want stability and reliability, install something just that bit older.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.