From slothpuck at gmail.com Sat Mar 3 20:15:45 2012 From: slothpuck at gmail.com (lee jones) Date: Sat, 3 Mar 2012 20:15:45 +0000 Subject: [ARMedslack] Armedslack on WM8650 Message-ID: Hello all :) Was just wondering if anyone had tried to get armedslack to run on one of these devices at all? They're sort of a very cheap (found on ebay) small netbook -- WM8650 cpu @ 800mhz, 800x480 screen, 256mb and keyboard. They come in both netbook and tablet configurations, I'm using the netbook version. Found a couple of other distros others had made/ported, namely debian and angstrom. Though it somehow looks like it uses the android kernel in conjuction with those distros in some way. I've briefly tried downloading the debian-based distro and replacing it with armedslack (it comes in two seconds - a fat section and a ext2 section). The idea is to create 2 partitions on an sd card, forat the first as fat, the second ext2 and then extract. Though I found if I replaced the distro (the files on the ext2 section) all it would do is lock up. The first part is just the boot loader and kernel (uzImage). I guess it would need a special compile to get armedslack working. Some links btw; http://www.slatedroid.com/topic/21211-7-wm8650-netbook-linux-port/ http://openwm8650.org/web/ http://www.slatedroid.com/topic/28914-wm8650-angstrom-linux-with-gnome-desktop/ ftp://ftp.gpl-devices.org/pub/vendors/Wondermedia/WM8650/ ljones -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Mar 5 07:26:27 2012 From: louigi600 at yahoo.it (Davide) Date: Mon, 5 Mar 2012 07:26:27 +0000 (GMT) Subject: [ARMedslack] Armedslack on WM8650 In-Reply-To: References: Message-ID: <1330932387.18654.YahooMailNeo@web29701.mail.ird.yahoo.com> You will just need to compile a kernel ... the userland should run on that hardware. I did the same sort of thing to get armedslack working on an AC100. Regards David ________________________________ Da: lee jones A: armedslack at lists.armedslack.org Inviato: Sabato 3 Marzo 2012 21:15 Oggetto: [ARMedslack] Armedslack on WM8650 Hello all :) Was just wondering if anyone had tried to get armedslack to run on one of these devices at all? They're sort of a very cheap (found on ebay) small netbook -- WM8650 cpu @ 800mhz, 800x480 screen, 256mb and keyboard. They come in both netbook and tablet configurations, I'm using the netbook version. Found a couple of other distros others had made/ported, namely debian and angstrom. Though it somehow looks like it uses the android kernel in conjuction with those distros in some way. I've briefly tried downloading the debian-based distro and replacing it with armedslack (it comes in two seconds - a fat section and a ext2 section). The idea is to create 2 partitions on an sd card, forat the first as fat, the second ext2 and then extract. Though I found if I replaced the distro (the files on the ext2 section) all it would do is lock up. The first part is just the boot loader and kernel (uzImage). I guess it would need a special compile to get armedslack working. Some links btw; http://www.slatedroid.com/topic/21211-7-wm8650-netbook-linux-port/ http://openwm8650.org/web/ http://www.slatedroid.com/topic/28914-wm8650-angstrom-linux-with-gnome-desktop/ ftp://ftp.gpl-devices.org/pub/vendors/Wondermedia/WM8650/ ljones _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthony.debeus at gmail.com Sun Mar 18 21:59:54 2012 From: anthony.debeus at gmail.com (debeus) Date: Sun, 18 Mar 2012 14:59:54 -0700 Subject: [ARMedslack] ARMEDSlack on the ix2-200 Message-ID: <1332107994.3116.20.camel@critters> Hello fellow ARMEDSlackers, I've been installing on the ix2-200 Cloud Edition, a low cost NAS with two SATA drives, a wired gigabit ethernet port and a few usb ports. Everything's working but the LEDs, the buttons and a little odd problem with the RAID setup. See below for details. First thing I did was plug in a serial/TTL ftdi cable to access the serial console. The instructions/pin-outs can be found on http://iomega.nas-central.org/wiki/Category:Ix2-200 but are Pin 1 VCC (3.3V) Pin 2 TxD Pin 3 GND Pin 4 RxD Pretty much you can follow directions for the Marvell kirkwood series; I also found this: http://blog.nobiscuit.com/ tremendously helpful. There's a patch for controlling the LEDs and buttons, which successfully applies to 3.2.6 (-current). I've compiled it, but haven't run it yet because I'm trying to figure out my RAID problem first. Installation in a nutshell: (nearly identical to the above source and the ARMEDSlackware Marvell-kirkwood instructions) For the ix2-200 systems: Marvell>> setenv arcNumber 1682 Marvell>> setenv ethaddr AA:00:00:00:00:01 Marvell>> setenv mainlineLinux yes Marvell>> saveenv Marvell>> reset I decided to install to the built in ide, but you can use an external usb drive as well. Just be aware that the usb drive will reorder the names of the ide drives. ie sda becomes sdc, etc. I also had a conflict between the usb drives and a usb printer on boot (making the drives not recognized by uboot), but it may just be that particular printer. You have to use eth1 not eth0. After install you also need to modify rc.inet1.conf to replace eth0 with eth1 (change the DHCP="yes" to "" and vice versa) Marvell>> ide reset Marvell>> tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img Marvell>> tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood Marvell>> setenv bootargs console=ttyS0,115200 kbd=us nic=auto:eth1:dhcp root=/dev/ram rw;bootm 0x00800000 0x01100000 After install to disk: setenv bootargs_console 'console=ttyS0,115200 kbd=us nic=auto:eth1:dhcp mtdparts=orion_nand:0x300000 at 0x100000(uImage),0x1000000 at 0x540000(uInitrd)' setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4' setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_slk ; reset' setenv bootcmd_slk 'ide reset;ext2load ide 0:1 0x01100000 /uinitrd-kirkwood;ext2load ide 0:1 0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000' saveenv reset Note that I setup the mtdparts for flashing the NAND with the kernel and initrd, but I haven't done that part ..yet. I'm running -current on it. There are a few curiosities. I reformatted the disks, because they were GPT and uBoot doesn't do GPT. Clearly, the modified debian kernel and initrd in flash mounted the RAID on GPT, but that seemed entirely too precarious to mess with for a first installation. I followed the suggestions on the ARMEDSlackware installation, with the exception that I made a fourth partition setup as RAID-1 for storing data. The slackware installer recognizes and starts my RAID drives, but the installed kernel and initrd do not, and give the following error: from dmesg [ 27.885568] mdadm: sending ioctl 1261 to a partition! [ 27.891016] mdadm: sending ioctl 1261 to a partition! [ 27.896092] mdadm: sending ioctl 1261 to a partition! [ 27.968245] md: md0 stopped. [ 27.981895] md: bind [ 27.999198] md: bind [ 28.056769] bio: create slab at 1 [ 28.079794] md: personality for level 1 is not loaded! from mdadm -D /dev/md0 State : active, Not Started whereas the installer dmesg states: [ 25.321046] mdadm: sending ioctl 1261 to a partition! [ 25.321065] mdadm: sending ioctl 1261 to a partition! [ 25.324330] mdadm: sending ioctl 1261 to a partition! [ 25.324348] mdadm: sending ioctl 1261 to a partition! [ 25.778956] md: bind [ 25.813034] md: bind [ 25.830783] md: raid1 personality registered for level 1 [ 25.831386] bio: create slab at 1 [ 25.831633] md/raid1:md127: active with 2 out of 2 mirrors [ 25.831768] md127: detected capacity change from 0 to 977827812352 [ 25.851975] md127: unknown partition table [ 26.155539] md127: detected capacity change from 977827812352 to 0 [ 26.155562] md: md127 stopped. [ 26.155582] md: unbind [ 26.155638] md: export_rdev(sdb4) [ 26.155795] md: unbind [ 26.156905] md: export_rdev(sda4) [ 26.251771] md: md0 stopped. [ 26.267501] md: bind [ 26.272242] md: bind [ 26.298228] bio: create slab at 1 [ 26.298693] md/raid1:md0: active with 2 out of 2 mirrors [ 26.298828] md0: detected capacity change from 0 to 977827812352 [ 26.306706] md0: unknown partition table and the mdadm -D /dev/md0 State : clean Any suggestions as to why the raid1 personality is missing from the installed kernel would be greatly appreciated. Anyone else here have one of these things? From gregg.drwho8 at gmail.com Wed Mar 21 00:33:08 2012 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Tue, 20 Mar 2012 20:33:08 -0400 Subject: [ARMedslack] PogoPlug support? Message-ID: Hello! I finally took the plunge and obtained a PogoPlug from a vendor today. Also a drive container. (Drive holder I already had a drive in mind.) Would someone please confirm or refute this one, that the device is definitely supported? This because while the documentation on the site is very well written. But however it does not mention if that device is definitely on the supported lists if at all. I can confirm that I have only unboxed it, and not attached it to my network, and not attached that chosen drive. Also the Internet hasn't seen it, also I have not created an account with the firm behind the device. (I'm also a member of the original NSLU2 lists under a different e-mail address as it happens and something about the plug's presence on their site also says that, and naturally brings me to state that, I apologize if I've stepped on any toes here.) ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." From mozes at slackware.com Wed Mar 21 10:25:09 2012 From: mozes at slackware.com (Stuart Winter) Date: Wed, 21 Mar 2012 03:25:09 -0700 (PDT) Subject: [ARMedslack] Call for community documentaion for platforms that are not officially supported Message-ID: Hi Back in the older versions of Slackware ARM, I maintained a document[1] that contained links to installation documentation that allowed owners of devices that were not officially supported by Slackware ARM to be able to get a head start with using Slackware on their device. I have moved this page here[2]. If you have written any good quality documentation that will allow others to get Slackware ARM onto an unsupported device, please drop me a mail : mozes at slackware.com with the details. Thanks! s. [1]ftp://ftp.armedslack.org/armedslack/armedslack-13.1/Compatible_Boards_and_Devices.txt [2]http://www.armedslack.org/doku.php?id=supported_platforms -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From richard.lapointe at gmail.com Wed Mar 21 10:21:35 2012 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Wed, 21 Mar 2012 06:21:35 -0400 Subject: [ARMedslack] PogoPlug support? In-Reply-To: References: Message-ID: <4F69ABAF.8000405@laprjns.com> Gregg, I've got two Pogoplugs, both Pogo P21 that are really E02 versions. Check the label on the bottom of the stand for the model number. http://www.jr.com/pogoplug/pe/PGG_POGOP21/ Same hardware as Dockstars with 256M ram. These are kirkwood base, so yes ArmedSlack 13.37 runs on them but I not sure that anyone here will tell you that it's officially supported. You need to make sure that the version you have is kirkwood based system. There are versions that have are "oxnas" based and required a different kernel. Rich Lapointe On 03/20/2012 08:33 PM, Gregg Levine wrote: > Hello! > I finally took the plunge and obtained a PogoPlug from a vendor today. > Also a drive container. (Drive holder I already had a drive in mind.) > > Would someone please confirm or refute this one, that the device is > definitely supported? This because while the documentation on the site > is very well written. But however it does not mention if that device > is definitely on the supported lists if at all. > I can confirm that I have only unboxed it, and not attached it to my > network, and not attached that chosen drive. Also the Internet hasn't > seen it, also I have not created an account with the firm behind the > device. > > (I'm also a member of the original NSLU2 lists under a different > e-mail address as it happens and something about the plug's presence > on their site also says that, and naturally brings me to state that, I > apologize if I've stepped on any toes here.) > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From cedric.vincent at gmail.com Tue Mar 27 14:54:18 2012 From: cedric.vincent at gmail.com (=?UTF-8?Q?C=C3=A9dric_VINCENT?=) Date: Tue, 27 Mar 2012 16:54:18 +0200 Subject: [ARMedslack] [Announce] Lightweight emulation environment for Slackware/ARM applications Message-ID: Hello, I'm pleased to announce you PRoot (http://proot.me), a new tool that requires no privilege nor setup to: * run Slackware/ARM applications on your Linux/PC thanks to a CPU emulator like QEMU user-mode ("binfmt_misc" equivalent); * isolate these ARM applications inside the Slackware/ARM root file-system ("chroot" equivalent); and * make some host files accessible inside this guest root file-system ("mount --bind" equivalent). It's a kind of "lightweight emulation environment" since QEMU user-mode emulates the guest CPU only: all requests to devices are redirected to the host device drivers (file-system, network, ...). Let's see an example: the command below runs on a Linux/PC the Slackware/ARM program "/bin/sh" -- and all of its sub-programs -- through the specified QEMU: $ proot -Q qemu-arm /path/to/armedslack-rootfs/ Since there's no difference between this emulated environment and a native ARM environment (beside devices), you can use PRoot+QEMU to develop, debug, and test embedded applications seamlessly on our Linux/PC. Here is my favorite example: Perl is known not to be cross-compilable, however there's no problem to build Perl for Slackware/ARM on your Linux/PC with PRoot+QEMU (the prompts were changed for readability purpose): $ proot -Q qemu-arm /path/to/armedslack-rootfs/ $ cd perl-5.14.2 $ ./Configure -de $ make $ make check There's a lot of things to say about PRoot and if you are curious I invite you to have a look at the following "Examples" section: http://proot.me/#examples If you have some questions and/or comments, I will be pleased to answer you either in this thread if they are related to Slackware/ARM, or in PRoot mailing-list/forum otherwise. Note that PRoot works on any host Linux distro and with any guest Linux distro, so you may wonder why I make an announce on this mailing-list? Actually PRoot was developed on Slackware64 and heavily tested with Slackware/ARM; Also, I'm expecting some interesting questions/comments from Slackware users/developers ;) Regards, C?dric.