Discussion forums for Arch Linux, a simple, lightweight linux distribution.
You are not logged in.
mgp wrote:
Hi,
I am having problems using the repositories in the wiki article for the zen eee kernel. What are the working repos for this file? Should I just download manualy from the google code above to update my kernel?
Thanks uin advance,
Michael
Hi!
The archkernel now supports everything in eee 901, so you dont need the zen kernel (the reposityory is not avail anymore afaik)
So, just run the standard kernel and you have a go!
Offline
Thanks for the explanation bud!
Thanks, also, to everyone who was patching and option selecting the eee specific kernels! Your work has been very useful while waiting for the archkernel to catch up.
Offline
Hello,
I have an Eeepc 901. I use stock kernel.
I have a problem, I think with eeepc_laptop.
If I load this module in rc.local file, screen became blank just before login prompt and Eeepc is totaly unusable.
If I load this module in rc.conf, the boot work fine and I can enter login and pass, everything work fine.
In the two situation I have sometimes an problem when I start my laptop: It won't start, I have nor bios display, nor grub. I need to unplug ac-adapter and battery, and waiting a long time.
Somebody has same problem? What is the solution for avoiding this two problems?
Thank you very much.
Gwenhaël
Offline
I blacklist eeepc_laptop in rc.conf and load in the background from rc.local and it works fine for me (stock kernel): my rc.local looks like this:
modprobe eeepc_laptop &
Welcome to the forums!
Last edited by jasonwryan (2009-08-10 02:36:57)
Offline
When I've installed Archlinux on my Eeepc, I have made exactly the same thing.
But I have a problem with this solution, the screen become blank at the boot end and I have no other solution than stop with pressing on power button.
This is why I load eeepc_laptop in rc.conf file.
Could you send me the complete lsmod result, perhaps I've a conflict with an other module?
Gwenhaël
Offline
Here you go:
Module Size Used by i915 183016 1 drm 154656 2 i915 i2c_algo_bit 5864 1 i915 eeepc_laptop 13240 0 rfkill 10640 3 eeepc_laptop ipv6 277972 18 snd_seq_dummy 2696 0 snd_seq_oss 31168 0 snd_seq_midi_event 7012 1 snd_seq_oss snd_seq 53744 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event joydev 10400 0 snd_seq_device 6768 3 snd_seq_dummy,snd_seq_oss,snd_seq uvcvideo 61040 0 videodev 36544 1 uvcvideo v4l1_compat 15688 2 uvcvideo,videodev usb_storage 51456 0 snd_hda_codec_realtek 206504 1 snd_pcm_oss 40352 0 snd_mixer_oss 17540 1 snd_pcm_oss snd_hda_intel 26664 0 iTCO_wdt 10952 0 iTCO_vendor_support 3080 1 iTCO_wdt fan 4392 0 snd_hda_codec 71716 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 7656 1 snd_hda_codec snd_pcm 73672 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec uhci_hcd 23540 0 video 19832 1 i915 output 2884 1 video psmouse 59644 0 thermal 13888 0 processor 35800 2 intel_agp 27484 1 snd_timer 21100 2 snd_seq,snd_pcm snd 58436 11 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_codec_realtek,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer soundcore 6848 1 snd snd_page_alloc 8876 2 snd_hda_intel,snd_pcm sg 27928 0 ehci_hcd 35664 0 button 5556 0 i2c_i801 9656 0 rt2860sta 561272 1 serio_raw 5704 0 evdev 10176 9 agpgart 32756 3 drm,intel_agp pcspkr 2372 0 atl1e 33240 0 usbcore 150192 5 uvcvideo,usb_storage,uhci_hcd,ehci_hcd i2c_core 22776 4 i915,drm,i2c_algo_bit,i2c_i801 battery 10984 0 ac 4360 0 fuse 60896 0 rtc_cmos 11212 0 rtc_core 18048 1 rtc_cmos rtc_lib 2500 1 rtc_core ext2 69036 2 mbcache 7080 1 ext2 sd_mod 27328 4 pata_acpi 4228 0 ata_generic 4680 0 ata_piix 23080 2 libata 168012 3 pata_acpi,ata_generic,ata_piix scsi_mod 110708 4 usb_storage,sg,sd_mod,libata
Offline
hello,
your lsmod didn't show acpi-cpufreq. It's normal?
On the wiki page, MODULES contain acpi-cpufreq.
My lsmod seem not different than your.
If someone help me.
Offline
please can someone update wiki in a FSB clocking/volting sections? moving to the blind's (and later to the stock) kernel and acpi-eeepc-generic cost me about hour and half battery time. well i know about eee-control but i don't like it's gnome dependencies and it's far less customisable
Offline
I have compiled the 2.6.30-zen4 kernel for eeepc 901 with eee module built in for fsb management. In case anyone is interested, you can download it from
http://zen-kernel-eee-901-arch.googleco … pkg.tar.gz
and install it using pacman -U.
I will upload the pkgbuild and sources later when I have time.
P.S.: 2.6.30-zen4 has atom architechture support, which I have enabled.
Last edited by ashishp (2009-09-14 13:45:10)
Offline
Hi,
I'm really confused by Asus Eee PC 901 article on ArchWiki. What do I have to do to get CPU scaling to work? Does acpi-eeepc-generic support cpu scaling (probably not)? Or should I install something else.
As you've probably noticed, I'm new to Arch ![]()
b3d3r
Offline
Hi b3d3r,
To get the CPU scalling, all you need is to load a kernel module. On the 901 (which uses the intel Atom processor) the module is "acpi_cpufreq". You will also need a 'governor' to tell the kernel what freqeuncy to put the processor. You have the choice between performance where the frequency is always the fastest, powersave where the frequenecy is always the slowest available, and ondemand where it jumps from one to the other depending on the need. You will need to load the kernel module on the governor you want to use (or all of them if you want to switch from one governor to the other):
sudo modprobe acpi_cpufreq sudo modprobe cpufreq_ondemand sudo modprobe cpufreq_powersave sudo modprobe cpufreq_performance
I suggest the ondemand governor, as its the easiest to setup (you don't have anything to worry about) and it should give you the max of your battery while preserving performances. Add the modules to your rc.conf file in the MODULES=() section:
/etc/rc.conf wrote:
[...]
MODULES=([...] acpi_cpufreq cpufreq_ondemand [...])
[...]
Note that if you load different governor modules, you can switch between them using "cpufreq-set" command. You can always type "cpufreq-info" to get more information.
acpi-eeepc-generic does not touch cpu scaling at all. It is used to setup special actions of the eee, like Fn+Fx keys (volume/brightness up/down, toggle wireless, lid close, etc).
Now maybe you got confused with FSB scaling, which is not the same thing as CPU scaling. FSB stands for Front Side Bus. It is the connection between the processor and other parts of the motherboard, for example memory. Faster FSB will mean faster memory access, but more power usage. The Central Processing Unit (CPU) frequency can be changed to preserve power. A slower CPU frequency will do its calculation in more time then when the frenquency is higher, so as FSB scaling, CPU scaling will make things slower but save more power.
Version 0.9 of acpi-eeepc-generic does not control the FSB scaling nor CPU scalling (remember, CPU scalling is controled automatically by cpufreq, the module you have already loaded). I'm in the process of adding FSB scaling control to acpi-eeepc-generic: you will be able to choose which profile you want to use. You can follow the developpement from the google code page.
Hope that helped ![]()
Offline
After kernel-update (2.6.31), acpi-eeepc-generic (or the messages) are reacting a little bit strange. First of all, I had to change ALSA_MUTE_MIXER to Master, because something in Alsa changed and iSpeaker and LineOut are no more (but I see Headphone and Speaker now), as I can see. If I mute now, a message says to me "unmute 100%", but I'm muting it. Same if I unmute it.
Also, shortly after every message (like mute/unmute/toggle volume [which goes down by 10% instead of 5% for every step {Fn+F12}], there is a "no message, no action" message.
Is there a way to get it back to normal? (Right message without "no message", right volume up/down steps)
And i've noticed: If wifi is enabled and I'm trying to disable it with Fn+F2, it enables it first and after a second Fn+F2, it finally disables it. Is there also a way to get it back to normal?
Offline
Running zodmaner's kernel-eeepc-901-kms, just upgraded a few minutes ago to the latest Xorg and installed various drivers updates with the testing repo enabled.
Upon logging into Gnome, the screen basically goes wonky. This also occurs in the vanilla kernel, as well as zodmaner's kernel-eeepc-901, with the xorg.conf that I've been using for a long time as well as using no config at all.
So I'm just wondering if anyone else is having this issue? Looks like I'm going to have to downgrade.
Offline
@ChemBro
I checked it and you are right. Alsa mixers are ALWAYS changing name. Its really annoying. Not only on the eee but also on another laptop of mine. I wish they would settle to one set of mixers and then STOP freaking changing it!!!
I changed how volume is managed. You now only have to choose the set of mixers (you can have one or many) you want to mute and those you want to change the volume. You can test this if you want: its in the 1.0 branch (see svn on google code page)
If you find any other problem, like the wifi one, please report it on the google code page's issue section, so I can keep track of it.
Offline
kud0h wrote:
Running zodmaner's kernel-eeepc-901-kms, just upgraded a few minutes ago to the latest Xorg and installed various drivers updates with the testing repo enabled.
Upon logging into Gnome, the screen basically goes wonky. This also occurs in the vanilla kernel, as well as zodmaner's kernel-eeepc-901, with the xorg.conf that I've been using for a long time as well as using no config at all.
So I'm just wondering if anyone else is having this issue? Looks like I'm going to have to downgrade.
I haven't upgrade X.org to the newest version yet, but for now you could try using my non-KMS kernel to see if problem is caused by KMS.
Will try to upgrade and test thing out as soon as possible.
Offline
To any who wants to test KMS or easily disable it without too much fuss. Instead of putting "options i915 modeset=1" into /etc/modprobe.d/modprobe.conf and rebuilding the initramfs, just add this "i915.modeset=1" to your kernel line in grub. That way, if something goes wrong, you can always hit a key while grub is booting (to deactivate the timer) select the kernel to boot (should be the already selected one) type "e" to edit the line, replace the "=1" by "=0" of the 915.modeset, press enter to confirm and then "b" to boot it.
I always prefer putting stuff in grub like this so it is dead easy to temporarly disable if needed.
Offline
zodmaner wrote:
kud0h wrote:
Running zodmaner's kernel-eeepc-901-kms, just upgraded a few minutes ago to the latest Xorg and installed various drivers updates with the testing repo enabled.
Upon logging into Gnome, the screen basically goes wonky. This also occurs in the vanilla kernel, as well as zodmaner's kernel-eeepc-901, with the xorg.conf that I've been using for a long time as well as using no config at all.
So I'm just wondering if anyone else is having this issue? Looks like I'm going to have to downgrade.I haven't upgrade X.org to the newest version yet, but for now you could try using my non-KMS kernel to see if problem is caused by KMS.
Will try to upgrade and test thing out as soon as possible.
I have since found out what the problem was: the latest version of Compiz, after disabling it, everything runs fine again. Now the only problem that remains is new intel driver performance is pretty terrible, although I believe this is due largely in part to the drivers themselves, releases tend to range from pretty average to abysmal, anyway.
Thanks for your reply.
Offline
@big_gie
Is it possible to change cpu frequency "on the fly"?
Offline
@b3d3r
Yes: you need to change cpufreq's governor using the tool "cpufreq-set" (install cpufrequtils). I suggest you to use the "ondemand" governor, as this will automatically scale the frequency based on the system load. For this, type:
cpufre-set -g ondemand
You can see more info using "cpufreq-info".
If you want to change to a specific frequency, use the "userspace" governor:
modprobe cpufreq_userspace
cpufreq-set -g userspace
Check google for even more control ![]()
Offline
Thanks
It was actually working before but I didn't notice it, cpufreq-info shows that I have 2 CPUs (?) and I was always looking at the second one ![]()
One other thing: what's your battery life? When I was using Windows (with wifi turned off and minimum brightness) I got about 9 hours of battery life (this was what Windows showed). Now I'm using Arch and acpi command is only showing about 7 hours. Is this because?
1. Linux is consuming more power? Does it depend on file system? I use ext4 with journaling.
2. Linux/Windows consume the same amount of power but have different battery monitors? If yes witch one is more accurate?
I assume that my battery has the same capacity as when I was using Windows ![]()
Last edited by b3d3r (2009-10-22 18:22:27)
Offline
b3d3r wrote:
I assume that my battery has the same capacity as when I was using Windows
You might want to check that. My "Last Full" capacity is consistently 18% down on its design capacity.
Offline