[ARMedslack] ARMedSlack on Seagate Dockstar

Rich richard.lapointe at gmail.com
Tue Dec 21 02:37:12 UTC 2010

My testing indicates that it not getting an ip assign during 
initialization because the rc.inet1.conf file isn't configured   I'm a 
wimp, so I've been using serial cable to observe what is happening.  
Using a desktop with Linux (Salix OS) I partitioned a Memorex 2G USB 
Stick into two partitions, one (sda1) for the root file system and a 
second for a swap partitions. I untar'ed the mini file system on to 
sda1, edited fstab to have sda1 mounted / and sda2 as swap. I then added 
sym links for the kernel and initrd

     ln -s uImage-kirkwood- uImage
     ln -s unitrd-kirkwood02.6.33.5 uInitrd

Then I plug the stick into my dockstar (using doozan uboot along with 
his rescue system) and booted it.  I monitored the boot up process with 
a netconsole terminal and a serial terminal connection to the 
dockstar.   The two file attached are the output of each of these 
terminals during the boot process.   On the initial boot, it did boot 
the kernel and started the system initialization scripts but then fdisk 
the sda1 and rebooted.  The second boot did complete and I got a login 
prompt on the serial terminal.  The netconole terminal stop at Starting 
kernel...... , but did show the reboot into the second boot up and then 
again stop at starting kernel.   Although it did boot to the login 
prompt, my router did not indicate that the dockstar was connected.  
Using the serial console, i looked in and checked ifconfig and fond that 
there was no ip

Last login: Thu Jan  1 01:00:52 +0100 1970 on /dev/ttyS0.
You have mail.
root at slackware:~# ifconfig
lo        Link encap:Local Loopback
           inet addr:  Mask:
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:8 errors:0 dropped:0 overruns:0 frame:0
           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

I then checked /etc/rc.d/rc.inet1.conf file and noticed that it wasn't 
configured. I edited to use dhcp
rebooted and was able to ssh into the dockstar

Rich Lapointe

On 12/10/2010 10:58 AM, Stuart Winter wrote:
>> Does anyone know if the pre-compiled ARMedslackware kernel support
>> netconsole? (If so, then it looks like the kernel boot crashes before
>> netconsole is operational).
> It's compiled as a module, so you'd have to include it in the initrd.
> I've taken the latest code from kernel.SlackBuild (where the initrd's are
> made) and made this script:
>     http://stash.armedslack.org/scripts/make-new-initrd.sh
> (This is useful for people in general, btw).
> This will make a new initrd for the *Operating system*, however, not the
> installer.
> There's no point in adding netconsole to the installer initrd because the
> installer's initrd is quite a different beast and if it's not making it as
> far as running the /etc/rc.d/rc.modules-arm script, then you're buggered.
> Actually - what driver does the dockstar use for its ethernet?
> I assume it's mv643xx_eth -- if not, then that's your problem ;-)
> I can't imagine it'd be anything other than that though.
> In order to use netconsole with the installer you'd have to recompile the
> kernel to include netconsole and the ethernet driver into the kernel
> itself.
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: test-1_serial.txt
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20101220/042cd1da/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: test-1_netconsole.txt
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20101220/042cd1da/attachment-0003.txt>

More information about the ARMedslack mailing list