Arch on Eee PC

ighea · 2008-03-12 22:25:44

vomix wrote:

ighea wrote:
Try using AP_COMMAND="terminal -e htop".
Nope, it doesn't work, even with a simple thing like AP_COMMAND=thunar.
After installing your package, pacman said something about the /etc/acpi/events/anything file. In fact, I didn't really understand, and modified the file as marked, but I'm not sure. It's maybe related to those changes?

This is most likely issue with the current way used to verify X session and user who's running it. Could you please provide output of command "who" while running X and your locale settings. I may assume that the external display switching is not working either for you?

faelar · 2008-03-13 19:46:24

same here with :
AP_COMMAND=sakura -e htop
and who return my user name on vc/1

ighea · 2008-03-13 20:03:15

faelar wrote:

same here with :
AP_COMMAND=sakura -e htop
and who return my user name on vc/1

So you are saying that while running X "who" only reports user on vc/1 and nothing more? Just one line? In which vc should your X session be running and how do you login to / start your X?

Nothing similar to following?

[ighea@eee ~]$ who
ighea    vc/7         2008-03-13 21:30 (:0)

Currently "vc/7" and "(:0)" are important because those are used for determine user who's running the X session. Maybe I'll try to do some kind of tweak to overcome this issue with all users, I just need more information.

vomix · 2008-03-13 20:32:00

In my case, the who command didn't show anything, that's weird!

Here's the results of the who -a command:

[eko@nodrom ~]$ who -a
                        2008-03-13 20:16               469 id=rc    term=0 exit=0
           system boot  2008-03-13 20:16
           run-level 3  2008-03-13 20:16                   last=S
                        2008-03-13 20:16              1135 id=rm    term=0 exit=0
LOGIN      vc/1         2008-03-13 20:16              1525 id=c1
LOGIN      vc/2         2008-03-13 20:16              1526 id=c2
LOGIN      vc/3         2008-03-13 20:16              1527 id=c3
LOGIN      vc/4         2008-03-13 20:16              1528 id=c4
LOGIN      vc/5         2008-03-13 20:16              1529 id=c5
LOGIN      vc/6         2008-03-13 20:16              1530 id=6
                        2008-03-13 20:16              1530 id=c6

I'm logging with slim, using exec openbox-session in my .xinitrc file.

PS: Ighea, what do you mean by sharing my locales settings?

[EDIT]
And here are the results after login without slim, using the startx command:

[eko@nodrom ~]$ who
eko      vc/1         2008-03-13 21:32

As you can see, there's no (:0) in it, it must be our problem.

[eko@nodrom ~]$ who -a
                        2008-03-13 20:16               469 id=rc    term=0 exit=0
           system boot  2008-03-13 20:16
           run-level 3  2008-03-13 20:16                   last=S
                        2008-03-13 20:16              1135 id=rm    term=0 exit=0
eko      - vc/1         2008-03-13 21:32 00:02        1525
LOGIN      vc/2         2008-03-13 20:16              1526 id=c2
LOGIN      vc/3         2008-03-13 20:16              1527 id=c3
LOGIN      vc/4         2008-03-13 20:16              1528 id=c4
LOGIN      vc/5         2008-03-13 20:16              1529 id=c5
LOGIN      vc/6         2008-03-13 20:16              1530 id=6
                        2008-03-13 20:16              1530 id=c6

[/EDIT]

Last edited by vomix (2008-03-13 20:41:20)

faelar · 2008-03-13 22:06:00

who

I login directly in the first console, it starts X for me (so no login manager involved).

ighea · 2008-03-15 00:08:44

Lets hope that task manager/AP-button (Fn-F6) now works with everybody.
I have also done some minor modifications like all configurable options can now be found in /etc/acpi/eee.conf.

http://kapsi.fi/~ighea/eee/acpi-eee/acp … pkg.tar.gz

vomix · 2008-03-16 14:43:06

It's fine now, thank you!

faelar · 2008-03-16 20:46:51

It works
External monitor too.
I think the problem for X was :

Load "extmod"

If I look to Ighea's one I've got :

Load "dbe"

instead.
Other options I changed/added :

    Option      "XAANoOffscreenPixmaps" "true"
    Option      "AddARGBGLXVisuals"     "true"

...

Section "Extensions"
       Option         "Composite"   "Enable"
EndSection

jmtan · 2008-03-17 15:06:44

Hi guys, relatively new user to Arch Linux but installed it on my eeepc anyway. I'm currently using toofishes kernel and am encountering the same old problem with snd_hda_intel not being unloaded during shutdown. The rmmod method listed in the wiki isn't working, and I've read toofishes explanation of the problem, but is there another workaround for it or is everyone just holding down the power button during shutdown?

Thanks for all the helpful information listed in this thread and the wiki btw, and of course for kernel-eee

zodmaner · 2008-03-17 17:44:26

jmtan wrote:

Hi guys, relatively new user to Arch Linux but installed it on my eeepc anyway. I'm currently using toofishes kernel and am encountering the same old problem with snd_hda_intel not being unloaded during shutdown. The rmmod method listed in the wiki isn't working, and I've read toofishes explanation of the problem, but is there another workaround for it or is everyone just holding down the power button during shutdown?
Thanks for all the helpful information listed in this thread and the wiki btw, and of course for kernel-eee

EDIT: Depreciated. Please use toofishes fix below.

Last edited by zodmaner (2008-03-19 07:53:10)

ighea · 2008-03-18 20:30:46

Once again a small update for the acpi-scripts.
I added vbetool as dependency and modified the suspend script so that all virtual terminals should now be usable after suspend. Also the screen brightness is now restrored correctly.
I even noticed faster resuming times from the suspend with this setup, but it might all be just my imagination.

http://kapsi.fi/~ighea/eee/acpi-eee/acp … pkg.tar.gz

toofishes · 2008-03-18 22:02:55

zodmaner wrote:

jmtan wrote:
Hi guys, relatively new user to Arch Linux but installed it on my eeepc anyway. I'm currently using toofishes kernel and am encountering the same old problem with snd_hda_intel not being unloaded during shutdown. The rmmod method listed in the wiki isn't working, and I've read toofishes explanation of the problem, but is there another workaround for it or is everyone just holding down the power button during shutdown?
Thanks for all the helpful information listed in this thread and the wiki btw, and of course for kernel-eee
As a temporary solution until a proper fix arrives, you could recompile toofishes's kernel and made snd_hda_intel driver a module.

No, I've said this should not be necessary, and I think I found a "fix".

echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind

Try adding the above to your rc.local.shutdown in place of the rmmod line. You will still have to move the call of rc.local.shutdown below the daemons line if you want to save your ALSA levels. Of course the above assumes your sound card is on the same PCI bus address as mine- it should be, but to check you can use lspci.

Feedback appreciated if this works for everyone (and of course if it doesn't work).

I'm planning on having a new kernel out soon that adds some of the device mapper/crypto stuff for those that requested it. Sorry for the long wait but I have been quite busy with other stuff.

EDIT: added stuff about lspci/bus numbers

Last edited by toofishes (2008-03-18 22:03:43)

zodmaner · 2008-03-19 07:51:07

I have try your fix and it seems to work fine on my Eee. Thank you toofishes, I really appreciated your work. Now we don't have to use rmmod hack anymore (finally!).

Also, concerning the ALSA levels, I've found that if you stop ALSA daemon before apply the fix by edit rc.local.shutdown file to look something like this:

# /etc/rc.local.shutdown

# Stop ALSA daemon
/etc/rc.d/alsa stop

# Then apply the fix
echo -n "0000:00:1b.0" > /sys/bus/pci/drivers/HDA\ Intel/unbind

Then the machine will save ALSA levels and shutdown just fine without us having to edit /etc/rc.shutdown file.

Last edited by zodmaner (2008-03-19 07:56:25)

jmtan · 2008-03-19 12:35:31

It works perfectly, thank you both for your replies!

faelar · 2008-03-19 17:16:57

Only one successfull shutdown means nothing. But if it works we are near to perfection

Now some questions :
Do I really need to add alsa stop in rc.local.shutdown ? (I need to check but I remember no problem with the daemon when exiting...)
How can I change asus osd ?
Will acpi-eee be added to toofishes' repo ?

Again, I would like to thank everyone in this topic ! You keep it simple, futhermore you make me understand what a great linux community is !

brncmp · 2008-03-20 00:52:45

Thanks for everybody hard work.

Is there a way to make the eee wake when the lid is opened instead of having to touch the power button. This is the first laptop I have seen like this.

I have also noticed that the batteries drain quickly (<10 hrs) when the eee is asleep (lid closed) and will eventually shut down. When this happens is it a clean shutdown? I assume, this is because power is needed to keep things in ram?

If I set up suspend to disk will this help? Can I use a usb flash drive for this, do I have to partition it as swap (I don't care about the life)?

Also, where would be a good place for people to post their apps, configs, wallpapers, and sreenshots that they use on there eee. I have found several great apps and ideas else where in the forums (not eee specific). I think it would be a good idea to try to get a list of sorts in a place so other people could find easy. I think that this thread should keep to hardware and kernel. What do you think?

Sorry for all the questions and rambling.
brncmp

ighea · 2008-03-21 18:39:23

faelar wrote:

Now some questions :
Do I really need to add alsa stop in rc.local.shutdown ? (I need to check but I remember no problem with the daemon when exiting...)
How can I change asus osd ?

You don't really have to stop the alsa daemon at all, it is mostly used to store your current mixer states. If you have alsa in rc.conf's DAEMONS array it will be shut down automatically. Only shutting down the sound device by removing the module or doing as shown by toofishes is essential for clean shutdown.
What do you meen by "change asus osd", could you clarify?

brncmp wrote:

Is there a way to make the eee wake when the lid is opened instead of having to touch the power button. This is the first laptop I have seen like this.
I have also noticed that the batteries drain quickly (<10 hrs) when the eee is asleep (lid closed) and will eventually shut down. When this happens is it a clean shutdown? I assume, this is because power is needed to keep things in ram?

Having the eee wake up when the lid is opened isn't possible for now and might never be. It is so called hard coded feature and we can only hope that someone figures easy way to bypass it.
Second sad thing it as you have also noticed that the suspend to ram is not really useful feature at all. Luckily with correct configuration and toofishes kernel the Eee boots up fast so shutting it down when not needed is the most efficient option for now.

toofishes: Might it be possible to have vesa frame buffer support included in to your kernel? There's great demand for nice boot splash! We can't lose to Asus in this matter.
Also your hda-intel tweak works fine.

EDIT: How does this madwifi snapshot differ from the current one used with kernel eee ? http://snapshots.madwifi.org/special/ma … 007.tar.gz I came across it in here: http://justingill.com/blog/2008/03/16/t … buntu-804/

Last edited by ighea (2008-03-21 18:48:57)

faelar · 2008-03-21 19:58:40

Sorry if I wasn't clear enough. By "changing" I mean, to skin it, make a new theme, use other pictures, change their position on the screen etc...
I know where I can find the default png, but where are the other files ?

Second sad thing it as you have also noticed that the suspend to ram is not really useful feature at all. Luckily with correct configuration and toofishes kernel the Eee boots up fast so shutting it down when not needed is the most efficient option for now.

I agree with you. It's nice to see that eeepc boot as fast as the default xandros.
And thank you for your answer about alsa daemon.

Else it seems that shutdown fix works.

Another point, not sure it's eeepc related, but if I exit my openbox session (go back to the prompt), and press the power button, it display information about daemon etc...
But if I press the button before exitting X, it only prints the first lines (init, shutdown now) and nothing else. I'm just curious, anyway it shutdown correctly in both case so it's not a matter.

ighea · 2008-03-21 20:30:03

faelar wrote:

Sorry if I wasn't clear enough. By "changing" I mean, to skin it, make a new theme, use other pictures, change their position on the screen etc...
I know where I can find the default png, but where are the other files ?

With pacman -Ql acpi-eee command you should see all files included in the package. Asusosd is not too customizable or not at all. You can always replace the images in your system but changing the position on screen is hard coded in to the source. I'll see what I can do about that once I finish reading the latest Harry Potter!

faelar wrote:

Another point, not sure it's eeepc related, but if I exit my openbox session (go back to the prompt), and press the power button, it display information about daemon etc...
But if I press the button before exitting X, it only prints the first lines (init, shutdown now) and nothing else. I'm just curious, anyway it shutdown correctly in both case so it's not a matter.

This may have something to do with your syslogger. Are you using some modified syslogger config files or anything exceptional? It might just be that once you press power button while still in X most of the shutdown messages are printed to tty7 while you are whatching tty1 once the X is killed.
In the end the overall shutdown process should be cleanly/correctly finished.

jensp · 2008-03-21 21:13:32

ighea wrote:

toofishes: Might it be possible to have vesa frame buffer support included in to your kernel? There's great demand for nice boot splash! We can't lose to Asus in this matter.

I was just gonna ask about that, too
I'd also love to see Framebuffer Support for the eeepc (preferably with uvesafb).

Defre · 2008-03-21 23:12:41

Hi everybody, thanks for supporting arch on eee .
I've followed many tutorial and now i have an almost fully functional arch linux installation on eee, with the eee kernel and drivers from twofishes + acpi-eee-7.2.
However, i still have two problems:
- i can't enable vertical synchronisation while viewing videos with mplayer. vsync was working on xandros
- since last update (new madwifi and netcfg2), wireless (i'm using WPA) detection is unpredictable: i've to reload the profile up to five or six times before my AP to be detected, while this was instantly done with previous configuration.

Thx for your help,
Fred

faelar · 2008-03-22 11:02:42

With madwifi-ng-eee 3367-1, netcfg 2.0.6-1 no problem. At home I use WPA on a linksys wrt54gl. The only network issue I have is that /etc/resolv.conf is sometimes not updated. I have to launch :

#dhcpcd ath0

ighea · 2008-03-22 16:05:48

So I'm not the only one having problems with the wifi drivers/device. After you turn off your wifi are you able to get it always back up and running?
After turning the wifi off on the first try I usually, or more likely always, get HAL error and next try after that it detects the device and gets all drivers loaded but the wifi AP scanning is only feature functioning correctly. I am not able to assiciate with any wifi access points. Sadly that turning the wifi on and off worked well in Xandros so there must be something we can do. :<

loon · 2008-03-23 19:41:47

Hello,

Can you build a LiveCD with a kernel eeepc suited to integrating modules eeepc?

In reality it is for a friend, he discovered Linux (Xandros, eeeubuntu, eeexbuntu ....)
But it deals with problems modules unstable.
I showed him http://wiki.archlinux.org/index.php/Ins … sus_EEE_PC but find it too complicated ...

That is why I come here, you are asking to build a LiveCD eeepc easily installed as a LiveCD archlinux normal.

Thanks to advance to the realization of this LiveCD archlinux eeepc.
Google is my translator

Last edited by loon (2008-03-23 19:44:43)

slyson · 2008-03-23 20:14:36

Update: Upgrading pacman to the latest version allowed me to install the webcam drivers

Update2: Since I reinstalled I haven't noticed the keyboard locking up anymore. If it ever does, ctrl-alt-f2 to switch to the next console works as a temporary solution.

I'm moving to France for 7 months on Tuesday, and I'm taking my eee pc with me. Sadly, I will most likely have no internet the whole time because I'm staying in a rural area, so whatever I don't get setup about my newly bought eee pc now, I will have to live with. That said, I'd appreciate it very much if anybody could help.

I can't install the webcam drivers from toofishes.

error: cannot resolve dependencies for "linux-uvc-eee-svn" ("kernel-eee<2.6.24.4" is not in the package set)

I have toofishes repository in pacman.conf and the community repository is enabled. I've manged to install the kernel and the wifi driver from toofishes repository as per the instructions on the wiki.

uname -r 
2.6.24.3eee

Also, has anyone had the problem when working on a console that all of a sudden the keyboard stops working, including ctrl-alt-del? I have to hold down the off button for 5 seconds and then pray I haven't lost any files. The install is relatively clean, and I don't think the eeepc is totally locking up/overheating because if I'm running X it also happens, but luckily I can just launch another terminal with a right-click menu on the desktop and type in that. I did install acpi_eee alongside the toofishes drivers, so maybe that is conflicting?

Last edited by slyson (2008-03-23 22:47:43)

Arch Linux

#501 2008-03-12 22:25:44

Re: Arch on Eee PC

#502 2008-03-13 19:46:24

Re: Arch on Eee PC

#503 2008-03-13 20:03:15

Re: Arch on Eee PC

#504 2008-03-13 20:32:00

Re: Arch on Eee PC

#505 2008-03-13 22:06:00

Re: Arch on Eee PC

#506 2008-03-15 00:08:44

Re: Arch on Eee PC

#507 2008-03-16 14:43:06

Re: Arch on Eee PC

#508 2008-03-16 20:46:51

Re: Arch on Eee PC

#509 2008-03-17 15:06:44

Re: Arch on Eee PC

#510 2008-03-17 17:44:26

Re: Arch on Eee PC

#511 2008-03-18 20:30:46

Re: Arch on Eee PC

#512 2008-03-18 22:02:55

Re: Arch on Eee PC

#513 2008-03-19 07:51:07

Re: Arch on Eee PC

#514 2008-03-19 12:35:31

Re: Arch on Eee PC

#515 2008-03-19 17:16:57

Re: Arch on Eee PC

#516 2008-03-20 00:52:45

Re: Arch on Eee PC

#517 2008-03-21 18:39:23

Re: Arch on Eee PC

#518 2008-03-21 19:58:40

Re: Arch on Eee PC

#519 2008-03-21 20:30:03

Re: Arch on Eee PC

#520 2008-03-21 21:13:32

Re: Arch on Eee PC

#521 2008-03-21 23:12:41

Re: Arch on Eee PC

#522 2008-03-22 11:02:42

Re: Arch on Eee PC

#523 2008-03-22 16:05:48

Re: Arch on Eee PC

#524 2008-03-23 19:41:47

Re: Arch on Eee PC

#525 2008-03-23 20:14:36

Re: Arch on Eee PC

Board footer