[SOLVED] Slack ARM on Seagate FreeAgent GoFlex Net
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: slackware 13.37 x86_64 desktop, Slackware-current on laptop
I have successfully installed armedslack 13.37 on a sheevaplug. I had to upgrade uboot, no experience with a go flex but I am sure there is documentation if you use your google-fu about the differences, also if you ftp transfer the armedslack tree make sure that you transfer in binary and not ascii as it will mangle your kernel and you will be stuck with a bad crc data error and unable to boot for the installer. Otherwise it was quite easy after getting those things out of the way for me. Hope this helps.
Thanks for the links. I had already installed Jeff's latest uboot, but prior to that had connected to Pogoplug and couldn't stop it downloading an update. Which meant that I faced some issues having installed Jeff's uboot and can now no longer get into the Pogoplug OS.
However, I have successfully installed Slackware onto a USB hard drive and booted into it
After installing the kernel, I will remove the external hard drive from its enclosure, place it into the SATA port, set the correct arcnumber + IDE boot parameters in uboot console.. and see what happens...
I do not think I will need to make/install a new initrd, but can someone just confirm that the Marvell SATA driver is built-in in the default config?
And once the kernel is 'made', is it simply a case of copying across to /boot?
SATA functionality tested and working from within Slackware I'm still trying to troubleshoot booting from it, though.
A couple of notes:
U-Boot detects the SATA ports 'backwards', ie. sda as port 1 and sdb as port 0 [EDIT: THIS IS NOT TRUE ANY MORE]
Linux allocates device nodes to SATA before USB... so with 1 SATA drive installed, any USB storage will be sdb(+). With 2 installed, USB drives will be sdc(+). The latter is an assumption and I am yet to test it.
I've also managed to boot into the Slackware install environment (over tftp) using my custom kernel, meaning one can install straight onto a SATA drive.
One thing I don't quite understand, is that I can see terminal output while booting the install environment from RAM (as in the armedslack install instructions), but not when booting from USB or (attempting to) from SATA - is this fixable? It would make things a lot easier right now. I have 'bootargs console=ttyS0,115200' set in both cases.
Wuala seems to be working perfectly, though bear in mind I'm only using it for trading. The 100GB trading limit is a little low for my liking, but does mean I can at least make use of my 160GB root drive, and dedicate the 1TB drive to solely NAS duties
I set up a user called 'wuala' with no extra privileges, logged-in to wuala manually from that user, and set the trade size to 100GB. Then edit the init script (renamed to rc.wuala), chmod +x it and reference it from rc.local. Reboot, and Bob's yer uncle!