I've been using a stock kernel. In fact, I think (despite advice to the contrary) I'm using hugesmp. The only tweak I've had to do is compile and install Broadcom's wireless driver to support the wireless card. That was easy and works great with wicd. All the other hardware has worked from the get-go. For what it is worth, when I got the Mini, 12.2 hadn't been released, so I tried installing 12.1, and that wouldn't install no matter what I did. However, 12.2 installed smoothly.

Thanks for the info...now I must find some time. The inclusion of the drivers for the Atheros wireless chip in the 2.6.29 kernel certainly make life easier. A working webcam would be nice, but I have other machines with working cams so whatever...

Btw, I'm assuming you went with no swap partition and the 'noatime' setting to minimize writes to the SSD. Oh, and would you be willing to share your kernel .config file. I feel like such a newb for asking, but free time is way limited right now.

That's correct. I nuked the original partitions and created a single partition. I have never attempted to get suspend-to-disk working. Suspend-to-ram works fine and it doesn't take long to boot or shutdown.

See attached. No guarantees that it is perfect but it works for me and should get you started. It is just the original Asus .config that I keep running through "make oldconfig". I build the kernel on my desktop PC, make a Slackware package out of it (kernel and modules in one) and install using installpkg/upgradepkg.

Geoff.

Attached Files

config-2.6.29.3-gsl-eeepc701.txt (52.1 KB, 34 views)

What I would ultimately like to do is do what I did with my old Gateway computer, which is triple boot my computer between windows, slackware, and ubuntu. My only question is how do I setup the slackware dvd iso on a flash drive as bootable?

I really appreciate it. A kernel stripped down to match the hardware is always the best option, IMHO, and it's how I roll on all my other machines. Your config file will give me a nice working kernel that I can tweak later if I have the time and/or need.

I don't know if that's possible. My standard way to install from a flash drive is make a bootable flash drive using usbboot.img (in usb-and-pxe-installers/ on the DVD, check out README_USB.TXT in the same dir) and have some or all of the slackware/ disk sets on another flash drive which you have plugged in at bootup. Then choose "Hard drive partition" for your source media and follow the instructions.

Geoff.

Might I suggest UNetbootin

Hi Unr3a164,

is the internal microphone works on your s10 with slackware?, since it's the only problem i have under ubuntu

You may certainly suggest it, but I can't see any reason why you should.
The home page of unetbootin does NOT claim to be able to install Slackware. Further reading of other pages on the site also make no such claims. If you managed to get it working, could you expand your suggestion into a How-To please.

Please note that in the very first paragraph on the main UNetbootin page, under "Introduction", it states the following:

"or supply your own Linux .iso file if you've already downloaded one or your preferred distribution isn't on the list."

Additionally, under the section titled 'Installing Other Distributions Using UNetbootin' on the main page you'll see a nice screen shot illustrating how to use an ISO file you've already downloaded.

In fact, I see nothing on the entire UNetbootin page that suggests it can't handle a Slackware iso file.

To answer your question, no I haven't used UNetbootin with a Slackware iso yet. Haven't needed to...but that may change soon. If I do, I'll be sure to come back and let everyone know how it went.

My question to you is: have you tried Unetbootin with Slackware and had it fail? Perhaps a recounting of your experience (if you've had one) would be more beneficial to the community. If you have nothing else to offer, please take your negativity elsewhere.

@Crashbox

Yes - I tried Unetbootin about a year ago. It failed. I can't remember the details. I was disappointed because it seems to work for Slax, Vector and Zenwalk - all Slack derivatives. So I was quite surprised that it didn't work - but then if it did, it would surely claim that ?

As far as negativity - giving advice that you have not personally tested and proved to work is rather low. This entire website is based on the giving of useful advice. If you didn't know something for certain (and you just claimed that), then at least qualify the suggestion with a "I haven't tried this but ...."

I have some issues with the SSD on current, It seems to deny access when some process is using it (for example i cannot write something to the disk while copying a file). I'm still to find a solution...

Thank you for making my point. Instead of responding in a way that made it sound like Slackware expressly did not work with UNetbootin, you could have said: "hey, I tried it a year ago and it didn't work. maybe it's worth another look."

UNetbootin may very well work with Slack now and it may very well be the solution to the guy's problem. Your previous response though, would have turned him off of it completely. I gave him a suggestion of where to start.

And for the record, I've used UNetbootin with iso files from several distros 'not included' and have had no trouble, nor have I found anything which would lead me to believe Slack won't work now. But you're right, I haven't done it. Maybe someone who has could enlighten both of us.


Unless I'm able to provide additional assistance to someone who needs it, I won't be posting anymore in this thread. I've been hanging around here for some time now and I think I'm pretty familiar with LQ and it's goals. I'm not terribly interested in etiquette advice from a guy whose only been here a few months.

I, too, have tried unetbootin on a number of distros, including Slackware. As Crashbox states, the installation can be any iso. I have only had two distros fail to boot, and, unfortuantely one of them was Slackware 12.2. I got a module error that initial needed modules couldn't be loaded. I do intend to try it again this week. All I want to do is get enough installed to get a network install started. I do believe it will work, but I cannot confirm that because my only attempt failed.

Bob

I'd heard that there were problems like this with the SSD devices. For this reason (and that of capacity), I opted for a regular hard drive. Unfortunately, I can't be any help, I'm afraid.