I haven't had that problem with my Acer Aspire One.

Running -current on my eeepc 900, very happy with it :)

What works out of the box:
Wireless
Wired Ethernet
Webcam
Graphics
Sound
Touchpad gestures (Two fingers to scroll down/up)

Things I haven't tried:
Card reader
Microphone

Thanks for posting this: sounds like a project for this evening. Ubuntu (don't ask!) is horrible on this light machine, and I though Slack would be perfect for it. Your positive experience makes me want to try :)

I've tried all those same things on my EEEPC 1000, and they all work including the card reader. I don't know for sure, but I've read that the microphone should work on a recent kernel... like slackware-current's. I think it's a pretty solid system.

I installed -current last night, and so far so good. As you said, the wireless, camera, graphics, sound, touchpad gestures and ethernet all work out of the box. Also, I used the USB installer provided to install Slackware using the SD Card slot on the EeePC, so can confirm that that definitely works with Slackware :) I've only got the microphone left to test.

I did have to leave out the whole of the K and KDEI series otherwise I was going to run out of space on the 4G SSD I installed it to. However, Xfce is very nippy in -current (I've got KDE4 on my main box), which is perfect for this machine.

Incidentally, I remember having to add certain mount options to fstab to reduce wear due to excessive writes - does anyone know if this is still the case with ext4?

Good to hear the card reader works :) I could use some extra storage in the form of an SD card(I'd rather my netbook not have wings(USB) :p)

I installed Slackware onto my 8GB SSD(The install took up about 5GB) which leaves me 4GB for /home.

Have you specified any particular mount options in /etc/fstab to prevent excessive writes to the SSDs?

I've had a quick look around, and people mention adding either noatime or relatime to decrease the number of writes to the disks when all you're doing is accessing a file, which seems straightforward enough. I'll give it a go and see what happens.

I've been aching to get rid of Ubuntu on this thing for as long as I can remember, so glad to have finally done it! :)

I honestly never thought of specifying mount options to prevent excessive writes, but after reading this article I decided to add 'noatime' to both / and /home. I'm curious tho, don't a lot of applications rely on knowing when files were accessed?

I think only a few apps do (mutt does, I think). I don't think anything important breaks without the access times being updated.

I think I'll try the relatime option since it still does the atime updates, but it does so a bit more intelligently.

Slackware 13.1 Wifi on Acer Aspire One
 

I've had some problems using my wifi with my AAO, then I found the following somewhat helpful. Not sure if folks would want to use it when needed or just put it somewhere to run at bootup so it's always there. The code is as follows, and it MUST be run as root:

modprobe ath5k
sleep 3
/sbin/iwconfig wlan0 mode managed rate 54M key off essid "wifi network name"
dhcpcd wlan0


This is somewhat unweildy, but it does work. A better solution (I'm lazy) is to get wifi running at bootup, which I haven't done yet. If someone knows specifically how that's done, please post it.

dont buy anything with the gma500 chipset........im dying to install in my eeepc1201ha a fresh slack13.1, but i cant......slack doesnt have a a nice support for that chipset. At the moment

I'm running Slackware 13.1 on my EeePC 1201T.

• Wireless: Running (But you have to download rtl8192se → http://www.realtek.com.tw/downloads/...Downloads=true
  lspci outputs somehow the wrong name. Probably a bug of the chip itself.
• Sound: Running
• Graphics: Running (ATI Radeon HD ... dunno)
• Ethernet: Working
• Touchpad: Working
• Cardreader: Working

For more information Archlinux Wiki

I recently installed -current on 2 AAOs, and I don't recall having any wireless issues - I install and use wicd from extra; I'm pretty sure it ran right out of the box....

DISCLAIMER: I am a child of the 60's, and my memory isn't foolproof....

cheers,

I've got 13.1 stable going on my eeePC 1000ha. Everything with the exception of some of the function keys works out of the box.

Unr3a164 wrote, in relevant part:
"My only question is how do I setup the slackware dvd iso on a flash drive as bootable?"

My reply:
The SSD cards can, indeed be used much like any hard drive on your netbook. I have an Asus 701SD in which I installed the following:
Lucid Puppy Linux 5.0.1 on /dev/sda1, ext2
Ubuntu Lucid Lynx on /dev/sda2, ext3
Slackware 13.1 on /dev/sda3, ext3

I wiped WinXP and booted into Puppy, which I used to re-partition the SSD with G-Parted into three separate partitions as shown above. I then installed Puppy and its GRUB, followed by Ubuntu, and then Slackware. Once these three were installed, I re-booted into Puppy LIVE, not from the SSD, and re-installed GRUB. While still running from the live CD I opened /dev/sda1, which is where I'd installed GRUB, and edited the entries appropriately. Remember: when installing GRUB from Puppy, it gives youmany options as to what type of device you're installing to. DON'T install it as though it was a USB stick. Use the "Internal" drive option. Read the list to be certain. I'm using my SSD as though it was an internal hard disk and it works fine. I replaced the stock 8gb SSD with a 32gb unit, but Slackware will work in an 8gb drive alongside something else, as I originally tried that, too, using a smaller Puppy partition. Did I mention I'm not using a swap partition? You can, though, as I've done that also on 8gb with Puppy and Slackware.

I should also mention that I did, in fact, install Puppy 5.0.1 and Slackware 13.1 on my other netbook, an Acer Aspire One alongside WinXP, which it came with. I did this, of course, by shrinking the XP partition and adding others after it. I left the "Recovery" partition alone, and added it to my menu.lst file in GRUB. That's another story.

I can't stress the importance of one fact: I used Lucid Puppy 5.0.1 in LIVE mode from the CD to install GRUB and edit the menu.lst file in /boot/grub, as installing the other distros with GRUB overwrites you MBR. Don't be fooled by the way GRUB does this. It will ask you where you dwant to install it, and you should choose the MBR. It will also ask you where to install the "grub files", which is menu.lst, among other things. This second later choice is where your GRUB directory will go, with its menu.lst file, and this is your choice, although I used /dev/sda1, which may be known as /dev/hda1 to your distro, unless Windoze is on the first partition, in which case you must decide for yourself. I always choose my first Linux partition.

I hope this makes it easier for the absolute newbies, which are really the only ones I can show something to. I'm no guru at this, although I've been installing linux & unix since the mid-90's. I neither qualify for, nor aspire to, any elite status, but I don't mind sharing for others, who can proceed from there at their own risk as I did. There are plenty of folks that install only one distro on their machines. I'd have about five linux and two unix distros if I didn't have a 4-partition limit....

Mike