With respect, it's easy for you or any other Arch old hand to say this, but a paragraph on AAO custom kernels doesn't seem much to ask on a wiki page detailing how to optimise Arch an AAO. You could take your argument a stage further and not even mention the custom kernels.

+

With respect, it's easy for you or any other Arch old hand to say this, but a paragraph on AAO custom kernels doesn't seem much to ask on a wiki page detailing how to optimise Arch on an AAO. You could take your argument a stage further and not even mention the custom kernels.

I agree that explaining "pacman -U" (or anything else with a man page) certainly shouldn't be necessary, but what I would find very useful is an explanation of the development and release cycle of these kernels. For example, do I download kernel26-one-dev-latest-i686.pkg.tar.gz or kernel26-one-dev-2.6.33stable-1-i686.pkg.tar.gz from dolly.rulex.net? Or should I download the kernel-one-dev maintained by Tera on AUR, where there currently doesn't even seem to be a valid link to a compiled kernel? I've asked for this clarification in the kernel-one-dev development thread but have yet had no reply.

I agree that explaining "pacman -U" (or anything else with a man page) certainly shouldn't be necessary, but what I would find very useful is an explanation of the development and release cycle of these kernels. For example, do I download kernel26-one-dev-latest-i686.pkg.tar.gz or kernel26-one-dev-2.6.33stable-1-i686.pkg.tar.gz from dolly.rulex.net? Or should I download the kernel-one-dev maintained by Tera on AUR, where there currently doesn't even seem to be a valid link to a compiled kernel? I've asked for this clarification in the kernel-one-dev development thread but have yet had no reply.

Complete re-write / split needed

I believe this article needs to be completely revised to account for the new 10.1" models, which don't seem to require half the adjustments or concerns included here. Perhaps we should split this into two articles--SSD and HDD versions, or AOA150s and AOD150s. I will work on my own notes as time permits and make the appropriate changes.

I alluded to this below, and in my _OPINION_, no, they don't. There is an AWFUL amount of FUD about how SSD devices wear out quickly if you write to them at all. Mind you, various vendors are shipping SSD for RAID devices now, in server systems; so there's at least one conflicting opinion to the common "ZOMG NO NEVER WRITE TO THE SSD DRIVE!"
However, it _is_ a valid choice, and I honestly think it would be best to put some sort of 'SSD' notes up on a separate page for general SSD use (as SSD will become more prevalent and less expensive in the coming decade.)

I haven't had time to do that yet.

I, myself, now have _both_ models, and the real difference is SPEED. The SSD is _slow_ compared to the HD. Really slow. So in THAT regard, the SSD model should have some notes about it, speeding up writes, etc.

Article formatting and contents

There are now more than 2 models of the Aspire One...

Thanks to whomever (I should check history but... things to do) edited the start of the article to reflect choice based on knowledge, not FUD about SSD, and to explain the various options concerning filesystems and how they can affect you as a user.

Deletion of section "How to install kernel26-one?"

This section is totally unneeded. First, everyone using Arch should be able to know about "pacman -U", can't be that difficult. There is also no initrd needed as was falsely suggested by the section. And more importantly we have a section about the custom kernel. Expand that if you feel you need so.

What I was thinking about maybe adding a sub section how to get kernel-one installed right away during initial installation process. Like with "pacman -U -r /tmp/install kernel26-one-2.6.27.8-1.pkg.tar.gz". Ideas about this? --Inkaine 22:40, 6 December 2008 (EST)

With respect, it's easy for you or any other Arch old hand to say this, but a paragraph on AAO custom kernels doesn't seem much to ask on a wiki page detailing how to optimise Arch on an AAO. You could take your argument a stage further and not even mention the custom kernels.

I agree that explaining "pacman -U" (or anything else with a man page) certainly shouldn't be necessary, but what I would find very useful is an explanation of the development and release cycle of these kernels. For example, do I download kernel26-one-dev-latest-i686.pkg.tar.gz or kernel26-one-dev-2.6.33stable-1-i686.pkg.tar.gz from dolly.rulex.net? Or should I download the kernel-one-dev maintained by Tera on AUR, where there currently doesn't even seem to be a valid link to a compiled kernel? I've asked for this clarification in the kernel-one-dev development thread but have yet had no reply.

Maybe I'm just unlucky in having the combination of coming brand new to Arch linux three days ago - with an AAO...
Bananabrain 15:57, 9 May 2010 (EDT)

Suspend with mounted SDHC

Is there a proper way for suspending while having an sdhc card mounted without configuring and compiling a kernel myself?
Doesn't work here, once it ruined my FS...
Lobotomisator 15:00 09.12.08

Using XFS for the filesystem solved the issue of corrupted SD-cards for me.
--Trontonic 18:10, 13 April 2009 (EDT)

More on SD Card Reader

As I was getting an error on boot when using the 'setpci -d 197b:2381 ...' command, I tried as root and lo and behold, you get a 'No Devices Selected' error - IF you don't have cards in the slots. The Debian wiki NOW states reasons why they don't reccomend this anymore. (Basically, the hardware doesn't show these devices AT ALL if there's nothing in them, no matter what you do outside of inserting a card into either slot.) They have some scripts, but I haven't tested them, and as half of the scripts are the pciehp bits that are already in the wiki - hotplug may be solved.

In addition, hotplug may not make any sense when using this wiki as is for setting up - as it suggests mounting /home on an SD card. Removing /home while it's mounted will confuse users who aren't used to Unix/Linux. (That doesn't mean we can't teach them, we can - by writing this in a way that makes sense.)

Which again I don't have time for right now ): (I am setting up the AO110 again, after attempting some tests.)

Eee 900HA

Regarding the proper frame buffer (1024x600 natively),
I can confirm that this works on a Eee 900HA if anyone would like to put that on this page. ( I don't want to as I just signed up for this and I don't want it to be marked as spam.)

Thanks

fdisk -l

The fdisk -l at the bottom has a swap partition, despite the advice towards the top of the page not to use one. Maybe there should be separate ones for the HDD and SSD models? Or perhaps the SSD advice should be split into a different article - not necessarily AAO specific, something like "Arch on SSD"

--

One needs a swap partition in either case if Hibernate is to work, as I understand it.

networking

webcam

I did not need to modprobe uvcvideo as the directions said I would. At least I don't recall doing so. Have others? Electron 23:23, 15 December 2009 (EST)

Removal of the userspace fan control solutions

As the userspace fan control solution (acer_ec.pl) has possible race-conditions, which can damage the hardware, the kernel module acerhdf should be used instead. Acerhdf uses atomic kernel functions to prevent those race-conditions. That's why I think only the kernel module solution should mentioned in the wiki. What do you think?
piie 19:22 14.02.09

I had no problems with the userspace fan control and weren't too worried about the race-conditions either, as my AAO isn't an important server to me.
However, if acerhdf works better, then that's great. I switched to acerhdf too, and it works fine here. So, in essense, we don't need the non-acerhdf method anymore.
Actually, I'll be so bold that I remove that outdated information right now. If I hurt anyone's feelings, just undelete the text please. :)