From w.lohman at chello.nl Thu Jun 11 09:16:05 2009 From: w.lohman at chello.nl (w.lohman at chello.nl) Date: Thu, 11 Jun 2009 11:16:05 +0200 Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <482596.79753.qm@web57905.mail.re3.yahoo.com> References: <482596.79753.qm@web57905.mail.re3.yahoo.com> Message-ID: <200906111116.05954.w.lohman@chello.nl> Hi! There where more people working on the ARMedslack/Freerunner combo. I'm curious, any progress yet? I sometimes feel these are uncharted waters and the methods for the Sheevalug don't translate 1:1 to the Freerunner. Alas I don't have much time on my hands at the moment, so I'm not progressing as fast as I'd like. But I give it a couple of hours per week. Most time working on this I spend reading though... All very interesting, but it'll be good to start something with #!/bin/bash again sometime soon and get some results ;-) If someone is interested in discussing what needs to be done in order to install ARMedslack on the Freerunner? Cheers, Wybrand On Saturday 30 May 2009 08:47:19 Guilherme Alberici de Santi wrote: > Hello everyone, > I am new to list and also new to the Linux embedded community. > I work for Sony Ericsson in a project emulating hardware like the QEMU. > I am running Slackware in x86 hardware for years and now it is time to run > it on an ARM machine, but I have little background in doing this. I have > bought a Neo FreeRunner and want to run ARMedslack on it. > Does anyone have some idea on the first steps I have to go into? > Thanks for any help. > > Guilherme > > > > Veja quais s?o os assuntos do momento no Yahoo! +Buscados > http://br.maisbuscados.yahoo.com From hachreak at gmail.com Thu Jun 11 12:28:01 2009 From: hachreak at gmail.com (Leo) Date: Thu, 11 Jun 2009 14:28:01 +0200 Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <200906111116.05954.w.lohman@chello.nl> References: <482596.79753.qm@web57905.mail.re3.yahoo.com> <200906111116.05954.w.lohman@chello.nl> Message-ID: Hi to all, i was an italian slackware and freerunner young supporter. > If someone is interested in discussing what needs to be done in order to > install ARMedslack on the Freerunner? > I'm very interested!!! I have a FreeRunner and love Slack! :D But i haven't experience to port slackware into embedded device.. :-p Now i use SHR distro, but if i can... :-p bye bye .hachreak. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guidesanti at yahoo.com.br Thu Jun 11 16:39:44 2009 From: guidesanti at yahoo.com.br (Guilherme Alberici de Santi) Date: Thu, 11 Jun 2009 09:39:44 -0700 (PDT) Subject: [armedslack] ARMedSlack running on Neo FreeRunner Message-ID: <878561.12176.qm@web57902.mail.re3.yahoo.com> Hi, I am very interested in ARMedslack and Neo FreeRunner. However, I am waiting for my Neo to arrive to start working on it. I have no idea in where to start this task, but as soon as I have some news I can post here the progress of the work and everyone is welcome to help on this task. I don't know, but I think the first steps are to install the boot loader correctly into the NAND flash of the Neo FreeRunner and flash a kernel image with the console device drivers to be able to see the kernel messages when it was booting. Any suggestions on this stuffs? Guilherme --- Em qui, 11/6/09, w.lohman at chello.nl escreveu: De: w.lohman at chello.nl Assunto: Re: [armedslack] ARMedSlack running on Neo FreeRunner Para: armedslack at lists.armedslack.org Data: Quinta-feira, 11 de Junho de 2009, 6:16 Hi! There where more people working on the ARMedslack/Freerunner combo. I'm curious, any progress yet? I sometimes feel these are uncharted waters and the methods for the Sheevalug don't translate 1:1 to the Freerunner. Alas I don't have much time on my hands at the moment, so I'm not progressing as fast as I'd like. But I give it a couple of hours per week. Most time working on this I spend reading though... All very interesting, but it'll be good to start something with #!/bin/bash again sometime soon and get some results ;-) If someone is interested in discussing what needs to be done in order to install ARMedslack on the Freerunner? Cheers, Wybrand On Saturday 30 May 2009 08:47:19 Guilherme Alberici de Santi wrote: > Hello everyone, > I am new to list and also new to the Linux embedded community. > I work for Sony Ericsson in a project emulating hardware like the QEMU. > I am running Slackware in x86 hardware for years and now it is time to run > it on an ARM machine, but I have little background in doing this. I have > bought a Neo FreeRunner and want to run ARMedslack on it. > Does anyone have some idea on the first steps I have to go into? > Thanks for any help. > > Guilherme > > > >? ? ???Veja quais s?o os assuntos do momento no Yahoo! +Buscados > http://br.maisbuscados.yahoo.com Veja quais s?o os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Jun 11 19:09:53 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 11 Jun 2009 20:09:53 +0100 (BST) Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <878561.12176.qm@web57902.mail.re3.yahoo.com> References: <878561.12176.qm@web57902.mail.re3.yahoo.com> Message-ID: It's probably more simple than you think - it took me about a week in the evenings after work to get ARMedslack installing natively on the SheevaPlug; which involved some additional work on the installer, and packages, which means it *should* be easier to add new ports. I do already have the ARM build environment setup and I know how Slackware works pretty well, so I had a head start, but even so, it's probably not *too* much work ;-) The main things are: 1. Find yourself a good kernel '.config' Make sure that it does NOT compile with the 'New EABI' # CONFIG_AEABI is not set To begin with it'd be easier to compile all of the hardware support, including filesystems, into the kernel - just to bootstrap. Once that's done, go back to a modular kernel. I can add support to build another Kernel and initrd pretty easily. Check out armedslack-current/source/k/kernel.SlackBuild Some of it's a bit hairy (esp the installing of modules onto the filesystem) but it works fine! 2. Build the kernel. 3. Figure out what you need to do to get the Kernel onto the device, how you interact with the boot loader Usually Debian or Gentoo have done this already, so you can follow their documentation. 4. Boot the Kernel and see if it works. Even if you use it to try and boot the existing Linux OS (if it has one onboard/flash) then it'll fail because the OS will probably be EABI and your Kernel is oldabi. At least it boots :-) 5. What I did to get ARMedslack bootstrapped onto the SheevaPlug was to take an existing ARMedslack installation from a QEMU image, extract it, partition & format a USB stick, and rsync the QEMU image onto the usb stick. ftp://ftp.armedslack.org/armedslack/armedslack-current/QEMU_INSTALL.TXT You can install an ARMedslack natively using QEMU by following the document above. Then rather than booting the OS and rsycning from inside the live filesystem (since that'd take *ages* and I'd have to stop udev and stuff like that), I mounted the QEMU disk on the x86 and rsynced from there -- follow this doc: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/qemu-to-sheeva.txt Once that's done, I booted my new 'kirkwood' (SheevaPlug) Kernel and it booted. Once that was done I had to do some more work to make ARMedslack's build scripts work with another set of Kernel and Kernel modules, and add support for root logins over serial console; stopping some packages from being configured from the installer. The FreeRunner probably requires other stuff - maybe some additional support packages, or configuration changes - but to at least get ARMedslack running so you can login remotely, it *may* be reasonably simple! If anybody has any questions about it then feel free to ask on here. I intend on releasing ARMedslack next week, now that Linux 2.6.30 has been released; and from there I'll be starting on the new EABI port but still could add an additional architecture to ARMedslack 12.2 at a later date, since the EABI port won't be available for a long while. On Thu, 11 Jun 2009, Guilherme Alberici de Santi wrote: > Hi, > I am very interested in ARMedslack and Neo FreeRunner. > However, I am waiting for my Neo to arrive to start working on it. > I have no idea in where to start this task, but as soon as I have some news I can post here the progress of the work and everyone is welcome to help on this task. > > I don't know, but I think the first steps are to install the boot loader correctly into the NAND flash of the Neo FreeRunner and flash a kernel image with the console device drivers to be able to see the kernel messages when it was booting. > > Any suggestions on this stuffs? > > Guilherme > > > > --- Em qui, 11/6/09, w.lohman at chello.nl escreveu: > > De: w.lohman at chello.nl > Assunto: Re: [armedslack] ARMedSlack running on Neo FreeRunner > Para: armedslack at lists.armedslack.org > Data: Quinta-feira, 11 de Junho de 2009, 6:16 > > Hi! > > There where more people working on the ARMedslack/Freerunner combo. I'm > curious, any progress yet? > > I sometimes feel these are uncharted waters and the methods for the Sheevalug > don't translate 1:1 to the Freerunner. Alas I don't have much time on my > hands at the moment, so I'm not progressing as fast as I'd like. But I give > it a couple of hours per week. Most time working on this I spend reading > though... All very interesting, but it'll be good to start something with > #!/bin/bash again sometime soon and get some results ;-) > > If someone is interested in discussing what needs to be done in order to > install ARMedslack on the Freerunner? > > Cheers, > Wybrand > > > > On Saturday 30 May 2009 08:47:19 Guilherme Alberici de Santi wrote: > > Hello everyone, > > I am new to list and also new to the Linux embedded community. > > I work for Sony Ericsson in a project emulating hardware like the QEMU. > > I am running Slackware in x86 hardware for years and now it is time to run > > it on an ARM machine, but I have little background in doing this. I have > > bought a Neo FreeRunner and want to run ARMedslack on it. > > Does anyone have some idea on the first steps I have to go into? > > Thanks for any help. > > > > Guilherme > > > > > > > >? ? ???Veja quais s?o os assuntos do momento no Yahoo! +Buscados > > http://br.maisbuscados.yahoo.com > > > > > > > Veja quais s?o os assuntos do momento no Yahoo! +Buscados > http://br.maisbuscados.yahoo.com -- Stuart Winter www.armedslack.org From w.lohman at chello.nl Thu Jun 11 20:50:35 2009 From: w.lohman at chello.nl (w.lohman at chello.nl) Date: Thu, 11 Jun 2009 22:50:35 +0200 Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: References: <878561.12176.qm@web57902.mail.re3.yahoo.com> Message-ID: <200906112250.35418.w.lohman@chello.nl> I'm installing my first ARMedslack version inside Qemu at the moment. Stuart, your documentation is excellent! But boy! When you said the installer inside Qemu was slow, you wheren't kidding where you? This is 1.6Ghz iron it's running on, and I don't mean 1.6 dual Core :-( Anyways, I haven't wrapped my head around how I can shave off enough MB to fit into the openmoko yet. That seems a different program all together. There is the SD card capable of ~500MB, but other than that I need to bring the rootfs back to ~100MB (to allow for a good margin). But that means subtracting from the Qemu install, because otherwise I can't compile a kernel inside Qemu. Hmmmm, I'm not sure if I can get that right all in one go. I'll keep you posted on progress, but I'm allowed out of the dark basement untill monday, so I'm not expecting to do anything serious before then :-p @Guilherme You asked for advice. Feel free but just flash the device a couple of times with different Freerunner OS's when you get the Freerunner. Get USB-networking going and make yourself comfertable with ssh'ing into it. It's easy enough, but it's good to get a little familiar with things that work on the Freerunner before you sail into these uncharted waters. Oh, and if you don't already know how to mount jffs2 filesystems, read into that too. It's *ehm* different? I'm looking for a good howto :-S And you asked about kernel messages, but that is not a big deal. They come to screen if you can read Real Fast, and otherwise dmesg|less does the trick nicely. --- btw I looked at the Debian and Gentoo people to see how they where doing, but it seems to me they are doing it very different from how I have things in mind. We'll see. It all depends I guess on what you want the device to do when you're done. Or perhaps I have to bump my nose a couple of times before I see what they have seen? The trick will be to keep it small enough but workable. I had a mind to use the initrd of ARMedslacks installer, convert this to jffs2 just to Prove the Concept and thus gain something bootable. Knowing the initrd of Slackwares installer, there is everything you need for testing purposes. Monday. Cheers, Wybrand On Thursday 11 June 2009 21:09:53 Stuart Winter wrote: > It's probably more simple than you think - it took me about a week in the > evenings after work to get ARMedslack installing natively on the > SheevaPlug; which involved some additional work on the installer, and > packages, which means it *should* be easier to add new ports. > I do already have the ARM build environment setup and I know > how Slackware works pretty well, so I had a head start, but even > so, it's probably not *too* much work ;-) > > > The main things are: > 1. Find yourself a good kernel '.config' > Make sure that it does NOT compile with the 'New EABI' > # CONFIG_AEABI is not set > To begin with it'd be easier to compile all of the hardware > support, including filesystems, into the kernel - just to bootstrap. > Once that's done, go back to a modular kernel. I can add > support to build another Kernel and initrd pretty easily. > Check out armedslack-current/source/k/kernel.SlackBuild > Some of it's a bit hairy (esp the installing of modules onto > the filesystem) but it works fine! > > 2. Build the kernel. > > 3. Figure out what you need to do to get the Kernel onto the > device, how you interact with the boot loader > Usually Debian or Gentoo have done this already, so you can > follow their documentation. > > 4. Boot the Kernel and see if it works. > Even if you use it to try and boot the existing Linux OS > (if it has one onboard/flash) then it'll fail because the > OS will probably be EABI and your Kernel is oldabi. > At least it boots :-) > > 5. What I did to get ARMedslack bootstrapped onto the SheevaPlug > was to take an existing ARMedslack installation from a QEMU > image, extract it, partition & format a USB stick, and > rsync the QEMU image onto the usb stick. > > ftp://ftp.armedslack.org/armedslack/armedslack-current/QEMU_INSTALL.TXT > > You can install an ARMedslack natively using QEMU by following the > document above. > Then rather than booting the OS and rsycning from inside the > live filesystem (since that'd take *ages* and I'd have to stop udev and > stuff like that), I mounted the > QEMU disk on the x86 and rsynced from there -- follow this doc: > ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/qemu-to- >sheeva.txt > > Once that's done, I booted my new 'kirkwood' (SheevaPlug) Kernel and > it booted. > Once that was done I had to do some more work to make ARMedslack's build > scripts work with another set of Kernel and Kernel modules, and add > support for root logins over serial console; stopping some packages > from being configured from the installer. > > The FreeRunner probably requires other stuff - maybe some additional > support packages, or configuration changes - but to at least get > ARMedslack running so you can login remotely, it *may* be reasonably > simple! > > If anybody has any questions about it then feel free to ask on here. > I intend on releasing ARMedslack next week, now that Linux 2.6.30 has > been released; and from there I'll be starting on the new EABI port > but still could add an additional architecture to ARMedslack 12.2 > at a later date, since the EABI port won't be available for a long > while. > > On Thu, 11 Jun 2009, Guilherme Alberici de Santi wrote: > > Hi, > > I am very interested in ARMedslack and Neo FreeRunner. > > However, I am waiting for my Neo to arrive to start working on it. > > I have no idea in where to start this task, but as soon as I have some > > news I can post here the progress of the work and everyone is welcome to > > help on this task. > > > > I don't know, but I think the first steps are to install the boot loader > > correctly into the NAND flash of the Neo FreeRunner and flash a kernel > > image with the console device drivers to be able to see the kernel > > messages when it was booting. > > > > Any suggestions on this stuffs? > > > > Guilherme > > > > > > > > --- Em qui, 11/6/09, w.lohman at chello.nl escreveu: > > > > De: w.lohman at chello.nl > > Assunto: Re: [armedslack] ARMedSlack running on Neo FreeRunner > > Para: armedslack at lists.armedslack.org > > Data: Quinta-feira, 11 de Junho de 2009, 6:16 > > > > Hi! > > > > There where more people working on the ARMedslack/Freerunner combo. I'm > > curious, any progress yet? > > > > I sometimes feel these are uncharted waters and the methods for the > > Sheevalug don't translate 1:1 to the Freerunner. Alas I don't have much > > time on my hands at the moment, so I'm not progressing as fast as I'd > > like. But I give it a couple of hours per week. Most time working on this > > I spend reading though... All very interesting, but it'll be good to > > start something with #!/bin/bash again sometime soon and get some results > > ;-) > > > > If someone is interested in discussing what needs to be done in order to > > install ARMedslack on the Freerunner? > > > > Cheers, > > Wybrand > > > > On Saturday 30 May 2009 08:47:19 Guilherme Alberici de Santi wrote: > > > Hello everyone, > > > I am new to list and also new to the Linux embedded community. > > > I work for Sony Ericsson in a project emulating hardware like the QEMU. > > > I am running Slackware in x86 hardware for years and now it is time to > > > run it on an ARM machine, but I have little background in doing this. I > > > have bought a Neo FreeRunner and want to run ARMedslack on it. > > > Does anyone have some idea on the first steps I have to go into? > > > Thanks for any help. > > > > > > Guilherme > > > > > > > > > > > >? ? ???Veja quais s?o os assuntos do momento no Yahoo! +Buscados > > > http://br.maisbuscados.yahoo.com > > > > Veja quais s?o os assuntos do momento no Yahoo! +Buscados > > http://br.maisbuscados.yahoo.com From hachreak at gmail.com Thu Jun 11 22:50:10 2009 From: hachreak at gmail.com (Leo) Date: Fri, 12 Jun 2009 00:50:10 +0200 Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <878561.12176.qm@web57902.mail.re3.yahoo.com> References: <878561.12176.qm@web57902.mail.re3.yahoo.com> Message-ID: 2009/6/11 Guilherme Alberici de Santi > Hi, > I am very interested in ARMedslack and Neo FreeRunner. > However, I am waiting for my Neo to arrive to start working on it. > I have no idea in where to start this task, but as soon as I have some news > I can post here the progress of the work and everyone is welcome to help on > this task. > > I don't know, but I think the first steps are to install the boot loader > correctly into the NAND flash of the Neo Flash new distro into frerunner is very simple with dfu-utils! Read this: http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner I have a question to cross-compile software: openmoko use bitbake. I haven't experience, but i think is more complicated! For example, hackable1 use a more standard system: http://example.org/2003/12/13/atom03 with standard $ ./configure --host=arm-linux-gnueabi $ make what is your experience? :D bye bye .hachreak. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guidesanti at yahoo.com.br Fri Jun 12 17:07:13 2009 From: guidesanti at yahoo.com.br (Guilherme Alberici de Santi) Date: Fri, 12 Jun 2009 10:07:13 -0700 (PDT) Subject: [armedslack] ARMedSlack running on Neo FreeRunner Message-ID: <231114.65673.qm@web57906.mail.re3.yahoo.com> Hi, in fact I have a very little expericence in cross compilers, but I think it should not be very difficult to create and use a cross compiler or you can get a pre-build toolchain (the precompiled binaries). I have found some instructions here http://www.ailis.de/~k/archives/19-ARM-cross-compiling-howto.html to build your own cross-compiler and binutils. May be I am wrong but as I have understood OpenMoko project uses a GNU toolchain and Bitbike is something like the build system of the kernel or something like a a build system scheme. It is not the cross-compiler itself. As soon as I have more knowlegde about this I post more news here. Guilherme --- Em qui, 11/6/09, Leo escreveu: De: Leo Assunto: Re: [armedslack] ARMedSlack running on Neo FreeRunner Para: armedslack at lists.armedslack.org Data: Quinta-feira, 11 de Junho de 2009, 19:50 2009/6/11 Guilherme Alberici de Santi Hi, I am very interested in ARMedslack and Neo FreeRunner. However, I am waiting for my Neo to arrive to start working on it. I have no idea in where to start this task, but as soon as I have some news I can post here the progress of the work and everyone is welcome to help on this task. I don't know, but I think the first steps are to install the boot loader correctly into the NAND flash of the Neo Flash new distro into frerunner is very simple with dfu-utils! Read this: http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner ?I have a question to cross-compile software: openmoko use bitbake. I haven't experience, but i think is more complicated! For example, hackable1 use a more standard system: http://example.org/2003/12/13/atom03 with standard $ ./configure --host=arm-linux-gnueabi $ make what is your experience? :D ???????? bye bye???? .hachreak. Veja quais s?o os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From w.lohman at chello.nl Fri Jun 12 16:14:42 2009 From: w.lohman at chello.nl (Wybrand Lohman) Date: Fri, 12 Jun 2009 18:14:42 +0200 Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: References: <878561.12176.qm@web57902.mail.re3.yahoo.com> Message-ID: <200906121814.42483.w.lohman@chello.nl> Hi, I can't ssh to my new ARMedslack install. When I ssh into the virtual machine, it asks for the password and when I fill that in it complains about my password being expired and asks for a new one. I then get the familiar routine that I have to fill in the old password, and the new one twice. Then the connection closes, and this is every time. Can this be related to the local time being epoch?? Hmmm, I can still telnet so it's not a big deal. Oh, and Stuart, in your QEMU_INSTALL.TXT I missed a `modprobe tun`. I added this to /etc/rc.d/rc.local, and everything worked flawlesly. Good work! Cheers, Wybrand From m-lists at biscuit.org.uk Sat Jun 13 13:04:37 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 13 Jun 2009 14:04:37 +0100 (BST) Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <200906121814.42483.w.lohman@chello.nl> References: <878561.12176.qm@web57902.mail.re3.yahoo.com> <200906121814.42483.w.lohman@chello.nl> Message-ID: Hi Wybrand > I can't ssh to my new ARMedslack install. When I ssh into the virtual machine, > it asks for the password and when I fill that in it complains about my > password being expired and asks for a new one. > I then get the familiar routine that I have to fill in the old password, and > the new one twice. Then the connection closes, and this is every time. Can > this be related to the local time being epoch?? Hmmm, I can still telnet so > it's not a big deal. If you add an ntpdate or similar to your VM's rc.local, as it suggests in the qemu_install doc, does that fix it on the 2nd login? I used to have this problem until I set the time with ntpdate. What I also do, which isn't documented, is run ntpdate from the installer so that the files generated during installation have a fresh time stamp; which fixes the problem. I'll update the QEMU install document with some more information. > Oh, and Stuart, in your QEMU_INSTALL.TXT I missed a `modprobe tun`. I added > this to /etc/rc.d/rc.local, and everything worked flawlesly. Good work! Thanks I forgot about that - tun is compiled into my kernel. I've added modprobes into the qemu helper scripts. -- Stuart Winter www.armedslack.org From m-lists at biscuit.org.uk Sat Jun 13 13:28:14 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 13 Jun 2009 14:28:14 +0100 (BST) Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <231114.65673.qm@web57906.mail.re3.yahoo.com> References: <231114.65673.qm@web57906.mail.re3.yahoo.com> Message-ID: Hi > in fact I have a very little expericence in cross compilers, but I think > it should not be very difficult to create and use a cross compiler or > you can get a pre-build toolchain (the precompiled binaries). I have > found some instructions here > http://www.ailis.de/~k/archives/19-ARM-cross-compiling-howto.html to > build your own cross-compiler and binutils. [..] You'd need to check whether the binaries the toolchain produces are for old ABI or new abi. Example: On ARMedslack: readelf -h /bin/ls | grep -i flag Flags: 0x2, has entry point, GNU EABI This means that it's using the Old ABI. Taking an 'armel' (their definition for 'ARM eabi, Little endian') Debian binary, for example, you'll see: New ABI: Flags: 0x4000002, has entry point, Version4 EABI For the current ARMedslack release, you need to make sure that your toolchain produces output for the oldabi. I build ARMedslack by building natively, but using distcc to distribute the compile jobs to a number of X86 machines running a cross compiler, and a distccd. I build the toolchain myself using the script here. I haven't built it for a while, but everything in here ought to work on Slackware 12.2 at least: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain (you might need to wait for it to appear on the ftp site - the sync only runs every few hours) That toolchain build script builds just what it needs to work with distcc, and puts it into /opt/arm on your x86. You then start distccd on the x86 hosts by adding this line to /etc/rc.d/rc.local # Distcc: PATH=/opt/arm/bin /usr/bin/distccd -j 50 --daemon --allow 0/0 The number of jobs is probably a bit high there - I actually don't have a super computer in my front room ;-) Then, on my ARMedslack installations, I have this script: root at stokely:~# cat ~/armedslack/dbuild #!/bin/bash if [ -f .no-distcc ]; then echo "This source is not to be built with distcc (.no-distcc exists)" ./arm/build else if [ ! -d /tmp/DISTCC ]; then mkdir -p /tmp/DISTCC ( cd /tmp/DISTCC ln -vfs /usr/bin/distcc gcc ln -vfs /usr/bin/distcc cc ln -vfs /usr/bin/distcc g++ ln -vfs /usr/bin/distcc c++ ln -vfs /usr/bin/distcc arm-slackware-linux-c++ ln -vfs /usr/bin/distcc arm-slackware-linux-g++ ln -vfs /usr/bin/distcc arm-slackware-linux-gcc ) fi # With zippo: # export DISTCC_HOSTS="192.168.1.1/2 192.168.1.15/2 192.168.1.11/2 192.168.1.2 192.168.1.14" # export NUMJOBS="-j5" # Without zippo: # export DISTCC_HOSTS="192.168.1.1/2 192.168.1.15/2 192.168.1.11/2 192.168.1.2" # With turrican: export DISTCC_HOSTS="192.168.1.2/2 192.168.1.1/2 192.168.1.15/2 192.168.1.11/2" export NUMJOBS="-j8" # Without turrican or zippo: # Timeouts may happen with distcc when compiling huge things, but these # timeouts aren't configureable so distcc will stop waiting and run natively # instead :-( export DISTCC_HOSTS="192.168.1.1/2 192.168.1.15/2 192.168.1.11/2" export NUMJOBS="-j4" export CC=distcc PATH=/tmp/DISTCC:$PATH ./arm/build $@ fi root at stokely:~# To build bash, for example: cd armedslack-current/source/a/bash ~/armedslack/dbuild And this script runs the 'arm/build' script inside 'source/a/bash', setting up the environment to use distcc rather than a local C compiler. It's a bit hacky which is why I don't include these scripts in the source tree, but it works. From m-lists at biscuit.org.uk Sat Jun 13 13:36:33 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 13 Jun 2009 14:36:33 +0100 (BST) Subject: [armedslack] ARMedSlack running on Neo FreeRunner In-Reply-To: <200906112250.35418.w.lohman@chello.nl> References: <878561.12176.qm@web57902.mail.re3.yahoo.com> <200906112250.35418.w.lohman@chello.nl> Message-ID: > I'm installing my first ARMedslack version inside Qemu at the moment. Stuart, > your documentation is excellent! But boy! When you said the installer inside > Qemu was slow, you wheren't kidding where you? This is 1.6Ghz iron it's > running on, and I don't mean 1.6 dual Core :-( Oh - yeah. I feel for you ;-) I can barely bring myself to use QEMU now I've got the SheevaPlugs - I only use it to test that AS still *works* in QEMU ;-) > back to ~100MB (to allow for a good margin). But that means subtracting from > the Qemu install, because otherwise I can't compile a kernel inside Qemu. The thing doesn't have a Network card and you can't mount a temp dir over NFS? > We'll see. It all depends I guess on what you want the device to do when > you're done. Or perhaps I have to bump my nose a couple of times before I see > what they have seen? Yes - this is the case, and is why I am only personally interested in particular ARM devices that have a minimum of 512MB RAM, a fast CPU, and can use a hard disk - I need build machines where I can build the entire of Slackware. I'm really looking forward to these ARM laptops. That'd be my dream to have ARMedslack running on one of those and use it as my day to day laptop! > The trick will be to keep it small enough but workable. I had a mind to use > the initrd of ARMedslacks installer, convert this to jffs2 just to Prove the > Concept and thus gain something bootable. Knowing the initrd of Slackwares > installer, there is everything you need for testing purposes. Monday. I can't include the actual build script for the Slackware installer, but the one attached might be useful. The installer for the 'kirkwood' is produced by reprocessing the 'Versatile' installer, and replacing the Versatile kernel modules with the kirkwood ones, and adding some additional modules that are required for the Kirkwood. At the top of the script it sources part of the 'slackkit' package's package building kit. For this script, it's really only using $PKGSTORE, which is a pointer to where your armedslack tree is: armedslack-current/slackware Have fun! :) -------------- next part -------------- #!/bin/bash ############################################################## # Script: mk-kirkwood.sh # Purpose: Take the ARM Versatile Slackware ARM installer and # produce a new installer for the Marvell Kirkwood # devices. # Author : Stuart Witner # Date : 15-May-2009 ############################################################### # Load in the ARMedslack build kit from the 'slackkit' package. source /usr/share/slackdev/buildkit.sh # For any -rc releases, remove the hyphen. KERNELVER="$( ls -1 $PKGSTORE/a/kernel_kirkwood*.t?z | head -1 | rev | cut -d- -f3 | rev | cut -d_ -f1 )" SLKARCH=kirkwood cd /tmp rm -rf kirkwood-installer mkdir -vpm755 kirkwood-installer/{unpack,tree} cd kirkwood-installer LIST=/tmp/kirkwood-installer/i-mod-list # Unpack the Versatile installer. # The installers for all ARM architectures are identical - the # only thing we need to change per architecture is the Kernel modules. # The default architecture for ARMedslack is the 'Versatile' because # it's the most accessible, being supported by QEMU. # pushd tree zcat $PKGSTORE/../isolinux/initrd-versatile.img | cpio -div cd lib/modules/ ( cd *versatile* #find . -type f | sed 's?.gz??' > $LIST # Generate the list of Kernel modules which are included in the installer: find . -type f > $LIST ) # Delete the ARM Versatile kernel modules; we'll be replacing these # with the Kirkwood's. rm -rf *versatile* EXTPOS=$PWD popd # Add a few additional modules required for the Kirkwood series. # These can include specific hardware drivers, or additional # USB/SCSI drivers which aren't needed by the ARM Versatile # board. # # cat << EOF >> $LIST ./kernel/drivers/mmc/ ./kernel/drivers/net/mv643xx_eth.ko.gz ./kernel/drivers/usb/storage/usb-libusual.ko.gz ./kernel/drivers/scsi/scsi_tgt.ko.gz ./kernel/drivers/scsi/scsi_mod.ko.gz ./kernel/drivers/scsi/sg.ko.gz ./kernel/lib/crc-t10dif.ko.gz ./kernel/drivers/usb/core/usbcore.ko.gz ./kernel/drivers/usb/storage/usb-storage.ko.gz ./kernel/drivers/usb/storage/ums-cypress.ko.gz ./kernel/drivers/usb/host/ehci-hcd.ko.gz EOF pushd unpack # Unpack the kirkwood Kernel modules into a temporary # space: tar --wildcards -xvvf $PKGSTORE/a/kernel-modules-${SLKARCH}-${KERNELVER}_${SLKARCH}-*.tgz -C. lib/modules/* || exit 1 cd lib/modules/ # Work out what the name of the Kernel is (this may not match the # Kernel version number in this script, although it should!) KERNELNAME="$( ls -1d * )" cd $KERNELNAME # Create the /lib/modules/2.6.x-kirkwood directory: mkdir -vpm755 $EXTPOS/$KERNELNAME # Copy the same Kernel modules as the Versatile does -- including those # additional ones in the list above -- into the Kirkwood installer: tar pvvcf - -T $LIST | tar -C $EXTPOS/$KERNELNAME/ -pxf - popd cd tree # Re-generate module dependencies list: find ./lib/modules -type d -mindepth 1 -maxdepth 1 -printf "%f\n" | xargs -i depmod {} -b. #read -p "Make the mods now then hit ENTER" # Create U-Boot image & put it into the # Slackware ARM tree ready for distribution: find . | cpio -o -H newc | gzip -9fv > ../Slackware_Installer_$SLKARCH.gz mkimage \ -A arm \ -O linux \ -T ramdisk \ -C gzip \ -n 'Slackware ARM Installer' \ -d ../Slackware_Installer_$SLKARCH.gz \ $PKGSTORE/../isolinux/uinitrd-$SLKARCH.img # /tmp/uinitrd-${SLKARCH}.img From w.lohman at chello.nl Mon Jun 15 08:08:49 2009 From: w.lohman at chello.nl (Wybrand Lohman) Date: Mon, 15 Jun 2009 10:08:49 +0200 Subject: [armedslack] ARMedslack says: "Hello World", on the Openmoko Freerunner Message-ID: <200906151008.49649.w.lohman@chello.nl> Hi y'all! Today I inform you that ARMedslack has said 'Hello World" on the Openmoko Freerunner. Now this is nothing to get excited about. "Hello World" is all she wrote. For now, booting the device gives ~10,000 errors. It complains about just about everything and its dog. There is no way to interface with the device yet. No access to a shell, no method of input either locally or remotely. All these things need to be worked on. But! This, to me, is encouraging to continue working on the device, as this proved it is possible to install a custom payload and not have the device die. The method I used is crude. What I did was I took the initrd from the ARMedslack installer, because that's an environment I am familiar with on x86 and I've used it before to build a very limited (but effective) network based OS. The initrd of Slackwares installer has useful networking and maintenance tools while being relatively small, so it's ideal for this sort of work. I added some minor adjustments in this initrd, and converted it to a jffs2 filesystem. I flashed that onto the device, and lo! It booted :D I don't even have a todo list yet. I'm thinking that the mentioned initrd with some changes somehow pulls the rest of the ARMedslack installer files over NFS so to allow a local install on the device. But this will be Real Slow, so I'm considering other options... Thoughts on this are welcome ;-) Cheers, Wybrand This is how I did it: ####################### # INSIDE QEMU ARMedslack INSTALL # ####################### # Assuming this is a Full Install, import two packages: # 1) 'MTD-utils' (Memory Technology Devices) # This is needed to make jffs2 filesystems # 2) 'initrd-versatile' from the ARMedslack installer # This image is a good place to start the first # tests on. ####################### # WARNING # Do not run this as script echo "No warranties and all that" exit ####################### # MTD-UTILS # This gets the tools needed to builds jffs2 filesystems: wget ftp://ftp.infradead.org/pub/mtd-utils/mtd-utils-1.2.0.tar.bz2 # Install per usual: tar -xjf mtd-utils-1.2.0.tar.bz2 cd mtd-utils-1.2.0 make && make clean make install ####################### # INITRD-VERSATILE # This gets the ramdisk image: wget \ ftp.slackware.org.uk/armedslack/armedslack-current/isolinux/initrd-versatile.img # Create working directory: mkdir /tmp/moko ; cp initrd-versatile.img /tmp/moko cd /tmp/moko # Extract image: gzip -dc initrd-versatile.img | cpio -id # Look around for a bit: ls # This is what the device will look like # This is an excellent time to make some adjustments to the image. # I recommend at least adding a 'Hello World' in /tmp/moko/etc/rc.d/rc.S # At line 160 is a good idea, because as of yet the device doesn't # accept input and boot hangs on 'Select keyboard'. ####################### # MKFS.JFFS2 # This creates a jffs2 filesystem from the current directory. # Relying heavily on defaults, which is probaby not a good idea. More # reading is required... when time allows. For now it works. mkfs.jffs2 -o /path/to/outputfile.jffs2 ####################### # FLASHING THE DEVICE # Flash the device as normal: dfu-util -a rootfs -R -D /path/to/outputfile.jffs2 From mozes at slackware.com Sat Jun 20 17:15:53 2009 From: mozes at slackware.com (Stuart Winter) Date: Sat, 20 Jun 2009 10:15:53 -0700 (PDT) Subject: [armedslack] ARMedslack 12.2-rc6 Message-ID: Hi I've uploaded rc6 of ARMedslack 12.2 - it includes a few security fixes and a few doc updates. When Linux 2.6.30.1 is released and I've done some tests, ARMedslack will be released! If anybody has anything that'd stand in the way of a release, please speak up! :) -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From bluecolour.sz at gmail.com Wed Jun 24 05:20:56 2009 From: bluecolour.sz at gmail.com (cheesiong) Date: Wed, 24 Jun 2009 13:20:56 +0800 Subject: [armedslack] saying hi. Message-ID: <8ab1d9170906232220l38ffbcdhf35a2639489634ed@mail.gmail.com> hi all, i am trying to make armslack running on storlink SL351X platform. i have try a few applications and is working. the blob boot doesnt load the armedslack kernel. please anybody share on this topics if there is any. more steps to go but slow. i have question if the armedslack have the svn package? regards, cheesiong. -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Wed Jun 24 15:33:06 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 24 Jun 2009 16:33:06 +0100 (BST) Subject: [armedslack] saying hi. In-Reply-To: <8ab1d9170906232220l38ffbcdhf35a2639489634ed@mail.gmail.com> References: <8ab1d9170906232220l38ffbcdhf35a2639489634ed@mail.gmail.com> Message-ID: Hi > i am trying to make armslack running on storlink SL351X platform. > i have try a few applications and is working. the blob boot doesnt load the > armedslack kernel. Each device and ARM CPU version (there are many) needs its own Kernel. ARMedslack provides a Kernel for the ARM Versatile PB development board, and the Marvell SheevaPlug, but not the Storlink; you'd need to build a kernel using the "Old ABI" ABI for it. I think I explained this recently on this list, although you may have only just joined and I didn't setup list archives but I can re-send what I wrote, if it'd be useful. > i have question if the armedslack have the svn package? Yes it does. It's a full port of Slackware, only excluding packages that are x86 only, have no source or just don't work. subversion works so it's in there :) -- Stuart Winter www.armedslack.org From bluecolour.sz at gmail.com Fri Jun 26 03:49:44 2009 From: bluecolour.sz at gmail.com (cheesiong) Date: Fri, 26 Jun 2009 11:49:44 +0800 Subject: [armedslack] saying hi. In-Reply-To: References: <8ab1d9170906232220l38ffbcdhf35a2639489634ed@mail.gmail.com> Message-ID: <8ab1d9170906252049w687b8574s74e77c77747bbf63@mail.gmail.com> hi all, i try to install sshd in the storlink platform. i tried openssh-5.1p1-arm-2.tgz but it seem problem for the library. so i tried openssh-4.4p1-arm-1.tgz. it seem working. but i having problem when using another machine to connect to the storlink host. this is ssh client for the storlink platform testing, it is working fine. storlink> ssh 10.104.8.126 -v OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 debug1: Connecting to 10.104.8.126 [10.104.8.126] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7 debug1: match: OpenSSH_4.7 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '10.104.8.126' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: password root at 10.104.8.126's password: debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug1: Entering interactive session. Last login: Fri Jun 26 11:24:06 2009 from xxx.xxx.xxx (i changed it). root [ ~ ]# --------------------------------------------------------------------------------------------------------------------------------- this is using storlink platform to connect itself. problem! storlink> ssh localhost -v OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.4 debug1: match: OpenSSH_4.4 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:3 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: password root at localhost's password: debug1: Authentications that can continue: publickey,password,keyboard-interactive Permission denied, please try again. root at localhost's password: debug1: Authentications that can continue: publickey,password,keyboard-interactive Permission denied, please try again. root at localhost's password: debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: No more authentication methods to try. Permission denied (publickey,password,keyboard-interactive). storlinkf> can anyone help me on this? regards, --cheesiong On Wed, Jun 24, 2009 at 11:33 PM, Stuart Winter wrote: > > Hi > > > i am trying to make armslack running on storlink SL351X platform. > > i have try a few applications and is working. the blob boot doesnt load > the > > armedslack kernel. > > Each device and ARM CPU version (there are many) needs its own Kernel. > > ARMedslack provides a Kernel for the ARM Versatile PB > development board, and the Marvell SheevaPlug, but not the Storlink; > you'd need to build a kernel using the "Old ABI" ABI for it. > I think I explained this recently on this list, although you may have only > just joined and I didn't setup list archives but I can re-send what > I wrote, if it'd be useful. > > > i have question if the armedslack have the svn package? > > Yes it does. It's a full port of Slackware, only excluding packages > that are x86 only, have no source or just don't work. > subversion works so it's in there :) > > -- > Stuart Winter > www.armedslack.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jun 26 07:30:52 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 26 Jun 2009 08:30:52 +0100 (BST) Subject: [armedslack] saying hi. In-Reply-To: <8ab1d9170906252049w687b8574s74e77c77747bbf63@mail.gmail.com> References: <8ab1d9170906232220l38ffbcdhf35a2639489634ed@mail.gmail.com> <8ab1d9170906252049w687b8574s74e77c77747bbf63@mail.gmail.com> Message-ID: > i try to install sshd in the storlink platform. > i tried openssh-5.1p1-arm-2.tgz but it seem problem for the library. > so i tried openssh-4.4p1-arm-1.tgz. it seem working. [..] > can anyone help me on this? You are trying to run ARMedslack binaries on the existing Linux distribution on your Storlink? Occasionally you can have luck doing this, but this is not what ARMedslack nor Debian, Fedora or Gentoo ARM ports are for -- it's an operating system in its own right - to be installed as you would install Slackware or any other distribution; not to be confused with a supplementary 3rd party package repository. From mozes at slackware.com Tue Jun 30 07:13:24 2009 From: mozes at slackware.com (Stuart Winter) Date: Tue, 30 Jun 2009 00:13:24 -0700 (PDT) Subject: [armedslack] Slackware ARM 12.2 is released Message-ID: Hi Slackware ARM 12.2 was released yesterday evening UK time. Slackware ARM is now listed in the Changelogs section of www.slackware.com: http://www.slackware.com/changelog/ Thanks to everyone who has helped support this development cycle (which has been quite some time ;-) ). Enjoy Stuart -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org