From slackware at langfinger.org Mon Oct 1 15:32:41 2012 From: slackware at langfinger.org (Michael Langfinger) Date: Mon, 01 Oct 2012 17:32:41 +0200 Subject: [ARMedslack] Installing Slackware 14.0 on Sheevaplug (with ESATA) Message-ID: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> Hi, i am currently installing the new Slackware for ARM on my Sheevaplug (with ESATA) following the guide (INSTALL_KIRKWOOD.TXT). During the installation process i stumbled upon some problems/deprecated information regarding U-Boot and creating the partitions on the sd card. Maybe the following information helps someone else who encounters the same kind of problems. :-) U-Boot: It seems like you can't boot the new kernel that is delivered with Slackware 14.0 (3.4.11) with an older U-Boot version (mine was from mid 2011, iirc). The bootup process will hang after "Uncompressing linux kernel...". My first guess was a wrong machine id set in u-boot, but the kernel and the init ramdisk from Slackware 13.37 work fine. Nevertheless, upgrading u-boot to a current version (i used one from March 2012) solves the problem. You can find instructions on how to do this and links to current versions here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html WARNING: Do not use the version that is located under "2012.04.01-2"! You will be able to boot the slackware installer with this version, but booting the system from sd card will fail because verifying the checksum of the kernel image fails. This seems to be a bug, you can find a discussion about the matter under the following link if you're interested: http://www.plugcomputer.org/plugforum/index.php?topic=6170.0 The version located under 2011.12-3 works fine, so just use this one. Partitioning: I wasn't able to create the partitions (/boot, swap, root) with fdisk. Opening /dev/mmcblk0 with fdisk works, but as soon as you try to write the changes to the sd card you get the error message "unable to write /dev/mmcbklk0p: bad file descriptor". I haven't found out what causes this problem yet. As a workaround you have to partition the card on some other computer (i used my desktop computer). Creating the file system with the slackware installer works. Installation Guide: The guide says that you have to set the variable "arcNumber" to 2678/0xa76 in u-boot, but in fact you have to set the variable "machid" to 0xa76 (on the Sheevaplug with ESATA). Setting the variable arcNumber has no effect. I think that this also applies to the other mentied devices (at least the Guruplug), but i am not 100% sure about that. Maybe someone who owns a Guruplug is able to verify this. I am also not sure if you really need to set the variable mainlineLinux, i will test this later. Nevertheless: Thanks a lot Stuart for all the time and the effort that you put into Slackware for ARM! I have been using Slackware on my Sheevaplug and on a Dreamplug for several months now and i am looking forward to install it on my new Raspberry PI. It's a great distribution! bye, Michael Langfinger From m-lists at biscuit.org.uk Mon Oct 1 16:20:22 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 1 Oct 2012 17:20:22 +0100 (BST) Subject: [ARMedslack] Installing Slackware 14.0 on Sheevaplug (with ESATA) In-Reply-To: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> References: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> Message-ID: Hi Michael, Thanks for your mail. [..] > U-Boot: > It seems like you can't boot the new kernel that is delivered with Slackware > 14.0 (3.4.11) with an older U-Boot version (mine was from mid 2011, iirc). The > bootup process will hang after "Uncompressing linux kernel...". My first guess > was a wrong machine id set in u-boot, but the kernel and the init ramdisk from > Slackware 13.37 work fine. Nevertheless, upgrading u-boot to a current version > (i used one from March 2012) solves the problem. You can find instructions on > how to do this and links to current versions here: Thanks - there was a similar sounding problem for the Guruplug too, caused by a bug in u-boot that was triggered by newer kernels. [..] > The version located under 2011.12-3 works fine, so just use this one. I will add a section about the Sheevaplug ESATA system to here http://www.armedslack.org/maint_kirkwooduboot/ > Partitioning: > I wasn't able to create the partitions (/boot, swap, root) with fdisk. Opening > /dev/mmcblk0 with fdisk works, but as soon as you try to write the changes to > the sd card you get the error message "unable to write /dev/mmcbklk0p: bad > file descriptor". I haven't found out what causes this problem yet. As a > workaround you have to partition the card on some other computer (i used my > desktop computer). Creating the file system with the slackware installer > works. If you find out, let me know - I've never used an SD card there as all of my machines have hard drives. > Installation Guide: > The guide says that you have to set the variable "arcNumber" to 2678/0xa76 in > u-boot, but in fact you have to set the variable "machid" to 0xa76 (on the > Sheevaplug with ESATA). The arcNumber variable was the correct name on the u-boot for the original SheevaPlugs. However, is it even needed at all? I seem to recall Jawkins saying it wasn't required when he was looking at why the guruplug wouldn't boot. I think it might be that the variable inside u-boot has changed. I don't don't have an ESATA Sheevaplug, and would have had to look up the arch numbers from another source -- which I assume were correct at the time. I've amended the INSTALL_KIRKWOOD document with the change above, and I'll add a note about needing to upgrade the u-boot on an ESATA Sheevaplug I'll add it into 14.0 soonish. [..] > Nevertheless: Thanks a lot Stuart for all the time and the effort that you put > into Slackware for ARM! I have been using Slackware on my Sheevaplug and on a > Dreamplug for several months now and i am looking forward to install it on my > new Raspberry PI. It's a great distribution! Thanks! From armedslack at innes.veryspeedy.net Mon Oct 1 17:27:09 2012 From: armedslack at innes.veryspeedy.net (Innes Read) Date: Mon, 01 Oct 2012 18:27:09 +0100 Subject: [ARMedslack] Anyone weigh in on Dreamplug install for 14.0? Message-ID: <1349112429.4399.140661135054701.22A7166F@webmail.messagingengine.com> Hi, I'm about to start upgrading my Dreamplug to Slackware 14.0. Last time I had problems with the 13.37 Slackware kernel because of MTD being enabled (kernel boot locks when it probes for NAND flash which isn't present on the Dreamplug), and also the lack of ext2load command in the U-Boot. I got over it by using the Guruplug arcnumber (2659), putting the kernel + initrd on a local memory card which U-Boot could access, and using a generic kernel from another source which had no MTD turned on. That was about a year ago and it seems that while some things have improved, others remain the same. The Dreamplug now has its own arcnumber (3550) although it seems like flattened device trees may have made that stuff irrelevant. There is a problem with CONFIG_ARM_PATCH_PHYS_VIRT which causes the apparent hang at the Kernel Uncompressing... message which looks to be fixed in later U-Boots. However, I don't really see a clean U-Boot replacement for the Dreamplug anywhere (Debian may have one but as I don't have access to a copy of my current/original U-Boot image I'm not sure I want to go there). The other issue with U-Boot is of course the booting direct from disk - which I'd love to do (and the SlackwareARM install assumes you can do) but cannot with my current system. Before I dive in and experiment, has anyone got any insights into Dreamplug installs for Slackware 14.0 or am I too early? I'd be happy to continue with the current U-Boot and putting the kernel/initrd elsewhere for now, but does anyone know if the Slackware kernels can be used on the Dreamplug directly, or whether I need to be looking for another one (or build my own)? Thanks, Innes. -- Please do not send unsolicited e-mail to this address From m-lists at biscuit.org.uk Mon Oct 1 17:30:00 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 1 Oct 2012 18:30:00 +0100 (BST) Subject: [ARMedslack] Installing Slackware 14.0 on Sheevaplug (with ESATA) In-Reply-To: References: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> Message-ID: [..] > I think it might be that the variable inside u-boot has changed. I don't > don't have an ESATA Sheevaplug, and would have had to look up the arch > numbers from another source -- which I assume were correct at the time. Yes that's what's happened - this is the upstream version, as it says here. http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html Can someone try using the u-boot from there on a guruplug? I'm pondering changing the instructions to use this version of u-boot instead.. From slackware at langfinger.org Mon Oct 1 21:17:47 2012 From: slackware at langfinger.org (Michael Langfinger) Date: Mon, 01 Oct 2012 23:17:47 +0200 Subject: [ARMedslack] Installing Slackware 14.0 on Sheevaplug (with ESATA) In-Reply-To: <5069FB7E.9060509@gmail.com> References: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> <5069FB7E.9060509@gmail.com> Message-ID: Hi, you're right. This is a typo, i meant /dev/mmcblk0. Anyway, i just booted the Slackware Installer again to verify this and now i can create the partitions. Seems to work now, although i have no idea why. I also checked the 'arcNumber'/'mainlineLinux'/'machid' variables at this occasion. To boot the installer you only have to set the 'machid' variable and the 'mainlineLinux' variable. The 'arcNumber' variable is not required, at least not with the u-boot version i used. > mmcbklk0p is not a valid device. > > root at guruslack:/dev# l mmc* > brw-rw---- 1 root disk 179, 0 Aug 13 04:00 mmcblk0 > brw-rw---- 1 root disk 179, 1 Aug 13 04:00 mmcblk0p1 > brw-rw---- 1 root disk 179, 2 Aug 13 04:00 mmcblk0p2 > brw-rw---- 1 root disk 179, 3 Aug 13 04:00 mmcblk0p3 > brw-rw---- 1 root disk 179, 4 Aug 13 04:00 mmcblk0p4 > brw-rw---- 1 root disk 179, 5 Aug 13 04:00 mmcblk0p5 > brw-rw---- 1 root disk 179, 6 Aug 13 04:00 mmcblk0p6 > brw-rw---- 1 root disk 179, 7 Aug 13 04:00 mmcblk0p7 > > If these do not exist on the install initrd that you will have a > problem. It should be there for all plug PC installs. > > I always had to partition by hand then run the install to mmc > partitions as the slackware scrips did not detect mmc partitions > (unless I altered it). (Pre 13.37 at least) > > I run boot/root off mmc on sheevas. Guru uses the USB bus so it is > sdb (LUN 1). My Dockstar is a USB plugged device so it is sda. From unixjohn1969 at gmail.com Mon Oct 1 20:22:22 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Mon, 01 Oct 2012 16:22:22 -0400 Subject: [ARMedslack] Installing Slackware 14.0 on Sheevaplug (with ESATA) In-Reply-To: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> References: <2d1c5ddd409b023ff885f5a4b497f98a-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3XFoWXV1xH1RdQ1xfLkQBW1NYQF1QXgk=-webmailer2@server01.webmailer.hosteurope.de> Message-ID: <5069FB7E.9060509@gmail.com> On 10/01/2012 11:32 AM, Michael Langfinger wrote: > Partitioning: > I wasn't able to create the partitions (/boot, swap, root) with fdisk. Opening > /dev/mmcblk0 with fdisk works, but as soon as you try to write the changes to > the sd card you get the error message "unable to write /dev/mmcbklk0p: bad file > descriptor". I haven't found out what causes this problem yet. As a workaround > you have to partition the card on some other computer (i used my desktop > computer). Creating the file system with the slackware installer works. mmcbklk0p is not a valid device. root at guruslack:/dev# l mmc* brw-rw---- 1 root disk 179, 0 Aug 13 04:00 mmcblk0 brw-rw---- 1 root disk 179, 1 Aug 13 04:00 mmcblk0p1 brw-rw---- 1 root disk 179, 2 Aug 13 04:00 mmcblk0p2 brw-rw---- 1 root disk 179, 3 Aug 13 04:00 mmcblk0p3 brw-rw---- 1 root disk 179, 4 Aug 13 04:00 mmcblk0p4 brw-rw---- 1 root disk 179, 5 Aug 13 04:00 mmcblk0p5 brw-rw---- 1 root disk 179, 6 Aug 13 04:00 mmcblk0p6 brw-rw---- 1 root disk 179, 7 Aug 13 04:00 mmcblk0p7 If these do not exist on the install initrd that you will have a problem. It should be there for all plug PC installs. I always had to partition by hand then run the install to mmc partitions as the slackware scrips did not detect mmc partitions (unless I altered it). (Pre 13.37 at least) I run boot/root off mmc on sheevas. Guru uses the USB bus so it is sdb (LUN 1). My Dockstar is a USB plugged device so it is sda. -- === 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 slackware at langfinger.org Tue Oct 2 18:47:33 2012 From: slackware at langfinger.org (Michael Langfinger) Date: Tue, 02 Oct 2012 20:47:33 +0200 Subject: [ARMedslack] =?utf-8?q?Anyone_weigh_in_on_Dreamplug_install_for_1?= =?utf-8?q?4=2E0=3F?= In-Reply-To: <1349112429.4399.140661135054701.22A7166F@webmail.messagingengine.com> References: <1349112429.4399.140661135054701.22A7166F@webmail.messagingengine.com> Message-ID: <78740e1017d39284da66f227eced0880-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl5oAFZUQ15XQCoDXF5QQlhWXg1c-webmailer2@server05.webmailer.hosteurope.de> Hi Innes, i had some spare time today to play around with my Dreamplug and the new Slackware 14.0. I couldn't boot up the Dreamplug yet with the kernel image that is provided by the slackware installer, but on my way trying i found out some things you also might be interested in. :-) 1.) U-Boot Upgrade: The original Dreamplug U-Boot is in fact very annoying, mainly because of the missing ext2load support. I think we spoke about that and about the workaround a while ago here on the mailing list. Anyway, you can easily upgrade your U-Boot to a newer one. Just put u-boot.kwb and uboot.elf from [1] on a vfat formatted usb flash drive (or any other media you can access) and update u-boot with the following commands (taken from [2]): WARNING: All u-boot variables will be erased in the process, including the ethernet mac adresses! Don't forget to backup/restore them! > usb start > fatload usb 2 0x6400000 dreamplug/u-boot.kwb > sf probe 0 > sf erase 0x0 0x80000 > sf write 0x6400000 0x0 0x${filesize} ${filesize} is the size that is displayed after executing the fatload command. You have to convert the value into the corresponding hex value. You can now replace your vfat partition containing the kernel image with an ext2 formatted partition. I tried this with my old Slackware 13.37 installation, worked fine. 2.) Booting Slackware 14.0 Installer Unfortunately you can't boot the slackware installer even with the new U-Boot version (i tried 2011.12-3 and 2012.04.01-2). There are two different effects, depending on which machine id you set. a) Machine ID 3550/0xDDE (Dreamplug): The kernel won't boot and hangs at "Uncompressing Linux... done, booting the kernel.". I first suspected CONFIG_ARM_PATCH_PHYS_VIRT as source of the problem, but a patch for this problem exists since february 2012 [1] and should be included in the u-boot versions i tried. Also, the kernel boots if i set another machid (see b)). Nevertheless, i haven't ruled this out yet. I will b) Machine ID 2659/0xA63 (Guruplug): The kernel starts booting and then freezes, last line is "[ 2.396407] brd: module loaded". I suppose this is related to the known problem with probing the NAND flash (CONFIG_MTD_NAND_ORION=y). 3.) Next steps? I see two possibilities on how to proceed: a) Build a custom kernel with NAND probing disabled and set the machine id to the one that is also used by the Guruplug. I don't like this , but it might be a quick workaround. You would also have to make sure that you don't accidentally overwrite your custom kernel with the default one from Slackware, because this would result in a non-bootable system. b) Find out what causes the kernel hang from 2a). This would mean that you can set the machine id to the correct value and that you don't have to use any workarounds. So, long story short: You still have to take a custom kernel to be able to use Slackware on the Dreamplug, but you can now store your kernel images on an ext2 partition if you update u-boot. I will have a look at the u-boot sources that where used to build the u-boot images under [1] later, maybe the patch for CONFIG_ARM_PATCH_PHYS_VIRT isn't included. If this is the case, i will try to patch and build u-boot myself, maybe it helps. Michael [1] http://people.debian.org/~tbm/u-boot/ [2] http://wiki.debian.org/FreedomBox/Firmware [3] http://lists.denx.de/pipermail/u-boot/2012-February/117020.html > Hi, > > I'm about to start upgrading my Dreamplug to Slackware 14.0. Last > time > I had problems with the 13.37 Slackware kernel because of MTD being > enabled (kernel boot locks when it probes for NAND flash which isn't > present on the Dreamplug), and also the lack of ext2load command in > the > U-Boot. I got over it by using the Guruplug arcnumber (2659), > putting > the kernel + initrd on a local memory card which U-Boot could access, > and using a generic kernel from another source which had no MTD > turned > on. That was about a year ago and it seems that while some things > have > improved, others remain the same. > > The Dreamplug now has its own arcnumber (3550) although it seems like > flattened device trees may have made that stuff irrelevant. There is > a > problem with CONFIG_ARM_PATCH_PHYS_VIRT which causes the apparent > hang > at the Kernel Uncompressing... message which looks to be fixed in > later > U-Boots. However, I don't really see a clean U-Boot replacement for > the > Dreamplug anywhere (Debian may have one but as I don't have access to > a > copy of my current/original U-Boot image I'm not sure I want to go > there). The other issue with U-Boot is of course the booting direct > from disk - which I'd love to do (and the SlackwareARM install > assumes > you can do) but cannot with my current system. > > Before I dive in and experiment, has anyone got any insights into > Dreamplug installs for Slackware 14.0 or am I too early? I'd be > happy > to continue with the current U-Boot and putting the kernel/initrd > elsewhere for now, but does anyone know if the Slackware kernels can > be > used on the Dreamplug directly, or whether I need to be looking for > another one (or build my own)? > > Thanks, Innes. > -- > Please do not send unsolicited e-mail to this address > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From armedslack at innes.veryspeedy.net Tue Oct 2 20:02:14 2012 From: armedslack at innes.veryspeedy.net (Innes Read) Date: Tue, 02 Oct 2012 21:02:14 +0100 Subject: [ARMedslack] Anyone weigh in on Dreamplug install for 14.0? In-Reply-To: <78740e1017d39284da66f227eced0880-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl5oAFZUQ15XQCoDXF5QQlhWXg1c-webmailer2@server05.webmailer.hosteurope.de> References: <1349112429.4399.140661135054701.22A7166F@webmail.messagingengine.com> <78740e1017d39284da66f227eced0880-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl5oAFZUQ15XQCoDXF5QQlhWXg1c-webmailer2@server05.webmailer.hosteurope.de> Message-ID: <1349208134.5872.140661135617409.0D6DC17E@webmail.messagingengine.com> Thanks Michael, you've confirmed a lot of what I've been discovering! I have now built my own 3.4.11 with MTD disabled as a workaround (I also had to disable PHYS_VIRT in my case as I have not upgraded U-Boot yet) and that does indeed boot into the 14.0 installer successfully. When I switch to using the Dreamplug board number / FDT config I also see the same lockup right after the "Uncompressing...done" message - it's interesting that upgrading U-Boot did not fix that for you (but have you checked CONFIG_SERIAL_OF_PLATFORM as per [1], I believe the Slackware install kernel has that set to N). Let me know if you find anything interesting in the U-Boot sources - I have now procured what appears to be the original U-Boot image from another source (thanks Jim!) so I feel a little more secure about blowing my current U-Boot image away with a new one! Cheers, Innes. [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2012-June/102533.html On Tue, Oct 2, 2012, at 19:47, Michael Langfinger wrote: > Hi Innes, > > i had some spare time today to play around with my Dreamplug and the > new Slackware 14.0. I couldn't boot up the Dreamplug yet with the kernel > image that is provided by the slackware installer, but on my way trying > i found out some things you also might be interested in. :-) > > 1.) U-Boot Upgrade: > The original Dreamplug U-Boot is in fact very annoying, mainly because > of the missing ext2load support. I think we spoke about that and about > the workaround a while ago here on the mailing list. Anyway, you can > easily upgrade your U-Boot to a newer one. Just put u-boot.kwb and > uboot.elf from [1] on a vfat formatted usb flash drive (or any other > media you can access) and update u-boot with the following commands > (taken from [2]): > > WARNING: All u-boot variables will be erased in the process, including > the ethernet mac adresses! Don't forget to backup/restore them! > > > usb start > > fatload usb 2 0x6400000 dreamplug/u-boot.kwb > > sf probe 0 > > sf erase 0x0 0x80000 > > sf write 0x6400000 0x0 0x${filesize} > > ${filesize} is the size that is displayed after executing the fatload > command. You have to convert the value into the corresponding hex value. > > You can now replace your vfat partition containing the kernel image > with an ext2 formatted partition. I tried this with my old Slackware > 13.37 installation, worked fine. > > 2.) Booting Slackware 14.0 Installer > Unfortunately you can't boot the slackware installer even with the new > U-Boot version (i tried 2011.12-3 and 2012.04.01-2). There are two > different effects, depending on which machine id you set. > > a) Machine ID 3550/0xDDE (Dreamplug): The kernel won't boot and hangs > at "Uncompressing Linux... done, booting the kernel.". I first suspected > CONFIG_ARM_PATCH_PHYS_VIRT as source of the problem, but a patch for > this problem exists since february 2012 [1] and should be included in > the u-boot versions i tried. Also, the kernel boots if i set another > machid (see b)). Nevertheless, i haven't ruled this out yet. I will > > b) Machine ID 2659/0xA63 (Guruplug): The kernel starts booting and then > freezes, last line is "[ 2.396407] brd: module loaded". I suppose > this is related to the known problem with probing the NAND flash > (CONFIG_MTD_NAND_ORION=y). > > 3.) Next steps? > > I see two possibilities on how to proceed: > > a) Build a custom kernel with NAND probing disabled and set the machine > id to the one that is also used by the Guruplug. I don't like this , but > it might be a quick workaround. You would also have to make sure that > you don't accidentally overwrite your custom kernel with the default one > from Slackware, because this would result in a non-bootable system. > b) Find out what causes the kernel hang from 2a). This would mean that > you can set the machine id to the correct value and that you don't have > to use any workarounds. > > So, long story short: You still have to take a custom kernel to be able > to use Slackware on the Dreamplug, but you can now store your kernel > images on an ext2 partition if you update u-boot. I will have a look at > the u-boot sources that where used to build the u-boot images under [1] > later, maybe the patch for CONFIG_ARM_PATCH_PHYS_VIRT isn't included. If > this is the case, i will try to patch and build u-boot myself, maybe it > helps. > > Michael > > [1] http://people.debian.org/~tbm/u-boot/ > [2] http://wiki.debian.org/FreedomBox/Firmware > [3] http://lists.denx.de/pipermail/u-boot/2012-February/117020.html > > > > Hi, > > > > I'm about to start upgrading my Dreamplug to Slackware 14.0. Last > > time > > I had problems with the 13.37 Slackware kernel because of MTD being > > enabled (kernel boot locks when it probes for NAND flash which isn't > > present on the Dreamplug), and also the lack of ext2load command in > > the > > U-Boot. I got over it by using the Guruplug arcnumber (2659), > > putting > > the kernel + initrd on a local memory card which U-Boot could access, > > and using a generic kernel from another source which had no MTD > > turned > > on. That was about a year ago and it seems that while some things > > have > > improved, others remain the same. > > > > The Dreamplug now has its own arcnumber (3550) although it seems like > > flattened device trees may have made that stuff irrelevant. There is > > a > > problem with CONFIG_ARM_PATCH_PHYS_VIRT which causes the apparent > > hang > > at the Kernel Uncompressing... message which looks to be fixed in > > later > > U-Boots. However, I don't really see a clean U-Boot replacement for > > the > > Dreamplug anywhere (Debian may have one but as I don't have access to > > a > > copy of my current/original U-Boot image I'm not sure I want to go > > there). The other issue with U-Boot is of course the booting direct > > from disk - which I'd love to do (and the SlackwareARM install > > assumes > > you can do) but cannot with my current system. > > > > Before I dive in and experiment, has anyone got any insights into > > Dreamplug installs for Slackware 14.0 or am I too early? I'd be > > happy > > to continue with the current U-Boot and putting the kernel/initrd > > elsewhere for now, but does anyone know if the Slackware kernels can > > be > > used on the Dreamplug directly, or whether I need to be looking for > > another one (or build my own)? > > > > Thanks, Innes. > > -- > > Please do not send unsolicited e-mail to this address > > > > _______________________________________________ > > 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 -- Please do not send unsolicited e-mail to this address From slackware at langfinger.org Wed Oct 3 17:30:56 2012 From: slackware at langfinger.org (Michael Langfinger) Date: Wed, 03 Oct 2012 19:30:56 +0200 Subject: [ARMedslack] ARMv4 assembler optimizations for OpenSSL Message-ID: <546688d1a39cfa4b4c5904823a96a78e-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl1oA1BLWVkwQEYGVlhRRVxQXg==-webmailer2@server02.webmailer.hosteurope.de> Hi, i just found out that the openssl package of Slackware for ARM 14.0 doesn't use the assembler optimizations available for ARMv4 in OpenSSL. Since all the packages are built for the baseline architecture of ARMv5te, enabling the optimization shouldn't affect the compatibility to any of the platforms that are supported by Slackware for ARM 14.0.* It would, however, have a huge impact on the performance of OpenSSL and very likely all the programs that use OpenSSL libraries (like OpenSSH). (* I am not 100% sure about that because i am no expert regarding the different ARM architectures, so maybe i am wrong here. Maybe someone on the mailing list with more expertise on this matter can confirm my assumption or correct me?) I rebuilt the OpenSSL package and ran some tests on my Sheevaplug. As you can see the results are pretty impressive (the original output of the "openssl speed" command is much longer, this is just an excerpt): OpenSSL 1.0.1c, default package (no optimization) The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes md5 3309.68k 11805.99k 34086.83k 64614.06k 87405.91k aes-128 cbc 10003.75k 11224.32k 11537.49k 11619.33k 11635.37k aes-192 cbc 8812.01k 9592.04k 9819.65k 9879.89k 9890.47k aes-256 cbc 7777.37k 8376.77k 8548.95k 8593.75k 8601.60k sha256 2670.09k 6356.61k 11432.70k 14294.36k 15349.08k sha512 412.84k 1650.65k 2386.60k 3272.36k 3670.02k sign verify sign/s verify/s rsa 512 bits 0.002360s 0.000218s 423.8 4589.0 rsa 1024 bits 0.012267s 0.000625s 81.5 1599.4 rsa 2048 bits 0.074701s 0.002067s 13.4 483.8 rsa 4096 bits 0.494286s 0.007278s 2.0 137.4 OpenSSL 1.0.1c, with ARMv4 assembler optimization enabled The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes md5 4078.73k 14215.30k 38787.16k 68390.57k 88432.50k aes-128 cbc 15095.54k 16847.00k 17382.31k 17521.32k 17555.46k aes-192 cbc 13213.38k 14536.19k 14932.91k 15036.76k 15059.63k aes-256 cbc 11756.32k 12785.60k 13089.37k 13167.96k 13186.39k sha256 5125.39k 12176.15k 21252.61k 26089.81k 28068.52k sha512 1446.27k 5780.57k 8251.65k 11255.81k 12593.83k sign verify sign/s verify/s rsa 512 bits 0.001101s 0.000106s 907.9 9456.0 rsa 1024 bits 0.005549s 0.000313s 180.2 3190.6 rsa 2048 bits 0.035971s 0.001120s 27.8 892.8 rsa 4096 bits 0.257692s 0.004279s 3.9 233.7 Short summary (performance increase, numbers rounded) aes-128 cbc: +50% (16 bytes) aes-192 cbc: +50% (16 bytes) aes-256 cbc: +50% (16 bytes) sha256: +90% (16 bytes) sha512: +250% (16 bytes) rsa 512 bits: +115% (sign) / +105% (verify) rsa 1024 bits: +120% / +100% rsa 2048 bits: + 110% / +85% rsa 4096 bits: + 100% / +70% If you want to test this yourself, just add the switch "-linux-armv4" when you run the Configure script from OpenSSL or apply the patch [1] to the debian-targets.patch file before running the Slackbuild script. Warning: As OpenSSL is removed during the build process, you won't be able to login with SSH during the build process and until you reinstall the openssl package. So don't forget to temporarily enable telnet or something similar, especially if you only have remote access to the machine. I found out about the assembler optimization from the Raspberry Pi forum [2]. Cheers, Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676533 [2] http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=8433 From slackware at langfinger.org Wed Oct 3 17:57:41 2012 From: slackware at langfinger.org (Michael Langfinger) Date: Wed, 03 Oct 2012 19:57:41 +0200 Subject: [ARMedslack] =?utf-8?q?Anyone_weigh_in_on_Dreamplug_install_for_1?= =?utf-8?q?4=2E0=3F?= In-Reply-To: <1349208134.5872.140661135617409.0D6DC17E@webmail.messagingengine.com> References: <1349112429.4399.140661135054701.22A7166F@webmail.messagingengine.com> <78740e1017d39284da66f227eced0880-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl5oAFZUQ15XQCoDXF5QQlhWXg1c-webmailer2@server05.webmailer.hosteurope.de> <1349208134.5872.140661135617409.0D6DC17E@webmail.messagingengine.com> Message-ID: Hi Innes, i also built my own 3.4.11 kernel now (took 6+ hours... ;)), with the following changes: CONFIG_SERIAL_OF_PLATFORM=y # CONFIG_MTD_NAND_ORION is not set This leads to the following: - Dreamplug machine id (0xdde) set: Lockup after the "Uncompressing..." message. - Guruplug machine id (0xa63) set: System boots (because of MTD disabled) I also checked the sources from the u-boot version that i use and the bugfix for the CONFIG_ARM_PATCH_PHYS_VIRT problem is included in this version. I made sure that the system really hangs (and not that there is just no output over the serial line) by changing the bootargs variable with: setenv bootargs console=ttyS0,115200 kbd=uk nic=auto:eth0:dhcp root=/dev/ram rw and then booting the kernel. The system boots up and gets an address if i use the Guruplug machine id, but it doesn't get an address using the Dreamplug machine id. So, still no idea what's causing the lockup. Seems like using the Guruplug machid and compiling a custom kernel is still the only way to get the Dreamplug booting... Cheers, Michael > Thanks Michael, you've confirmed a lot of what I've been discovering! > > I have now built my own 3.4.11 with MTD disabled as a workaround (I > also > had to disable PHYS_VIRT in my case as I have not upgraded U-Boot > yet) > and that does indeed boot into the 14.0 installer successfully. > > When I switch to using the Dreamplug board number / FDT config I also > see the same lockup right after the "Uncompressing...done" message - > it's interesting that upgrading U-Boot did not fix that for you (but > have you checked CONFIG_SERIAL_OF_PLATFORM as per [1], I believe the > Slackware install kernel has that set to N). Let me know if you find > anything interesting in the U-Boot sources - I have now procured what > appears to be the original U-Boot image from another source (thanks > Jim!) so I feel a little more secure about blowing my current U-Boot > image away with a new one! > > Cheers, Innes. > > [1] > > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-June/102533.html From m-lists at biscuit.org.uk Thu Oct 4 07:37:38 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 4 Oct 2012 08:37:38 +0100 (BST) Subject: [ARMedslack] ARMv4 assembler optimizations for OpenSSL In-Reply-To: <546688d1a39cfa4b4c5904823a96a78e-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl1oA1BLWVkwQEYGVlhRRVxQXg==-webmailer2@server02.webmailer.hosteurope.de> References: <546688d1a39cfa4b4c5904823a96a78e-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl1oA1BLWVkwQEYGVlhRRVxQXg==-webmailer2@server02.webmailer.hosteurope.de> Message-ID: [..] > I found out about the assembler optimization from the Raspberry Pi forum [2]. I ran it on my Trimslice - before: sign verify sign/s verify/s rsa 512 bits 0.001829s 0.000159s 546.7 6306.3 rsa 1024 bits 0.009681s 0.000470s 103.3 2125.9 rsa 2048 bits 0.057977s 0.001583s 17.2 631.7 rsa 4096 bits 0.382593s 0.005495s 2.6 182.0 sign verify sign/s verify/s dsa 512 bits 0.001640s 0.001847s 609.9 541.3 dsa 1024 bits 0.004744s 0.005640s 210.8 177.3 dsa 2048 bits 0.015681s 0.018537s 63.8 53.9 After: sign verify sign/s verify/s rsa 512 bits 0.000882s 0.000088s 1133.2 11407.0 rsa 1024 bits 0.004885s 0.000278s 204.7 3595.5 rsa 2048 bits 0.032961s 0.001008s 30.3 992.0 rsa 4096 bits 0.238333s 0.003873s 4.2 258.2 sign verify sign/s verify/s dsa 512 bits 0.000886s 0.000960s 1128.6 1041.7 dsa 1024 bits 0.002722s 0.003172s 367.4 315.3 dsa 2048 bits 0.009785s 0.011479s 102.2 87.1 I'll add the new packages into patches in 14.0. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Thu Oct 4 16:25:11 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 4 Oct 2012 17:25:11 +0100 (BST) Subject: [ARMedslack] ARMv4 assembler optimizations for OpenSSL In-Reply-To: References: <546688d1a39cfa4b4c5904823a96a78e-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlAWWl1oA1BLWVkwQEYGVlhRRVxQXg==-webmailer2@server02.webmailer.hosteurope.de> Message-ID: [..] > I'll add the new packages into patches in 14.0. Done! From frank at thor.baldar.de Tue Oct 9 16:00:16 2012 From: frank at thor.baldar.de (Frank Boehm) Date: Tue, 9 Oct 2012 18:00:16 +0200 (CEST) Subject: [ARMedslack] fix for missing Xvnc in tightvnc Message-ID: Hello, I missed Xvnc in tightvnc package, -lwrap -lnsl were missing for me and I could compile it on my RaspberryPi. /root/tmp/build-tightvnc/vnc_unixsrc/Xvnc/programs/Xserver/Makefile VNCSYSLIBS = -L/usr/local/lib -ljpeg -lz -lcrypt -lwrap -lnsl my Xvnc can be found here: ftp://li-la.de/pub/baldar/slackware/slackwarearm-14.0/Xvnc or you can compile it on your own too before I had my own Xvnc I used x11vnc, but I need Xvnc for xrdp # CAUTION: make raspberrypi X server accessible without password! /usr/bin/x11vnc -display :0 & have fun, cu Frank -- When man calls an animal "vicious", he usually means that it will attempt to defend itself when he tries to kill it. From m-lists at biscuit.org.uk Wed Oct 10 07:05:45 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 10 Oct 2012 08:05:45 +0100 (BST) Subject: [ARMedslack] fix for missing Xvnc in tightvnc In-Reply-To: References: Message-ID: > before I had my own Xvnc I used x11vnc, but I need Xvnc for xrdp > # CAUTION: make raspberrypi X server accessible without password! > /usr/bin/x11vnc -display :0 & x11vnc is in /extra already and works for me. Is there something wrong with it? -- Stuart Winter Slackware ARM: www.armedslack.org From frank at thor.baldar.de Wed Oct 10 08:25:33 2012 From: frank at thor.baldar.de (Frank Boehm) Date: Wed, 10 Oct 2012 10:25:33 +0200 (CEST) Subject: [ARMedslack] fix for missing Xvnc in tightvnc In-Reply-To: References: Message-ID: On Wed, 10 Oct 2012, Stuart Winter wrote: > >> before I had my own Xvnc I used x11vnc, but I need Xvnc for xrdp >> # CAUTION: make raspberrypi X server accessible without password! >> /usr/bin/x11vnc -display :0 & > > x11vnc is in /extra already and works for me. > Is there something wrong with it? nothing wrong with x11vnc, but different intentions Xvnc <> x11vnc x11vnc - (VNC server for real X displays) Xvnc - an X server providing VNC connectivity Xvnc is a virtual Display, can be started with the resolution and color depth of the connecting client. Several of them running at the same time for different users. With the help of xrdp and Xvnc I'm able to connect to my pi from any windows pc without installing extra software. There are problems with international keymaps, most of them patched for de layout in my version, thats not perfect, but good enough for me. cu Frank -- Life's too short to read boring signatures. From pr0f3ss0r1492 at yahoo.com Fri Oct 19 09:42:07 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Fri, 19 Oct 2012 10:42:07 +0100 Subject: [ARMedslack] New Samsung Chromebook Message-ID: Just read this: http://www.eweek.com/pc-hardware/samsung-offers-new-laptop-running-google-chrome-os/ Does anybody know which ARM processor it has and if it can potentially run Slackware ARM in a proper and easy way? Thanks -- Ottavio Caruso From christophe.lyon at gmail.com Fri Oct 19 10:28:12 2012 From: christophe.lyon at gmail.com (Christophe Lyon) Date: Fri, 19 Oct 2012 12:28:12 +0200 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: On Fri, Oct 19, 2012 at 11:42 AM, Ottavio Caruso wrote: > Just read this: > http://www.eweek.com/pc-hardware/samsung-offers-new-laptop-running-google-chrome-os/ > > Does anybody know which ARM processor it has and if it can potentially > run Slackware ARM in a proper and easy way? > It's a dual Cortex-A15 processor, with 2GB RAM and 16GB SSD. Christophe. From pr0f3ss0r1492 at yahoo.com Fri Oct 19 14:58:43 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Fri, 19 Oct 2012 15:58:43 +0100 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: On 19 October 2012 11:28, Christophe Lyon wrote: > It's a dual Cortex-A15 processor, with 2GB RAM and 16GB SSD. > > Christophe. Thanks. 2GB ram for an ARM is quite a lot, isn't it? What are the panel's view on this device? -- Ottavio From pirkster at gmail.com Fri Oct 19 15:54:13 2012 From: pirkster at gmail.com (Steve Pirk) Date: Fri, 19 Oct 2012 08:54:13 -0700 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: I have been using Chromebooks since December 2010, and 2GB is just about right on the memory. The Chrome browser uses a lot of ram :-) I would love to get my hands on this new ARM processor based unit, but I already have 3 Chrome OS devices. It should be fairly easy to experiment with, as each device has a developer switch that 1) gives you a bash shell, and 2) allows you to set it up for dual or triple booting. On Oct 19, 2012 7:59 AM, "Ottavio Caruso" wrote: > On 19 October 2012 11:28, Christophe Lyon > wrote: > > It's a dual Cortex-A15 processor, with 2GB RAM and 16GB SSD. > > > > Christophe. > > Thanks. 2GB ram for an ARM is quite a lot, isn't it? What are the > panel's view on this device? > > -- > Ottavio > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Fri Oct 19 18:56:30 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Fri, 19 Oct 2012 19:56:30 +0100 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: On 19 October 2012 16:54, Steve Pirk wrote: > as each device has a developer switch that 1) gives you a bash shell, and 2) > allows you to set it up for dual or triple booting. Can I take advantage of your kindness and ask you to expand on this topic, especially the dual booting thing? Unfortunately I haven't got my hands on any of these devices and I know nobody who has. From pirkster at gmail.com Fri Oct 19 23:12:29 2012 From: pirkster at gmail.com (Steve Pirk) Date: Fri, 19 Oct 2012 16:12:29 -0700 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: You most certainly may! I have been playing with Chromium OS since Feb 2010. The OS is a very optimized version of Gentoo, and the entires source tree is available from chromium.org (the open source version of Google's Chrome OS which is what the Samsung is loaded with). A Chromebook can be in a verified boot mode, meaning the basic OS is read only, or it can be in dev mode, which allows you to perform normal Linux system operations. What Google has done that is different from other OS's, is that they have made the Chrome browser the entire GUI and window manager. It is really very slick. The first unit released by Google was the Cr-48, essentially a hardware reference platform they sent to schools to pilot test and to a bunch of geeks who proceed to hack the hell out of them (as Google hoped they would). My Cr-48 is in dev mode, and I have added pre-built packages (very similar to Slackware packages) that have added tar, streamripper, mplayer2 and a bunch of other programs not supplied with Chrome OS. That is the simplest way to have a Chromebook that can also perform many standalone Linux applications. I am not sure this link will work, but the author shared his Google Drive folder with all of the x86_64 packages in it to the public. Long url https://docs.google.com/folder/d/0Byyp8R1NxgJlUHIxWDNEYW5neFk/edit?docId=0Byyp8R1NxgJlbThyS0xGU1lQbTA Short url http://goo.gl/GZDij One of the first things people did was to be able to dual boot Chrome OS devices with Ubuntu. Then came Windows and now Mac. This is a link to Chrubuntu - adding Ubuntu 12.04 to a Chromebook: http://chromeos-cr48.blogspot.com/2012/04/chrubuntu-1204-now-with-double-bits.html Ubuntu 11.04 http://chromeos-cr48.blogspot.com/2011/04/ubuntu-1104-for-cr-48-is-ready.html If you want to test drive Chromium OS, there is a kid named Hexxeh who builds bootable USB images you can test out on your current machines: http://chromeos.hexxeh.net/ There are more resources out there, and I will add good ones as I find them. -- steve On Fri, Oct 19, 2012 at 11:56 AM, Ottavio Caruso wrote: > On 19 October 2012 16:54, Steve Pirk wrote: > > as each device has a developer switch that 1) gives you a bash shell, > and 2) > > allows you to set it up for dual or triple booting. > > Can I take advantage of your kindness and ask you to expand on this > topic, especially the dual booting thing? Unfortunately I haven't got > my hands on any of these devices and I know nobody who has. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chekkizhar.linux at gmail.com Sun Oct 21 10:22:28 2012 From: chekkizhar.linux at gmail.com (chekkizhar N) Date: Sun, 21 Oct 2012 18:22:28 +0800 Subject: [ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev C Message-ID: Hi, I am trying to load slack-13.37-miniroot_01May11.tar in Beagle Board -xm - Rev C. So far, I made the following changes, 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4, in /etc/boot dir. 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file I *NOT* changed anything in "/boot" partition, which has MLO,uboot-bin,uEnv.txt file.[ came alone with the board ] Getting the following, ########################################################################## Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56) Beagle xM Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42) OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #577200229ff80000016849a901022026 Hit any key to stop autoboot: 0 The user button is currently NOT pressed. SD/MMC found on device 0 reading uEnv.txt 134 bytes read Loaded environment from uEnv.txt Importing environment from mmc ... Loading file "/boot/uImage" from mmc device 0:2 (xxa2) 2033192 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 80200000 ... Image Name: Linux-2.6.38.4-kirkwood Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2033128 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... ################################################################# After the Loading Kernel Image , message nothing is happening. Can anyone Help? Thanks, Chekkiizhar -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sun Oct 21 12:34:54 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 21 Oct 2012 13:34:54 +0100 (BST) Subject: [ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev C In-Reply-To: References: Message-ID: On Sun, 21 Oct 2012, chekkizhar N wrote: [..] > 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4, in > /etc/boot dir. > 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file /etc/boot? what is using /etc/boot ? serial console in /etc/fstab? I assume you mean /etc/inittab The 'kirkwood' kernels are for the Marvell Kirkwood systems such as the Sheevaplug, not machines with a 'Cortex' CPU like the Beagleboard. Slackware ARM does not provided kernels for the Cortex. In Linux 3.7 with the planned one kernel for all, once I've understood how it works I'll include support for as many of the main architectures as I can. For now, google 'armedslack beagleboard' and hopefully there'll be enough there to get you going. From fdonkers at zonnet.nl Wed Oct 24 13:02:20 2012 From: fdonkers at zonnet.nl (Frank Donkers) Date: Wed, 24 Oct 2012 15:02:20 +0200 Subject: [ARMedslack] Using a bootdisk to install armedslack on TrimSlice Message-ID: <5087E6DC.1090704@zonnet.nl> Hi all, I wanted to install armedslack 14.0 on my new TrimSlice, but didn't feel like setting up any (boot) servers. According to the wiki, the stock firmware looks for a boot.scr script file on an attached SD card, micro-SD or USB device, so I decided to use that method. Here are my steps: 1. You need the mkimage command from the u-boot toolkit. Install the u-boot-tools package from AlienBOB's repository. 2. Create a new text file called boot.cmd with the following content: --------------------------------------------------------------- # Slackware u-boot installation script. Create image with: # mkimage -A arm -O linux -T script -C none -d boot.cmd boot.scr setenv kerneladdr 0x00800000 setenv initrdaddr 0x01100000 setenv kernelfile /boot/uImage-tegra setenv initrdfile /boot/uinitrd-tegra.img # setenv loadinitrd ${fs}load ${interface} ${device} ${initrdaddr} ${initrdfile} setenv loadkernel ${fs}load ${interface} ${device} ${kerneladdr} ${kernelfile} setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw setenv bootcmd bootm ${kerneladdr} ${initrdaddr} # run loadinitrd run loadkernel bootd --------------------------------------------------------------- 3. Create the script file as follows: mkimage -A arm -O linux -T script -C none -d boot.cmd boot.scr 4. Take an SD card or USB pendrive with an ext2/ext3/fat filesystem and enough room for the kernel and root fs. Create a new /boot directory on it. Copy the new boot.scr file to /boot. 5. From the ARM tree, copy isolinux/uinitrd-tegra.img and kernels/tegra/uImage-tegra to /boot. 6. Now insert the card/pendrive and start the TrimSlice. The default firmware will find the boot.scr file and execute it. This will load the slackware installer. I have my ARM tree on an external USB disk, so I installed from a pre-mounted directory. 7. Finish with the regular INSTALL_TEGRA.TXT instructions to setup u-boot. That's it. If your install device is large enough, you could put the ARM tree on that. My external HD has xfs, so I couldn't combine those steps. I tried to mount the SD card from the installer, but I couldn't get that to work. Maybe I did something wrong... NOTE: during the process, I upgraded the firmware to the latest 2012 version. Big mistake; that version only works with the 3.5 kernel, so I couldn't boot. The 2010 firmware version works fine. Anyway, thought I would share this. Let me know what you think. regards, Frank Donkers. From pr0f3ss0r1492 at yahoo.com Fri Oct 26 19:04:57 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Fri, 26 Oct 2012 20:04:57 +0100 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: On 19 October 2012 10:42, Ottavio Caruso wrote: > Does anybody know which ARM processor it has and if it can potentially > run Slackware ARM in a proper and easy way? Olof Johansson has just posted a way to install an alternative Linux distro on the new Chromebook: https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ He has succeded with Suse just using the Suse root filesystem and the Chrome OS stock kernel. It looks like a complicated procedure (at least for me) and the catch is that it will boot from the Chrome partition, but I understand that he and other developers are working on booting from an external storage altogether. If anybody has any ideas on this subject they will do me a great favour. I have a limited budget. I was saving money to buy the new Genesi device which hasn't come yet but this little gem is tempting me now. -- Ottavio Caruso From m-lists at biscuit.org.uk Sun Oct 28 17:58:06 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 28 Oct 2012 17:58:06 +0000 (GMT) Subject: [ARMedslack] fix for missing Xvnc in tightvnc In-Reply-To: References: Message-ID: hey Frank, [..] > With the help of xrdp and Xvnc I'm able to connect to my pi from any windows > pc without installing extra software. There are problems with international > keymaps, most of them patched for de layout in my version, thats not perfect, > but good enough for me. Thanks - I'll be putting out a patched package in 14.0 that contains Xvnc. -- Stuart Winter Slackware ARM: www.armedslack.org From louigi600 at yahoo.it Tue Oct 30 06:46:41 2012 From: louigi600 at yahoo.it (Davide) Date: Tue, 30 Oct 2012 06:46:41 +0000 (GMT) Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: <1351579601.85320.YahooMailNeo@web29702.mail.ird.yahoo.com> ________________________________ >> Does anybody know which ARM processor it has and if it can potentially >> run Slackware ARM in a proper and easy way? > >Olof Johansson has just posted a way to install an alternative Linux >distro on the new Chromebook: >ttps://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ > >He has succeded with Suse just using the Suse root filesystem and the >Chrome OS stock kernel. It looks like a complicated procedure (at >least for me) and the catch is that it will boot from the Chrome >partition, but I understand that he and other developers are working >on booting from an external storage altogether. > >If anybody has any ideas on this subject they will do me a great >favour. I have a limited budget. I was saving money to buy the new >Genesi device which hasn't come yet but this little gem is tempting me >now. Can't be much more difficult then any other arm platform: get a kernel that works for the hardware, get the tools to manipulate the kernel image so that the boot loader on the hardware will liad it (may need to package the initrd in there too), setup your initrd to look for whereever you plan to put the real root filesystem (that will contain whatever distro uou prefer) find a way of writing your boot image to the hardware (and root image if not on a removable media), cross your fingers and boot. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From chekkizhar.linux at gmail.com Tue Oct 30 08:21:15 2012 From: chekkizhar.linux at gmail.com (chekkizhar N) Date: Tue, 30 Oct 2012 13:51:15 +0530 Subject: [ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev C Message-ID: ok. I will wait and meanwhile will do searching as Stuart told. I got this mail today [30/10/2012 in India ] only. But, the question and the reply was made on that day [ Sun, 21 Oct 2012 ] itself. So, what went wrong? On Tue, Oct 30, 2012 at 12:19 PM, wrote: > Send ARMedslack mailing list submissions to > armedslack at lists.armedslack.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.armedslack.org/mailman/listinfo/armedslack > or, via email, send a message with subject or body 'help' to > armedslack-request at lists.armedslack.org > > You can reach the person managing the list at > armedslack-owner at lists.armedslack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ARMedslack digest..." > > > Today's Topics: > > 1. Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev > C (chekkizhar N) > 2. Re: Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - > Rev C (Stuart Winter) > 3. Using a bootdisk to install armedslack on TrimSlice > (Frank Donkers) > 4. Re: New Samsung Chromebook (Ottavio Caruso) > 5. Re: fix for missing Xvnc in tightvnc (Stuart Winter) > 6. Re: New Samsung Chromebook (Davide) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 21 Oct 2012 18:22:28 +0800 > From: chekkizhar N > To: armedslack at lists.armedslack.org > Subject: [ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle > Board -xm - Rev C > Message-ID: > ZQX0s06oY-+9Dm1FMxpvig at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > I am trying to load slack-13.37-miniroot_01May11.tar in Beagle Board -xm - > Rev C. > > So far, I made the following changes, > 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4, in > /etc/boot dir. > 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file > > I *NOT* changed anything in "/boot" partition, which has > MLO,uboot-bin,uEnv.txt file.[ came alone with the board ] > > Getting the following, > ########################################################################## > Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56) > Beagle xM > Reading boot sector > Loading u-boot.bin from mmc > > > U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42) > > OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz > OMAP3 Beagle board + LPDDR/NAND > I2C: ready > DRAM: 512 MiB > NAND: 0 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - readenv() failed, using default environment > > In: serial > Out: serial > Err: serial > Beagle xM Rev C > No EEPROM on expansion board > Die ID #577200229ff80000016849a901022026 > Hit any key to stop autoboot: 0 > The user button is currently NOT pressed. > SD/MMC found on device 0 > reading uEnv.txt > > 134 bytes read > Loaded environment from uEnv.txt > Importing environment from mmc ... > Loading file "/boot/uImage" from mmc device 0:2 (xxa2) > 2033192 bytes read > Booting from mmc ... > ## Booting kernel from Legacy Image at 80200000 ... > Image Name: Linux-2.6.38.4-kirkwood > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2033128 Bytes = 1.9 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... OK > Loading Kernel Image ... > ################################################################# > > After the Loading Kernel Image , message nothing is happening. > Can anyone Help? > > Thanks, > Chekkiizhar > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.armedslack.org/pipermail/armedslack/attachments/20121021/beefdf0d/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Sun, 21 Oct 2012 13:34:54 +0100 (BST) > From: Stuart Winter > To: Slackware ARM port > Subject: Re: [ARMedslack] Failed to Boot ARMSlackware [13.37] in > Beagle Board -xm - Rev C > Message-ID: > > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Sun, 21 Oct 2012, chekkizhar N wrote: > > [..] > > 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4, > in > > /etc/boot dir. > > 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file > > /etc/boot? what is using /etc/boot ? > serial console in /etc/fstab? I assume you mean /etc/inittab > > The 'kirkwood' kernels are for the Marvell Kirkwood systems such as the > Sheevaplug, not machines with a 'Cortex' CPU like the Beagleboard. > Slackware ARM does not provided kernels for the Cortex. In Linux 3.7 > with the planned one kernel for all, once I've understood how it works > I'll include support for as many of the main architectures as I can. > > For now, google 'armedslack beagleboard' and hopefully there'll be enough > there to get you going. > > > ------------------------------ > > Message: 3 > Date: Wed, 24 Oct 2012 15:02:20 +0200 > From: Frank Donkers > To: armedslack at lists.armedslack.org > Subject: [ARMedslack] Using a bootdisk to install armedslack on > TrimSlice > Message-ID: <5087E6DC.1090704 at zonnet.nl> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi all, > > I wanted to install armedslack 14.0 on my new TrimSlice, but didn't feel > like setting up any (boot) servers. According to the wiki, the stock > firmware looks for a boot.scr script file on an attached SD card, > micro-SD or USB device, so I decided to use that method. Here are my steps: > > 1. You need the mkimage command from the u-boot toolkit. Install the > u-boot-tools package from AlienBOB's repository. > > 2. Create a new text file called boot.cmd with the following content: > --------------------------------------------------------------- > # Slackware u-boot installation script. Create image with: > # mkimage -A arm -O linux -T script -C none -d boot.cmd boot.scr > setenv kerneladdr 0x00800000 > setenv initrdaddr 0x01100000 > setenv kernelfile /boot/uImage-tegra > setenv initrdfile /boot/uinitrd-tegra.img > # > setenv loadinitrd ${fs}load ${interface} ${device} ${initrdaddr} > ${initrdfile} > setenv loadkernel ${fs}load ${interface} ${device} ${kerneladdr} > ${kernelfile} > setenv bootargs console=ttyS0,115200 nodhcp kbd=uk root=/dev/ram rw > setenv bootcmd bootm ${kerneladdr} ${initrdaddr} > # > run loadinitrd > run loadkernel > bootd > --------------------------------------------------------------- > > 3. Create the script file as follows: > mkimage -A arm -O linux -T script -C none -d boot.cmd boot.scr > > 4. Take an SD card or USB pendrive with an ext2/ext3/fat filesystem and > enough room for the kernel and root fs. Create a new /boot directory on > it. Copy the new boot.scr file to /boot. > > 5. From the ARM tree, copy isolinux/uinitrd-tegra.img and > kernels/tegra/uImage-tegra to /boot. > > 6. Now insert the card/pendrive and start the TrimSlice. The default > firmware will find the boot.scr file and execute it. This will load the > slackware installer. I have my ARM tree on an external USB disk, so I > installed from a pre-mounted directory. > > 7. Finish with the regular INSTALL_TEGRA.TXT instructions to setup u-boot. > > That's it. If your install device is large enough, you could put the ARM > tree on that. My external HD has xfs, so I couldn't combine those steps. > I tried to mount the SD card from the installer, but I couldn't get that > to work. Maybe I did something wrong... > > NOTE: during the process, I upgraded the firmware to the latest 2012 > version. Big mistake; that version only works with the 3.5 kernel, so I > couldn't boot. The 2010 firmware version works fine. > > Anyway, thought I would share this. Let me know what you think. > > regards, > Frank Donkers. > > > ------------------------------ > > Message: 4 > Date: Fri, 26 Oct 2012 20:04:57 +0100 > From: Ottavio Caruso > To: ARMedslack at lists.armedslack.org > Subject: Re: [ARMedslack] New Samsung Chromebook > Message-ID: > 9uQM2CFr+kE+AkrGTZ+yHEUVLOq4wDg at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 19 October 2012 10:42, Ottavio Caruso wrote: > > Does anybody know which ARM processor it has and if it can potentially > > run Slackware ARM in a proper and easy way? > > Olof Johansson has just posted a way to install an alternative Linux > distro on the new Chromebook: > https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ > > He has succeded with Suse just using the Suse root filesystem and the > Chrome OS stock kernel. It looks like a complicated procedure (at > least for me) and the catch is that it will boot from the Chrome > partition, but I understand that he and other developers are working > on booting from an external storage altogether. > > If anybody has any ideas on this subject they will do me a great > favour. I have a limited budget. I was saving money to buy the new > Genesi device which hasn't come yet but this little gem is tempting me > now. > > -- > Ottavio Caruso > > > ------------------------------ > > Message: 5 > Date: Sun, 28 Oct 2012 17:58:06 +0000 (GMT) > From: Stuart Winter > To: Slackware ARM port > Subject: Re: [ARMedslack] fix for missing Xvnc in tightvnc > Message-ID: > > Content-Type: TEXT/PLAIN; charset=US-ASCII > > > hey Frank, > > [..] > > With the help of xrdp and Xvnc I'm able to connect to my pi from any > windows > > pc without installing extra software. There are problems with > international > > keymaps, most of them patched for de layout in my version, thats not > perfect, > > but good enough for me. > > Thanks - I'll be putting out a patched package in 14.0 that contains Xvnc. > > -- > Stuart Winter > Slackware ARM: www.armedslack.org > > > ------------------------------ > > Message: 6 > Date: Tue, 30 Oct 2012 06:46:41 +0000 (GMT) > From: Davide > To: Slackware ARM port > Subject: Re: [ARMedslack] New Samsung Chromebook > Message-ID: > <1351579601.85320.YahooMailNeo at web29702.mail.ird.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > > > > > ________________________________ > > >> Does anybody know which ARM processor it has and if it can potentially > >> run Slackware ARM in a proper and easy way? > > > >Olof Johansson has just posted a way to install an alternative Linux > >distro on the new Chromebook: > >ttps://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ > > > >He has succeded with Suse just using the Suse root filesystem and the > >Chrome OS stock kernel. It looks like a complicated procedure (at > >least for me) and the catch is that it will boot from the Chrome > >partition, but I understand that he and other developers are working > >on booting from an external storage altogether. > > > >If anybody has any ideas on this subject they will do me a great > >favour. I have a limited budget. I was saving money to buy the new > >Genesi device which hasn't come yet but this little gem is tempting me > >now. > > Can't be much more difficult then any other arm platform: > get a kernel that works for the hardware, > get the tools to manipulate the kernel image so that the boot loader on > the hardware will liad it (may need to package the initrd in there too), > setup your initrd to look for whereever you plan to put the real root > filesystem (that will contain whatever distro uou prefer) > find a way of writing your boot image to the hardware (and root image if > not on a removable media), > cross your fingers and boot. > > Ciao > David > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.armedslack.org/pipermail/armedslack/attachments/20121030/a4c70b9a/attachment.html > > > > ------------------------------ > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > > End of ARMedslack Digest, Vol 34, Issue 5 > ***************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Tue Oct 30 10:01:48 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 30 Oct 2012 10:01:48 +0000 (GMT) Subject: [ARMedslack] Failed to Boot ARMSlackware [13.37] in Beagle Board -xm - Rev C In-Reply-To: References: Message-ID: On Tue, 30 Oct 2012, chekkizhar N wrote: > ok. I will wait and meanwhile will do searching as Stuart told. > I got this mail today [30/10/2012 in India ] only. > But, the question and the reply was made on that day [ Sun, 21 Oct 2012 ] > itself. > So, what went wrong? Time zone config on the local servers and people who wrote the mails. From m-lists at biscuit.org.uk Tue Oct 30 14:08:26 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 30 Oct 2012 14:08:26 +0000 (GMT) Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: <1351579601.85320.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1351579601.85320.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: > >> Does anybody know which ARM processor it has and if it can potentially > >> run Slackware ARM in a proper and easy way? I'm going to wait a month or so to see how people get on with them and whether there is support for it in the kernel.org kernel, as I don't use other people's kernels. If there is, I'll be getting one of these as it matches my goal of having a laptop running Slackware ARM. But then the dream will be fulfilled so I might have to stop working on Slackeare and get a new hobby ;-) -- Stuart Winter Slackware ARM: www.armedslack.org From fdonkers at zonnet.nl Tue Oct 30 16:31:38 2012 From: fdonkers at zonnet.nl (Frank Donkers) Date: Tue, 30 Oct 2012 17:31:38 +0100 Subject: [ARMedslack] Missing firmware for Ralink RT2870/RT3070 Wireless Adapter Message-ID: <509000EA.3070008@zonnet.nl> Hi, The Trimslice is using a Ralink RT2870/RT3070 adapter via USB. When starting this interface in Slackwarearm 14.0, it is complaining about missing firmware. I copied the rt2* and rt3* firmware files from /lib/firmware on my laptop to the trimslice and that fixed the problem. Wireless interface is now up. regards, Frank Donkers From m-lists at biscuit.org.uk Tue Oct 30 17:13:34 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 30 Oct 2012 17:13:34 +0000 (GMT) Subject: [ARMedslack] Missing firmware for Ralink RT2870/RT3070 Wireless Adapter In-Reply-To: <509000EA.3070008@zonnet.nl> References: <509000EA.3070008@zonnet.nl> Message-ID: It's patch-o-rama this week! > I copied the rt2* and rt3* firmware files from /lib/firmware on my laptop to > the trimslice and that fixed the problem. Wireless interface is now up. I did wonder if anybody'd ever notice that I was bundling the firmware from the kernel source tree rather than the separate repo that's used in x86. Thanks - I'll put an update out for that one soon. From pirkster at gmail.com Tue Oct 30 19:37:15 2012 From: pirkster at gmail.com (Steve Pirk) Date: Tue, 30 Oct 2012 12:37:15 -0700 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: Interesting that you mentioned Olaf Johansson. I saw his post and got very interested. If you want to learn about Chromium internals, I recommend a couple of mailing lists to join. The first is cros-discuss+subscribe at googlegroups.com. Olaf and many other "chromium.org" people are very active in discussing hacking and making the official and open source versions of Chrome OS work on various systems. Another group that discusses topics like dual boot and hacking Chrome OSin general, you might check a web only group called chromebook-central on Google groups. -- steve On Fri, Oct 26, 2012 at 12:04 PM, Ottavio Caruso wrote: > On 19 October 2012 10:42, Ottavio Caruso wrote: > > Does anybody know which ARM processor it has and if it can potentially > > run Slackware ARM in a proper and easy way? > > Olof Johansson has just posted a way to install an alternative Linux > distro on the new Chromebook: > https://plus.google.com/u/0/109993695638569781190/posts/b2fazijJppZ > > He has succeded with Suse just using the Suse root filesystem and the > Chrome OS stock kernel. It looks like a complicated procedure (at > least for me) and the catch is that it will boot from the Chrome > partition, but I understand that he and other developers are working > on booting from an external storage altogether. > > If anybody has any ideas on this subject they will do me a great > favour. I have a limited budget. I was saving money to buy the new > Genesi device which hasn't come yet but this little gem is tempting me > now. > > -- > Ottavio Caruso > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Tue Oct 30 20:48:27 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Tue, 30 Oct 2012 20:48:27 +0000 Subject: [ARMedslack] New Samsung Chromebook In-Reply-To: References: Message-ID: On 30 October 2012 19:37, Steve Pirk wrote: > Interesting that you mentioned Olaf Johansson. I saw his post and got very > interested. If you want to learn about Chromium internals, I recommend a > couple of mailing lists to join. The first is > cros-discuss+subscribe at googlegroups.com. Olaf and many other "chromium.org" > people are very active in discussing hacking and making the official and > open source versions of Chrome OS work on various systems. > > Another group that discusses topics like dual boot and hacking Chrome OSin > general, you might check a web only group called chromebook-central on > Google groups. Thanks. I have been subscribed to CRos-discuss for some time but never posted. I have just joined Chromebook Central and I have just posted a question there. By the way, I would like to see what Genesi have in mind. They were planning a device based on a quad-core Freescale IMX.6. I am more inclined to buy a device from a small and independent manufacturer than Google.