Difference between revisions of "Talk:Acer Aspire One"

From ArchWiki
Jump to: navigation, search
(Xorg 1.5 + hotplugging + gnome)
(remove closed sections)
 
(37 intermediate revisions by 16 users not shown)
Line 1: Line 1:
There are 2 models of the Aspire One, this is mentioned at top.
+
== 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.
  
The article then goes on to write as if they both use faulty media that will die if you write to it.  This is a CONCERN, yes, but recent discussions surrounding the media used for the non-hd model indicate that this may in fact be more FUD than truth.
+
[[User:Thayer|Thayer]] 13:49, Mar 15, 2009
  
The article should give the person installing on an Aspire One _understanding_ of their media, and allow them to make choices; not _assume_ the person wants to set up an exact duplicate of an Ubuntu system.
+
:Does the AAO110 really need that extra attention? Do SSDs really get worn quicker than HDDs? Any sources on this?
 +
:-- [[User:Trontonic|Trontonic]] 19:35, 24 March 2009 (EDT)
  
I may rewrite sections of this later, right now, I am thinking perhaps I'm overreacting. I'll come back to this later and review.
+
::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.
 +
::
 +
::-- [[User:Lastebil|Lastebil]] 15:08, 28 March 2009 (EDT)
  
(Also, the 'xorg.conf' posted as the original does NOT match my copy. Some keyboard tweaks based on the fact that I'm in Finland. (Which, surprizingly enough, the initial install had in the xorg.conf but NOT in the loaded software - no .fi locales at all beyond that (: ) [[User:Lastebil|Lastebil]] 16:03, 20 August 2008 (EDT)
+
:::There are a few more models of Aspire Ones, this may need to be revisited. I have a D255e, with a different wireless/wired network configuration. The standard ISO image does not work. I would be willing to work on a rewrite for the D255 if it warrants its own page. Right now, bits and pieces are placed within this Wiki and many parts are not applicable at all.
 +
:::-- [[User:Multiphrenic|Multiphrenic]] 10:51, 26 April 2011 (EDT)
  
== Xorg 1.5 + hotplugging + gnome ==
+
== 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...
 +
[[User:Lobotomisator|Lobotomisator]] 15:00 09.12.08
  
Hi,
+
Using XFS for the filesystem solved the issue of corrupted SD-cards for me.
before answering to read Wiki and Forum please read on :)
+
--[[User:Trontonic|Trontonic]] 18:10, 13 April 2009 (EDT)
  
Well, I've followed any possible post or wiki entry, but still have got some problem:
+
== 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.
  
I'm Italian, so my keyboard.
+
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.)
The xorg.conf for 1.5 posted 2 days ago is wonderful and works like a charm, but still it doesn't solve the real problem which is letting Xorg manage the input devices with evdev, without disabling the new hotplugging features, or forcing to use the x11 xkb module for keyboards.
+
  
If I enable the option "AutoAddDevices", letting hal policy to set "evdev" as driver, then setting via hal the properties {input.xkb.model=evdev, input.xkb.layout=it, input.xkb.variant=nodeadkeys}, then setting Gnome Keyboard disposition as "Italian no dead keys" "Managed by Evdev", all my keyboard keys get working correctly....but the "Up arrow" key and the "Print screen" key.
+
Which again I don't have time for right now ):  (I am setting up the AO110 again, after attempting some tests.)
  
In fact when I press "Print screen" nothing happens, when I press "Up", quite randomly Gnome receive only "Up", only "Print Screen" or both.
+
[[User:Lastebil|Lastebil]] 15:15, 28 March 2009 (EDT)
The strange thing is that in some circumstances, as when "browsing" trough the Gnome Menu (the one with the foot icon), the "Up" key works as the "Up" key, without asking for a Screenshot. So I tried disabling the "Allow windows to manage keyboard disposition indipendently" (I'm translating from italian) check, and to restart the whole X server. But still I experience this problem.
+
  
Is anyone succesfully trying to use the new hotplugging feature with keymap different from "us"?
+
== Eee 900HA ==
  
[[User:Romen|Romen]] 08:02, 4 December 2008 (EST)
+
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.)
  
This does not belong to the wiki talk section. Here is for discussions about the actual content of the wiki. But to answer your question, I'm successfully using Gnome with evdev and German keyboard layout. And AFAIK so does gothicknight (the creator of the kernel-one package) with a Portuguese one.
+
Thanks
  
Please for further discussion on that use the forum. So after reading my comment here, please delete it altogether with your long question. Maybe read on the forums first, because there have been plenty of all kind of threads on this topic already. Then you can still post it there...--[[User:Inkaine|Inkaine]] 21:51, 6 December 2008 (EST)
+
== fdisk -l ==
  
--[[User:Inkaine|Inkaine]] 21:51, 6 December 2008 (EST)
+
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.
 +
 
 +
--[[User:Trontonic|Trontonic]] 19:37, 24 March 2009 (EDT)
 +
 
 +
== networking ==
 +
Is this line needed or just overcautious? If you have problems with r8169, try r8101.
 +
 
 +
:I don't think it's needed.
 +
:-- [[User:Trontonic|Trontonic]] 10:01, 15 March 2012 (EDT)
 +
 
 +
== 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?
 +
<br>-- [[User:piie|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. :)
 +
:
 +
:-- [[User:Trontonic|Trontonic]] 19:46, 24 March 2009 (EDT)
 +
 
 +
==Framebuffer==
 +
Added stuff about using grub2-915resolution and intelfb for the framebuffer... hope this is alright :s (i'm more than happy if anyone changes/fixes/...s it :p )
 +
 
 +
== Initscripts are no longer supported ==
 +
 
 +
This article needs to be written for configurations that do not use initscripts which includes additions to rc.local if possible,<br>
 +
-- [[User:Dewdrop|Dewdrop]] ([[User talk:Dewdrop|talk]]) 20:26, 2 March 2013 (UTC)

Latest revision as of 09:22, 10 March 2013

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.

Thayer 13:49, Mar 15, 2009

Does the AAO110 really need that extra attention? Do SSDs really get worn quicker than HDDs? Any sources on this?
-- Trontonic 19:35, 24 March 2009 (EDT)
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.
-- Lastebil 15:08, 28 March 2009 (EDT)
There are a few more models of Aspire Ones, this may need to be revisited. I have a D255e, with a different wireless/wired network configuration. The standard ISO image does not work. I would be willing to work on a rewrite for the D255 if it warrants its own page. Right now, bits and pieces are placed within this Wiki and many parts are not applicable at all.
-- Multiphrenic 10:51, 26 April 2011 (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.)

Lastebil 15:15, 28 March 2009 (EDT)

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.

--Trontonic 19:37, 24 March 2009 (EDT)

networking

Is this line needed or just overcautious? If you have problems with r8169, try r8101.

I don't think it's needed.
-- Trontonic 10:01, 15 March 2012 (EDT)

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. :)
-- Trontonic 19:46, 24 March 2009 (EDT)

Framebuffer

Added stuff about using grub2-915resolution and intelfb for the framebuffer... hope this is alright :s (i'm more than happy if anyone changes/fixes/...s it :p )

Initscripts are no longer supported

This article needs to be written for configurations that do not use initscripts which includes additions to rc.local if possible,
-- Dewdrop (talk) 20:26, 2 March 2013 (UTC)