You can compare the kernel build configurations and that could help you to find out why it is not working with your custom kernel build. When building the custom kernel, you can "oldmenuconfig" to start with the base stock Slackware kernel.

Ran Slackware 13 on 900A Worst Buy model. Required a bit of experimentation at first, but eventually everything ran silky smooth. A few of the Fn keys never did work (wireless card, for instance, was always on unless disabled in BIOS at boot). Decided recently to give FSF's distro a whirl just to try something different but will be, in all likelihood, switching back in the future.

Firefox seemed to take to my EEEPC better than my desktop and became my browser of choice. Familiarity carried a lot of weight in that decision.

Did not attempt much heavy lifting with the system (and never found the time to dedicate to really getting the most out of it).

I found XFCE to be a good fit and was pretty responsive.

Although my install method was a bit... clunky (I've only recently discovered the joys of Slackpkg), it was fairly painless.

While not suitable for a primary workstation (for me), I've found the portability makes up for the slightly cramped keyboard in that it may be easily taken basically anywhere.

I'm using FF3.5 and it's plenty fast for me on my 1000H. I use it for google docs, mail etc all the time and often have 5-10 tabs open at once.

Thanks, I was having this problem with my Dell Mini 10v but didn't think much about it until reading your post. Hope I didn't do too much damage to my hard drive in the month that I've been using it without this.

My HD has a total load cycle of >230,000 now - it's in old age in that respect, but performs absolutely fine. The worry is it may fail any day now, but my attitude to backup is that any HD could fail any day anyway, so this does not worry me unduly.

Firefox 3.6 works great on my 900A; I found Chrome to be Not Ready for Prime Time. And for Mr. Hales benefit, here's a link to how to get wireless toggle hotkey to work on the 900A (works for me):
http://wooush.com/node/3#38

1 members found this post helpful.

Well my new config was already based on the old one. I tried other variations, too. It's the driver that has changed -- even the controls that appear in alsamixer are different. For example, with 2.6.31 and before, there is a switch to select capture source between front mic and internal mic. With 2.6.32 it's gone. Skype works, but I couldn't make Ekiga record the sound. There was one kernel in which I managed to get both of them to work, but I don't remember which one.

Another difference from <=2.6.31 to .32 seems to be the Fn keys. With 2.6.32 the volume keys and the key that turns off LCD the screen stopped working. The boot option acpi_osi=Linux brought the volume keys back but the other one is still dead.

(Reminder: This is an EeePC 1005HA system).

Did you use the Alien Bob scrips in the EeePC 1005 HA?

I just tried (thanks for pointing out, btw), but unfortunately there was no change in functionality. In fact, I had to remove the package as using the brightness keys causes an info window to flash in the middle of the screen indefinitely.

I am buying a 1500 HA soon. What problems do you have on yours with Slackware? It is functional on Slackware 13? What features do you have in windows that you would like to have in Slackware?

I don't consider the situation "problematic" in any way. I can do without the "turn off the LCD" key (or just use 2.6.31). I don't use windows on this machine (although I kept the installation on disk, just in case) so I can't make a detailed comparison, but here is a list:

- I wish I could get Ekiga to capture sound. Skype does, so the problem could be with Ekiga rather than the sound support.

- In windows you can disable Bluetooth, the camera and ethernet to save power on battery (there's a system tray utility for doing that). I don't know if it's the same thing but I'm using the USB autosuspend feature in Linux.

- The Fn key that turns off the wireless doesn't work, but I don't care as I usually use the net (somewhere I read people having success with it, but apparently the eeepc-laptop module is still in development -- it's marked "experimental" anyway). Currently the Fn keys that I couldn't get to work are F2 (wireless), F3 (disable mouse), F4 (don't know what it is -- looks like zooming), F7 (only on 2.6.32 - turn off LCD). F8 is untested (external video device) and I don't know what F9 is for.

But I don't consider any of these a hiccup, let alone being essential. I'm very happy for choosing 1005HA, it performs way better than I expected and has good battery time.

By the way: With the 13.0 stock kernel the wireless etc. should all work out of the box, but if you use wicd, I recommend that you upgrade to the 1.6.2.2 version.

I'm on 1005 HA and I choose Xfce for my X. KDE was too heavy for it. And I couldn't still put the webcam working. I will report the performance of my machine in the future.

Is KDE uselessly slow? Shouldn't be. I don't use it regularly but I have it open right now on another screen (besides XFCE) and it's doing fine. But if you expect super-smooth effects, then maybe anything is slow for KDE 4. Or maybe, for 4.2.4 at least. There were quite a few people reporting better luck with 4.3.1 (the latest version for which 13.0-compatible packages were released, afaik) so you may want to give it a try.

As far as I can remember the camera was working with the default kernel. It uses the uvcvideo driver which was included in kernel 2.6.29, I believe. If not, you can download it separately or you can upgrade your kernel. I submit below my kernel config for 2.6.32.5, in case if it's of use to anyone (it has some crypto-stuff compiled in which you don't need if you're not using LUKS). Good luck,

Attached Files

config_325.txt (61.7 KB, 16 views)

I'm with difficulty to configure webcam in amsn. Anyone can give me a hand?

EDIT: It was easy. I just needed add my user to group video.

Ah, good. When I saw your post I rebooted into the stock kernel only to see that everything works.

If you use the "adduser" command to create your user account, you can try the up arrow in the "additional groups" stage to get the list of default additional groups. In Slack they are

.

You may want to add yout user to the other ones as well, for better functionality.