From: Tinfoil Hat on
Danno, on 02/27/2010 06:14 PM, wrote:

> Just want to be clear. You PXE-booted the Microclient, then
> installed Slack13.0 over a network connection onto to a USB key
> plugged into the Microclient?

Exactly

> I wonder about that as well, booting a USB stick should have been
> trivial. Are you able to test-boot the USB key in another
> computer? Did you maintain all the USB connections exactly as
> they were when you installed (eg : you didn't change the drive
> from /dev/sdb to /dev/sdc)? That is, you didn't add/remove a USB
> mouse, swap the USB stick into a different port, etc.

Nope, nothing at all, just rebooted the microclient at the end of
Slack setup, leaving the USB in place.

Going back to your suggestion

> Navigate the kernel config into
> -> Device Drivers
> -> Serial ATA (prod) and Parallel ATA (experimental) drivers
> -> RDC PATA support

I don't even have "RDC PATA support" or pata_RDC in that menu on my
big pc, Slackware 13, so I guess I won't see in the CF installation
either. I've tried with the search function too.

In the meantime, I've tried Slax. It boots from a vfat USB, hangs
from an ext4 USB.

Now I'm working with Slax, and I think I'll stick with it. I don't
want to deal with a kernel tampered by somebody like me!

New problem: No trace of eth0 with Slax, so now I'm investigating
this new pain in the neck.

Thanks for your help so far.

From: Tinfoil Hat on
Tinfoil Hat, on 02/28/2010 08:00 PM, wrote:

> New problem: No trace of eth0 with Slax, so now I'm investigating
> this new pain in the neck.

By the way, I know that eth0 works, because I was able to PXE-boot
and network-install Slackware without a fuss earlier on, so it must
be some glitch with Slax.