Re: [ARMedslack] A quick primer for the PI
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 tom...@spoko.eu.org A: armedslack@lists.armedslack.org armedslack@lists.armedslack.org Cc: Davide louigi...@yahoo.it 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 computerLOL Tom W liście z 26 września 2013: From: stan...@stanleygarvey.com To: louigi...@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 louigi...@yahoo.it ssc Date: Thu, 26 Sep 2013 15:23:43 ssc To: stan...@stanleygarvey.comstan...@stanleygarvey.com; ssc dowe...@netscape.netdowe...@netscape.net; ssc armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org ssc Reply-To: Davide louigi...@yahoo.it 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@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: 0x7091 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@darkstar:/tmp# echo $((32 * 512)) ssc 16384 ssc root@darkstar:/tmp# losetup -o 16384 /dev/loop0 ssc slackwarearm-14.0-8GB-20130623.img ssc root@darkstar:/tmp# modprobe vfat ssc root@darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ ssc root@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@darkstar:/tmp# ssc Is there something obscure that need to be done to the dor partition ? ssc Regards ssc David ssc ssc Da: stan...@stanleygarvey.com stan...@stanleygarvey.com ssc A: Davide louigi...@yahoo.it; dowe...@netscape.net ssc dowe...@netscape.net; armedslack@lists.armedslack.org ssc armedslack@lists.armedslack.org 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 louigi...@yahoo.it ssc Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) ssc To: stanley garveystan...@stanleygarvey.com; ssc dowe...@netscape.netdowe...@netscape.net; ssc armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org ssc ReplyTo: Davide louigi...@yahoo.it 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
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 louigi...@yahoo.it To: Tom tom...@spoko.eu.org; armedslack armedslack@lists.armedslack.org 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 tom...@spoko.eu.org A: armedslack@lists.armedslack.org armedslack@lists.armedslack.org Cc: Davide louigi...@yahoo.it 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 computerLOL Tom W liście z 26 września 2013: From: stan...@stanleygarvey.com To: louigi...@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 louigi...@yahoo.it ssc Date: Thu, 26 Sep 2013 15:23:43 ssc To: stan...@stanleygarvey.comstan...@stanleygarvey.com; ssc dowe...@netscape.netdowe...@netscape.net; ssc armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org ssc Reply-To: Davide louigi...@yahoo.it 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@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: 0x7091
Re: [ARMedslack] A quick primer for the PI
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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
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 tom...@spoko.eu.org To: Slackware ARM port armedslack@lists.armedslack.org 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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
On Sep 27, 2013 12:16 Tom tom...@spoko.eu.org 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: https://salwach.pl/img/RPi/slack14_tom.zip 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 ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] Raspberry-Pi sanity check
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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
