Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2011-01-27 Thread Christophe Lyon
On Thu, Jan 27, 2011 at 7:35 AM, John O'Donnell unixjohn1...@gmail.com wrote:
 On 01/26/2011 08:25 PM, Rich wrote:

 The dockstar led is controlled by uboot and armedSlack's kernel doesn't
 know how
 to control it.

 I'd be willing to bet it is controlled by  standard kernel settings.  I
 control my guruplug's LEDs in /sys/class/leds

 Take a peek

In /sys/class/leds, I can only see:
plug:green:health

If I try:
echo heartbeat  /sys/class/leds/plug\:green\:health/trigger
-bash: echo: write error: Invalid argument
# uname -a
Linux dockstar 2.6.33.5-kirkwood #2 PREEMPT Thu May 27 14:47:11 BST
2010 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug
Reference Board GNU/Linux

Christophe
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] mfloat-abi

2011-01-27 Thread Christophe Lyon
2011/1/27 Thorsten Mühlfelder thenk...@gmx.de:
 Hi,

 I did not really understand what's the difference between -mfloat-abi=soft
 and -mfloat-abi=softfp? Does soft always use software floating point
 and softfp could use hardware floating point if a correct -mfpu is given?

Exactly.
- soft: only software emulation
- softfp + mfpu=xxx: enables the compiler to use FP
instructions/registers inside functions, but not as function
parameters. This way, code remains compatible with 'soft' libraries
- hard: it's a different ABI, where parameters can be passed in FP
registers, avoiding expensive moves between core and FP registers. But
such code is not compatible with 'soft' libraries.

Christophe
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2011-01-26 Thread Christophe Lyon
On Wed, Jan 26, 2011 at 2:11 AM, Rich richard.lapoi...@gmail.com wrote:
 Well, i think its good news because you confirmed that the installer can be
 started and  you seem to have gone through a complete installation.  Now  I
 think you hit the next problem. The installed system doesn't boot because
 there is no real time clock in the dockstar and hence all the files have
 dates of 1969.  What's happen is when the system is booting it tries to
 check the root file system and gets an unexpected inconsistency and
 requires users input to do a manual fsck on the file system.  If you had a
 serial line you would be able to type in the root password and then continue
 doing a fsck.  Once completed, it would reboot into the system.  The way
 around this is to a add this file to the /etc directory.
     ftp://laprjns.com/in/e2fsck.conf

OK, I have added this file. Belongs to root, permissions 644.

 Apparently this configuration file tells fsck to ignore bad file dates.  You
 should add this at the end of the install before rebooting.  I would also
 suggest at this time you make the necessary changes to start the ntp daemon
 on boot up.  Just do a chmod +x /etc/rc.d/rc.ntpd along with making the
 necessary change to /etc/ntp.conf.   It should boot after this.

What are exactly the necessary changes? I have only uncommented the line
server pool.ntp.org

When I reboot, nothing has changed :-( uboot says 'starting kernel'
and then nothing more. At the same time, the dockstar  usb key stop
blinking.


However I have noticed that e2fsck finds tons of errors like
Inode 81277 was part of the orphaned inode list.  IGNORED.

I have repeated the whole install process (+mke2fs before) several
times, and I always get this kind of errors.
They are reported by both arm native e2fsck on the dockstar when my
usb key is attached to it, and by my x86 desktop PC.
It seems very strange to me.

I can't reformat it during the install process, otherwise it will the
installer given that it contains /boot, right?


 How long did it take for you installation?  I been using an Adata 4G usb
 stick and it took hours to install the packages.  Base on that I really not
 sure that this is a viable way to install armedSlack on the dockstar.
I am using a noname 4GB usb key, formatted as 3.5GB ext3, 500MB swap.

I did not install Qt/KDE, nor X/XAP, nor games, nor TeX. It takes about 2h.
The step 'processing 1002 packages' takes about 5 minutes.

 As for the serial cable, here's where I got mine.

  http://cgi.ebay.com/NEW-Data-Cable-Nokia-6101-6102-6102i-6103-CA-42-/200353624748?pt=PDA_Accessorieshash=item2ea601b2ac

 It  literally came on a slow boat from China :)
:-) Thanks for the reference.
And then, I have to do something like that, right?
http://www.yourwarrantyisvoid.com/2010/07/21/seagate-dockstar-add-an-accessible-serial-port/
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2011-01-08 Thread Christophe Lyon
On Tue, Dec 21, 2010 at 3:37 AM, Rich richard.lapoi...@gmail.com wrote:
 I then checked /etc/rc.d/rc.inet1.conf file and noticed that it wasn't
 configured. I edited to use dhcp
 USE_DHCP[0]=yes
 rebooted and was able to ssh into the dockstar

 Rich Lapointe


Thanks! I confirm it also works for me.

Christophe.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2010-12-15 Thread Christophe Lyon
On Fri, Dec 10, 2010 at 5:06 PM, Claudio Cavalera
claudio.caval...@gmail.com wrote:
 I have it when I run lsmod in the debian
 mv643xx_eth


For the record, I have also noticed that under Debian the kernel
version is a bit older:
r...@debian:~# uname -a
Linux debian 2.6.32-5-kirkwood #1 Fri Nov 26 07:01:06 UTC 2010
armv5tel GNU/Linux

The modules loaded are:
r...@debian:~# lsmod
Module  Size  Used by
ipv6  253826  10
hmac2475  0
sha1_generic1717  0
mv_cesa 9262  0
aes_generic32820  1 mv_cesa
ext2   55411  1
mbcache 4860  1 ext2
sd_mod 31312  3
crc_t10dif  1106  1 sd_mod
usb_storage34879  2
scsi_mod  119252  2 sd_mod,usb_storage
ehci_hcd   35579  0
usbcore   122203  3 usb_storage,ehci_hcd
mvsdio  5318  0
nls_base5367  1 usbcore
mv643xx_eth22562  0
mmc_core   50206  1 mvsdio
libphy 14836  1 mv643xx_eth
inet_lro5060  1 mv643xx_eth
configfs   20841  0

 # cat /proc/cpuinfo
Processor   : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS: 1192.75
Features: swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part: 0x131
CPU revision: 1
Hardware: Marvell SheevaPlug Reference Board
Revision: 
Serial  : 

Christophe.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2010-12-11 Thread Christophe Lyon
2010/12/11 Cédric VINCENT cedric.vinc...@gmail.com:
 Christophe, I should be able to provide you a kernel with the
 netconsole as a builtin on Monday if you wish.  Will you give it a try
 with ARMedSlack mini-rootfs and investigate what's going on?


Yes, it could be useful, thanks!
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2010-12-10 Thread Christophe Lyon
On Fri, Dec 10, 2010 at 12:30 AM, Claudio Cavalera
claudio.caval...@gmail.com wrote:
 On Thu, Dec 9, 2010 at 21:02, Christophe Lyon christophe.l...@gmail.com 
 wrote:

 I already have the right serial cable with the right connector. But
 I'm too lazy to open the dockstar. :-)

 Too bad!
 I misread your initial post and thought you actually succeeded in
 booting Slackware :-(

 Maybe I've booted it but it did not get an IP Address. Serial cable is
 for whimps. :-)
 Which parameters do you use at bootm= ?

As I said, I used Jeff Doozan's script to update my uboot, which also
sets to boot parameters.

I have:
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root
rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts

usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot

usb_boot=mw 0x80 0 1; ext2load usb $usb_device 0x80
/boot/uImage; if ext2load usb $usb_device 0x110 /boot/uInitrd;
then bootm 0x80 0x110; else bootm 0x80; fi

(usb_device is set to 0:1 by usb_scan)

bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run
usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

(I copied only the usb_bootcmd part, as it is the only relevant one here)

I have tried to add netconsole parameters to usb_set_bootargs, with no effect.

Christophe.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2010-12-10 Thread Christophe Lyon
 As I said, I used Jeff Doozan's script to update my uboot, which also
 sets to boot parameters.

 I have also used that script to update/patch my uboot but just for that.
 I then activated the netconsole and used uboot interactively with a
 couple of nc sessions. You should be able to do this if you read well
 within my old emails at this list.
 I think we are using completely different approaches.
 I was using a tftp server with tftpboot commands at uboot prompt.


Indeed, I'd like to avoid tftp if it's not absolutely necessary... and
I don't see why it would be.

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).

Christophe.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] ARMedSlack on Seagate Dockstar

2010-12-09 Thread Christophe Lyon

 I already have the right serial cable with the right connector. But
 I'm too lazy to open the dockstar. :-)

Too bad!
I misread your initial post and thought you actually succeeded in
booting Slackware :-(
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


Re: [ARMedslack] Setting up distcc for cross compiling

2010-08-31 Thread Christophe Lyon
 Did you use distcc there, too? What about moving all jobs to the other hosts?
 I know there are still tasks left for the build host (linking?), but no idea
 how much RAM they need.
 But I've already thought that RAM will be a problem. Perhaps there may be some
 tricks that can help, e.g.
 http://hostingfu.com/article/compiling-with-gcc-on-low-memory-vps

Why wouldn't you completely cross-build? I mean you don't have to link
on your ARM box given that you have already installed cross-toolchains
on your x86 hosts.


 Yes, I wanted to buy a SheevaPlug, but my prefered model seemed to be out of
 stock at the moment. Furthermore the Dockstar was so pretty cheap (20 €),
 that I just wanted to give it a try. And it looks fine in my living room with
 the 2.5 disk attached ;-) hdparm gives me a speed of 26 MB/s which is quite
 OK for an USB drive.
Too bad shipping costs are so high between Germany  France :-(

Christophe.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack