From carlo.caione at gmail.com Thu Nov 4 22:05:13 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Thu, 04 Nov 2010 23:05:13 +0100 Subject: [ARMedslack] ARM GCC Native compiling... Message-ID: <4CD32E19.4000605@gmail.com> Hi, during the development of slackedarm did you use slackbuilds? I'm trying to port slackware to a beagleboard (cortex-a8) using proper optimization for compiler (-mfpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 -mthumb -march=armv7-a) but i'm having big troubles especially during cross-compiling of GCC (to build native GCC for ARM)... Have you any suggestions in this sense? To build the native (ARM) GCC did you use the GCC version provided with slackware sources? Thank you, -- Carlo From unixjohn1969 at gmail.com Fri Nov 5 06:23:05 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 05 Nov 2010 02:23:05 -0400 Subject: [ARMedslack] NFS Kernel panic Message-ID: <4CD3A2C9.8000908@gmail.com> HEY! I finally got that NFS kernel panic that causes all my NFS mounts to hang while the console was attached. Running ktorrent on the plug with the data on the NFS shares. armedslack-current kernel from armedslack 13.1 root at guruslack:~# mount /dev/sdb2 on / type ext4 (rw,relatime,barrier=1,data=ordered) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sdb1 on /boot type vfat (rw) tmpfs on /dev/shm type tmpfs (rw) /dev/ubi0_0 on /mnt/debian type ubifs (ro) mrlinux:/root on /mnt/mrlinux/root type nfs (rw,addr=192.168.1.3) mrlinux:/t on /mnt/mrlinux/t type nfs (rw,addr=192.168.1.3) mrlinux:/z on /mnt/mrlinux/z type nfs (rw,addr=192.168.1.3) mrlinux:/y on /mnt/mrlinux/y type nfs (rw,addr=192.168.1.3) root at guruslack:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb2 7724692 3944836 3387464 54% / /dev/sdb1 32720 9574 23146 30% /boot tmpfs 257672 0 257672 0% /dev/shm /dev/ubi0_0 473324 190260 283064 41% /mnt/debian mrlinux:/root 71173888 36441600 34732288 52% /mnt/mrlinux/root mrlinux:/t 1442145280 1251308544 117579776 92% /mnt/mrlinux/t mrlinux:/z 245104384 231718400 13385984 95% /mnt/mrlinux/z mrlinux:/y 41294848 6363648 32833536 17% /mnt/mrlinux/y root at guruslack:~# Run for a bit and BLAMMO! Never had one happen so soon after booting though. Doesnt happen often but it happens... Seyon Copyright (c) 1992-1993 Muhammad M. Saggaf. All rights reserved. Version 2 rev. 20c i686-Linux root at tree 02/18/07 23:55:39. Locating Modems... Modem `/dev/ttyUSB0' is Available. >> Error: /OFV/ Could not open the file `startup' >> Notice: Tried the default directory `~/.seyon' >> Notice: Tried the current directory Welcome to Linux 2.6.33.5-kirkwood (ttyS0) guruslack login: [ 1841.302091] Unable to handle kernel NULL pointer dereference at virtual address 000007b3 [ 1841.313785] pgd = dede0000 [ 1841.317424] [000007b3] *pgd=1e64a031, *pte=00000000, *ppte=00000000 [ 1841.325352] Internal error: Oops: 801 [#1] PREEMPT [ 1841.330166] last sysfs file: /sys/devices/platform/leds-gpio/leds/guruplug:re d:wmode/brightness [ 1841.338902] Modules linked in: uap8xxx ipt_MASQUERADE iptable_nat nf_nat nf_c onntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ipv6 nls_utf8 nls_c p437 libertas_sdio btmrvl_sdio libertas asix btmrvl usbnet cfg80211 bluetooth li b80211 rfkill mv_cesa aes_generic mvsdio nfs lockd nfs_acl auth_rpcgss sunrpc mv 643xx_eth fscache xfs jfs reiserfs ext4 ext3 ext2 mbcache dm_mod md_mod exportfs jbd2 jbd vfat fat ums_onetouch ums_jumpshot ums_alauda ums_sddr55 ums_sddr09 um s_isd200 ums_freecom ums_usbat ums_cypress usb_storage usb_libusual ohci_hcd usb hid hid uhci_hcd ehci_hcd usbcore nls_base sata_mv libata mmc_block mmc_core scs i_tgt sr_mod cdrom sd_mod crc_t10dif sg scsi_mod [last unloaded: uap8xxx] [ 1841.401943] CPU: 0 Not tainted (2.6.33.5-kirkwood #2) [ 1841.407377] PC is at __kprobes_text_end+0x80c/0xadc [ 1841.412276] LR is at tcp_sendmsg+0x328/0xb08 [ 1841.416567] pc : [] lr : [] psr: 20000013 [ 1841.416574] sp : dfddfcb8 ip : 00000220 fp : 0000c040 [ 1841.428109] r10: d637e880 r9 : de2592dc r8 : 00000000 [ 1841.433359] r7 : f33a311e r6 : c207542a r5 : 000007b3 r4 : fffffff2 [ 1841.439917] r3 : b824ebe0 r2 : 000005a8 r1 : de943498 r0 : d637ec04 [ 1841.446475] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kern el [ 1841.453817] Control: 0005397f Table: 1e12c000 DAC: 00000017 [ 1841.459589] Process rpciod/0 (pid: 596, stack limit = 0xdfdde270) [ 1841.465711] Stack: (0xdfddfcb8 to 0xdfde0000) [ 1841.470089] fca0: de943118 000005a8 [ 1841.478317] fcc0: de259260 d29aa380 000005a8 00000000 00000000 c029fe00 dfddf d0c 00000004 [ 1841.486539] fce0: 0000c040 00000880 00000000 000005a8 dfdde000 000005a8 00000 780 fbc542e9 [ 1841.494762] fd00: 00000000 dfddfe48 0000c040 00000000 00000000 000005a8 0000c 040 d2a289a0 [ 1841.502985] fd20: 00001000 dfddfe2c d2a289a0 00000000 00000000 00003000 00011 f68 c025a5a0 [ 1841.511207] fd40: dfdde000 000005a8 00000000 00000001 ffffffff 00000000 00000 000 00000000 [ 1841.519431] fd60: 00000000 00000000 df842b60 d2a289a0 00000000 00000000 c1257 7fc 00000000 [ 1841.527654] fd80: dfddfdb8 00000000 00000000 c025a5a0 de3df0c0 de259260 00000 000 00000001 [ 1841.535876] fda0: ffffffff 00000000 00000000 00000000 00000000 00000000 df842 b60 c028a9dc [ 1841.544101] fdc0: 00000000 00001000 d2a289a0 80000000 00000000 dfddfe2c c0473 690 c0317924 [ 1841.552323] fde0: 00000000 c04746a8 de3df0c0 c0473690 00000040 c0291f70 00000 000 00000000 [ 1841.560547] fe00: 0001637e d637e000 00000038 c025a5f8 00001000 dfddfe2c 00016 37e c025da84 [ 1841.568769] fe20: 00001000 dfddfe7c 80000000 00000000 00000000 dfddfe48 00000 001 00000000 [ 1841.576992] fe40: 00000000 0000c040 d637e000 00001000 de259260 0000c040 d2a28 9a0 00000000 [ 1841.585215] fe60: 0000df68 c02a0624 0000c040 bf48e850 000000c0 c040cf04 00001 000 c003be00 [ 1841.593438] fe80: 00000000 00000000 df842b60 c0740fc0 dfddfedc c003c8d8 d290b 804 00001000 [ 1841.601661] fea0: c12577fc d2a289a0 00000000 0000df68 00000038 00003000 00011 f68 bf48e9a8 [ 1841.609884] fec0: 0000c040 00000000 00000000 de6582c8 00000000 c12577f8 de128 000 df29c204 [ 1841.618107] fee0: c12577fc bf4ad648 bf49105c fffffe00 00000000 bf48eb94 0000a 158 00000013 [ 1841.626330] ff00: dfddff28 c12577f8 de128000 df29c204 de128340 00000000 fffff e00 bf48c9a4 [ 1841.634553] ff20: df29c204 df29c204 c12577f8 bf4ad648 00000001 00000000 bf491 05c fffffe00 [ 1841.642777] ff40: 00000000 bf489f98 df29c204 00000000 a0000013 df29c204 df29c 24c bf491794 [ 1841.650999] ff60: df29c204 dfdde000 dfdd38c0 c0412d60 df29c25c df29c258 bf491 938 00000000 [ 1841.659222] ff80: dfdd38c8 c005bc90 00000000 00000000 00000000 00000000 df842 b60 c005fcb4 [ 1841.667445] ffa0: dfddffa0 dfddffa0 dfdd38c0 c1361e98 dfddffd4 c005ba88 dfdd3 8c0 00000000 [ 1841.675667] ffc0: 00000000 00000000 00000000 c005f848 00000000 00000000 dfddf fd8 dfddffd8 [ 1841.683890] ffe0: 00000000 00000000 00000000 00000000 00000000 c0028a74 e1a07 000 e1a04008 [ 1841.692114] Code: 00000000 00000000 e3e0400d e59b5004 (e5854000) [ 1841.715455] ---[ end trace 9025e4e6bf91ac72 ]--- At this point I log into the plug and do a df and it will hang the session root at guruslack:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb2 7724692 3944836 3387464 54% / /dev/sdb1 32720 9574 23146 30% /boot tmpfs 257672 0 257672 0% /dev/shm /dev/ubi0_0 473324 190260 283064 41% /mnt/debian I unplug and replugin the Guru each time or SUB on the console. -- === Never ask a geek why, just nod your head and slowly back away.=== +================================+==================================+ | John O'Donnell | | | (Sr. Systems Engineer, | http://juanisan.homeip.net | | Net Admin, Programmer, etc.) | E-Mail: unixjohn1969 at gmail.com | +================================+==================================+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson From m-lists at biscuit.org.uk Fri Nov 5 10:13:45 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 5 Nov 2010 10:13:45 +0000 (GMT) Subject: [ARMedslack] ARM GCC Native compiling... In-Reply-To: <4CD32E19.4000605@gmail.com> References: <4CD32E19.4000605@gmail.com> Message-ID: > during the development of slackedarm did you use slackbuilds? Yes but also a lot was done manually because some things won't build without other dependencies, so you need to build them differently (usually without a particular feature) to build bootstrap versions of them, then package by package recompile everything over and over until you can use the slackbuilds without modification. > I'm trying to port slackware to a beagleboard (cortex-a8) using proper > optimization for compiler (-mfpu=neon -mfloat-abi=softfp -mcpu=cortex-a8 > -mthumb -march=armv7-a) but i'm having big troubles especially during > cross-compiling of GCC (to build native GCC for ARM)... > Have you any suggestions in this sense? To build the native (ARM) GCC did you > use the GCC version provided with slackware sources? Check the armedslack-current/source/d/gcc directory and the gcc.SlackBuild. You'll find the patches I've applied in there. There's no gcc source in the armedslack tree because armedslack is built "against" the x86_64 source tree. This is described in armedslack-current/source/README.TXT After you've looked at the gcc.SlackBuild script, perhaps you could build your compiler natively on armedslack? I can't think of any reason it won't work, off the top of my head. -- Stuart Winter Slackware ARM: www.armedslack.org From carlo.caione at gmail.com Sun Nov 7 09:59:18 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Sun, 7 Nov 2010 10:59:18 +0100 Subject: [ARMedslack] ARM GCC Native compiling... In-Reply-To: References: <4CD32E19.4000605@gmail.com> Message-ID: <0FFCD672-B22A-47B5-8717-9A335784F95E@gmail.com> On Nov 5, 2010, at 11:13 AM, Stuart Winter wrote: [cut] > After you've looked at the gcc.SlackBuild script, perhaps you could build > your compiler natively on armedslack? I can't think of any reason it > won't work, off the top of my head. Oh yes, good idea.... I'll let you know... thank you... -- Carlo Caione From m-lists at biscuit.org.uk Sun Nov 7 20:38:55 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 7 Nov 2010 20:38:55 +0000 (GMT) Subject: [ARMedslack] A few questions on kirkwood initrd In-Reply-To: References: <4C4FC69B.9010204@gmail.com> <4C506986.7040904@gmail.com> Message-ID: [..] > Though I am using a serial cable, it's theoretically possible to do > this without the serial cable by using the fw_envset commands to alter > the mtd3 u-Boot from within the DockStar' stock Linux install in NAND. > Though the armedslack installer initrd startup scripts look like they > should launch dhcpcd and dropbear, neither actually happens on bootup > so I still had to run those commands via serial. If this were fixed, > then no serial cable would be necessary and the install could be > carried out purely via SSH. This isn't broken - it's by design - you have to specify the additional kernel parameters: nic=auto:eth0:dhcp So to boot the installer, bring up the network interface, request IP by DHCP and start SSHd: tftpboot 0x01100000 armedslack-current/uinitrd-kirkwood.img tftpboot 0x00800000 armedslack-current/uImage-kirkwood setenv bootargs console=ttyS0,115200 nodhcp kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;reset I've added this into the INSTALL_KIRKWOOD.TXT. From m-lists at biscuit.org.uk Sun Nov 7 20:49:31 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 7 Nov 2010 20:49:31 +0000 (GMT) Subject: [ARMedslack] A few questions on kirkwood initrd In-Reply-To: References: <4C4FC69B.9010204@gmail.com> <4C506986.7040904@gmail.com> Message-ID: > setenv bootargs console=ttyS0,115200 nodhcp kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;reset Obviously best to take out "nodhcp", although it still worked with it in: setenv bootargs console=ttyS0,115200 kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;reset -- Stuart Winter Slackware ARM: www.armedslack.org From claudio.cavalera at gmail.com Sun Nov 7 21:44:24 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Sun, 7 Nov 2010 22:44:24 +0100 Subject: [ARMedslack] A few questions on kirkwood initrd In-Reply-To: References: <4C4FC69B.9010204@gmail.com> <4C506986.7040904@gmail.com> Message-ID: Hello, I'm the cause of this thread's revival. I aim to be the first armed slacker without the serial cable. :-) I've patched the uboot with these commands on the dockstar: cd /tmp wget http://plugapps.com/os/pogoplug/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh ./install_uboot_mtd0.sh (it's the uboot from doozan: http://jeff.doozan.com/debian/uboot/ ) I've set up a netconsole like suggested here http://forum.doozan.com/read.php?3,14 and it's working so and so. The problem is that when I load the stuff from the tftpboot, but when I bootm the last thing I see on my netcat session is: Starting kernel... then I would expect my dockstar to be online in order to ssh in it and run setup, but it does not reply to ping. :-( I've tried the commands from Stuart as well as the commands from the original poster: setenv arcNumber 2097 setenv mainlineLinux yes usb start tftpboot 0x1800000 armedslack-13.1/uinitrd-kirkwood.img tftpboot 0x6000000 armedslack-13.1/uImage-kirkwood setenv bootargs console=ttyS0,115200 kbd=it nic=auto:eth0:dhcp root=/dev/ram rw bootm 0x6000000 0x1800000 The original poster also said something about an "uncompressed kernel" to be used with dockstar. http://blog.gmane.org/gmane.linux.slackware.armedslack/month=20100801 Could be this the reason of my problem? Thanks, Claudio On Sun, Nov 7, 2010 at 21:49, Stuart Winter wrote: > >> setenv bootargs console=ttyS0,115200 nodhcp kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;reset > > Obviously best to take out "nodhcp", although it still worked with it in: > > setenv bootargs console=ttyS0,115200 kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;reset > > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From claudio.cavalera at gmail.com Fri Nov 12 13:23:54 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Fri, 12 Nov 2010 14:23:54 +0100 Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: <201009151129.12028.thenktor@gmx.de> References: <201009151129.12028.thenktor@gmx.de> Message-ID: Thorsten, could you please provide some guidelines to put armed slack on the dockstar? I've explained where I'm stuck at, in the other thread on this ML. Thanks a lot, Claudio 2010/9/15 Thorsten M?hlfelder : > 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 > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From claudio.cavalera at gmail.com Sat Nov 13 20:03:44 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Sat, 13 Nov 2010 21:03:44 +0100 Subject: [ARMedslack] Armedslack on a dockstar :-) In-Reply-To: References: <201009151129.12028.thenktor@gmx.de> Message-ID: I'm clueless :-( Could someone point me in the right direction? I think all the info is already available here on the ML in different threads but I can't make sense of it, any guru who would go through the threads will easily spot what I'm missing! For example, what's the story with the uncompressed kernel image here http://blog.gmane.org/gmane.linux.slackware.armedslack/month=20100801 ? This is what I get with net console, after that I would like to ping the dockstar and ssh in it but it doesn't get an ip address. :-( Marvell>> tftpboot 0x1800000 armedslack-13.1/uinitrd.img Using egiga0 device TFTP from server 192.168.1.38; our IP address is 192.168.1.229 Filename 'armedslack-13.1/uinitrd.img'. Load address: 0x1800000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ########### done Bytes transferred = 14699044 (e04a24 hex) Marvell>> tftpboot 0x6000000 armedslack-13.1/uImage tftpboot 0x6000000 armedslack-13.1/uImage Using egiga0 device TFTP from server 192.168.1.38; our IP address is 192.168.1.229 Filename 'armedslack-13.1/uImage'. Load address: 0x6000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #################### done Bytes transferred = 2096780 (1ffe8c hex) Marvell>> usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Marvell>> setenv bootargs console=ttyS0,115200 nic=auto:eth0:dhcp root=/dev/ram rw; Marvell>> bootm 0x6000000 0x1800000 ## Booting kernel from Legacy Image at 06000000 ... Image Name: Linux-2.6.33.5-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2096716 Bytes = 2 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01800000 ... Image Name: Slackware ARM Installer Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 14698980 Bytes = 14 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... On Fri, Nov 12, 2010 at 14:23, Claudio Cavalera wrote: > Thorsten, > could you please provide some guidelines to put armed slack on the dockstar? > I've explained where I'm stuck at, in the other thread on this ML. > Thanks a lot, > Claudio > > 2010/9/15 Thorsten M?hlfelder : >> 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 >> _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > From claudio.cavalera at gmail.com Mon Nov 15 21:36:41 2010 From: claudio.cavalera at gmail.com (Claudio Cavalera) Date: Mon, 15 Nov 2010 22:36:41 +0100 Subject: [ARMedslack] Hello In-Reply-To: <4CE0143F.7090801@gmail.com> 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> <4CE0143F.7090801@gmail.com> Message-ID: Thx for your answer Richard! I've ccopied the ML because I think this stuff could be also useful to someone else. Are you also on the #armedslack IRC Channel on freenode? I really would like to install Slackware on my dockstar. I don't have made the serial cable yet :-) I'm sorry you have bricked your dockstar with the rescue system, is it broken or is it because of your mistake? (where have you bought your other dockstars? I can't find them anywhere in Europe anymore). Anyway could you please help me identify the proper sequence of commands ? It shouldn't be so long after one has done the tftp and NFS configuration part on a slackware server. I've summarized this one at the moment. My goal is to have the dockstar booting and getting an IP address from the DHCP router as it already does when it starts with pogoplug. This way I should be able to start the slackware installer by doing ssh into the dockstar and without the serial cable. If we can achieve this goal we could write a guide to share on armedslack also (if we double check the procedure). Here is what I'm doing, I'm missing something near the end, maybe the line with the dhcp part (so please read at least the last line :-) Unplug your internet. You don't want to accidentally stealth update the firmware Unplug your USB drives and boot to PogoPlug OS Log in via SSH as root, the default password is stxadmin, this may have changed if you registered with PogoPlug Remount the file system read and write with: mount / -rw -o remount edit or create /etc/hosts to add these lines: 127.0.0.1 service.pogoplug.com 127.0.0.1 pm1.pogoplug.com 127.0.0.1 pm2.pogoplug.com 127.0.0.1 service.cloudengines.com 127.0.0.1 upgrade.pogoplug.com save the file! Remount the file system back to read only: mount / -r -o remount Reboot: /sbin/reboot Install the new uboot version by Jeff Doozan: cd /tmp wget http://plugapps.com/os/pogoplug/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh ./install_uboot_mtd0.sh activate netconsole as explained here: http://forum.doozan.com/read.php?3,14,14 -bash-3.2# /usr/sbin/fw_setenv serverip 192.168.1.38 -bash-3.2# /usr/sbin/fw_setenv ipaddr 192.168.1.229 -bash-3.2# /usr/sbin/fw_setenv if_netconsole 'ping $serverip' -bash-3.2# /usr/sbin/fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;' -bash-3.2# /usr/sbin/fw_setenv preboot 'run if_netconsole start_netconsole' then on your linux pc 192.168.1.38: nc -l -u -p 6666 & nc -u 192.168.1.229 6666 # run killall -9 nc after you've finished to kill the background nc process; if you have problems I suggest run nc in foreground in two separate sessions (e.g. two shells or two screen sessions) Then enter the uboot prompt by pressing ENTER just after a reboot of the dockstar Marvell>> tftpboot 0x01100000 armedslack-13.1/uinitrd-kirkwood.img Marvell>> tftpboot 0x00800000 armedslack-13.1/uImage-kirkwood setenv bootargs console=ttyS0,115200 kbd=it nic=auto:eth0:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000;reset Thanks, Claudio On Sun, Nov 14, 2010 at 17:54, Rich wrote: > Hi Claudio, > Yes, I still read the armed slack mail list. Regarding getting armed slack > installed on my Dockstar, I first tried doing what Thorsten did, loading the > mini root file system onto a usb drive and renaming the kernel and uinitrd > to uImage, but it just resulted in getting the "Starting kernel" message and > continual reboots. So then yes I used those ?commands, following the armed > slack INSTALL_KIRKWOOD.TXT instructions and was able get armed slack running > on my Dockstar. I had it running for over a month, but just last week I > managed to semi-brick it installing Jeff Doozan Rescue System. ?Now all I > can do is boot into uboot. > I too would like to be able to install without a serial cable since I have > two more Dockstars that I want to get up and running. > Regards > Rich Lapointe > > On 11/13/2010 03:07 PM, Claudio Cavalera wrote: >> >> Hi Richard, >> do you still read the armed slack mailing list? could you please help >> me out a bit with my dockstar? >> Have you run this commands to install your dockstar? >> Thx, >> Claudio >> >> >> ?4.4 ?Booting the installer >> ? ? ? ? ?--------------------- >> >> ? ? ? ? ?Now download the Kernel and Slackware ARM installer via TFTP: >> >> ? ? ?Marvell>> ? ?tftpboot 0x01100000 armedslack-13.1/uinitrd-kirkwood.img >> ? ? ?Marvell>> ? ?tftpboot 0x00800000 armedslack-13.1/uImage-kirkwood >> ? ? ?Marvell>> ? ?setenv bootargs console=ttyS0,115200 nodhcp kbd=uk >> root=/dev/ram rw >> ? ? ?Marvell>> ? ?bootm 0x00800000 0x01100000 >> >> ? ? ? ? ? Note: >> ? ? ? ? ? ? The second line above ("setenv bootargs..") sets the keyboard >> ? ? ? ? ? ? setting to 'uk'. ?You may choose another such as "us", one one >> ? ? ? ? ? ? of the other valid keymaps. ?The installation will be >> conducted >> ? ? ? ? ? ? through SSH which uses your local keymap, but you may wish to >> ? ? ? ? ? ? set this keymap here since you'll need to type a few commands >> in >> ? ? ? ? ? ? once the installer has booted. >> >> ? ? ? ? ? ? For those of you who are familiar with the Slackware >> installer, >> ? ? ? ? ? ? you will note that you will not be presented with the option >> to >> ? ? ? ? ? ? select your keymap as soon as the installer has booted. ?This >> is >> ? ? ? ? ? ? because the cursor keys don't work properly in the menus over >> the >> ? ? ? ? ? ? serial console; but you can configure it later in the main >> 'setup' menu. >> >> >> >> >> On Fri, Sep 17, 2010 at 00:55, 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 >>> >>> >>> >>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> ARMedslack mailing list >>> ARMedslack at lists.armedslack.org >>> http://lists.armedslack.org/mailman/listinfo/armedslack >>> >>> >> >> > From pino.otto at gmail.com Wed Nov 17 19:18:23 2010 From: pino.otto at gmail.com (Giovanni) Date: Wed, 17 Nov 2010 20:18:23 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? Message-ID: Hello, I am a member of the Slackware italian community (Slacky). Together with other people I am trying to learn how to compile the full Slackware ARM, in order to make a port to the BeagleBoard and PandaBoard. I downloaded the full Slackware ARM tree and installed it on a PlugComputer successfully. Now I woud like to compile all the Slackware ARM packages from the sources. I searched the source files in the armedslack-13.1/source directory, but I found only the build scripts. Here are my questions: - where can I find the source files? - do I have to download them from the main original Slackware tree? - if so, what is the suggested way to structure the build environment (file tree, environment variables, scripts, etc.) - is there a way to make the full compile of all the packages by launching some scripts? - do I have to launch the slackbuild manually for each package? - is there an how-to guide for compiling the full Slackware? Best regards, giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Thu Nov 18 09:26:56 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 18 Nov 2010 09:26:56 +0000 (GMT) Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: References: Message-ID: > I am a member of the Slackware italian community (Slacky). Together with > other people I am trying to learn how to compile the full Slackware ARM, in > order to make a port to the BeagleBoard and PandaBoard. A port for it? It'll already run on the beagleboard. What is making you think that you need to do anything other than build a kernel? > I searched the source files in the armedslack-13.1/source directory, but I > found only the build scripts. Here are my questions: The instructions to build from source: ftp://ftp.armedslack.org/armedslack/armedslack-current/source/README_SOURCE.txt > - is there an how-to guide for compiling the full Slackware? No - it's an iterative process - some packages will just need building once, but some will require rebuilding several times throughout the process so that they can link against newly built libraries etc. -- Stuart Winter Slackware ARM: www.armedslack.org From carlo.caione at gmail.com Thu Nov 18 09:51:47 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Thu, 18 Nov 2010 10:51:47 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: References: Message-ID: <4CE4F733.3000309@gmail.com> On 18/11/2010 10:26, Stuart Winter wrote: > > >> I am a member of the Slackware italian community (Slacky). Together with >> other people I am trying to learn how to compile the full Slackware ARM, in >> order to make a port to the BeagleBoard and PandaBoard. > > A port for it? It'll already run on the beagleboard. > What is making you think that you need to do anything other than build a > kernel? Ok, I hijack the discussion. As I explained before in my previous email the idea is to recompile armedslack with the right optimization for beaglebord (armv7 + neon + cortex-a8 optimization) and provide also a preconfigured omap-patched kernel, in addition to second and third stage bootloader (xloader and uboot) for beagleboard. That's the base idea of the project. Thank you, -- Carlo Caione From thenktor at gmx.de Thu Nov 18 10:05:54 2010 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 18 Nov 2010 11:05:54 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: <4CE4F733.3000309@gmail.com> References: <4CE4F733.3000309@gmail.com> Message-ID: <201011181105.54766.thenktor@gmx.de> Am Thursday 18 November 2010 10:51:47 schrieb Carlo Caione: > Ok, I hijack the discussion. > As I explained before in my previous email the idea is to recompile > armedslack with the right optimization for beaglebord (armv7 + neon + > cortex-a8 optimization) How much speed improvement can be gained by this, e.g. at Vorbis/Flac encoding or at compiling? From carlo.caione at gmail.com Thu Nov 18 10:41:57 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Thu, 18 Nov 2010 11:41:57 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: <201011181105.54766.thenktor@gmx.de> References: <4CE4F733.3000309@gmail.com> <201011181105.54766.thenktor@gmx.de> Message-ID: <4CE502F5.3050706@gmail.com> On 18/11/2010 11:05, Thorsten M?hlfelder wrote: > Am Thursday 18 November 2010 10:51:47 schrieb Carlo Caione: >> Ok, I hijack the discussion. >> As I explained before in my previous email the idea is to recompile >> armedslack with the right optimization for beaglebord (armv7 + neon + >> cortex-a8 optimization) > > How much speed improvement can be gained by this, e.g. at Vorbis/Flac encoding > or at compiling? Good point. I'm not sure, but I think that support for NEON could ensure a good speed up. Here some pointers (not mine), about performance for different compilers (but same parameters): http://hardwarebug.org/2009/08/05/arm-compiler-shoot-out/ From thenktor at gmx.de Thu Nov 18 11:17:06 2010 From: thenktor at gmx.de (Thorsten =?iso-8859-1?q?M=FChlfelder?=) Date: Thu, 18 Nov 2010 12:17:06 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: <4CE502F5.3050706@gmail.com> References: <201011181105.54766.thenktor@gmx.de> <4CE502F5.3050706@gmail.com> Message-ID: <201011181217.06165.thenktor@gmx.de> Am Thursday 18 November 2010 11:41:57 schrieb Carlo Caione: > Here some pointers (not mine), about performance for different compilers > (but same parameters): > > http://hardwarebug.org/2009/08/05/arm-compiler-shoot-out/ > Thanks for providing this link. As I can see there FLAC uses integer and Vorbis uses float. So rebuilding the libvorbis and flac packages should be the easiest method to get some test tools for different compiler optimizations. Does anybody want to do it? ;-) From carlo.caione at gmail.com Thu Nov 18 12:03:50 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Thu, 18 Nov 2010 13:03:50 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: <201011181217.06165.thenktor@gmx.de> References: <201011181105.54766.thenktor@gmx.de> <4CE502F5.3050706@gmail.com> <201011181217.06165.thenktor@gmx.de> Message-ID: <4CE51626.8020606@gmail.com> On 18/11/2010 12:17, Thorsten M?hlfelder wrote: > Am Thursday 18 November 2010 11:41:57 schrieb Carlo Caione: >> Here some pointers (not mine), about performance for different compilers >> (but same parameters): >> >> http://hardwarebug.org/2009/08/05/arm-compiler-shoot-out/ >> > > Thanks for providing this link. As I can see there FLAC uses integer and > Vorbis uses float. So rebuilding the libvorbis and flac packages should be > the easiest method to get some test tools for different compiler > optimizations. > Does anybody want to do it? ;-) Ok, I'll let you know :) [no deadline pls ;)] -- Carlo From m-lists at biscuit.org.uk Thu Nov 18 13:16:53 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 18 Nov 2010 13:16:53 +0000 (GMT) Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: <4CE51626.8020606@gmail.com> References: <201011181105.54766.thenktor@gmx.de> <4CE502F5.3050706@gmail.com> <201011181217.06165.thenktor@gmx.de> <4CE51626.8020606@gmail.com> Message-ID: > > > Here some pointers (not mine), about performance for different compilers > > > (but same parameters): > > > > > > http://hardwarebug.org/2009/08/05/arm-compiler-shoot-out/ > > > > > > > Thanks for providing this link. As I can see there FLAC uses integer and > > Vorbis uses float. So rebuilding the libvorbis and flac packages should be > > the easiest method to get some test tools for different compiler > > optimizations. > > Does anybody want to do it? ;-) I think this makes the most sense. You'd probably also want to rebuild glibc, but I don't think rebuilding the entire distribution would be worthwhile -- because I'm not convinced about the speed improvement *and* how long it'd take to build the packages: it's not a fast process. -- Stuart Winter Slackware ARM: www.armedslack.org From carlo.caione at gmail.com Thu Nov 18 14:16:36 2010 From: carlo.caione at gmail.com (Carlo Caione) Date: Thu, 18 Nov 2010 15:16:36 +0100 Subject: [ARMedslack] How to compile the whole Slackware ARM? In-Reply-To: References: <201011181105.54766.thenktor@gmx.de> <4CE502F5.3050706@gmail.com> <201011181217.06165.thenktor@gmx.de> <4CE51626.8020606@gmail.com> Message-ID: <4CE53544.5090703@gmail.com> On 18/11/2010 14:16, Stuart Winter wrote: > >>>> Here some pointers (not mine), about performance for different compilers >>>> (but same parameters): >>>> >>>> http://hardwarebug.org/2009/08/05/arm-compiler-shoot-out/ >>>> >>> >>> Thanks for providing this link. As I can see there FLAC uses integer and >>> Vorbis uses float. So rebuilding the libvorbis and flac packages should be >>> the easiest method to get some test tools for different compiler >>> optimizations. >>> Does anybody want to do it? ;-) > > I think this makes the most sense. You'd probably also want to rebuild > glibc, but I don't think rebuilding the entire distribution would be > worthwhile -- because I'm not convinced about the speed improvement *and* > how long it'd take to build the packages: it's not a fast process. Agree. So far as concerns me, I'm interested now in a very minimal distro (no X and superfluous packages). Anyway ASAP I'll try to use armedslack with beagle without recompiling anything (just a well-patched kernel). Thank you, -- Carlo Caione From blair.hoddinott at gmail.com Mon Nov 22 23:49:17 2010 From: blair.hoddinott at gmail.com (Blair Hoddinott) Date: Mon, 22 Nov 2010 18:49:17 -0500 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus Message-ID: Hello All, First off, I wanted to say hello to the armed slack community! Been a long time follower and lover of Slackware for many, many, many years. When I got my first plug a while ago (a SheevaPlug) I stumbled across the Armedslack tree and was in heaven. Everything worked great and I was in bliss. So when the new GuruPlugs came out, I bought 2 and some hard drives and excitedely waited for their arrival, and grabbed a fresh copy of the 13.1 tree to await their arrival. Well, they came and that's when the fun started. With my first plug (the Sheeva) the powersupply gave up its ghost, so I figured I would just move the USB hard drive over to the new guruplug, set the boot paramaters in the NAND and then I'd be off to the races! Well, after several days of trying to get it to work, I gave up figuring that maybe the USB boot wouldn't cut it. I went out this weekend and grabbed up a nice 2TB sata drive, with an eSATA enclosure and got my heart set on ArmedSlack over eSATA with my GuruPlug. Nothing can stop me now! I went through the installation document meticulously, and the installation went through without a hitch. It worked great! Until it came time to reboot. My heart sank when through the JTAG I saw the all-too-familliar: ext2load -- command not found This is after I had gone through and updated to the u-boot.bin file pointed out in the docs. I confirmed the version with what was in the help file, so after a bit of searching I grabbed the uboot.kwb file from this page: http://plugcomputer.org/index.php/us/resources/downloads?func=select&id=15 To be fair, I also grabbed the one from this mailing list, which I found here: http://oinkzwurgl.org/guruplug_uboot Even still, after using those versions of uboot, I have this: ... Hit any key to stop autoboot: 0 Unknown command 'ide' - try 'help' ** Block device ide 1 not supported ** Block device ide 1 not supported Wrong Image Format for bootm command ERROR: can't get kernel image! resetting ... ... I've searched for hours, and have come across the same posts time and time again. I've tried modifying the boot parameters for ide 1:0, 0:0, 0:1... all to no avail. Am I missing something basic? Let me know if you need any more info. Thanks in advance! _B -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Tue Nov 23 20:26:52 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 23 Nov 2010 20:26:52 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: Message-ID: > With my first plug (the Sheeva) the powersupply gave up its ghost, so I > figured I would just move the USB hard drive over to the new guruplug, set > the boot paramaters in the NAND and then I'd be off to the races! Well, > after several days of trying to get it to work, I gave up figuring that > maybe the USB boot wouldn't cut it. Well, it should work assuming you're using the kernel supplied with ARMedslack. > This is after I had gone through and updated to the u-boot.bin file pointed > out in the docs. I confirmed the version with what was in the help file, so > after a bit of searching I grabbed the uboot.kwb file from this page: I thought that the one I was linking to at: http://www.armedslack.org/maint_kirkwooduboot contained the ext2load command, but running strings on it doesn't find it. Jawkins - do you have the u-boot binary you built from the Marvell sources? does it have ext2 & eSATA support? -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Wed Nov 24 10:38:29 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 24 Nov 2010 10:38:29 +0000 (GMT) Subject: [ARMedslack] Anybody with an OpenRD? Message-ID: Hi As some of you may have noticed, I included a paragraph about the console looking "interlaced" on my OpenRD client. I don't have immediate access to the ARMedslack development systems at the moment, so I cannot test kernels to check my theory about whether compiling the XGI driver into the kernel makes a difference or not. Is anybody able to test this? I can build a test kernel which has the driver compiled in, if so. -- Stuart Winter Slackware ARM: www.armedslack.org From jawkins at armedslack.org Sun Nov 28 10:48:10 2010 From: jawkins at armedslack.org (Jim Hawkins) Date: Sun, 28 Nov 2010 10:48:10 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: Message-ID: On Tue, 23 Nov 2010, Stuart Winter wrote: > Jawkins - do you have the u-boot binary you built from the Marvell > sources? does it have ext2 & eSATA support? I never actually got round to building it in the end, but looking at the latest u-boot git repo, it looks like the GuruPlug should have ext2 and SATA enabled by default. Cheers, Jim From m-lists at biscuit.org.uk Sun Nov 28 12:44:01 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 28 Nov 2010 12:44:01 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: Message-ID: > I never actually got round to building it in the end, but looking at the > latest u-boot git repo, it looks like the GuruPlug should have ext2 and > SATA enabled by default. OK. I've just looked at this: http://oinkzwurgl.org/guruplug_uboot and downloaded the binaries. Running strings over u-boot.bin (from the tar archive) shows it has ext2load: perhaps you want to try using this u-boot binary for convenience? From rw at rlworkman.net Sun Nov 28 15:43:31 2010 From: rw at rlworkman.net (Robby Workman) Date: Sun, 28 Nov 2010 09:43:31 -0600 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: Message-ID: <20101128094331.506cdab1@liberty> On Sun, 28 Nov 2010 12:44:01 +0000 (GMT) Stuart Winter wrote: > I've just looked at this: > http://oinkzwurgl.org/guruplug_uboot > and downloaded the binaries. Running strings over u-boot.bin (from > the tar archive) shows it has ext2load: perhaps you want to try using > this u-boot binary for convenience? Well, it's *slow* loading the stuff this way (but maybe I'm just used to pulling from the nand), and it worked the first two times I booted, but now it just hangs after "booting the kernel": NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 0 (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 5 USB Device(s) found scanning bus for storage devices... Device NOT ready Request Sense returned 02 3A 00 2 Storage Device(s) found Loading file "uinitrd-kirkwood" from usb device 1:1 (usbdb1) 7819143 bytes read Loading file "uImage-kirkwood" from usb device 1:1 (usbdb1) 2012420 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.36-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2012356 Bytes = 1.9 MiB 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: 7819079 Bytes = 7.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. *** yep,that's it *** Here's the environment info: GuruPlug>> version U-Boot 2010.09-02612-g27fb783-dirty (Nov 11 2010 - 22:51:37) Marvell-GuruPlug (-: flipflip's version 20101111 :-) GuruPlug>> printenv arcNumber=2659 baudrate=115200 bootargs_console=console=ttyS0,115200 bootargs_root=root=/dev/sdb2 waitforroot=10 rootfs=ext4 bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; run bootcmd_slack; bootcmd_slack=bootm 0x00800000 0x01100000 bootcmd_usb=usb start; ext2load usb 1:1 0x01100000 uinitrd-kirkwood; ext2load usb 1:1 0x00800000 uImage-kirkwood bootdelay=3 eth1addr=02:50:43:eb:75:43 ethact=egiga0 ethaddr=00:50:43:01:5D:EA filesize=1EB504 ipaddr=192.168.13.1 mainlineLinux=yes serverip=192.168.13.11 stderr=serial stdin=serial stdout=serial Environment size: 612/131068 bytes -RW From unixjohn1969 at gmail.com Sun Nov 28 15:57:13 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Sun, 28 Nov 2010 10:57:13 -0500 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: <20101128094331.506cdab1@liberty> References: <20101128094331.506cdab1@liberty> Message-ID: You are booting from ext. It is HIDEOUSLY slow. I make a small FAT partition and boot from that on the guru usb. ** This message has been delivered via a Google Android ** On Nov 28, 2010 10:43 AM, "Robby Workman" wrote: On Sun, 28 Nov 2010 12:44:01 +0000 (GMT) Stuart Winter wrote: > I've just ... Well, it's *slow* loading the stuff this way (but maybe I'm just used to pulling from the nand), and it worked the first two times I booted, but now it just hangs after "booting the kernel": NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 0 (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 5 USB Device(s) found scanning bus for storage devices... Device NOT ready Request Sense returned 02 3A 00 2 Storage Device(s) found Loading file "uinitrd-kirkwood" from usb device 1:1 (usbdb1) 7819143 bytes read Loading file "uImage-kirkwood" from usb device 1:1 (usbdb1) 2012420 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.36-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2012356 Bytes = 1.9 MiB 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: 7819079 Bytes = 7.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. *** yep,that's it *** Here's the environment info: GuruPlug>> version U-Boot 2010.09-02612-g27fb783-dirty (Nov 11 2010 - 22:51:37) Marvell-GuruPlug (-: flipflip's version 20101111 :-) GuruPlug>> printenv arcNumber=2659 baudrate=115200 bootargs_console=console=ttyS0,115200 bootargs_root=root=/dev/sdb2 waitforroot=10 rootfs=ext4 bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; run bootcmd_slack; bootcmd_slack=bootm 0x00800000 0x01100000 bootcmd_usb=usb start; ext2load usb 1:1 0x01100000 uinitrd-kirkwood; ext2load usb 1:1 0x00800000 uImage-kirkwood bootdelay=3 eth1addr=02:50:43:eb:75:43 ethact=egiga0 ethaddr=00:50:43:01:5D:EA filesize=1EB504 ipaddr=192.168.13.1 mainlineLinux=yes serverip=192.168.13.11 stderr=serial stdin=serial stdout=serial Environment size: 612/131068 bytes -RW _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From linuxxr at yahoo.com Sun Nov 28 16:15:32 2010 From: linuxxr at yahoo.com (Brian Kelley) Date: Sun, 28 Nov 2010 08:15:32 -0800 (PST) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: <20101128094331.506cdab1@liberty> Message-ID: <776004.68970.qm@web52401.mail.re2.yahoo.com> has anybody tried using Qi? instead of uboot? --- On Sun, 11/28/10, Robby Workman wrote: From: Robby Workman Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus To: "Slackware ARM port" Date: Sunday, November 28, 2010, 9:43 AM On Sun, 28 Nov 2010 12:44:01 +0000 (GMT) Stuart Winter wrote: > I've just looked at this: > http://oinkzwurgl.org/guruplug_uboot > and downloaded the binaries.? Running strings over u-boot.bin (from > the tar archive) shows it has ext2load: perhaps you want to try using > this u-boot binary for convenience? Well, it's *slow* loading the stuff this way (but maybe I'm just used to pulling from the nand), and it worked the first two times I booted, but now it just hangs after "booting the kernel": NAND:? 512 MiB In:? ? serial Out:???serial Err:???serial Net:???egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot:? 0 (Re)start USB... USB:???Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 5 USB Device(s) found ? ? ???scanning bus for storage devices... Device NOT ready ???Request Sense returned 02 3A 00 2 Storage Device(s) found Loading file "uinitrd-kirkwood" from usb device 1:1 (usbdb1) 7819143 bytes read Loading file "uImage-kirkwood" from usb device 1:1 (usbdb1) 2012420 bytes read ## Booting kernel from Legacy Image at 00800000 ... ???Image Name:???Linux-2.6.36-kirkwood ???Image Type:???ARM Linux Kernel Image (uncompressed) ???Data Size:? ? 2012356 Bytes = 1.9 MiB ???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:? ? 7819079 Bytes = 7.5 MiB ???Load Address: 00000000 ???Entry Point:? 00000000 ???Verifying Checksum ... OK ???Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. *** yep,that's it *** Here's the environment info: GuruPlug>> version U-Boot 2010.09-02612-g27fb783-dirty (Nov 11 2010 - 22:51:37) Marvell-GuruPlug (-: flipflip's version 20101111 :-) GuruPlug>> printenv arcNumber=2659 baudrate=115200 bootargs_console=console=ttyS0,115200 bootargs_root=root=/dev/sdb2 waitforroot=10 rootfs=ext4 bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; run bootcmd_slack; bootcmd_slack=bootm 0x00800000 0x01100000 bootcmd_usb=usb start; ext2load usb 1:1 0x01100000 uinitrd-kirkwood; ext2load usb 1:1 0x00800000 uImage-kirkwood bootdelay=3 eth1addr=02:50:43:eb:75:43 ethact=egiga0 ethaddr=00:50:43:01:5D:EA filesize=1EB504 ipaddr=192.168.13.1 mainlineLinux=yes serverip=192.168.13.11 stderr=serial stdin=serial stdout=serial Environment size: 612/131068 bytes -RW _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From blair.hoddinott at gmail.com Sun Nov 28 19:18:54 2010 From: blair.hoddinott at gmail.com (blair.hoddinott at gmail.com) Date: Sun, 28 Nov 2010 19:18:54 +0000 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: References: Message-ID: <173170425-1290971934-cardhu_decombobulator_blackberry.rim.net-612887520-@bda2673.bisx.prod.on.blackberry> Yeah, I've tried that uboot (in my OP), but still no joy. It comes up with bad block device. This makes me think it doesn't see the esata. Before, using that uboot to my usb drive, results in the hang at uncompressing linux which Ron is experiencing. _B Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Stuart Winter Sender: armedslack-bounces at lists.armedslack.org Date: Sun, 28 Nov 2010 12:44:01 To: Slackware ARM port Reply-To: Slackware ARM port Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus > I never actually got round to building it in the end, but looking at the > latest u-boot git repo, it looks like the GuruPlug should have ext2 and > SATA enabled by default. OK. I've just looked at this: http://oinkzwurgl.org/guruplug_uboot and downloaded the binaries. Running strings over u-boot.bin (from the tar archive) shows it has ext2load: perhaps you want to try using this u-boot binary for convenience? _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Mon Nov 29 07:03:14 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 29 Nov 2010 07:03:14 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: On Sun, 28 Nov 2010, John O'Donnell wrote: > You are booting from ext. It is HIDEOUSLY slow. I make a small FAT partition > and boot from that on the guru usb. This must be something to do with the Guruplug. I boot from an ext2 partition on my sheevaplugs and openrd (which has an eSATA drive) and it takes a couple of seconds to load both the kernel & initrd. From blair.hoddinott at gmail.com Mon Nov 29 07:11:40 2010 From: blair.hoddinott at gmail.com (blair.hoddinott at gmail.com) Date: Mon, 29 Nov 2010 07:11:40 +0000 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: <143197444-1291014700-cardhu_decombobulator_blackberry.rim.net-1603317200-@bda2673.bisx.prod.on.blackberry> This was my experience with the sheevaplug as well. Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Stuart Winter Sender: armedslack-bounces at lists.armedslack.org Date: Mon, 29 Nov 2010 07:03:14 To: Slackware ARM port Reply-To: Slackware ARM port Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus On Sun, 28 Nov 2010, John O'Donnell wrote: > You are booting from ext. It is HIDEOUSLY slow. I make a small FAT partition > and boot from that on the guru usb. This must be something to do with the Guruplug. I boot from an ext2 partition on my sheevaplugs and openrd (which has an eSATA drive) and it takes a couple of seconds to load both the kernel & initrd. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Mon Nov 29 10:23:16 2010 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 29 Nov 2010 10:23:16 +0000 (GMT) Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: <143197444-1291014700-cardhu_decombobulator_blackberry.rim.net-1603317200-@bda2673.bisx.prod.on.blackberry> References: <20101128094331.506cdab1@liberty> <143197444-1291014700-cardhu_decombobulator_blackberry.rim.net-1603317200-@bda2673.bisx.prod.on.blackberry> Message-ID: > This was my experience with the sheevaplug as well. The SheevaPlug's USB was a bit flaky though, so I'm not *that* surprised; but using the u-boot linked from the armedslack web site, my two boot very quickly off USB, and the OpenRD is also fine. I wouldn't recommend a FAT partition since installpkg won't be able to create the symlinks for the kernel package -- but as long as you're aware of this, you can fix it up manually. Whatever works :) From blair.hoddinott at gmail.com Mon Nov 29 14:57:32 2010 From: blair.hoddinott at gmail.com (blair.hoddinott at gmail.com) Date: Mon, 29 Nov 2010 14:57:32 +0000 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: References: <20101128094331.506cdab1@liberty> Message-ID: <1770277144-1291042654-cardhu_decombobulator_blackberry.rim.net-1197064690-@bda2673.bisx.prod.on.blackberry> Sorry, I meant to say that my experience was it booting no problem from the sheevaplug. Nothing but problems with the guruplug... I'm starting to think its a lost cause. _B Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Stuart Winter Sender: armedslack-bounces at lists.armedslack.org Date: Mon, 29 Nov 2010 07:03:14 To: Slackware ARM port Reply-To: Slackware ARM port Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server Plus On Sun, 28 Nov 2010, John O'Donnell wrote: > You are booting from ext. It is HIDEOUSLY slow. I make a small FAT partition > and boot from that on the guru usb. This must be something to do with the Guruplug. I boot from an ext2 partition on my sheevaplugs and openrd (which has an eSATA drive) and it takes a couple of seconds to load both the kernel & initrd. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From unixjohn1969 at gmail.com Mon Nov 29 16:57:52 2010 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Mon, 29 Nov 2010 11:57:52 -0500 Subject: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus In-Reply-To: References: <20101128094331.506cdab1@liberty> <1770277144-1291042654-cardhu_decombobulator_blackberry.rim.net-1197064690-@bda2673.bisx.prod.on.blackberry> Message-ID: Oh my problems were only with the GuruPlug as far as ext booting is concerned. Never with the Sheeva plug. And I do what Stuart says and maintain the /boot manually since FAT doesn't handle sym-links. ** This message has been delivered via a Google Android ** On Nov 29, 2010 9:57 AM, wrote: Sorry, I meant to say that my experience was it booting no problem from the sheevaplug. Nothing but problems with the guruplug... I'm starting to think its a lost cause. _B Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Stu... On Sun, 28 Nov 2010, John O'Donnell wrote: > You are booting from ext. It is HIDEOUSLY slow. I make... -------------- next part -------------- An HTML attachment was scrubbed... URL: