From ottavio2006-usenet2012 at yahoo.com Tue Apr 2 14:45:13 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Tue, 2 Apr 2013 15:45:13 +0100 Subject: [ARMedslack] How does Armedslack handle touchscreens? Message-ID: I know it's a broad question but, in case I wanted to jailbreak my Samsung Galaxy player and install some Linux distro fs in a chroot, how would for example Slackware handle a touchscreen? (My device is too small to attach a keyboard). For example when I installed Slackware on the Chromebook I copied over /lib/firmware and /lib/modules to the chroot. Would this work on an Android host? Has anybody tried it? Thanks -- Ottavio From stanley at stanleygarvey.com Tue Apr 2 16:29:40 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Tue, 02 Apr 2013 17:29:40 +0100 Subject: [ARMedslack] Quick question In-Reply-To: References: <20130331222434.BB2BC7BDE0FC2@bmail04.one.com> Message-ID: <20130402162940.3CDCAD605E269@bmail-n01.one.com> On Mar 31, 2013 23:37 "Ottavio Caruso" wrote: > An installer assumes that you have a removable media from which you > can boot, which is not the case for most commercial devices on the > market, as they are boot-locked. > > Okay, the user would need a set of screwdrivers, and a distinction in > electronic servicing. My bad. :) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openpandora at free.fr Tue Apr 2 16:37:44 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 2 Apr 2013 18:37:44 +0200 (CEST) Subject: [ARMedslack] How does Armedslack handle touchscreens? In-Reply-To: Message-ID: <1616011102.6097563.1364920664682.JavaMail.root@zimbra53-e8.priv.proxad.net> I think it's evdev. I had problem with tslib since 14.0 as the input X driver crashed X. LS. ----- Mail original ----- De: "Ottavio Caruso" ?: ARMedslack at lists.armedslack.org Envoy?: Mardi 2 Avril 2013 16:45:13 Objet: [ARMedslack] How does Armedslack handle touchscreens? I know it's a broad question but, in case I wanted to jailbreak my Samsung Galaxy player and install some Linux distro fs in a chroot, how would for example Slackware handle a touchscreen? (My device is too small to attach a keyboard). For example when I installed Slackware on the Chromebook I copied over /lib/firmware and /lib/modules to the chroot. Would this work on an Android host? Has anybody tried it? Thanks -- Ottavio _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From openpandora at free.fr Tue Apr 2 16:41:37 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 2 Apr 2013 18:41:37 +0200 (CEST) Subject: [ARMedslack] Jumping cursor with touchscreen. In-Reply-To: <1362173139.51311cd311de4@imp.free.fr> Message-ID: <1174701102.6101177.1364920897181.JavaMail.root@zimbra53-e8.priv.proxad.net> I've made a video about my jumping cursor: http://slackware.openpandora.org/pandora/videos/screen/jumping_touchscreen.avi Meanwhile, i recompiled the latest evdev driver, so now, i'm 100% sure it's not the culprit. It's something more GTK-related. ----- Mail original ----- De: openpandora at free.fr ?: armedslack at lists.armedslack.org Envoy?: Vendredi 1 Mars 2013 22:25:39 Objet: [ARMedslack] Jumping cursor with touchscreen. Hi ! Sometimes, the cursor jumps to the top left corner of the screen when i'm manipulating particular things on the screen. Things like a scrollbar, an object in Thunar, a slider, the menu's up and down, so it's not a hardware or a calibration problem (same behavior on my two Pandora units). As i've no idea about where to begin (gtk bug ?), i'm asking there. beagleboard.googlecode.com/files/evtest.c reports no "jumping" coordinates. Are Xfce sliders and so on handled by gtk+, gtk+2 ? LS _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Tue Apr 2 16:42:53 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 2 Apr 2013 17:42:53 +0100 (BST) Subject: [ARMedslack] Quick question In-Reply-To: <20130402162940.3CDCAD605E269@bmail-n01.one.com> References: <20130331222434.BB2BC7BDE0FC2@bmail04.one.com> <20130402162940.3CDCAD605E269@bmail-n01.one.com> Message-ID: > > An installer assumes that you have a removable media from which you > > can boot, which is not the case for most commercial devices on the > > market, as they are boot-locked. > > > > Okay, the user would need a set of screwdrivers, and a distinction in > > electronic servicing. My bad. :) The Slackware installers on Kirkwood and Tegra do not use removable media - it's installed over the network. My own personal opinion (which I think isn't at all in line with anyone else's, from what I can tell) is that a device such as a phone isn't really a candidate for your favourite OS - it's just about what apps you can install upon it; thus it would never cross my mind to want to install Slackware on my ARM powered phone. -- Stuart Winter Slackware ARM: http://arm.slackware.com From ottavio2006-usenet2012 at yahoo.com Tue Apr 2 17:28:54 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Tue, 2 Apr 2013 18:28:54 +0100 Subject: [ARMedslack] Quick question In-Reply-To: References: <20130331222434.BB2BC7BDE0FC2@bmail04.one.com> <20130402162940.3CDCAD605E269@bmail-n01.one.com> Message-ID: On Apr 2, 2013 5:43 PM, "Stuart Winter" wrote: > > > > > An installer assumes that you have a removable media from which you > > > can boot, which is not the case for most commercial devices on the > > > market, as they are boot-locked. > > > > > > Okay, the user would need a set of screwdrivers, and a distinction in > > > electronic servicing. My bad. :) > > The Slackware installers on Kirkwood and Tegra do not use removable > media - it's installed over the network. > > My own personal opinion (which I think isn't at all in line with anyone > else's, from what I can tell) is that a device such as a phone isn't > really a candidate for your favourite OS - it's just about what apps you > can install upon it; thus it would never cross my mind to want to install > Slackware on my ARM powered phone. Disappointed! But let me make a prediction: you will change your mind. > -- > Stuart Winter > Slackware ARM: http://arm.slackware.com > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From nsollars at gmail.com Fri Apr 5 19:52:14 2013 From: nsollars at gmail.com (Nigel Sollars) Date: Fri, 5 Apr 2013 15:52:14 -0400 Subject: [ARMedslack] Slackware on ASUS Transformer Pad? In-Reply-To: <20130405104602.GA7093@lnb.localnet> References: <20130405104602.GA7093@lnb.localnet> Message-ID: Hi, Not me, interesting idea though. Firmware flashing would be a challenge I would imagine out of the gate. Would be the time to try thought with Open Tegra SoC drivers becoming available. Nige -------------- next part -------------- An HTML attachment was scrubbed... URL: From mozes at slackware.com Wed Apr 10 13:38:00 2013 From: mozes at slackware.com (Stuart Winter) Date: Wed, 10 Apr 2013 06:38:00 -0700 (PDT) Subject: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0 Message-ID: Hi When I bumped the minimum kernel version required by glibc to Linux 3.4.0, I'd checked the Raspberry Pi stuff and believed that the Raspberry Pi's had a mimimum of Linux Kernel v3.6 available. >From what I can see now, it looks like some of the RPi images are using Linux 3.1. Is there anyone who's distributing anything that's older than this version? It looks like I'll need to respin glibc to change the mimimum kernel to be 3.1.0 so that RPi users can upgrade to Slackware ARM 14.0 to 14.1. -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: http://arm.slackware.com From stanley at stanleygarvey.com Wed Apr 10 22:20:05 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Wed, 10 Apr 2013 23:20:05 +0100 Subject: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0 In-Reply-To: References: Message-ID: <20130410222005.D5FA2E35ACC96@bmail-n01.one.com> On Apr 10, 2013 14:38 "Stuart Winter" wrote: > Hi > > When I bumped the minimum kernel version required by glibc to Linux > 3.4.0, > I'd checked the Raspberry Pi stuff and believed that the Raspberry > Pi's > had a mimimum of Linux Kernel v3.6 available. > > From what I can see now, it looks like some of the RPi images are > using > Linux 3.1. Is there anyone who's distributing anything that's older > than > this version? It looks like I'll need to respin glibc to change the > mimimum kernel to be 3.1.0 so that RPi users can upgrade to Slackware > ARM > 14.0 to 14.1. > > Hello, > David spencers installer uses the 3.1.9 kernel, Sorinm's image is also > using 3.1.9, I am using 3.2.27, I don't know of any kernels older that > these. Some people use the Rpi-update script and so will be using v3.6 > even if they started using v3.1. My 3.2.27 kernels are now built using > your build scripts and no longer use the default name 'kernel.bin' and > would be unaffected by Rpi-update. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Apr 11 07:40:28 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 11 Apr 2013 08:40:28 +0100 (BST) Subject: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0 In-Reply-To: <20130410222005.D5FA2E35ACC96@bmail-n01.one.com> References: <20130410222005.D5FA2E35ACC96@bmail-n01.one.com> Message-ID: > > David spencers installer uses the 3.1.9 kernel, Sorinm's image is also > > using 3.1.9, I am using 3.2.27, I don't know of any kernels older that > > these. Some people use the Rpi-update script and so will be using v3.6 > > even if they started using v3.1. My 3.2.27 kernels are now built using > > your build scripts and no longer use the default name 'kernel.bin' and > > would be unaffected by Rpi-update. OK thanks - I've rebuilt glibc against 3.1.0 so as to allow a live upgrade from 14.0 to 14.1. It'd be nice to see some Rpi kernel upgrades to the latest release -- is the Rpi support not yet in the upstream kernels? -- Stuart Winter Slackware ARM: http://arm.slackware.com From openpandora at free.fr Thu Apr 11 11:50:39 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Thu, 11 Apr 2013 13:50:39 +0200 (CEST) Subject: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0 In-Reply-To: Message-ID: <1881236110.15654918.1365681039821.JavaMail.root@zimbra53-e8.priv.proxad.net> God news for the Open Pandora port. The kernel is 3.2 and i had troubles building a more recent. LS ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Jeudi 11 Avril 2013 09:40:28 Objet: Re: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0 > > David spencers installer uses the 3.1.9 kernel, Sorinm's image is also > > using 3.1.9, I am using 3.2.27, I don't know of any kernels older that > > these. Some people use the Rpi-update script and so will be using v3.6 > > even if they started using v3.1. My 3.2.27 kernels are now built using > > your build scripts and no longer use the default name 'kernel.bin' and > > would be unaffected by Rpi-update. OK thanks - I've rebuilt glibc against 3.1.0 so as to allow a live upgrade from 14.0 to 14.1. It'd be nice to see some Rpi kernel upgrades to the latest release -- is the Rpi support not yet in the upstream kernels? -- Stuart Winter Slackware ARM: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From openpandora at free.fr Thu Apr 11 22:09:47 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 00:09:47 +0200 (CEST) Subject: [ARMedslack] Openjre/jdk in -current. In-Reply-To: <643270982.16201220.1365718168525.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1057597207.16201267.1365718187603.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! I would like to know about it's inclusion in /d , or it's non-inclusion (in /patches ?). LS From stanley at stanleygarvey.com Thu Apr 11 22:50:15 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 11 Apr 2013 23:50:15 +0100 Subject: [ARMedslack] Raspberry Pi Linux kernel versions for Slackware ARM 14.0 In-Reply-To: References: <20130410222005.D5FA2E35ACC96@bmail-n01.one.com> Message-ID: <20130411225015.87D6EC718DB1D@bmail03.one.com> On Apr 11, 2013 08:40 "Stuart Winter" wrote: > > > David spencers installer uses the 3.1.9 kernel, Sorinm's image is > > > also > > > using 3.1.9, I am using 3.2.27, I don't know of any kernels older > > > that > > > these. Some people use the Rpi-update script and so will be using > > > v3.6 > > > even if they started using v3.1. My 3.2.27 kernels are now built > > > using > > > your build scripts and no longer use the default name 'kernel.bin' > > > and > > > would be unaffected by Rpi-update. > > OK thanks - I've rebuilt glibc against 3.1.0 so as to allow a live > upgrade > from 14.0 to 14.1. It'd be nice to see some Rpi kernel upgrades to the > latest release -- is the Rpi support not yet in the upstream kernels? > > I will have a look at kernel.org over the weekend to see if Rpi > support is included. My feeling is that Rpi support will probably be > included for v3.1 and 3.2 as active development has ceased for these > versions on github. This is why I stuck with 3.2.27, kernel upgrades > are frequent on github and v3.6.y is in constant flux at present. > > David Spencers site has not been updated since august last year and > although Sorinms site seems to be active I note he is still using > v3.1.9, Sorinm is also not a fan of the rpi-update script as it may > silently break something. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openpandora at free.fr Thu Apr 11 23:20:22 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 01:20:22 +0200 (CEST) Subject: [ARMedslack] Openjre/jdk in -current. In-Reply-To: <1057597207.16201267.1365718187603.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1725151725.16222930.1365722422260.JavaMail.root@zimbra53-e8.priv.proxad.net> Just saw it's in /extra . LS ----- Mail original ----- De: openpandora at free.fr ?: "Slackware ARM port" Envoy?: Vendredi 12 Avril 2013 00:09:47 Objet: [ARMedslack] Openjre/jdk in -current. Hi ! I would like to know about it's inclusion in /d , or it's non-inclusion (in /patches ?). LS _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Fri Apr 12 06:40:16 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 12 Apr 2013 07:40:16 +0100 (BST) Subject: [ARMedslack] Openjre/jdk in -current. In-Reply-To: <1725151725.16222930.1365722422260.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <1725151725.16222930.1365722422260.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: > Just saw it's in /extra . The 'patches' directory is only used once a tree has been marked as a stable release. From openpandora at free.fr Fri Apr 12 13:33:08 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 15:33:08 +0200 (CEST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: <395526539.16843661.1365773561270.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <2065779663.16844016.1365773588311.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! The omap driver isn't included in Slackware ARM: http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ LS From openpandora at free.fr Fri Apr 12 13:46:31 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 15:46:31 +0200 (CEST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: <2065779663.16844016.1365773588311.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <996391424.16859895.1365774391635.JavaMail.root@zimbra53-e8.priv.proxad.net> Arhh, this version seems not stable: http://archlinuxarm.org/forum/viewtopic.php?t=4147&p=24412#p24509 ----- Mail original ----- De: openpandora at free.fr ?: "Slackware ARM port" Envoy?: Vendredi 12 Avril 2013 15:33:08 Objet: [ARMedslack] Omap video driver request. Hi ! The omap driver isn't included in Slackware ARM: http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ LS _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From ottavio2006-usenet2012 at yahoo.com Fri Apr 12 13:44:33 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Fri, 12 Apr 2013 14:44:33 +0100 Subject: [ARMedslack] Omap video driver request. In-Reply-To: <2065779663.16844016.1365773588311.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <395526539.16843661.1365773561270.JavaMail.root@zimbra53-e8.priv.proxad.net> <2065779663.16844016.1365773588311.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: On 12 April 2013 14:33, wrote: > Hi ! > > The omap driver isn't included in Slackware ARM: > http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ > The source is in the "slackware64-current/source/x/x11/src/driver" repo. can you build it from there? (And is it supposed to work on ARM?) -- Ottavio From m-lists at biscuit.org.uk Fri Apr 12 14:16:41 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 12 Apr 2013 15:16:41 +0100 (BST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: References: <395526539.16843661.1365773561270.JavaMail.root@zimbra53-e8.priv.proxad.net> <2065779663.16844016.1365773588311.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: > > The omap driver isn't included in Slackware ARM: > > http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ > > > > The source is in the "slackware64-current/source/x/x11/src/driver" > repo. can you build it from there? (And is it supposed to work on > ARM?) It builds... http://armed.slackware.com/slackwarearm-current/test/x/xf86-video-omap-0.4.3-arm-1.tgz Does it work on the *latest* -current? (not one from months ago ;p) From openpandora at free.fr Fri Apr 12 15:15:18 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 17:15:18 +0200 (CEST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: Message-ID: <165470968.16962645.1365779718478.JavaMail.root@zimbra53-e8.priv.proxad.net> Tired your package. Same result as mine: [ 7251.661] ABI class: X.Org XInput driver, version 19.1 [ 7251.661] (II) OMAP: Driver for TI OMAP: OMAP3430 with PowerVR SGX530, OMAP3630 with PowerVR SGX530, OMAP4430 with PowerVR SGX540, OMAP4460 with PowerVR SGX540, OMAP5430 with PowerVR SGX544 MP, OMAP5432 with PowerVR SGX544 MP [ 7251.662] (--) using VT number 7 [ 7251.666] (WW) Falling back to old probe method for omap [ 7251.994] (EE) No devices detected. [ 7251.994] Fatal server error: [ 7251.994] no screens found [ 7251.994] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org For previous Slackware versions, i used this one, which was working perfectly: http://git.pingu.fi/xf86-video-omapfb For now it doesn't compile: omapfb-driver.c: In function 'OMAPFBCloseScreen': omapfb-driver.c:487:2: warning: passing argument 1 of 'pScreen->CloseScreen' makes pointer from integer without a cast [enabled by default] return (*pScreen->CloseScreen)(scrnIndex, pScreen); ^ omapfb-driver.c:487:2: note: expected 'ScreenPtr' but argument is of type 'int' omapfb-driver.c:487:2: error: too many arguments to function 'pScreen->CloseScreen' omapfb-driver.c: In function 'OMAPFBScreenInit': omapfb-driver.c:497:23: warning: assignment from incompatible pointer type [enabled by default] pScreen->CloseScreen = OMAPFBCloseScreen; ^ omapfb-driver.c: At top level: omapfb-driver.c:713:2: warning: initialization discards 'const' qualifier from pointer target type [enabled by default] OMAPFB_DRIVER_NAME, ^ make[2]: *** [omapfb-driver.lo] Error 1 make[2]: Leaving directory `/root/xf86-video-omapfb/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/xf86-video-omapfb' make: *** [all] Error 2 root at darkstar:~/xf86-video-omapfb# ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Vendredi 12 Avril 2013 16:16:41 Objet: Re: [ARMedslack] Omap video driver request. > > The omap driver isn't included in Slackware ARM: > > http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ > > > > The source is in the "slackware64-current/source/x/x11/src/driver" > repo. can you build it from there? (And is it supposed to work on > ARM?) It builds... http://armed.slackware.com/slackwarearm-current/test/x/xf86-video-omap-0.4.3-arm-1.tgz Does it work on the *latest* -current? (not one from months ago ;p) _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From openpandora at free.fr Fri Apr 12 15:17:13 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 17:17:13 +0200 (CEST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: Message-ID: <1549266587.16964217.1365779833176.JavaMail.root@zimbra53-e8.priv.proxad.net> Yes, omap is a Texas Instruments SoC brand: http://en.wikipedia.org/wiki/Omap ----- Mail original ----- De: "Ottavio Caruso" ?: "Slackware ARM port" Envoy?: Vendredi 12 Avril 2013 15:44:33 Objet: Re: [ARMedslack] Omap video driver request. On 12 April 2013 14:33, wrote: > Hi ! > > The omap driver isn't included in Slackware ARM: > http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ > The source is in the "slackware64-current/source/x/x11/src/driver" repo. can you build it from there? (And is it supposed to work on ARM?) -- Ottavio _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Fri Apr 12 15:39:54 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 12 Apr 2013 16:39:54 +0100 (BST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: <165470968.16962645.1365779718478.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <165470968.16962645.1365779718478.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: > Tired your package. Same result as mine: What about the fb versio? http://armed.slackware.com/slackwarearm-current/test/x/xf86-video-omapfb-0.1.1.1-arm-1.tgz From openpandora at free.fr Fri Apr 12 20:04:02 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 22:04:02 +0200 (CEST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: Message-ID: <1233149592.17211197.1365797042635.JavaMail.root@zimbra53-e8.priv.proxad.net> Segfault: [ 372.736] (II) omapfb(0): XRandR extension initialized [ 372.736] (--) omapfb(0): Virtual size is 800x1440 (pitch 800) [ 372.736] (**) omapfb(0): Mode "720x574": 13.5 MHz, 15.6 kHz, 25.0 Hz [ 372.736] (II) omapfb(0): Modeline "720x574"x25.0 13.50 720 732 788 864 574 579 615 625 (15.6 kHz P) [ 372.736] (==) omapfb(0): DPI set to (96, 96) [ 372.737] (EE) [ 372.737] (EE) Backtrace: [ 372.737] (EE) [ 372.737] (EE) Segmentation fault at address 0x3 [ 372.737] Fatal server error: [ 372.737] Caught signal 11 (Segmentation fault). Server aborting [ 372.737] [ 372.737] (EE) ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Vendredi 12 Avril 2013 17:39:54 Objet: Re: [ARMedslack] Omap video driver request. > Tired your package. Same result as mine: What about the fb versio? http://armed.slackware.com/slackwarearm-current/test/x/xf86-video-omapfb-0.1.1.1-arm-1.tgz _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From openpandora at free.fr Fri Apr 12 21:54:06 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 12 Apr 2013 23:54:06 +0200 (CEST) Subject: [ARMedslack] xorgsetup doesn't seem to produce any xorg.conf Message-ID: <627547096.17259015.1365803646872.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! Tried two times. LS From m-lists at biscuit.org.uk Sat Apr 13 07:24:29 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 13 Apr 2013 08:24:29 +0100 (BST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: <1233149592.17211197.1365797042635.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <1233149592.17211197.1365797042635.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: > Segfault: > [ 372.736] (II) omapfb(0): XRandR extension initialized > [ 372.736] (--) omapfb(0): Virtual size is 800x1440 (pitch 800) > [ 372.736] (**) omapfb(0): Mode "720x574": 13.5 MHz, 15.6 kHz, 25.0 Hz > [ 372.736] (II) omapfb(0): Modeline "720x574"x25.0 13.50 720 732 788 864 574 579 615 625 (15.6 kHz P) > [ 372.736] (==) omapfb(0): DPI set to (96, 96) > [ 372.737] (EE) > [ 372.737] (EE) Backtrace: > [ 372.737] (EE) > [ 372.737] (EE) Segmentation fault at address 0x3 > [ 372.737] > Fatal server error: > [ 372.737] Caught signal 11 (Segmentation fault). Server aborting > [ 372.737] > [ 372.737] (EE) Is this actually a recent current? I ask since you've already said that you haven't updated since you couldn't run glibc-2.17 as it was built to require Linux 3.4.0. The xorg server has been updated since then. From ottavio2006-usenet2012 at yahoo.com Sat Apr 13 08:37:46 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Sat, 13 Apr 2013 09:37:46 +0100 Subject: [ARMedslack] xorgsetup doesn't seem to produce any xorg.conf In-Reply-To: <627547096.17259015.1365803646872.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <627547096.17259015.1365803646872.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: On 12 April 2013 22:54, wrote: > Hi ! > > Tried two times. > I don't know about ARM but on the PC creating a xorg.conf file is deprecated. One should manipulate files in /etc/X11/xorg.d/ instead. -- Ottavio From ottavio2006-usenet2012 at yahoo.com Sat Apr 13 08:51:46 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Sat, 13 Apr 2013 09:51:46 +0100 Subject: [ARMedslack] TI OMAP 3630, was: Omap video driver request. Message-ID: On 12 April 2013 14:44, Ottavio Caruso wrote: > On 12 April 2013 14:33, wrote: >> Hi ! >> >> The omap driver isn't included in Slackware ARM: >> http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ And incidentally, I have a Samsung 4.2'' player with CPU OMAP 3630. Does anybody know if it's fully supported (module and firmware-wise) in the vanilla kernel? Thanks -- Ottavio From ottavio2006-usenet2012 at yahoo.com Sat Apr 13 11:37:14 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Sat, 13 Apr 2013 12:37:14 +0100 Subject: [ARMedslack] TI OMAP 3630, was: Omap video driver request. In-Reply-To: References: Message-ID: On 13 April 2013 09:51, Ottavio Caruso wrote: > And incidentally, I have a Samsung 4.2'' player with CPU OMAP 3630. > Does anybody know if it's fully supported (module and firmware-wise) > in the vanilla kernel? I'll rephrase my question: does the OMAP3 cover all OMAP3**** variants? -- Ottavio From openpandora at free.fr Sat Apr 13 12:05:13 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 13 Apr 2013 14:05:13 +0200 (CEST) Subject: [ARMedslack] xorgsetup doesn't seem to produce any xorg.conf In-Reply-To: Message-ID: <1588881298.17740951.1365854713221.JavaMail.root@zimbra53-e8.priv.proxad.net> Ah ok. Times are changing... Thx. ----- Mail original ----- De: "Ottavio Caruso" ?: "Slackware ARM port" Envoy?: Samedi 13 Avril 2013 10:37:46 Objet: Re: [ARMedslack] xorgsetup doesn't seem to produce any xorg.conf On 12 April 2013 22:54, wrote: > Hi ! > > Tried two times. > I don't know about ARM but on the PC creating a xorg.conf file is deprecated. One should manipulate files in /etc/X11/xorg.d/ instead. -- Ottavio _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From openpandora at free.fr Sat Apr 13 12:06:13 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 13 Apr 2013 14:06:13 +0200 (CEST) Subject: [ARMedslack] Omap video driver request. In-Reply-To: Message-ID: <1969399116.17741453.1365854773377.JavaMail.root@zimbra53-e8.priv.proxad.net> Yes, it's recent from yesterday. I resumed the work on -current as soon as it was possible. ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Samedi 13 Avril 2013 09:24:29 Objet: Re: [ARMedslack] Omap video driver request. > Segfault: > [ 372.736] (II) omapfb(0): XRandR extension initialized > [ 372.736] (--) omapfb(0): Virtual size is 800x1440 (pitch 800) > [ 372.736] (**) omapfb(0): Mode "720x574": 13.5 MHz, 15.6 kHz, 25.0 Hz > [ 372.736] (II) omapfb(0): Modeline "720x574"x25.0 13.50 720 732 788 864 574 579 615 625 (15.6 kHz P) > [ 372.736] (==) omapfb(0): DPI set to (96, 96) > [ 372.737] (EE) > [ 372.737] (EE) Backtrace: > [ 372.737] (EE) > [ 372.737] (EE) Segmentation fault at address 0x3 > [ 372.737] > Fatal server error: > [ 372.737] Caught signal 11 (Segmentation fault). Server aborting > [ 372.737] > [ 372.737] (EE) Is this actually a recent current? I ask since you've already said that you haven't updated since you couldn't run glibc-2.17 as it was built to require Linux 3.4.0. The xorg server has been updated since then. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From nsollars at gmail.com Sat Apr 13 11:30:58 2013 From: nsollars at gmail.com (Nigel Sollars) Date: Sat, 13 Apr 2013 07:30:58 -0400 Subject: [ARMedslack] TI OMAP 3630, was: Omap video driver request. In-Reply-To: References: Message-ID: HI, I would say no, as it contains the PowerVR SGX gpu core ( would be the same for OMAP4 ). This one is still very proprietary, on saying that though the hope I have is that with AMD entering the fray and Tegra having open source releases ( all be it slowly ), Imagination technologies my very well do the same. Nige On Sat, Apr 13, 2013 at 4:51 AM, Ottavio Caruso < ottavio2006-usenet2012 at yahoo.com> wrote: > On 12 April 2013 14:44, Ottavio Caruso > wrote: > > On 12 April 2013 14:33, wrote: > >> Hi ! > >> > >> The omap driver isn't included in Slackware ARM: > >> http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/ > > And incidentally, I have a Samsung 4.2'' player with CPU OMAP 3630. > Does anybody know if it's fully supported (module and firmware-wise) > in the vanilla kernel? > > Thanks > > > -- > Ottavio > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: From nsollars at gmail.com Sat Apr 13 11:55:37 2013 From: nsollars at gmail.com (Nigel Sollars) Date: Sat, 13 Apr 2013 07:55:37 -0400 Subject: [ARMedslack] TI OMAP 3630, was: Omap video driver request. In-Reply-To: References: Message-ID: In General that statement would be true, but ( and there is one ) you have to be careful with the slight variants, looking at the Ti site: http://www.ti.com/lsds/ti/omap-applications-processors/omap-3-processors-products.page?paramCriteria=no%3f it seems they have dropped anything below 36xx, but I am sure there are still alot of 3xxx hardware below that one being produced. As far as the Linux kernel is concerned, they have really done an awesome job of building the boilerplate generic base for all Arm Cortex SoC's to which then you would add specific modules too that support your manufacturer ( Nv, Ti Omap etc etc etc )... I think to be honest the up and coming 3.9 kernel should probably be the defecto choice if you have an Arm SoC, since there have been so many changes and additions to the Arm tree. Nige On Sat, Apr 13, 2013 at 7:37 AM, Ottavio Caruso < ottavio2006-usenet2012 at yahoo.com> wrote: > On 13 April 2013 09:51, Ottavio Caruso > wrote: > > And incidentally, I have a Samsung 4.2'' player with CPU OMAP 3630. > > Does anybody know if it's fully supported (module and firmware-wise) > > in the vanilla kernel? > > I'll rephrase my question: does the OMAP3 cover all OMAP3**** variants? > > > > > -- > Ottavio > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Apr 15 14:43:44 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 15 Apr 2013 15:43:44 +0100 (BST) Subject: [ARMedslack] miniroot 14 and current: vi is broken In-Reply-To: References: Message-ID: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> I noticed that in the miniroot, both current and 14, vi? is broken looking for libperl and libpython . I know most of you will like to use nano ... but I'm an old fart and I still like vi !!! It can be fixed by installing a few packages: perl-5.16.1-arm-1.tgz python-2.7.3-arm-2.tgz -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Apr 15 15:52:22 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 15 Apr 2013 16:52:22 +0100 (BST) Subject: [ARMedslack] miniroot 14 and current: vi is broken In-Reply-To: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: On Mon, 15 Apr 2013, Davide wrote: > I noticed that in the miniroot, both current and 14, vi? is broken looking for libperl and libpython . > I know most of you will like to use nano ... but I'm an old fart and I still like vi !!! Hmm. I'm going to replace vim with elvis as this works without bundling additional packages. -- Stuart Winter Slackware ARM: http://arm.slackware.com From Norman.Evanson at arm.com Mon Apr 15 15:54:46 2013 From: Norman.Evanson at arm.com (Norman Evanson) Date: Mon, 15 Apr 2013 16:54:46 +0100 Subject: [ARMedslack] (no subject) Message-ID: <32A567653942814C9A113261661F9EBC40E112885D@GEORGE.Emea.Arm.com> unsubscribe -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben at bauers.ca Mon Apr 15 19:46:37 2013 From: ben at bauers.ca (Ben Bauer) Date: Mon, 15 Apr 2013 15:46:37 -0400 Subject: [ARMedslack] Avatar S701-R2A-1 Sirius 7" Tablet Message-ID: <20130415154637.27cb07df@woad.local.net> http://www.comtronic.ca/cci/home.php?do=ShowProducts&cmd=detail&cid=NB&pid=017133 CPU ARM Cortex-A9 1.0GHz Single Core GPU Mali-400, with 3D Accelerator Memory 1GB DDR3 Storage 4GB NAND Flash Display 7" TFT-LCD ... I/O Ports 1 x Micro USB 2.0 Port 1 x Mini HDMI Port 1 x TF Card Slot 1 x Power Port Does anyone have experience with this (or similar hardware)? I am hoping to put Slackware native on this and move over some python programs (currently prototyped on an Atom processor) that I have written for classroom use ( audience response system, multiple choice testing, flashcards etc). I am a Slacker since 1994 but ARM is new to me. Naive questions: 1) any chance I can boot from CF card ? 2) if so, is a USB keyboard likely to autodetect? 3) would X be mulitouch or single? 4) is there a better/easier sub $100 device I should consider? From stanley at stanleygarvey.com Mon Apr 15 20:02:32 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 15 Apr 2013 21:02:32 +0100 Subject: [ARMedslack] Avatar S701-R2A-1 Sirius 7" Tablet In-Reply-To: <20130415154637.27cb07df@woad.local.net> References: <20130415154637.27cb07df@woad.local.net> Message-ID: <20130415200232.647F01D68E17B@bmail06.one.com> On Apr 15, 2013 20:46 "Ben Bauer" wrote: > B&pid=017133> > > CPU ARM Cortex-A9 1.0GHz Single Core > GPU Mali-400, with 3D Accelerator > Memory 1GB DDR3 > Storage 4GB NAND Flash > Display 7" TFT-LCD > ... > I/O Ports 1 x Micro USB 2.0 Port > 1 x Mini HDMI Port > 1 x TF Card Slot > 1 x Power Port > > Does anyone have experience with this (or similar hardware)? > I am hoping to put Slackware native on this and move over some > python programs (currently prototyped on an Atom processor) > that I have written for classroom use ( audience response > system, multiple choice testing, flashcards etc). I am a Slacker > since 1994 but ARM is new to me. Naive questions: > > 1) any chance I can boot from CF card ? > 2) if so, is a USB keyboard likely to autodetect? > 3) would X be mulitouch or single? > 4) is there a better/easier sub $100 device I should consider? > _______________________________________________ > ARMedslack mailing list > > > 4) Yes, consider using a raspberry pi, it is under $100 and runs > slackwarearm debian arch and more. The raspberriy pi is a neat little > arm computer that runs from CF card. It's not a tablet but can connect > to tv's monitors and hdtv's.it needs a 5 volt 1 amp psu has no moving > parts and no fan and yes it is ARM! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Mon Apr 15 20:21:52 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Mon, 15 Apr 2013 21:21:52 +0100 Subject: [ARMedslack] Avatar S701-R2A-1 Sirius 7" Tablet In-Reply-To: <20130415200232.647F01D68E17B@bmail06.one.com> References: <20130415154637.27cb07df@woad.local.net> <20130415200232.647F01D68E17B@bmail06.one.com> Message-ID: The Raspberry is a million times less usable than the worst tablet on the market. It's ok to laud such projects but the reality is that tablets and mobiles are the de facto new standard. (sent from my 4.2" Samsung) On Apr 15, 2013 9:02 PM, "stanley garvey" wrote: > On Apr 15, 2013 20:46 "Ben Bauer" wrote: > > > http://www.comtronic.ca/cci/home.php?do=ShowProducts&cmd=detail&cid=NB&pid=017133 > > CPU ARM Cortex-A9 1.0GHz Single Core > GPU Mali-400, with 3D Accelerator > Memory 1GB DDR3 > Storage 4GB NAND Flash > Display 7" TFT-LCD > ... > I/O Ports 1 x Micro USB 2.0 Port > 1 x Mini HDMI Port > 1 x TF Card Slot > 1 x Power Port > > Does anyone have experience with this (or similar hardware)? > I am hoping to put Slackware native on this and move over some > python programs (currently prototyped on an Atom processor) > that I have written for classroom use ( audience response > system, multiple choice testing, flashcards etc). I am a Slacker > since 1994 but ARM is new to me. Naive questions: > > 1) any chance I can boot from CF card ? > 2) if so, is a USB keyboard likely to autodetect? > 3) would X be mulitouch or single? > 4) is there a better/easier sub $100 device I should consider? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > 4) Yes, consider using a raspberry pi, it is under $100 and runs > slackwarearm debian arch and more. The raspberriy pi is a neat little arm > computer that runs from CF card. It's not a tablet but can connect to tv's > monitors and hdtv's.it needs a 5 volt 1 amp psu has no moving parts and > no fan and yes it is ARM! > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Mon Apr 15 20:33:59 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Mon, 15 Apr 2013 21:33:59 +0100 Subject: [ARMedslack] Avatar S701-R2A-1 Sirius 7" Tablet In-Reply-To: <20130415154637.27cb07df@woad.local.net> References: <20130415154637.27cb07df@woad.local.net> Message-ID: Looking at the specs I wouldn't pay more than $40 for that device and in general anything less than $150 is rubbish (but I paid only ?80 for my Samsung Player and hardware-wise it's ok). If you want a Linux ready tablet go for the Pengpod, but honestly I'm no fan of the Allwinner A10 and due yo no UK based vendor I'll pass on it. With regards to native Slackware on tablets, I've asked this questions both here and on LQ, the reception has been negative. On Apr 15, 2013 8:47 PM, "Ben Bauer" wrote: > > http://www.comtronic.ca/cci/home.php?do=ShowProducts&cmd=detail&cid=NB&pid=017133 > > CPU ARM Cortex-A9 1.0GHz Single Core > GPU Mali-400, with 3D Accelerator > Memory 1GB DDR3 > Storage 4GB NAND Flash > Display 7" TFT-LCD > ... > I/O Ports 1 x Micro USB 2.0 Port > 1 x Mini HDMI Port > 1 x TF Card Slot > 1 x Power Port > > Does anyone have experience with this (or similar hardware)? > I am hoping to put Slackware native on this and move over some > python programs (currently prototyped on an Atom processor) > that I have written for classroom use ( audience response > system, multiple choice testing, flashcards etc). I am a Slacker > since 1994 but ARM is new to me. Naive questions: > > 1) any chance I can boot from CF card ? > 2) if so, is a USB keyboard likely to autodetect? > 3) would X be mulitouch or single? > 4) is there a better/easier sub $100 device I should consider? > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Apr 16 15:20:26 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 16 Apr 2013 16:20:26 +0100 (BST) Subject: [ARMedslack] miniroot 14 and current: vi is broken In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> Well actually on my live slackware 14 (x86)? vi is a link to elvis Although both are installed, by default vi is linked to elvis (and it's not something I did manually). PACKAGE NAME:???? vim-7.3.645-i486-1 COMPRESSED PACKAGE SIZE:???? 5.2M UNCOMPRESSED PACKAGE SIZE:???? 24M PACKAGE LOCATION: /var/log/mount/slackware/ap/vim-7.3.645-i486-1.txz PACKAGE NAME:???? elvis-2.2_0-i486-2 COMPRESSED PACKAGE SIZE:???? 655.0K UNCOMPRESSED PACKAGE SIZE:???? 2.6M PACKAGE LOCATION: /var/log/mount/slackware/a/elvis-2.2_0-i486-2.txz looking at the sizes I cannot but agree that on the miniroot vim is just eating up space (just guessing that the arm packages will me more or less the same size) and on top of that there's 120Mb of dependencies to use it ! I remover the unused dependencies and added in elvis saving some 120Mb of disk space on the miniroot. Bye David ________________________________ Da: Stuart Winter A: Slackware ARM port Inviato: Luned? 15 Aprile 2013 17:52 Oggetto: Re: [ARMedslack] miniroot 14 and current: vi is broken On Mon, 15 Apr 2013, Davide wrote: > I noticed that in the miniroot, both current and 14, vi? is broken looking for libperl and libpython . > I know most of you will like to use nano ... but I'm an old fart and I still like vi !!! Hmm.? I'm going to replace vim with elvis as this works without bundling additional packages. -- Stuart Winter Slackware ARM: http://arm.slackware.com _______________________________________________ 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 Tue Apr 16 15:34:08 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 16 Apr 2013 16:34:08 +0100 (BST) Subject: [ARMedslack] miniroot 14 and current: vi is broken In-Reply-To: <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: On Tue, 16 Apr 2013, Davide wrote: > Well actually on my live slackware 14 (x86)? vi is a link to elvis > > Although both are installed, by default vi is linked to elvis (and it's > not something I did manually). looking at the sizes I cannot but agree > that on the miniroot vim is just eating up space (just guessing that the > arm packages will me more or less the same size) and on top of that > there's 120Mb of dependencies to use it ! [..] Since (if selected) elvis is installed first (due to being in series 'a'), it sets up a symlink in the doinst.sh script. If vim is installed, its doinst.sh script checks for the presence of the 'vi' symlink, and if not present, will symlink 'vi' to 'vim'. root at pepa:~/ac/source/a/elvis# head -n2 /var/log/scripts/elvis-2.2-arm-2 ( cd usr/bin ; rm -rf vi ) ( cd usr/bin ; ln -sf elvis vi ) root at pepa:~/ac/source/a/elvis# From louigi600 at yahoo.it Wed Apr 17 14:01:10 2013 From: louigi600 at yahoo.it (Davide) Date: Wed, 17 Apr 2013 15:01:10 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> I'ts been a while since I last fiddled with the seagate dockstar ... I puklled it back out wanting to involve it on media streaming via DLNA. I fiddled with a slackwarearm 14 miniroot image on a versatile emulated machine untill I thaught I had all the bits and pieces needed to boot from the dockstar ... but when I put the image on usb stick this is all I'm getting: Loading file "/boot/uImage" from usb device 0:1 (usbda1) 2343448 bytes read Loading file "/boot/uinitrd" from usb device 0:1 (usbda1) 7314743 bytes read USB device 0:1 is bootable ## Booting kernel from Legacy Image at 00800000 ... ?? Image Name:?? Linux-3.8.7-kirkwood ?? Image Type:?? ARM Linux Kernel Image (uncompressed) ?? Data Size:??? 2343384 Bytes = 2.2 MiB ?? Load Address: 00008000 ?? Entry Point:? 00008000 ?? Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... ?? Image Name:?? Slackware ARM for kirkwood platf ?? Image Type:?? ARM Linux RAMDisk Image (gzip compressed) ?? Data Size:??? 7314679 Bytes = 7 MiB ?? Load Address: 00000000 ?? Entry Point:? 00000000 ?? Verifying Checksum ... OK ?? Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. And that's it ... nothing more on the serial console and nothing on the network .... actually it does not even appear to mount the root filesystem as the last mount seems to be coherent with the last time I mounted it on my PC Do I need to recompile the kernel (I'm using the kirkwood uImage) or is there something else wrong ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Wed Apr 17 14:12:53 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Wed, 17 Apr 2013 10:12:53 -0400 Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: On Wed, Apr 17, 2013 at 10:01 AM, Davide wrote: > > I'ts been a while since I last fiddled with the seagate dockstar ... I > puklled it back out wanting to involve it on media streaming via DLNA. > I fiddled with a slackwarearm 14 miniroot image on a versatile emulated > machine untill I thaught I had all the bits and pieces needed to boot from > the dockstar ... but when I put the image on usb stick this is all I'm > getting: > > Loading file "/boot/uImage" from usb device 0:1 (usbda1) > 2343448 bytes read > Loading file "/boot/uinitrd" from usb device 0:1 (usbda1) > 7314743 bytes read > USB device 0:1 is bootable > ## Booting kernel from Legacy Image at 00800000 ... > Image Name: Linux-3.8.7-kirkwood > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2343384 Bytes = 2.2 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at 01100000 ... > Image Name: Slackware ARM for kirkwood platf > Image Type: ARM Linux RAMDisk Image (gzip compressed) > Data Size: 7314679 Bytes = 7 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > And that's it ... nothing more on the serial console and nothing on the > network .... actually it does not even appear to mount the root filesystem > as the last mount seems to be coherent with the last time I mounted it on my > PC > Do I need to recompile the kernel (I'm using the kirkwood uImage) or is > there something else wrong ? > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Hello! Probably. But we need more information. How did you collect the information that you've shown us? How is your system (if that term can be applied) configured? Including how did you connect its serial console? I have one here, about all I did was pop off its housing and study the internals. My other problems were along the lines of setting the boot blocks to boot from an attached USB key. Currently I'm running my activities on a plain black pogoplug. Who has an 8Gig key attached, and one of those portable external drives attached sized 80 Gig and formatted as FAT32. I originally had plans to, do stuff with either via the USB ports but not as if either were wearing drives with stuff on them, but doing something specific. I still want to, ah, target my Dock Star but the difficult part is to workout how to attach that serial console and without damaging things. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From dhm at mersenne.com Wed Apr 17 14:17:16 2013 From: dhm at mersenne.com (David Madden) Date: Wed, 17 Apr 2013 07:17:16 -0700 Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <516EAEEC.8090604@mersenne.com> On 4/17/2013 07:12, Gregg Levine wrote: > I still want to, ah, target my Dock Star but the difficult part is to > workout how to attach that serial console and without damaging things. It's a plain ol' TTL UART on a slightly-small pin block just to the left of the front edge of the PCB (left of the LED). You can find pinout pictures on the 'net, but I have mine marked as: o o o o o o o Rx Tx Gnd (LED) -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 1500 SW First Ave. ? Suite 1170 ? Portland, Oregon 97201 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4003 bytes Desc: S/MIME Cryptographic Signature URL: From m-lists at biscuit.org.uk Wed Apr 17 14:46:44 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 17 Apr 2013 15:46:44 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: > Uncompressing Linux... done, booting the kernel. > > And that's it ... nothing more on the serial console and nothing on the > network .... actually it does not even appear to mount the root > filesystem as the last mount seems to be coherent with the last time I > mounted it on my PC Do I need to recompile the kernel (I'm using the > kirkwood uImage) or is there something else wrong ? This usually happens when the kernel +initrd does not fit into the allocated memory locations. Make sure you have the u-boot memory settings correctly set: Marvell>> tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img Marvell>> tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood Marvell>> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw Marvell>> bootm 0x00800000 0x01100000 I haven't tried the latest Kirkwood kernel on a Plug machine, but I know it does work on the OpenRD client. I added the 'earlyprintk' debugging to the Tegra20 kernel which'd show you what was wrong, but I don't think this is available in the kirkwood implementation (although I'll have a look again later). -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Wed Apr 17 14:53:39 2013 From: louigi600 at yahoo.it (Davide) Date: Wed, 17 Apr 2013 15:53:39 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1366210419.70087.YahooMailNeo@web28803.mail.ir2.yahoo.com> >> >> I'ts been a while since I last fiddled with the seagate dockstar ... I >> puklled it back out wanting to involve it on media streaming via DLNA. >> I fiddled with a slackwarearm 14 miniroot image on a versatile emulated >> machine untill I thaught I had all the bits and pieces needed to boot from >> the dockstar ... but when I put the image on usb stick this is all I'm >> getting: >> >> Loading file "/boot/uImage" from usb device 0:1 (usbda1) >> 2343448 bytes read >> Loading file "/boot/uinitrd" from usb device 0:1 (usbda1) >> 7314743 bytes read >> USB device 0:1 is bootable >> ## Booting kernel from Legacy Image at 00800000 ... >>? ? Image Name:? Linux-3.8.7-kirkwood >>? ? Image Type:? ARM Linux Kernel Image (uncompressed) >>? ? Data Size:? ? 2343384 Bytes = 2.2 MiB >>? ? Load Address: 00008000 >>? ? Entry Point:? 00008000 >>? ? Verifying Checksum ... OK >> ## Loading init Ramdisk from Legacy Image at 01100000 ... >>? ? Image Name:? Slackware ARM for kirkwood platf >>? ? Image Type:? ARM Linux RAMDisk Image (gzip compressed) >>? ? Data Size:? ? 7314679 Bytes = 7 MiB >>? ? Load Address: 00000000 >>? ? Entry Point:? 00000000 >>? ? Verifying Checksum ... OK >>? ? Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> >> And that's it ... nothing more on the serial console and nothing on the >> network .... actually it does not even appear to mount the root filesystem >> as the last mount seems to be coherent with the last time I mounted it on my >> PC >> Do I need to recompile the kernel (I'm using the kirkwood uImage) or is >> there something else wrong ? > >Hello! >Probably. But we need more information. How did you collect the >information that you've shown us? How is your system (if that term can >be applied) configured? Including how did you connect its serial >console? Seial via a modified DKU-5 cable and use minicom to manage that. The console is connected right and I can use it if I boot into the old image I burned into the internal flash .... but that old system is too crippled to do the streaming stuff !!!! >I have one here, about all I did was pop off its housing and study the >internals. My other problems were along the lines of setting the boot >blocks to boot from an attached USB key. The custom uboot scripts I'm using can boot ok from a USB stick provided you put the images in the right place so uboot can find them ... and as you can see they are found and loaded. I even tested that all was ok by booting from a clashNG image on the usb stick too and it boots ok. >Currently I'm running my activities on a plain black pogoplug. Who has >an 8Gig key attached, and one of those portable external drives >attached sized 80 Gig and formatted as FAT32. >I originally had plans to, do stuff with either via the USB ports but >not as if either were wearing drives with stuff on them, but doing >something specific. >I still want to, ah, target my Dock Star but the difficult part is to >workout how to attach that serial console and without damaging things. Buy a DKU-5 compatible cell Phone cable it has the required voltage serial port interface for the dockstar (and may more devices) ... you will just need to tut off the phone plug and wire up an old 2.5" hdu conenctor to the cable so that you can plug it into the dockstar. I think I mention how I did that on the clashNG project If you want a readymade woking image for the dockstar have a look at bclash on sourceforge ... it's unmaintained over the last 2 years but it still boots from my onboard flash on the dockstar. ? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Wed Apr 17 15:15:51 2013 From: louigi600 at yahoo.it (Davide) Date: Wed, 17 Apr 2013 16:15:51 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> >> Uncompressing Linux... done, booting the kernel. >> >> And that's it ... nothing more on the serial console and nothing on the >> network .... actually it does not even appear to mount the root >> filesystem as the last mount seems to be coherent with the last time I >> mounted it on my PC Do I need to recompile the kernel (I'm using the >> kirkwood uImage) or is there something else wrong ? >This usually happens when the kernel +initrd does not fit into the >allocated memory locations.? Make sure you have the u-boot memory settings >correctly set: >? ? Marvell>>? tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img >? ? Marvell>>? tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood >? ? Marvell>>? setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw >? ? Marvell>>? bootm 0x00800000 0x01100000 >I haven't tried the latest Kirkwood kernel on a Plug machine, but I know >it does work on the OpenRD client.? I added the 'earlyprintk' debugging to >the Tegra20 kernel which'd show you what was wrong, but I don't think this >is available in the kirkwood implementation (although I'll have a look >again later). O possibly the sizes matched what i was using 2 years back ... might nit fit the new images I've lost familiarity with uboot command line .... I load them from usb with something that looks like this: ${dev} $part ${usb_boot_dir} get populated somewhere along the execution of the script ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd setenv usb_boot_address 0x800000 0x1100000 bootm $usb_boot_address but they do look as if they are ok .... The images got into /boot when by installing the packages from the versatile virtual machine (I then manually linked with the correct names my uboot looks for) root at darkstar:/mnt/floppy/boot# ls System.map@???????????????? config-kirkwood-3.4.11? uImage-kirkwood-3.4.11? uinitrd-kirkwood-3.4.11 System.map-kirkwood-3.4.11? uImage@???????????????? uinitrd@ root at darkstar:/mnt/floppy/boot#? md5sum uinitrd-kirkwood-3.4.11 uImage-kirkwood-3.4.11 0ff11c800fa6745b04676787596246de? uinitrd-kirkwood-3.4.11 0c5e9a376a92e49863e2989875564a12? uImage-kirkwood-3.4.11 root at darkstar:/mnt/floppy/boot# so I'm supposing that it's not an issue on how they got into the image. anyway just incase anyone is intrested on the script I'm using for booting from usb stick if present (and correctly setup) or from internal flash here's a dump of printenv: Marvell>> printenv usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdids=nand0=orion_nand partition=nand0,2 led_init=green blinking led_exit=green off led_error=orange blinking ethact=egiga0 arcNumber=2998 usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part} usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part} usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part} usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part} usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part} usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part} usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part} set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro ${root_fstype} mtdparts=mtdparts=orion_nand:1M(u-boot),4M at 1M(uImage),32M at 5M(rootfs),219M at 37M(data) root_fs=root=/dev/mtdblock2 root_fstype=rootfstype=jffs2 bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel ethaddr=00:10:75:1A:21:B7 usb_part_list=4 3 2 1 usb_dev_list=6 5 4 3 2 1 0 usb_dev_part=0 usb_scan=usb start; setenv usb_boot_dev none; for dev in? $usb_dev_list; do for part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv usb_boot_dir; ext2ls usb ${dev}:$part /boot && setenv usb_boot_dir /boot; if ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv usb_boot_address 0x800000; setenv root_fstype rootfstype=ext2; run usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd; && setenv usb_boot_address 0x800000 0x1100000; fi; done; done; if test "$usb_boot_dev" = "none"; then echo "No USB bootable device found"; else echo "USB device ${usb_boot_dev}:$usb_dev_part is bootable"; bootm $usb_boot_address; fi; flash_root_fstype=rootfstype=jffs2 flash_kernel_size=0x300000 flash_kernel_load_addr=0x6400000 set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} ro ${flash_root_fstype} boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest $flash_kernel_size; bootm $flash_kernel_load_addr flash_root_fs=root=/dev/mtdblock2 flash_kernel_offest=0x100000 stdin=serial stdout=serial stderr=serial -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Thu Apr 18 01:32:22 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Wed, 17 Apr 2013 21:32:22 -0400 Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <516F4D26.8070509@laprjns.com> Maybe you need a new uboot : http://forum.doozan.com/read.php?3,6965oot I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS. All three are running Slackwarearm 14.0 I also use these for my serial connection. http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0&_nkw=USB+2.0+to+TTL+UART&_sacat=0&_from=R40 root at pogo-161:/home/rich# uname -a Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux root at pogo-161:/home/rich# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done usb_scan_list=1 2 3 4 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_init=run usb_scan usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset ethaddr=00:25:31:xx:xx:xx arcNumber=2097 ipaddr=192.168.1.161 if_netconsole=ping $serverip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; preboot=run if_netconsole start_netconsole serverip=192.168.1.71 set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_pogo=run bootcmd_rescue rescue_installed=1 force_rescue=0 usb_custom_params=nic=auto:eth0:dhcp kbd=us Regards Rich Lapointe On 04/17/2013 11:15 AM, Davide wrote: >> Uncompressing Linux... done, booting the kernel. >> >> And that's it ... nothing more on the serial console and nothing on the >> network .... actually it does not even appear to mount the root >> filesystem as the last mount seems to be coherent with the last time I >> mounted it on my PC Do I need to recompile the kernel (I'm using the >> kirkwood uImage) or is there something else wrong ? >This usually happens when the kernel +initrd does not fit into the >allocated memory locations. Make sure you have the u-boot memory settings >correctly set: > Marvell>> tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img > Marvell>> tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood > Marvell>> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw > Marvell>> bootm 0x00800000 0x01100000 >I haven't tried the latest Kirkwood kernel on a Plug machine, but I know >it does work on the OpenRD client. I added the 'earlyprintk' debugging to >the Tegra20 kernel which'd show you what was wrong, but I don't think this >is available in the kirkwood implementation (although I'll have a look >again later). O possibly the sizes matched what i was using 2 years back ... might nit fit the new images I've lost familiarity with uboot command line .... I load them from usb with something that looks like this: ${dev} $part ${usb_boot_dir} get populated somewhere along the execution of the script ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd setenv usb_boot_address 0x800000 0x1100000 bootm $usb_boot_address but they do look as if they are ok .... The images got into /boot when by installing the packages from the versatile virtual machine (I then manually linked with the correct names my uboot looks for) root at darkstar:/mnt/floppy/boot# ls System.map@ config-kirkwood-3.4.11 uImage-kirkwood-3.4.11 uinitrd-kirkwood-3.4.11 System.map-kirkwood-3.4.11 uImage@ uinitrd@ root at darkstar:/mnt/floppy/boot# md5sum uinitrd-kirkwood-3.4.11 uImage-kirkwood-3.4.11 0ff11c800fa6745b04676787596246de uinitrd-kirkwood-3.4.11 0c5e9a376a92e49863e2989875564a12 uImage-kirkwood-3.4.11 root at darkstar:/mnt/floppy/boot# so I'm supposing that it's not an issue on how they got into the image. anyway just incase anyone is intrested on the script I'm using for booting from usb stick if present (and correctly setup) or from internal flash here's a dump of printenv: Marvell>> printenv usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdids=nand0=orion_nand partition=nand0,2 led_init=green blinking led_exit=green off led_error=orange blinking ethact=egiga0 arcNumber=2998 usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part} usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part} usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part} usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part} usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part} usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part} usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part} set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro ${root_fstype} mtdparts=mtdparts=orion_nand:1M(u-boot),4M at 1M(uImage),32M at 5M(rootfs),219M at 37M(data) root_fs=root=/dev/mtdblock2 root_fstype=rootfstype=jffs2 bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel ethaddr=00:10:75:1A:21:B7 usb_part_list=4 3 2 1 usb_dev_list=6 5 4 3 2 1 0 usb_dev_part=0 usb_scan=usb start; setenv usb_boot_dev none; for dev in $usb_dev_list; do for part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv usb_boot_dir; ext2ls usb ${dev}:$part /boot && setenv usb_boot_dir /boot; if ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv usb_boot_address 0x800000; setenv root_fstype rootfstype=ext2; run usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd; && setenv usb_boot_address 0x800000 0x1100000; fi; done; done; if test "$usb_boot_dev" = "none"; then echo "No USB bootable device found"; else echo "USB device ${usb_boot_dev}:$usb_dev_part is bootable"; bootm $usb_boot_address; fi; flash_root_fstype=rootfstype=jffs2 flash_kernel_size=0x300000 flash_kernel_load_addr=0x6400000 set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} ro ${flash_root_fstype} boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest $flash_kernel_size; bootm $flash_kernel_load_addr flash_root_fs=root=/dev/mtdblock2 flash_kernel_offest=0x100000 stdin=serial stdout=serial stderr=serial > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Thu Apr 18 02:00:09 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Wed, 17 Apr 2013 22:00:09 -0400 Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <516F4D26.8070509@laprjns.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> Message-ID: On Wed, Apr 17, 2013 at 9:32 PM, Richard Lapointe wrote: > Maybe you need a new uboot : > http://forum.doozan.com/read.php?3,6965oot > > I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS. > All three are running Slackwarearm 14.0 > > I also use these for my serial connection. > http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0&_nkw=USB+2.0+to+TTL+UART&_sacat=0&_from=R40 > > > root at pogo-161:/home/rich# uname -a > Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 > armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board > GNU/Linux > > root at pogo-161:/home/rich# fw_printenv > ethact=egiga0 > bootdelay=3 > baudrate=115200 > mainlineLinux=yes > console=ttyS0,115200 > > led_init=green blinking > led_exit=green off > led_error=orange blinking > mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) > mtdids=nand0=orion_nand > partition=nand0,2 > stdin=serial > stdout=serial > stderr=serial > rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 > root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params > rescue_bootcmd=if test $rescue_installed -eq 1; then run > rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; > else run pogo_bootcmd; fi > pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi > force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 > 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run > rescue_bootcmd; fi > ubifs_mtd=3 > ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd > root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params > ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs > && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; > then bootm 0x800000 0x1100000; fi > usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; > if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; > then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv > usb_device $usb; setenv usb_root /dev/$dev; fi; done > usb_scan_list=1 2 3 4 > usb_scan_1=usb=0:1 dev=sda1 > usb_scan_2=usb=1:1 dev=sdb1 > usb_scan_3=usb=2:1 dev=sdc1 > usb_scan_4=usb=3:1 dev=sdd1 > usb_init=run usb_scan > > usb_device=0:1 > usb_root=/dev/sda1 > usb_rootfstype=ext2 > usb_rootdelay=10 > usb_set_bootargs=setenv bootargs console=$console root=$usb_root > rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts > $usb_custom_params > usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot > usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if > ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 > 0x1100000; else bootm 0x800000; fi > bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run > usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset > ethaddr=00:25:31:xx:xx:xx > arcNumber=2097 > ipaddr=192.168.1.161 > if_netconsole=ping $serverip > start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin > nc; setenv stdout nc; setenv stderr nc; version; > preboot=run if_netconsole start_netconsole > serverip=192.168.1.71 > set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 > root=ubi0:rootfs ro rootfstype=ubifs $mtdparts > bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 > 0x400000; bootm 0x800000 > bootcmd_pogo=run bootcmd_rescue > rescue_installed=1 > force_rescue=0 > usb_custom_params=nic=auto:eth0:dhcp kbd=us > > > Regards > > Rich Lapointe > > > > On 04/17/2013 11:15 AM, Davide wrote: >>> Uncompressing Linux... done, booting the kernel. >>> >>> And that's it ... nothing more on the serial console and nothing on the >>> network .... actually it does not even appear to mount the root >>> filesystem as the last mount seems to be coherent with the last time I >>> mounted it on my PC Do I need to recompile the kernel (I'm using the >>> kirkwood uImage) or is there something else wrong ? > >>This usually happens when the kernel +initrd does not fit into the >>allocated memory locations. Make sure you have the u-boot memory settings >>correctly set: > >> Marvell>> tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img >> Marvell>> tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood >> Marvell>> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk >> root=/dev/ram rw >> Marvell>> bootm 0x00800000 0x01100000 > >>I haven't tried the latest Kirkwood kernel on a Plug machine, but I know >>it does work on the OpenRD client. I added the 'earlyprintk' debugging to >>the Tegra20 kernel which'd show you what was wrong, but I don't think this >>is available in the kirkwood implementation (although I'll have a look >>again later). > > O possibly the sizes matched what i was using 2 years back ... might nit fit > the new images > I've lost familiarity with uboot command line .... > I load them from usb with something that looks like this: > > ${dev} > $part > ${usb_boot_dir} > get populated somewhere along the execution of the script > > ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage > ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd > setenv usb_boot_address 0x800000 0x1100000 > bootm $usb_boot_address > > but they do look as if they are ok .... > > The images got into /boot when by installing the packages from the versatile > virtual machine (I then manually linked with the correct names my uboot > looks for) > root at darkstar:/mnt/floppy/boot# ls > System.map@ config-kirkwood-3.4.11 uImage-kirkwood-3.4.11 > uinitrd-kirkwood-3.4.11 > System.map-kirkwood-3.4.11 uImage@ uinitrd@ > root at darkstar:/mnt/floppy/boot# md5sum uinitrd-kirkwood-3.4.11 > uImage-kirkwood-3.4.11 > 0ff11c800fa6745b04676787596246de uinitrd-kirkwood-3.4.11 > 0c5e9a376a92e49863e2989875564a12 uImage-kirkwood-3.4.11 > root at darkstar:/mnt/floppy/boot# > > so I'm supposing that it's not an issue on how they got into the image. > > anyway just incase anyone is intrested on the script I'm using for booting > from usb stick if present (and correctly setup) or from internal flash > here's a dump of printenv: > Marvell>> printenv > usb_device=0:1 > usb_root=/dev/sda1 > usb_rootfstype=ext2 > usb_rootdelay=10 > bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200 > bootdelay=3 > baudrate=115200 > console=console=ttyS0,115200 > mtdids=nand0=orion_nand > partition=nand0,2 > led_init=green blinking > led_exit=green off > led_error=orange blinking > ethact=egiga0 > arcNumber=2998 > usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part} > usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part} > usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part} > usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part} > usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part} > usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part} > usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part} > set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro > ${root_fstype} > mtdparts=mtdparts=orion_nand:1M(u-boot),4M at 1M(uImage),32M at 5M(rootfs),219M at 37M(data) > root_fs=root=/dev/mtdblock2 > root_fstype=rootfstype=jffs2 > bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel > ethaddr=00:10:75:1A:21:B7 > usb_part_list=4 3 2 1 > usb_dev_list=6 5 4 3 2 1 0 > usb_dev_part=0 > usb_scan=usb start; setenv usb_boot_dev none; for dev in $usb_dev_list; do > for part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv > usb_boot_dir; ext2ls usb ${dev}:$part /boot && setenv usb_boot_dir /boot; if > ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} > /uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv > usb_boot_address 0x800000; setenv root_fstype rootfstype=ext2; run > usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part > 0x1100000 ${usb_boot_dir}/uinitrd; && setenv usb_boot_address > 0x800000 0x1100000; fi; done; done; if test "$usb_boot_dev" = "none"; then > echo "No USB bootable device found"; else echo "USB device > ${usb_boot_dev}:$usb_dev_part is bootable"; bootm $usb_boot_address; fi; > flash_root_fstype=rootfstype=jffs2 > flash_kernel_size=0x300000 > flash_kernel_load_addr=0x6400000 > set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} > ro ${flash_root_fstype} > boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest > $flash_kernel_size; bootm $flash_kernel_load_addr > flash_root_fs=root=/dev/mtdblock2 > flash_kernel_offest=0x100000 > stdin=serial > stdout=serial > stderr=serial Hello! Makes sense. However I've already decided what my plans are for adding a serial port to mine. As it happens I have here a breakout board for the FT232R (Or FT232RL) device. So that's what I'll be using. As for the other ideas. Time will tell. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From louigi600 at yahoo.it Thu Apr 18 06:48:46 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 07:48:46 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <516F4D26.8070509@laprjns.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> Message-ID: <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> The old uboot image instalelt over 2 years ago on my dockstar was a Jeff Doozan image with a modified environment ... and it still boots 2.6 kernels that I was using at the time (not sure if I ever got round to diddling with 3.x kernels on my dockstar but I'll check asap). Did Doozan's uboot images brake somwhere along the kernel developement line? from 2.6.38 to 3.4 ? This is a live clashNG environment running from internal flash on my dockstar: root at surap:~# cat /proc/cpuinfo Processor?????? : Feroceon 88FR131 rev 1 (v5l) BogoMIPS??????? : 1192.75 Features??????? : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant???? : 0x2 CPU part??????? : 0x131 CPU revision??? : 1 Hardware??????? : Seagate FreeAgent DockStar Revision??????? : 0000 Serial????????? : 0000000000000000 root at surap:~# uname -a Linux surap 2.6.38.3-kirkwood #2 PREEMPT Fri Apr 15 22:36:21 BST 2011 armv5tel GNU/Linux root at surap:~# And this is a live armedslack 13.37 running from that same dockstar and booting from a usb stick: root at slackware:~# cat /etc/slackware-version Slackware 13.37.0 root at slackware:~# uname -a Linux slackware 2.6.38.7-kirkwood #1 PREEMPT Thu May 26 08:29:19 BST 2011 armv5tel Feroceon 88FR131x root at slackware:~# cat /proc/cpuinfo Processor?????? : Feroceon 88FR131 rev 1 (v5l) BogoMIPS??????? : 1192.75 Features??????? : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant???? : 0x2 CPU part??????? : 0x131 CPU revision??? : 1 Hardware??????? : Seagate FreeAgent DockStar Revision??????? : 0000 Serial????????? : 0000000000000000 root at slackware:~# df -m Filesystem?????????? 1M-blocks????? Used Available Use% Mounted on /dev/sda2???????????????? 7483????? 3463????? 4020? 47% / root at slackware:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100 root at slackware:~# So I'm pretty much sure that the u-boot setup is ok ... just happens that for some reason I'm unable to boot the new 3.4.... kirkwood kernel. Yeah I got a couple of DKU-5 compatible cables from an ebay user (I forgot the details since it was 2 years ago) and i recall that for? something like 5 Euro I had them both shipped to my door. Doing enbedded stuff without at least a serial cable suitable for the target platform is difficult to say the least ... at some stage I plan to start using jtag too ;) ________________________________ Da: Richard Lapointe A: Davide ; Slackware ARM port Inviato: Gioved? 18 Aprile 2013 3:32 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Maybe you need a new uboot : http://forum.doozan.com/read.php?3,6965oot I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS.? All three are running Slackwarearm 14.0 I also use these for my serial connection.? http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0&_nkw=USB+2.0+to+TTL+UART&_sacat=0&_from=R40 root at pogo-161:/home/rich# uname -a Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux root at pogo-161:/home/rich# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done usb_scan_list=1 2 3 4 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_init=run usb_scan usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset ethaddr=00:25:31:xx:xx:xx arcNumber=2097 ipaddr=192.168.1.161 if_netconsole=ping $serverip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; preboot=run if_netconsole start_netconsole serverip=192.168.1.71 set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_pogo=run bootcmd_rescue rescue_installed=1 force_rescue=0 usb_custom_params=nic=auto:eth0:dhcp kbd=us Regards Rich Lapointe On 04/17/2013 11:15 AM, Davide wrote: >> Uncompressing Linux... done, booting the kernel. >> >> And that's it ... nothing more on the serial console and nothing on the >> network .... actually it does not even appear to mount the root >> filesystem as the last mount seems to be coherent with the last time I >> mounted it on my PC Do I need to recompile the kernel (I'm using the >> kirkwood uImage) or is there something else wrong ? >This usually happens when the kernel +initrd does not fit into the >allocated memory locations.? Make sure you have the u-boot memory settings >correctly set: >? ? Marvell>>? tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img >? ? Marvell>>? tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood >? ? Marvell>>? setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw >? ? Marvell>>? bootm 0x00800000 0x01100000 >I haven't tried the latest Kirkwood kernel on a Plug machine, but I know >it does work on the OpenRD client.? I added the 'earlyprintk' debugging to >the Tegra20 kernel which'd show you what was wrong, but I don't think this >is available in the kirkwood implementation (although I'll have a look >again later). O possibly the sizes matched what i was using 2 years back ... might nit fit the new images I've lost familiarity with uboot command line .... I load them from usb with something that looks like this: ${dev} $part ${usb_boot_dir} get populated somewhere along the execution of the script ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd setenv usb_boot_address 0x800000 0x1100000 bootm $usb_boot_address but they do look as if they are ok .... The images got into /boot when by installing the packages from the versatile virtual machine (I then manually linked with the correct names my uboot looks for) root at darkstar:/mnt/floppy/boot# ls System.map@???????????????? config-kirkwood-3.4.11? uImage-kirkwood-3.4.11? uinitrd-kirkwood-3.4.11 System.map-kirkwood-3.4.11? uImage@???????????????? uinitrd@ root at darkstar:/mnt/floppy/boot#? md5sum uinitrd-kirkwood-3.4.11 uImage-kirkwood-3.4.11 0ff11c800fa6745b04676787596246de? uinitrd-kirkwood-3.4.11 0c5e9a376a92e49863e2989875564a12? uImage-kirkwood-3.4.11 root at darkstar:/mnt/floppy/boot# so I'm supposing that it's not an issue on how they got into the image. anyway just incase anyone is intrested on the script I'm using for booting from usb stick if present (and correctly setup) or from internal flash here's a dump of printenv: Marvell>> printenv usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdids=nand0=orion_nand partition=nand0,2 led_init=green blinking led_exit=green off led_error=orange blinking ethact=egiga0 arcNumber=2998 usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part} usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part} usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part} usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part} usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part} usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part} usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part} set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro ${root_fstype} mtdparts=mtdparts=orion_nand:1M(u-boot),4M at 1M(uImage),32M at 5M(rootfs),219M at 37M(data) root_fs=root=/dev/mtdblock2 root_fstype=rootfstype=jffs2 bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel ethaddr=00:10:75:1A:21:B7 usb_part_list=4 3 2 1 usb_dev_list=6 5 4 3 2 1 0 usb_dev_part=0 usb_scan=usb start; setenv usb_boot_dev none; for dev in? $usb_dev_list; do for part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv usb_boot_dir; ext2ls usb ${dev}:$part /boot && setenv usb_boot_dir /boot; if ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv usb_boot_address 0x800000; setenv root_fstype rootfstype=ext2; run usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd; && setenv usb_boot_address 0x800000 0x1100000; fi; done; done; if test "$usb_boot_dev" = "none"; then echo "No USB bootable device found"; else echo "USB device ${usb_boot_dev}:$usb_dev_part is bootable"; bootm $usb_boot_address; fi; flash_root_fstype=rootfstype=jffs2 flash_kernel_size=0x300000 flash_kernel_load_addr=0x6400000 set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} ro ${flash_root_fstype} boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest $flash_kernel_size; bootm $flash_kernel_load_addr flash_root_fs=root=/dev/mtdblock2 flash_kernel_offest=0x100000 stdin=serial stdout=serial stderr=serial > > >_______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Apr 18 08:37:22 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 09:37:22 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> Ok I had a read on Jeffs uboot page and: "Kernel 3.2.y introduced a default setting for the kernel that affects kirkwood machines in particular, because of an unintended u-boot behavior with regard to the Level2Cache and decompression of the kernel image. Call it a latent bug in u-boot, a regression in the kernel, or whatever... the defconfig kirkwood kernel build of 3.2.y (and by extension, higher versions) will fail to boot in most/many cases." So I updated the uboot image with the install script (I did it by hand the first time around and I;ll savemyself the trouble if possible) and nor the kernel gets loaded properly. I still have an issue concerning that the root filesystem on the usb stick is ext2 while the slackware arm 14 initrd is looking to mount an ext3 filesystem. I think I can fix that by remaking my usb stick image or by repackaging the initrd with the correct fstype ... maybe I just need to recheck how I pass boot parameters to kernel from uboot when I detect a valid usb stick ! Regards David ________________________________ Da: Davide A: Richard Lapointe ; Slackware ARM port Inviato: Gioved? 18 Aprile 2013 8:48 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar The old uboot image instalelt over 2 years ago on my dockstar was a Jeff Doozan image with a modified environment ... and it still boots 2.6 kernels that I was using at the time (not sure if I ever got round to diddling with 3.x kernels on my dockstar but I'll check asap). Did Doozan's uboot images brake somwhere along the kernel developement line? from 2.6.38 to 3.4 ? This is a live clashNG environment running from internal flash on my dockstar: root at surap:~# cat /proc/cpuinfo Processor?????? : Feroceon 88FR131 rev 1 (v5l) BogoMIPS??????? : 1192.75 Features??????? : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant???? : 0x2 CPU part??????? : 0x131 CPU revision??? : 1 Hardware??????? : Seagate FreeAgent DockStar Revision??????? : 0000 Serial????????? : 0000000000000000 root at surap:~# uname -a Linux surap 2.6.38.3-kirkwood #2 PREEMPT Fri Apr 15 22:36:21 BST 2011 armv5tel GNU/Linux root at surap:~# And this is a live armedslack 13.37 running from that same dockstar and booting from a usb stick: root at slackware:~# cat /etc/slackware-version Slackware 13.37.0 root at slackware:~# uname -a Linux slackware 2.6.38.7-kirkwood #1 PREEMPT Thu May 26 08:29:19 BST 2011 armv5tel Feroceon 88FR131x root at slackware:~# cat /proc/cpuinfo Processor?????? : Feroceon 88FR131 rev 1 (v5l) BogoMIPS??????? : 1192.75 Features??????? : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant???? : 0x2 CPU part??????? : 0x131 CPU revision??? : 1 Hardware??????? : Seagate FreeAgent DockStar Revision??????? : 0000 Serial????????? : 0000000000000000 root at slackware:~# df -m Filesystem?????????? 1M-blocks????? Used Available Use% Mounted on /dev/sda2???????????????? 7483????? 3463????? 4020? 47% / root at slackware:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100 root at slackware:~# So I'm pretty much sure that the u-boot setup is ok ... just happens that for some reason I'm unable to boot the new 3.4.... kirkwood kernel. Yeah I got a couple of DKU-5 compatible cables from an ebay user (I forgot the details since it was 2 years ago) and i recall that for? something like 5 Euro I had them both shipped to my door. Doing enbedded stuff without at least a serial cable suitable for the target platform is difficult to say the least ... at some stage I plan to start using jtag too ;) ________________________________ Da: Richard Lapointe A: Davide ; Slackware ARM port Inviato: Gioved? 18 Aprile 2013 3:32 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Maybe you need a new uboot : http://forum.doozan.com/read.php?3,6965oot I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS.? All three are running Slackwarearm 14.0 I also use these for my serial connection.? http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0&_nkw=USB+2.0+to+TTL+UART&_sacat=0&_from=R40 root at pogo-161:/home/rich# uname -a Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux root at pogo-161:/home/rich# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done usb_scan_list=1 2 3 4 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_init=run usb_scan usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset ethaddr=00:25:31:xx:xx:xx arcNumber=2097 ipaddr=192.168.1.161 if_netconsole=ping $serverip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; preboot=run if_netconsole start_netconsole serverip=192.168.1.71 set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_pogo=run bootcmd_rescue rescue_installed=1 force_rescue=0 usb_custom_params=nic=auto:eth0:dhcp kbd=us Regards Rich Lapointe On 04/17/2013 11:15 AM, Davide wrote: >> Uncompressing Linux... done, booting the kernel. >> >> And that's it ... nothing more on the serial console and nothing on the >> network .... actually it does not even appear to mount the root >> filesystem as the last mount seems to be coherent with the last time I >> mounted it on my PC Do I need to recompile the kernel (I'm using the >> kirkwood uImage) or is there something else wrong ? >This usually happens when the kernel +initrd does not fit into the >allocated memory locations.? Make sure you have the u-boot memory settings >correctly set: >? ? Marvell>>? tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img >? ? Marvell>>? tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood >? ? Marvell>>? setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw >? ? Marvell>>? bootm 0x00800000 0x01100000 >I haven't tried the latest Kirkwood kernel on a Plug machine, but I know >it does work on the OpenRD client.? I added the 'earlyprintk' debugging to >the Tegra20 kernel which'd show you what was wrong, but I don't think this >is available in the kirkwood implementation (although I'll have a look >again later). O possibly the sizes matched what i was using 2 years back ... might nit fit the new images I've lost familiarity with uboot command line .... I load them from usb with something that looks like this: ${dev} $part ${usb_boot_dir} get populated somewhere along the execution of the script ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd setenv usb_boot_address 0x800000 0x1100000 bootm $usb_boot_address but they do look as if they are ok .... The images got into /boot when by installing the packages from the versatile virtual machine (I then manually linked with the correct names my uboot looks for) root at darkstar:/mnt/floppy/boot# ls System.map@???????????????? config-kirkwood-3.4.11? uImage-kirkwood-3.4.11? uinitrd-kirkwood-3.4.11 System.map-kirkwood-3.4.11? uImage@???????????????? uinitrd@ root at darkstar:/mnt/floppy/boot#? md5sum uinitrd-kirkwood-3.4.11 uImage-kirkwood-3.4.11 0ff11c800fa6745b04676787596246de? uinitrd-kirkwood-3.4.11 0c5e9a376a92e49863e2989875564a12? uImage-kirkwood-3.4.11 root at darkstar:/mnt/floppy/boot# so I'm supposing that it's not an issue on how they got into the image. anyway just incase anyone is intrested on the script I'm using for booting from usb stick if present (and correctly setup) or from internal flash here's a dump of printenv: Marvell>> printenv usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdids=nand0=orion_nand partition=nand0,2 led_init=green blinking led_exit=green off led_error=orange blinking ethact=egiga0 arcNumber=2998 usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part} usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part} usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part} usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part} usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part} usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part} usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part} set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro ${root_fstype} mtdparts=mtdparts=orion_nand:1M(u-boot),4M at 1M(uImage),32M at 5M(rootfs),219M at 37M(data) root_fs=root=/dev/mtdblock2 root_fstype=rootfstype=jffs2 bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel ethaddr=00:10:75:1A:21:B7 usb_part_list=4 3 2 1 usb_dev_list=6 5 4 3 2 1 0 usb_dev_part=0 usb_scan=usb start; setenv usb_boot_dev none; for dev in? $usb_dev_list; do for part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv usb_boot_dir; ext2ls usb ${dev}:$part /boot && setenv usb_boot_dir /boot; if ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv usb_boot_address 0x800000; setenv root_fstype rootfstype=ext2; run usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd; && setenv usb_boot_address 0x800000 0x1100000; fi; done; done; if test "$usb_boot_dev" = "none"; then echo "No USB bootable device found"; else echo "USB device ${usb_boot_dev}:$usb_dev_part is bootable"; bootm $usb_boot_address; fi; flash_root_fstype=rootfstype=jffs2 flash_kernel_size=0x300000 flash_kernel_load_addr=0x6400000 set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} ro ${flash_root_fstype} boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest $flash_kernel_size; bootm $flash_kernel_load_addr flash_root_fs=root=/dev/mtdblock2 flash_kernel_offest=0x100000 stdin=serial stdout=serial stderr=serial > > >_______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Apr 18 08:37:22 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 09:37:22 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> Ok I had a read on Jeffs uboot page and: "Kernel 3.2.y introduced a default setting for the kernel that affects kirkwood machines in particular, because of an unintended u-boot behavior with regard to the Level2Cache and decompression of the kernel image. Call it a latent bug in u-boot, a regression in the kernel, or whatever... the defconfig kirkwood kernel build of 3.2.y (and by extension, higher versions) will fail to boot in most/many cases." So I updated the uboot image with the install script (I did it by hand the first time around and I;ll savemyself the trouble if possible) and nor the kernel gets loaded properly. I still have an issue concerning that the root filesystem on the usb stick is ext2 while the slackware arm 14 initrd is looking to mount an ext3 filesystem. I think I can fix that by remaking my usb stick image or by repackaging the initrd with the correct fstype ... maybe I just need to recheck how I pass boot parameters to kernel from uboot when I detect a valid usb stick ! Regards David ________________________________ Da: Davide A: Richard Lapointe ; Slackware ARM port Inviato: Gioved? 18 Aprile 2013 8:48 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar The old uboot image instalelt over 2 years ago on my dockstar was a Jeff Doozan image with a modified environment ... and it still boots 2.6 kernels that I was using at the time (not sure if I ever got round to diddling with 3.x kernels on my dockstar but I'll check asap). Did Doozan's uboot images brake somwhere along the kernel developement line? from 2.6.38 to 3.4 ? This is a live clashNG environment running from internal flash on my dockstar: root at surap:~# cat /proc/cpuinfo Processor?????? : Feroceon 88FR131 rev 1 (v5l) BogoMIPS??????? : 1192.75 Features??????? : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant???? : 0x2 CPU part??????? : 0x131 CPU revision??? : 1 Hardware??????? : Seagate FreeAgent DockStar Revision??????? : 0000 Serial????????? : 0000000000000000 root at surap:~# uname -a Linux surap 2.6.38.3-kirkwood #2 PREEMPT Fri Apr 15 22:36:21 BST 2011 armv5tel GNU/Linux root at surap:~# And this is a live armedslack 13.37 running from that same dockstar and booting from a usb stick: root at slackware:~# cat /etc/slackware-version Slackware 13.37.0 root at slackware:~# uname -a Linux slackware 2.6.38.7-kirkwood #1 PREEMPT Thu May 26 08:29:19 BST 2011 armv5tel Feroceon 88FR131x root at slackware:~# cat /proc/cpuinfo Processor?????? : Feroceon 88FR131 rev 1 (v5l) BogoMIPS??????? : 1192.75 Features??????? : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant???? : 0x2 CPU part??????? : 0x131 CPU revision??? : 1 Hardware??????? : Seagate FreeAgent DockStar Revision??????? : 0000 Serial????????? : 0000000000000000 root at slackware:~# df -m Filesystem?????????? 1M-blocks????? Used Available Use% Mounted on /dev/sda2???????????????? 7483????? 3463????? 4020? 47% / root at slackware:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100 root at slackware:~# So I'm pretty much sure that the u-boot setup is ok ... just happens that for some reason I'm unable to boot the new 3.4.... kirkwood kernel. Yeah I got a couple of DKU-5 compatible cables from an ebay user (I forgot the details since it was 2 years ago) and i recall that for? something like 5 Euro I had them both shipped to my door. Doing enbedded stuff without at least a serial cable suitable for the target platform is difficult to say the least ... at some stage I plan to start using jtag too ;) ________________________________ Da: Richard Lapointe A: Davide ; Slackware ARM port Inviato: Gioved? 18 Aprile 2013 3:32 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Maybe you need a new uboot : http://forum.doozan.com/read.php?3,6965oot I use this uboot in my dockstar and 2 pogoplug P21 (E02) kirkwood base NAS.? All three are running Slackwarearm 14.0 I also use these for my serial connection.? http://www.ebay.com/sch/i.html?_trksid=p2047675.m570.l1313.TR0.TRC0&_nkw=USB+2.0+to+TTL+UART&_sacat=0&_from=R40 root at pogo-161:/home/rich# uname -a Linux pogo-161 3.4.11-kirkwood #2 PREEMPT Sat Sep 15 21:42:15 BST 2012 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux root at pogo-161:/home/rich# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done usb_scan_list=1 2 3 4 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_init=run usb_scan usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset ethaddr=00:25:31:xx:xx:xx arcNumber=2097 ipaddr=192.168.1.161 if_netconsole=ping $serverip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; preboot=run if_netconsole start_netconsole serverip=192.168.1.71 set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 bootcmd_pogo=run bootcmd_rescue rescue_installed=1 force_rescue=0 usb_custom_params=nic=auto:eth0:dhcp kbd=us Regards Rich Lapointe On 04/17/2013 11:15 AM, Davide wrote: >> Uncompressing Linux... done, booting the kernel. >> >> And that's it ... nothing more on the serial console and nothing on the >> network .... actually it does not even appear to mount the root >> filesystem as the last mount seems to be coherent with the last time I >> mounted it on my PC Do I need to recompile the kernel (I'm using the >> kirkwood uImage) or is there something else wrong ? >This usually happens when the kernel +initrd does not fit into the >allocated memory locations.? Make sure you have the u-boot memory settings >correctly set: >? ? Marvell>>? tftpboot 0x01100000 %SLACKTREE%/uinitrd-kirkwood.img >? ? Marvell>>? tftpboot 0x00800000 %SLACKTREE%/uImage-kirkwood >? ? Marvell>>? setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw >? ? Marvell>>? bootm 0x00800000 0x01100000 >I haven't tried the latest Kirkwood kernel on a Plug machine, but I know >it does work on the OpenRD client.? I added the 'earlyprintk' debugging to >the Tegra20 kernel which'd show you what was wrong, but I don't think this >is available in the kirkwood implementation (although I'll have a look >again later). O possibly the sizes matched what i was using 2 years back ... might nit fit the new images I've lost familiarity with uboot command line .... I load them from usb with something that looks like this: ${dev} $part ${usb_boot_dir} get populated somewhere along the execution of the script ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd setenv usb_boot_address 0x800000 0x1100000 bootm $usb_boot_address but they do look as if they are ok .... The images got into /boot when by installing the packages from the versatile virtual machine (I then manually linked with the correct names my uboot looks for) root at darkstar:/mnt/floppy/boot# ls System.map@???????????????? config-kirkwood-3.4.11? uImage-kirkwood-3.4.11? uinitrd-kirkwood-3.4.11 System.map-kirkwood-3.4.11? uImage@???????????????? uinitrd@ root at darkstar:/mnt/floppy/boot#? md5sum uinitrd-kirkwood-3.4.11 uImage-kirkwood-3.4.11 0ff11c800fa6745b04676787596246de? uinitrd-kirkwood-3.4.11 0c5e9a376a92e49863e2989875564a12? uImage-kirkwood-3.4.11 root at darkstar:/mnt/floppy/boot# so I'm supposing that it's not an issue on how they got into the image. anyway just incase anyone is intrested on the script I'm using for booting from usb stick if present (and correctly setup) or from internal flash here's a dump of printenv: Marvell>> printenv usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 bootcmd_pogo=fsload uboot-original-mtd0.kwb; go 0x800200 bootdelay=3 baudrate=115200 console=console=ttyS0,115200 mtdids=nand0=orion_nand partition=nand0,2 led_init=green blinking led_exit=green off led_error=orange blinking ethact=egiga0 arcNumber=2998 usb_boot_0=setenv root_fs root=/dev/sda${usb_dev_part} usb_boot_1=setenv root_fs root=/dev/sdb${usb_dev_part} usb_boot_2=setenv root_fs root=/dev/sdc${usb_dev_part} usb_boot_3=setenv root_fs root=/dev/sdd${usb_dev_part} usb_boot_4=setenv root_fs root=/dev/sde${usb_dev_part} usb_boot_5=setenv root_fs root=/dev/sdf${usb_dev_part} usb_boot_6=setenv root_fs root=/dev/sdg${usb_dev_part} set_usb_bootargs=setenv bootargs ${console} ${mtdparts} ${root_fs} ro ${root_fstype} mtdparts=mtdparts=orion_nand:1M(u-boot),4M at 1M(uImage),32M at 5M(rootfs),219M at 37M(data) root_fs=root=/dev/mtdblock2 root_fstype=rootfstype=jffs2 bootcmd=run usb_scan; run set_flash_bootargs; run boot_flash_kernel ethaddr=00:10:75:1A:21:B7 usb_part_list=4 3 2 1 usb_dev_list=6 5 4 3 2 1 0 usb_dev_part=0 usb_scan=usb start; setenv usb_boot_dev none; for dev in? $usb_dev_list; do for part in $usb_part_list; do if ext2ls usb ${dev}:$part /etc; then setenv usb_boot_dir; ext2ls usb ${dev}:$part /boot && setenv usb_boot_dir /boot; if ext2load usb ${dev}:$part 0x800000 ${usb_boot_dir} /uImage; then setenv usb_dev_part $part; setenv usb_boot_dev $dev; setenv usb_boot_address 0x800000; setenv root_fstype rootfstype=ext2; run usb_boot_$dev ; run set_usb_bootargs; fi; ext2load usb ${dev}:$usb_dev_part 0x1100000 ${usb_boot_dir}/uinitrd; && setenv usb_boot_address 0x800000 0x1100000; fi; done; done; if test "$usb_boot_dev" = "none"; then echo "No USB bootable device found"; else echo "USB device ${usb_boot_dev}:$usb_dev_part is bootable"; bootm $usb_boot_address; fi; flash_root_fstype=rootfstype=jffs2 flash_kernel_size=0x300000 flash_kernel_load_addr=0x6400000 set_flash_bootargs=setenv bootargs ${console} ${mtdparts} ${flash_root_fs} ro ${flash_root_fstype} boot_flash_kernel=nand read $flash_kernel_load_addr $flash_kernel_offest $flash_kernel_size; bootm $flash_kernel_load_addr flash_root_fs=root=/dev/mtdblock2 flash_kernel_offest=0x100000 stdin=serial stdout=serial stderr=serial > > >_______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Apr 18 09:15:36 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 18 Apr 2013 10:15:36 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: On Thu, 18 Apr 2013, Davide wrote: > So I updated the uboot image with the install script (I did it by hand > the first time around and I;ll savemyself the trouble if possible) and > nor the kernel gets loaded properly. I still have an issue concerning > that the root filesystem on the usb stick is ext2 while the slackware > arm 14 initrd is looking to mount an ext3 filesystem. I think I can fix > that by remaking my usb stick image or by repackaging the initrd with > the correct fstype ... maybe I just need to recheck how I pass boot > parameters to kernel from uboot when I detect a valid usb stick ! The resson it's doing that is purely because the kernels are built on a machine that has an ext3 root fs. Have a look through the INSTALL_KIRKWOOD document, as it explains what configuration to set up. You need to supply the kernel parameter: rootfstype=ext2 to your boot string. From louigi600 at yahoo.it Thu Apr 18 09:47:47 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 10:47:47 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> >> So I updated the uboot image with the install script (I did it by hand >> the first time around and I;ll savemyself the trouble if possible) and >> nor the kernel gets loaded properly. I still have an issue concerning >> that the root filesystem on the usb stick is ext2 while the slackware >> arm 14 initrd is looking to mount an ext3 filesystem. I think I can fix >> that by remaking my usb stick image or by repackaging the initrd with >> the correct fstype ... maybe I just need to recheck how I pass boot >> parameters to kernel from uboot when I detect a valid usb stick ! >The resson it's doing that is purely because the kernels are built on a >machine that has an ext3 root fs. >Have a look through the INSTALL_KIRKWOOD document, as it explains what >configuration to set up.? You need to supply the kernel parameter: >? rootfstype=ext2 >to your boot string. I remember that every time I change something in the uboot environment I tend to get unexpected things that require debugging. Since the usb stick was created from a versatile virtual machine the easiest thing to get going is to remake another image formatted in ext3. In fact that's what I did just to see that everything else was ok(and now I can boot into the real root). On the long run it's probably not a good idea to have journaled filesystem intended for disk on a MLC flash device ... so some time later I will look into getting things to work on ext2, for the time being I'll just make sure that the filesystem is mounted with noatime option. One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be missing from the slackware arm 14 repo ... I forgot where I got it from on 13.37 but on my old armedslack 13.37 it's installed: u-boot-tools-2010.12rc1-arm-1 Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Apr 18 09:56:55 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 10:56:55 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1366279015.83590.YahooMailNeo@web28802.mail.ir2.yahoo.com> >One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be missing from the slackware arm 14 repo ... I forgot where I got it from on 13.37 but on my old armedslack 13.37 it's installed: >u-boot-tools-2010.12rc1-arm-1 ooops ... maybe something wrong with me ... it's installed probabbly on the miniroot -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Apr 18 09:56:55 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 10:56:55 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <1366279015.83590.YahooMailNeo@web28802.mail.ir2.yahoo.com> >One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be missing from the slackware arm 14 repo ... I forgot where I got it from on 13.37 but on my old armedslack 13.37 it's installed: >u-boot-tools-2010.12rc1-arm-1 ooops ... maybe something wrong with me ... it's installed probabbly on the miniroot -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Thu Apr 18 10:24:45 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 18 Apr 2013 06:24:45 -0400 Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: On Thu, Apr 18, 2013 at 5:47 AM, Davide wrote: > > >>> So I updated the uboot image with the install script (I did it by hand >>> the first time around and I;ll savemyself the trouble if possible) and >>> nor the kernel gets loaded properly. I still have an issue concerning >>> that the root filesystem on the usb stick is ext2 while the slackware >>> arm 14 initrd is looking to mount an ext3 filesystem. I think I can fix >>> that by remaking my usb stick image or by repackaging the initrd with >>> the correct fstype ... maybe I just need to recheck how I pass boot >>> parameters to kernel from uboot when I detect a valid usb stick ! > >>The resson it's doing that is purely because the kernels are built on a >>machine that has an ext3 root fs. > >>Have a look through the INSTALL_KIRKWOOD document, as it explains what >>configuration to set up. You need to supply the kernel parameter: >> rootfstype=ext2 >>to your boot string. > > I remember that every time I change something in the uboot environment I > tend to get unexpected things that require debugging. > Since the usb stick was created from a versatile virtual machine the easiest > thing to get going is to remake another image formatted in ext3. > > In fact that's what I did just to see that everything else was ok(and now I > can boot into the real root). On the long run it's probably not a good idea > to have journaled filesystem intended for disk on a MLC flash device ... so > some time later I will look into getting things to work on ext2, for the > time being I'll just make sure that the filesystem is mounted with noatime > option. > > One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be > missing from the slackware arm 14 repo ... I forgot where I got it from on > 13.37 but on my old armedslack 13.37 it's installed: > u-boot-tools-2010.12rc1-arm-1 > > > Regards > David Hello! Interesting. I'll need to check my local repository, (local to me that is), because I just finished a check of one of the ones online, and that particular version isn't at home. Both of the ones that were there were either for 2011 or 2013. Not the release you name. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From richard.lapointe at gmail.com Thu Apr 18 10:39:36 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Thu, 18 Apr 2013 06:39:36 -0400 Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <516FCD68.7040903@laprjns.com> > One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems > to be missing from the slackware arm 14 repo ... I forgot where I got > it from on 13.37 but on my old armedslack 13.37 it's installed: > u-boot-tools-2010.12rc1-arm-1 It's in the repo root at pogo-161:/home/rich# slapt-get --se U-boot u-boot-tools-2012.04.01-arm-1 [inst=yes]: u-boot-tools (Tools for systems using the Das U-Boot Linux Loader) Rich Lapointe -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Apr 18 11:42:56 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 18 Apr 2013 12:42:56 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <516FCD68.7040903@laprjns.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> Message-ID: <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> Yeah ... I realized just after having sent the first mail ... I was probably typing something wrong without realizing and slackpkg was telling me there was nothing to install because it was already installed :-D Sorry for making a noise about my dyslexic typing on the keyboard? lol. David ________________________________ Da: Richard Lapointe A: armedslack at lists.armedslack.org Inviato: Gioved? 18 Aprile 2013 12:39 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar > One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems > to be missing from the slackware arm 14 repo ... I forgot where I got > it from on 13.37 but on my old armedslack 13.37 it's installed: > u-boot-tools-2010.12rc1-arm-1 It's in the repo root at pogo-161:/home/rich# slapt-get --se U-boot?? u-boot-tools-2012.04.01-arm-1 [inst=yes]: u-boot-tools (Tools for systems using the Das U-Boot Linux Loader) Rich Lapointe _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Apr 19 06:21:34 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 19 Apr 2013 07:21:34 +0100 (BST) Subject: [ARMedslack] slackwarearm on seagate dosckstar In-Reply-To: <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <1366352494.44199.YahooMailNeo@web28804.mail.ir2.yahoo.com> Ok ... just wish to thank you all for the help. I now have slackware arm 14 up and running on my dockstar and have moved my attention to compiling mediatomb on it. David ________________________________ Da: Davide A: Slackware ARM port Inviato: Gioved? 18 Aprile 2013 13:42 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar Yeah ... I realized just after having sent the first mail ... I was probably typing something wrong without realizing and slackpkg was telling me there was nothing to install because it was already installed :-D Sorry for making a noise about my dyslexic typing on the keyboard? lol. David ________________________________ Da: Richard Lapointe A: armedslack at lists.armedslack.org Inviato: Gioved? 18 Aprile 2013 12:39 Oggetto: Re: [ARMedslack] slackwarearm on seagate dosckstar > One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems > to be missing from the slackware arm 14 repo ... I forgot where I got > it from on 13.37 but on my old armedslack 13.37 it's installed: > u-boot-tools-2010.12rc1-arm-1 It's in the repo root at pogo-161:/home/rich# slapt-get --se U-boot?? u-boot-tools-2012.04.01-arm-1 [inst=yes]: u-boot-tools (Tools for systems using the Das U-Boot Linux Loader) Rich Lapointe _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Apr 22 12:49:13 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 22 Apr 2013 13:49:13 +0100 (BST) Subject: [ARMedslack] getting SATA working on seagate goflex net In-Reply-To: <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> Message-ID: <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> I decided it was time to pull out the goflexnet and hook up two 2.5" sata drives on it. I've slackware arm 14 running on it but I can't seem to see anything like a sata bus detected on my goflex net. Do I need to do something on uboot ro enable sata before the kernel is started ? I've also fixed the rootfs not being passed correctly via kernel command line: fw_setenv usb_scan 'usb start; setenv usb_boot_dev none; for dev in? $usb_dev_list; do test $dev -eq 0 && setenv devname /dev/sda ; test $dev -eq 1 && setenv devname /dev/sdb ; test $dev -eq 2 && setenv devname /dev/sdc ; test $dev -eq 3 && setenv devname /dev/sdd ; echo $devname ; for part in $usb_part_list; do echo $dev $part ; if ext2ls usb ${dev}:$part /etc ; then setenv root_fs root=${devname}$part ; setenv rootfstype rootfs=ext2 ; fi ; if ext2load usb ${dev}:$part 0x800000 /boot/uImage 10 ; then setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir /boot ; fi? ; if ext2load usb ${dev}:$part 0x800000 /uImage 10 ; then setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir ; fi? ; done; done; if test "$usb_boot_dev" = "none" ; then echo "No USB bootable device found" ; else echo "USB device $usb_boot_dev is bootable" ; setenv bootargs $console $mtdparts $root_fs ro $rootfstype ; echo $bootargs ; sleep 1; ext2load usb $usb_boot_dev 0x800000 $usb_boot_dir/uImage && setenv usb_boot_address 0x800000 ; ext2load usb $usb_boot_dev 0x1100000 $usb_boot_dir/uinitrd && setenv usb_boot_address 0x800000 0x1100000 ; bootm $usb_boot_address ; fi;' fw_setenv bootcmd 'run usb_scan; run set_flash_bootargs; run boot_flash_kernel' but that does not seem to help detecting anything connected to the sata ports. Is the arch number correct ? arcNumber=2097 Also I can't find where the leds are controlled ... there are a total of 8 monochromatic and one bicolr lets on this thing but I can only find this: root at slackware:/sys/class/leds# ls plug:green:health@? plug:red:misc@ root at slackware:/sys/class/leds# what's up with the 8 white leds ? Reegards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Mon Apr 22 22:42:01 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Mon, 22 Apr 2013 18:42:01 -0400 Subject: [ARMedslack] getting SATA working on seagate goflex net In-Reply-To: <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> Message-ID: <5175BCB9.7000904@laprjns.com> Maybe this will help http://forum.doozan.com/read.php?2,12045,12045#msg-12045 Rich Lapointe On 04/22/2013 08:49 AM, Davide wrote: > I decided it was time to pull out the goflexnet and hook up two 2.5" > sata drives on it. > I've slackware arm 14 running on it but I can't seem to see anything > like a sata bus detected on my goflex net. > > Do I need to do something on uboot ro enable sata before the kernel is > started ? > > I've also fixed the rootfs not being passed correctly via kernel > command line: > fw_setenv usb_scan 'usb start; setenv usb_boot_dev none; for dev in > $usb_dev_list; do test $dev -eq 0 && setenv devname /dev/sda ; test > $dev -eq 1 && setenv devname /dev/sdb ; test $dev -eq 2 && setenv > devname /dev/sdc ; test $dev -eq 3 && setenv devname /dev/sdd ; echo > $devname ; for part in $usb_part_list; do echo $dev $part ; if ext2ls > usb ${dev}:$part /etc ; then setenv root_fs root=${devname}$part ; > setenv rootfstype rootfs=ext2 ; fi ; if ext2load usb ${dev}:$part > 0x800000 /boot/uImage 10 ; then setenv usb_boot_dev $dev:$part ; > setenv usb_boot_dir /boot ; fi ; if ext2load usb ${dev}:$part > 0x800000 /uImage 10 ; then setenv usb_boot_dev $dev:$part ; setenv > usb_boot_dir ; fi ; done; done; if test "$usb_boot_dev" = "none" ; > then echo "No USB bootable device found" ; else echo "USB device > $usb_boot_dev is bootable" ; setenv bootargs $console $mtdparts > $root_fs ro $rootfstype ; echo $bootargs ; sleep 1; ext2load usb > $usb_boot_dev 0x800000 $usb_boot_dir/uImage && setenv usb_boot_address > 0x800000 ; ext2load usb $usb_boot_dev 0x1100000 $usb_boot_dir/uinitrd > && setenv usb_boot_address 0x800000 0x1100000 ; bootm > $usb_boot_address ; fi;' > fw_setenv bootcmd 'run usb_scan; run set_flash_bootargs; run > boot_flash_kernel' > > but that does not seem to help detecting anything connected to the > sata ports. > > Is the arch number correct ? > arcNumber=2097 > > Also I can't find where the leds are controlled ... there are a total > of 8 monochromatic and one bicolr lets on this thing but I can only > find this: > root at slackware:/sys/class/leds# ls > plug:green:health@ plug:red:misc@ > root at slackware:/sys/class/leds# > > what's up with the 8 white leds ? > > Reegards > David > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Apr 23 07:17:33 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 23 Apr 2013 08:17:33 +0100 (BST) Subject: [ARMedslack] getting SATA working on seagate goflex net In-Reply-To: <5175BCB9.7000904@laprjns.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366207270.56386.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1366211751.18831.YahooMailNeo@web28801.mail.ir2.yahoo.com> <516F4D26.8070509@laprjns.com> <1366267726.66275.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366274242.70229.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366278467.500.YahooMailNeo@web28805.mail.ir2.yahoo.com> <516FCD68.7040903@laprjns.com> <1366285376.44148.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1366634953.80971.YahooMailNeo@web28803.mail.ir2.yahoo.com> <5175BCB9.7000904@laprjns.com> Message-ID: <1366701453.22435.YahooMailNeo@web28806.mail.ir2.yahoo.com> I came across that yesterday while trying to check if I had the right arcnumber ... it would be really handy to have a list of the devices and their correct archnumber? somewhere ;-) I tried setting 3089 as archnumber but the slackware kernel no longer boots if I do that. This can probably be fixed if I rebuild the kernel (not sure if patching is needed too) ... but since my work on ClashNG there are 2 new members in my family so if I can avoid time consuming stuff that would be really good. Can I borrow a kernel from somewhere else that is known to work well if I use it on a slackware arm 14 userland (and has support for all features of the goflex net )? Regards David ________________________________ Da: Richard Lapointe A: Davide ; Slackware ARM port Inviato: Marted? 23 Aprile 2013 0:42 Oggetto: Re: [ARMedslack] getting SATA working on seagate goflex net Maybe this will help http://forum.doozan.com/read.php?2,12045,12045#msg-12045 Rich Lapointe On 04/22/2013 08:49 AM, Davide wrote: I decided it was time to pull out the goflexnet and hook up two 2.5" sata drives on it. >I've slackware arm 14 running on it but I can't seem to see anything like a sata bus detected on my goflex net. > >Do I need to do something on uboot ro enable sata before the kernel is started ? > >I've also fixed the rootfs not being passed correctly via kernel command line: >fw_setenv usb_scan 'usb start; setenv usb_boot_dev none; for dev in? $usb_dev_list; do test $dev -eq 0 && setenv devname /dev/sda ; test $dev -eq 1 && setenv devname /dev/sdb ; test $dev -eq 2 && setenv devname /dev/sdc ; test $dev -eq 3 && setenv devname /dev/sdd ; echo $devname ; for part in $usb_part_list; do echo $dev $part ; if ext2ls usb ${dev}:$part /etc ; then setenv root_fs root=${devname}$part ; setenv rootfstype rootfs=ext2 ; fi ; if ext2load usb ${dev}:$part 0x800000 /boot/uImage 10 ; then setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir /boot ; fi? ; if ext2load usb ${dev}:$part 0x800000 /uImage 10 ; then setenv usb_boot_dev $dev:$part ; setenv usb_boot_dir ; fi? ; done; done; if test "$usb_boot_dev" = "none" ; then echo "No USB bootable device found" ; else echo "USB device $usb_boot_dev is bootable" ; setenv bootargs $console $mtdparts $root_fs ro $rootfstype ; echo $bootargs ; sleep 1; ext2load usb $usb_boot_dev 0x800000 $usb_boot_dir/uImage && setenv usb_boot_address 0x800000 ; ext2load usb $usb_boot_dev 0x1100000 $usb_boot_dir/uinitrd && setenv usb_boot_address 0x800000 0x1100000 ; bootm $usb_boot_address ; fi;' >fw_setenv bootcmd 'run usb_scan; run set_flash_bootargs; run boot_flash_kernel' > >but that does not seem to help detecting anything connected to the sata ports. > >Is the arch number correct ? >arcNumber=2097 > >Also I can't find where the leds are controlled ... there are a total of 8 monochromatic and one bicolr lets on this thing but I can only find this: >root at slackware:/sys/class/leds# ls >plug:green:health@? plug:red:misc@ >root at slackware:/sys/class/leds# > >what's up with the 8 white leds ? > >Reegards >David > > >_______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Tue Apr 30 22:02:15 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Tue, 30 Apr 2013 18:02:15 -0400 (EDT) Subject: [ARMedslack] Slackware ARM on Raspberry Pi Message-ID: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> Hi, The packages from Dave's Collective (Kernel 3.1.9) don't seem to support the extra memory on the revised Raspberry Pi Model B board. I think this is because the firmware package used is downlevel. So I've made some new firmware, kernel (3.6.11) and module packages. They can be found here http://www.dowelld.net/?p=43. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregg.drwho8 at gmail.com Tue Apr 30 22:35:42 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Tue, 30 Apr 2013 18:35:42 -0400 Subject: [ARMedslack] Slackware ARM on Raspberry Pi In-Reply-To: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> References: <8D01405829E8E32-DA4-CEC3@webmail-m134.sysops.aol.com> Message-ID: On Tue, Apr 30, 2013 at 6:02 PM, wrote: > Hi, > > The packages from Dave's Collective (Kernel 3.1.9) don't seem to support the > extra memory on the revised Raspberry Pi Model B board. I think this is > because the firmware package used is downlevel. > > So I've made some new firmware, kernel (3.6.11) and module packages. They > can be found here http://www.dowelld.net/?p=43. > > Thanks > Dave > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > Hello! Dave how did you get Slackware for ARM running on yours? I didn't have much luck originally with my setup and decided to put it aside. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."