From m-lists at biscuit.org.uk Mon Jan 3 19:06:56 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 3 Jan 2011 19:06:56 +0000 (GMT) Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline Message-ID: Hi Since officially at the moment, Slackware ARM supports systems which have an ARMv5t minimum CPU, I am thinking of changing the baseline target CPU to be armv5t, rather than armv4t as it is at the moment. The reasoning is that: 1. I don't think the ARMedslack user base is huge and 2. Of that user base, who is actually using a system with anything less than an armv5 CPU? In my experience, armv4t systems are 1. Slow CPUs 2. Little RAM 3. Lack high capacity storage 4. Generally unsuitable to have any sort of enjoyable user experience running a general purpose OS such as Slackware. Therefore, I'd rather get whatever minimal improvements there are to be had by compiling for armv5t. Thoughts? -- Stuart Winter Slackware ARM: www.armedslack.org From unixjohn1969 at gmail.com Tue Jan 4 09:59:09 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Tue, 04 Jan 2011 04:59:09 -0500 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: References: Message-ID: <4D22EF6D.9050406@gmail.com> On 01/03/2011 02:06 PM, Stuart Winter wrote: > Since officially at the moment, Slackware ARM supports systems which have > an ARMv5t minimum CPU, I am thinking of changing the baseline target CPU > to be armv5t, rather than armv4t as it is at the moment. http://en.wikipedia.org/wiki/ARM_architecture Has a nice chart of what is out there with those processors. This would block out that little Zipit Wireless Messenger. My GP2X would be out too. But I'd never be installing Slackware on that. 64M RAM and 64M flash. Very custom device. http://wiki.gp2x.org/wiki/GP2X I wouldn't be upset if the base hardware were bumped up. -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Tue Jan 4 11:50:37 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 4 Jan 2011 11:50:37 +0000 (GMT) Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D22EF6D.9050406@gmail.com> References: <4D22EF6D.9050406@gmail.com> Message-ID: > This would block out that little Zipit Wireless Messenger. It looks like Zipit uses an Xscale which is armv5, so it would work, as far as I can tell. -- Stuart Winter Slackware ARM: www.armedslack.org From unixjohn1969 at gmail.com Tue Jan 4 11:55:25 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Tue, 04 Jan 2011 06:55:25 -0500 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: References: <4D22EF6D.9050406@gmail.com> Message-ID: <4D230AAD.20103@gmail.com> On 01/04/2011 06:50 AM, Stuart Winter wrote: > >> This would block out that little Zipit Wireless Messenger. > > It looks like Zipit uses an Xscale which is armv5, so it would work, as > far as I can tell. Zipit uses ARM720T (ARMv4T), the same as my GP2X primary processor (GP2X has a 940T co-processor) -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Tue Jan 4 12:03:51 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 4 Jan 2011 12:03:51 +0000 (GMT) Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D230AAD.20103@gmail.com> References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> Message-ID: > > It looks like Zipit uses an Xscale which is armv5, so it would work, as > > far as I can tell. > > Zipit uses ARM720T (ARMv4T), the same as my GP2X primary processor (GP2X has a > 940T co-processor) http://en.wikipedia.org/wiki/Zipit_Wireless_Messenger_%28Z2%29 So this must be a newer version? Even this version with 32MB RAM isn't suitable. I don't even think Slackware on x86 can really run reliably in 32MB of RAM. So I'm not exactly concerned about this device :) -- Stuart Winter Slackware ARM: www.armedslack.org From unixjohn1969 at gmail.com Tue Jan 4 12:14:23 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Tue, 04 Jan 2011 07:14:23 -0500 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> Message-ID: <4D230F1F.3010107@gmail.com> On 01/04/2011 07:03 AM, Stuart Winter wrote: > > >>> It looks like Zipit uses an Xscale which is armv5, so it would work, as >>> far as I can tell. >> >> Zipit uses ARM720T (ARMv4T), the same as my GP2X primary processor (GP2X has a >> 940T co-processor) > > http://en.wikipedia.org/wiki/Zipit_Wireless_Messenger_%28Z2%29 > > So this must be a newer version? > > Even this version with 32MB RAM isn't suitable. I don't even think > Slackware on x86 can really run reliably in 32MB of RAM. > > So I'm not exactly concerned about this device :) Dunno. I went off the entry in the http://en.wikipedia.org/wiki/ARM_architecture Which says ARM720T. must be wrong. I have a 386 40mhz AMD with a 387 coprocessor (ISA SCSI 9gb Seagate / 32MB Ram - huge for the day) in storage. Would love to test that theory... But another year maybe ;-) -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From jawkins at armedslack.org Tue Jan 4 12:27:35 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Tue, 4 Jan 2011 12:27:35 +0000 (GMT) Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D230F1F.3010107@gmail.com> References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D230F1F.3010107@gmail.com> Message-ID: On Tue, 4 Jan 2011, John O'Donnell wrote: > On 01/04/2011 07:03 AM, Stuart Winter wrote: > > > > > > It looks like Zipit uses an Xscale which is armv5, so it would work, as > > > > far as I can tell. > > > > > > Zipit uses ARM720T (ARMv4T), the same as my GP2X primary processor (GP2X > > > has a > > > 940T co-processor) > > > > http://en.wikipedia.org/wiki/Zipit_Wireless_Messenger_%28Z2%29 > > > > So this must be a newer version? > > > > Even this version with 32MB RAM isn't suitable. I don't even think > > Slackware on x86 can really run reliably in 32MB of RAM. > > > > So I'm not exactly concerned about this device :) > > Dunno. I went off the entry in the > http://en.wikipedia.org/wiki/ARM_architecture > Which says ARM720T. must be wrong. That page states that the "Zipit Wireless Messenger" has an ARM720T and the "Zipit Z2" has an XScale. Cheers, Jim From atelszewski at gmail.com Tue Jan 4 12:43:12 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 04 Jan 2011 13:43:12 +0100 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> Message-ID: <4D2315E0.40402@gmail.com> On 01/04/2011 01:03 PM, Stuart Winter wrote: > > Even this version with 32MB RAM isn't suitable. I don't even think > Slackware on x86 can really run reliably in 32MB of RAM. > > So I'm not exactly concerned about this device :) > > Hi, Armed works fine on device with 32MB of RAM. Remember that the need for memory depends on the services you need. Don't assume that Armed is only for strong devices, where you run X, KDE, etc. I like Armed and I like it running on my small device;) So if the gain from changing from v4 to v5 isn't really worth, then I prefer it staying v4 (my processor is arm920t). -- Pozdrawiam, Best regards, Andrzej Telszewski From unixjohn1969 at gmail.com Tue Jan 4 13:04:12 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Tue, 04 Jan 2011 08:04:12 -0500 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D2315E0.40402@gmail.com> References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D2315E0.40402@gmail.com> Message-ID: <4D231ACC.6090008@gmail.com> On 01/04/2011 07:43 AM, Andrzej Telszewski wrote: > I like Armed and I like it running on my small device;) So if the gain from > changing from v4 to v5 isn't really worth, then I prefer it staying v4 (my > processor is arm920t). What do you run it on and what do you run? I loved my GP2X but I couldnt conceive running armedslack. It was extremely small and custom. Like alot of the HD-DVD and Blu-Ray players I had seen back then. -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From atelszewski at gmail.com Tue Jan 4 13:22:02 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 04 Jan 2011 14:22:02 +0100 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D231ACC.6090008@gmail.com> References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D2315E0.40402@gmail.com> <4D231ACC.6090008@gmail.com> Message-ID: <4D231EFA.8020406@gmail.com> On 01/04/2011 02:04 PM, John O'Donnell wrote: > What do you run it on and what do you run? > I loved my GP2X but I couldnt conceive running armedslack. It was > extremely small and custom. Like alot of the HD-DVD and Blu-Ray players > I had seen back then. > Hi, It's my prototyping board, you can find it http://boff.pl/?shop=1&p_id=5 At the moment I'm not using it, because I don't have time - but soon it will be the subject of my thesis. See here for results on running Armed: http://lists.armedslack.org/pipermail/armedslack/2010-March/000354.html The main purpose I'd like to use this board is control home automation, but it is far future... -- Pozdrawiam, Best regards, Andrzej Telszewski From pino.otto at gmail.com Tue Jan 4 13:38:55 2011 From: pino.otto at gmail.com (Giovanni) Date: Tue, 4 Jan 2011 14:38:55 +0100 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D231EFA.8020406@gmail.com> References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D2315E0.40402@gmail.com> <4D231ACC.6090008@gmail.com> <4D231EFA.8020406@gmail.com> Message-ID: What about Openmoko FreeRunner? regards giovanni On Tue, Jan 4, 2011 at 2:22 PM, Andrzej Telszewski wrote: > On 01/04/2011 02:04 PM, John O'Donnell wrote: > >> What do you run it on and what do you run? >> I loved my GP2X but I couldnt conceive running armedslack. It was >> extremely small and custom. Like alot of the HD-DVD and Blu-Ray players >> I had seen back then. >> >> > Hi, > > It's my prototyping board, you can find it http://boff.pl/?shop=1&p_id=5 > At the moment I'm not using it, because I don't have time - but soon it > will be the subject of my thesis. > > See here for results on running Armed: > http://lists.armedslack.org/pipermail/armedslack/2010-March/000354.html > > The main purpose I'd like to use this board is control home automation, but > it is far future... > > > -- > Pozdrawiam, > Best regards, > Andrzej Telszewski > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From unixjohn1969 at gmail.com Tue Jan 4 14:04:32 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Tue, 04 Jan 2011 09:04:32 -0500 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D2315E0.40402@gmail.com> <4D231ACC.6090008@gmail.com> <4D231EFA.8020406@gmail.com> Message-ID: <4D2328F0.2040305@gmail.com> On 01/04/2011 08:38 AM, Giovanni wrote: > What about Openmoko FreeRunner? > > regards > giovanni Google is your friend http://www.google.com/search?q=openmoko+freerunner+processor * 400/500 MHz Samsung 2442B Processor/SOC (400 minimum, ARM920T core, ARMv4T) * Unbrickable dual Boot code in NAND FLASH and 2MB NOR FLASH * 128 MB SDRAM total, 64 MB CPU internal, 64 MB external * 256MB NAND Flash MCP package. -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Tue Jan 4 15:00:10 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 4 Jan 2011 15:00:10 +0000 (GMT) Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: <4D2315E0.40402@gmail.com> References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D2315E0.40402@gmail.com> Message-ID: > Armed works fine on device with 32MB of RAM. Heh. It's called "ARMedslack" or "Slackware ARM". Every time I see "Armed" I get images of men in balaclavas committing a bank robbery ;-) Yes 32MB will work for minimal services like dhcp, dns and stuff like that, but IME not much else! > I like Armed and I like it running on my small device;) So if the gain from > changing from v4 to v5 isn't really worth, then I prefer it staying v4 (my > processor is arm920t). I'm not yet sure of what performance increase there would be. I've read a bit about this but haven't come across any figures yet. I'll keep having a look around. -- Stuart Winter Slackware ARM: www.armedslack.org From thenktor at gmx.de Tue Jan 4 15:06:24 2011 From: thenktor at gmx.de (Thorsten =?ISO-8859-1?B?TfxobGZlbGRlcg==?=) Date: Tue, 4 Jan 2011 16:06:24 +0100 Subject: [ARMedslack] Thinking about changing Slackware ARM to armv5t baseline In-Reply-To: References: <4D22EF6D.9050406@gmail.com> <4D230AAD.20103@gmail.com> <4D2315E0.40402@gmail.com> Message-ID: <20110104160624.51ae0821@pinkfloyd.tm-net> Am Tue, 4 Jan 2011 15:00:10 +0000 (GMT) schrieb Stuart Winter : > > > Armed works fine on device with 32MB of RAM. > > Heh. It's called "ARMedslack" or "Slackware ARM". Every time I see > "Armed" I get images of men in balaclavas committing a bank > robbery ;-) > > Yes 32MB will work for minimal services like dhcp, dns and stuff like > that, but IME not much else! Yep, 32 MB is enough. See one of my devices (it uses 10 MB RAM so there should be enough left for some small services): root at slackware:~# free -m total used free shared buffers cached Mem: 60 29 31 0 0 18 -/+ buffers/cache: 10 49 Swap: 0 0 0 root at slackware:~# ps ax PID TTY STAT TIME COMMAND 1 ? Ss 0:21 init [3] 2 ? S 0:00 [kthreadd] 3 ? S 0:00 [ksoftirqd/0] 4 ? S 0:00 [events/0] 5 ? S 0:00 [khelper] 8 ? S 0:00 [async/mgr] 83 ? S 0:00 [sync_supers] 85 ? S 0:00 [bdi-default] 87 ? S 0:00 [kblockd/0] 98 ? S 0:00 [khubd] 118 ? S 0:00 [kswapd0] 119 ? S 0:00 [aio/0] 287 ? S 0:00 [mtdblock0] 292 ? S 0:00 [mtdblock1] 316 ? S 0:00 [yaffs-bg-1] 361 ? Ss 0:00 /usr/sbin/syslogd 392 ? Ss 0:00 /usr/sbin/klogd -c 3 -x 426 ? Ss 0:00 /sbin/dhcpcd -t 10 eth0 500 ? Ss 0:00 /usr/sbin/sshd 505 ? Ss 0:00 /usr/sbin/ntpd -g -p /var/run/ntpd.pid 510 ? Ss 0:00 /usr/sbin/crond -l10 512 ttyS0 Ss+ 0:00 /sbin/agetty -L ttyS0 115200 vt100 513 ttyS1 Ss+ 0:00 /sbin/agetty -L ttyS1 115200 vt100 514 ? Ss 0:00 sshd: root at ttyp0 516 ? S 0:00 [flush-31:1] 517 ttyp0 Ss 0:00 -bash 529 ttyp0 R+ 0:00 ps ax root at slackware:~# cat /proc/cpuinfo Processor : ARM926EJ-S rev 5 (v5l) BogoMIPS : 87.24 Features : swp half thumb fastmult edsp java CPU implementer : 0x41 CPU architecture: 5TEJ CPU variant : 0x0 CPU part : 0x926 CPU revision : 5 Hardware : Olimex SAM9-L9260 Revision : 0000 Serial : 0000000000000000 From m-lists at biscuit.org.uk Thu Jan 6 14:21:49 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 6 Jan 2011 14:21:49 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: > When I've got some time I'll look into making it work more reliably. Have you looked into it yet ? :-) From jawkins at armedslack.org Thu Jan 6 14:55:22 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Thu, 6 Jan 2011 14:55:22 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Thu, 6 Jan 2011, Stuart Winter wrote: > > When I've got some time I'll look into making it work more reliably. > > Have you looked into it yet ? :-) I did have a look actually, but I think I've run into an initialisation issue. It works intermittently - if you run up a kernel, halt and then reset via JTAG, it will detect the drive, but fail when trying to access it. If you reset the plug after that happens the drive then becomes accessible to u-boot. I'll look into it some more at some point. Cheers, Jim From m-lists at biscuit.org.uk Thu Jan 6 15:12:12 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 6 Jan 2011 15:12:12 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: > I did have a look actually, but I think I've run into an initialisation > issue. It works intermittently - if you run up a kernel, halt and then > reset via JTAG, it will detect the drive, but fail when trying to access > it. If you reset the plug after that happens the drive then becomes > accessible to u-boot. Is the symptom that when u-boot tries to find the drive, it stops with a "T" and won't go further? I see this on one of my sheevaplugs and afaict it's because the drive spun down. This is why I have a "reset" at the end of the boot command -- if the timeout happens, the plug reboots, the drive is still spinning and the boot works. This happens every time I complete a reinstallation of the plug (I assume because the spin down delay is just short enough that by the time the installer has shut itself down, and the system's rebooted, the drive has spun down). From jawkins at armedslack.org Thu Jan 6 17:00:54 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Thu, 6 Jan 2011 17:00:54 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Thu, 6 Jan 2011, Stuart Winter wrote: > > I did have a look actually, but I think I've run into an > > initialisation issue. It works intermittently - if you run up a > > kernel, halt and then reset via JTAG, it will detect the drive, but > > fail when trying to access it. If you reset the plug after that > > happens the drive then becomes accessible to u-boot. > > Is the symptom that when u-boot tries to find the drive, it stops with a > "T" and won't go further? It reads the drive info the first time you try, but fails after that: Marvell>> ide reset Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: SAMSUNG HD204UI Firm: 1AQ10001 Ser#: xxxx Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) Error (no IRQ) dev 0 blk 16: status 0xd0 IDE read: device 0 not ready Device 1: not available Marvell>> ide reset Reset IDE: Bus 0: ............................................................** Timeout ** not available Bus 1: ............................................................** Timeout ** not available Marvell>> > I see this on one of my sheevaplugs and afaict it's because the drive > spun down. This is why I have a "reset" at the end of the boot command > -- if the timeout happens, the plug reboots, the drive is still spinning > and the boot works. Yeah, sounds like it's because the drive has spun down. It's fine if you reboot from Linux without halting, which I assume doesn't cause a drive spin down. > This happens every time I complete a reinstallation of the plug (I > assume because the spin down delay is just short enough that by the time > the installer has shut itself down, and the system's rebooted, the drive > has spun down). Well you could have mentioned that before, couldn't you ;) Cheers, Jim From blair.hoddinott at gmail.com Thu Jan 6 17:01:38 2011 From: blair.hoddinott at gmail.com (blair.hoddinott at gmail.com) Date: Thu, 6 Jan 2011 17:01:38 +0000 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: <1042617683-1294333298-cardhu_decombobulator_blackberry.rim.net-338655008-@bda2673.bisx.prod.on.blackberry> Not for me, its just a straight no boot device error. :( Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Stuart Winter Sender: armedslack-bounces at lists.armedslack.org Date: Thu, 6 Jan 2011 15:12:12 Reply-To: Slackware ARM port Cc: Slackware ARM port Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus > I did have a look actually, but I think I've run into an initialisation > issue. It works intermittently - if you run up a kernel, halt and then > reset via JTAG, it will detect the drive, but fail when trying to access > it. If you reset the plug after that happens the drive then becomes > accessible to u-boot. Is the symptom that when u-boot tries to find the drive, it stops with a "T" and won't go further? I see this on one of my sheevaplugs and afaict it's because the drive spun down. This is why I have a "reset" at the end of the boot command -- if the timeout happens, the plug reboots, the drive is still spinning and the boot works. This happens every time I complete a reinstallation of the plug (I assume because the spin down delay is just short enough that by the time the installer has shut itself down, and the system's rebooted, the drive has spun down). _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Thu Jan 6 17:18:28 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 6 Jan 2011 17:18:28 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: > Yeah, sounds like it's because the drive has spun down. It's fine if you > reboot from Linux without halting, which I assume doesn't cause a drive > spin down. I just tried rebooting one of the SPs and the drive times out and u-boot reboots, then it works. > > the installer has shut itself down, and the system's rebooted, the drive > > has spun down). > > Well you could have mentioned that before, couldn't you ;) The boot command in the docs has "reset" as the last command, but you never read my docs do you ;-) -- Stuart Winter Slackware ARM: www.armedslack.org From jawkins at armedslack.org Thu Jan 6 22:40:05 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Thu, 6 Jan 2011 22:40:05 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Thu, 6 Jan 2011, Stuart Winter wrote: > I just tried rebooting one of the SPs and the drive times out and u-boot > reboots, then it works. The spin-up timeout in u-boot is set to 5 seconds, which seems a bit low - the specs for my drive say the typical drive ready time is 13s. I've increased the timeout to 30s and now it seems to work reliably. > The boot command in the docs has "reset" as the last command, but you > never read my docs do you ;-) Nope :) Cheers, Jim From m-lists at biscuit.org.uk Fri Jan 7 07:41:09 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 7 Jan 2011 07:41:09 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: > The spin-up timeout in u-boot is set to 5 seconds, which seems a bit low - > the specs for my drive say the typical drive ready time is 13s. I've > increased the timeout to 30s and now it seems to work reliably. If this works well can you upload the .bin to bourbon please and I'll distribute that instead of the one we have atm. Yours does have te ext2 support? -- Stuart Winter Slackware ARM: www.armedslack.org From jawkins at armedslack.org Fri Jan 7 13:27:03 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Fri, 7 Jan 2011 13:27:03 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Fri, 7 Jan 2011, Stuart Winter wrote: > > The spin-up timeout in u-boot is set to 5 seconds, which seems a bit > > low - the specs for my drive say the typical drive ready time is 13s. > > I've increased the timeout to 30s and now it seems to work reliably. > > If this works well can you upload the .bin to bourbon please and I'll > distribute that instead of the one we have atm. Why not compile your own u-boot binaries? I need to tidy up my changes, but I can give you my patches. > Yours does have te ext2 support? Yes. I'm booting my kernel from an ext2 formatted partition on an eSATA disk. Cheers, Jim From m-lists at biscuit.org.uk Fri Jan 7 13:39:27 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 7 Jan 2011 13:39:27 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: > > If this works well can you upload the .bin to bourbon please and I'll > > distribute that instead of the one we have atm. > > Why not compile your own u-boot binaries? I need to tidy up my changes, > but I can give you my patches. Because I don't have a guruplug to test it on, so I may as well take a pre-built binary that is known good. git clone git://git.denx.de/u-boot-marvell.git make guruplug Is this the same tree you used? I'll take your patches and build against that then, but someone else will have to test it since I don't have a guruplug. -- Stuart Winter Slackware ARM: www.armedslack.org From jawkins at armedslack.org Fri Jan 7 15:36:00 2011 From: jawkins at armedslack.org (Jim Hawkins) Date: Fri, 7 Jan 2011 15:36:00 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Fri, 7 Jan 2011, Stuart Winter wrote: > > > If this works well can you upload the .bin to bourbon please and > > > I'll distribute that instead of the one we have atm. > > > > Why not compile your own u-boot binaries? I need to tidy up my > > changes, but I can give you my patches. > > Because I don't have a guruplug to test it on, so I may as well take a > pre-built binary that is known good. You can test stuff on mine if you like. > git clone git://git.denx.de/u-boot-marvell.git > make guruplug > > Is this the same tree you used? I'm just using the master repo at git.denx.de/u-boot.git Cheers, Jim From blair.hoddinott at gmail.com Fri Jan 7 16:17:05 2011 From: blair.hoddinott at gmail.com (blair.hoddinott at gmail.com) Date: Fri, 7 Jan 2011 16:17:05 +0000 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: <1181777085-1294417021-cardhu_decombobulator_blackberry.rim.net-523283867-@bda2673.bisx.prod.on.blackberry> I can test it out on my guruplugs Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Jim Hawkins Sender: armedslack-bounces at lists.armedslack.org Date: Fri, 7 Jan 2011 15:36:00 To: Slackware ARM port Reply-To: Slackware ARM port Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus On Fri, 7 Jan 2011, Stuart Winter wrote: > > > If this works well can you upload the .bin to bourbon please and > > > I'll distribute that instead of the one we have atm. > > > > Why not compile your own u-boot binaries? I need to tidy up my > > changes, but I can give you my patches. > > Because I don't have a guruplug to test it on, so I may as well take a > pre-built binary that is known good. You can test stuff on mine if you like. > git clone git://git.denx.de/u-boot-marvell.git > make guruplug > > Is this the same tree you used? I'm just using the master repo at git.denx.de/u-boot.git Cheers, Jim _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Fri Jan 7 16:49:40 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 7 Jan 2011 16:49:40 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: > > Because I don't have a guruplug to test it on, so I may as well take a > > pre-built binary that is known good. > > You can test stuff on mine if you like. OK send me the details! > > git clone git://git.denx.de/u-boot-marvell.git > > make guruplug > > > > Is this the same tree you used? > > I'm just using the master repo at git.denx.de/u-boot.git OK can you put your patches onto bourbon when they're ready please. From christophe.lyon at gmail.com Sat Jan 8 21:46:28 2011 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Sat, 8 Jan 2011 22:46:28 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D1012D8.4070109@laprjns.com> References: <201012091514.36900.thenktor@gmx.de> <4D1012D8.4070109@laprjns.com> Message-ID: On Tue, Dec 21, 2010 at 3:37 AM, Rich 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. From blair.hoddinott at gmail.com Tue Jan 11 21:55:25 2011 From: blair.hoddinott at gmail.com (Blair Hoddinott) Date: Tue, 11 Jan 2011 16:55:25 -0500 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: Has anyone confirmed this resolves the problem with the eSATA booting? I'm about to give it a shot. _B On Fri, Jan 7, 2011 at 11:49 AM, Stuart Winter wrote: > > > > > Because I don't have a guruplug to test it on, so I may as well take a > > > pre-built binary that is known good. > > > > You can test stuff on mine if you like. > > OK send me the details! > > > > git clone git://git.denx.de/u-boot-marvell.git > > > make guruplug > > > > > > Is this the same tree you used? > > > > I'm just using the master repo at git.denx.de/u-boot.git > > OK can you put your patches onto bourbon when they're ready > please. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blair.hoddinott at gmail.com Tue Jan 11 23:58:53 2011 From: blair.hoddinott at gmail.com (Blair Hoddinott) Date: Tue, 11 Jan 2011 18:58:53 -0500 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: Ah, the U-Boot hasn't been updated on the website yet, my mistake. On Tue, Jan 11, 2011 at 4:55 PM, Blair Hoddinott wrote: > Has anyone confirmed this resolves the problem with the eSATA booting? I'm > about to give it a shot. > > _B > > On Fri, Jan 7, 2011 at 11:49 AM, Stuart Winter wrote: > >> >> >> > > Because I don't have a guruplug to test it on, so I may as well take a >> > > pre-built binary that is known good. >> > >> > You can test stuff on mine if you like. >> >> OK send me the details! >> >> > > git clone git://git.denx.de/u-boot-marvell.git >> > > make guruplug >> > > >> > > Is this the same tree you used? >> > >> > I'm just using the master repo at git.denx.de/u-boot.git >> >> OK can you put your patches onto bourbon when they're ready >> please. >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jan 14 09:25:10 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 14 Jan 2011 09:25:10 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> <4D1012D8.4070109@laprjns.com> Message-ID: > Thanks! I confirm it also works for me. http://salix.pastebin.com/J22Zudvw What boot line did you use? It looks as if you didn't specify the keyboard type nor network settings. ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/quickboot.txt You want the whole line that is underneath this: "-current (automatically starting DHCP and SSHd)" If you need to adjust the memory addresses then you'll need to do that of course; but the main changes are: nic=auto:eth0:dhcp kbd=uk and set your keyboard to a valid keymap that the "loadkeys" command can find. -- Stuart Winter Slackware ARM: www.armedslack.org From thenktor at gmx.de Fri Jan 14 09:56:05 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-15?q?M=FChlfelder?=) Date: Fri, 14 Jan 2011 10:56:05 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D1012D8.4070109@laprjns.com> References: <4D1012D8.4070109@laprjns.com> Message-ID: <201101141056.05705.thenktor@gmx.de> Am Tuesday 21 December 2010 03:37:12 schrieb Rich: > 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. I wonder how it booted the second time? IIRC I had to comment out the fdisk sectionin a rc script because the Dockstar does not have an RTC and after reboot the system time is set to 1970 again which causes another fsck run (fsck is forced if umount time is later than mount time). This ends up in an endless loop. > 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 Perhaps you remember that I've told you to do so ;-) From m-lists at biscuit.org.uk Fri Jan 14 10:20:51 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 14 Jan 2011 10:20:51 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <201101141056.05705.thenktor@gmx.de> References: <4D1012D8.4070109@laprjns.com> <201101141056.05705.thenktor@gmx.de> Message-ID: > I wonder how it booted the second time? IIRC I had to comment out the fdisk > sectionin a rc script because the Dockstar does not have an RTC and after > reboot the system time is set to 1970 again which causes another fsck run > (fsck is forced if umount time is later than mount time). This ends up in an > endless loop. This is how to do this properly: cat << EOF > etc/e2fsck.conf # These options stop e2fsck from erroring/requiring manual intervention # when it encounters bad time stamps on filesystems -- which happens on # the Versatile platform because QEMU does not have RTC (real time clock) # support. # [options] accept_time_fudge = 1 broken_system_clock = 1 EOF From thenktor at gmx.de Fri Jan 14 10:34:51 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Fri, 14 Jan 2011 11:34:51 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201101141056.05705.thenktor@gmx.de> Message-ID: <201101141134.51208.thenktor@gmx.de> Am Friday 14 January 2011 11:20:51 schrieb Stuart Winter: > > I wonder how it booted the second time? IIRC I had to comment out the > > fdisk sectionin a rc script because the Dockstar does not have an RTC and > > after reboot the system time is set to 1970 again which causes another > > fsck run (fsck is forced if umount time is later than mount time). This > > ends up in an endless loop. > > This is how to do this properly: > > cat << EOF > etc/e2fsck.conf > # These options stop e2fsck from erroring/requiring manual intervention > # when it encounters bad time stamps on filesystems -- which happens on > # the Versatile platform because QEMU does not have RTC (real time clock) > # support. > # > [options] > accept_time_fudge = 1 > broken_system_clock = 1 > EOF > Thanks! Looks like a much better and easier solution than editing the rc script ;-) From thenktor at gmx.de Fri Jan 14 10:38:53 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-15?q?M=FChlfelder?=) Date: Fri, 14 Jan 2011 11:38:53 +0100 Subject: [ARMedslack] Seagate Freeagent Dockstar price Message-ID: <201101141138.54059.thenktor@gmx.de> Hi, I've bought my Dockstar some months ago here in Germany for 20 ? + 5 ? shipping cost. Now I've noticed that the price has raised here to 80 ? + shipping. So my question is: What the cheapest price nowadays all over the world? Of course I have to check shipping cost to Germany then... Thanks for infos Thorsten From richard.lapointe at gmail.com Fri Jan 14 11:10:38 2011 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Fri, 14 Jan 2011 06:10:38 -0500 Subject: [ARMedslack] Seagate Freeagent Dockstar price In-Reply-To: <201101141138.54059.thenktor@gmx.de> References: <201101141138.54059.thenktor@gmx.de> Message-ID: This is the best I've seen lately: http://www.beachcamera.com/shop/product.aspx?sku=SESTDSA10GRK Rich Lapointe 2011/1/14 Thorsten M?hlfelder > Hi, > > I've bought my Dockstar some months ago here in Germany for 20 ? + 5 ? > shipping cost. Now I've noticed that the price has raised here to 80 ? + > shipping. > So my question is: What the cheapest price nowadays all over the world? Of > course I have to check shipping cost to Germany then... > > Thanks for infos > Thorsten > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Fri Jan 14 23:51:08 2011 From: richard.lapointe at gmail.com (richard.lapointe at gmail.com) Date: Fri, 14 Jan 2011 23:51:08 +0000 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de><4D1012D8.4070109@laprjns.com> Message-ID: <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> I got the chance to run a quick test last night so I loaded the installer and kernel onto a usb thumb drive ext2 partition, renamed them to uImage and uInitrd and booted with the existing doozan uboot and boot lines. As seen in the pastebin boot log, it booted normally until it stuck waiting for a keyboard entry. Since I was using a serial cable I was able to hit enter allowing the boot process to continue. Obviously I would not have able to continue if I did not have the serial cable. After logging in I check to see if the network interface was up and found that it was not. I assumed then that ssh was not running. After that I started the install process, using ftp install option. I didn't have enough time to complete the install but I have no doubt that it would have worked. So I would think the following three things need be addressed to allow the installer to work without the need for a serial cable: 1) Eliminate the need for a keyboard selection entry (may be a time out) 2) Start up dhcpd 3) Start up ssh Regards Rich Lapointe Sent via BlackBerry by AT&T -----Original Message----- From: Stuart Winter Sender: armedslack-bounces at lists.armedslack.orgDate: Fri, 14 Jan 2011 09:25:10 To: Slackware ARM port Reply-To: Slackware ARM port Subject: Re: [ARMedslack] ARMedSlack on Seagate Dockstar > Thanks! I confirm it also works for me. http://salix.pastebin.com/J22Zudvw What boot line did you use? It looks as if you didn't specify the keyboard type nor network settings. ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/quickboot.txt You want the whole line that is underneath this: "-current (automatically starting DHCP and SSHd)" If you need to adjust the memory addresses then you'll need to do that of course; but the main changes are: nic=auto:eth0:dhcp kbd=uk and set your keyboard to a valid keymap that the "loadkeys" command can find. -- Stuart Winter Slackware ARM: www.armedslack.org _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Sat Jan 15 09:40:44 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 15 Jan 2011 09:40:44 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> References: <201012091514.36900.thenktor@gmx.de><4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> Message-ID: > I got the chance to run a quick test last night so I loaded the > installer and kernel onto a usb thumb drive ext2 partition, renamed them > to uImage and uInitrd and booted with the existing doozan uboot and boot > lines. As seen in the pastebin boot log, it booted normally until it > stuck waiting for a keyboard entry. Since I was using a serial cable I > was able to hit enter allowing the boot process to continue. Obviously > I would not have able to continue if I did not have the serial cable. > After logging in I check to see if the network interface was up and > found that it was not. I assumed then that ssh was not running. After > that I started the install process, using ftp install option. I didn't > have enough time to complete the install but I have no doubt that it > would have worked. So I would think the following three things need be > addressed to allow the installer to work without the need for a serial > cable: 1) Eliminate the need for a keyboard selection entry (may be a > time out) 2) Start up dhcpd 3) Start up ssh These things are already taken care of, when you specify the correct boot parameters. What is the boot line you used in u-boot? From m-lists at biscuit.org.uk Thu Jan 20 11:17:19 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 20 Jan 2011 11:17:19 +0000 (GMT) Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages Message-ID: Hi Linux 2.6.36.3 works fine on my OpenRD client but on the SheevaPlug with a USB hard drive (/sev/sda), the MD raid module is binding to /dev/sda and preventing it from being used directly. I'm not sure why this is yet - I'm looking into it. -- Stuart Winter Slackware ARM: www.armedslack.org From claudio.cavalera at gmail.com Thu Jan 20 17:08:27 2011 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 20 Jan 2011 18:08:27 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> Message-ID: On Sat, Jan 15, 2011 at 10:40, Stuart Winter wrote: >> I got the chance to run a quick test last night so I loaded the >> installer and kernel onto a usb thumb drive ext2 partition, renamed them >> to uImage and uInitrd and booted with the existing doozan uboot and boot >> lines. ?As seen in the pastebin boot log, it booted normally until it >> stuck waiting for a keyboard entry. ?Since I was using a serial cable I >> was able to hit enter allowing the boot process to continue. ?Obviously >> I would not have able to continue if I did not have the serial cable. >> After logging in I check to see if the network interface was up and >> found that it was not. ?I assumed then that ssh was not running. ?After >> that I started the install process, using ftp install option. ?I didn't >> have enough time to complete the install but I have no doubt that it >> would have worked. So I would think the following three things need be >> addressed to allow the installer to work without the need for a serial >> cable: 1) Eliminate the need for a keyboard selection entry (may be a >> time out) 2) Start up dhcpd 3) Start up ssh > > These things are already taken care of, when you specify the > correct boot parameters. > > What is the boot line you used in u-boot? >From what I've understood Richard has used the bootline which is included in the patched Uboot from Jeff Doozan (e.g. plug the usb key and let the uboot boot the kernel and installer automagically). Instead with the serial cable (or with a netconsole activated in the uboot) it is possible by pressing enter during the startup to interrupt the boot process and type the commands to the uboot interactively. I have the feeling, but I might be wrong, that Richard has not done this. Come on guys, we are almost there! :-) Ciao, Claudio From pino.otto at gmail.com Thu Jan 20 19:56:24 2011 From: pino.otto at gmail.com (Giovanni) Date: Thu, 20 Jan 2011 20:56:24 +0100 Subject: [ARMedslack] Slackware on Pandaboard Message-ID: Is it possible to install Slackware ARM on Pandaboard? http://pandaboard.org If so, how? Do you have any instructions or suggestions? Best regards giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Jan 20 20:35:49 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 20 Jan 2011 20:35:49 +0000 (GMT) Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages In-Reply-To: References: Message-ID: > Linux 2.6.36.3 works fine on my OpenRD client but on the SheevaPlug with a > USB hard drive (/sev/sda), the MD raid module is binding to /dev/sda and > preventing it from being used directly. > > I'm not sure why this is yet - I'm looking into it. It's actually mdadm being naughty. I've reverted it to the previous version and I'll upload the rebuilt installer within the next day or so. I'm surprised nobody's noticed this problem before though. -- Stuart Winter Slackware ARM: www.armedslack.org From atelszewski at gmail.com Thu Jan 20 23:58:02 2011 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 21 Jan 2011 00:58:02 +0100 Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: References: Message-ID: <4D38CC0A.2000102@gmail.com> > Is it possible to install Slackware ARM on Pandaboard? > > http://pandaboard.org > > If so, how? Do you have any instructions or suggestions? First of all, you have to check if your processor is supported by Linux kernel. Then try to compile the kernel for your CPU and try to boot it. I see there is SD/MMC slot, so maybe it is possible to install OS there. -- Pozdrawiam, Best regards, Andrzej Telszewski From m-lists at biscuit.org.uk Fri Jan 21 08:34:39 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Jan 2011 08:34:39 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <201012091514.36900.thenktor@gmx.de> <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> Message-ID: > uboot) it is possible by pressing enter during the startup to > interrupt the boot process and type the commands to the uboot > interactively. I have the feeling, but I might be wrong, that Richard > has not done this. Come on guys, we are almost there! :-) I was speaking to Richard on IRC and I don't think it's as simple as it seems. You wanted to do this without a serial cable: I don't think it's possible to use the proper slackware installer to install onto this device. You're going to need to set the boot parameters in order to tell the kernel where the root partition is, and stuff like that. This is done normally by setting the config in u-boot to match what partition scheme you have chosen. Of course if you follow my docs exactly then you can paste in the ones from my docs, since they will match the partition scheme (also suggested in the docs). However, if you want a custom partition scheme then you will need to be able to configure your boot loader to pass the root= parameter to the kernel. >From reading the Debian stuff, my guess would be that the best way to proceed is to do something similar to what they've done: take the miniroot and write a script to set it up in the way that works best for the Doozan rescue system. You could then use slackpkg to upgrade the installation after the miniroot has been unpacked onto the device. They're not actually installing Debian using the debian installer. The easiest way is to get a serial cabl and stop faffing around ;-) From m-lists at biscuit.org.uk Fri Jan 21 08:40:02 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Jan 2011 08:40:02 +0000 (GMT) Subject: [ARMedslack] Slackware on Pandaboard In-Reply-To: <4D38CC0A.2000102@gmail.com> References: <4D38CC0A.2000102@gmail.com> Message-ID: > First of all, you have to check if your processor is supported by Linux > kernel. Then try to compile the kernel for your CPU and try to boot it. I see > there is SD/MMC slot, so maybe it is possible to install OS there. first thing: if you have such a device already in your posession: - download the miniroot fs for armedslack-current - chroot into it Does it work? If not then it's either: - because their kernel is older than linux 2.6.31 - or the userland of armedslack just doesn't work on that board (which would be sad, but possible). Ubuntu is on it already, so there's Kernel support for it -- the easiest thing I would do is to take the latest 2.6.37 or 2.6.38rc1 and check if the OMAP Panda Support is in the kernel - take which ever one has it (if it's there -- if not, find the patches and apply them to the appropriate kernel -- ensuring that it's at least linux 2.6.31). Compile the kernel: easiest thing first is to build a monolithic kernel with all of the bits your device will need. It's easier to bootstrap this way than to faff around with an initrd. Find out how to configure the boot loader to boot your own kernel. Ideally if it can tftp load then setup a tftp server and boot the kernel from there. Some of the Slackware ARM installation docs explain how to do this. Once you've got that far you can then boot into a miniroot and see how far you get. This board looks interesting. If they sell it with a case, I'd be tempted to get one. From m-lists at biscuit.org.uk Fri Jan 21 13:25:43 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Jan 2011 13:25:43 +0000 (GMT) Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages In-Reply-To: References: Message-ID: > It's actually mdadm being naughty. > I've reverted it to the previous version and I'll upload the rebuilt > installer within the next day or so. > > I'm surprised nobody's noticed this problem before though. After dd /dev/zero the whole disc, repartitioning and re-creating the filesystems, putting mdadm-2.6 back into the installer and installing; I now find that mdadm-3 works just fine with Linux 2.6.36.3 on the same system. I've no idea whatsoever what's gone on there, but it seems everything works now. -- Stuart Winter Slackware ARM: www.armedslack.org From unixjohn1969 at gmail.com Fri Jan 21 13:32:24 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 21 Jan 2011 08:32:24 -0500 Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages In-Reply-To: References: Message-ID: <4D398AE8.1020608@gmail.com> On 01/21/2011 08:25 AM, Stuart Winter wrote: > >> It's actually mdadm being naughty. >> I've reverted it to the previous version and I'll upload the rebuilt >> installer within the next day or so. >> >> I'm surprised nobody's noticed this problem before though. > > After dd /dev/zero the whole disc, repartitioning and re-creating the > filesystems, putting mdadm-2.6 back into the installer and installing; > I now find that mdadm-3 works just fine with Linux 2.6.36.3 on the same > system. > > I've no idea whatsoever what's gone on there, but it seems everything > works now. > shouldnt have to DD the whole disk as zero just the first few blocks.. errrr what i tried at least for a few other problems... -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Fri Jan 21 13:48:25 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Jan 2011 13:48:25 +0000 (GMT) Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages In-Reply-To: <4D398AE8.1020608@gmail.com> References: <4D398AE8.1020608@gmail.com> Message-ID: > shouldnt have to DD the whole disk as zero just the first few blocks.. errrr > what i tried at least for a few other problems... I know - but mdadm was still taking /dev/sda even *without* partitions. I'm guessing somehow, somewhere, there was some residue from when the disc may have been in a raid configuration somewhere on another system from where the disc originated (I have a collection of old discs from a variety of places where I used to be a sysadmin). *shrug* From unixjohn1969 at gmail.com Fri Jan 21 13:54:09 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 21 Jan 2011 08:54:09 -0500 Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages In-Reply-To: References: <4D398AE8.1020608@gmail.com> Message-ID: <4D399001.2060200@gmail.com> On 01/21/2011 08:48 AM, Stuart Winter wrote: > >> shouldnt have to DD the whole disk as zero just the first few blocks.. errrr >> what i tried at least for a few other problems... > > I know - but mdadm was still taking /dev/sda even *without* partitions. > I'm guessing somehow, somewhere, there was some residue from when the disc > may have been in a raid configuration somewhere on another system from > where the disc originated (I have a collection of old discs from a > variety of places where I used to be a sysadmin). > > *shrug* You should write to the mdadm writers as that is really weird . I would hav zeroed and started from there. There are asking for failure! -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Fri Jan 21 14:01:23 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Jan 2011 14:01:23 +0000 (GMT) Subject: [ARMedslack] Problem with Linux 2.6.36.3 packages In-Reply-To: <4D399001.2060200@gmail.com> References: <4D398AE8.1020608@gmail.com> <4D399001.2060200@gmail.com> Message-ID: > > *shrug* > You should write to the mdadm writers as that is really weird . I would hav > zeroed and started from there. There are asking for failure! That was the plan - reinstall and get a working system by putting mdadm-2.6 into the installer, boot into the new OS and start working out why 3.x was behaving as it was; but after the fresh installation onto the new partitions, the problem's gone away -- so I can't replicate anymore. I've just reinstalled whilst having 3.x in the installer again, and the problem no longer exists. From richard.lapointe at gmail.com Sun Jan 23 20:33:22 2011 From: richard.lapointe at gmail.com (Rich) Date: Sun, 23 Jan 2011 15:33:22 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> Message-ID: <4D3C9092.3050201@laprjns.com> OK, I've got a way of getting the installer started on my Dockstar without the use of a serial line. This method requires Jeff Doozan's uboot, first because it has uboot environments that allow to boot off a usb drive and second it installs fw_setenv and fw_print command line routines into the pogoplugs (and Dockstar) stock operating system. These are needed because there are some bootargs that need to be passed to slack installer to get the network up and a keyboard selected. Jeff's uboot environment includes a variable called usb_custum_params which can be used to pass these needed bootargs so that the installer doesn't get "stuck". So here how it done: 1. SSH into the Dockstar stock operating system (pogoplug) 2. Install Jeff's uboot per these instructions http://jeff.doozan.com/debian/uboot/. After the new uboot is installed reboot into the pogoplug operating system and ssh back in. 3.Add the needed uboot environment parameters. fw_setenv usb_custom_params nic=auto:eth0:dhcp kbd=uk 4. Partition a drive with partition 1 (sda1) and format to ext2 file system. You may be able to use others types, but this is the only type I've tried. Mount the partition: mkdir /tmp/sda1 mount /dev/sda1 /mnt/sda1 5.Make a /boot directory on the new partition and copy the armedSlack installer and kernel to it mkdir /tmp/sda1/boot cd /tmp/sda1/boot wget ftp://ftp.slackware.org.uk/armedslack/armedslack-current/kernels/kirkwood/uImage-kirkwood wget ftp://ftp.slackware.org.uk/armedslack/armedslack-current/isolinux/uinitrd-kirkwood.img 6.Create some symbolic links Jeff uboot looks to boot uImage and uInitrd so do the following ln -s uImage-kirkwood uImage ln -s uinitrd-kirkwood.img uInitrd 7.Reboot! A word of warning, it took over three minutes to boot into the installer, but I think this depends on the usb device that you use. If you have questions, check the armedSlack irc channel, I'm usually log in. Regards Rich Lapointe On 01/21/2011 03:34 AM, Stuart Winter wrote: > >> uboot) it is possible by pressing enter during the startup to >> interrupt the boot process and type the commands to the uboot >> interactively. I have the feeling, but I might be wrong, that Richard >> has not done this. Come on guys, we are almost there! :-) >> > I was speaking to Richard on IRC and I don't think it's as simple as it > seems. > > You wanted to do this without a serial cable: I don't think it's possible > to use the proper slackware installer to install onto this device. > > You're going to need to set the boot parameters in order to tell > the kernel where the root partition is, and stuff like that. > This is done normally by setting the config in u-boot to match > what partition scheme you have chosen. Of course if you follow my docs > exactly then you can paste in the ones from my docs, since they will > match the partition scheme (also suggested in the docs). > However, if you want a custom partition > scheme then you will need to be able to configure your boot loader to pass > the root= parameter to the kernel. > > > From reading the Debian stuff, my guess would be that the best way to > proceed is to do something similar to what they've done: take the miniroot > and write a script to set it up in the way that works best for the > Doozan rescue system. You could then use slackpkg to upgrade > the installation after the miniroot has been unpacked onto the > device. > They're not actually installing Debian using the debian installer. > > The easiest way is to get a serial cabl and stop faffing around ;-) > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christophe.lyon at gmail.com Tue Jan 25 22:30:55 2011 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Tue, 25 Jan 2011 23:30:55 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D3C9092.3050201@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> Message-ID: Hi! On Sun, Jan 23, 2011 at 9:33 PM, Rich wrote: > OK, I've got a way of getting the installer started on my Dockstar without > the use of a serial line. Thanks for this procedure. I have tried it but... The installer started, and the installation seemed to be OK, but when I reboot, the netconsole only shows "Starting kernel...." and I am not able to ssh into the dockstar anymore :-( At configuration time, I have asked for DHCP, so I think it's OK. Any hints except buying a serial cable? :-) (BTW, any pointer to the right cable to purchase?) Christophe. From richard.lapointe at gmail.com Wed Jan 26 01:11:12 2011 From: richard.lapointe at gmail.com (Rich) Date: Tue, 25 Jan 2011 20:11:12 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> Message-ID: <4D3F74B0.5010805@laprjns.com> 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 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. 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. 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_Accessories&hash=item2ea601b2ac It literally came on a slow boat from China :) Regards Rich Lapointe On 01/25/2011 05:30 PM, Christophe Lyon wrote: > Hi! > > On Sun, Jan 23, 2011 at 9:33 PM, Rich wrote: > >> OK, I've got a way of getting the installer started on my Dockstar without >> the use of a serial line. >> > Thanks for this procedure. I have tried it but... The installer > started, and the installation seemed to be OK, but when I reboot, the > netconsole only shows "Starting kernel...." and I am not able to ssh > into the dockstar anymore :-( > At configuration time, I have asked for DHCP, so I think it's OK. > > Any hints except buying a serial cable? :-) (BTW, any pointer to the > right cable to purchase?) > > Christophe. > > From donnie at thepennington.com Wed Jan 26 04:24:38 2011 From: donnie at thepennington.com (Donnie Pennington) Date: Tue, 25 Jan 2011 23:24:38 -0500 Subject: [ARMedslack] Setting Time Sheeva Armedslack Message-ID: I successfully installed armedslack-current to my new Sheeva plug (on an sd card) following Stuart's excellent INSTALL_KIRKWOOD directions. But I'm stumped by the system clock. Nothing I do will set the time. The plug thinks it's March 2010 and that's all there is to it. I've run ntpdate to known good time servers and run hwclock -w to no avail. Any thoughts? -- Donnie -------------- next part -------------- An HTML attachment was scrubbed... URL: From donnie at thepennington.com Wed Jan 26 05:03:16 2011 From: donnie at thepennington.com (Donnie Pennington) Date: Wed, 26 Jan 2011 00:03:16 -0500 Subject: [ARMedslack] Setting Time Sheeva Armedslack Message-ID: False alarm, I figured it out. Sorry for the noise. -- Donnie -------------- next part -------------- An HTML attachment was scrubbed... URL: From claudio.cavalera at gmail.com Wed Jan 26 08:39:12 2011 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Wed, 26 Jan 2011 09:39:12 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D3F74B0.5010805@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: On Wed, Jan 26, 2011 at 02:11, Rich 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. I'm sorry I have not had time to look into this yet; However I think it's good news, I hope we can make this procedure official somehow. Is it possible to host the jeff uboot on armedslack.org without breaking any license? If you backup the full USB with dd and put it on another one, would it boot ? Thanks, Claudio From m-lists at biscuit.org.uk Wed Jan 26 09:37:40 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 26 Jan 2011 09:37:40 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D3F74B0.5010805@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: On Tue, 25 Jan 2011, Rich 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. He's not managed to get the OS installed. I suspect you ought to look at your DHCP server logs and find out what IP address the Dockstar has been given. From claudio.cavalera at gmail.com Wed Jan 26 10:42:10 2011 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Wed, 26 Jan 2011 11:42:10 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: On Wed, Jan 26, 2011 at 10:37, Stuart Winter wrote: > > He's not managed to get the OS installed. > Stuart what do you mean? Cristophe wrote: "Thanks for this procedure. I have tried it but... The installer started, and the installation seemed to be OK, but when I reboot, the netconsole only shows "Starting kernel...." and I am not able to ssh into the dockstar anymore :-( At configuration time, I have asked for DHCP, so I think it's OK." Isn't he talking about the reboot at the end of installation? Thanks, Claudio From m-lists at biscuit.org.uk Wed Jan 26 10:56:16 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 26 Jan 2011 10:56:16 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: > > He's not managed to get the OS installed. > > > > Stuart what do you mean? > > Cristophe wrote: > "Thanks for this procedure. I have tried it but... The installer > started, and the installation seemed to be OK, but when I reboot, the [..] > Isn't he talking about the reboot at the end of installation? I think you're right! I misread that. Forget what I said - do what Richard said :-) From claudio.cavalera at gmail.com Wed Jan 26 11:01:25 2011 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Wed, 26 Jan 2011 12:01:25 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: On Wed, Jan 26, 2011 at 11:56, Stuart Winter wrote: > >> > He's not managed to get the OS installed. >> > >> >> Stuart what do you mean? >> >> Cristophe wrote: >> "Thanks for this procedure. I have tried it but... The installer >> started, and the installation seemed to be OK, but when I reboot, the > > [..] >> Isn't he talking about the reboot at the end of installation? > > > I think you're right! I misread that. > > Forget what I said - do what Richard said :-) Now I expect full official support by armed slack and the patched uboot available too! :-) From m-lists at biscuit.org.uk Wed Jan 26 11:11:58 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 26 Jan 2011 11:11:58 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: > > Forget what I said - do what Richard said :-) > > Now I expect full official support by armed slack and the patched > uboot available too! :-) I expect to win the lottery too, but it ain't happened yet. What does "official support" mean? All that I can see is that the INSTALL_KIRKWOOD doc needs a couple of extra points to make the installation work: - fsck config - starting NTP on boot Can you actually upgradepkg the kernel packages and reboot into the new kernel without modifying any u-boot config? If you give me all the u-boot stuff, I can put the u-boot binaies on the ftp site and link to them from the "device maintenance" page on the web site. I'm not sure where I'd put the modifying of the u-boot environment/rescue thing. From claudio.cavalera at gmail.com Wed Jan 26 11:24:59 2011 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Wed, 26 Jan 2011 12:24:59 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: On Wed, Jan 26, 2011 at 12:11, Stuart Winter wrote: > >> > Forget what I said - do what Richard said :-) >> >> Now I expect full official support by armed slack and the patched >> uboot available too! :-) > > I expect to win the lottery too, but it ain't happened yet. Just joking. :-) > What does "official support" mean? You should put a dockstar on a wishlist so that we can buy it to you and then you could test and mantain armedslack on it! :-) > All that I can see is that the INSTALL_KIRKWOOD doc needs a couple of > extra points to make the installation work: > ?- fsck config > ?- starting NTP on boot This is what I mean, provide full instructions to install on a dockstar. > Can you actually upgradepkg the kernel packages and reboot into the new > kernel without modifying any u-boot config? I don't know but I think yes, in debian for sure I've already apt-get upgraded the kernel. However this is a test for Richard and Cristophe. > If you give me all the u-boot stuff, I can put the u-boot binaies on the > ftp site and link to them from the "device maintenance" page on the web > site. > I'm not sure where I'd put the modifying of the u-boot environment/rescue > thing. The rescue thing is not necessary and I would avoid it. It's just a matter of the uboot. *Maybe* we could have a page on armedslack web site like this one: http://jeff.doozan.com/debian/uboot/ and hosting an adjusted script like this http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh which pulls out things from the armedslack website instead of doozan.com We should inform doozan though. :-) the fw_printenv stuff I don't think is really needed, if we could patch the uboot to have the special bootline needed for the dockstar... I agree, it's a lot of work anyway but dockstars are nice! :-) Ciao, Claudio From m-lists at biscuit.org.uk Wed Jan 26 13:59:39 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 26 Jan 2011 13:59:39 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: > You should put a dockstar on a wishlist so that we can buy it to you > and then you could test and mantain armedslack on it! :-) Hah. I'd not put a Dockstar on it, that's for sure :-) On a serious note: I'm very cautious about expanding the range of "official" (meaning it works out of the box and I endevour to make sure the OS works on it) supported devices, due to a mixture of time and interest. My thoughts are that if someone's interested in a device then they can check whether the new packages work (usually kernels and x11 would be device specific) and let me know. > > extra points to make the installation work: > > ?- fsck config > > ?- starting NTP on boot > > This is what I mean, provide full instructions to install on a dockstar. OK - give me a diff to the INSTALL_KIRKWOOD doc and I'll look at it. > *Maybe* we could have a page on armedslack web site like this one: > http://jeff.doozan.com/debian/uboot/ You mean like this? http://www.armedslack.org/maint_kirkwooduboot > and hosting an adjusted script like this > http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh Can't you just use nandwrite from the u-boot console? The script looks far too complicated: - can't you just use nandwrite from the u-boot console? - or use the mtd tools in linux to write it? I don't like tools which download stuff from web sites and try to automate things. My preference is to include simple, pasteable commands. (which may happen to include wget); but it's nicer to let the user see what's going on. > I agree, it's a lot of work anyway but dockstars are nice! :-) Nice as paper weights, yes ;-) From christophe.lyon at gmail.com Wed Jan 26 21:41:46 2011 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Wed, 26 Jan 2011 22:41:46 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D3F74B0.5010805@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: On Wed, Jan 26, 2011 at 2:11 AM, Rich 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_Accessories&hash=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/ From richard.lapointe at gmail.com Thu Jan 27 00:01:00 2011 From: richard.lapointe at gmail.com (Rich) Date: Wed, 26 Jan 2011 19:01:00 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: <4D40B5BC.10507@laprjns.com> On 01/26/2011 03:39 AM, Claudio Cavalera wrote: > Is it possible to host the jeff uboot on armedslack.org without > breaking any license? > Why would you need to do this?. Just get it off of Jeff site > If you backup the full USB with dd and put it on another one, would it boot ? > It should of you plug it into the same dockstar. Regards Rich Lapointe From richard.lapointe at gmail.com Thu Jan 27 00:09:49 2011 From: richard.lapointe at gmail.com (Rich) Date: Wed, 26 Jan 2011 19:09:49 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: <4D40B7CD.6060106@laprjns.com> On 01/26/2011 06:11 AM, Stuart Winter wrote: > Can you actually upgradepkg the kernel packages and reboot into the new > kernel without modifying any u-boot config? > Yes, as long as you changed the symbolic links to point to the new kernel and initrd. > If you give me all the u-boot stuff, I can put the u-boot binaies on the > ftp site and link to them from the "device maintenance" page on the web > site. > Why not just leave there on Jeff's site and just put the link in the armedslack installation instructions > I'm not sure where I'd put the modifying of the u-boot environment/rescue thing. > Again, why not put it the instructions. Also you can ignore the rescue thing, it's needed. Jeff's has kind of a generic uboot with some environmental variables to boot his rescue system. If the rescue system is not installed the uboot just go on to the next thing to try and boot. Regards Rich Lapointe > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > From richard.lapointe at gmail.com Thu Jan 27 00:33:26 2011 From: richard.lapointe at gmail.com (Rich) Date: Wed, 26 Jan 2011 19:33:26 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: <4D40BD56.60601@laprjns.com> On 01/26/2011 06:24 AM, Claudio Cavalera wrote: > On Wed, Jan 26, 2011 at 12:11, Stuart Winter wrote: > >> Can you actually upgradepkg the kernel packages and reboot into the new >> kernel without modifying any u-boot config? >> > I don't know but I think yes, in debian for sure I've already apt-get > upgraded the kernel. > However this is a test for Richard and Cristophe. > Yes, as long as you change the symbolic links to point to the new kernel >> If you give me all the u-boot stuff, I can put the u-boot binaies on the >> ftp site and link to them from the "device maintenance" page on the web >> site. >> I'm not sure where I'd put the modifying of the u-boot environment/rescue >> thing. >> > The rescue thing is not necessary and I would avoid it. It's just a > matter of the uboot. Yes, the rescue thing is not necessary but it s nice to have. It's mini operating system that's better than the stock plug software. Regards Rich Lapointe From richard.lapointe at gmail.com Thu Jan 27 00:52:57 2011 From: richard.lapointe at gmail.com (Rich) Date: Wed, 26 Jan 2011 19:52:57 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: <4D40C1E9.60403@laprjns.com> On 01/26/2011 08:59 AM, Stuart Winter wrote: >> *Maybe* we could have a page on armedslack web site like this one: >> http://jeff.doozan.com/debian/uboot/ > You mean like this? > http://www.armedslack.org/maint_kirkwooduboot and hosting an adjusted script like this >> http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh >> > Can't you just use nandwrite from the u-boot console? > The script looks far too complicated: > - can't you just use nandwrite from the u-boot console? > - or use the mtd tools in linux to write it? > > I don't like tools which download stuff from web sites and try to automate > things. My preference is to include simple, pasteable commands. > (which may happen to include wget); but it's nicer to let the user see > what's going on. > > Both Debian and plugapps do their install by a mini root file system, not an installer like we're using. In Debian case, Jeff has created a completely automatic script, which I imagine is a lot of work to maintain. Plugapps uses instructions just i a wiki format http://plugapps.com/index.php5?title=Ten%28ish%29_steps_to_setting_up_a_Seagate_Dockstar All you need to do is copy and paste. I think that instructions is all that is needed. By the way, the uboot variables are only needed to boot the installer, they are not required once you go through an installation. Regards Rich Lapointe From richard.lapointe at gmail.com Thu Jan 27 01:25:11 2011 From: richard.lapointe at gmail.com (Rich) Date: Wed, 26 Jan 2011 20:25:11 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> Message-ID: <4D40C977.8010206@laprjns.com> On 01/26/2011 04:41 PM, Christophe Lyon wrote: > > What are exactly the necessary changes? I have only uncommented the line > server pool.ntp.org > Edit the ntp.conf file to un-comment the server pool line like this: #server 127.127.1.0 # local clock #fudge 127.127.1.0 stratum 10 server pool.ntp.org #server 192.168.101.1 > When I reboot, nothing has changed :-( uboot says 'starting kernel' > and then nothing more. You should not expect to see anything more on your netconsole once the armedSlack kernel starts to boot. Did you set up the network during in the installation?. Assuming you did need to open another terminal screen, change to root an ssh into the dockstar from there. If you set it up using dhcp then you'll have to check your router or something to see what ip it assigned to the dockstar. > At the same time, the dockstar& usb key stop > blinking. > The dockstar led is controlled by uboot and armedSlack's kernel doesn't know how to control it. > > 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? > yes, you can reformat during the install process. The installer gets loaded into ram and the usb stick is not used after loading; >> 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. > Yes, about the same for me. >> 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_Accessories&hash=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/ > yea, or if you are not worry about looks and you don't mind having it connected all the time go to Radio shack and buy a wire wrap tool http://www.radioshack.com/product/index.jsp?productId=2103243&CAWELAID=107590412 Regards Rich Lapointe From unixjohn1969 at gmail.com Thu Jan 27 06:35:39 2011 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 27 Jan 2011 01:35:39 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D40C977.8010206@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40C977.8010206@laprjns.com> Message-ID: <4D41123B.8050504@gmail.com> 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 -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From claudio.cavalera at gmail.com Thu Jan 27 08:43:56 2011 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 27 Jan 2011 09:43:56 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D40B5BC.10507@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40B5BC.10507@laprjns.com> Message-ID: On Thu, Jan 27, 2011 at 01:01, Rich wrote: > On 01/26/2011 03:39 AM, Claudio Cavalera wrote: >> >> Is it possible to host the jeff uboot on armedslack.org without >> breaking any license? >> > > Why would you need to do this?. ?Just get it off of Jeff site Maybe it's better to be on our own concerning stuff to be downloaded, but I'm not sure. Ciao, Claudio From thenktor at gmx.de Thu Jan 27 14:38:21 2011 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 27 Jan 2011 15:38:21 +0100 Subject: [ARMedslack] mfloat-abi Message-ID: <201101271538.22016.thenktor@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? And why is none of them used in Armed Slack? In my understanding it should be much faster than FPU emulation in the kernel. http://www.arm.linux.org.uk/mailinglists/faq.php#f3 Greetings Thorsten From christophe.lyon at gmail.com Thu Jan 27 21:36:05 2011 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Thu, 27 Jan 2011 22:36:05 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D40C977.8010206@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40C977.8010206@laprjns.com> Message-ID: On Thu, Jan 27, 2011 at 2:25 AM, Rich wrote: > On 01/26/2011 04:41 PM, Christophe Lyon wrote: >> I can't reformat it during the install process, otherwise it will the >> installer given that it contains /boot, right? >> > > yes, you can reformat during the install process. ?The installer gets loaded > into ram and the usb stick is not used after loading; Good news! I finally managed to reboot after installation!!! This time, I reformatted during the install. Upon reboot, uboot (Jeff Doozan's) complained that it did not find /boot/uImage nor /boot/uInitrd. I recreated them, and voila! I guess that during my previous installs withouth reformatting, the installer left dangling symlinks in /boot, and uboot did not manage to handle them properly? I am not really convinced by this explanation because uboot used to go until 'starting kernel', so it did seem to succeed loading it. So to summarize, I think than Richard's procedure should be completed by cd /mnt/sda1//boot ln -s uImage-kirkwood uImage ln -s uinitrd-kirkwood.img uInitrd at least after reformattting. I can give another try without reformatting during install if you want. Thanks guys! From christophe.lyon at gmail.com Thu Jan 27 21:38:42 2011 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Thu, 27 Jan 2011 22:38:42 +0100 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D41123B.8050504@gmail.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40C977.8010206@laprjns.com> <4D41123B.8050504@gmail.com> Message-ID: On Thu, Jan 27, 2011 at 7:35 AM, John O'Donnell 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 From christophe.lyon at gmail.com Thu Jan 27 21:45:54 2011 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Thu, 27 Jan 2011 22:45:54 +0100 Subject: [ARMedslack] mfloat-abi In-Reply-To: <201101271538.22016.thenktor@gmx.de> References: <201101271538.22016.thenktor@gmx.de> Message-ID: 2011/1/27 Thorsten M?hlfelder : > 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 From richard.lapointe at gmail.com Fri Jan 28 00:44:37 2011 From: richard.lapointe at gmail.com (Rich) Date: Thu, 27 Jan 2011 19:44:37 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40C977.8010206@laprjns.com> Message-ID: <4D421175.7040909@laprjns.com> On 01/27/2011 04:36 PM, Christophe Lyon wrote: > > So to summarize, I think than Richard's procedure should be completed by > cd /mnt/sda1//boot > ln -s uImage-kirkwood uImage > ln -s uinitrd-kirkwood.img uInitrd > at least after reformattting. > > I can give another try without reformatting during install if you want. > > Thanks guys! > > Oops, your right, I forgot to add that to my earlier email. Rich Lapointe From richard.lapointe at gmail.com Fri Jan 28 00:51:19 2011 From: richard.lapointe at gmail.com (Rich) Date: Thu, 27 Jan 2011 19:51:19 -0500 Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40C977.8010206@laprjns.com> <4D41123B.8050504@gmail.com> Message-ID: <4D421307.70300@laprjns.com> On 01/27/2011 04:38 PM, Christophe Lyon wrote: > On Thu, Jan 27, 2011 at 7:35 AM, John O'Donnell 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 at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Control of the LED isn't high on my list yet, but there is a lot of information here; http://forum.doozan.com/read.php?2,524 It's Debian centric, but you get the idea. I really haven't read completely through it yet but i think for kernels < 2.6.36 you need to patch them. For 36 and up there has been some type of dockstar support added to the kernel. Rich Lapointe From m-lists at biscuit.org.uk Fri Jan 28 11:39:07 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 28 Jan 2011 11:39:07 +0000 (GMT) Subject: [ARMedslack] ARMedSlack on Seagate Dockstar In-Reply-To: <4D421307.70300@laprjns.com> References: <4D1012D8.4070109@laprjns.com> <1965398766-1295049073-cardhu_decombobulator_blackberry.rim.net-1045577298-@bda285.bisx.prod.on.blackberry> <4D3C9092.3050201@laprjns.com> <4D3F74B0.5010805@laprjns.com> <4D40C977.8010206@laprjns.com> <4D41123B.8050504@gmail.com> <4D421307.70300@laprjns.com> Message-ID: > http://forum.doozan.com/read.php?2,524 > It's Debian centric, but you get the idea. I really haven't read completely > through it yet but i think for kernels < 2.6.36 you need to patch them. For > 36 and up there has been some type of dockstar support added to the kernel. The new kernels in -current have the dockstar support compiled in. From m-lists at biscuit.org.uk Fri Jan 28 11:39:34 2011 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 28 Jan 2011 11:39:34 +0000 (GMT) Subject: [ARMedslack] mfloat-abi In-Reply-To: References: <201101271538.22016.thenktor@gmx.de> Message-ID: > - 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. You can also do gcc -dumpspecs to see what the compiler's defaults are.