From openpandora at free.fr Sat Sep 7 09:07:33 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 7 Sep 2013 11:07:33 +0200 (CEST) Subject: [ARMedslack] Hardware advice, plug and laptop. In-Reply-To: <1660163675.220009272.1378544738836.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <266450001.220011510.1378544853557.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! I would like to buy a plug-like computer (small form, not especially wall-charger type) and also an ARM laptop. It's for a very common usage, internet, video chat, etc. Can you guys recommend me some products/websites ? LS. From louigi600 at yahoo.it Mon Sep 9 08:00:04 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 9 Sep 2013 09:00:04 +0100 (BST) Subject: [ARMedslack] Hardware advice, plug and laptop. In-Reply-To: <266450001.220011510.1378544853557.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <1660163675.220009272.1378544738836.JavaMail.root@zimbra53-e8.priv.proxad.net> <266450001.220011510.1378544853557.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1378713604.77913.YahooMailNeo@web173101.mail.ir2.yahoo.com> >Hi ! >I would like to buy a plug-like computer (small form, not especially wall-charger type) and also an ARM laptop. >It's for a very common usage, internet, video chat, etc. >Can you guys recommend me some products/websites ? A lot depends on what you want out of your plug like computer ,,, if you want video output of some sort probably a "Raspberry PI" or a? Olimex A13 (https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware) might be the sort of thing you want, but if it's to be used a sort of appliance (no need for video output) maybe some member of the plug family could be well suited. For the arm laptop, I don't know if you can get laptop sized ARM portables, but you might get lucky if you can get a netbook leftover that is arm based. Choose one that is know to be able to run custom images unless you are happy to use android. In some countries netbooks have been discontinued, in favor of the tablets, dew to poor demand. You might get lucky if you co to some hyperstore and find some ARM netbook leftover. For the arm laptop, I think that IBM have e new line of ARM powered laptops one thing you really want to make sure is that whatever you choose is know to be able to run custom images without going mad with issues in the boot loader. If it uses u-boot as boot loader there's a good chance that you can easily run custom linux images. ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Mon Sep 9 08:06:10 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Mon, 9 Sep 2013 09:06:10 +0100 Subject: [ARMedslack] Hardware advice, plug and laptop. In-Reply-To: <1378713604.77913.YahooMailNeo@web173101.mail.ir2.yahoo.com> References: <1660163675.220009272.1378544738836.JavaMail.root@zimbra53-e8.priv.proxad.net> <266450001.220011510.1378544853557.JavaMail.root@zimbra53-e8.priv.proxad.net> <1378713604.77913.YahooMailNeo@web173101.mail.ir2.yahoo.com> Message-ID: On 9 September 2013 09:00, Davide wrote: > For the arm laptop, I think that IBM have e new line of ARM powered laptops > one thing you really want to make sure is that whatever you choose is know > to be able to run custom images without going mad with issues in the boot > loader. If it uses u-boot as boot loader there's a good chance that you can > easily run custom linux images. Can you provide an example? I don't know of any ARM laptop that allows you to load your own image. Besides, you would have a problem or two with proprietary drivers. You see, my tablet has been stolen, I've returned my Windows 8 laptop and I am waiting to see if there is any development on the tablet side, but I don't see any. The ARM world is as proprietary and locked as it can be. The PC at work is the only one I use at the moment. -- Ottavio From louigi600 at yahoo.it Mon Sep 16 15:13:15 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 16 Sep 2013 16:13:15 +0100 (BST) Subject: [ARMedslack] Kernel for Allwinner A1X In-Reply-To: References: <979854346.198562218.1377188765222.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1379344395.68349.YahooMailNeo@web173106.mail.ir2.yahoo.com> It appears that the usb driver in the linux-sunxi kernel is bust (at least on A1X based devices) and I don't think that there is any chance of them fixing it any time soon. I even downloaded the 3.0 stable version sources hoping that at least their stable version (as opposed to the 3.4 developement kernel) still had working usb correctly, but it had the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb devices work properly while some that work correctly on the stock android kernel just don't work with their kernel). Anyone tried using vanilla kernels on Allwinner SOC based systems ? Anyone know what's going to work and what's not going to work if I try compiling a kernel from kernel.org ? touch screen is not important because that's not working well enough to be functional anyway. ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Sep 16 15:25:41 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 16 Sep 2013 16:25:41 +0100 (BST) Subject: [ARMedslack] Kernel for Allwinner A1X In-Reply-To: <1379344395.68349.YahooMailNeo@web173106.mail.ir2.yahoo.com> References: <979854346.198562218.1377188765222.JavaMail.root@zimbra53-e8.priv.proxad.net> <1379344395.68349.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: > It appears that the usb driver in the linux-sunxi kernel is bust (at > least on A1X based devices) and I don't think that there is any chance > of them fixing it any time soon. I even downloaded the 3.0 stable > version sources hoping that at least their stable version (as opposed to > the 3.4 developement kernel) still had working usb correctly, but it had > the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb > devices work properly while some that work correctly on the stock > android kernel just don't work with their kernel). > > Anyone tried using vanilla kernels on Allwinner SOC based systems ? > Anyone know what's going to work and what's not going to work if I try > compiling a kernel from kernel.org ? touch screen is not important > because that's not working well enough to be functional anyway. I don't have any Allwiner machines, but I did add some Allwinner SoC configs into the Linux 3.10 kernels. If there are any patches, I could apply them to Linux 3.10. I think we'll be using Linux 3.10 for the Slackware 14.1 release. I did try Linux 3.11 but it was quite broken. -- Stuart Winter Slackware ARM: http://arm.slackware.com From openpandora at free.fr Tue Sep 17 17:31:16 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 17 Sep 2013 19:31:16 +0200 (CEST) Subject: [ARMedslack] fbdev ABI problem in -current and new video driver In-Reply-To: <1870309880.236167036.1379438952740.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <2020418742.236169152.1379439076436.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! So i'm having trouble using fbdev X driver, i got a Server ABI 14 and driver ABI 13 error. Also, just to inform there's an new X driver for ARM, dunno its state, here's the link: http://git.linaro.org/gitweb?p=arm/xorg/driver/xf86-video-armsoc.git Cheers. From m-lists at biscuit.org.uk Tue Sep 17 20:46:58 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 17 Sep 2013 21:46:58 +0100 (BST) Subject: [ARMedslack] fbdev ABI problem in -current and new video driver In-Reply-To: <2020418742.236169152.1379439076436.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <2020418742.236169152.1379439076436.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: Hello > So i'm having trouble using fbdev X driver, i got a Server ABI 14 and driver ABI 13 error. Thanks for that, it'd slipped through the cracks of the last rebuild round. > Also, just to inform there's an new X driver for ARM, dunno its state, here's the link: > http://git.linaro.org/gitweb?p=arm/xorg/driver/xf86-video-armsoc.git I've updated this to the latest snapshot. -- Stuart Winter Slackware ARM: http://arm.slackware.com From openpandora at free.fr Tue Sep 17 21:20:06 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 17 Sep 2013 23:20:06 +0200 (CEST) Subject: [ARMedslack] fbdev ABI problem in -current and new video driver In-Reply-To: Message-ID: <485966233.236417217.1379452806749.JavaMail.root@zimbra53-e8.priv.proxad.net> Cool ! I usually report bugs i create myself, so i'm happy to finally be useful ;^) . ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Mardi 17 Septembre 2013 22:46:58 Objet: Re: [ARMedslack] fbdev ABI problem in -current and new video driver Hello > So i'm having trouble using fbdev X driver, i got a Server ABI 14 and driver ABI 13 error. Thanks for that, it'd slipped through the cracks of the last rebuild round. > Also, just to inform there's an new X driver for ARM, dunno its state, here's the link: > http://git.linaro.org/gitweb?p=arm/xorg/driver/xf86-video-armsoc.git I've updated this to the latest snapshot. -- Stuart Winter Slackware ARM: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From louigi600 at yahoo.it Fri Sep 20 09:08:32 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 20 Sep 2013 10:08:32 +0100 (BST) Subject: [ARMedslack] Skype on ARM linux In-Reply-To: <485966233.236417217.1379452806749.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <485966233.236417217.1379452806749.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1379668112.28093.YahooMailNeo@web173105.mail.ir2.yahoo.com> I'll begin my stating that I do not consider Android as having much to do with ARM linux. This this in mind what are the alternatives, if any, for having skype on ARM linux ? Is there some other instant messaging client (chat and video capable) that is knows to work well on ARM linux ? I read somewhere that pidgin supports video chat as of version 2.6: anyone tried video chatting with it ? will it work on Slackware ARM without chasing dependencies till you're driven nuts ? ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From openpandora at free.fr Fri Sep 20 19:20:49 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 20 Sep 2013 21:20:49 +0200 (CEST) Subject: [ARMedslack] Skype on ARM linux In-Reply-To: <1379668112.28093.YahooMailNeo@web173105.mail.ir2.yahoo.com> Message-ID: <882375014.241571237.1379704849142.JavaMail.root@zimbra53-e8.priv.proxad.net> Ekiga works well with VOIP, and is supposed to handle video but i've never tested. ----- Mail original ----- De: "Davide" ?: "Slackware ARM port" Envoy?: Vendredi 20 Septembre 2013 11:08:32 Objet: [ARMedslack] Skype on ARM linux I'll begin my stating that I do not consider Android as having much to do with ARM linux. This this in mind what are the alternatives, if any, for having skype on ARM linux ? Is there some other instant messaging client (chat and video capable) that is knows to work well on ARM linux ? I read somewhere that pidgin supports video chat as of version 2.6: anyone tried video chatting with it ? will it work on Slackware ARM without chasing dependencies till you're driven nuts ? ATB David _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From openpandora at free.fr Fri Sep 20 19:21:49 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Fri, 20 Sep 2013 21:21:49 +0200 (CEST) Subject: [ARMedslack] Skype on ARM linux In-Reply-To: <1379668112.28093.YahooMailNeo@web173105.mail.ir2.yahoo.com> Message-ID: <1004354206.241571837.1379704909449.JavaMail.root@zimbra53-e8.priv.proxad.net> Oh, there's also Linphone which is pretty good. ----- Mail original ----- De: "Davide" ?: "Slackware ARM port" Envoy?: Vendredi 20 Septembre 2013 11:08:32 Objet: [ARMedslack] Skype on ARM linux I'll begin my stating that I do not consider Android as having much to do with ARM linux. This this in mind what are the alternatives, if any, for having skype on ARM linux ? Is there some other instant messaging client (chat and video capable) that is knows to work well on ARM linux ? I read somewhere that pidgin supports video chat as of version 2.6: anyone tried video chatting with it ? will it work on Slackware ARM without chasing dependencies till you're driven nuts ? ATB David _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From louigi600 at yahoo.it Sat Sep 21 05:39:25 2013 From: louigi600 at yahoo.it (Davide) Date: Sat, 21 Sep 2013 06:39:25 +0100 (BST) Subject: [ARMedslack] Skype on ARM linux In-Reply-To: <1004354206.241571837.1379704909449.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <1379668112.28093.YahooMailNeo@web173105.mail.ir2.yahoo.com> <1004354206.241571837.1379704909449.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1379741965.21524.YahooMailNeo@web173103.mail.ir2.yahoo.com> Yesterday I did a bit of research and found a few more options: kopete (does not properly support socks proxy so I cannot use it @ work but appart from that looks quite promising and is already packaged in Slackware), pidgin (needs gnome to have the video/audio stuff work properly, I'm not going to evade all the gnome dependencies any time soon), ekiga (I remember having to work quite hard to get some sort of basic functionality on x86 slackware last time I tried it as soft phone @ work, I'll do without that) I've still to try amsn linphone (I remember having to exclude this as s soft phone option @ work and hadto go with ekiga, but I can't recall why) ATB David ________________________________ Da: "openpandora at free.fr" A: Davide ; Slackware ARM port Inviato: Venerd? 20 Settembre 2013 21:21 Oggetto: Re: [ARMedslack] Skype on ARM linux Oh, there's also Linphone which is pretty good. ----- Mail original ----- De: "Davide" ?: "Slackware ARM port" Envoy?: Vendredi 20 Septembre 2013 11:08:32 Objet: [ARMedslack] Skype on ARM linux I'll begin my stating that I do not consider Android as having much to do with ARM linux. This this in mind what are the alternatives, if any, for having skype on ARM linux ? Is there some other instant messaging client (chat and video capable) that is knows to work well on ARM linux ? I read somewhere that pidgin supports video chat as of version 2.6: anyone tried video chatting with it ? will it work on Slackware ARM without chasing dependencies till you're driven nuts ? ATB David _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Sun Sep 22 13:08:14 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Sun, 22 Sep 2013 09:08:14 -0400 Subject: [ARMedslack] fw_env,conf offsets for Pogoplugs and Dockstars Message-ID: <523EEBBE.8000605@laprjns.com> Hi, Would it be possible to add the following offsets in the stock /etc/fw_env.conf file? # Dockstar and Pogoplug offsets: /dev/mtd0 0xc0000 0x20000 0x20000 I have several Kirkwood based Dockstars and Pogoplugs running Slackwarearm and I always have to update this configuration file. Regards and thank you for Slackwarearm Rich Lapointe (laprjns) From m-lists at biscuit.org.uk Mon Sep 23 16:16:25 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 23 Sep 2013 17:16:25 +0100 (BST) Subject: [ARMedslack] fw_env,conf offsets for Pogoplugs and Dockstars In-Reply-To: <523EEBBE.8000605@laprjns.com> References: <523EEBBE.8000605@laprjns.com> Message-ID: > > Would it be possible to add the following offsets in the stock > /etc/fw_env.conf file? Yes I've added it into the config file and it'll be pushed out in the next batch. From richard.lapointe at gmail.com Mon Sep 23 22:49:46 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Mon, 23 Sep 2013 18:49:46 -0400 Subject: [ARMedslack] fw_env,conf offsets for Pogoplugs and Dockstars In-Reply-To: References: <523EEBBE.8000605@laprjns.com> Message-ID: <5240C58A.8050300@laprjns.com> Thanks! Rich Lapointe On 09/23/2013 12:16 PM, Stuart Winter wrote: >> Would it be possible to add the following offsets in the stock >> /etc/fw_env.conf file? > Yes I've added it into the config file and it'll be pushed out in the next > batch. > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From louigi600 at yahoo.it Tue Sep 24 08:38:59 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 24 Sep 2013 09:38:59 +0100 (BST) Subject: [ARMedslack] Kernel for Allwinner A1X In-Reply-To: References: <979854346.198562218.1377188765222.JavaMail.root@zimbra53-e8.priv.proxad.net> <1379344395.68349.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: <1380011939.99207.YahooMailNeo@web173102.mail.ir2.yahoo.com> >> It appears that the usb driver in the linux-sunxi kernel is bust (at >> least on A1X based devices) and I don't think that there is any chance >> of them fixing it any time soon. I even downloaded the 3.0 stable >> version sources hoping that at least their stable version (as opposed to >> the 3.4 developement kernel) still had working usb correctly, but it had >> the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb >> devices work properly while some that work correctly on the stock >> android kernel just don't work with their kernel). >> >> Anyone tried using vanilla kernels on Allwinner SOC based systems ? >> Anyone know what's going to work and what's not going to work if I try >> compiling a kernel from kernel.org ? touch screen is not important >> because that's not working well enough to be functional anyway. >I don't have any Allwiner machines, but I did add some Allwinner SoC >configs into the Linux 3.10 kernels.? If there are any patches, I could >apply them to Linux 3.10.? I think we'll be using Linux 3.10 for the >Slackware 14.1 release.? I did try Linux 3.11 but it was quite broken. I'm gonna try building 3.10.12 without any patches at all just to see what's going to work and what's not. ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Sep 24 09:19:54 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 24 Sep 2013 10:19:54 +0100 (BST) Subject: [ARMedslack] Kernel for Allwinner A1X In-Reply-To: <1380011939.99207.YahooMailNeo@web173102.mail.ir2.yahoo.com> References: <979854346.198562218.1377188765222.JavaMail.root@zimbra53-e8.priv.proxad.net> <1379344395.68349.YahooMailNeo@web173106.mail.ir2.yahoo.com> <1380011939.99207.YahooMailNeo@web173102.mail.ir2.yahoo.com> Message-ID: <1380014394.18525.YahooMailNeo@web173106.mail.ir2.yahoo.com> >>> It appears that the usb driver in the linux-sunxi kernel is bust (at >>> least on A1X based devices) and I don't think that there is any chance >>> of them fixing it any time soon. I even downloaded the 3.0 stable >>> version sources hoping that at least their stable version (as opposed to >>> the 3.4 developement kernel) still had working usb correctly, but it had >>> the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb >>> devices work properly while some that work correctly on the stock >>> android kernel just don't work with their kernel). >>> >>> Anyone tried using vanilla kernels on Allwinner SOC based systems ? >>> Anyone know what's going to work and what's not going to work if I try >>> compiling a kernel from kernel.org ? touch screen is not important >>> because that's not working well enough to be functional anyway. >>I don't have any Allwiner machines, but I did add some Allwinner SoC >>configs into the Linux 3.10 kernels.? If there are any patches, I could >>apply them to Linux 3.10.? I think we'll be using Linux 3.10 for the >>Slackware 14.1 release.? I did try Linux 3.11 but it was quite broken. >I'm gonna try building 3.10.12 without any patches at all just to see what's going to work and what's not. It looks like usb is not going to work right because the A13 has a specific usb controller that is not in the vanilla kernel tree. Maybe it will work by applying some patches ... but the linux-sunxi team is working only on 3.0 amd 3.4 kernels. I doubt that the patches will apply trouble free to 3.10 kernel. I'm kindof stuck :-( ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Sep 24 09:19:54 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 24 Sep 2013 10:19:54 +0100 (BST) Subject: [ARMedslack] Kernel for Allwinner A1X In-Reply-To: <1380011939.99207.YahooMailNeo@web173102.mail.ir2.yahoo.com> References: <979854346.198562218.1377188765222.JavaMail.root@zimbra53-e8.priv.proxad.net> <1379344395.68349.YahooMailNeo@web173106.mail.ir2.yahoo.com> <1380011939.99207.YahooMailNeo@web173102.mail.ir2.yahoo.com> Message-ID: <1380014394.18525.YahooMailNeo@web173106.mail.ir2.yahoo.com> >>> It appears that the usb driver in the linux-sunxi kernel is bust (at >>> least on A1X based devices) and I don't think that there is any chance >>> of them fixing it any time soon. I even downloaded the 3.0 stable >>> version sources hoping that at least their stable version (as opposed to >>> the 3.4 developement kernel) still had working usb correctly, but it had >>> the exact same issues as the 3.4 linux-sunxi kernel (ie only some usb >>> devices work properly while some that work correctly on the stock >>> android kernel just don't work with their kernel). >>> >>> Anyone tried using vanilla kernels on Allwinner SOC based systems ? >>> Anyone know what's going to work and what's not going to work if I try >>> compiling a kernel from kernel.org ? touch screen is not important >>> because that's not working well enough to be functional anyway. >>I don't have any Allwiner machines, but I did add some Allwinner SoC >>configs into the Linux 3.10 kernels.? If there are any patches, I could >>apply them to Linux 3.10.? I think we'll be using Linux 3.10 for the >>Slackware 14.1 release.? I did try Linux 3.11 but it was quite broken. >I'm gonna try building 3.10.12 without any patches at all just to see what's going to work and what's not. It looks like usb is not going to work right because the A13 has a specific usb controller that is not in the vanilla kernel tree. Maybe it will work by applying some patches ... but the linux-sunxi team is working only on 3.0 amd 3.4 kernels. I doubt that the patches will apply trouble free to 3.10 kernel. I'm kindof stuck :-( ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Wed Sep 25 14:46:29 2013 From: louigi600 at yahoo.it (Davide) Date: Wed, 25 Sep 2013 15:46:29 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: References: <523EEBBE.8000605@laprjns.com> Message-ID: <1380120389.87434.YahooMailNeo@web173104.mail.ir2.yahoo.com> I got a friend to lend me a PI? for a week ... I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) I'm supposing that the first partition (the dos one) is where this stuff should be put ? The content in there looks about right: root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00007091 ???????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux root at darkstar:/tmp# echo $((32 * 512)) 16384 root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img root at darkstar:/tmp# modprobe vfat root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root at darkstar:/tmp# ls /mnt/floppy/ COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* bootcode.bin*?????????????????? fixup_cd.dat* cmdline.txt*??????????????????? initrd-raspberrypi.img* root at darkstar:/tmp# I plan to play a little with a miniroot so I won't need an 8Gb SD :) ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Wed Sep 25 15:59:08 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Wed, 25 Sep 2013 15:59:08 +0000 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380120389.87434.YahooMailNeo@web173104.mail.ir2.yahoo.com> References: <523EEBBE.8000605@laprjns.com> <1380120389.87434.YahooMailNeo@web173104.mail.ir2.yahoo.com> Message-ID: <1100813190-1380124750-cardhu_decombobulator_blackberry.rim.net-438236202-@b15.c14.bise7.blackberry> Try the installer image. The gpu boots the system. At work now so can' explain further at he moment. Regards Stanley Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Davide Sender: "ARMedslack" Date: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM port Reply-To: Davide , Slackware ARM port Subject: [ARMedslack] A quick primer for the PI _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From stanley at stanleygarvey.com Wed Sep 25 18:58:51 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Wed, 25 Sep 2013 18:58:51 +0000 Subject: [ARMedslack] A quick primer for the PI Message-ID: <942830333-1380135532-cardhu_decombobulator_blackberry.rim.net-1676274212-@b15.c14.bise7.blackberry> The pi requires a fat filesystem to boot from. That partition is normally mountesd on /boot and should contain a kernel - default kernel.img, start.elf, bootcode.bin, cmdline.txt and optionally a config.txt which is used to overide defaut settings. ------Original Message------ From: stanley at stanleygarvey.com Sender: ARMedslack To: Davide To: Slackware ARM port ReplyTo: stanley at stanleygarvey.com ReplyTo: Slackware ARM port Subject: Re: [ARMedslack] A quick primer for the PI Sent: 25 Sep 2013 16:59 Try the installer image. The gpu boots the system. At work now so can' explain further at he moment. Regards Stanley Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Davide Sender: "ARMedslack" Date: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM port Reply-To: Davide , Slackware ARM port Subject: [ARMedslack] A quick primer for the PI _______________________________________________ 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 Sent from my BlackBerry smartphone from Virgin Media From dowelld at netscape.net Wed Sep 25 21:54:35 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Wed, 25 Sep 2013 17:54:35 -0400 (EDT) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380120389.87434.YahooMailNeo@web173104.mail.ir2.yahoo.com> References: <523EEBBE.8000605@laprjns.com> <1380120389.87434.YahooMailNeo@web173104.mail.ir2.yahoo.com> Message-ID: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> -----Original Message----- From: Davide To: Slackware ARM port Sent: Wed, Sep 25, 2013 3:46 pm Subject: [ARMedslack] A quick primer for the PI I got a friend to lend me a PI for a week ... I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: what does the GPU look for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) I'm supposing that the first partition (the dos one) is where this stuff should be put ? The content in there looks about right: root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00007091 Device Boot Start End Blocks Id System slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux swap slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux root at darkstar:/tmp# echo $((32 * 512)) 16384 root at darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img root at darkstar:/tmp# modprobe vfat root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root at darkstar:/tmp# ls /mnt/floppy/ COPYING.linux* config-raspberrypi-3.2.27* start.elf* LICENCE.broadcom* config.txt* start_cd.elf* System.map-raspberrypi-3.2.27* fixup.dat* zImage-raspberrypi-3.2.27* bootcode.bin* fixup_cd.dat* cmdline.txt* initrd-raspberrypi.img* root at darkstar:/tmp# I plan to play a little with a miniroot so I won't need an 8Gb SD :) ATB David Hi David, The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then loads kernel.img, and feeds it the contents of cmdline.txt. So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Sep 26 07:13:42 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 08:13:42 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <942830333-1380135532-cardhu_decombobulator_blackberry.rim.net-1676274212-@b15.c14.bise7.blackberry> References: <942830333-1380135532-cardhu_decombobulator_blackberry.rim.net-1676274212-@b15.c14.bise7.blackberry> Message-ID: <1380179622.36562.YahooMailNeo@web173105.mail.ir2.yahoo.com> Where can I get more details on how the PI boots ? Does the GPU get properly initialized right away ? can I see the kenel booting on the HDMI output ? or do I need a serial console for that ? So all the other files are not necessary for booting ? COPYING.linux and LICENCE.broadcom are probabbly there for the boot code ... I'm sure I can omit them safely. But what about fixup.dat , fixup_cd.dat and start_cd.elf ? I don't really want to do the install thing as I generally prefer to start from a miniroot and add what I need rather then answring a lot of questions, tinkering with tagfiles or installing everything. On a PC with 1Tb of mass storage installing everything just to going fast is ok ... but on slower hardware with slower flash storage I really prefer the miniroot way. Regards David ________________________________ Da: "stanley at stanleygarvey.com" A: stanley at stanleygarvey.com; Slackware ARM port Inviato: Mercoled? 25 Settembre 2013 20:58 Oggetto: Re: [ARMedslack] A quick primer for the PI The pi requires a fat filesystem to boot from. That partition is normally mountesd on /boot and should contain a kernel - default kernel.img, start.elf, bootcode.bin, cmdline.txt and optionally a config.txt which is used to overide defaut settings. ------Original Message------ From: stanley at stanleygarvey.com Sender: ARMedslack To: Davide To: Slackware ARM port ReplyTo: stanley at stanleygarvey.com ReplyTo: Slackware ARM port Subject: Re: [ARMedslack] A quick primer for the PI Sent: 25 Sep 2013 16:59 Try the installer image. The gpu boots the system. At work now so can' explain further at he moment. Regards Stanley Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Davide Sender: "ARMedslack" Date: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM port Reply-To: Davide , ??? Slackware ARM port? Subject: [ARMedslack] A quick primer for the PI _______________________________________________ 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 Sent from my BlackBerry smartphone from Virgin Media _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Sep 26 07:13:42 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 08:13:42 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <942830333-1380135532-cardhu_decombobulator_blackberry.rim.net-1676274212-@b15.c14.bise7.blackberry> References: <942830333-1380135532-cardhu_decombobulator_blackberry.rim.net-1676274212-@b15.c14.bise7.blackberry> Message-ID: <1380179622.36562.YahooMailNeo@web173105.mail.ir2.yahoo.com> Where can I get more details on how the PI boots ? Does the GPU get properly initialized right away ? can I see the kenel booting on the HDMI output ? or do I need a serial console for that ? So all the other files are not necessary for booting ? COPYING.linux and LICENCE.broadcom are probabbly there for the boot code ... I'm sure I can omit them safely. But what about fixup.dat , fixup_cd.dat and start_cd.elf ? I don't really want to do the install thing as I generally prefer to start from a miniroot and add what I need rather then answring a lot of questions, tinkering with tagfiles or installing everything. On a PC with 1Tb of mass storage installing everything just to going fast is ok ... but on slower hardware with slower flash storage I really prefer the miniroot way. Regards David ________________________________ Da: "stanley at stanleygarvey.com" A: stanley at stanleygarvey.com; Slackware ARM port Inviato: Mercoled? 25 Settembre 2013 20:58 Oggetto: Re: [ARMedslack] A quick primer for the PI The pi requires a fat filesystem to boot from. That partition is normally mountesd on /boot and should contain a kernel - default kernel.img, start.elf, bootcode.bin, cmdline.txt and optionally a config.txt which is used to overide defaut settings. ------Original Message------ From: stanley at stanleygarvey.com Sender: ARMedslack To: Davide To: Slackware ARM port ReplyTo: stanley at stanleygarvey.com ReplyTo: Slackware ARM port Subject: Re: [ARMedslack] A quick primer for the PI Sent: 25 Sep 2013 16:59 Try the installer image. The gpu boots the system. At work now so can' explain further at he moment. Regards Stanley Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Davide Sender: "ARMedslack" Date: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM port Reply-To: Davide , ??? Slackware ARM port? Subject: [ARMedslack] A quick primer for the PI _______________________________________________ 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 Sent from my BlackBerry smartphone from Virgin Media _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Sep 26 07:25:10 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 08:25:10 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> References: <523EEBBE.8000605@laprjns.com> <1380120389.87434.YahooMailNeo@web173104.mail.ir2.yahoo.com> <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> Message-ID: <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> >>I got a friend to lend me a PI? for a week ... >>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>The content in there looks about right: >>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>Units = sectors of 1 * 512 = 512 bytes >>Sector size (logical/physical): 512 bytes / 512 bytes >>I/O size (minimum/optimal): 512 bytes / 512 bytes >>Disk identifier: 0x00007091 >> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>root at darkstar:/tmp# echo $((32 * 512)) >>16384 >>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>root at darkstar:/tmp# modprobe vfat >>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>root at darkstar:/tmp# ls /mnt/floppy/ >>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>bootcode.bin*?????????????????? fixup_cd.dat* >>cmdline.txt*??????????????????? initrd-raspberrypi.img* >root at darkstar:/tmp# >>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >Hi David, Hi Dave ;) >The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! Is there something wrong with this image or is loader.bin optional ? >So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. Is the initrd loading governed by config.txt ? I see in there ramfsfile=initrd-raspberrypi.img Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? When is the HDMI output initiated ? ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Thu Sep 26 11:15:49 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Thu, 26 Sep 2013 12:15:49 +0100 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> Message-ID: <20130926111549.CB931FC3B57FA@bmail-n01.one.com> On Sep 26, 2013 08:25 "Davide" wrote: > > > >>I got a friend to lend me a PI for a week ... > > > > > > >>I had a quick look at the community links for slackware on the PI > >>but none really tell me what i want to know: > >>what does the GPU look for in the SD ? (as fas as I know it's the > >>GPU that loads stuff from SD into memory and then passes control to > >>it) > >>does it look for a second stage boot loader like a uboot image or > >>does it load kernel and initrd ? (bootcode.bin) > >>I'm supposing that the first partition (the dos one) is where this > >>stuff should be put ? > >>The content in there looks about right: > > >>root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img > > >>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes > >>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors > >>Units = sectors of 1 * 512 = 512 bytes > >>Sector size (logical/physical): 512 bytes / 512 bytes > >>I/O size (minimum/optimal): 512 bytes / 512 bytes > >>Disk identifier: 0x00007091 > > >> Device Boot Start End Blocks Id System > >>slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) > >>slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux > >>swap > >>slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux > >>root at darkstar:/tmp# echo $((32 * 512)) > >>16384 > >>root at darkstar:/tmp# losetup -o 16384 /dev/loop0 > >>slackwarearm-14.0-8GB-20130623.img > >>root at darkstar:/tmp# modprobe vfat > >>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ > >>root at darkstar:/tmp# ls /mnt/floppy/ > >>COPYING.linux* config-raspberrypi-3.2.27* start.elf* > >>LICENCE.broadcom* config.txt* start_cd.elf* > >>System.map-raspberrypi-3.2.27* fixup.dat* zImage-raspberrypi-3.2.27* > >>bootcode.bin* fixup_cd.dat* > >>cmdline.txt* initrd-raspberrypi.img* > >root at darkstar:/tmp# > > > >>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > > >Hi David, > Hi Dave ;) > >The GPU looks for bootcode.bin, which looks for and loads loader.bin. > >Loader.bin reads in config.txt (to configure the hardware) and loads > >start.elf (the GPU binary blob). Once it has configured the hardware, > >it then >loads kernel.img, and feeds it the contents of cmdline.txt. > > But on the readymade image from > http://stanleygarvey.com/slackwarearm_rpi/index.php there is no > loader.bin in the dos partition ! > Is there something wrong with this image or is loader.bin optional ? > > Hi Davide, ther is nothing wrong with the image, I use it at home, > > it could be that loader bin is a new addition to the Fat32 boot > > partitionfor Debian variants. the boot layout I use has not changed > > since last Christmas. > > >So you have to have bootcode.bin, loader.bin, config.txt, start.elf, > >kernel.img, and cmdline.txt, then if you load a ramdisk image in the > >cmdline.txt file you need the ramdisk image file. > > > yes > > Is the initrd loading governed by config.txt ? > > yes > > I see in there ramfsfile=initrd-raspberrypi.img > Can I change that manualy with vi and load a different initrd ? or > comment it out to not load an initrd at all ? > > > Yes you can edit the file with vi and load a different initrd. It is > > commented out in my config.txt as it is not required to boot a > > running system. initrd-raspberrypi.img is the installer, It has been > > left there so you can reinstall if you wish, it is a > > versatile-initrd that has been modified with a modified version of > > the mk-tegra.sh. > > When is the HDMI output initiated ? > > >Before the system comes up as the GPU boots the system. > > > if you ate looking for a mini root try the installer image, it is > > 1GB and is the standard slackwarearm installer so has busybox and > > other stuff. you won't be able to install a full system on 1GB the > > 3rd partition is a stub and should be deleted and recreated to use > > the remaining space on whatever size card you have before stating > > 'setup'. you may be able to get a base slackwarearm systm (a)(ap) > > series on a 4GB card. > Hope that helps, > Stanley. > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Sep 26 12:38:21 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <20130926111549.CB931FC3B57FA@bmail-n01.one.com> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> Message-ID: <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David ________________________________ Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: > >>>I got a friend to lend me a PI? for a week ... > >>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>The content in there looks about right: > >>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>Units = sectors of 1 * 512 = 512 bytes >>>Sector size (logical/physical): 512 bytes / 512 bytes >>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>Disk identifier: 0x00007091 > >>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>root at darkstar:/tmp# echo $((32 * 512)) >>>16384 >>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>root at darkstar:/tmp# modprobe vfat >>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>root at darkstar:/tmp# ls /mnt/floppy/ >>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>bootcode.bin*?????????????????? fixup_cd.dat* >>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>root at darkstar:/tmp# > > >>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >>Hi David, >Hi Dave ;) > >>The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. > >But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >Is there something wrong with this image or is loader.bin optional ? > >> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. > >>So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > >> yes > >Is the initrd loading governed by config.txt ? > >> yes > >I see in there ramfsfile=initrd-raspberrypi.img >Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > >> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. > >When is the HDMI output initiated ? > >>Before the system comes up as the GPU boots the system. > >>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >Hope that helps, >Stanley. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Thu Sep 26 12:52:53 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Thu, 26 Sep 2013 12:52:53 +0000 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> Message-ID: <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> Did you dd the image onto the card? What suze of card? Try the installer image at stanleygarvey.com Regards, Stanley Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Davide Date: Thu, 26 Sep 2013 13:38:21 To: stanley garvey; dowelld at netscape.net; armedslack at lists.armedslack.org Reply-To: Davide Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David ________________________________ Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: > >>>I got a friend to lend me a PI? for a week ... > >>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>The content in there looks about right: > >>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>Units = sectors of 1 * 512 = 512 bytes >>>Sector size (logical/physical): 512 bytes / 512 bytes >>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>Disk identifier: 0x00007091 > >>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>root at darkstar:/tmp# echo $((32 * 512)) >>>16384 >>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>root at darkstar:/tmp# modprobe vfat >>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>root at darkstar:/tmp# ls /mnt/floppy/ >>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>bootcode.bin*?????????????????? fixup_cd.dat* >>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>root at darkstar:/tmp# > > >>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >>Hi David, >Hi Dave ;) > >>The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. > >But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >Is there something wrong with this image or is loader.bin optional ? > >> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. > >>So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > >> yes > >Is the initrd loading governed by config.txt ? > >> yes > >I see in there ramfsfile=initrd-raspberrypi.img >Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > >> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. > >When is the HDMI output initiated ? > >>Before the system comes up as the GPU boots the system. > >>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >Hope that helps, >Stanley. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Thu Sep 26 12:58:39 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Thu, 26 Sep 2013 08:58:39 -0400 (EDT) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> Message-ID: <8D088CF412D4C23-9D4-B025@webmail-m288.sysops.aol.com> I recognise that behaviour, I encountered the same kind of behaviour. In my case it was because the bootloader code/GPU was trying to initialise the HDMI interface, and I run the pi headless. I fixed that by adding the line: hdmi_safe=1 to config.txt I'm using a later level of GPU firmware than you are, but I think that line was supported on the version you're using. The files I use to boot to the installer are available here http://www.dowelld.net/?p=49 the txt file explains how I use them. Thanks Dave -----Original Message----- From: Davide To: stanley garvey ; dowelld ; armedslack Sent: Thu, Sep 26, 2013 1:38 pm Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: >>I got a friend to lend me a PI for a week ... >>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>what does the GPU look for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>The content in there looks about right: >>root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img >>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>Units = sectors of 1 * 512 = 512 bytes >>Sector size (logical/physical): 512 bytes / 512 bytes >>I/O size (minimum/optimal): 512 bytes / 512 bytes >>Disk identifier: 0x00007091 >> Device Boot Start End Blocks Id System >>slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) >>slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux swap >>slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux >>root at darkstar:/tmp# echo $((32 * 512)) >>16384 >>root at darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img >>root at darkstar:/tmp# modprobe vfat >>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>root at darkstar:/tmp# ls /mnt/floppy/ >>COPYING.linux* config-raspberrypi-3.2.27* start.elf* >>LICENCE.broadcom* config.txt* start_cd.elf* >>System.map-raspberrypi-3.2.27* fixup.dat* zImage-raspberrypi-3.2.27* >>bootcode.bin* fixup_cd.dat* >>cmdline.txt* initrd-raspberrypi.img* >root at darkstar:/tmp# >>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >Hi David, Hi Dave ;) >The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! Is there something wrong with this image or is loader.bin optional ? > Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partition for Debian variants. the boot layout I use has not changed since last Christmas. >So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > yes Is the initrd loading governed by config.txt ? > yes I see in there ramfsfile=initrd-raspberrypi.img Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. When is the HDMI output initiated ? >Before the system comes up as the GPU boots the system. > if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. Hope that helps, Stanley. -------------- next part -------------- An HTML attachment was scrubbed... URL: From halinux at frontier.com Thu Sep 26 13:54:13 2013 From: halinux at frontier.com (Hal) Date: Thu, 26 Sep 2013 09:54:13 -0400 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> Message-ID: <20130926135413.GA2460@lnx6> On Thu, Sep 26, 2013 at 12:52:53PM +0000, stanley at stanleygarvey.com wrote: > Did you dd the image onto the card? > What suze of card? > Try the installer image at stanleygarvey.com > Regards, > Stanley FWIW; I had intermittent issues using dd so tried: cat xxxxx.img > /dev/sd_ Dunno why it worked better for three different distributions.. -- Hal UNIX-GNU/Linux; Slackware 13.1 kernel 2.6.33.4-smp-JFS From louigi600 at yahoo.it Thu Sep 26 14:23:43 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 15:23:43 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> Message-ID: <1380205423.18790.YahooMailNeo@web173105.mail.ir2.yahoo.com> No I formatted the filesystem myself and copied files into it. The firs lot of boot loader stuff was gotten out of http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip , unzipp created loop device with off set on the image first partition ... mounted it and copied files over. root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00007091 ???????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux root at darkstar:/tmp# echo $((32 * 512)) 16384 root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img root at darkstar:/tmp# modprobe vfat root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root at darkstar:/tmp# ls /mnt/floppy/ COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* bootcode.bin*?????????????????? fixup_cd.dat* cmdline.txt*??????????????????? initrd-raspberrypi.img* root at darkstar:/tmp# Is there something obscure that need to be done to the dor partition ? Regards David ________________________________ Da: "stanley at stanleygarvey.com" A: Davide ; "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" Inviato: Gioved? 26 Settembre 2013 14:52 Oggetto: Re: [ARMedslack] A quick primer for the PI Did you dd the image onto the card? What suze of card? Try the installer image at stanleygarvey.com Regards, Stanley Sent from my BlackBerry smartphone from Virgin Media ________________________________ From: Davide Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) To: stanley garvey; dowelld at netscape.net; armedslack at lists.armedslack.org ReplyTo: Davide Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David ________________________________ Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: > >>>I got a friend to lend me a PI? for a week ... > >>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>The content in there looks about right: > >>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>Units = sectors of 1 * 512 = 512 bytes >>>Sector size (logical/physical): 512 bytes / 512 bytes >>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>Disk identifier: 0x00007091 > >>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>root at darkstar:/tmp# echo $((32 * 512)) >>>16384 >>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>root at darkstar:/tmp# modprobe vfat >>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>root at darkstar:/tmp# ls /mnt/floppy/ >>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>bootcode.bin*?????????????????? fixup_cd.dat* >>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>root at darkstar:/tmp# > > >>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >>Hi David, >Hi Dave ;) > >>The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. > >But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >Is there something wrong with this image or is loader.bin optional ? > >> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. > >>So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > >> yes > >Is the initrd loading governed by config.txt ? > >> yes > >I see in there ramfsfile=initrd-raspberrypi.img >Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > >> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. > >When is the HDMI output initiated ? > >>Before the system comes up as the GPU boots the system. > >>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >Hope that helps, >Stanley. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Sep 26 14:30:25 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 15:30:25 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <8D088CF412D4C23-9D4-B025@webmail-m288.sysops.aol.com> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> <8D088CF412D4C23-9D4-B025@webmail-m288.sysops.aol.com> Message-ID: <1380205825.87541.YahooMailNeo@web173104.mail.ir2.yahoo.com> Hum ... I tried with both HDM plugged and unplugged ... made no difference. After having failed I fiddled with the config.txt ... this is what it look like stripped from comments: root at darkstar:/mnt/floppy# grep -vE "^ *$|^#" config.txt hdmi_safe=1 hdmi_force_hotplug=1 hdmi_drive=2 hdmi_mode=4 disable_overscan=1 kernel=zImage-raspberrypi-3.10.3 root at darkstar:/mnt/floppy# and this is the last content of the boot partition: root at darkstar:/mnt/floppy# ls -l total 49665 -rwxr-xr-x 1 root root??? 18693 Sep 26 10:18 COPYING.linux* -rwxr-xr-x 1 root root???? 1447 Sep 26 10:18 LICENCE.broadcom* -rwxr-xr-x 1 root root? 1536531 Aug? 1 03:23 System.map-raspberrypi-3.10.3* -rwxr-xr-x 1 root root? 1258940 Sep 26 10:18 System.map-raspberrypi-3.2.27* -rwxr-xr-x 1 root root??? 16536 Jul? 7? 2012 bootcode.bin* -rwxr-xr-x 1 root root????? 208 Sep 26 11:14 cmdline.txt* -rwxr-xr-x 1 root root??? 68928 Sep 26 11:05 config-raspberrypi-3.10.3* -rwxr-xr-x 1 root root??? 75124 Sep 26 10:18 config-raspberrypi-3.2.27* -rwxr-xr-x 1 root root??? 29619 Sep 26 11:49 config.txt* -rwxr-xr-x 1 root root 39558430 Sep 26 10:18 initrd-raspberrypi.img* -rwxr-xr-x 1 root root?? 275235 Jun 17? 2012 loader.bin* -rwxr-xr-x 1 root root? 2053296 Aug? 1? 2012 start.elf* -rwxr-xr-x 1 root root? 3233208 Aug? 1 03:23 zImage-raspberrypi-3.10.3* -rwxr-xr-x 1 root root? 2727800 Sep 26 10:18 zImage-raspberrypi-3.2.27* root at darkstar:/mnt/floppy# I'm puzzled ! David ________________________________ Da: "dowelld at netscape.net" A: louigi600 at yahoo.it; stanley at stanleygarvey.com; armedslack at lists.armedslack.org Inviato: Gioved? 26 Settembre 2013 14:58 Oggetto: Re: [ARMedslack] A quick primer for the PI I recognise that behaviour, I encountered the same kind of behaviour. In my case it was because the bootloader code/GPU was trying to initialise the HDMI interface, and I run the pi headless. I fixed that by adding the line: hdmi_safe=1 to config.txt I'm using a later level of GPU firmware than you are, but I think that line was supported on the version you're using. The files I use to boot to the installer are available here http://www.dowelld.net/?p=49 the txt file explains how I use them. Thanks Dave -----Original Message----- From: Davide To: stanley garvey ; dowelld ; armedslack Sent: Thu, Sep 26, 2013 1:38 pm Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David ________________________________ Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: > > >>>I got a friend to lend me a PI? for a week ... > > > > > > > > >>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>The content in there looks about right: > >>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>Units = sectors of 1 * 512 = 512 bytes >>>Sector size (logical/physical): 512 bytes / 512 bytes >>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>Disk identifier: 0x00007091 > >>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>root at darkstar:/tmp# echo $((32 * 512)) >>>16384 >>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>root at darkstar:/tmp# modprobe vfat >>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>root at darkstar:/tmp# ls /mnt/floppy/ >>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>bootcode.bin*?????????????????? fixup_cd.dat* >>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>root at darkstar:/tmp# > > >>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >>Hi David, >Hi Dave ;) > >>The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. > >But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >Is there something wrong with this image or is loader.bin optional ? > >> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. > >>So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > >> yes > >Is the initrd loading governed by config.txt ? > >> yes > >I see in there ramfsfile=initrd-raspberrypi.img >Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > >> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. > >When is the HDMI output initiated ? > >>Before the system comes up as the GPU boots the system. > >>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >Hope that helps, >Stanley. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Thu Sep 26 15:58:53 2013 From: stanley at stanleygarvey.com (stanley at stanleygarvey.com) Date: Thu, 26 Sep 2013 15:58:53 +0000 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380205423.18790.YahooMailNeo@web173105.mail.ir2.yahoo.com> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> <1380205423.18790.YahooMailNeo@web173105.mail.ir2.yahoo.com> Message-ID: <979531866-1380211135-cardhu_decombobulator_blackberry.rim.net-1174902497-@b15.c14.bise7.blackberry> No nothing obscure needs to be done it should just work. I checked today at home. These images have been tested on a multitude of boards and have never failed to boot. Have you created a swap and ext4 root fs? Donkt know if it will boot without these being present. Sent from my BlackBerry smartphone from Virgin Media -----Original Message----- From: Davide Date: Thu, 26 Sep 2013 15:23:43 To: stanley at stanleygarvey.com; dowelld at netscape.net; armedslack at lists.armedslack.org Reply-To: Davide Subject: Re: [ARMedslack] A quick primer for the PI No I formatted the filesystem myself and copied files into it. The firs lot of boot loader stuff was gotten out of http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip , unzipp created loop device with off set on the image first partition ... mounted it and copied files over. root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00007091 ???????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux root at darkstar:/tmp# echo $((32 * 512)) 16384 root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img root at darkstar:/tmp# modprobe vfat root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root at darkstar:/tmp# ls /mnt/floppy/ COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* bootcode.bin*?????????????????? fixup_cd.dat* cmdline.txt*??????????????????? initrd-raspberrypi.img* root at darkstar:/tmp# Is there something obscure that need to be done to the dor partition ? Regards David ________________________________ Da: "stanley at stanleygarvey.com" A: Davide ; "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" Inviato: Gioved? 26 Settembre 2013 14:52 Oggetto: Re: [ARMedslack] A quick primer for the PI Did you dd the image onto the card? What suze of card? Try the installer image at stanleygarvey.com Regards, Stanley Sent from my BlackBerry smartphone from Virgin Media ________________________________ From: Davide Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) To: stanley garvey; dowelld at netscape.net; armedslack at lists.armedslack.org ReplyTo: Davide Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David ________________________________ Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: > >>>I got a friend to lend me a PI? for a week ... > >>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>The content in there looks about right: > >>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>Units = sectors of 1 * 512 = 512 bytes >>>Sector size (logical/physical): 512 bytes / 512 bytes >>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>Disk identifier: 0x00007091 > >>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>root at darkstar:/tmp# echo $((32 * 512)) >>>16384 >>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>root at darkstar:/tmp# modprobe vfat >>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>root at darkstar:/tmp# ls /mnt/floppy/ >>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>bootcode.bin*?????????????????? fixup_cd.dat* >>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>root at darkstar:/tmp# > > >>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >>Hi David, >Hi Dave ;) > >>The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. > >But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >Is there something wrong with this image or is loader.bin optional ? > >> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. > >>So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > >> yes > >Is the initrd loading governed by config.txt ? > >> yes > >I see in there ramfsfile=initrd-raspberrypi.img >Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > >> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. > >When is the HDMI output initiated ? > >>Before the system comes up as the GPU boots the system. > >>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >Hope that helps, >Stanley. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomeks at spoko.eu.org Thu Sep 26 17:44:49 2013 From: tomeks at spoko.eu.org (Tom) Date: Thu, 26 Sep 2013 19:44:49 +0200 Subject: [ARMedslack] A quick primer for the PI Message-ID: <1366445387.20130926194449@spoko.eu.org> Davide, I've also had problems installing Slackware on RPi. My board/card did not work with kernel / images they provided. I've suggested Slackware for RPI should use Raspbian kernel - because it is ACTIVELY supported. Try my way https://salwach.pl/rpi_slackware >These images have been tested on a > multitude of boards and have never failed to boot. Recently I've bought 2nd RPi, just switched SD card to new one..and ooops...black screen. Old works, new one not. After download of "new" Raspbian and replacing bootloader I've got it working. RPi is NOT Arduino - it changes too fast. And guys here do not understand that or ignore it. Standard answer: "Works on my computer"....LOL Tom W li?cie z 26 wrze?nia 2013: From: stanley at stanleygarvey.com To: louigi600 at yahoo.it CC: ssc> No nothing obscure needs to be done it should just work. I ssc> checked today at home. These images have been tested on a ssc> multitude of boards and have never failed to boot. ssc> Have you created a swap and ext4 root fs? Donkt know if it will ssc> boot without these being present. ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> -----Original Message----- ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 15:23:43 ssc> To: stanley at stanleygarvey.com; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> Reply-To: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> No I formatted the filesystem myself and copied files into it. ssc> The firs lot of boot loader stuff was gotten out of ssc> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip ssc> , unzipp created loop device with off set on the image first ssc> partition ... mounted it and copied files over. ssc> root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors ssc> Units = sectors of ssc> 1 * 512 = 512 bytes ssc> Sector size (logical/physical): 512 bytes / 512 bytes ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes ssc> Disk identifier: 0x00007091 ssc> ???????????????????????????? Device Boot????? Start???????? End? Blocks?? Id? System ssc> slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663? 48816??? c? W95 FAT32 (LBA) ssc> slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847? 390592?? 82? Linux ssc> swap ssc> slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167? 7436160?? 83? Linux ssc> root at darkstar:/tmp# echo $((32 * 512)) ssc> 16384 ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0? ssc> slackwarearm-14.0-8GB-20130623.img ssc> root at darkstar:/tmp# modprobe vfat ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc> root at darkstar:/tmp# ls /mnt/floppy/ ssc> COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* ssc> LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* ssc> System.map-raspberrypi-3.2.27*? ssc> fixup.dat*????????????????? zImage-raspberrypi-3.2.27* ssc> bootcode.bin*?????????????????? fixup_cd.dat* ssc> cmdline.txt*??????????????????? initrd-raspberrypi.img* ssc> root at darkstar:/tmp# ssc> Is there something obscure that need to be done to the dor partition ? ssc> Regards ssc> David ssc> ________________________________ ssc> Da: "stanley at stanleygarvey.com" ssc> A: Davide ; "dowelld at netscape.net" ssc> ; "armedslack at lists.armedslack.org" ssc> ssc> Inviato: Gioved? 26 Settembre 2013 14:52 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc> ssc> Did you dd the image onto the card? ssc> What suze of card? ssc> Try the installer image at stanleygarvey.com ssc> Regards, ssc> Stanley ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> ________________________________ ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc> To: stanley garvey; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> ReplyTo: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> I can't get it to boot at all. ssc> If I turn the PI on I get the PER led solid on but the ACT led does this: ssc> first faint on, the bright on for a second or do then it goes off and stays off. ssc> I've tried 2 different SD cards supposing that the firs may have ssc> had some sort of compatibility issue but the second does the same thing. ssc> I downloaded updated boot stuff from here: ssc> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ssc> ... but nothing seems to change. ssc> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted ssc> I suspect that its not booting because if I take out the SD and ssc> mount in on the PC fsck does not detect the filesystem dirty flag ssc> that I should have if the thing booted but showed nothing on the TV. ssc> ATB ssc> David ssc> ________________________________ ssc> Da: stanley garvey ssc> A: "dowelld at netscape.net" ; ssc> "armedslack at lists.armedslack.org" ssc> ; Davide ; ssc> Slackware ARM port ssc> Inviato: Gioved? 26 Settembre 2013 13:15 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc> ssc> On Sep 26, 2013 08:25 "Davide" wrote: >> >>>>I got a friend to lend me a PI? for a week ... >> >>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>The content in there looks about right: >> >>>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >> >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>Units = sectors of ssc> 1 * 512 = 512 bytes >>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>Disk identifier: 0x00007091 >> >>>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux ssc> swap >>>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>16384 >>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>>root at darkstar:/tmp# modprobe vfat >>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>>System.map-raspberrypi-3.2.27*? ssc> fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>>bootcode.bin*?????????????????? fixup_cd.dat* >>>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>>root at darkstar:/tmp# >> >> >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >> >>>Hi David, >>Hi Dave ;) >> >>>The GPU looks for ssc> bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in ssc> config.txt (to configure the hardware) and loads start.elf (the GPU ssc> binary blob). Once it has configured the hardware, it then >loads ssc> kernel.img, and feeds it the contents of cmdline.txt. >> >>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>Is there something wrong with this image or is loader.bin optional ? >> >>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >> >>>So you have ssc> to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt ssc> file you need the ramdisk image file. >> >>> yes >> >>Is the initrd loading governed by config.txt ? >> >>> yes >> >>I see in there ramfsfile=initrd-raspberrypi.img >>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >> >>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >> >>When is the HDMI output initiated ? >> >>>Before the system ssc> comes up as the GPU boots the system. >> >>>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>Hope that helps, >>Stanley. >> >> >> >> >> >> >> >> >> >> >> From halinux at frontier.com Thu Sep 26 18:45:44 2013 From: halinux at frontier.com (Hal) Date: Thu, 26 Sep 2013 14:45:44 -0400 Subject: [ARMedslack] Tiny CLI Font Change?? Message-ID: <20130926184544.GA3519@lnx6> Exclusively Slackware since Version 1.0, I guess I'm used to the original 80x25 default font. :^).. I just acquired a RasPi B and installed armedslack13.37, that's running fine.. Searching the Web I see much dialogue but nothing, so far, for armedslack. Can someone point me to a site that might help getting my CLI screen font larger? I am using a 17" DVI monitor, Samsung 740B, but connecting the RasPi to a HDMI TV prints the same tiny font.. (I note that other RasPi ports boot and run with that same font.) TIA. -- Hal UNIX-GNU/Linux; Slackware 13.1 kernel 2.6.33.4-smp-JFS From louigi600 at yahoo.it Thu Sep 26 19:21:40 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 20:21:40 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <979531866-1380211135-cardhu_decombobulator_blackberry.rim.net-1174902497-@b15.c14.bise7.blackberry> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> <1380205423.18790.YahooMailNeo@web173105.mail.ir2.yahoo.com> <979531866-1380211135-cardhu_decombobulator_blackberry.rim.net-1174902497-@b15.c14.bise7.blackberry> Message-ID: <1380223300.89565.YahooMailNeo@web173102.mail.ir2.yahoo.com> No swap and? ext4 filesystem on the second partition, but I think I've edited corrispondingly cmdline and fstab. I also wrote the image to an SD card by using "dd if= of=/dev/ bs=4096" but that did not boot ... leds still do the same as before. Tomorrow I'll see if I can get the dude that lent it to me to lend me his rasbian image ... maybe I can see where the difference is. ATB David ________________________________ Da: "stanley at stanleygarvey.com" A: Davide ; "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" Inviato: Gioved? 26 Settembre 2013 17:58 Oggetto: Re: [ARMedslack] A quick primer for the PI No nothing obscure needs to be done it should just work. I checked today at home. These images have been tested on a multitude of boards and have never failed to boot. Have you created a swap and ext4 root fs? Donkt know if it will boot without these being present. Sent from my BlackBerry smartphone from Virgin Media ________________________________ From: Davide Date: Thu, 26 Sep 2013 15:23:43 +0100 (BST) To: stanley at stanleygarvey.com; dowelld at netscape.net; armedslack at lists.armedslack.org ReplyTo: Davide Subject: Re: [ARMedslack] A quick primer for the PI No I formatted the filesystem myself and copied files into it. The firs lot of boot loader stuff was gotten out of http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip , unzipp created loop device with off set on the image first partition ... mounted it and copied files over. root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00007091 ???????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux root at darkstar:/tmp# echo $((32 * 512)) 16384 root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img root at darkstar:/tmp# modprobe vfat root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root at darkstar:/tmp# ls /mnt/floppy/ COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* bootcode.bin*?????????????????? fixup_cd.dat* cmdline.txt*??????????????????? initrd-raspberrypi.img* root at darkstar:/tmp# Is there something obscure that need to be done to the dor partition ? Regards David ________________________________ Da: "stanley at stanleygarvey.com" A: Davide ; "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" Inviato: Gioved? 26 Settembre 2013 14:52 Oggetto: Re: [ARMedslack] A quick primer for the PI Did you dd the image onto the card? What suze of card? Try the installer image at stanleygarvey.com Regards, Stanley Sent from my BlackBerry smartphone from Virgin Media ________________________________ From: Davide Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) To: stanley garvey; dowelld at netscape.net; armedslack at lists.armedslack.org ReplyTo: Davide Subject: Re: [ARMedslack] A quick primer for the PI I can't get it to boot at all. If I turn the PI on I get the PER led solid on but the ACT led does this: first faint on, the bright on for a second or do then it goes off and stays off. I've tried 2 different SD cards supposing that the firs may have had some sort of compatibility issue but the second does the same thing. I downloaded updated boot stuff from here: http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ... but nothing seems to change. Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted I suspect that its not booting because if I take out the SD and mount in on the PC fsck does not detect the filesystem dirty flag that I should have if the thing booted but showed nothing on the TV. ATB David ________________________________ Da: stanley garvey A: "dowelld at netscape.net" ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Gioved? 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 "Davide" wrote: > >>>I got a friend to lend me a PI? for a week ... > >>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>The content in there looks about right: > >>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>Units = sectors of 1 * 512 = 512 bytes >>>Sector size (logical/physical): 512 bytes / 512 bytes >>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>Disk identifier: 0x00007091 > >>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux swap >>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>root at darkstar:/tmp# echo $((32 * 512)) >>>16384 >>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>root at darkstar:/tmp# modprobe vfat >>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>root at darkstar:/tmp# ls /mnt/floppy/ >>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>System.map-raspberrypi-3.2.27*? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>bootcode.bin*?????????????????? fixup_cd.dat* >>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>root at darkstar:/tmp# > > >>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >>Hi David, >Hi Dave ;) > >>The GPU looks for bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in config.txt (to configure the hardware) and loads start.elf (the GPU binary blob). Once it has configured the hardware, it then >loads kernel.img, and feeds it the contents of cmdline.txt. > >But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >Is there something wrong with this image or is loader.bin optional ? > >> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. > >>So you have to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, and cmdline.txt, then if you load a ramdisk image in the cmdline.txt file you need the ramdisk image file. > >> yes > >Is the initrd loading governed by config.txt ? > >> yes > >I see in there ramfsfile=initrd-raspberrypi.img >Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? > >> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. > >When is the HDMI output initiated ? > >>Before the system comes up as the GPU boots the system. > >>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >Hope that helps, >Stanley. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Sep 26 19:23:30 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 26 Sep 2013 20:23:30 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <576813278.20130926192812@spaceguard.pl> References: <8D08850F4FB510B-2234-5E09@webmail-d213.sysops.aol.com> <1380180310.46060.YahooMailNeo@web173102.mail.ir2.yahoo.com> <20130926111549.CB931FC3B57FA@bmail-n01.one.com> <1380199101.5279.YahooMailNeo@web173101.mail.ir2.yahoo.com> <628584630-1380199976-cardhu_decombobulator_blackberry.rim.net-103970031-@b15.c14.bise7.blackberry> <1380205423.18790.YahooMailNeo@web173105.mail.ir2.yahoo.com> <979531866-1380211135-cardhu_decombobulator_blackberry.rim.net-1174902497-@b15.c14.bise7.blackberry> <576813278.20130926192812@spaceguard.pl> Message-ID: <1380223410.87155.YahooMailNeo@web173102.mail.ir2.yahoo.com> Thanks ... I'll have a crack at that tomorrow. Regards David ________________________________ Da: Tomasz Salwach A: "armedslack at lists.armedslack.org" Cc: Davide Inviato: Gioved? 26 Settembre 2013 19:28 Oggetto: Re: [ARMedslack] A quick primer for the PI Davide, I've also had problems installing Slackware on RPi. My board/card did not work with kernel / images they provided. I've suggested Slackware for RPI should use Raspbian kernel - because it is ACTIVELY supported. Try my way https://salwach.pl/rpi_slackware >These images have been tested on a > multitude of boards and have never failed to boot. Recently I've bought 2nd RPi, just switched SD card to new one..and ooops...black screen. Old works, new one not. After download of "new" Raspbian and replacing bootloader I've got it working. RPi is NOT Arduino - it changes too fast. And guys here do not understand that or ignore it. Standard answer: "Works on my computer"....LOL Tom W li?cie z 26 wrze?nia 2013: From: stanley at stanleygarvey.com To: louigi600 at yahoo.it CC: ssc> No nothing obscure needs to be done it should just work. I ssc> checked today at home. These images have been tested on a ssc> multitude of boards and have never failed to boot. ssc> Have you created a swap and ext4 root fs? Donkt know if it will ssc> boot without these being present. ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> -----Original Message----- ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 15:23:43 ssc> To: stanley at stanleygarvey.com; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> Reply-To: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> No I formatted the filesystem myself and copied files into it. ssc> The firs lot of boot loader stuff was gotten out of ssc> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip ssc> , unzipp created loop device with off set on the image first ssc> partition ... mounted it and copied files over. ssc> root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors ssc> Units = sectors of ssc>? 1 * 512 = 512 bytes ssc> Sector size (logical/physical): 512 bytes / 512 bytes ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes ssc> Disk identifier: 0x00007091 ssc> ???????????????????????????? Device Boot????? Start???????? End? Blocks?? Id? System ssc> slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663? 48816??? c? W95 FAT32 (LBA) ssc> slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847? 390592?? 82? Linux ssc>? swap ssc> slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167? 7436160?? 83? Linux ssc> root at darkstar:/tmp# echo $((32 * 512)) ssc> 16384 ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0? ssc> slackwarearm-14.0-8GB-20130623.img ssc> root at darkstar:/tmp# modprobe vfat ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc> root at darkstar:/tmp# ls /mnt/floppy/ ssc> COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* ssc> LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* ssc> System.map-raspberrypi-3.2.27*? ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* ssc> bootcode.bin*?????????????????? fixup_cd.dat* ssc> cmdline.txt*??????????????????? initrd-raspberrypi.img* ssc> root at darkstar:/tmp# ssc> Is there something obscure that need to be done to the dor partition ? ssc> Regards ssc> David ssc> ________________________________ ssc>? Da: "stanley at stanleygarvey.com" ssc> A: Davide ; "dowelld at netscape.net" ssc> ; "armedslack at lists.armedslack.org" ssc> ssc> Inviato: Gioved? 26 Settembre 2013 14:52 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>? ssc> Did you dd the image onto the card? ssc> What suze of card? ssc> Try the installer image at stanleygarvey.com ssc> Regards, ssc> Stanley ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> ________________________________ ssc> From:? Davide ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc> To: stanley garvey; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> ReplyTo:? Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> I can't get it to boot at all. ssc> If I turn the PI on I get the PER led solid on but the ACT led does this: ssc> first faint on, the bright on for a second or do then it goes off and stays off. ssc> I've tried 2 different SD cards supposing that the firs may have ssc> had some sort of compatibility issue but the second does the same thing. ssc> I downloaded updated boot stuff from here: ssc> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ssc> ... but nothing seems to change. ssc> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted ssc> I suspect that its not booting because if I take out the SD and ssc> mount in on the PC fsck does not detect the filesystem dirty flag ssc> that I should have if the thing booted but showed nothing on the TV. ssc> ATB ssc> David ssc> ________________________________ ssc>? Da: stanley garvey ssc> A: "dowelld at netscape.net" ; ssc> "armedslack at lists.armedslack.org" ssc> ; Davide ; ssc> Slackware ARM port ssc> Inviato: Gioved? 26 Settembre 2013 13:15 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>? ssc> On Sep 26, 2013 08:25 "Davide" wrote: >> >>>>I got a friend to lend me a PI? for a week ... >> >>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>The content in there looks about right: >> >>>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >> >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>Units = sectors of ssc>? 1 * 512 = 512 bytes >>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>Disk identifier: 0x00007091 >> >>>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux ssc>? swap >>>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>16384 >>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>>root at darkstar:/tmp# modprobe vfat >>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>>System.map-raspberrypi-3.2.27*? ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>>bootcode.bin*?????????????????? fixup_cd.dat* >>>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>>root at darkstar:/tmp# >> >> >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >> >>>Hi David, >>Hi Dave ;) >> >>>The GPU looks for ssc>? bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in ssc>? config.txt (to configure the hardware) and loads start.elf (the GPU ssc> binary blob). Once it has configured the hardware, it then >loads ssc> kernel.img, and feeds it the contents of cmdline.txt. >> >>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>Is there something wrong with this image or is loader.bin optional ? >> >>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >> >>>So you have ssc>? to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt ssc> file you need the ramdisk image file. >> >>> yes >> >>Is the initrd loading governed by config.txt ? >> >>> yes >> >>I see in there ramfsfile=initrd-raspberrypi.img >>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >> >>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >> >>When is the HDMI output initiated ? >> >>>Before the system ssc>? comes up as the GPU boots the system. >> >>>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>Hope that helps, >>Stanley. >> >> >> >> >> >> >> >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Sep 27 08:10:45 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 27 Sep 2013 09:10:45 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1366445387.20130926194449@spoko.eu.org> References: <1366445387.20130926194449@spoko.eu.org> Message-ID: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> I'm downloading the NOOBS and rasbian images to see if I can use those to boot the PI that has been lent to me. Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a new or an old board ? I'm beginning to think that the whole PI project is scrap: the boards were meant to be 25 or 35 USD respectively fro the A or B model, but the cheapest you can get one in europe is for 50 Euro (that's damm close to 70 USD) ... it's twice the price it was supposed to be !!!! you get one and you may not be able to boot it untill you get the correct images for it downloading stuff from the foundation's' ftp server is really slow ... they must have a PI itself serving files? I'm not even sure I want to complete my tests because I don't think I'm gonna buy one ... but I'm just curious to see how bad it actually is. I'll see if I want to try booting after the estimated 4 and 7 hour estimated download time, that I've hadto restart over again because it got truncated and resume does not seem to work. ATB David ________________________________ Da: Tom A: "armedslack at lists.armedslack.org" Cc: Davide Inviato: Gioved? 26 Settembre 2013 19:44 Oggetto: Re: [ARMedslack] A quick primer for the PI Davide, I've also had problems installing Slackware on RPi. My board/card did not work with kernel / images they provided. I've suggested Slackware for RPI should use Raspbian kernel - because it is ACTIVELY supported. Try my way https://salwach.pl/rpi_slackware >These images have been tested on a > multitude of boards and have never failed to boot. Recently I've bought 2nd RPi, just switched SD card to new one..and ooops...black screen. Old works, new one not. After download of "new" Raspbian and replacing bootloader I've got it working. RPi is NOT Arduino - it changes too fast. And guys here do not understand that or ignore it. Standard answer: "Works on my computer"....LOL Tom W li?cie z 26 wrze?nia 2013: From: stanley at stanleygarvey.com To: louigi600 at yahoo.it CC: ssc> No nothing obscure needs to be done it should just work. I ssc> checked today at home. These images have been tested on a ssc> multitude of boards and have never failed to boot. ssc> Have you created a swap and ext4 root fs? Donkt know if it will ssc> boot without these being present. ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> -----Original Message----- ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 15:23:43 ssc> To: stanley at stanleygarvey.com; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> Reply-To: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> No I formatted the filesystem myself and copied files into it. ssc> The firs lot of boot loader stuff was gotten out of ssc> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip ssc> , unzipp created loop device with off set on the image first ssc> partition ... mounted it and copied files over. ssc> root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors ssc> Units = sectors of ssc>? 1 * 512 = 512 bytes ssc> Sector size (logical/physical): 512 bytes / 512 bytes ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes ssc> Disk identifier: 0x00007091 ssc> ???????????????????????????? Device Boot????? Start???????? End? Blocks?? Id? System ssc> slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663? 48816??? c? W95 FAT32 (LBA) ssc> slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847? 390592?? 82? Linux ssc>? swap ssc> slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167? 7436160?? 83? Linux ssc> root at darkstar:/tmp# echo $((32 * 512)) ssc> 16384 ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0? ssc> slackwarearm-14.0-8GB-20130623.img ssc> root at darkstar:/tmp# modprobe vfat ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc> root at darkstar:/tmp# ls /mnt/floppy/ ssc> COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* ssc> LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* ssc> System.map-raspberrypi-3.2.27*? ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* ssc> bootcode.bin*?????????????????? fixup_cd.dat* ssc> cmdline.txt*??????????????????? initrd-raspberrypi.img* ssc> root at darkstar:/tmp# ssc> Is there something obscure that need to be done to the dor partition ? ssc> Regards ssc> David ssc> ________________________________ ssc>? Da: "stanley at stanleygarvey.com" ssc> A: Davide ; "dowelld at netscape.net" ssc> ; "armedslack at lists.armedslack.org" ssc> ssc> Inviato: Gioved? 26 Settembre 2013 14:52 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>? ssc> Did you dd the image onto the card? ssc> What suze of card? ssc> Try the installer image at stanleygarvey.com ssc> Regards, ssc> Stanley ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> ________________________________ ssc> From:? Davide ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc> To: stanley garvey; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> ReplyTo:? Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> I can't get it to boot at all. ssc> If I turn the PI on I get the PER led solid on but the ACT led does this: ssc> first faint on, the bright on for a second or do then it goes off and stays off. ssc> I've tried 2 different SD cards supposing that the firs may have ssc> had some sort of compatibility issue but the second does the same thing. ssc> I downloaded updated boot stuff from here: ssc> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ssc> ... but nothing seems to change. ssc> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted ssc> I suspect that its not booting because if I take out the SD and ssc> mount in on the PC fsck does not detect the filesystem dirty flag ssc> that I should have if the thing booted but showed nothing on the TV. ssc> ATB ssc> David ssc> ________________________________ ssc>? Da: stanley garvey ssc> A: "dowelld at netscape.net" ; ssc> "armedslack at lists.armedslack.org" ssc> ; Davide ; ssc> Slackware ARM port ssc> Inviato: Gioved? 26 Settembre 2013 13:15 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>? ssc> On Sep 26, 2013 08:25 "Davide" wrote: >> >>>>I got a friend to lend me a PI? for a week ... >> >>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>The content in there looks about right: >> >>>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >> >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>Units = sectors of ssc>? 1 * 512 = 512 bytes >>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>Disk identifier: 0x00007091 >> >>>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux ssc>? swap >>>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>16384 >>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>>root at darkstar:/tmp# modprobe vfat >>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>>System.map-raspberrypi-3.2.27*? ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>>bootcode.bin*?????????????????? fixup_cd.dat* >>>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>>root at darkstar:/tmp# >> >> >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >> >>>Hi David, >>Hi Dave ;) >> >>>The GPU looks for ssc>? bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in ssc>? config.txt (to configure the hardware) and loads start.elf (the GPU ssc> binary blob). Once it has configured the hardware, it then >loads ssc> kernel.img, and feeds it the contents of cmdline.txt. >> >>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>Is there something wrong with this image or is loader.bin optional ? >> >>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >> >>>So you have ssc>? to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt ssc> file you need the ramdisk image file. >> >>> yes >> >>Is the initrd loading governed by config.txt ? >> >>> yes >> >>I see in there ramfsfile=initrd-raspberrypi.img >>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >> >>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >> >>When is the HDMI output initiated ? >> >>>Before the system ssc>? comes up as the GPU boots the system. >> >>>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>Hope that helps, >>Stanley. >> >> >> >> >> >> >> >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomeks at spoko.eu.org Fri Sep 27 08:35:58 2013 From: tomeks at spoko.eu.org (Tom) Date: Fri, 27 Sep 2013 10:35:58 +0200 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: <199484843.20130927103558@spoko.eu.org> > Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a new or an old board ? Mine "new" has E2613RS2V13B1.0 Tom > ________________________________ > Da: Tom > A: "armedslack at lists.armedslack.org" > > Cc: Davide > Inviato: Gioved? 26 Settembre 2013 19:44 > Oggetto: Re: [ARMedslack] A quick primer for the PI > > Davide, I've also had problems installing Slackware on RPi. > My board/card did not work with kernel / images they provided. > I've suggested Slackware for RPI should use Raspbian kernel - because > it is ACTIVELY supported. > Try my way > https://salwach.pl/rpi_slackware >>These images have been tested on a >> multitude of boards and have never failed to boot. > Recently I've bought 2nd RPi, just switched SD card to new > one..and ooops...black screen. Old works, new one not. > After download of "new" Raspbian and replacing bootloader I've got it > working. > RPi is NOT Arduino - it changes too fast. > And guys here do not understand that or ignore it. > Standard answer: "Works on my computer"....LOL > Tom > W li?cie z 26 wrze?nia 2013: > From: stanley at stanleygarvey.com > To: louigi600 at yahoo.it > CC: ssc>> No nothing obscure needs to be done it should just work. I ssc>> checked today at home. These images have been tested on a ssc>> multitude of boards and have never failed to boot. ssc>> Have you created a swap and ext4 root fs? Donkt know if it will ssc>> boot without these being present. ssc>> Sent from my BlackBerry smartphone from Virgin Media ssc>> -----Original Message----- ssc>> From: Davide ssc>> Date: Thu, 26 Sep 2013 15:23:43 ssc>> To: stanley at stanleygarvey.com; ssc>> dowelld at netscape.net; ssc>> armedslack at lists.armedslack.org ssc>> Reply-To: Davide ssc>> Subject: Re: [ARMedslack] A quick primer for the PI ssc>> No I formatted the filesystem myself and copied files into it. ssc>> The firs lot of boot loader stuff was gotten out of ssc>> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip ssc>> , unzipp created loop device with off set on the image first ssc>> partition ... mounted it and copied files over. ssc>> root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img ssc>> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes ssc>> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors ssc>> Units = sectors of ssc>>? 1 * 512 = 512 bytes ssc>> Sector size (logical/physical): 512 bytes / 512 bytes ssc>> I/O size (minimum/optimal): 512 bytes / 512 bytes ssc>> Disk identifier: 0x00007091 ssc>> ???????????????????????????? Device Boot????? Start???????? End? Blocks?? Id? System ssc>> slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663? 48816??? c? W95 FAT32 (LBA) ssc>> slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847? 390592?? 82? Linux ssc>>? swap ssc>> slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167? 7436160?? 83? Linux ssc>> root at darkstar:/tmp# echo $((32 * 512)) ssc>> 16384 ssc>> root at darkstar:/tmp# losetup -o 16384 /dev/loop0? ssc>> slackwarearm-14.0-8GB-20130623.img ssc>> root at darkstar:/tmp# modprobe vfat ssc>> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc>> root at darkstar:/tmp# ls /mnt/floppy/ ssc>> COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* ssc>> LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* ssc>> System.map-raspberrypi-3.2.27*? ssc>>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* ssc>> bootcode.bin*?????????????????? fixup_cd.dat* ssc>> cmdline.txt*??????????????????? initrd-raspberrypi.img* ssc>> root at darkstar:/tmp# ssc>> Is there something obscure that need to be done to the dor partition ? ssc>> Regards ssc>> David ssc>> ________________________________ ssc>>? Da: "stanley at stanleygarvey.com" ssc>> A: Davide ; "dowelld at netscape.net" ssc>> ; "armedslack at lists.armedslack.org" ssc>> ssc>> Inviato: Gioved? 26 Settembre 2013 14:52 ssc>> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>>? ssc>> Did you dd the image onto the card? ssc>> What suze of card? ssc>> Try the installer image at stanleygarvey.com ssc>> Regards, ssc>> Stanley ssc>> Sent from my BlackBerry smartphone from Virgin Media ssc>> ________________________________ ssc>> From:? Davide ssc>> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc>> To: stanley garvey; ssc>> dowelld at netscape.net; ssc>> armedslack at lists.armedslack.org ssc>> ReplyTo:? Davide ssc>> Subject: Re: [ARMedslack] A quick primer for the PI ssc>> I can't get it to boot at all. ssc>> If I turn the PI on I get the PER led solid on but the ACT led does this: ssc>> first faint on, the bright on for a second or do then it goes off and stays off. ssc>> I've tried 2 different SD cards supposing that the firs may have ssc>> had some sort of compatibility issue but the second does the same thing. ssc>> I downloaded updated boot stuff from here: ssc>> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ssc>> ... but nothing seems to change. ssc>> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? ssc>> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted ssc>> I suspect that its not booting because if I take out the SD and ssc>> mount in on the PC fsck does not detect the filesystem dirty flag ssc>> that I should have if the thing booted but showed nothing on the TV. ssc>> ATB ssc>> David ssc>> ________________________________ ssc>>? Da: stanley garvey ssc>> A: "dowelld at netscape.net" ; ssc>> "armedslack at lists.armedslack.org" ssc>> ; Davide ; ssc>> Slackware ARM port ssc>> Inviato: Gioved? 26 Settembre 2013 13:15 ssc>> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>>? ssc>> On Sep 26, 2013 08:25 "Davide" wrote: >>> >>>>>I got a friend to lend me a PI? for a week ... >>> >>>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>>The content in there looks about right: >>> >>>>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >>> >>>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>>Units = sectors of ssc>>? 1 * 512 = 512 bytes >>>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>>Disk identifier: 0x00007091 >>> >>>>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux ssc>>? swap >>>>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>>16384 >>>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>>>root at darkstar:/tmp# modprobe vfat >>>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>>>System.map-raspberrypi-3.2.27*? ssc>>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>>>bootcode.bin*?????????????????? fixup_cd.dat* >>>>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>>>root at darkstar:/tmp# >>> >>> >>>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >>> >>>>Hi David, >>>Hi Dave ;) >>> >>>>The GPU looks for ssc>>? bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in ssc>>? config.txt (to configure the hardware) and loads start.elf (the GPU ssc>> binary blob). Once it has configured the hardware, it then >loads ssc>> kernel.img, and feeds it the contents of cmdline.txt. >>> >>>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>>Is there something wrong with this image or is loader.bin optional ? >>> >>>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >>> >>>>So you have ssc>>? to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, ssc>> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt ssc>> file you need the ramdisk image file. >>> >>>> yes >>> >>>Is the initrd loading governed by config.txt ? >>> >>>> yes >>> >>>I see in there ramfsfile=initrd-raspberrypi.img >>>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >>> >>>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >>> >>>When is the HDMI output initiated ? >>> >>>>Before the system ssc>>? comes up as the GPU boots the system. >>> >>>>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>>Hope that helps, >>>Stanley. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- Pozdrowienia, Tom From dowelld at netscape.net Fri Sep 27 08:41:14 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Fri, 27 Sep 2013 04:41:14 -0400 (EDT) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: <8D089747568A4B5-9D4-14338@webmail-m288.sysops.aol.com> I can honestly say I'm quite surprised by some of what is being revealed by some of these emails. I take blank SD cards prep them as per the instructions in that txt file I put up with the files I use, and boot them on different PI boards over and over again. I have days when I run 10-15 installs a day on different Pi boards, and different SD cards (from 2GB to 32GB). All without problems. The same files were used to install and create a two images for distcc which I run across 6+ Pi boards. I've only encountered two problems with booting, the first was the hdmi_safe one, and the second was the base firmwware being old and not supporting the 512M version B boards, hence me updating the firmware and creating the files I put up. Did you try my files? Take an SD card. Partition it to have one (type 6) 50M fat partition on it. mkfs.vfat it to get a fat filesystem on it. copy the files to it. put it in a pi, connect the power, and it should boot, to the standard installer. I have days when I do that multiple times a day, on different SD cards, using different Pi boards (all model B some 256M some 512M versions) I deliberately do it across multiple different boards, because I have to know it will work on both. Thanks. Dave -----Original Message----- From: Davide To: Tom ; armedslack Sent: Fri, Sep 27, 2013 9:10 am Subject: Re: [ARMedslack] A quick primer for the PI I'm downloading the NOOBS and rasbian images to see if I can use those to boot the PI that has been lent to me. Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a new or an old board ? I'm beginning to think that the whole PI project is scrap: the boards were meant to be 25 or 35 USD respectively fro the A or B model, but the cheapest you can get one in europe is for 50 Euro (that's damm close to 70 USD) ... it's twice the price it was supposed to be !!!! you get one and you may not be able to boot it untill you get the correct images for it downloading stuff from the foundation's' ftp server is really slow ... they must have a PI itself serving files I'm not even sure I want to complete my tests because I don't think I'm gonna buy one ... but I'm just curious to see how bad it actually is. I'll see if I want to try booting after the estimated 4 and 7 hour estimated download time, that I've hadto restart over again because it got truncated and resume does not seem to work. ATB David Da: Tom A: "armedslack at lists.armedslack.org" Cc: Davide Inviato: Gioved? 26 Settembre 2013 19:44 Oggetto: Re: [ARMedslack] A quick primer for the PI Davide, I've also had problems installing Slackware on RPi. My board/card did not work with kernel / images they provided. I've suggested Slackware for RPI should use Raspbian kernel - because it is ACTIVELY supported. Try my way https://salwach.pl/rpi_slackware >These images have been tested on a > multitude of boards and have never failed to boot. Recently I've bought 2nd RPi, just switched SD card to new one..and ooops...black screen. Old works, new one not. After download of "new" Raspbian and replacing bootloader I've got it working. RPi is NOT Arduino - it changes too fast. And guys here do not understand that or ignore it. Standard answer: "Works on my computer"....LOL Tom W li?cie z 26 wrze?nia 2013: From: stanley at stanleygarvey.com To: louigi600 at yahoo.it CC: ssc> No nothing obscure needs to be done it should just work. I ssc> checked today at home. These images have been tested on a ssc> multitude of boards and have never failed to boot. ssc> Have you created a swap and ext4 root fs? Donkt know if it will ssc> boot without these being present. ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> -----Original Message----- ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 15:23:43 ssc> To: stanley at stanleygarvey.com; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> Reply-To: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> No I formatted the filesystem myself and copied files into it. ssc> The firs lot of boot loader stuff was gotten out of ssc> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip ssc> , unzipp created loop device with off set on the image first ssc> partition ... mounted it and copied files over. ssc> root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors ssc> Units = sectors of ssc> 1 * 512 = 512 bytes ssc> Sector size (logical/physical): 512 bytes / 512 bytes ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes ssc> Disk identifier: 0x00007091 ssc> Device Boot Start End Blocks Id System ssc> slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) ssc> slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux ssc> swap ssc> slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux ssc> root at darkstar:/tmp# echo $((32 * 512)) ssc> 16384 ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0 ssc> slackwarearm-14.0-8GB-20130623.img ssc> root at darkstar:/tmp# modprobe vfat ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc> root at darkstar:/tmp# ls /mnt/floppy/ ssc> COPYING.linux* config-raspberrypi-3.2.27* start.elf* ssc> LICENCE.broadcom* config.txt* start_cd.elf* ssc> System.map-raspberrypi-3.2.27* ssc> fixup.dat* zImage-raspberrypi-3.2.27* ssc> bootcode.bin* fixup_cd.dat* ssc> cmdline.txt* initrd-raspberrypi.img* ssc> root at darkstar:/tmp# ssc> Is there something obscure that need to be done to the dor partition ? ssc> Regards ssc> David ssc> ________________________________ ssc> Da: "stanley at stanleygarvey.com" ssc> A: Davide ; "dowelld at netscape.net" ssc> ; "armedslack at lists.armedslack.org" ssc> ssc> Inviato: Gioved? 26 Settembre 2013 14:52 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc> ssc> Did you dd the image onto the card? ssc> What suze of card? ssc> Try the installer image at stanleygarvey.com ssc> Regards, ssc> Stanley ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> ________________________________ ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc> To: stanley garvey; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> ReplyTo: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> I can't get it to boot at all. ssc> If I turn the PI on I get the PER led solid on but the ACT led does this: ssc> first faint on, the bright on for a second or do then it goes off and stays off. ssc> I've tried 2 different SD cards supposing that the firs may have ssc> had some sort of compatibility issue but the second does the same thing. ssc> I downloaded updated boot stuff from here: ssc> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ssc> ... but nothing seems to change. ssc> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted ssc> I suspect that its not booting because if I take out the SD and ssc> mount in on the PC fsck does not detect the filesystem dirty flag ssc> that I should have if the thing booted but showed nothing on the TV. ssc> ATB ssc> David ssc> ________________________________ ssc> Da: stanley garvey ssc> A: "dowelld at netscape.net" ; ssc> "armedslack at lists.armedslack.org" ssc> ; Davide ; ssc> Slackware ARM port ssc> Inviato: Gioved? 26 Settembre 2013 13:15 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc> ssc> On Sep 26, 2013 08:25 "Davide" wrote: >> >>>>I got a friend to lend me a PI for a week ... >> >>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>what does the GPU look for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>The content in there looks about right: >> >>>>root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img >> >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>Units = sectors of ssc> 1 * 512 = 512 bytes >>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>Disk identifier: 0x00007091 >> >>>> Device Boot Start End Blocks Id System >>>>slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 (LBA) >>>>slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux ssc> swap >>>>slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 Linux >>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>16384 >>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img >>>>root at darkstar:/tmp# modprobe vfat >>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>COPYING.linux* config-raspberrypi-3.2.27* start.elf* >>>>LICENCE.broadcom* config.txt* start_cd.elf* >>>>System.map-raspberrypi-3.2.27* ssc> fixup.dat* zImage-raspberrypi-3.2.27* >>>>bootcode.bin* fixup_cd.dat* >>>>cmdline.txt* initrd-raspberrypi.img* >>>root at darkstar:/tmp# >> >> >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >> >>>Hi David, >>Hi Dave ;) >> >>>The GPU looks for ssc> bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in ssc> config.txt (to configure the hardware) and loads start.elf (the GPU ssc> binary blob). Once it has configured the hardware, it then >loads ssc> kernel.img, and feeds it the contents of cmdline.txt. >> >>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>Is there something wrong with this image or is loader.bin optional ? >> >>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >> >>>So you have ssc> to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt ssc> file you need the ramdisk image file. >> >>> yes >> >>Is the initrd loading governed by config.txt ? >> >>> yes >> >>I see in there ramfsfile=initrd-raspberrypi.img >>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >> >>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >> >>When is the HDMI output initiated ? >> >>>Before the system ssc> comes up as the GPU boots the system. >> >>> if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>Hope that helps, >>Stanley. >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Sep 27 08:46:23 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 27 Sep 2013 09:46:23 +0100 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: <20130927084623.7A63D351F7A43@bmail06.one.com> David I have put up a new boot layout tested here this morning at ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ Still no loader.bin, files taken from weezy 2013-09-10 ( boot files are float agnostic). hope that helps. Stanley On Sep 27, 2013 09:10 "Davide" wrote: > I'm downloading the NOOBS and rasbian images to see if I can use those > to boot the PI that has been lent to me. > > Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a > new or an old board ? > > > > > I'm beginning to think that the whole PI project is scrap: > > the boards were meant to be 25 or 35 USD respectively fro the A or B > model, but the cheapest you can get one in europe is for 50 Euro > (that's damm close to 70 USD) ... it's twice the price it was supposed > to be !!!! > > you get one and you may not be able to boot it untill you get the > correct images for it > > downloading stuff from the foundation's' ftp server is really slow ... > they must have a PI itself serving files > > > > > I'm not even sure I want to complete my tests because I don't think > I'm gonna buy one ... but I'm just curious to see how bad it actually > is. > > I'll see if I want to try booting after the estimated 4 and 7 hour > estimated download time, that I've hadto restart over again because it > got truncated and resume does not seem to work. > > > > > ATB > > David > > > > > Da: Tom > A: "armedslack at lists.armedslack.org" > Cc: Davide > Inviato: Gioved? 26 Settembre 2013 19:44 > Oggetto: Re: [ARMedslack] A quick primer for the PI > > > Davide, I've also had problems installing Slackware on RPi. > My board/card did not work with kernel / images they provided. > > I've suggested Slackware for RPI should use Raspbian kernel - because > it is ACTIVELY supported. > > Try my way > > > /run/media/stanley/B052-F700/ > >These images have been tested on a > > multitude of boards and have never failed to boot. > > Recently I've bought 2nd RPi, just switched SD card to new > one..and ooops...black screen. Old works, new one not. > After download of "new" Raspbian and replacing bootloader I've got it > working. > > RPi is NOT Arduino - it changes too fast. > /run/media/stanley/B052-F700/ > And guys here do not understand that or ignore it. > > Standard answer: "Works on my computer"....LOL > > > Tom > > W li?cie z 26 wrze?nia 2013: > From: > To: > CC: > /run/media/stanley/B052-F700/ > ssc> No nothing obscure needs to be done it should just work. I > ssc> checked today at home. These images have been tested on a > ssc> multitude of boards and have never failed to boot. > ssc> Have you created a swap and ext4 root fs? Donkt know if it will > ssc> boot without these being present. > ssc> Sent from my BlackBerry smartphone from Virgin Media > > ssc> -----Original Message----- > ssc> From: Davide <> > ssc> Date: Thu, 26 Sep 2013 15:23:43 > ssc> To: <>; > ssc> <>; > ssc> > <> > ssc> Reply-To: Davide <> > ssc> Subject: Re: [ARMedslack] A quick primer for the PI > > ssc> No I formatted the filesystem myself and copied files into it. > > ssc> The firs lot of boot loader stuff was gotten out of > ssc> > 623.zip> > ssc> , unzipp created loop device with off set on the image first > ssc> partition ... mounted it and copied files over. > > > ssc> :/tmp# fdisk -l > slackwarearm-14.0-8GB-20130623.img > > ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 > bytes > ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors > ssc> Units = sectors of > ssc> 1 * 512 = 512 bytes > ssc> Sector size (logical/physical): 512 bytes / 512 bytes > ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes > ssc> Disk identifier: 0x00007091 > > ssc> Device Boot Start End Blocks Id System > ssc> slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 > (LBA) > ssc> slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux > ssc> swap > ssc> slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 > Linux > ssc> :/tmp# echo $((32 * 512)) > ssc> 16384 > ssc> :/tmp# losetup -o 16384 /dev/loop0 > ssc> slackwarearm-14.0-8GB-20130623.img > ssc> :/tmp# modprobe vfat > ssc> :/tmp# mount /dev/loop0 /mnt/floppy/ > ssc> :/tmp# ls /mnt/floppy/ > ssc> COPYING.linux* config-raspberrypi-3.2.27* start.elf* > ssc> LICENCE.broadcom* config.txt* start_cd.elf* > ssc> System.map-raspberrypi-3.2.27* > ssc> fixup.dat* zImage-raspberrypi-3.2.27* > ssc> bootcode.bin* fixup_cd.dat* > ssc> cmdline.txt* initrd-raspberrypi.img* > ssc> :/tmp# > > > ssc> Is there something obscure that need to be done to the dor > partition ? > > ssc> Regards > ssc> David > > > ssc> ________________________________ > ssc> Da: "" <> > ssc> A: Davide <>; "" > ssc> <>; "" > ssc> <> > ssc> Inviato: Gioved? 26 Settembre 2013 14:52 > ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI > ssc> > > > ssc> Did you dd the image onto the card? > ssc> What suze of card? > ssc> Try the installer image at stanleygarvey.com > ssc> Regards, > ssc> Stanley > ssc> Sent from my BlackBerry smartphone from Virgin Media > ssc> ________________________________ > > ssc> From: Davide <> > ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) > ssc> To: stanley garvey<>; > ssc> <>; > ssc> > <> > ssc> ReplyTo: Davide <> > ssc> Subject: Re: [ARMedslack] A quick primer for the PI > > ssc> I can't get it to boot at all. > ssc> If I turn the PI on I get the PER led solid on but the ACT led > does this: > ssc> first faint on, the bright on for a second or do then it goes off > and stays off. > > ssc> I've tried 2 different SD cards supposing that the firs may have > ssc> had some sort of compatibility issue but the second does the same > thing. > ssc> I downloaded updated boot stuff from here: > ssc> > -1_dbs.tgz> > ssc> ... but nothing seems to change. > ssc> Is the PI finiky on where the dos partition should begin ? or on > the formatting of it ? > ssc> mine starts at sector 2048 (1Mb from the beginning of the device) > and is fat32 formatted > > ssc> I suspect that its not booting because if I take out the SD and > ssc> mount in on the PC fsck does not detect the filesystem dirty flag > ssc> that I should have if the thing booted but showed nothing on the > TV. > > ssc> ATB > ssc> David > > > > ssc> ________________________________ > ssc> Da: stanley garvey <> > ssc> A: "" <>; > ssc> "" > ssc> <>; Davide > <>; > ssc> Slackware ARM port <> > ssc> Inviato: Gioved? 26 Settembre 2013 13:15 > ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI > ssc> > > > > > > ssc> On Sep 26, 2013 08:25 "Davide" <> wrote: > > >> > >>>>I got a friend to lend me a PI for a week ... > >> > >>>>I had a quick look at the community links for slackware on the PI > >>>>but none really tell me what i want to know: > >>>>what does the GPU look for in the SD ? (as fas as I know it's the > >>>>GPU that loads stuff from SD into memory and then passes control > >>>>to it) > >>>>does it look for a second stage boot loader like a uboot image or > >>>>does it load kernel and initrd ? (bootcode.bin) > >>>>I'm supposing that the first partition (the dos one) is where this > >>>>stuff should be put ? > >>>>The content in there looks about right: > >> > >>>>:/tmp# fdisk -l > >>>>slackwarearm-14.0-8GB-20130623.img > >> > >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes > >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors > >>>>Units = sectors of > ssc> 1 * 512 = 512 bytes > >>>>Sector size (logical/physical): 512 bytes / 512 bytes > >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes > >>>>Disk identifier: 0x00007091 > >> > >>>> Device Boot Start End Blocks Id System > >>>>slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c W95 FAT32 > >>>>(LBA) > >>>>slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 82 Linux > ssc> swap > >>>>slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 83 > >>>>Linux > >>>>:/tmp# echo $((32 * 512)) > >>>>16384 > >>>>:/tmp# losetup -o 16384 /dev/loop0 > >>>>slackwarearm-14.0-8GB-20130623.img > >>>>:/tmp# modprobe vfat > >>>>:/tmp# mount /dev/loop0 /mnt/floppy/ > >>>>:/tmp# ls /mnt/floppy/ > >>>>COPYING.linux* config-raspberrypi-3.2.27* start.elf* > >>>>LICENCE.broadcom* config.txt* start_cd.elf* > >>>>System.map-raspberrypi-3.2.27* > ssc> fixup.dat* zImage-raspberrypi-3.2.27* > >>>>bootcode.bin* fixup_cd.dat* > >>>>cmdline.txt* initrd-raspberrypi.img* > >>>:/tmp# > >> > >> > >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD > >>>>:) > >> > >>>Hi David, > >>Hi Dave ;) > >> > >>>The GPU looks for > ssc> bootcode.bin, which looks for and loads loader.bin. Loader.bin > reads in > ssc> config.txt (to configure the hardware) and loads start.elf (the > GPU > ssc> binary blob). Once it has configured the hardware, it then >loads > ssc> kernel.img, and feeds it the contents of cmdline.txt. > >> > >>But on the readymade image from > >>there is no > >>loader.bin in the dos partition ! > >>Is there something wrong with this image or is loader.bin optional ? > >> > >>> Hi Davide, ther is nothing wrong with the image, I use it at home, > >>> it could be that loader bin is a new addition to the Fat32 boot > >>> partitionfor Debian variants. the boot layout I use has not > >>> changed since last Christmas. > >> > >>>So you have > ssc> to have bootcode.bin, loader.bin, config.txt, start.elf, > kernel.img, > ssc> and cmdline.txt, then if you load a ramdisk image in the > cmdline.txt > ssc> file you need the ramdisk image file. > >> > >>> yes > >> > >>Is the initrd loading governed by config.txt ? > >> > >>> yes > >> > >>I see in there ramfsfile=initrd-raspberrypi.img > >>Can I change that manualy with vi and load a different initrd ? or > >>comment it out to not load an initrd at all ? > >> > >>> Yes you can edit the file with vi and load a different initrd. It > >>> is commented out in my config.txt as it is not required to boot a > >>> running system. initrd-raspberrypi.img is the installer, It has > >>> been left there so you can reinstall if you wish, it is a > >>> versatile-initrd that has been modified with a modified version of > >>> the mk-tegra.sh. > >> > >>When is the HDMI output initiated ? > >> > >>>Before the system > ssc> comes up as the GPU boots the system. > >> > >>> if you ate looking for a mini root try the installer image, it is > >>> 1GB and is the standard slackwarearm installer so has busybox and > >>> other stuff. you won't be able to install a full system on 1GB the > >>> 3rd partition is a stub and should be deleted and recreated to use > >>> the remaining space on whatever size card you have before stating > >>> 'setup'. you may be able to get a base slackwarearm systm (a)(ap) > >>> series on a 4GB card. > >>Hope that helps, > >>Stanley. > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Sep 27 08:51:45 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 27 Sep 2013 09:51:45 +0100 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <199484843.20130927103558@spoko.eu.org> References: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> <199484843.20130927103558@spoko.eu.org> Message-ID: <20130927085145.DF062BECD435F@bmail04.one.com> On Sep 27, 2013 09:35 "Tom" wrote: > > Looking on the underside there is a sticker: E1213RS2V13B1.0 is this > > a new or an old board ? > > Mine "new" has E2613RS2V13B1.0 > > > >HI Tom, I was not aware the BOM for raspberry pi had changed? I will > >up date my files accordingly. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomeks at spoko.eu.org Fri Sep 27 09:18:08 2013 From: tomeks at spoko.eu.org (Tom) Date: Fri, 27 Sep 2013 11:18:08 +0200 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <20130927085145.DF062BECD435F@bmail04.one.com> References: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> <199484843.20130927103558@spoko.eu.org> <20130927085145.DF062BECD435F@bmail04.one.com> Message-ID: <2610359261.20130927111808@spoko.eu.org> There is some mystery in it... I've two boards. Both with /proc/cpuinfo Revision: 000d, And new one didn't start with SD card just pulled out from previous one...after replacing "old" (2013-02-09) Raspbian bootcode/start_elf/kernel with latest (2013-06-19) both boards run. Physically the differ in CPU - in fact RAM - markings, RAM is from different manufacturer. Tom W li?cie z 27 wrze?nia 2013: From: stanley at stanleygarvey.com To: armedslack at lists.armedslack.org CC: sg> On Sep 27, 2013 09:35 "Tom" wrote: >> > Looking on the underside there is a sticker: E1213RS2V13B1.0 is this >> > a new or an old board ? >> >> Mine "new" has E2613RS2V13B1.0 >> >> >> >HI Tom, I was not aware the BOM for raspberry pi had changed? I will >> >up date my files accordingly. >> From stanley at stanleygarvey.com Fri Sep 27 10:04:31 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 27 Sep 2013 11:04:31 +0100 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <2610359261.20130927111808@spoko.eu.org> References: <20130927085145.DF062BECD435F@bmail04.one.com> <2610359261.20130927111808@spoko.eu.org> Message-ID: <20130927100431.A364E9995BE5E@bmail06.one.com> On Sep 27, 2013 10:18 "Tom" wrote: > There is some mystery in it... > I've two boards. > Both with /proc/cpuinfo Revision: 000d, > > And new one didn't start with SD card just pulled out from previous > one...after replacing "old" (2013-02-09) Raspbian > bootcode/start_elf/kernel with > latest (2013-06-19) both boards run. > > Physically the differ in CPU - in fact RAM - markings, RAM is from > different manufacturer. > > Tom > ____________________________________________________ > Thanks Tom, > Would you be prepared to test one of my images on your new pi to see > if they boot? Either the 8GB or the installer with the old boot > layout? the new firmware I tried this morning is causing the pi to > reboot on 'shutdown -h now' . This is undesirable. > Regards, > Stanley. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.lapointe at gmail.com Fri Sep 27 10:40:13 2013 From: richard.lapointe at gmail.com (Richard Lapointe) Date: Fri, 27 Sep 2013 06:40:13 -0400 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: <5245608D.2040503@laprjns.com> Geez...maybe its not the rpi that's the problem. Try this http://rpi.fatdog.eu/ Works on my $35 rpi Rich Lapointe On 09/27/2013 04:10 AM, Davide wrote: > I'm downloading the NOOBS and rasbian images to see if I can use those > to boot the PI that has been lent to me. > Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a > new or an old board ? > > I'm beginning to think that the whole PI project is scrap: > the boards were meant to be 25 or 35 USD respectively fro the A or B > model, but the cheapest you can get one in europe is for 50 Euro > (that's damm close to 70 USD) ... it's twice the price it was supposed > to be !!!! > you get one and you may not be able to boot it untill you get the > correct images for it > downloading stuff from the foundation's' ftp server is really slow ... > they must have a PI itself serving files > > I'm not even sure I want to complete my tests because I don't think > I'm gonna buy one ... but I'm just curious to see how bad it actually is. > I'll see if I want to try booting after the estimated 4 and 7 hour > estimated download time, that I've hadto restart over again because it > got truncated and resume does not seem to work. > > ATB > David > > ------------------------------------------------------------------------ > *Da:* Tom > *A:* "armedslack at lists.armedslack.org" > *Cc:* Davide > *Inviato:* Gioved? 26 Settembre 2013 19:44 > *Oggetto:* Re: [ARMedslack] A quick primer for the PI > > Davide, I've also had problems installing Slackware on RPi. > My board/card did not work with kernel / images they provided. > > I've suggested Slackware for RPI should use Raspbian kernel - because > it is ACTIVELY supported. > > Try my way > > https://salwach.pl/rpi_slackware > > >These images have been tested on a > > multitude of boards and have never failed to boot. > > Recently I've bought 2nd RPi, just switched SD card to new > one..and ooops...black screen. Old works, new one not. > After download of "new" Raspbian and replacing bootloader I've got it > working. > > RPi is NOT Arduino - it changes too fast. > > And guys here do not understand that or ignore it. > > Standard answer: "Works on my computer"....LOL > > > Tom > > W lis'cie z 26 wrzes'nia 2013: > From: stanley at stanleygarvey.com > To: louigi600 at yahoo.it > CC: > > ssc> No nothing obscure needs to be done it should just work. I > ssc> checked today at home. These images have been tested on a > ssc> multitude of boards and have never failed to boot. > ssc> Have you created a swap and ext4 root fs? Donkt know if it will > ssc> boot without these being present. > ssc> Sent from my BlackBerry smartphone from Virgin Media > > ssc> -----Original Message----- > ssc> From: Davide > > ssc> Date: Thu, 26 Sep 2013 15:23:43 > ssc> To: stanley at stanleygarvey.com > >; > ssc> dowelld at netscape.net > >; > ssc> armedslack at lists.armedslack.org > > > ssc> Reply-To: Davide > > ssc> Subject: Re: [ARMedslack] A quick primer for the PI > > ssc> No I formatted the filesystem myself and copied files into it. > > ssc> The firs lot of boot loader stuff was gotten out of > ssc> > http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip > ssc> , unzipp created loop device with off set on the image first > ssc> partition ... mounted it and copied files over. > > > ssc> root at darkstar :/tmp# fdisk -l > slackwarearm-14.0-8GB-20130623.img > > ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes > ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors > ssc> Units = sectors of > ssc> 1 * 512 = 512 bytes > ssc> Sector size (logical/physical): 512 bytes / 512 bytes > ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes > ssc> Disk identifier: 0x00007091 > > ssc> Device Boot Start End > Blocks Id System > ssc> slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c > W95 FAT32 (LBA) > ssc> slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 > 82 Linux > ssc> swap > ssc> slackwarearm-14.0-8GB-20130623.img3 878848 15751167 7436160 > 83 Linux > ssc> root at darkstar :/tmp# echo $((32 * 512)) > ssc> 16384 > ssc> root at darkstar :/tmp# losetup -o 16384 > /dev/loop0 > ssc> slackwarearm-14.0-8GB-20130623.img > ssc> root at darkstar :/tmp# modprobe vfat > ssc> root at darkstar :/tmp# mount /dev/loop0 > /mnt/floppy/ > ssc> root at darkstar :/tmp# ls /mnt/floppy/ > ssc> COPYING.linux* config-raspberrypi-3.2.27* start.elf* > ssc> LICENCE.broadcom* config.txt* start_cd.elf* > ssc> System.map-raspberrypi-3.2.27* > ssc> fixup.dat* zImage-raspberrypi-3.2.27* > ssc> bootcode.bin* fixup_cd.dat* > ssc> cmdline.txt* initrd-raspberrypi.img* > ssc> root at darkstar :/tmp# > > > ssc> Is there something obscure that need to be done to the dor > partition ? > > ssc> Regards > ssc> David > > > ssc> ________________________________ > ssc> Da: "stanley at stanleygarvey.com > " > > ssc> A: Davide >; > "dowelld at netscape.net " > ssc> >; > "armedslack at lists.armedslack.org " > ssc> > > ssc> Inviato: Gioved? 26 Settembre 2013 14:52 > ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI > ssc> > > > ssc> Did you dd the image onto the card? > ssc> What suze of card? > ssc> Try the installer image at stanleygarvey.com > ssc> Regards, > ssc> Stanley > ssc> Sent from my BlackBerry smartphone from Virgin Media > ssc> ________________________________ > > ssc> From: Davide > > ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) > ssc> To: stanley garvey >; > ssc> dowelld at netscape.net > >; > ssc> armedslack at lists.armedslack.org > > > ssc> ReplyTo: Davide > > ssc> Subject: Re: [ARMedslack] A quick primer for the PI > > ssc> I can't get it to boot at all. > ssc> If I turn the PI on I get the PER led solid on but the ACT led > does this: > ssc> first faint on, the bright on for a second or do then it goes off > and stays off. > > ssc> I've tried 2 different SD cards supposing that the firs may have > ssc> had some sort of compatibility issue but the second does the same > thing. > ssc> I downloaded updated boot stuff from here: > ssc> > http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz > ssc> ... but nothing seems to change. > ssc> Is the PI finiky on where the dos partition should begin ? or on > the formatting of it ? > ssc> mine starts at sector 2048 (1Mb from the beginning of the device) > and is fat32 formatted > > ssc> I suspect that its not booting because if I take out the SD and > ssc> mount in on the PC fsck does not detect the filesystem dirty flag > ssc> that I should have if the thing booted but showed nothing on the TV. > > ssc> ATB > ssc> David > > > > ssc> ________________________________ > ssc> Da: stanley garvey > > ssc> A: "dowelld at netscape.net " > >; > ssc> "armedslack at lists.armedslack.org > " > ssc> >; Davide >; > ssc> Slackware ARM port > > ssc> Inviato: Gioved? 26 Settembre 2013 13:15 > ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI > ssc> > > > > > > ssc> On Sep 26, 2013 08:25 "Davide" > wrote: > > >> > >>>>I got a friend to lend me a PI for a week ... > >> > >>>>I had a quick look at the community links for slackware on the PI > but none really tell me what i want to know: > >>>>what does the GPU look for in the SD ? (as fas as I know it's > the GPU that loads stuff from SD into memory and then passes control > to it) > >>>>does it look for a second stage boot loader like a uboot image or > does it load kernel and initrd ? (bootcode.bin) > >>>>I'm supposing that the first partition (the dos one) is where this > stuff should be put ? > >>>>The content in there looks about right: > >> > >>>>root at darkstar :/tmp# fdisk -l > slackwarearm-14.0-8GB-20130623.img > >> > >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes > >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors > >>>>Units = sectors of > ssc> 1 * 512 = 512 bytes > >>>>Sector size (logical/physical): 512 bytes / 512 bytes > >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes > >>>>Disk identifier: 0x00007091 > >> > >>>> Device Boot Start > End Blocks Id System > >>>>slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 > c W95 FAT32 (LBA) > >>>>slackwarearm-14.0-8GB-20130623.img2 97664 878847 > 390592 82 Linux > ssc> swap > >>>>slackwarearm-14.0-8GB-20130623.img3 878848 15751167 > 7436160 83 Linux > >>>>root at darkstar :/tmp# echo $((32 * 512)) > >>>>16384 > >>>>root at darkstar :/tmp# losetup -o 16384 > /dev/loop0 slackwarearm-14.0-8GB-20130623.img > >>>>root at darkstar :/tmp# modprobe vfat > >>>>root at darkstar :/tmp# mount /dev/loop0 > /mnt/floppy/ > >>>>root at darkstar :/tmp# ls /mnt/floppy/ > >>>>COPYING.linux* config-raspberrypi-3.2.27* start.elf* > >>>>LICENCE.broadcom* config.txt* start_cd.elf* > >>>>System.map-raspberrypi-3.2.27* > ssc> fixup.dat* zImage-raspberrypi-3.2.27* > >>>>bootcode.bin* fixup_cd.dat* > >>>>cmdline.txt* initrd-raspberrypi.img* > >>>root at darkstar :/tmp# > >> > >> > >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) > >> > >>>Hi David, > >>Hi Dave ;) > >> > >>>The GPU looks for > ssc> bootcode.bin, which looks for and loads loader.bin. Loader.bin > reads in > ssc> config.txt (to configure the hardware) and loads start.elf (the GPU > ssc> binary blob). Once it has configured the hardware, it then >loads > ssc> kernel.img, and feeds it the contents of cmdline.txt. > >> > >>But on the readymade image from > http://stanleygarvey.com/slackwarearm_rpi/index.php there is no > loader.bin in the dos partition ! > >>Is there something wrong with this image or is loader.bin optional ? > >> > >>> Hi Davide, ther is nothing wrong with the image, I use it at home, > it could be that loader bin is a new addition to the Fat32 boot > partitionfor Debian variants. the boot layout I use has not changed > since last Christmas. > >> > >>>So you have > ssc> to have bootcode.bin, loader.bin, config.txt, start.elf, > kernel.img, > ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt > ssc> file you need the ramdisk image file. > >> > >>> yes > >> > >>Is the initrd loading governed by config.txt ? > >> > >>> yes > >> > >>I see in there ramfsfile=initrd-raspberrypi.img > >>Can I change that manualy with vi and load a different initrd ? or > comment it out to not load an initrd at all ? > >> > >>> Yes you can edit the file with vi and load a different initrd. It > is commented out in my config.txt as it is not required to boot a > running system. initrd-raspberrypi.img is the installer, It has been > left there so you can reinstall if you wish, it is a versatile-initrd > that has been modified with a modified version of the mk-tegra.sh. > >> > >>When is the HDMI output initiated ? > >> > >>>Before the system > ssc> comes up as the GPU boots the system. > >> > >>> if you ate looking for a mini root try the installer image, it is > 1GB and is the standard slackwarearm installer so has busybox and > other stuff. you won't be able to install a full system on 1GB the 3rd > partition is a stub and should be deleted and recreated to use the > remaining space on whatever size card you have before stating 'setup'. > you may be able to get a base slackwarearm systm (a)(ap) series on a > 4GB card. > >>Hope that helps, > >>Stanley. > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomeks at spoko.eu.org Fri Sep 27 10:48:31 2013 From: tomeks at spoko.eu.org (Tom) Date: Fri, 27 Sep 2013 12:48:31 +0200 Subject: [ARMedslack] A quick primer for the PI Message-ID: <1412438041.20130927124831@spoko.eu.org> >> Thanks Tom, >> Would you be prepared to test one of my images on your new pi to see >> if they boot? Either the 8GB or the installer with the old boot >> layout? the new firmware I tried this morning is causing the pi to >> reboot on 'shutdown -h now' . This is undesirable. OK, I can test it, if not in next 3h it would be on Monday. Regards Tom From tomeks at spoko.eu.org Fri Sep 27 11:16:40 2013 From: tomeks at spoko.eu.org (Tom) Date: Fri, 27 Sep 2013 13:16:40 +0200 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <20130927100431.A364E9995BE5E@bmail06.one.com> References: <20130927085145.DF062BECD435F@bmail04.one.com> <2610359261.20130927111808@spoko.eu.org> <20130927100431.A364E9995BE5E@bmail06.one.com> Message-ID: <916470782.20130927131640@spoko.eu.org> I do not need images to test, just boot files and kernel. With these: ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ Both of mine RPis hang at "colorful" screen. Set of files that work for me: https://salwach.pl/img/RPi/slack14_tom.zip Tom >> Would you be prepared to test one of my images on your new pi to see >> if they boot? Either the 8GB or the installer with the old boot >> layout? the new firmware I tried this morning is causing the pi to >> reboot on 'shutdown -h now' . This is undesirable. From gregg.drwho8 at gmail.com Fri Sep 27 14:08:17 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Fri, 27 Sep 2013 10:08:17 -0400 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> Message-ID: Hello! I've gotten Slackware (on ARM) to work on my Pi. However the big problem was in getting the installer based one to actually install the operating system. Then I had some issues getting the other images to work properly on my device. In this case it was one of setting the proper boot settings and not drop back into install mode. In any case I still want to go ahead and try again at a future point in time. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." On Fri, Sep 27, 2013 at 4:10 AM, Davide wrote: > I'm downloading the NOOBS and rasbian images to see if I can use those to > boot the PI that has been lent to me. > Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a new > or an old board ? > > I'm beginning to think that the whole PI project is scrap: > the boards were meant to be 25 or 35 USD respectively fro the A or B model, > but the cheapest you can get one in europe is for 50 Euro (that's damm close > to 70 USD) ... it's twice the price it was supposed to be !!!! > you get one and you may not be able to boot it untill you get the correct > images for it > downloading stuff from the foundation's' ftp server is really slow ... they > must have a PI itself serving files > > I'm not even sure I want to complete my tests because I don't think I'm > gonna buy one ... but I'm just curious to see how bad it actually is. > I'll see if I want to try booting after the estimated 4 and 7 hour estimated > download time, that I've hadto restart over again because it got truncated > and resume does not seem to work. > > ATB > David > > ________________________________ > Da: Tom > > A: "armedslack at lists.armedslack.org" > Cc: Davide > Inviato: Gioved? 26 Settembre 2013 19:44 > > Oggetto: Re: [ARMedslack] A quick primer for the PI > > Davide, I've also had problems installing Slackware on RPi. > My board/card did not work with kernel / images they provided. > > I've suggested Slackware for RPI should use Raspbian kernel - because > it is ACTIVELY supported. > > Try my way > > https://salwach.pl/rpi_slackware > >>These images have been tested on a >> multitude of boards and have never failed to boot. > > Recently I've bought 2nd RPi, just switched SD card to new > one..and ooops...black screen. Old works, new one not. > After download of "new" Raspbian and replacing bootloader I've got it > working. > > RPi is NOT Arduino - it changes too fast. > > And guys here do not understand that or ignore it. > > Standard answer: "Works on my computer"....LOL > > > Tom > > W li?cie z 26 wrze?nia 2013: > From: stanley at stanleygarvey.com > To: louigi600 at yahoo.it > CC: > > ssc> No nothing obscure needs to be done it should just work. I > ssc> checked today at home. These images have been tested on a > ssc> multitude of boards and have never failed to boot. > ssc> Have you created a swap and ext4 root fs? Donkt know if it will > ssc> boot without these being present. > ssc> Sent from my BlackBerry smartphone from Virgin Media > > ssc> -----Original Message----- > ssc> From: Davide > ssc> Date: Thu, 26 Sep 2013 15:23:43 > ssc> To: stanley at stanleygarvey.com; > ssc> dowelld at netscape.net; > ssc> armedslack at lists.armedslack.org > ssc> Reply-To: Davide > ssc> Subject: Re: [ARMedslack] A quick primer for the PI > > ssc> No I formatted the filesystem myself and copied files into it. > > ssc> The firs lot of boot loader stuff was gotten out of > ssc> > http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip > ssc> , unzipp created loop device with off set on the image first > ssc> partition ... mounted it and copied files over. > > > ssc> root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img > > ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes > ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors > ssc> Units = sectors of > ssc> 1 * 512 = 512 bytes > ssc> Sector size (logical/physical): 512 bytes / 512 bytes > ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes > ssc> Disk identifier: 0x00007091 > > ssc> Device Boot Start End Blocks > Id System > ssc> slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 > c W95 FAT32 (LBA) > ssc> slackwarearm-14.0-8GB-20130623.img2 97664 878847 390592 > 82 Linux > ssc> swap > ssc> slackwarearm-14.0-8GB-20130623.img3 878848 15751167 > 7436160 83 Linux > ssc> root at darkstar:/tmp# echo $((32 * 512)) > ssc> 16384 > ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0 > ssc> slackwarearm-14.0-8GB-20130623.img > ssc> root at darkstar:/tmp# modprobe vfat > ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ > ssc> root at darkstar:/tmp# ls /mnt/floppy/ > ssc> COPYING.linux* config-raspberrypi-3.2.27* start.elf* > ssc> LICENCE.broadcom* config.txt* > start_cd.elf* > ssc> System.map-raspberrypi-3.2.27* > ssc> fixup.dat* zImage-raspberrypi-3.2.27* > ssc> bootcode.bin* fixup_cd.dat* > ssc> cmdline.txt* initrd-raspberrypi.img* > ssc> root at darkstar:/tmp# > > > ssc> Is there something obscure that need to be done to the dor partition ? > > ssc> Regards > ssc> David > > > ssc> ________________________________ > ssc> Da: "stanley at stanleygarvey.com" > ssc> A: Davide ; "dowelld at netscape.net" > ssc> ; "armedslack at lists.armedslack.org" > ssc> > ssc> Inviato: Gioved? 26 Settembre 2013 14:52 > ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI > ssc> > > > ssc> Did you dd the image onto the card? > ssc> What suze of card? > ssc> Try the installer image at stanleygarvey.com > ssc> Regards, > ssc> Stanley > ssc> Sent from my BlackBerry smartphone from Virgin Media > ssc> ________________________________ > > ssc> From: Davide > ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) > ssc> To: stanley garvey; > ssc> dowelld at netscape.net; > ssc> armedslack at lists.armedslack.org > ssc> ReplyTo: Davide > ssc> Subject: Re: [ARMedslack] A quick primer for the PI > > ssc> I can't get it to boot at all. > ssc> If I turn the PI on I get the PER led solid on but the ACT led does > this: > ssc> first faint on, the bright on for a second or do then it goes off and > stays off. > > ssc> I've tried 2 different SD cards supposing that the firs may have > ssc> had some sort of compatibility issue but the second does the same > thing. > ssc> I downloaded updated boot stuff from here: > ssc> > http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz > ssc> ... but nothing seems to change. > ssc> Is the PI finiky on where the dos partition should begin ? or on the > formatting of it ? > ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and > is fat32 formatted > > ssc> I suspect that its not booting because if I take out the SD and > ssc> mount in on the PC fsck does not detect the filesystem dirty flag > ssc> that I should have if the thing booted but showed nothing on the TV. > > ssc> ATB > ssc> David > > > > ssc> ________________________________ > ssc> Da: stanley garvey > ssc> A: "dowelld at netscape.net" ; > ssc> "armedslack at lists.armedslack.org" > ssc> ; Davide ; > ssc> Slackware ARM port > ssc> Inviato: Gioved? 26 Settembre 2013 13:15 > ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI > ssc> > > > > > > ssc> On Sep 26, 2013 08:25 "Davide" wrote: > >>> >>>>>I got a friend to lend me a PI for a week ... >>> >>>>>I had a quick look at the community links for slackware on the PI but >>>>> none really tell me what i want to know: >>>>>what does the GPU look for in the SD ? (as fas as I know it's the GPU >>>>> that loads stuff from SD into memory and then passes control to it) >>>>>does it look for a second stage boot loader like a uboot image or does >>>>> it load kernel and initrd ? (bootcode.bin) >>>>>I'm supposing that the first partition (the dos one) is where this stuff >>>>> should be put ? >>>>>The content in there looks about right: >>> >>>>>root at darkstar:/tmp# fdisk -l slackwarearm-14.0-8GB-20130623.img >>> >>>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>>Units = sectors of > ssc> 1 * 512 = 512 bytes >>>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>>Disk identifier: 0x00007091 >>> >>>>> Device Boot Start End >>>>> Blocks Id System >>>>>slackwarearm-14.0-8GB-20130623.img1 32 97663 >>>>> 48816 c W95 FAT32 (LBA) >>>>>slackwarearm-14.0-8GB-20130623.img2 97664 878847 >>>>> 390592 82 Linux > ssc> swap >>>>>slackwarearm-14.0-8GB-20130623.img3 878848 15751167 >>>>> 7436160 83 Linux >>>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>>16384 >>>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0 >>>>> slackwarearm-14.0-8GB-20130623.img >>>>>root at darkstar:/tmp# modprobe vfat >>>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>>COPYING.linux* config-raspberrypi-3.2.27* start.elf* >>>>>LICENCE.broadcom* config.txt* >>>>> start_cd.elf* >>>>>System.map-raspberrypi-3.2.27* > ssc> fixup.dat* zImage-raspberrypi-3.2.27* >>>>>bootcode.bin* fixup_cd.dat* >>>>>cmdline.txt* initrd-raspberrypi.img* >>>>root at darkstar:/tmp# >>> >>> >>>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >>> >>>>Hi David, >>>Hi Dave ;) >>> >>>>The GPU looks for > ssc> bootcode.bin, which looks for and loads loader.bin. Loader.bin reads > in > ssc> config.txt (to configure the hardware) and loads start.elf (the GPU > ssc> binary blob). Once it has configured the hardware, it then >loads > ssc> kernel.img, and feeds it the contents of cmdline.txt. >>> >>>But on the readymade image from >>> http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin >>> in the dos partition ! >>>Is there something wrong with this image or is loader.bin optional ? >>> >>>> Hi Davide, ther is nothing wrong with the image, I use it at home, it >>>> could be that loader bin is a new addition to the Fat32 boot partitionfor >>>> Debian variants. the boot layout I use has not changed since last Christmas. >>> >>>>So you have > ssc> to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, > ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt > ssc> file you need the ramdisk image file. >>> >>>> yes >>> >>>Is the initrd loading governed by config.txt ? >>> >>>> yes >>> >>>I see in there ramfsfile=initrd-raspberrypi.img >>>Can I change that manualy with vi and load a different initrd ? or comment >>> it out to not load an initrd at all ? >>> >>>> Yes you can edit the file with vi and load a different initrd. It is >>>> commented out in my config.txt as it is not required to boot a running >>>> system. initrd-raspberrypi.img is the installer, It has been left there so >>>> you can reinstall if you wish, it is a versatile-initrd that has been >>>> modified with a modified version of the mk-tegra.sh. >>> >>>When is the HDMI output initiated ? >>> >>>>Before the system > ssc> comes up as the GPU boots the system. >>> >>>> if you ate looking for a mini root try the installer image, it is 1GB >>>> and is the standard slackwarearm installer so has busybox and other stuff. >>>> you won't be able to install a full system on 1GB the 3rd partition is a >>>> stub and should be deleted and recreated to use the remaining space on >>>> whatever size card you have before stating 'setup'. you may be able to get a >>>> base slackwarearm systm (a)(ap) series on a 4GB card. >>>Hope that helps, >>>Stanley. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From louigi600 at yahoo.it Fri Sep 27 15:14:43 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 27 Sep 2013 16:14:43 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <8D089747568A4B5-9D4-14338@webmail-m288.sysops.aol.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> <8D089747568A4B5-9D4-14338@webmail-m288.sysops.aol.com> Message-ID: <1380294883.98797.YahooMailNeo@web173102.mail.ir2.yahoo.com> I've tied a lot of stuff and retried it with modifications but had no success. The firs thing I was able to boot on my board was a rasbian image 2013-09-10-wheezy-raspbian.img I'll see if I can use the boot and kernel from that to start a slackware userland. I'm not sure if this could be the problem but I've been partitioning with id "c" and mkdosfs -F 32 on the partition. I see that bothe the 8Gb slackware image http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip and the rasbian have id "c" and to my understandin mkdosfs -F 32 doe a vfat filesystem. Appart from that I'm manually copying over files to the partition I made. I may have made some mistakes ... I'll do it again but using the stuff from the rasbian image so it it fails I'm sure it's something I'm doing wrong. ATB David ________________________________ Da: "dowelld at netscape.net" A: louigi600 at yahoo.it; armedslack at lists.armedslack.org Inviato: Venerd? 27 Settembre 2013 10:41 Oggetto: Re: [ARMedslack] A quick primer for the PI I can honestly say I'm quite surprised by some of what is being revealed by some of these emails. I take blank SD cards prep them as per the instructions in that txt file I put up with the files I use, and boot them on different PI boards over and over again. I have days when I run 10-15 installs a day on different Pi boards, and different SD cards (from 2GB to 32GB). All without problems. The same files were used to install and create a two images for distcc which I run across 6+ Pi boards. I've only encountered two problems with booting, the first was the hdmi_safe one, and the second was the base firmwware being old and not supporting the 512M version B boards, hence me updating the firmware and creating the files I put up. Did you try my files? Take an SD card. Partition it to have one (type 6) 50M fat partition on it. mkfs.vfat it to get a fat filesystem on it. copy the files to it. put it in a pi, connect the power, and it should boot, to the standard installer. I have days when I do that multiple times a day, on different SD cards, using different Pi boards (all model B some 256M some 512M versions) I deliberately do it across multiple different boards, because I have to know it will work on both. Thanks. Dave -----Original Message----- From: Davide To: Tom ; armedslack Sent: Fri, Sep 27, 2013 9:10 am Subject: Re: [ARMedslack] A quick primer for the PI I'm downloading the NOOBS and rasbian images to see if I can use those to boot the PI that has been lent to me. Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a new or an old board ? I'm beginning to think that the whole PI project is scrap: the boards were meant to be 25 or 35 USD respectively fro the A or B model, but the cheapest you can get one in europe is for 50 Euro (that's damm close to 70 USD) ... it's twice the price it was supposed to be !!!! you get one and you may not be able to boot it untill you get the correct images for it downloading stuff from the foundation's' ftp server is really slow ... they must have a PI itself serving files? I'm not even sure I want to complete my tests because I don't think I'm gonna buy one ... but I'm just curious to see how bad it actually is. I'll see if I want to try booting after the estimated 4 and 7 hour estimated download time, that I've hadto restart over again because it got truncated and resume does not seem to work. ATB David ________________________________ Da: Tom A: "armedslack at lists.armedslack.org" Cc: Davide Inviato: Gioved? 26 Settembre 2013 19:44 Oggetto: Re: [ARMedslack] A quick primer for the PI Davide, I've also had problems installing Slackware on RPi. My board/card did not work with kernel / images they provided. I've suggested Slackware for RPI should use Raspbian kernel - because it is ACTIVELY supported. Try my way https://salwach.pl/rpi_slackware >These images have been tested on a > multitude of boards and have never failed to boot. Recently I've bought 2nd RPi, just switched SD card to new one..and ooops...black screen. Old works, new one not. After download of "new" Raspbian and replacing bootloader I've got it working. RPi is NOT Arduino - it changes too fast. And guys here do not understand that or ignore it. Standard answer: "Works on my computer"....LOL Tom W li?cie z 26 wrze?nia 2013: From: stanley at stanleygarvey.com To: louigi600 at yahoo.it CC: ssc> No nothing obscure needs to be done it should just work. I ssc> checked today at home. These images have been tested on a ssc> multitude of boards and have never failed to boot. ssc> Have you created a swap and ext4 root fs? Donkt know if it will ssc> boot without these being present. ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> -----Original Message----- ssc> From: Davide ssc> Date: Thu, 26 Sep 2013 15:23:43 ssc> To: stanley at stanleygarvey.com; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> Reply-To: Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> No I formatted the filesystem myself and copied files into it. ssc> The firs lot of boot loader stuff was gotten out of ssc> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip ssc> , unzipp created loop device with off set on the image first ssc> partition ... mounted it and copied files over. ssc> root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors ssc> Units = sectors of ssc>? 1 * 512 = 512 bytes ssc> Sector size (logical/physical): 512 bytes / 512 bytes ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes ssc> Disk identifier: 0x00007091 ssc> ???????????????????????????? Device Boot????? Start???????? End? Blocks?? Id? System ssc> slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663? 48816??? c? W95 FAT32 (LBA) ssc> slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847? 390592?? 82? Linux ssc>? swap ssc> slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167? 7436160?? 83? Linux ssc> root at darkstar:/tmp# echo $((32 * 512)) ssc> 16384 ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0? ssc> slackwarearm-14.0-8GB-20130623.img ssc> root at darkstar:/tmp# modprobe vfat ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc> root at darkstar:/tmp# ls /mnt/floppy/ ssc> COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* ssc> LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* ssc> System.map-raspberrypi-3.2.27*? ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* ssc> bootcode.bin*?????????????????? fixup_cd.dat* ssc> cmdline.txt*??????????????????? initrd-raspberrypi.img* ssc> root at darkstar:/tmp# ssc> Is there something obscure that need to be done to the dor partition ? ssc> Regards ssc> David ssc> ________________________________ ssc>? Da: "stanley at stanleygarvey.com" ssc> A: Davide ; "dowelld at netscape.net" ssc> ; "armedslack at lists.armedslack.org" ssc> ssc> Inviato: Gioved? 26 Settembre 2013 14:52 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>? ssc> Did you dd the image onto the card? ssc> What suze of card? ssc> Try the installer image at stanleygarvey.com ssc> Regards, ssc> Stanley ssc> Sent from my BlackBerry smartphone from Virgin Media ssc> ________________________________ ssc> From:? Davide ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc> To: stanley garvey; ssc> dowelld at netscape.net; ssc> armedslack at lists.armedslack.org ssc> ReplyTo:? Davide ssc> Subject: Re: [ARMedslack] A quick primer for the PI ssc> I can't get it to boot at all. ssc> If I turn the PI on I get the PER led solid on but the ACT led does this: ssc> first faint on, the bright on for a second or do then it goes off and stays off. ssc> I've tried 2 different SD cards supposing that the firs may have ssc> had some sort of compatibility issue but the second does the same thing. ssc> I downloaded updated boot stuff from here: ssc> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz ssc> ... but nothing seems to change. ssc> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted ssc> I suspect that its not booting because if I take out the SD and ssc> mount in on the PC fsck does not detect the filesystem dirty flag ssc> that I should have if the thing booted but showed nothing on the TV. ssc> ATB ssc> David ssc> ________________________________ ssc>? Da: stanley garvey ssc> A: "dowelld at netscape.net" ; ssc> "armedslack at lists.armedslack.org" ssc> ; Davide ; ssc> Slackware ARM port ssc> Inviato: Gioved? 26 Settembre 2013 13:15 ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI ssc>? ssc> On Sep 26, 2013 08:25 "Davide" wrote: >> >>>>I got a friend to lend me a PI? for a week ... >> >>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>The content in there looks about right: >> >>>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >> >>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>Units = sectors of ssc>? 1 * 512 = 512 bytes >>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>Disk identifier: 0x00007091 >> >>>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux ssc>? swap >>>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>16384 >>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>>root at darkstar:/tmp# modprobe vfat >>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>>System.map-raspberrypi-3.2.27*? ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>>bootcode.bin*?????????????????? fixup_cd.dat* >>>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>>root at darkstar:/tmp# >> >> >>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >> >>>Hi David, >>Hi Dave ;) >> >>>The GPU looks for ssc>? bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in ssc>? config.txt (to configure the hardware) and loads start.elf (the GPU ssc> binary blob). Once it has configured the hardware, it then >loads ssc> kernel.img, and feeds it the contents of cmdline.txt. >> >>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>Is there something wrong with this image or is loader.bin optional ? >> >>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >> >>>So you have ssc>? to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt ssc> file you need the ramdisk image file. >> >>> yes >> >>Is the initrd loading governed by config.txt ? >> >>> yes >> >>I see in there ramfsfile=initrd-raspberrypi.img >>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >> >>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >> >>When is the HDMI output initiated ? >> >>>Before the system ssc>? comes up as the GPU boots the system. >> >>>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>Hope that helps, >>Stanley. >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Sep 27 15:16:27 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 27 Sep 2013 16:16:27 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <20130927084623.7A63D351F7A43@bmail06.one.com> References: <1366445387.20130926194449@spoko.eu.org> <1380269445.54727.YahooMailNeo@web173106.mail.ir2.yahoo.com> <20130927084623.7A63D351F7A43@bmail06.one.com> Message-ID: <1380294987.91523.YahooMailNeo@web173104.mail.ir2.yahoo.com> Oh ... I've been working in the same direction but have not got round to finishing up. Regards David ________________________________ Da: stanley garvey A: Tom ; "armedslack at lists.armedslack.org" ; Davide ; Slackware ARM port Inviato: Venerd? 27 Settembre 2013 10:46 Oggetto: Re: [ARMedslack] A quick primer for the PI David I have put up a new boot layout tested here this morning at ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ Still no loader.bin, files taken from weezy 2013-09-10 ( boot files are float agnostic). hope that helps. Stanley On Sep 27, 2013 09:10 "Davide" wrote: I'm downloading the NOOBS and rasbian images to see if I can use those to boot the PI that has been lent to me. >Looking on the underside there is a sticker: E1213RS2V13B1.0 is this a new or an old board ? > > >I'm beginning to think that the whole PI project is scrap: >the boards were meant to be 25 or 35 USD respectively fro the A or B model, but the cheapest you can get one in europe is for 50 Euro (that's damm close to 70 USD) ... it's twice the price it was supposed to be !!!! >you get one and you may not be able to boot it untill you get the correct images for it > >downloading stuff from the foundation's' ftp server is really slow ... they must have a PI itself serving files? > > >I'm not even sure I want to complete my tests because I don't think I'm gonna buy one ... but I'm just curious to see how bad it actually is. >I'll see if I want to try booting after the estimated 4 and 7 hour estimated download time, that I've hadto restart over again because it got truncated and resume does not seem to work. > > > >ATB >David > > > > >________________________________ > Da: Tom >A: "armedslack at lists.armedslack.org" >Cc: Davide >Inviato: Gioved? 26 Settembre 2013 19:44 >Oggetto: Re: [ARMedslack] A quick primer for the PI > > >Davide, I've also had problems installing Slackware on RPi. >My board/card did not work with kernel / images they provided. > >I've suggested Slackware for RPI should use Raspbian kernel - because >it is ACTIVELY supported. > >Try my way > >https://salwach.pl/rpi_slackware >/run/media/stanley/B052-F700/ >>These images have been tested on a >> multitude of boards and have never failed to boot. > >Recently I've bought 2nd RPi, just switched SD card to new >one..and ooops...black screen. Old works, new one not. >After download of "new" Raspbian and replacing bootloader I've got it >working. > >RPi is NOT Arduino - it changes too fast. >/run/media/stanley/B052-F700/ >And guys here do not understand that or ignore it. > >Standard answer: "Works on my computer"....LOL > > >Tom > >W li?cie z 26 wrze?nia 2013: >From: stanley at stanleygarvey.com >To: louigi600 at yahoo.it >CC: >/run/media/stanley/B052-F700/ >ssc> No nothing obscure needs to be done it should just work. I >ssc> checked today at home. These images have been tested on a >ssc> multitude of boards and have never failed to boot. >ssc> Have you created a swap and ext4 root fs? Donkt know if it will >ssc> boot without these being present. >ssc> Sent from my BlackBerry smartphone from Virgin Media > >ssc> -----Original Message----- >ssc> From: Davide >ssc> Date: Thu, 26 Sep 2013 15:23:43 >ssc> To: stanley at stanleygarvey.com; >ssc> dowelld at netscape.net; >ssc> armedslack at lists.armedslack.org >ssc> Reply-To: Davide >ssc> Subject: Re: [ARMedslack] A quick primer for the PI > >ssc> No I formatted the filesystem myself and copied files into it. > >ssc> The firs lot of boot loader stuff was gotten out of >ssc> http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip >ssc> , unzipp created loop device with off set on the image first >ssc> partition ... mounted it and copied files over. > > >ssc> root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img > >ssc> Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >ssc> 4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >ssc> Units = sectors of >ssc>? 1 * 512 = 512 bytes >ssc> Sector size (logical/physical): 512 bytes / 512 bytes >ssc> I/O size (minimum/optimal): 512 bytes / 512 bytes >ssc> Disk identifier: 0x00007091 > >ssc> ???????????????????????????? Device Boot????? Start???????? End? Blocks?? Id? System >ssc> slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663? 48816??? c? W95 FAT32 (LBA) >ssc> slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847? 390592?? 82? Linux >ssc>? swap >ssc> slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167? 7436160?? 83? Linux >ssc> root at darkstar:/tmp# echo $((32 * 512)) >ssc> 16384 >ssc> root at darkstar:/tmp# losetup -o 16384 /dev/loop0? >ssc> slackwarearm-14.0-8GB-20130623.img >ssc> root at darkstar:/tmp# modprobe vfat >ssc> root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >ssc> root at darkstar:/tmp# ls /mnt/floppy/ >ssc> COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >ssc> LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >ssc> System.map-raspberrypi-3.2.27*? >ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >ssc> bootcode.bin*?????????????????? fixup_cd.dat* >ssc> cmdline.txt*??????????????????? initrd-raspberrypi.img* >ssc> root at darkstar:/tmp# > > >ssc> Is there something obscure that need to be done to the dor partition ? > >ssc> Regards >ssc> David > > >ssc> ________________________________ >ssc>? Da: "stanley at stanleygarvey.com" >ssc> A: Davide ; "dowelld at netscape.net" >ssc> ; "armedslack at lists.armedslack.org" >ssc> >ssc> Inviato: Gioved? 26 Settembre 2013 14:52 >ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI >ssc>? > > >ssc> Did you dd the image onto the card? >ssc> What suze of card? >ssc> Try the installer image at stanleygarvey.com >ssc> Regards, >ssc> Stanley >ssc> Sent from my BlackBerry smartphone from Virgin Media >ssc> ________________________________ > >ssc> From:? Davide >ssc> Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) >ssc> To: stanley garvey; >ssc> dowelld at netscape.net; >ssc> armedslack at lists.armedslack.org >ssc> ReplyTo:? Davide >ssc> Subject: Re: [ARMedslack] A quick primer for the PI > >ssc> I can't get it to boot at all. >ssc> If I turn the PI on I get the PER led solid on but the ACT led does this: >ssc> first faint on, the bright on for a second or do then it goes off and stays off. > >ssc> I've tried 2 different SD cards supposing that the firs may have >ssc> had some sort of compatibility issue but the second does the same thing. >ssc> I downloaded updated boot stuff from here: >ssc> http://www.daves-collective.co.uk/raspi/system/raspi-boot-20120801-fw-1_dbs.tgz >ssc> ... but nothing seems to change. >ssc> Is the PI finiky on where the dos partition should begin ? or on the formatting of it ? >ssc> mine starts at sector 2048 (1Mb from the beginning of the device) and is fat32 formatted > >ssc> I suspect that its not booting because if I take out the SD and >ssc> mount in on the PC fsck does not detect the filesystem dirty flag >ssc> that I should have if the thing booted but showed nothing on the TV. > >ssc> ATB >ssc> David > > > >ssc> ________________________________ >ssc>? Da: stanley garvey >ssc> A: "dowelld at netscape.net" ; >ssc> "armedslack at lists.armedslack.org" >ssc> ; Davide ; >ssc> Slackware ARM port >ssc> Inviato: Gioved? 26 Settembre 2013 13:15 >ssc> Oggetto: Re: [ARMedslack] A quick primer for the PI >ssc>? > > > > > >ssc> On Sep 26, 2013 08:25 "Davide" wrote: > >>> >>>>>I got a friend to lend me a PI? for a week ... >>> >>>>>I had a quick look at the community links for slackware on the PI but none really tell me what i want to know: >>>>>what does the GPU? look? for in the SD ? (as fas as I know it's the GPU that loads stuff from SD into memory and then passes control to it) >>>>>does it look for a second stage boot loader like a uboot image or does it load kernel and initrd ? (bootcode.bin) >>>>>I'm supposing that the first partition (the dos one) is where this stuff should be put ? >>>>>The content in there looks about right: >>> >>>>>root at darkstar:/tmp# fdisk? -l slackwarearm-14.0-8GB-20130623.img >>> >>>>>Disk slackwarearm-14.0-8GB-20130623.img: 2558 MB, 2558967808 bytes >>>>>4 heads, 32 sectors/track, 39046 cylinders, total 4997984 sectors >>>>>Units = sectors of >ssc>? 1 * 512 = 512 bytes >>>>>Sector size (logical/physical): 512 bytes / 512 bytes >>>>>I/O size (minimum/optimal): 512 bytes / 512 bytes >>>>>Disk identifier: 0x00007091 >>> >>>>> ?????????????????????????? Device Boot????? Start???????? End????? Blocks?? Id? System >>>>>slackwarearm-14.0-8GB-20130623.img1????????????? 32?????? 97663?????? 48816??? c? W95 FAT32 (LBA) >>>>>slackwarearm-14.0-8GB-20130623.img2?????????? 97664????? 878847????? 390592?? 82? Linux >ssc>? swap >>>>>slackwarearm-14.0-8GB-20130623.img3????????? 878848??? 15751167???? 7436160?? 83? Linux >>>>>root at darkstar:/tmp# echo $((32 * 512)) >>>>>16384 >>>>>root at darkstar:/tmp# losetup -o 16384 /dev/loop0? slackwarearm-14.0-8GB-20130623.img >>>>>root at darkstar:/tmp# modprobe vfat >>>>>root at darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ >>>>>root at darkstar:/tmp# ls /mnt/floppy/ >>>>>COPYING.linux*????????????????? config-raspberrypi-3.2.27*? start.elf* >>>>>LICENCE.broadcom*?????????????? config.txt*???????????????? start_cd.elf* >>>>>System.map-raspberrypi-3.2.27*? >ssc>? fixup.dat*????????????????? zImage-raspberrypi-3.2.27* >>>>>bootcode.bin*?????????????????? fixup_cd.dat* >>>>>cmdline.txt*??????????????????? initrd-raspberrypi.img* >>>>root at darkstar:/tmp# >>> >>> >>>>>I plan to play a little with a miniroot so I won't need an 8Gb SD :) >>> >>>>Hi David, >>>Hi Dave ;) >>> >>>>The GPU looks for >ssc>? bootcode.bin, which looks for and loads loader.bin. Loader.bin reads in >ssc>? config.txt (to configure the hardware) and loads start.elf (the GPU >ssc> binary blob). Once it has configured the hardware, it then >loads >ssc> kernel.img, and feeds it the contents of cmdline.txt. >>> >>>But on the readymade image from http://stanleygarvey.com/slackwarearm_rpi/index.php there is no loader.bin in the dos partition ! >>>Is there something wrong with this image or is loader.bin optional ? >>> >>>> Hi Davide, ther is nothing wrong with the image, I use it at home, it could be that loader bin is a new addition to the Fat32 boot partitionfor Debian variants. the boot layout I use has not changed since last Christmas. >>> >>>>So you have >ssc>? to have bootcode.bin, loader.bin, config.txt, start.elf, kernel.img, >ssc> and cmdline.txt, then if you load a ramdisk image in the cmdline.txt >ssc> file you need the ramdisk image file. >>> >>>> yes >>> >>>Is the initrd loading governed by config.txt ? >>> >>>> yes >>> >>>I see in there ramfsfile=initrd-raspberrypi.img >>>Can I change that manualy with vi and load a different initrd ? or comment it out to not load an initrd at all ? >>> >>>> Yes you can edit the file with vi and load a different initrd. It is commented out in my config.txt as it is not required to boot a running system. initrd-raspberrypi.img is the installer, It has been left there so you can reinstall if you wish, it is a versatile-initrd that has been modified with a modified version of the mk-tegra.sh. >>> >>>When is the HDMI output initiated ? >>> >>>>Before the system >ssc>? comes up as the GPU boots the system. >>> >>>>? if you ate looking for a mini root try the installer image, it is 1GB and is the standard slackwarearm installer so has busybox and other stuff. you won't be able to install a full system on 1GB the 3rd partition is a stub and should be deleted and recreated to use the remaining space on whatever size card you have before stating 'setup'. you may be able to get a base slackwarearm systm (a)(ap) series on a 4GB card. >>>Hope that helps, >>>Stanley. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowelld at netscape.net Fri Sep 27 19:01:05 2013 From: dowelld at netscape.net (dowelld at netscape.net) Date: Fri, 27 Sep 2013 15:01:05 -0400 (EDT) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <916470782.20130927131640@spoko.eu.org> References: <20130927085145.DF062BECD435F@bmail04.one.com> <2610359261.20130927111808@spoko.eu.org> <20130927100431.A364E9995BE5E@bmail06.one.com> <916470782.20130927131640@spoko.eu.org> Message-ID: <8D089CB0D603ED7-9D4-195C0@webmail-m288.sysops.aol.com> Hi Tom, You can try my files if you want, they work for me. http://www.dowelld.net/?p=49 Thanks Dave -----Original Message----- From: Tom To: Slackware ARM port Sent: Fri, Sep 27, 2013 12:16 pm Subject: Re: [ARMedslack] A quick primer for the PI I do not need images to test, just boot files and kernel. With these: ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ Both of mine RPis hang at "colorful" screen. Set of files that work for me: https://salwach.pl/img/RPi/slack14_tom.zip Tom >> Would you be prepared to test one of my images on your new pi to see >> if they boot? Either the 8GB or the installer with the old boot >> layout? the new firmware I tried this morning is causing the pi to >> reboot on 'shutdown -h now' . This is undesirable. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Sep 27 20:08:26 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 27 Sep 2013 21:08:26 +0100 Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <916470782.20130927131640@spoko.eu.org> References: <20130927100431.A364E9995BE5E@bmail06.one.com> <916470782.20130927131640@spoko.eu.org> Message-ID: <20130927200826.E92927B1D974B@bmail02.one.com> On Sep 27, 2013 12:16 "Tom" wrote: > I do not need images to test, just boot files and kernel. > > With these: > ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ > > Both of mine RPis hang at "colorful" screen. > > Set of files that work for me: > > > Tom > > > > > Thanks for testing, > > > ftp://ftp.stanleygarvey.co.uk/pub/slackwarearm_rpi/boot/ > > > These are the new raspbian wheezy 2013-09-10 boot files and where > > > for Davide to try. > > > The kernel is mine, but expects swap on partition 2 and ext4 > > > rootfs on partition 3, and the cmdline.txt is compiled into the > > > kernel. the kernel also requires the config.txt to point to it as > > > it is not called kernel.img. > > > I am sure your files will work for me here but so do mine. > > > Thanks for your help. > > > Stanley > > > > > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Sep 27 21:20:43 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 27 Sep 2013 22:20:43 +0100 Subject: [ARMedslack] Raspberry-Pi sanity check Message-ID: <20130927212043.4682C4217A595@bmail04.one.com> Okay, Just to check I am sane I will now demonstrate how to install an image to SDHC card, there will be no camera tricks or fudges: As root: ------------------------------------------------------------------------ -------------------- bash-4.2# cd /home/stanley bash-4.2# mkdir sanity-check bash-4.2# cd sanity-check bash-4.2# wget http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623 .zip --2013-09-27 20:26:42-- http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623 .zip Resolving stanleygarvey.com (stanleygarvey.com)... 46.30.211.48 Connecting to stanleygarvey.com (stanleygarvey.com)|46.30.211.48|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1632447253 (1.5G) [application/zip] Saving to: 'slackwarearm-14.0-8GB-20130623.zip' 100%[====================================>] 1,632,447,253 7.43MB/s in 3m 36s 2013-09-27 20:30:47 (7.22 MB/s) - 'slackwarearm-14.0-8GB-20130623.zip' saved [1632447253/1632447253] bash-4.2# unzip slackwarearm-14.0-8GB-20130623.zip Archive: slackwarearm-14.0-8GB-20130623.zip inflating: slackwarearm-14.0-8GB-20130623.img ------------------------------------------------------------------------ ----------------- Just for good measure ------------------------------------------------------------------------ ------------------ bash-4.2# md5sum slackwarearm-14.0-8GB-20130623.img b96fbb397ce028af8cc257b5b5c4f443 slackwarearm-14.0-8GB-20130623.img ------------------------------------------------------------------------ ------------------ Now I insert an SDHC 8GB card, on this system. I have 1 hard drive(/dev/sda) and one USB Drive(dev/sdb) the SDHC card becomes /dev/sdc ------------------------------------------------------------------------ ------------------ bash-4.2# dd if=slackwarearm-14.0-8GB-20130623.img of=/dev/sdc bs=65536 123056+0 records in 123056+0 records out 8064598016 bytes (8.1 GB) copied, 1856 s, 4.3 MB/s ------------------------------------------------------------------------ ------------------- Well that took a while! Now I pop the SDHC card into a random Raspberry Pi and boot and ... Er ..it just boots up. -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Sep 30 10:30:10 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 30 Sep 2013 11:30:10 +0100 (BST) Subject: [ARMedslack] A quick primer for the PI In-Reply-To: <20130927200826.E92927B1D974B@bmail02.one.com> References: <20130927100431.A364E9995BE5E@bmail06.one.com> <916470782.20130927131640@spoko.eu.org> <20130927200826.E92927B1D974B@bmail02.one.com> Message-ID: <1380537010.25641.YahooMailNeo@web173102.mail.ir2.yahoo.com> Ok I grabbed the boot stuff from rasbian (2013-09-10) and used the slackware arm miniroot in a freshlu formatted and partitioned SD .... it boots (minor issue complaining about root being already mounted rw ... probabbly need to add? ro to cmdline or edit the fstab). ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From y.turgut at gmail.com Mon Sep 30 18:50:08 2013 From: y.turgut at gmail.com (Yigit Turgut) Date: Mon, 30 Sep 2013 21:50:08 +0300 Subject: [ARMedslack] Raspberry-Pi sanity check In-Reply-To: <20130927212043.4682C4217A595@bmail04.one.com> References: <20130927212043.4682C4217A595@bmail04.one.com> Message-ID: You post feels like installing windows xp and/thus doesn't prove that you are sane. http://en.wikipedia.org/wiki/Sane I think it would be better if you could give instructions to get slackarm-current from official source,burn to card,boot up (the whole procedure....) - like fatdog. On Sat, Sep 28, 2013 at 12:20 AM, stanley garvey wrote: > Okay, Just to check I am sane I will now demonstrate how to install an > image to SDHC card, there will be no camera tricks or fudges: > As root: > > -------------------------------------------------------------------------------------------- > bash-4.2# cd /home/stanley > bash-4.2# mkdir sanity-check > bash-4.2# cd sanity-check > bash-4.2# wget > http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip > --2013-09-27 20:26:42-- > http://stanleygarvey.com/slackwarearm_rpi/slackwarearm-14.0-8GB-20130623.zip > Resolving stanleygarvey.com (stanleygarvey.com)... 46.30.211.48 > Connecting to stanleygarvey.com (stanleygarvey.com)|46.30.211.48|:80... > connected. > HTTP request sent, awaiting response... 200 OK > Length: 1632447253 (1.5G) [application/zip] > Saving to: 'slackwarearm-14.0-8GB-20130623.zip' > > 100%[====================================>] 1,632,447,253 7.43MB/s in 3m > 36s > > 2013-09-27 20:30:47 (7.22 MB/s) - 'slackwarearm-14.0-8GB-20130623.zip' > saved [1632447253/1632447253] > bash-4.2# unzip slackwarearm-14.0-8GB-20130623.zip > Archive: slackwarearm-14.0-8GB-20130623.zip > inflating: slackwarearm-14.0-8GB-20130623.img > > ----------------------------------------------------------------------------------------- > Just for good measure > > ------------------------------------------------------------------------------------------ > bash-4.2# md5sum slackwarearm-14.0-8GB-20130623.img > b96fbb397ce028af8cc257b5b5c4f443 slackwarearm-14.0-8GB-20130623.img > > ------------------------------------------------------------------------------------------ > Now I insert an SDHC 8GB card, on this system. I have 1 hard > drive(/dev/sda) and one USB Drive(dev/sdb) > the SDHC card becomes /dev/sdc > > ------------------------------------------------------------------------------------------ > bash-4.2# dd if=slackwarearm-14.0-8GB-20130623.img of=/dev/sdc bs=65536 > 123056+0 records in > 123056+0 records out > 8064598016 bytes (8.1 GB) copied, 1856 s, 4.3 MB/s > > ------------------------------------------------------------------------------------------- > Well that took a while! Now I pop the SDHC card into a random Raspberry > Pi and boot and ... Er ..it just boots up. > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Mon Sep 30 19:37:31 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 30 Sep 2013 20:37:31 +0100 Subject: [ARMedslack] Raspberry-Pi sanity check In-Reply-To: References: <20130927212043.4682C4217A595@bmail04.one.com> Message-ID: <20130930193731.4E7358FA63293@bmail03.one.com> On Sep 30, 2013 19:50 "Yigit Turgut" wrote: > > You post feels like installing windows xp and/thus doesn't prove that > you are sane. > > > > I think it would be better if you could give instructions to get > slackarm-current from official source,burn to card,boot up (the whole > procedure....) - like fatdog. > > Yes I do need to document more, In this instance I just needed to > prove to myself and to anyone that was listening that the files were > not corrupt and booted. > The Images are an easy way to skip the installation procedure, the > installer is better, you get to select the packages you want. > I have no wish to reinvent the wheel and there are some great texts > around showing how to install a Slackware system, fatdog has done an > excellent job. Personally I would install via FTP of HTTP and not from > a USB stick, however not everyone has internet access, so it's horses > for courses. > If you wish to install current then use the installer and point it to > the official source. The Installer is just the standard Slackwarearm > installer I have changed very little. > Regards. > Stanley > > > > > > > > > > > _______________________________________________ > > ARMedslack mailing list > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: