From mozes at biscuit.org.uk Wed Sep 16 17:33:18 2009 From: mozes at biscuit.org.uk (Stuart Winter) Date: Wed, 16 Sep 2009 18:33:18 +0100 (BST) Subject: [ARMedslack] foo In-Reply-To: References: Message-ID: woo From peterdirichlet.freesoftware at gmail.com Tue Sep 1 19:17:06 2009 From: peterdirichlet.freesoftware at gmail.com (Johann Peter Dirichlet) Date: Tue, 1 Sep 2009 16:17:06 -0300 Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) Message-ID: Hello people! I am Torres, a brazilian computer enthusiastic (sorry my very bad English...), and I am a Linux&&NetBSD user since a long heck of time. I am new in this mail-list, and even if I have no ARM machine I really like much this architecture. In fact I have tried it many years ago (Debian/ARM inside QEMU, but it was not so exciting). I am trying a similar experience, ARMedslack inside QEMU, but I have no spare time for that. But my question here is different: someone have tried running ARMedslack "inside" Beagleboard? I am thinking buy some, and play (and make heavy use, of course) with them. Many thanks! Torres From laurens at daemon.be Wed Sep 2 14:43:05 2009 From: laurens at daemon.be (Laurens Vets) Date: Wed, 02 Sep 2009 16:43:05 +0200 Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) In-Reply-To: References: Message-ID: <4A9E8479.7080503@daemon.be> Hello Torres, > I am Torres, a brazilian computer enthusiastic (sorry my very bad > English...), and I am a Linux&&NetBSD user since a long heck of time. > > I am new in this mail-list, and even if I have no ARM machine I really > like much this architecture. In fact I have tried it many years ago > (Debian/ARM inside QEMU, but it was not so exciting). I am trying a > similar experience, ARMedslack inside QEMU, but I have no spare time > for that. > > But my question here is different: someone have tried running > ARMedslack "inside" Beagleboard? I am thinking buy some, and play (and > make heavy use, of course) with them. I have a BeagleBoard, but I haven't found time yet to get Armedslack running on it. It's on my TODO list though... :) I don't know whether the current ARM compiled Slackware will work or boot on it... Kind regards, Laurens From m-lists at biscuit.org.uk Wed Sep 2 15:50:18 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 2 Sep 2009 16:50:18 +0100 (BST) Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) In-Reply-To: <4A9E8479.7080503@daemon.be> References: <4A9E8479.7080503@daemon.be> Message-ID: > > But my question here is different: someone have tried running > > ARMedslack "inside" Beagleboard? I am thinking buy some, and play (and > > make heavy use, of course) with them. > > I have a BeagleBoard, but I haven't found time yet to get Armedslack running > on it. It's on my TODO list though... :) > > I don't know whether the current ARM compiled Slackware will work or boot on > it... I knew there was someone with a beagleboard. I've done a brief web search -- Debian runs on the beagleboard so I would imagine that the ARMedslack packages would be ok too; you would need your own Kernel though - Linux 2.6.22 minimum (because glibc expects 2.6.22 or greater). What do you want to do with the beagle board? I have had a quick look at beagleboard.org but I can't figure out exactly what the board's market is. Even though ARM is predominantly for embedded devices, Slackware ARM is aimed at "full" systems like desktop machines, or devices where you have disc storage and enough RAM. I'm currently looking at the OpenRD client: http://www.globalscaletechnologies.com/t-openrdcdetails.aspx This looks like a great device because of the size of RAM and expansion ports; I'm waiting the plugcomputer.org forum to see how people get on with it before buying it though, but since ARMedslack already supports the SheevaPlug, the OpenRD hopefully should be relatively easy to get ARMedslack onto. -- Stuart Winter Slackware ARM: www.armedslack.org From phil at slug.org Wed Sep 2 16:50:06 2009 From: phil at slug.org (Phil Ehrens) Date: Wed, 2 Sep 2009 09:50:06 -0700 Subject: [armedslack] An ntp hint Message-ID: <20090902165006.GA17392@webserver.localnet> You probably don't want to run ntpd on a plug, unless you are using it as a time server, but you DO want the time to be correct, because it's a hazard to run a networked computer with time skew, so you should put this in /etc/cron.daily: ~~~ snip ~~~ #!/bin/sh # # Name: ntpsynch.sh # # Purpose: Keep the clock sane! # # Comment: # # ntpdate is called twice because it # takes two calls to get it "dead-on". # /usr/sbin/ntpdate -b time.caltech.edu 2>&1 >/dev/null sleep 2 /usr/sbin/ntpdate -b time.caltech.edu 2>&1 >/dev/null ~~ snip ~~~ It should of course also be run as early as possible at reboot. Slackware calls rc.ntpd from rc.M, so you should copy this script to /etc/rc.d/rc.ntpd as well if you want to be sure your clock is sane at boot. Phil From niels.horn at gmail.com Wed Sep 2 17:06:35 2009 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 2 Sep 2009 14:06:35 -0300 Subject: [armedslack] An ntp hint In-Reply-To: <20090902165006.GA17392@webserver.localnet> References: <20090902165006.GA17392@webserver.localnet> Message-ID: <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> To run after every boot, put in in /etc/rc.d/rc.local Also, it is better to use one of the servers from the ntp pool. (see http://www.pool.ntp.org/ for a list of servers). This way you won't depend on the availability of a single time server. Niels Horn Rio de Janeiro, RJ Brasil site: www.nielshorn.net e-mail: niels.horn at gmail.com On Wed, Sep 2, 2009 at 1:50 PM, Phil Ehrens wrote: > You probably don't want to run ntpd on a plug, unless you > are using it as a time server, but you DO want the time to > be correct, because it's a hazard to run a networked computer > with time skew, so you should put this in /etc/cron.daily: > > ~~~ snip ~~~ > #!/bin/sh > # > # Name: ntpsynch.sh > # > # Purpose: Keep the clock sane! > # > # Comment: > # > # ? ?ntpdate is called twice because it > # ? ?takes two calls to get it "dead-on". > # > /usr/sbin/ntpdate -b time.caltech.edu 2>&1 >/dev/null > sleep 2 > /usr/sbin/ntpdate -b time.caltech.edu 2>&1 >/dev/null > ~~ snip ~~~ > > It should of course also be run as early as possible at > reboot. Slackware calls rc.ntpd from rc.M, so you should > copy this script to /etc/rc.d/rc.ntpd as well if you > want to be sure your clock is sane at boot. > > Phil > > From phil at slug.org Wed Sep 2 17:40:16 2009 From: phil at slug.org (Phil Ehrens) Date: Wed, 2 Sep 2009 10:40:16 -0700 Subject: [armedslack] An ntp hint In-Reply-To: <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> References: <20090902165006.GA17392@webserver.localnet> <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> Message-ID: <20090902174016.GA18015@webserver.localnet> Niels Horn wrote: > To run after every boot, put in in /etc/rc.d/rc.local rc.local runs AFTER everything else... That's why Slackware runs ntpd from rc.M. The clock needs to be synched before logging and network services start. > Also, it is better to use one of the servers from the ntp pool. > (see http://www.pool.ntp.org/ for a list of servers). > This way you won't depend on the availability of a single time server. Good advice. I agree. I've been using ntp since the days before pools, and I tend to forget that pools exist. By the way, you top-posted in your reply, which is bad, because it makes it impossible for other people to maintain the context after you do it. See: http://www.idallen.com/topposting.html Phil From phil at slug.org Wed Sep 2 18:13:55 2009 From: phil at slug.org (Phil Ehrens) Date: Wed, 2 Sep 2009 11:13:55 -0700 Subject: [armedslack] An ntp hint In-Reply-To: <20090902174016.GA18015@webserver.localnet> References: <20090902165006.GA17392@webserver.localnet> <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> <20090902174016.GA18015@webserver.localnet> Message-ID: <20090902181355.GA18324@webserver.localnet> Phil Ehrens wrote: > Niels Horn wrote: > > To run after every boot, put in in /etc/rc.d/rc.local > > rc.local runs AFTER everything else... That's why Slackware > runs ntpd from rc.M. The clock needs to be synched before > logging and network services start. Oops, obviously, not before syslog... But in any case, it needs to be run at the same stage in the boot process as ntpd, and the Slackware rc.M does it at the right point. From niels.horn at gmail.com Wed Sep 2 18:23:59 2009 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 2 Sep 2009 15:23:59 -0300 Subject: [armedslack] An ntp hint In-Reply-To: <20090902181355.GA18324@webserver.localnet> References: <20090902165006.GA17392@webserver.localnet> <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> <20090902174016.GA18015@webserver.localnet> <20090902181355.GA18324@webserver.localnet> Message-ID: <3f18b2310909021123m15934b7ey8ca3fb73154c50f5@mail.gmail.com> On Wed, Sep 2, 2009 at 3:13 PM, Phil Ehrens wrote: > Phil Ehrens wrote: >> Niels Horn wrote: >> > To run after every boot, put in in /etc/rc.d/rc.local >> >> rc.local runs AFTER everything else... That's why Slackware >> runs ntpd from rc.M. The clock needs to be synched before >> logging and network services start. > > Oops, obviously, not before syslog... But in any case, it needs > to be run at the same stage in the boot process as ntpd, and > the Slackware rc.M does it at the right point. > > I suggested putting it in rc.local as editing rc.M is not for everyone... If you use your machine as a desktop, putting the ntpdate command in rc.local is good enough most of the time, as your local clock should be reasonably accurate. ntpdate then should only correct any imprecisions that crept in between boots. For servers it *is* better to edit rc.M and sync time before critical services (like databases etc) start. And sorry for the top-posting, I'm at work and using webmail at the moment :) Niels From thierry.merle at free.fr Wed Sep 2 19:40:49 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Wed, 2 Sep 2009 21:40:49 +0200 Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) In-Reply-To: References: <4A9E8479.7080503@daemon.be> Message-ID: <20090902214049.189af57d@lugdush.houroukhai.org> On Wed, 2 Sep 2009 16:50:18 +0100 (BST) Stuart Winter wrote: > > > > But my question here is different: someone have tried running > > > ARMedslack "inside" Beagleboard? I am thinking buy some, and play (and > > > make heavy use, of course) with them. > > > > I have a BeagleBoard, but I haven't found time yet to get Armedslack running > > on it. It's on my TODO list though... :) > > > > I don't know whether the current ARM compiled Slackware will work or boot on > > it... > > I knew there was someone with a beagleboard. > > I've done a brief web search -- Debian runs on the beagleboard so > I would imagine that the ARMedslack packages would be ok too; > you would need your own Kernel though - Linux 2.6.22 minimum (because > glibc expects 2.6.22 or greater). > > What do you want to do with the beagle board? I have had a quick > look at beagleboard.org but I can't figure out exactly what the board's > market is. > > Even though ARM is predominantly for embedded devices, Slackware ARM > is aimed at "full" systems like desktop machines, or devices where > you have disc storage and enough RAM. > Well, I am running armedslack on my NSLU2 (266MHz ARM CPU, 32Mb RAM). It does some server stuff (imap/webmail, NFS, samba, digital TV recording, ...). You can do something similar with the beagleboard, at least. The dvi out + audio out makes it a good HD media player I suppose (with mplayer in fb mode). Personally I will change my NSLU2 for the sheevaplug (I hope to receive it soon), due to CPU speed mainly. > I'm currently looking at the OpenRD client: > http://www.globalscaletechnologies.com/t-openrdcdetails.aspx > This looks like a great device because of the size of RAM and > expansion ports; I'm waiting the plugcomputer.org forum to see how people > get on with it before buying it though, but since ARMedslack already > supports the SheevaPlug, the OpenRD hopefully should be relatively easy > to get ARMedslack onto. > The wired SATA, many USB and the VGA output makes this little device a good thin PC. Well a little old netbook is still better... Regards, Thierry From phil at slug.org Wed Sep 2 19:55:30 2009 From: phil at slug.org (Phil Ehrens) Date: Wed, 2 Sep 2009 12:55:30 -0700 Subject: [armedslack] An ntp hint In-Reply-To: <3f18b2310909021123m15934b7ey8ca3fb73154c50f5@mail.gmail.com> References: <20090902165006.GA17392@webserver.localnet> <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> <20090902174016.GA18015@webserver.localnet> <20090902181355.GA18324@webserver.localnet> <3f18b2310909021123m15934b7ey8ca3fb73154c50f5@mail.gmail.com> Message-ID: <20090902195530.GA18858@webserver.localnet> Niels Horn wrote: > On Wed, Sep 2, 2009 at 3:13 PM, Phil Ehrens wrote: > > Phil Ehrens wrote: > >> Niels Horn wrote: > >> > To run after every boot, put in in /etc/rc.d/rc.local > >> > >> rc.local runs AFTER everything else... That's why Slackware > >> runs ntpd from rc.M. The clock needs to be synched before > >> logging and network services start. > > > > Oops, obviously, not before syslog... But in any case, it needs > > to be run at the same stage in the boot process as ntpd, and > > the Slackware rc.M does it at the right point. > > > > > > I suggested putting it in rc.local as editing rc.M is not for > everyone... If you use your machine as a desktop, putting the ntpdate > command in rc.local is good enough most of the time, as your local > clock should be reasonably accurate. ntpdate then should only correct > any imprecisions that crept in between boots. > > For servers it *is* better to edit rc.M and sync time before critical > services (like databases etc) start. > > And sorry for the top-posting, I'm at work and using webmail at the moment :) I NEVER suggested editing rc.M - I suggested editing /etc/rc.d/rc.ntpd. As I pointed out, rc.M runs rc.ntpd at just the right time. I assumed that armedslack would generally be run on small devices that would not have battery powered clocks. Some network applications require good clock agreement between (possibly physically remote) nodes. From niels.horn at gmail.com Wed Sep 2 20:23:39 2009 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 2 Sep 2009 17:23:39 -0300 Subject: [armedslack] An ntp hint In-Reply-To: <20090902195530.GA18858@webserver.localnet> References: <20090902165006.GA17392@webserver.localnet> <3f18b2310909021006l69bf7d6cs6548ad9d648c4fd8@mail.gmail.com> <20090902174016.GA18015@webserver.localnet> <20090902181355.GA18324@webserver.localnet> <3f18b2310909021123m15934b7ey8ca3fb73154c50f5@mail.gmail.com> <20090902195530.GA18858@webserver.localnet> Message-ID: <3f18b2310909021323p37e77d99m5a30d3813377b02a@mail.gmail.com> On Wed, Sep 2, 2009 at 4:55 PM, Phil Ehrens wrote: > Niels Horn wrote: >> On Wed, Sep 2, 2009 at 3:13 PM, Phil Ehrens wrote: >> > Phil Ehrens wrote: >> >> Niels Horn wrote: >> >> > To run after every boot, put in in /etc/rc.d/rc.local >> >> >> >> rc.local runs AFTER everything else... That's why Slackware >> >> runs ntpd from rc.M. The clock needs to be synched before >> >> logging and network services start. >> > >> > Oops, obviously, not before syslog... But in any case, it needs >> > to be run at the same stage in the boot process as ntpd, and >> > the Slackware rc.M does it at the right point. >> > >> > >> >> I suggested putting it in rc.local as editing rc.M is not for >> everyone... If you use your machine as a desktop, putting the ntpdate >> command in rc.local is good enough most of the time, as your local >> clock should be reasonably accurate. ntpdate then should only correct >> any imprecisions that crept in between boots. >> >> For servers it *is* better to edit rc.M and sync time before critical >> services (like databases etc) start. >> >> And sorry for the top-posting, I'm at work and using webmail at the moment :) > > I NEVER suggested editing rc.M - I suggested editing > /etc/rc.d/rc.ntpd. As I pointed out, rc.M runs rc.ntpd > at just the right time. > > I assumed that armedslack would generally be run > on small devices that would not have battery > powered clocks. > > Some network applications require good clock agreement > between (possibly physically remote) nodes. > > Well, Linux is about options, and each user / administrator can choose to configure his / her system as he / she prefers. I just gave another, maybe simpler option. It might not be the best for all situations, but neither editing rc.ntpd may be. Editing the included rc.ntpd file may cause problems when it is updated in the future or the system changes administrators at some point in time. If you need to run ntpdate earlier in the boot process, I suggest including a single line at the right point in rc.M calling an external script like: [ -x /usr/local/sbin/yourscript ] && /usr/local/sbin/yourscript This script being saved in /usr/local/sbin/ can be symlinked in /etc/cron.daily so that you have only a single script being called from two different locations. The name should be obvious to clarify its purpose. But, again, just a suggestion... Niels From peterdirichlet.freesoftware at gmail.com Thu Sep 3 18:24:21 2009 From: peterdirichlet.freesoftware at gmail.com (Johann Peter Dirichlet) Date: Thu, 3 Sep 2009 15:24:21 -0300 Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) In-Reply-To: <20090902214049.189af57d@lugdush.houroukhai.org> References: <4A9E8479.7080503@daemon.be> <20090902214049.189af57d@lugdush.houroukhai.org> Message-ID: 2009/9/2 Thierry MERLE : > On Wed, 2 Sep 2009 16:50:18 +0100 (BST) > Stuart Winter wrote: > >> >> > > But my question here is different: someone have tried running >> > > ARMedslack "inside" Beagleboard? I am thinking buy some, and play (and >> > > make heavy use, of course) with them. >> > >> > I have a BeagleBoard, but I haven't found time yet to get Armedslack running >> > on it. It's on my TODO list though... :) >> > >> > I don't know whether the current ARM compiled Slackware will work or boot on >> > it... >> >> I knew there was someone with a beagleboard. >> >> I've done a brief web search -- Debian runs on the beagleboard so >> I would imagine that the ARMedslack packages would be ok too; >> you would need your own Kernel though - Linux 2.6.22 minimum (because >> glibc expects 2.6.22 or greater). >> >> What do you want to do with the beagle board? ?I have had a quick >> look at beagleboard.org but I can't figure out exactly what the board's >> market is. My idea is to make a netbook or nettop with a Beagleboard. >> >> Even though ARM is predominantly for embedded devices, Slackware ARM >> is aimed at "full" systems like desktop machines, or devices where >> you have disc storage and enough RAM. Desktop ARM... Sounds good! In fakt, Haiku project is doing an ARM version, too. >> > Well, I am running armedslack on my NSLU2 (266MHz ARM CPU, 32Mb RAM). > It does some server stuff (imap/webmail, NFS, samba, digital TV recording, ...). > You can do something similar with the beagleboard, at least. > The dvi out + audio out makes it a good HD media player I suppose (with mplayer in fb mode). > > Personally I will change my NSLU2 for the sheevaplug (I hope to receive it soon), due to CPU speed mainly. > >> I'm currently looking at the OpenRD client: >> http://www.globalscaletechnologies.com/t-openrdcdetails.aspx >> This looks like a great device because of the size of RAM and >> expansion ports; I'm waiting the plugcomputer.org forum to see how people >> get on with it before buying it though, but since ARMedslack already >> supports the SheevaPlug, the OpenRD hopefully should be relatively easy >> to get ARMedslack onto. >> > The wired SATA, many USB and the VGA output makes this little device a good thin PC. > Well a little old netbook is still better... > > Regards, > Thierry > > From mozes at slackware.com Thu Sep 3 22:24:10 2009 From: mozes at slackware.com (Stuart Winter) Date: Thu, 3 Sep 2009 15:24:10 -0700 (PDT) Subject: [armedslack] Help deciding which bits of mtd-utils to include in the installer In-Reply-To: References: Message-ID: Hi I'm updating the installer for the new EABI port, and although Slackware ARM won't yet support installation to flash/NAND, I know there are some people who'd want to do it. I've only got limited experience of working with NAND myself (having blown away the ubuntu stuff on my SheevaPlug and trying to install an initd on it to avoid uboot), so I'm not sure which bits of the mtd-utils package would be required -- any help is appreciated! prisere [a] # tar tvvf mtd-utils-310809-arm-1.tgz| grep usr/sbin | rev | awk '{print $1}'|rev usr/sbin/ usr/sbin/docfdisk usr/sbin/ftl_format usr/sbin/ubicrc32 usr/sbin/mkbootenv usr/sbin/flash_otp_info usr/sbin/flashcp usr/sbin/unubi usr/sbin/flash_erase usr/sbin/pddcustomize usr/sbin/ubinfo usr/sbin/nftldump usr/sbin/ubiattach usr/sbin/mkfs.jffs2 usr/sbin/nandwrite usr/sbin/flash_eraseall usr/sbin/rfddump usr/sbin/ubirename usr/sbin/pfiflash usr/sbin/nftl_format usr/sbin/mkpfi usr/sbin/ubimkvol usr/sbin/ftl_check usr/sbin/ubimirror usr/sbin/sumtool usr/sbin/ubiformat usr/sbin/flash_unlock usr/sbin/flash_lock usr/sbin/flash_otp_dump usr/sbin/mtdinfo usr/sbin/nandtest usr/sbin/mkfs.ubifs usr/sbin/ubidetach usr/sbin/nand2bin usr/sbin/serve_image usr/sbin/rfdformat usr/sbin/ubicrc32.pl usr/sbin/ubiupdatevol usr/sbin/doc_loadbios usr/sbin/jffs2dump usr/sbin/recv_image usr/sbin/pfi2bin usr/sbin/ubirmvol usr/sbin/bin2nand usr/sbin/nanddump usr/sbin/flash_info usr/sbin/ubigen usr/sbin/ubinize usr/sbin/mtd_debug prisere [a] # -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From laurens at daemon.be Fri Sep 4 07:20:24 2009 From: laurens at daemon.be (Laurens Vets) Date: Fri, 04 Sep 2009 07:20:24 +0000 Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) Message-ID: <20090904072024.3369.qmail@bromie.daemon.be> > What do you want to do with the beagle board? I have had a quick > look at beagleboard.org but I can't figure out exactly what the board's > market is. Low cost, low power printserver & WOL basestation :) From thierry.merle at free.fr Fri Sep 4 19:25:28 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Fri, 4 Sep 2009 21:25:28 +0200 Subject: [armedslack] Help deciding which bits of mtd-utils to include in the installer In-Reply-To: References: Message-ID: <20090904212528.7f93abac@lugdush.houroukhai.org> Hi Stuart, On Thu, 3 Sep 2009 15:24:10 -0700 (PDT) Stuart Winter wrote: > > Hi > > I'm updating the installer for the new EABI port, and although Slackware > ARM won't yet support installation to flash/NAND, I know there are some > people who'd want to do it. > What type of devices you plan to address? Concerning the NSLU2, I only access the mtd block devices, detected directly by the kernel by the MTD drivers (attached my config for NSLU2, kernel 2.6.7.4). To flash the kernel and the initrd, I grabbed a script from debian. There is some magic FIS decoding to calculate some offsets but this is particular to the NSLU2. He is a modified debian script, works only for flashing my custom kernel, only for NSLU2 (I did not update it for other devices). I commented out the annoying things (dpkg calls), and hardcoded values, it works... It requires devio, specific to write on mtd block devices. No need of any flash_erase or nanwrite (for char devices). Cheers, Thierry -------------- next part -------------- A non-text attachment was scrubbed... Name: config-2.6.27.4.gz Type: application/x-gzip Size: 16212 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: flash-kernel Type: application/octet-stream Size: 6113 bytes Desc: not available URL: From laurens at daemon.be Fri Sep 4 20:18:11 2009 From: laurens at daemon.be (Laurens Vets) Date: Fri, 04 Sep 2009 22:18:11 +0200 Subject: [armedslack] Armedslack/Beagleboard (someone have tried?) In-Reply-To: References: <4A9E8479.7080503@daemon.be> Message-ID: <4AA17603.809@daemon.be> > I'm currently looking at the OpenRD client: > http://www.globalscaletechnologies.com/t-openrdcdetails.aspx > This looks like a great device because of the size of RAM and > expansion ports; I'm waiting the plugcomputer.org forum to see how people > get on with it before buying it though, but since ARMedslack already > supports the SheevaPlug, the OpenRD hopefully should be relatively easy > to get ARMedslack onto. That looks very nice. I'm actually also waiting on my Touch Book :) From m-lists at biscuit.org.uk Mon Sep 7 11:16:43 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 7 Sep 2009 12:16:43 +0100 (BST) Subject: [armedslack] Help deciding which bits of mtd-utils to include in the installer In-Reply-To: <20090904212528.7f93abac@lugdush.houroukhai.org> References: <20090904212528.7f93abac@lugdush.houroukhai.org> Message-ID: > > ARM won't yet support installation to flash/NAND, I know there are some > > people who'd want to do it. > > > What type of devices you plan to address? How many are there? I thought that the mtd-utils are able to work with the NAND flash devices, so I thought as a minimum I'd include: usr/sbin/nandwrite usr/sbin/flash_eraseall On The Sheevaplug these mtd devices show as: root at stokely:~# mtdinfo Count of MTD devices: 3 Present MTD devices: mtd0, mtd1, mtd2 Sysfs interface supported: yes root at stokely:~# root at stokely:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 1fb00000 00020000 "root" root at stokely:~# And I can mount them as block devices: root at stokely:~# mount /dev/mtdblock2 /mnt/floppy/ -t jffs2 root at stokely:~# ls /mnt/floppy/ bin/ boot/ dev/ etc/ home/ lib/ media/ mnt/ opt/ proc/ root/ sbin/ selinux/ srv/ sys/ tmp/ usr/ var/ root at stokely:~# > Concerning the NSLU2, I only access the mtd block devices, detected > directly by the kernel by the MTD drivers (attached my config for NSLU2, > kernel 2.6.7.4). To flash the kernel and the initrd, I grabbed a script > from debian. There is some magic FIS decoding to calculate some offsets > but this is particular to the NSLU2. He is a modified debian script, > works only for flashing my custom kernel, only for NSLU2 (I did not > update it for other devices). I commented out the annoying things (dpkg > calls), and hardcoded values, it works... Ah that's interesting. I'm only going to support the hardware that ARMedslack provides kernels for, which would be the SheevaPlug at the moment (I won't get into the ARM versatile board). The point of this excercise was to provide useful tools to work with the onboard NAND for people who are installing onto the SheevaPlug, but who wanted to put the Kernel or to install onto the NAND rather than a USB device. I would like to provide the ability to flash the kernel & initrd to NAND on the Sheevaplug so that we can avoid u-boot's flaky USB support; but the challenge would be that the user would have to update offsets in the u-boot boot parameters manually. I think I'll put this idea on the back burner for a while :-) -- Stuart Winter Slackware ARM: www.armedslack.org From steve at pirk.com Mon Sep 7 14:14:33 2009 From: steve at pirk.com (Steve Pirk) Date: Mon, 07 Sep 2009 07:14:33 -0700 Subject: [armedslack] I think I am missing something? Message-ID: <4AA51549.2000002@pirk.com> Gents, Back at it after a trip, and am diving into the Acer Aspire One 11.6" (Intel Atom Z520). I Gave up getting the installer to "see" the ide drive and am now diving into building as an arm system. I think I am following the steps in INSTALL_QEMU.TXT correctly. Host dir set up, armed src dir exported, and I started the qemu installer, but bailed thinking it was going to write to local disk. Read again and saw that it write to the .img file. So, my slack 13 sony laptop is the dev build server, nfs mounting it's own volume to do a network install, and "bulds" a disk image file. If this is correct so far, how do I get the image file over to the Acer laptop? Or, am I supposed to be running the installer on the Acer arm netbook? (brain is still foggy from all the smoke in Glendale last week). -- steve pirk refiamerica.org - bremerton, wa "father... the sleeper has awakened..." paul atreides - dune From thierry.merle at free.fr Tue Sep 8 19:47:01 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Tue, 8 Sep 2009 21:47:01 +0200 Subject: [armedslack] Help deciding which bits of mtd-utils to include in the installer In-Reply-To: References: <20090904212528.7f93abac@lugdush.houroukhai.org> Message-ID: <20090908214701.4932a510@lugdush.houroukhai.org> On Mon, 7 Sep 2009 12:16:43 +0100 (BST) Stuart Winter wrote: > > > > ARM won't yet support installation to flash/NAND, I know there are some > > > people who'd want to do it. > > > > > What type of devices you plan to address? > > How many are there? Well I saw already 2 categories: - the ones which have partitioned flash description written by redboot or configured in kernel (in arch/arm/mach-xx/yy-setup.c). - the ones for which you have to either build a bootstrap image and flash it via jtag, or guess the flash partitions because this is still an unknown device for linux. The sheevaplug is in the first case, I see that you can read the mtd partitions. They have been configured in kernel in the file: arch/arm/mach-kirkwood/sheevaplug-setup.c A good guy did a good job :) > I thought that the mtd-utils are able to work with the NAND flash devices, > so I thought as a minimum I'd include: > usr/sbin/nandwrite > usr/sbin/flash_eraseall > Yes, mtd-utils are made for that, and you are right, you should include them. > On The Sheevaplug these mtd devices show as: > root at stokely:~# mtdinfo > Count of MTD devices: 3 > Present MTD devices: mtd0, mtd1, mtd2 > Sysfs interface supported: yes > root at stokely:~# > > root at stokely:~# cat /proc/mtd > dev: size erasesize name > mtd0: 00100000 00020000 "u-boot" > mtd1: 00400000 00020000 "uImage" > mtd2: 1fb00000 00020000 "root" > root at stokely:~# > > And I can mount them as block devices: > root at stokely:~# mount /dev/mtdblock2 /mnt/floppy/ -t jffs2 > root at stokely:~# ls /mnt/floppy/ > bin/ boot/ dev/ etc/ home/ lib/ media/ mnt/ opt/ proc/ root/ > sbin/ selinux/ srv/ sys/ tmp/ usr/ var/ > root at stokely:~# > Wow, more than 500Mb for root fs, I did not realize the flash was so huge. Good reason to put a whole root fs in it. > > Concerning the NSLU2, I only access the mtd block devices, detected > > directly by the kernel by the MTD drivers (attached my config for NSLU2, > > kernel 2.6.7.4). To flash the kernel and the initrd, I grabbed a script > > from debian. There is some magic FIS decoding to calculate some offsets > > but this is particular to the NSLU2. He is a modified debian script, > > works only for flashing my custom kernel, only for NSLU2 (I did not > > update it for other devices). I commented out the annoying things (dpkg > > calls), and hardcoded values, it works... > > Ah that's interesting. > Well, on second thought, I am not sure this script is a good starting point. Using nandwrite and flash_erase may be generic and better for all devices (see http://www.linux-mtd.infradead.org/faq/nand.html#L_nand_copyimg) I should write my own flash script to work with nandwrite. Sorry for the wrong direction. > I'm only going to support the hardware that ARMedslack provides kernels > for, which would be the SheevaPlug at the moment (I won't get into the ARM > versatile board). The point of this excercise was to provide useful tools > to work with the onboard NAND for people who are installing onto the > SheevaPlug, but who wanted to put the Kernel or to install onto the NAND > rather than a USB device. > OK. in fact you want a complete operating system in flash. Creating and formatting a jffs2 partition in /dev/mtdblock2. The user would be able to choose at TARGET step to put the root on a detected USB disk or an mtdblock device... > I would like to provide the ability to flash the kernel & initrd to > NAND on the Sheevaplug so that we can avoid u-boot's flaky USB support; > but the challenge would be that the user would have to update offsets > in the u-boot boot parameters manually. > uboot is able to boot from network. By providing a uboot image put on a NFS server should be possible. Sorry I am missing some practical background on the sheevaplug, I will see on mine. > I think I'll put this idea on the back burner for a while :-) > It is a great idea! I will look at it... as soon as I receive my sheevaplug :_( Thierry From m-lists at biscuit.org.uk Wed Sep 9 09:09:12 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 9 Sep 2009 10:09:12 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: <4AA51549.2000002@pirk.com> References: <4AA51549.2000002@pirk.com> Message-ID: Hi Steve > So, my slack 13 sony laptop is the dev build server, nfs mounting it's own > volume to do a network install, and "bulds" a disk image file. > If this is correct so far, how do I get the image file over to the Acer > laptop? Or, am I supposed to be running the installer on the Acer arm netbook? The installer is meant to be run on which ever machine you want to run QEMU on. A single Slackware/x86 (32 or 64bit) machine can be the NFS server used for the one time installation, *and* also host Slackware ARM inside QEMU. The tip is: put QEMU on the fastest CPU you have -- it's slow! QEMU 0.9 used to be significantly faster for ARM emulation than 0.10 -- I don't know what happened. It got more stable but slow! Does that help? I've adjusted the instructions in the first paragraph of the qemu installation document to make it clear that you only need one machine. Cheers s. -- Stuart Winter Slackware ARM: www.armedslack.org From steve at pirk.com Thu Sep 10 00:04:53 2009 From: steve at pirk.com (Stephen Pirk) Date: Wed, 9 Sep 2009 17:04:53 -0700 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> Message-ID: <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> On Wed, Sep 9, 2009 at 02:09, Stuart Winter wrote: > > Hi Steve > > The installer is meant to be run on which ever machine you want to run > QEMU on. > > A single Slackware/x86 (32 or 64bit) machine can be the NFS server used > for the one time installation, *and* also host Slackware ARM inside > QEMU. > > The tip is: put QEMU on the fastest CPU you have -- it's slow! > QEMU 0.9 used to be significantly faster for ARM emulation than > 0.10 -- I don't know what happened. It got more stable but slow! > > Does that help? I've adjusted the instructions in the first paragraph > of the qemu installation document to make it clear that you only need > one machine. > > Cheers > s. > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > Aha! (picture lucy flipping over backwards as charlie brown screams). QEMU is a compiler/emulator (like the 8051 dissasembler/assembler program I ran on an original '80's pc). qemu, builds the arm kernel and compiles all the programs for arm. At least that is what I see from your response. Ok then, I let it do it's thing, growing the disk image as needed as it builds the install image, then I probably create an ISO dvd from that disk - never mind... I think I saw instructions to transfer via usb later on in the how-to. Stuart, ya'll rock. Hey, what up with the hybrid bsd/penguin graphic on my regular slack 13 i686/smb install? This doesn't have anything to do with preliminary chrome code I have not heard of yet, does it? Has Slack always been the best of both? (which is what we were rooting for when I worked for EDS/Unigraphics in the '85-'95 time range. -- steve pirk refiamerica.org "father... the sleeper has awakened..." paul atreides - dune -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Sep 10 15:11:59 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 10 Sep 2009 16:11:59 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> Message-ID: Hi Steve > QEMU is a compiler/emulator (like the 8051 dissasembler/assembler program I > ran on an original '80's pc). qemu, builds the arm kernel and compiles all > the programs for arm. At least that is what I see from your response. QEMU is a full system emulator - emulating real hardware on an x86 host. It allows you to run -- in this case -- Slackware ARM , and make Slackware ARM think it's running on a real ARM development board. It's not a compiler. You'd be best off checking the QEMU web page for more information. > Ok then, I let it do it's thing, growing the disk image as needed as it > builds the install image, then I probably create an ISO dvd from that disk - > never mind... I think I saw instructions to transfer via usb later on in the > how-to. I'm a little puzzled by this: Slackware ARM is a port of Slackware -- QEMU is an emulator. You install Slackware ARM to an emulated SCSI hard disk (which is really a single image file on your host PC); and it behaves like Slackware x86 once installed -- and Slackware ARM believes it's running on real ARM hardware. The installation of Slackware ARM will be the same as Slackware x86 -- a full operating system, running off a disc. You could make a DVD ISO of it but I don't know why you'd want to, apart from say a backup. > Stuart, ya'll rock. Hey, what up with the hybrid bsd/penguin graphic on my > regular slack 13 i686/smb install? Linus introduced a Temporary logo change in the .29 series. It's back to standard Tux in .30. -- Stuart Winter Slackware ARM: www.armedslack.org From steve at pirk.com Thu Sep 10 17:48:10 2009 From: steve at pirk.com (Stephen Pirk) Date: Thu, 10 Sep 2009 10:48:10 -0700 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> Message-ID: <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> That is what I thought. Pretty cool running aserver in a window, but I could not get the mouse out, so the laptop was "locked" for the night long build. Yeah, I am seeing all this now. Slack _should_ just install, but it cannot find the IDE drive. Verra strange. I used dd to copy the qume image to a sd card, and poped it in. Same result: "operating system not found". I even installed from the slack 13 dvd iso and the install went fine, but no boot. Somewhere there is a switch, I just have to find it. Others posted lots of boot flags ide=xxx and other noporobe fails. Nothing. lspci never sees a hdd device. Let me load fedora again and see what it does with the disk. Like you mentioned earlier, it will probably be a /dev/sda scsi device. Ok, put the slack on the acer on hols, and time to load armedslack on my sheeva. Whoot! Thanks Stuart. On Thu, Sep 10, 2009 at 08:11, Stuart Winter wrote: > > Hi Steve > > > QEMU is a compiler/emulator (like the 8051 dissasembler/assembler program > I > > ran on an original '80's pc). qemu, builds the arm kernel and compiles > all > > the programs for arm. At least that is what I see from your response. > > QEMU is a full system emulator - emulating real hardware on an x86 host. > It allows you to run -- in this case -- Slackware ARM , and make Slackware > ARM think it's running on a real ARM development board. > > It's not a compiler. You'd be best off checking the QEMU web page > for more information. > > > Ok then, I let it do it's thing, growing the disk image as needed as it > > builds the install image, then I probably create an ISO dvd from that > disk - > > never mind... I think I saw instructions to transfer via usb later on in > the > > how-to. > > I'm a little puzzled by this: Slackware ARM is a port of Slackware -- QEMU > is an emulator. You install Slackware ARM to an emulated SCSI hard disk > (which is really a single image file on your host PC); and it behaves > like Slackware x86 once installed -- and Slackware ARM believes it's > running on real ARM hardware. > > The installation of Slackware ARM will be the same as Slackware x86 -- a > full operating system, running off a disc. You could make a DVD ISO of > it but I don't know why you'd want to, apart from say a backup. > > > Stuart, ya'll rock. Hey, what up with the hybrid bsd/penguin graphic on > my > > regular slack 13 i686/smb install? > > Linus introduced a Temporary logo change in the .29 series. It's back to > standard Tux in .30. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > -- steve pirk refiamerica.org "father... the sleeper has awakened..." paul atreides - dune Sent from Bremerton, WA, United States -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.guibert at gmail.com Fri Sep 11 08:33:46 2009 From: frank.guibert at gmail.com (Frank Guibert) Date: Fri, 11 Sep 2009 10:33:46 +0200 Subject: [armedslack] I think I am missing something? In-Reply-To: <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: 2009/9/10 Stephen Pirk : > That is what I thought. Pretty cool running aserver in a window, but I could > not get the mouse out, so the laptop was "locked" for the night long build. > > Yeah, I am seeing all this now. Slack _should_ just install, but it cannot > find the IDE drive. Verra strange. I used dd to copy the qume image to a sd > card, and poped it in. Same result: "operating system not found". I even > installed from the slack 13 dvd iso and the install went fine, but no boot. > > Somewhere there is a switch, I just have to find it. Others posted lots of > boot flags ide=xxx and other noporobe fails. Nothing. lspci never sees a hdd > device. > > Let me load fedora again and see what it does with the disk. Like you > mentioned earlier, it will probably be a /dev/sda scsi device. > > Ok, put the slack on the acer on hols, and time to load armedslack on my > sheeva. Whoot! > > Thanks Stuart. > > On Thu, Sep 10, 2009 at 08:11, Stuart Winter wrote: >> >> Hi Steve >> >> > QEMU is a compiler/emulator (like the 8051 dissasembler/assembler >> > program I >> > ran on an original '80's pc). qemu, builds the arm kernel and compiles >> > all >> > the programs for arm. At least that is what I see from your response. >> >> QEMU is a full system emulator - emulating real hardware on an x86 host. >> It allows you to run -- in this case -- Slackware ARM , and make Slackware >> ARM think it's running on a real ARM development board. >> >> It's not a compiler. ?You'd be best off checking the QEMU web page >> for more information. >> >> > Ok then, I let it do it's thing, growing the disk image as needed as it >> > builds the install image, then I probably create an ISO dvd from that >> > disk - >> > never mind... I think I saw instructions to transfer via usb later on in >> > the >> > how-to. >> >> I'm a little puzzled by this: Slackware ARM is a port of Slackware -- QEMU >> is an emulator. ?You install Slackware ARM to an emulated SCSI hard disk >> (which is really a single image file on your host PC); and it behaves >> like Slackware x86 once installed -- and Slackware ARM believes it's >> running on real ARM hardware. >> >> The installation of Slackware ARM will be the same as Slackware x86 -- a >> full operating system, running off a disc. ?You could make a DVD ISO of >> it but I don't know why you'd want to, apart from say a backup. >> >> > Stuart, ya'll rock. Hey, what up with the hybrid bsd/penguin graphic on >> > my >> > regular slack 13 i686/smb install? >> >> Linus introduced a Temporary logo change in the .29 series. ?It's back to >> standard Tux in .30. >> >> -- >> Stuart Winter >> Slackware ARM: www.armedslack.org >> > > > > -- > steve pirk > refiamerica.org > "father... the sleeper has awakened..." paul atreides - dune > Sent from Bremerton, WA, United States Hi Stephen, I installed Slackware 13 on a fit-pc 2 (Intel Atom Z530) and I had the same problem, it couldn't see the ide hard drive. Like you I tried without success to pass "ide generic" options to the kernel... I sorted out the problem by recompiling the kernels (both the kernel used by the Slack installer 2.6.29.6 and afterwards my "daily" kernel using 2.6.30.5) and adding pata_sch support (CONFIG_PATA_SCH=y in the .config file). Basically the pata_sch support has to be either built into your kernel (or into the initrd...I don't use initrd would that work ?? would that be a simpler way of adding pata_sch support on boot ??) otherwise the kernel won't be able to access your root partition when you boot. Hope this helps. Frank From m-lists at biscuit.org.uk Fri Sep 11 12:49:28 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 11 Sep 2009 13:49:28 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: > > Let me load fedora again and see what it does with the disk. Like you > > mentioned earlier, it will probably be a /dev/sda scsi device. I meant that in Slackware ARM, in QEMU, its discs show as SCSI devices. there's no IDE support in QEMU. > I sorted out the problem by recompiling the kernels (both the kernel > used by the Slack installer 2.6.29.6 and afterwards my "daily" kernel > using 2.6.30.5) and adding pata_sch support (CONFIG_PATA_SCH=y in the > .config file). > > Basically the pata_sch support has to be either built into your > kernel (or into the initrd...I don't use initrd would that work ?? > would that be a simpler way of adding pata_sch support on boot ??) > otherwise the kernel won't be able to access your root partition when > you boot. Thanks for letting us know, Frank -- I see that in the "huge" kernel this is compiled as a module when it should be compiled into the kernel. I've bounced your message to Patrick. -- Stuart Winter Slackware ARM: www.armedslack.org From frank.guibert at gmail.com Fri Sep 11 13:49:20 2009 From: frank.guibert at gmail.com (Frank Guibert) Date: Fri, 11 Sep 2009 15:49:20 +0200 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: 2009/9/11 Stuart Winter : > >> > Let me load fedora again and see what it does with the disk. Like you >> > mentioned earlier, it will probably be a /dev/sda scsi device. > > I meant that in Slackware ARM, in QEMU, its discs show as SCSI > devices. ?there's no IDE support in QEMU. > >> I sorted out the problem by recompiling the kernels (both the kernel >> used by the Slack installer 2.6.29.6 and afterwards my "daily" kernel >> using 2.6.30.5) and adding pata_sch support (CONFIG_PATA_SCH=y in the >> .config file). >> >> Basically ?the pata_sch support has to be either built into your >> kernel (or into the initrd...I don't use initrd would that work ?? >> would that be a simpler way of adding pata_sch support on boot ??) >> otherwise the kernel won't be able to access your root partition when >> you boot. > > Thanks for letting us know, Frank -- I see that in the "huge" kernel > this is compiled as a module when it should be compiled into the > kernel. > > I've bounced your message to Patrick. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > Hi Steve, There is something that puzzles me in your posts, first you wrote : > ....am diving into the Acer Aspire One 11.6" (Intel Atom Z520) and then you wrote : > Or, am I supposed to be running the installer on the Acer arm netbook? A netbook with an Intel Atom processor (x86 architecture) doesn't have an ARM type processor. So if you just want to install slackware on your Acer netbook you do not need armedslack at all....but the x86 version of slackware with a tweaked kernel supporting the intel ide controller. Just wanted to be sure we are all talking about the same things ! :-) Good luck with your install ! Frank From m-lists at biscuit.org.uk Fri Sep 11 16:29:09 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 11 Sep 2009 17:29:09 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: > A netbook with an Intel Atom processor (x86 architecture) doesn't have > an ARM type processor. > > So if you just want to install slackware on your Acer netbook you do > not need armedslack at all....but the x86 version of slackware with a > tweaked kernel supporting the intel ide controller. heh. I saw this and wondered the same thing, but assumed (I hope) that Steve was calling it the "arm netbook" because he wanted to put ARMedslack under QEMU on it! Anyway, my OpenRD client has arrived just now so I'm really looking forward to having an ARM box with keyboard, VGA and sound. Now I just have to find where the openrd kernel patches are and drop update the kirkwood kernel. -- Stuart Winter Slackware ARM: www.armedslack.org From steve at pirk.com Fri Sep 11 16:33:57 2009 From: steve at pirk.com (Stephen Pirk) Date: Fri, 11 Sep 2009 09:33:57 -0700 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: <940b2d520909110933u68a44a5bq70d408dcc3782a34@mail.gmail.com> On Fri, Sep 11, 2009 at 01:33, Frank Guibert wrote: > 2009/9/10 Stephen Pirk : > > That is what I thought. Pretty cool running aserver in a window, but I > could > > not get the mouse out, so the laptop was "locked" for the night long > build. > > > > Yeah, I am seeing all this now. Slack _should_ just install, but it > cannot > > find the IDE drive. Verra strange. I used dd to copy the qume image to a > sd > > card, and poped it in. Same result: "operating system not found". I even > > installed from the slack 13 dvd iso and the install went fine, but no > boot. > > > > > Hi Stephen, > > I installed Slackware 13 on a fit-pc 2 (Intel Atom Z530) and I had the > same problem, it couldn't see the ide hard drive. > > Like you I tried without success to pass "ide generic" options to the > kernel... > > I sorted out the problem by recompiling the kernels (both the kernel > used by the Slack installer 2.6.29.6 and afterwards my "daily" kernel > using 2.6.30.5) and adding pata_sch support (CONFIG_PATA_SCH=y in the > .config file). > > Basically the pata_sch support has to be either built into your > kernel (or into the initrd...I don't use initrd would that work ?? > would that be a simpler way of adding pata_sch support on boot ??) > otherwise the kernel won't be able to access your root partition when > you boot. > > Hope this helps. > > Frank > > Wow, that is very good news to hear. Let me sort out the best way to do this. Maybe I can build a kernel here on my sony laptop with that switch, and then put that kernel on the install dvd. Can you add a file to an iso image, or would I need to add it to the iso tree and then burn a new install disk from there. I will give it a try. I was beginning to think the laptop was bad. Was just getting ready to try and load win xp pro to see if it would boot at all, even fedora 11 fails now. It finds the disk to install on, but I get a "no operating system" error all the time. Thanks Frank! -steve -- steve pirk refiamerica.org "father... the sleeper has awakened..." paul atreides - dune -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at pirk.com Fri Sep 11 16:42:09 2009 From: steve at pirk.com (Stephen Pirk) Date: Fri, 11 Sep 2009 09:42:09 -0700 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: <940b2d520909110942q5878443co1f2baffca5bd0c3@mail.gmail.com> On Fri, Sep 11, 2009 at 09:29, Stuart Winter wrote: > > A netbook with an Intel Atom processor (x86 architecture) doesn't have > > an ARM type processor. > > > > So if you just want to install slackware on your Acer netbook you do > > not need armedslack at all....but the x86 version of slackware with a > > tweaked kernel supporting the intel ide controller. > > heh. I saw this and wondered the same thing, but assumed (I hope) that > Steve was calling it the "arm netbook" because he wanted to put ARMedslack > under QEMU on it! > > Anyway, my OpenRD client has arrived just now so I'm really looking > forward to having an ARM box with keyboard, VGA and sound. Now I just > have to find where the openrd kernel patches are and drop update the > kirkwood kernel. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > I think that "diversion" was caused by an early reply from Stuart, he mentioned Slack 13 was out and it should work, but also mentioned arm might work, so I played with that too. Hey, I learned a _lot_ and am now ready to play with custom builds. The slack way makes soooo much more sense that trying all those ubuntu hacks. Any of the team in communication with the Marvell people? Would it be worth reaching out to them and seeing if an armedslack version could be factory loaded for the noobs that are not quite ready to build from source [it is fun tho ;-] Once I get it going, I am going to build it solid state. a 16GB SD card should be just good enough for tan thin client where all home data is stored nfs or in the cloud. How 'bout a sheeva plug connected to a smart phone for internet access? Use the phone for the mini-display, keyboard and wireless? ;-] Talk about thin clients. -steve -- steve pirk refiamerica.org "father... the sleeper has awakened..." paul atreides - dune Sent from Bremerton, WA, United States -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank.guibert at gmail.com Fri Sep 11 16:47:11 2009 From: frank.guibert at gmail.com (Frank Guibert) Date: Fri, 11 Sep 2009 17:47:11 +0100 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: > heh. ?I saw this and wondered the same thing, but assumed (I hope) that > Steve was calling it the "arm netbook" because he wanted to put ARMedslack > under QEMU on it! > > Anyway, my OpenRD client has arrived just now so I'm really looking > forward to having an ARM box with keyboard, VGA and sound. ?Now I just > have to find where the openrd kernel patches are and drop update the > kirkwood kernel. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > Well....my SheevaPlug is in my former company in England and I am now working in Paris so I don't have a chance to play with it until I go back over there to get drunk with my ex-colleagues...and fetch the baby ! The fit-pc 2 is a nice low power thingy as well....except for the poulsbo graphic chipset which is a nightmare.....so I use it as a headless server ! Anyway thanks Stuart keep up the good work I can't wait to try armedslack on my Plug ! Frank From m-lists at biscuit.org.uk Fri Sep 11 18:01:58 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 11 Sep 2009 19:01:58 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: <940b2d520909110942q5878443co1f2baffca5bd0c3@mail.gmail.com> References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> <940b2d520909110942q5878443co1f2baffca5bd0c3@mail.gmail.com> Message-ID: > Any of the team in communication with the Marvell people? Would it be worth > reaching out to them and seeing if an armedslack version could be factory > loaded for the noobs that are not quite ready to build from source [it is > fun tho ;-] No I'm not in contact with them -- although I wouldn't have minded having a free SheevaPlug ;-) The SP comes with Ubuntu on the NAND flash so it's ready to be used. I haven't installed ARMedslack onto the NAND yet -- although I did experiment with putting the initrd onto it to avoid u-boot's hit or miss USB detection; but it didn't work out.. yet. > Once I get it going, I am going to build it solid state. a 16GB SD card > should be just good enough for tan thin client where all home data is stored > nfs or in the cloud. Be careful here: check the plugcomputer.org forums to find out which SD cards the SP can use -- as I said, u-boot is hit and miss -- I have 3 USB2 standard caddies here which U-boot can't detect, or won't boot from. Also I have only got AS installing onto the SP onto a USB stick or hard disk, as the instructions describe. I know some of the Debian people have been trying to figure out a working SD card and installation routine, so it's worth checking there. I'm not personally going to do that since I'm quite happy with the USB hard disk route as my machines are purely work horses for armedslack. > How 'bout a sheeva plug connected to a smart phone for internet access? Use > the phone for the mini-display, keyboard and wireless? ;-] Talk about thin > clients. You could use the built in ethernet for Internet access -- it's a bit easier but perhaps less fun ;-) -- Stuart Winter Slackware ARM: www.armedslack.org From steve at pirk.com Fri Sep 11 18:59:21 2009 From: steve at pirk.com (Stephen Pirk) Date: Fri, 11 Sep 2009 11:59:21 -0700 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> Message-ID: <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> On Fri, Sep 11, 2009 at 09:47, Frank Guibert wrote: > > heh. I saw this and wondered the same thing, but assumed (I hope) that > > Steve was calling it the "arm netbook" because he wanted to put > ARMedslack > > under QEMU on it! > > > > Anyway, my OpenRD client has arrived just now so I'm really looking > > forward to having an ARM box with keyboard, VGA and sound. Now I just > > have to find where the openrd kernel patches are and drop update the > > kirkwood kernel. > > Well....my SheevaPlug is in my former company in England and I am now > working in Paris so I don't have a chance to play with it until I go > back over there to get drunk with my ex-colleagues...and fetch the > baby ! > > The fit-pc 2 is a nice low power thingy as well....except for the > poulsbo graphic chipset which is a nightmare.....so I use it as a > headless server ! > > Anyway thanks Stuart keep up the good work I can't wait to try > armedslack on my Plug ! > > Frank > > As soon as I get my sheeva loaded with armedslack (this weekend) and I get it on the 'net, let me know and I should be able to create and account for you to ssh into to play. Just don't break anything... ;-] Yes, the Acer Aspire one 11.6 has the new 11.6 LED backlit display. If I can get it to boot off the SD card, I will have a netbook that should run 8 hours or so off the battery [going with the led lcd, that added 2 hours to the battery run time - just changing the display]. Ok, this is off-topic for the armedslack list. Maybe I start a netslack list that centers around netbook thin client implementations... Can't wait 'till I have the pocket change to order my open-rd dev boxen... whoot! -steve [egrep] -- steve pirk refiamerica.org "father... the sleeper has awakened..." paul atreides - dune Sent from Bremerton, WA, United States -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Sep 14 16:49:42 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 14 Sep 2009 17:49:42 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> Message-ID: > As soon as I get my sheeva loaded with armedslack (this weekend) and I get > it on the 'net, let me know and I should be able to create and account for > you to ssh into to play. Just don't break anything... ;-] Heh. Thanks for the offer -- although usually I try to keep my hands out of other people's systems ;-) > Ok, this is off-topic for the armedslack list. Maybe I start a netslack list > that centers around netbook thin client implementations... The power issues aside, wouldn't you need a small footprint Slackware OS? it's been a while since I tried to slim down a Slackware installation -- around version 8.1 -10 it used to be pretty easy since there were less packages, but there are many new packages since then and many of them depend on each other; so I'm not sure how easy it is to create a working slimmed down Slackware at the moment. > Can't wait 'till I have the pocket change to order my open-rd dev boxen... > whoot! Mine arrived today. I've been checking to see Marvell are with getting the OpenRD support into the main line kernel; and I discovered what appears to be a fork: http://code.google.com/p/openrd/ http://groups.google.com/group/openrd http://groups.google.com/group/openrd/browse_thread/thread/b4981ecb40628a00 The SheevaPlug support, AFAIK, came directly from Marvell and was always available from Marvell's git tree during development. I'll have to do a bit more digging around to find out why it's been forked. I hope that the development work does end up in the main line kernel otherwise these devices end up being a waste of money since the kernel patches become unmaintained. -- Stuart Winter Slackware ARM: www.armedslack.org From thierry.merle at free.fr Mon Sep 14 18:40:49 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Mon, 14 Sep 2009 20:40:49 +0200 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> Message-ID: <20090914204049.5486990a@lugdush.houroukhai.org> On Mon, 14 Sep 2009 17:49:42 +0100 (BST) Stuart Winter wrote: [...] > The SheevaPlug support, AFAIK, came directly from Marvell and was > always available from Marvell's git tree during development. > I'll have to do a bit more digging around to find out why it's been > forked. I hope that the development work does end up in the main line > kernel otherwise these devices end up being a waste of money since the > kernel patches become unmaintained. > The kernel patches come in mainline, but in linux-next before mainline: http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=7eeae54c68e91c46ec170e764d1cceac81f35969 I think the fork is more to have a working kernel than to have a real fork of linux. Thierry P.S.: I received by SP, I will play with flashing a kernel and initrd. From m-lists at biscuit.org.uk Mon Sep 14 18:54:41 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 14 Sep 2009 19:54:41 +0100 (BST) Subject: [armedslack] I think I am missing something? In-Reply-To: <20090914204049.5486990a@lugdush.houroukhai.org> References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> <20090914204049.5486990a@lugdush.houroukhai.org> Message-ID: > The kernel patches come in mainline, but in linux-next before mainline: > http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=7eeae54c68e91c46ec170e764d1cceac81f35969 > I think the fork is more to have a working kernel than to have a real fork of linux. ah I didn't know it'd got into linux-next. I know the fork isn't a fork of Linux, but I thought it was a fork of Marvell's own git tree. I'm still not sure what's going on with it (I might pose the question on the openrd google group) though, but the google group is linked from www.open-rd.org, so perhaps the support is just being handled by someone else. > P.S.: I received by SP, I will play with flashing a kernel and initrd. Flashing to the NAND? This script shows how to flash the kernel to the NAND -- it's two commands - 1 to erase and the next to flash. http://sheeva.with-linux.com/sheeva/README-2.6.30.5 When I last played with this, I thought that even if we can get the initrd into the flash, how do we update the u-boot boot arguments with the offsets without the user nothing down the values & doing it by hand? I was wondering if there's a way of updating the u-boot parameters from inside Linux. -- Stuart Winter Slackware ARM: www.armedslack.org From thierry.merle at free.fr Mon Sep 14 20:18:48 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Mon, 14 Sep 2009 22:18:48 +0200 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909091704v541a063g18fa5e69f4e0681e@mail.gmail.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> <20090914204049.5486990a@lugdush.houroukhai.org> Message-ID: <20090914221848.5dd6c22e@lugdush.houroukhai.org> On Mon, 14 Sep 2009 19:54:41 +0100 (BST) Stuart Winter wrote: > > > The kernel patches come in mainline, but in linux-next before mainline: > > http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=7eeae54c68e91c46ec170e764d1cceac81f35969 > > I think the fork is more to have a working kernel than to have a real fork of linux. > > ah I didn't know it'd got into linux-next. > > I know the fork isn't a fork of Linux, but I thought it was a fork of > Marvell's own git tree. > > I'm still not sure what's going on with it (I might pose the question on > the openrd google group) though, but the google group is linked from > www.open-rd.org, so perhaps the support is just being handled by someone > else. > ah, OK. Hope they will continue to put things in the mainline kernel. > > P.S.: I received by SP, I will play with flashing a kernel and initrd. > > Flashing to the NAND? > Yes, replacing the Ubuntu stuff. > This script shows how to flash the kernel to the NAND -- it's two commands > - 1 to erase and the next to flash. > http://sheeva.with-linux.com/sheeva/README-2.6.30.5 > Thanks, I was recompiling the 2.6.30 kernel on my NSLU2, this will speedup the thing :) > When I last played with this, I thought that even if we can get the initrd > into the flash, how do we update the u-boot boot arguments with the > offsets without the user nothing down the values & doing it by hand? > I was wondering if there's a way of updating the u-boot parameters from > inside Linux. Yes there is a way, but by raw editing the flash (the first 1MB flash bank), something that can brick your SP (I already bricked my SP; reverting to factory default uboot is quite easy). Well, I will do that configuration modification in a second time. My first aim is to reproduce the same behavior than on my NSLU2 that has its kernel and initrd in flash that allows to detect and boot safely on a USB device. I see 2 mtd partitions declared: mtd0: 00400000 00020000 "uImage" mtd1: 1fb00000 00020000 "rootfs" I will put the kernel in "mtd0", and my initrd in "mtd1". On a second time I will resize mtd1 to put the rootfs in flash. For a standard user, providing a binary image he can flash uImage, initrd and rootfs could be an easy solution. Thierry From steve at pirk.com Tue Sep 15 02:14:52 2009 From: steve at pirk.com (steve pirk [egrep]) Date: Mon, 14 Sep 2009 19:14:52 -0700 Subject: [armedslack] I think I am missing something? In-Reply-To: References: <4AA51549.2000002@pirk.com> <940b2d520909101048u64b42e8as75a0dc3c19f6c581@mail.gmail.com> <940b2d520909111159r304223e3i1179f029a48a84fc@mail.gmail.com> Message-ID: <940b2d520909141914p74f98c6bs13e054209bae4cd0@mail.gmail.com> I was going to split the install between the internal 512M disk and a 16GB sd card. Slack should run fine there, and it uses native sheeva code as far as I know. I need to get my diskless laptop going first, then sheeva when I get back. hey, wait, I can take a router and it with me on my trip. It is _small_ enough ;-] -steve On Mon, Sep 14, 2009 at 09:49, Stuart Winter wrote: > > > As soon as I get my sheeva loaded with armedslack (this weekend) and I > get > > it on the 'net, let me know and I should be able to create and account > for > > you to ssh into to play. Just don't break anything... ;-] > > Heh. Thanks for the offer -- although usually I try to keep my hands > out of other people's systems ;-) > > > Ok, this is off-topic for the armedslack list. Maybe I start a netslack > list > > that centers around netbook thin client implementations... > > The power issues aside, wouldn't you need a small footprint Slackware OS? > it's been a while since I tried to slim down a > Slackware installation -- around version 8.1 -10 it used to be pretty > easy since there were less packages, but there are many new packages since > then and many of them depend on each other; so I'm not sure how easy it is > to create a working slimmed down Slackware at the moment. > > > Can't wait 'till I have the pocket change to order my open-rd dev > boxen... > > whoot! > > Mine arrived today. I've been checking to see Marvell are with getting > the OpenRD support into the main line kernel; and I discovered what > appears to be a fork: > http://code.google.com/p/openrd/ > http://groups.google.com/group/openrd > http://groups.google.com/group/openrd/browse_thread/thread/b4981ecb40628a00 > > The SheevaPlug support, AFAIK, came directly from Marvell and was > always available from Marvell's git tree during development. > I'll have to do a bit more digging around to find out why it's been > forked. I hope that the development work does end up in the main line > kernel otherwise these devices end up being a waste of money since the > kernel patches become unmaintained. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > -- steve pirk refiamerica.org "father... the sleeper has awakened..." paul atreides - dune kexp.org member august '09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sam.albuquerque at gmail.com Wed Sep 16 10:27:17 2009 From: sam.albuquerque at gmail.com (Sam Albuquerque) Date: Wed, 16 Sep 2009 11:27:17 +0100 Subject: [armedslack] Installing Armed on the Sheeva NAND Flash Message-ID: Hi fellow slackers, I just booted from the ArmedSlack-12.2, sshed into it and started the setup. It says I need to partition HardDrives. Is there any way to install ArmedSlack on the internal NAND Partitions instead of an external device. Thanks, Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From mozes at biscuit.org.uk Wed Sep 16 17:47:36 2009 From: mozes at biscuit.org.uk (Stuart Winter) Date: Wed, 16 Sep 2009 18:47:36 +0100 (BST) Subject: [ARMedslack] test Message-ID: qsdsd -- The Biscuit Appreciation Society : www.biscuit.org.uk Slackware ARM : www.armedslack.org From mozes at slackware.com Wed Sep 16 17:53:07 2009 From: mozes at slackware.com (Stuart Winter) Date: Wed, 16 Sep 2009 10:53:07 -0700 (PDT) Subject: [ARMedslack] Mailing list move Message-ID: Hi folks I've moved the mailing list from my old creaking majordomo installation to Mailman - greatfully setup by Robby Workman on the slackbuilds.org server. The mailing list address has changed: New post address: armedslack at lists.armedslack.org The old address armedslack at lists.polplex.co.uk will forward there. List archives: Full archives from when the list began. http://lists.armedslack.org/pipermail/armedslack/ Mailman membership details: - No monthly reminders of passwords You can manage your subscription by visiting: http://lists.armedslack.org/mailman/listinfo/armedslack You'll also have received a welcome email containing your default password. Email filtering: An easy filter is to filter on the X header below: X-BeenThere: armedslack at lists.armedslack.org Any problems? let me know! I think the list archiving will be a huge benefit as the project moves forward. Cheers s. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From m-lists at biscuit.org.uk Wed Sep 16 18:49:13 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 16 Sep 2009 19:49:13 +0100 (BST) Subject: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash In-Reply-To: References: Message-ID: Hi Sam > I just booted from the ArmedSlack-12.2, sshed into it and started the setup. > It says I need to partition HardDrives. Is there any way to install > ArmedSlack on the internal NAND Partitions instead of an external device. The quick answer is "you can't". The longer answer is you *may* be able to do it, if you have a lot of patience, enough experience and tenacity :-) Things to note: 1. The installer "partition probe" doesn't look for NAND devices 2. Usually (from what I've read so far) you prepare a JFFS2 filesystem and write it to the NAND using "nandwrite" from the mtd-utils package then update the offsets in your u-boot boot loader config. I can't possibly think of a way to include this in the Slackware installer -- you'd have to install it on another machine using installpkg ROOT=/tmp/newarmmachine do some touchups to the configurations (since some of the package post-installation scripts wouldn't have run since they use chroot and run ARM binaries, which wouldn't work on an x86-- unless you happened to have a spare ARM box around to do the installation). A script to do the installation would be something like this: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/slackkit/sansinstaller You'd need to look at how to create a JFFS2 image of the result and write it to the NAND using "nandwrite". The research I did so far is here - ordered in some sort of useful fashion: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/ What also occurred to be is that you could mount the existing jffs2 filesystem from the Slackware installer, and wipe the contents: mount -t jffs2 /dev/mtdblock2 /mnt/ or something like this. This would have to be one of the ugliest ways of doing it. 3. You'd need to use "nandwrite" to flash the kernel. 4. The Slackware ARM 12.2 installer does not include the nandwrite tools. The -current installer includes nandwrite and flash_eraseall but this isn't available yet, and the installer wouldn't work for a v12.2 installation. All in all, I'd say that the contents of the NAND flash are to be prepared by the vendor; especially since it'd need a stripped down Slackware. In advance you'd have to know which packages to include in order to make a working bootable Slackware installation, with enough space left over to have a useable system. -- Stuart Winter Slackware ARM: www.armedslack.org From linuxxr at yahoo.com Thu Sep 17 17:46:40 2009 From: linuxxr at yahoo.com (brian kelley) Date: Thu, 17 Sep 2009 10:46:40 -0700 (PDT) Subject: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash In-Reply-To: Message-ID: <680433.8792.qm@web52403.mail.re2.yahoo.com> is there not a way to use? dfu-utilites to install the .jffs2 file to nand? --- On Wed, 9/16/09, Stuart Winter wrote: From: Stuart Winter Subject: Re: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash To: armedslack at lists.polplex.co.uk Date: Wednesday, September 16, 2009, 1:49 PM Hi Sam > I just booted from the ArmedSlack-12.2, sshed into it and started the setup. > It says I need to partition HardDrives. Is there any way to install > ArmedSlack on the internal NAND Partitions instead of an external device. The quick answer is "you can't". The longer answer is you *may* be able to do it, if you have a lot of patience, enough experience and tenacity :-) Things to note: 1.? The installer "partition probe" doesn't look for NAND devices 2.? Usually (from what I've read so far) you prepare a JFFS2 filesystem ? ???and write it to the NAND using "nandwrite" from the mtd-utils package ? ???then update the offsets in your u-boot boot loader config. ? ???I can't possibly think of a way to include this in the Slackware ? ???installer -- you'd have to install it on another machine using ? ???installpkg ROOT=/tmp/newarmmachine ? ???do some touchups to the configurations (since some of the package ? ???post-installation scripts wouldn't have run since they use chroot and ? ???run ARM binaries, which wouldn't work on an x86-- unless you happened ? ???to have a spare ARM box around to do the installation). ? ???A script to do the installation would be something like this: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/slackkit/sansinstaller ? ???You'd need to look at how to create a JFFS2 image of the result and ? ???write it to the NAND using "nandwrite". The research I did so far is here - ordered in some sort of useful fashion: ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/ ? ???What also occurred to be is that you could mount the existing jffs2 ? ???filesystem from the Slackware installer, and wipe the contents: ? ? ???mount -t jffs2 /dev/mtdblock2 /mnt/ ? ???or something like this.???This would have to be one of the ugliest ? ???ways of doing it. ? 3.? You'd need to use "nandwrite" to flash the kernel. ? 4.? The Slackware ARM 12.2 installer does not include the nandwrite ? ? ? tools.? The -current installer includes nandwrite and ? ? ? flash_eraseall but this isn't available yet, and the installer ? ? ? wouldn't work for a v12.2 installation. All in all, I'd say that the contents of the NAND flash are to be prepared by the vendor; especially since it'd need a stripped down Slackware. In advance you'd have to know which packages to include in order to make a working bootable Slackware installation, with enough space left over to have a useable system. -- Stuart Winter Slackware ARM: www.armedslack.org _______________________________________________ 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 Thu Sep 17 19:04:48 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 17 Sep 2009 20:04:48 +0100 (BST) Subject: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash In-Reply-To: <680433.8792.qm@web52403.mail.re2.yahoo.com> References: <680433.8792.qm@web52403.mail.re2.yahoo.com> Message-ID: > is there not a way to use? dfu-utilites to install the .jffs2 file to nand? Regardless of what tool was used to write a JFFS2 image to NAND, you'd still need to prepare the JFFS2 image somehow. How could this be achieved from the installer on an ARM box? You'd need somewhere to install to, then create a JFFS2 image from the installed "root". If you don't have an ARM box with the Slackware packaging tools, you have the same challenges I mentioned about the package post install scripts. All in all, my opinion is that the NAND is not somewhere to "install" to. It's a place for the vendor to ship a standard Blue Peter "look, here's what we did earlier" stock installation. I'm not saying that it cannot be done, but I think getting SD card installation support would be a) easier, b) more worth while since you can have large capacity SD cards. From linuxxr at yahoo.com Thu Sep 17 19:56:51 2009 From: linuxxr at yahoo.com (brian kelley) Date: Thu, 17 Sep 2009 12:56:51 -0700 (PDT) Subject: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash In-Reply-To: Message-ID: <96651.74194.qm@web52411.mail.re2.yahoo.com> ic? thanks --- On Thu, 9/17/09, Stuart Winter wrote: From: Stuart Winter Subject: Re: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash To: "Slackware ARM port" Date: Thursday, September 17, 2009, 2:04 PM > is there not a way to use? dfu-utilites to install the .jffs2 file to nand? Regardless of what tool was used to write a JFFS2 image to NAND, you'd still need to prepare the JFFS2 image somehow. How could this be achieved from the installer on an ARM box?? You'd need somewhere to install to, then create a JFFS2 image from the installed "root". If you don't have an ARM box with the Slackware packaging tools, you have the same challenges I mentioned about the package post install scripts. All in all, my opinion is that the NAND is not somewhere to "install" to. It's a place for the vendor to ship a standard Blue Peter "look, here's what we did earlier" stock installation. I'm not saying that it cannot be done, but I think getting SD card installation support would be a) easier, b) more worth while since you can have large capacity SD cards. -----Inline Attachment Follows----- _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.merle at free.fr Sat Sep 19 15:24:44 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Sat, 19 Sep 2009 17:24:44 +0200 Subject: [ARMedslack] sheevaplug: flashing initrd, consequently no uboot upgrade required Message-ID: <20090919172444.3c424dfd@lugdush.houroukhai.org> Hello, OK succeeded in flashing an initrd instead of the rootfs, and obviously booting on it. After some SP brickings (I even erased uboot by mistake, and I will never ever do that again), I managed to put initrd on flash and boot with it. In fact you should follow these directives: http://www.openplug.org/plugwiki/index.php/Flashing_an_Operating_System_onto_the_Plug But with some modifications: flash_erase /dev/mtdblock1 flash_eraseall /dev/mtd1 flash_erase /dev/mtdblock2 flash_eraseall /dev/mtd2 cat uImage-kirkwood > /dev/mtdblock1 cat uinitrd-kirkwood > /dev/mtdblock2 uImage-kirwood and uinitrd-kirkwood are found in armedslack-12.2 distribution. Then reboot and stop uboot in its automatic process with [ENTER] setenv bootcmd 'nand read.e 0x800000 0x100000 0x400000; nand read.e 0x01100000 0x500000 0x500000' #This will load in RAM the kernel, and the initrd image (5MB) setenv bootargs 'console=ttyS0,115200 ro root=/dev/sda1' #My USB disk has a root FS on sda1, in fact this is my NSLU2 installation. setenv arcNumber 2097 setenv mainlineLinux yes saveenv boot And you are done. I am not sure the flash_erase* commands are necessary but I experienced so many write errors that using them is the safest way to have something working. Well, I lied a bit, I did not flash the armedslack kernel but rebuilt a 2.6.31 kernel with the few patches to make it work on the SP (http://sheeva.with-linux.com/sheeva/index.php?dir=2.6.31%2Fpatches%2F) I had kernel panics with the armedslack kernel, specifically when I tried to configure Ethernet. I removed the kernel module from the initrd (mv643xx_eth) so the detection is made after, and no more kernel panic. This is probably a Thierry's problem. Cheers, Thierry From hachreak at gmail.com Sat Sep 19 15:41:52 2009 From: hachreak at gmail.com (Leo) Date: Sat, 19 Sep 2009 17:41:52 +0200 Subject: [ARMedslack] sheevaplug in europe Message-ID: Hi at all, i'm interested to use slackware in a sheevaplug. Sheevaplug is a interesting object because is power enough and very small. But i haven't found a seller in Italy, neither in Europe! Someone can help me? :-p Thanks a lot for any response. :D bye bye .hachreak. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry.merle at free.fr Sat Sep 19 16:11:15 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Sat, 19 Sep 2009 18:11:15 +0200 Subject: [ARMedslack] sheevaplug in europe In-Reply-To: References: Message-ID: <20090919181115.2369d9c3@lugdush.houroukhai.org> On Sat, 19 Sep 2009 17:41:52 +0200 Leo wrote: > Hi at all, > i'm interested to use slackware in a sheevaplug. > Sheevaplug is a interesting object because is power enough and very small. > But i haven't found a seller in Italy, neither in Europe! > Someone can help me? :-p http://www.globalscaletechnologies.com/p-26-sheevaplug-dev-kit-europe.aspx My SP comes from there, takes a couple of weeks. Thierry From thierry.merle at free.fr Sat Sep 19 16:55:02 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Sat, 19 Sep 2009 18:55:02 +0200 Subject: [ARMedslack] sheevaplug: flashing initrd, consequently no uboot upgrade required In-Reply-To: <20090919172444.3c424dfd@lugdush.houroukhai.org> References: <20090919172444.3c424dfd@lugdush.houroukhai.org> Message-ID: <20090919185502.21df46fc@lugdush.houroukhai.org> On Sat, 19 Sep 2009 17:24:44 +0200 Thierry MERLE wrote: > Hello, > OK succeeded in flashing an initrd instead of the rootfs, and obviously booting on it. > After some SP brickings (I even erased uboot by mistake, and I will never ever do that again), I managed to put initrd on flash and boot with it. > In fact you should follow these directives: http://www.openplug.org/plugwiki/index.php/Flashing_an_Operating_System_onto_the_Plug > But with some modifications: > flash_erase /dev/mtdblock1 > flash_eraseall /dev/mtd1 > flash_erase /dev/mtdblock2 > flash_eraseall /dev/mtd2 > cat uImage-kirkwood > /dev/mtdblock1 > cat uinitrd-kirkwood > /dev/mtdblock2 > uImage-kirwood and uinitrd-kirkwood are found in armedslack-12.2 distribution. > > Then reboot and stop uboot in its automatic process with [ENTER] > setenv bootcmd 'nand read.e 0x800000 0x100000 0x400000; nand read.e 0x01100000 0x500000 0x500000' sorry, the complete command is: setenv bootcmd 'nand read.e 0x800000 0x100000 0x400000; nand read.e 0x01100000 0x500000 0x500000; bootm 0x800000 0x01100000' in order to boot automatically after loading into RAM. > #This will load in RAM the kernel, and the initrd image (5MB) > setenv bootargs 'console=ttyS0,115200 ro root=/dev/sda1' > #My USB disk has a root FS on sda1, in fact this is my NSLU2 installation. > setenv arcNumber 2097 > setenv mainlineLinux yes > saveenv > boot > > And you are done. > I am not sure the flash_erase* commands are necessary but I experienced so many write errors that using them is the safest way to have something working. > > Well, I lied a bit, I did not flash the armedslack kernel but rebuilt a 2.6.31 kernel with the few patches to make it work on the SP (http://sheeva.with-linux.com/sheeva/index.php?dir=2.6.31%2Fpatches%2F) > I had kernel panics with the armedslack kernel, specifically when I > tried to configure Ethernet. I removed the kernel module from the initrd (mv643xx_eth) > so the detection is made after, and no more kernel panic. This is > probably a Thierry's problem. > > Cheers, > Thierry > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- , }\ ? _ .-` `-. o \`'./ (o)\ ) > ))) } O /_.'\ / \/ jgs `'---'=` http://thierry.merle.free.fr/ From mozes at slackware.com Mon Sep 21 13:51:42 2009 From: mozes at slackware.com (Stuart Winter) Date: Mon, 21 Sep 2009 06:51:42 -0700 (PDT) Subject: [ARMedslack] Slackware ARM current, EABI now available Message-ID: Hi I am pleased to announe the availability of the new EABI port of Slackware ARM, available as the work in progress "current" form. It's been a stable system for the last few months, so I'm pretty sure you'll have a good time using it. All of the main 'slackware' packages are built - I've not yet built all of the 'extra' packages yet though. This is a new port built from scratch, using the EABI, and is incompatible with Slackware ARM 12.2 -- so you can't upgrade your 12.2 installations using upgradepkg. For more information see: ftp://ftp.armedslack.org/armedslack/armedslack-current/ChangeLog.txt Enjoy! -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From gwenhael.le.moine at gmail.com Tue Sep 22 00:06:45 2009 From: gwenhael.le.moine at gmail.com (Gwenhael Le Moine) Date: Tue, 22 Sep 2009 07:06:45 +0700 Subject: [ARMedslack] Slackware ARM current, EABI now available In-Reply-To: References: Message-ID: <314c6c8f0909211706x47e16d15rfa0b9e06c4a30f54@mail.gmail.com> Now that's awesome! I was waiting for this great news to start fiddling with ArmedSlack on my zaurus (tosa). I played with Zubuntu a little bit, and with the Openembedded kexec kernel available it's a child's game to install a linux distro on this little beast :) I dreamt of running Slackware on this thing from the moment I bought it 5 years ago :P I hope to have something to report soon, I'm rsync'ing right now. Congrats, Gwenhael 2009/9/21 Stuart Winter : > > Hi > > I am pleased to announe the availability of the new EABI port of Slackware > ARM, available as the work in progress "current" form. > It's been a stable system for the last few months, so I'm pretty sure > you'll have a good time using it. ?All of the main 'slackware' packages > are built - I've not yet built all of the 'extra' packages yet though. > > This is a new port built from scratch, using the EABI, and is > incompatible with Slackware ARM 12.2 -- so you can't upgrade your > 12.2 installations using upgradepkg. > > For more information see: > ftp://ftp.armedslack.org/armedslack/armedslack-current/ChangeLog.txt > > Enjoy! > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From thierry.merle at free.fr Tue Sep 22 20:05:10 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Tue, 22 Sep 2009 22:05:10 +0200 Subject: [ARMedslack] Slackware ARM current, EABI now available In-Reply-To: References: Message-ID: <20090922220510.6f768ed5@lugdush.houroukhai.org> Hi Stuart, On Mon, 21 Sep 2009 06:51:42 -0700 (PDT) Stuart Winter wrote: > > Hi > > I am pleased to announe the availability of the new EABI port of Slackware > ARM, available as the work in progress "current" form. > It's been a stable system for the last few months, so I'm pretty sure > you'll have a good time using it. All of the main 'slackware' packages > are built - I've not yet built all of the 'extra' packages yet though. > > This is a new port built from scratch, using the EABI, and is > incompatible with Slackware ARM 12.2 -- so you can't upgrade your > 12.2 installations using upgradepkg. > > For more information see: > ftp://ftp.armedslack.org/armedslack/armedslack-current/ChangeLog.txt > > Enjoy! > Many thanks for this release. It installed it on my sheevaplug without any major problem since this morning. - I used the console setup, the setup runs and I am able to select packages and process through installation steps as for a standard slackware distribution. - After the installation, before rebooting, I flashed the uboot kernel and the uboot initrd using flash_erase/flash_eraseall/cat. Some issues: - the kirkwood uinitrd expects rootfs=/dev/sda4 as ext4, I had to modify it to boot properly on my system (well on a x86 slackware I always re-generate a custom initrd so I won't complain) - in the kernel, why CONFIG_DVB_CORE (between others in multimedia section) are not compiled? I will compile them since my sheevaplug (as my NSLU2 was) is used as a digital video recorder. In INSTALL_SHEEVAPLUG.TXT you talk about armedslack-12.2, should be armedslack-current. Not a real issue but dumb people like me could synchronize with armedslack-12.2 with in mind armedslack-current, by mistake :) Thierry From m-lists at biscuit.org.uk Wed Sep 23 09:15:22 2009 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 23 Sep 2009 10:15:22 +0100 (BST) Subject: [ARMedslack] Slackware ARM current, EABI now available In-Reply-To: <20090922220510.6f768ed5@lugdush.houroukhai.org> References: <20090922220510.6f768ed5@lugdush.houroukhai.org> Message-ID: Hi Thierry Thanks for the feedback. I'm pleased to see the EABI port being used so quickly! :-) > flash_erase/flash_eraseall/cat. Some issues: - the kirkwood uinitrd > expects rootfs=/dev/sda4 as ext4, These values are taken from whatever settings I happen to have on the build machine at the time of kernel compilation. I did consider making /dev/sda3 the default root partition since it's what the install docs use as an example, but I'd still have to specify the filesystem type -- which may or may not match the user's installed environment. The INSTALL_{QEMU,SHEEVAPLUG} documentation covers setting the root filesystem & partition to which ever values you use, so I'll leave the settings as they are when the kernel's built. > so I won't complain) - in the kernel, why CONFIG_DVB_CORE (between > others in multimedia section) are not compiled? They weren't in the Versatile config since doing that sort of task under QEMU isn't good for your mental health ;-) and the Kirkwood kernel config is based on the Versatile's. If you send me your new kernel config with the DVB stuff set as modules, I'll look at it and use it for the next kernel build. I have no problem including modules in the kernel-modules package, as long as the system remains stable. > recorder. In INSTALL_SHEEVAPLUG.TXT you talk about armedslack-12.2, > should be armedslack-current. Not a real issue but dumb people like me > could synchronize with armedslack-12.2 with in mind armedslack-current, > by mistake :) Thanks. It'll be fixed in the next update. -- Stuart Winter Slackware ARM: www.armedslack.org From thierry.merle at free.fr Thu Sep 24 20:16:23 2009 From: thierry.merle at free.fr (Thierry MERLE) Date: Thu, 24 Sep 2009 22:16:23 +0200 Subject: [ARMedslack] Slackware ARM current, EABI now available In-Reply-To: References: <20090922220510.6f768ed5@lugdush.houroukhai.org> Message-ID: <20090924221623.151d5112@lugdush.houroukhai.org> On Wed, 23 Sep 2009 10:15:22 +0100 (BST) Stuart Winter wrote: > > Hi Thierry > > Thanks for the feedback. I'm pleased to see the EABI port > being used so quickly! :-) > > > flash_erase/flash_eraseall/cat. Some issues: - the kirkwood uinitrd > > expects rootfs=/dev/sda4 as ext4, > > These values are taken from whatever settings I happen to have on > the build machine at the time of kernel compilation. > > I did consider making /dev/sda3 the default root partition since > it's what the install docs use as an example, but I'd still have > to specify the filesystem type -- which may or may not match > the user's installed environment. > > The INSTALL_{QEMU,SHEEVAPLUG} documentation covers setting the > root filesystem & partition to which ever values you use, so > I'll leave the settings as they are when the kernel's built. > OK. > If you send me your new kernel config with the DVB stuff set as modules, > I'll look at it and use it for the next kernel build. I have no problem > including modules in the kernel-modules package, as long as the system > remains stable. > Done. Tested OK with a dvb-t recorder, no issue. You can do a diff with the original config-kirkwood-2.6.31, only the multimedia part is compiled, as modules. Thierry -------------- next part -------------- A non-text attachment was scrubbed... Name: config-kirkwood-2.6.31-multimedia Type: application/octet-stream Size: 75010 bytes Desc: not available URL: From mozes at slackware.com Fri Sep 25 22:06:55 2009 From: mozes at slackware.com (Stuart Winter) Date: Fri, 25 Sep 2009 15:06:55 -0700 (PDT) Subject: [ARMedslack] Java Message-ID: Hi ARMedslack hasn't got a JRE yet, so I've been looking at OpenJDK and just realised how many other tools it requires in order to build. Is anybody familiar with building & packaging Java? :-) -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From linuxxr at yahoo.com Wed Sep 30 17:22:37 2009 From: linuxxr at yahoo.com (brian kelley) Date: Wed, 30 Sep 2009 10:22:37 -0700 (PDT) Subject: [ARMedslack] Java In-Reply-To: Message-ID: <801756.66698.qm@web52402.mail.re2.yahoo.com> i might have already asked this,,,???? is there a chance that SlackARM? will run on the openmoko freerunner? --- On Fri, 9/25/09, Stuart Winter wrote: From: Stuart Winter Subject: [ARMedslack] Java To: armedslack at lists.armedslack.org Date: Friday, September 25, 2009, 5:06 PM Hi ARMedslack hasn't got a JRE yet, so I've been looking at OpenJDK and just realised how many other tools it requires in order to build. Is anybody familiar with building & packaging Java? :-) -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmreis at epkis.com Wed Sep 30 17:33:21 2009 From: jmreis at epkis.com (Josep Maria Reis) Date: Wed, 30 Sep 2009 17:33:21 +0000 Subject: [ARMedslack] Java In-Reply-To: <801756.66698.qm@web52402.mail.re2.yahoo.com> References: <801756.66698.qm@web52402.mail.re2.yahoo.com> Message-ID: <3b92e1fd0909301033q4f2ef330n9e9b1876933cf4ba@mail.gmail.com> I've been searching it on google and i found nothing... I'm interested in SlackARM and FreeRunner too... Thanks! ;) 2009/9/30 brian kelley > i might have already asked this,,, is there a chance that SlackARM > will run on the openmoko freerunner? > > --- On *Fri, 9/25/09, Stuart Winter * wrote: > > > From: Stuart Winter > Subject: [ARMedslack] Java > To: armedslack at lists.armedslack.org > Date: Friday, September 25, 2009, 5:06 PM > > > Hi > > ARMedslack hasn't got a JRE yet, so I've been looking at OpenJDK and > just realised how many other tools it requires in order to build. > > Is anybody familiar with building & packaging Java? :-) > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -- Josep M? Reis Linux User #469871 http://epkis.com http://www.cobert.cat -------------- next part -------------- An HTML attachment was scrubbed... URL: