From m-lists at biscuit.org.uk Wed Sep 1 09:07:23 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 1 Sep 2010 10:07:23 +0100 (BST) Subject: [ARMedslack] Setting up distcc for cross compiling In-Reply-To: <201008311825.47923.thenktor@gmx.de> References: <201008311132.29616.thenktor@gmx.de> <201008311404.58604.thenktor@gmx.de> <201008311825.47923.thenktor@gmx.de> Message-ID: > > Too bad shipping costs are so high between Germany & France :-( > > I've seen it somewhere in France for 19 ?, too. But IIRC this was one of I haven't had time to digest this site, so I'll only post the link with the thought that NewIT can ship it around Europe cheaper than GlobalScale in the US: http://newit.co.uk/index.php?id=11 From mr.spuratic at gmail.com Wed Sep 1 10:05:23 2010 From: mr.spuratic at gmail.com (Conor McCarthy) Date: Wed, 1 Sep 2010 11:05:23 +0100 Subject: [ARMedslack] Setting up distcc for cross compiling In-Reply-To: References: <201008311132.29616.thenktor@gmx.de> <201008311404.58604.thenktor@gmx.de> <201008311825.47923.thenktor@gmx.de> Message-ID: On 1 September 2010 10:07, Stuart Winter wrote: > >> > Too bad shipping costs are so high between Germany & France :-( >> >> I've seen it somewhere in France for 19 ?, too. But IIRC this was one of > > I haven't had time to digest this site, so I'll only post the link with > the thought that NewIT can ship it around Europe cheaper than GlobalScale > in the US: > > http://newit.co.uk/index.php?id=11 I got my sheevaplug there (shipped to Ireland), fast delivery, and I'd be happy to use them again. Globalscale don't seem too interested in the end-user/hobbyist. Buying & shipping within Europe may save you a nasty import duty or VAT surprise... C. From niels.horn at gmail.com Sun Sep 5 12:54:55 2010 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 5 Sep 2010 09:54:55 -0300 Subject: [ARMedslack] Setting up Slackware-current (> 2010/07/29) as a new distccd server Message-ID: Hi, I just added an extra box as a server for my distcc setup, but this one uses Slackware-current. Running the 'bwl' script from devtools fails after a while with: Makefile:235: *** mixed implicit and normal rules. Stop. I traced this back to the new make version (3.82) in -current and found a fix from the LFS guys, running a sed command to change the manual/Makefile. The following patch to the x-build script solves it: --- x-build.orig 2010-09-05 08:27:53.000000000 -0300 +++ x-build 2010-09-05 09:00:28.000000000 -0300 @@ -193,6 +193,11 @@ #for i in patches/*.patch ; do # auto_apply_patch $i #done + +# Apply patch to build with make-3.82 +# (from: http://www.linuxquestions.org/questions/linux-from-scratch-13/glibc-not-compiling-in-chapter-6-9-a-824573/) +sed -i 's/ot \$/ot:\n\ttouch $@\n$/' manual/Makefile + set +x # Configure: Hope this is useful for other people running into this :) Regards, Niels Horn Rio de Janeiro, RJ Brasil site: www.nielshorn.net e-mail: niels.horn at gmail.com From m-lists at biscuit.org.uk Mon Sep 6 06:22:26 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 6 Sep 2010 07:22:26 +0100 (BST) Subject: [ARMedslack] Setting up Slackware-current (> 2010/07/29) as a new distccd server In-Reply-To: References: Message-ID: > Hope this is useful for other people running into this :) Thanks Niels. I've patched the script and it'll be available on the ftp site when I next push stuff. From thenktor at gmx.de Wed Sep 8 15:39:36 2010 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Wed, 8 Sep 2010 17:39:36 +0200 Subject: [ARMedslack] Setting up distcc for cross compiling In-Reply-To: References: <201008311132.29616.thenktor@gmx.de> Message-ID: <201009081739.36486.thenktor@gmx.de> Am Tuesday 31 August 2010 12:03:15 schrieb Stuart Winter: > > is there a good guide how to set up distcc to build to help building arm > > packages on my x86_64 and i486 hosts? > > Yep. Go back to the FTP site and download the script "dbuild" - I just > put it there. OK, had time to take a look at it. Please correct me if I'm wrong: You are creating gcc links to distcc in a temp dir, so that distcc can be called by usual command "gcc": cd /tmp/DISTCC ln -vfs /usr/bin/distcc gcc ln -vfs /usr/bin/distcc cc ln -vfs /usr/bin/distcc g++ ln -vfs /usr/bin/distcc c++ ln -vfs /usr/bin/distcc arm-slackware-linux-${EABI}c++ ln -vfs /usr/bin/distcc arm-slackware-linux-${EABI}g++ ln -vfs /usr/bin/distcc arm-slackware-linux-${EABI}gcc After and to make sure distcc is called instead of original gcc you place the directory with distcc symlinks at the beginning of the PATH. So it's not needed to specify CC in Makefiles: PATH=/tmp/DISTCC:$PATH Before distcc can be called it needs info what hosts to contact and the number of jobs the host should run: export DISTCC_HOSTS="hostnameA/3 hostnameB/1 hostnameC/1" And I probably have to do the same trick with the PATH on the host machines so that the cross compiler is run? From m-lists at biscuit.org.uk Wed Sep 8 18:40:26 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 8 Sep 2010 19:40:26 +0100 (BST) Subject: [ARMedslack] Setting up distcc for cross compiling In-Reply-To: <201009081739.36486.thenktor@gmx.de> References: <201008311132.29616.thenktor@gmx.de> <201009081739.36486.thenktor@gmx.de> Message-ID: [snip] Yes you understand it perfectly. The $PATH thing is a dirty hack but works nicely in 99% of cases. > And I probably have to do the same trick with the PATH on the host machines so > that the cross compiler is run? Check the file 'rc.local-addition' - this is how I start distcc on the x86 hosts. You have to adjust the PATH distccd on xx86 has in order for distcc to find the cross compile version of gcc, yes; but it has nothing to do with the /tmp/DISTCC paths on your ARM hosts. -- Stuart Winter Slackware ARM: www.armedslack.org From claudio.cavalera at gmail.com Mon Sep 13 16:25:59 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Mon, 13 Sep 2010 18:25:59 +0200 Subject: [ARMedslack] Armedslack on a dockstar :-) Message-ID: Hello, I'm new to this list! I've been using slackware on x86 since 7.1 and I tend to install it on every machine I touch. Recently I'm being in touch with the Seagate Dockstar which is a promising device based on Kirkwood Soc: http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device/ I've found this info on how to install armedslack on it: http://blog.gmane.org/gmane.linux.slackware.armedslack/month=20100801 I hope I'll succeed :-) Just one general question on armedslack: is it suggested to use slackbuilds.org scripts to compile and install software which is not officially in slackware or is it better to compile and install by hand ? Bye, Claudio From niels.horn at gmail.com Mon Sep 13 17:02:47 2010 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 13 Sep 2010 14:02:47 -0300 Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: References: Message-ID: On Mon, Sep 13, 2010 at 1:25 PM, Claudio Cavalera wrote: > Hello, > I'm new to this list! > I've been using slackware on x86 since 7.1 and I tend to install it on > every machine I touch. > Recently I'm being in touch with the Seagate Dockstar which is a > promising device based on Kirkwood Soc: > http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device/ > > I've found this info on how to install armedslack on it: > http://blog.gmane.org/gmane.linux.slackware.armedslack/month=20100801 > > I hope I'll succeed :-) > > Just one general question on armedslack: is it suggested to use > slackbuilds.org scripts to compile and install software which is not > officially in slackware or is it better to compile and install by hand > ? > > Bye, > Claudio Hi and welcome! I would definitely suggest to use the scripts on SlackBuilds.org After the change to Slackware 13.1, most will compile fine on ARMedslack. There are some exceptions of course, but you will find out trying. :) I have used several SlackBuilds to build packages for my SheevaPlug and maintain a few myself. The big advantage of building & installing a package is the maintainability. Regards, Niels Horn From m-lists at biscuit.org.uk Wed Sep 15 09:15:11 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 15 Sep 2010 10:15:11 +0100 (BST) Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: References: Message-ID: > Recently I'm being in touch with the Seagate Dockstar which is a > promising device based on Kirkwood Soc: > http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device/ This looks like an interesting device. You'll probably need to build a new kernel to begin with patched with support for the Dockstar, because I don't see anything about the "Dockstar" in the "kirkwood implementations" in the Kernel armedslack ships. There might be support in linux 2.6.36, in which case I'll add it in when I next update the kernel. Let us know how you get on with it. Good luck! :) From thenktor at gmx.de Wed Sep 15 09:29:11 2010 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Wed, 15 Sep 2010 11:29:11 +0200 Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: References: Message-ID: <201009151129.12028.thenktor@gmx.de> The Dockstar works fine with the Armed Slack kernel. See my message from 29.08.2010: > OK, I've received my Seagate Freeagent Dockstar. I've flashed a new > U-Boot loader to it. A description can be found here: > http://www.plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot > http://plugapps.com/os/pogoplug/uboot/ > > The board boots fine when the kirkwood kernel is used, that comes with > the mini rootfs. Here is the cpuinfo: > > cat /proc/cpuinfo > Processor : Feroceon 88FR131 rev 1 (v5l) > BogoMIPS : 1192.75 > Features : swp half thumb fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant : 0x2 > CPU part : 0x131 > CPU revision : 1 > > Hardware : Marvell SheevaPlug Reference Board > Revision : 0000 > Serial : 0000000000000000 I've installed the new U-Boot. Make sure the kernel is called uImage and the initrd is called uInitrd. Am Wednesday 15 September 2010 11:15:11 schrieb Stuart Winter: > > Recently I'm being in touch with the Seagate Dockstar which is a > > promising device based on Kirkwood Soc: > > http://xkyle.com/2010/07/19/the-seagate-dockstar-a-very-cool-linux-device > >/ > > This looks like an interesting device. > > You'll probably need to build a new > kernel to begin with patched with support for the Dockstar, because I > don't see anything about the "Dockstar" in the "kirkwood implementations" > in the Kernel armedslack ships. There might be support in linux 2.6.36, > in which case I'll add it in when I next update the kernel. > > Let us know how you get on with it. Good luck! :) > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -- ____________________________________________________ Dipl.-Ing. (FH) Thorsten M?hlfelder Hard- und Softwareentwicklung From jawkins at armedslack.org Wed Sep 15 15:22:00 2010 From: jawkins at armedslack.org (Jim Hawkins) Date: Wed, 15 Sep 2010 16:22:00 +0100 (BST) Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: References: Message-ID: On Wed, 15 Sep 2010, Stuart Winter wrote: > I don't see anything about the "Dockstar" in the "kirkwood > implementations" in the Kernel armedslack ships. There might be support > in linux 2.6.36, in which case I'll add it in when I next update the > kernel. Someone just posted a patch for the DockStar to the armlinux mailing list. Doesn't really have much device specific stuff in it - configures the GPIO pins for LEDs and USB power enable. You can probably get away with using a different Kirkwood kernel as Thorsten has found. Cheers, Jim From claudio.cavalera at gmail.com Thu Sep 16 09:05:07 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Thu, 16 Sep 2010 11:05:07 +0200 Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: References: Message-ID: On Wed, Sep 15, 2010 at 5:22 PM, Jim Hawkins wrote: > On Wed, 15 Sep 2010, Stuart Winter wrote: > >> I don't see anything about the "Dockstar" in the "kirkwood >> implementations" in the Kernel armedslack ships. ?There might be support >> in linux 2.6.36, in which case I'll add it in when I next update the >> kernel. > > Someone just posted a patch for the DockStar to the armlinux mailing list. > Doesn't really have much device specific stuff in it - configures the GPIO > pins for LEDs and USB power enable. You can probably get away with using a > different Kirkwood kernel as Thorsten has found. What is USB power enable? Thanks, Claudio From laprjns at comcast.net Thu Sep 16 22:55:26 2010 From: laprjns at comcast.net (Richard Lapointe) Date: Thu, 16 Sep 2010 18:55:26 -0400 Subject: [ARMedslack] Hello In-Reply-To: <20100824222444.231022c1@pinkfloyd.tm-net> References: <201008131344.46027.thenktor@gmx.de> <201008181725.10247.thenktor@gmx.de> <4C6C7529.5030301@comcast.net> <20100819080230.20c89a59@pinkfloyd.tm-net> <20100824222444.231022c1@pinkfloyd.tm-net> Message-ID: <4C92A05E.2000409@comcast.net> I subscribed to this list at the end of August, but have been having trouble getting my email so I just subscribed again with my alternate gmail account. Just wanted to tell you that I've got armedslack running on my dockstar. Once I got my serial line working, it was quite easy. I first follow the direction from here: http://plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot , but only through installing the uboot. After that I followed the instructions for 13.1 from here: ftp://ftp.armedslack.org/armedslack/armedslack-13.1/INSTALL_KIRKWOOD.TXT. I actually installed current first, so they both worked. Rich Lapointe On 08/24/2010 04:24 PM, Thorsten M?hlfelder wrote: > I've ordered one of these Dockstars now. I cannot get any cheaper thing > here (25 ? incl. shipping). Let's see what I can do with it. > > Am Thu, 19 Aug 2010 00:39:19 -0600 > schrieb Tyler T: > > >>> what CPU/RAM/flash does the Seagate Dockstar have? >>> >> 1.2GHz ARMv5TE (Kirkwood), 128MB DDR RAM, 256MB flash. >> _______________________________________________ >> 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 > From claudio.cavalera at gmail.com Fri Sep 17 14:55:38 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Fri, 17 Sep 2010 16:55:38 +0200 Subject: [ARMedslack] Hello In-Reply-To: <4C92A05E.2000409@comcast.net> References: <201008131344.46027.thenktor@gmx.de> <201008181725.10247.thenktor@gmx.de> <4C6C7529.5030301@comcast.net> <20100819080230.20c89a59@pinkfloyd.tm-net> <20100824222444.231022c1@pinkfloyd.tm-net> <4C92A05E.2000409@comcast.net> Message-ID: On Fri, Sep 17, 2010 at 12:55 AM, Richard Lapointe wrote: > I subscribed to this list at the end of August, but have been having trouble > getting my email so I just subscribed again with my alternate gmail account. > > Just wanted to tell you that I've got armedslack running on my dockstar. > ?Once I got my serial line working, it was quite easy. ?I first follow the > direction from here: > http://plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot , but only > through installing the uboot. ?After that I followed the instructions for > 13.1 from here: > ftp://ftp.armedslack.org/armedslack/armedslack-13.1/INSTALL_KIRKWOOD.TXT. ?I > actually installed current first, so they both worked. > > Rich Lapointe Great! I guess it's not possible to achieve that without a serial cable, is it? So you did not patched the kernel to have LEDs working and USB power did you? Thanks, Claudio From richard.lapointe at gmail.com Sun Sep 19 17:11:00 2010 From: richard.lapointe at gmail.com (Rich) Date: Sun, 19 Sep 2010 13:11:00 -0400 Subject: [ARMedslack] Hello In-Reply-To: References: <201008131344.46027.thenktor@gmx.de> <201008181725.10247.thenktor@gmx.de> <4C6C7529.5030301@comcast.net> <20100819080230.20c89a59@pinkfloyd.tm-net> <20100824222444.231022c1@pinkfloyd.tm-net> <4C92A05E.2000409@comcast.net> Message-ID: <4C964424.40908@gmail.com> For me no, I finally needed a serial cable. I did try loading the mini root file system on to a usb stick and renaming the kernel and initrd to uImage and uInitrd, but it just keep rebooting the armedslack kernel. In the mean time my CA-42 serial cable came in so, once I hooked it up I had no problems following the instruction that I linked to in my earlier post. I do believe that Thorsten (also on this mailing list) did manage to get armedslack working using the method that I just described. No, I have not patched the kernel. I believe that that patch is only cosmetic and just provides control of the leds. See here: http://jeff.doozan.com/debian/dockstar-kernel.patch. and http://forum.doozan.com/read.php?2,524,908#msg-908. If you haven't been to Jeff Doozan site, I would recommend it. Although it's Debian centric, there is lots of good information. Also it looks to me like he the main man for an alternate uboot (I'm using his uboot). Maybe someone could use his dockstar Debian installer to use as template to make an armedslack installer. I did install Debian to my dockstar using his installer and it was extremely easy, no need for a serial cable, however I quickly realized that I was not a Debian fan. Rich On 09/17/2010 10:55 AM, Claudio Cavalera wrote: > On Fri, Sep 17, 2010 at 12:55 AM, Richard Lapointe wrote: > >> I subscribed to this list at the end of August, but have been having trouble >> getting my email so I just subscribed again with my alternate gmail account. >> >> Just wanted to tell you that I've got armedslack running on my dockstar. >> Once I got my serial line working, it was quite easy. I first follow the >> direction from here: >> http://plugapps.com/index.php5?title=PlugApps:Pogoplug_Setboot , but only >> through installing the uboot. After that I followed the instructions for >> 13.1 from here: >> ftp://ftp.armedslack.org/armedslack/armedslack-13.1/INSTALL_KIRKWOOD.TXT. I >> actually installed current first, so they both worked. >> >> Rich Lapointe >> > > Great! > I guess it's not possible to achieve that without a serial cable, is it? > So you did not patched the kernel to have LEDs working and USB power did you? > Thanks, > Claudio > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > From m-lists at biscuit.org.uk Fri Sep 24 13:45:45 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 24 Sep 2010 14:45:45 +0100 (BST) Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? Message-ID: Has anyone tried it? It compiles OK without patches (openrd-ultimate is included upstream now) but when booting, it's not so happy. [ 1.987006] Stack: (0xdf829e68 to 0xdf82a000) [ 1.991388] 9e60: df829ea0 df829ea0 de7b7728 00000000 de7b7728 00000000 [ 1.999612] 9e80: de7b7788 df890368 00000001 01403fe4 df812400 df812460 c0403770 00000000 [ 2.007835] 9ea0: c01f9b38 c01bcb58 df812400 c01bcdd4 df812460 c0403770 df812400 c040ea20 [ 2.016058] 9ec0: df812460 df812460 c04037a0 c04037a0 c01f9b38 c01fab90 df812460 df812494 [ 2.024281] 9ee0: c04037a0 00000000 c01f9b38 c01faca8 c04037a0 df829f00 c01fac48 c01fa31c [ 2.032504] 9f00: df8418f8 df891cf0 c04037a0 c04037a0 de7a9ae0 c03f972c 00000000 c01f9c5c [ 2.040726] 9f20: c03adadc c03adadc c04037a0 c04037a0 c03f972c 00000000 00000000 00000000 [ 2.048949] 9f40: 00000000 c01faf7c c0403770 c04037a0 c03f972c 00000000 00000000 c01bd058 [ 2.057172] 9f60: c00258d4 c002120c c002a3d4 00000000 00000000 c0021714 c002a3d4 00000000 [ 2.065395] 9f80: 00000000 00000000 00000000 c00258d4 c002120c c002a3d4 00000000 00000000 [ 2.073617] 9fa0: 00000000 00000000 00000000 c00293f4 df813d80 00333131 00000000 00000000 [ 2.081841] 9fc0: 00000000 00000071 c00258d4 c0025944 c002a3d4 00000013 00000000 00000000 [ 2.090064] 9fe0: 00000000 c00083f8 00000000 c0008360 c002a3d4 c002a3d4 ffffffff ffffffff [ 2.098298] [] (xgifb_probe+0x158/0x13fc) from [] (local_pci_probe+0x14/0x18) [ 2.107219] [] (local_pci_probe+0x14/0x18) from [] (pci_device_probe+0x5c/0x90) [ 2.116314] [] (pci_device_probe+0x5c/0x90) from [] (driver_probe_device+0xb0/0x168) [ 2.125843] [] (driver_probe_device+0xb0/0x168) from [] (__driver_attach+0x60/0x84) [ 2.135286] [] (__driver_attach+0x60/0x84) from [] (bus_for_each_dev+0x48/0x84) [ 2.144381] [] (bus_for_each_dev+0x48/0x84) from [] (bus_add_driver+0x140/0x2bc) [ 2.153564] [] (bus_add_driver+0x140/0x2bc) from [] (driver_register+0xac/0x13c) [ 2.162746] [] (driver_register+0xac/0x13c) from [] (__pci_register_driver+0x38/0xb4) [ 2.172367] [] (__pci_register_driver+0x38/0xb4) from [] (xgifb_init+0x508/0x590) [ 2.181635] [] (xgifb_init+0x508/0x590) from [] (do_one_initcall+0xcc/0x1a8) [ 2.190467] [] (do_one_initcall+0xcc/0x1a8) from [] (kernel_init+0x98/0x14c) [ 2.199301] [] (kernel_init+0x98/0x14c) from [] (kernel_thread_exit+0x0/0x8) [ 2.208132] Code: e5951004 e3a02005 e59f3e44 e2411612 (e5c12000) [ 2.214358] ---[ end trace 21c8e1b90f481904 ]--- [ 2.219112] Kernel panic - not syncing: Attempted to kill init! [ 2.225080] [] (unwind_backtrace+0x0/0xf0) from [] (panic+0x60/0x184) [ 2.233328] [] (panic+0x60/0x184) from [] (do_exit+0x70/0x728) [ 2.240955] [] (do_exit+0x70/0x728) from [] (die+0x2d8/0x318) [ 2.248483] [] (die+0x2d8/0x318) from [] (__do_kernel_fault+0x64/0x88) [ 2.256810] [] (__do_kernel_fault+0x64/0x88) from [] (do_translation_fault+0x9c/0xa8) [ 2.266442] [] (do_translation_fault+0x9c/0xa8) from [] (do_DataAbort+0x34/0x94) [ 2.275641] [] (do_DataAbort+0x34/0x94) from [] (__dabt_svc+0x4c/0x60) [ 2.283961] Exception stack(0xdf829e20 to 0xdf829e68) [ 2.289050] 9e20: c0470d74 f0e00044 00000005 fee00001 df812400 c0470d74 c0403770 00000000 [ 2.297269] 9e40: c01f9b38 00000000 00000060 00000000 f2000046 df829e68 c02f4b90 c02f4ba0 [ 2.305499] 9e60: 60000013 ffffffff [ 2.309023] [] (__dabt_svc+0x4c/0x60) from [] (xgifb_probe+0x158/0x13fc) [ 2.317514] [] (xgifb_probe+0x158/0x13fc) from [] (local_pci_probe+0x14/0x18) [ 2.326454] [] (local_pci_probe+0x14/0x18) from [] (pci_device_probe+0x5c/0x90) [ 2.335566] [] (pci_device_probe+0x5c/0x90) from [] (driver_probe_device+0xb0/0x168) [ 2.345113] [] (driver_probe_device+0xb0/0x168) from [] (__driver_attach+0x60/0x84) [ 2.354573] [] (__driver_attach+0x60/0x84) from [] (bus_for_each_dev+0x48/0x84) [ 2.363685] [] (bus_for_each_dev+0x48/0x84) from [] (bus_add_driver+0x140/0x2bc) [ 2.372876] [] (bus_add_driver+0x140/0x2bc) from [] (driver_register+0xac/0x13c) [ 2.382078] [] (driver_register+0xac/0x13c) from [] (__pci_register_driver+0x38/0xb4) [ 2.391714] [] (__pci_register_driver+0x38/0xb4) from [] (xgifb_init+0x508/0x590) [ 2.401000] [] (xgifb_init+0x508/0x590) from [] (do_one_initcall+0xcc/0x1a8) [ 2.409849] [] (do_one_initcall+0xcc/0x1a8) from [] (kernel_init+0x98/0x14c) [ 2.418687] [] (kernel_init+0x98/0x14c) from [] (kernel_thread_exit+0x0/0x8) -- Stuart Winter Slackware ARM: www.armedslack.org From thierry.merle at free.fr Sat Sep 25 05:54:05 2010 From: thierry.merle at free.fr (Thierry Merle) Date: Sat, 25 Sep 2010 07:54:05 +0200 Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: References: Message-ID: <20100925075405.784dd9ca@gorbag.houroukhai.org> Le Fri, 24 Sep 2010 14:45:45 +0100 (BST), Stuart Winter a ?crit : > > Has anyone tried it? > It compiles OK without patches (openrd-ultimate is included upstream > now) but when booting, it's not so happy. [...] > [ 2.098298] [] (xgifb_probe+0x158/0x13fc) from > [] (local_pci_probe+0x14/0x18) [...] Seems that there is a problem with the xgifb staging driver. Just try to deactivate it... If I have time this week-end I will compile this kernel on my sheevaplug. Thierry From jawkins at armedslack.org Sat Sep 25 17:00:19 2010 From: jawkins at armedslack.org (Jim Hawkins) Date: Sat, 25 Sep 2010 18:00:19 +0100 (BST) Subject: [ARMedslack] Slackware ARM 13.1 rc1 ready In-Reply-To: <4BF6AF97.9050304@gmail.com> References: <4BF5CDBE.4060509@gmail.com> <4BF6AF97.9050304@gmail.com> Message-ID: On Fri, 21 May 2010, John O'Donnell wrote: > Jim Hawkins wrote: > > $ grep guruplug arch/arm/tools/mach-types > > guruplug MACH_GURUPLUG GURUPLUG 2659 > > > > Try arcNumber=2659 instead. > > [snip] > > It still hangs at the same spot. I finally got my GuruPlug Server Plus today, so I thought I'd follow up on this one. I'm not sure what the arcNumber stuff is all about, because I can't find any reference to it in the u-boot git tree, nor in the Marvell u-boot custodian tree, but after a bit of grepping on the source I've found you can do the following with the u-boot installed on the GuruPlug, straight out of the box: setenv machid a63 That's 2659 in hex. And that allows you to run the ARMedslack installer kernel just fine. Cheers, Jim From unixjohn1969 at gmail.com Sat Sep 25 22:15:42 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sat, 25 Sep 2010 18:15:42 -0400 Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: References: Message-ID: <4C9E748E.6050100@gmail.com> On 09/24/2010 09:45 AM, Stuart Winter wrote: > > Has anyone tried it? > It compiles OK without patches (openrd-ultimate is included upstream now) > but when booting, it's not so happy. I have only compiled a kernel and not updated the initrd. But it boots up to that point. Granted I stripped out ALOT of modules and bits and put in the kernel goodies that I want to use alot, but it boots... Took forever to compile last night... Starting a new compile (on the guruplug itself - not an emulator) with more fat trimmed, so I will send results with this kernel hopefully fully booted. GuruPlug>> bootm 0x00800000 0x01100000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.36-rc5-jjo Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2561028 Bytes = 2.4 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: Slackware ARM Initial RAM disk f Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 7706184 Bytes = 7.3 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.36-rc5-jjo (root at guruslack) (gcc version 4.4.4 (GCC) ) #1 Sat Sep 25 09:44:13 EDT 2010 CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 CPU: VIVT data cache, VIVT instruction cache Machine: Marvell GuruPlug Reference Board Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS0,115200 root=/dev/sdc3 waitforroot=10 rootfs=e xt3 ubi.mtd=2 PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB = 512MB total Memory: 507184k/507184k available, 17104k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0xe0800000 - 0xfe800000 ( 480 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .init : 0xc0008000 - 0xc0025000 ( 116 kB) .text : 0xc0025000 - 0xc048a000 (4500 kB) .data : 0xc04a2000 - 0xc04c38a0 ( 135 kB) Hierarchical RCU implementation. RCU-based detection of stalled CPUs is disabled. Verbose stalled-CPUs detection is disabled. NR_IRQS:114 Console: colour dummy device 80x30 Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 Kirkwood: MV88F6281-A1, TCLK=200000000. Feroceon L2: Cache support initialised. bio: create slab at 0 vgaarb: loaded usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb cfg80211: Calling CRDA to update world regulatory domain Switching to clocksource orion_clocksource NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Trying to unpack rootfs image as initramfs... Freeing initrd memory: 7524K NetWinder Floating Point Emulator V0.97 (double precision) JFFS2 version 2.2. (NAND) (SUMMARY) ?? 2001-2006 Red Hat, Inc. msgmni has been set to 1005 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A console [ttyS0] enabled brd: module loaded loop: module loaded NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bi t) Scanning device for bad blocks Bad eraseblock 3558 at 0x00001bcc0000 Creating 3 MTD partitions on "orion_nand": 0x000000000000-0x000000100000 : "u-boot" ftl_cs: FTL header not found. 0x000000100000-0x000000500000 : "uImage" ftl_cs: FTL header not found. 0x000000500000-0x000020000000 : "root" ftl_cs: FTL header not found. UBI: attaching mtd2 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 UBI: max. sequence number: 9868 UBI: attached mtd2 to ubi0 UBI: MTD device name: "root" UBI: MTD device size: 507 MiB UBI: number of good PEBs: 4055 UBI: number of bad PEBs: 1 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 4055 UBI: number of PEBs reserved for bad PEB handling: 40 UBI: max/mean erase counter: 5/3 UBI: image sequence number: -1 UBI: background thread "ubi_bgt0d" started, PID 334 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver orion-ehci orion-ehci.0: Marvell Orion EHCI orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: Marvell Orion EHCI usb usb1: Manufacturer: Linux 2.6.36-rc5-jjo ehci_hcd usb usb1: SerialNumber: orion-ehci.0 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver uhci_hcd: USB Universal Host Controller Interface driver usbcore: registered new interface driver libusual mice: PS/2 mouse device common for all mice rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0 i2c /dev entries driver cpuidle: using governor ladder cpuidle: using governor menu mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) TCP cubic registered NET: Registered protocol family 17 lib80211: common routines for IEEE802.11 drivers Registering the dns_resolver key type rtc-mv rtc-mv: setting system clock to 2010-09-25 17:40:02 UTC (1285436402) Freeing init memory: 116K No kernel modules found for Linux 2.6.36-rc5-jjo. usb 1-1: new high speed USB device using orion-ehci and address 2 usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 usb 1-1: Product: USB2.0 Hub hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.1: new high speed USB device using orion-ehci and address 3 usb 1-1.1: New USB device found, idVendor=05e3, idProduct=0726 usb 1-1.1: New USB device strings: Mfr=0, Product=1, SerialNumber=2 usb 1-1.1: Product: USB Storage usb 1-1.1: SerialNumber: 000000009909 usb 1-1.2: new high speed USB device using orion-ehci and address 4 usb 1-1.2: New USB device found, idVendor=0b95, idProduct=772a usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.2: Product: AX88x72A usb 1-1.2: Manufacturer: ASIX Elec. Corp. usb 1-1.2: SerialNumber: 000002 usb 1-1.3: new high speed USB device using orion-ehci and address 5 usb 1-1.3: New USB device found, idVendor=0781, idProduct=a3a4 usb 1-1.3: New USB device strings: Mfr=0, Product=4, SerialNumber=5 usb 1-1.3: Product: MobileMate SD+ usb 1-1.3: SerialNumber: 02692 udevd (427): /proc/427/oom_adj is deprecated, please use /proc/427/oom_score_adj instead. mdadm: No arrays found in config file No volume groups found mount: mounting /dev/sdc3 on /mnt failed: No such file or directory ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead. You can try to fix it. Type 'exit' when things are done. /bin/sh: can't access tty; job control turned off / # -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Sun Sep 26 10:09:51 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 26 Sep 2010 11:09:51 +0100 (BST) Subject: [ARMedslack] Slackware ARM 13.1 rc1 ready In-Reply-To: References: <4BF5CDBE.4060509@gmail.com> <4BF6AF97.9050304@gmail.com> Message-ID: > any reference to it in the u-boot git tree, nor in the Marvell u-boot > custodian tree, but after a bit of grepping on the source I've found you > can do the following with the u-boot installed on the GuruPlug, straight > out of the box: The factory u-boot does not have the "ext2load" function though, does it? So if you want to install to a USB/eSATA disc using the instructions (an ext2 /boot partition), then you can't; you'd have to faff around putting the kernel and initrd onto a FAT partition or something; or burning the kernel & initrd to flash. From m-lists at biscuit.org.uk Sun Sep 26 17:03:09 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 26 Sep 2010 18:03:09 +0100 (BST) Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: <4C9E748E.6050100@gmail.com> References: <4C9E748E.6050100@gmail.com> Message-ID: > I have only compiled a kernel and not updated the initrd. But it boots > up to that point. Granted I stripped out ALOT of modules and bits and [..] > /bin/sh: can't access tty; job control turned off Your kernel is fine. I guess whatever you have stripped out helps. But I am curious whether the kernel I built will boot on the guruplug. Could you test it? http://stash.armedslack.org/linux-2.6.36-rc5/ I wonder if it crashes on the openrd client which has the video chipset; and whether it'll work on a machine without it. I don't dare test on my sheevaplug since I don't have physical access to it. It'd be great if you could cause a system reboot via the JTAG cable but I don't think it is; otherwise I'd be much less cautious when upgrading kernels! -- Stuart Winter Slackware ARM: www.armedslack.org From thierry.merle at free.fr Sun Sep 26 20:26:24 2010 From: thierry.merle at free.fr (Thierry Merle) Date: Sun, 26 Sep 2010 22:26:24 +0200 Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: <20100925075405.784dd9ca@gorbag.houroukhai.org> References: <20100925075405.784dd9ca@gorbag.houroukhai.org> Message-ID: <20100926222624.18f52ced@gorbag.houroukhai.org> Le Sat, 25 Sep 2010 07:54:05 +0200, Thierry Merle a ?crit : > Le Fri, 24 Sep 2010 14:45:45 +0100 (BST), > Stuart Winter a ?crit : > > > > > Has anyone tried it? > > It compiles OK without patches (openrd-ultimate is included upstream > > now) but when booting, it's not so happy. > [...] > > [ 2.098298] [] (xgifb_probe+0x158/0x13fc) from > > [] (local_pci_probe+0x14/0x18) > [...] > Seems that there is a problem with the xgifb staging driver. > Just try to deactivate it... > If I have time this week-end I will compile this kernel on my > sheevaplug. > Compiled 2.6.36-rc5 this week-end and runs OK on my sheevaplug. I put xgifb as a module and when I load it manually, as expected, it is harmless. Thierry From thierry.merle at free.fr Sun Sep 26 20:50:34 2010 From: thierry.merle at free.fr (Thierry Merle) Date: Sun, 26 Sep 2010 22:50:34 +0200 Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: References: <4C9E748E.6050100@gmail.com> Message-ID: <20100926225034.65e2cca8@gorbag.houroukhai.org> Le Sun, 26 Sep 2010 18:03:09 +0100 (BST), Stuart Winter a ?crit : > > > I have only compiled a kernel and not updated the initrd. But it > > boots up to that point. Granted I stripped out ALOT of modules and > > bits and > > [..] > > /bin/sh: can't access tty; job control turned off > > Your kernel is fine. I guess whatever you have stripped out helps. > But I am curious whether the kernel I built will boot on the guruplug. > Could you test it? > > http://stash.armedslack.org/linux-2.6.36-rc5/ > > I wonder if it crashes on the openrd client which has the video > chipset; and whether it'll work on a machine without it. I don't > dare test on my sheevaplug since I don't have physical access to it. Tested OK your kernel image+initrd on my sheevaplug. Thierry From unixjohn1969 at gmail.com Mon Sep 27 01:10:54 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sun, 26 Sep 2010 21:10:54 -0400 Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: References: <4C9E748E.6050100@gmail.com> Message-ID: <4C9FEF1E.8030104@gmail.com> On 09/26/2010 01:03 PM, Stuart Winter wrote: > >> I have only compiled a kernel and not updated the initrd. But it boots >> up to that point. Granted I stripped out ALOT of modules and bits and > > [..] >> /bin/sh: can't access tty; job control turned off > > Your kernel is fine. I guess whatever you have stripped out helps. > But I am curious whether the kernel I built will boot on the guruplug. > Could you test it? > > http://stash.armedslack.org/linux-2.6.36-rc5/ root at guruslack:~# uname -a Linux guruslack 2.6.36rc5-kirkwood #2 PREEMPT Fri Sep 24 11:54:04 BST 2010 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell GuruPlug Reference Board GNU/Linux -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Mon Sep 27 15:21:24 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 27 Sep 2010 16:21:24 +0100 (BST) Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: <4C9FEF1E.8030104@gmail.com> References: <4C9E748E.6050100@gmail.com> <4C9FEF1E.8030104@gmail.com> Message-ID: > root at guruslack:~# uname -a > Linux guruslack 2.6.36rc5-kirkwood #2 PREEMPT Fri Sep 24 11:54:04 BST 2010 > armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell GuruPlug Reference Board > GNU/Linux hmph. Thanks for testing. I'll leave off 2.6.36 until someone with an openrd has tested it and hopefully found it's broken for them too. From m-lists at biscuit.org.uk Tue Sep 28 14:26:43 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 28 Sep 2010 15:26:43 +0100 (BST) Subject: [ARMedslack] Has anyone tried Linux 2.6.36-rc5? In-Reply-To: <20100926225034.65e2cca8@gorbag.houroukhai.org> References: <4C9E748E.6050100@gmail.com> <20100926225034.65e2cca8@gorbag.houroukhai.org> Message-ID: > Tested OK your kernel image+initrd on my sheevaplug. I made the driver into a module, so the kernel boots on my openrd too; but modprobing it causes ill messages to appear in syslog, although the box doesn't kernel panic; so it's an improvement! -- Stuart Winter Slackware ARM: www.armedslack.org