Re: [ARMedslack] A quick primer for the PI
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___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
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
Re: [ARMedslack] A quick primer for the PI
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: stan...@stanleygarvey.com stan...@stanleygarvey.com A: stan...@stanleygarvey.com; Slackware ARM port armedslack@lists.armedslack.org 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: stan...@stanleygarvey.com Sender: ARMedslack To: Davide To: Slackware ARM port ReplyTo: stan...@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 louigi...@yahoo.it Sender: ARMedslack armedslack-boun...@lists.armedslack.orgDate: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM portarmedslack@lists.armedslack.org Reply-To: Davide louigi...@yahoo.it, Slackware ARM port armedslack@lists.armedslack.org Subject: [ARMedslack] A quick primer for the PI ___ 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 Sent from my BlackBerry smartphone from Virgin Media ___ 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 Thu, Sep 26, 2013 at 12:52:53PM +, stan...@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 x.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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] A quick primer for the PI
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@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@darkstar:/mnt/floppy# and this is the last content of the boot partition: root@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@darkstar:/mnt/floppy# I'm puzzled ! David Da: dowe...@netscape.net dowe...@netscape.net A: louigi...@yahoo.it; stan...@stanleygarvey.com; armedslack@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 louigi...@yahoo.it To: stanley garvey stan...@stanleygarvey.com; dowelld dowe...@netscape.net; armedslack armedslack@lists.armedslack.org 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 stan...@stanleygarvey.com A: dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@lists.armedslack.org; Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 Davide louigi...@yahoo.it 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@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: 0x7091 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
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@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: 0x7091 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@darkstar:/tmp# echo $((32 * 512)) 16384 root@darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img root@darkstar:/tmp# modprobe vfat root@darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root@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@darkstar:/tmp# Is there something obscure that need to be done to the dor partition ? Regards David Da: stan...@stanleygarvey.com stan...@stanleygarvey.com A: Davide louigi...@yahoo.it; dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@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 louigi...@yahoo.it Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) To: stanley garveystan...@stanleygarvey.com; dowe...@netscape.netdowe...@netscape.net; armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org ReplyTo: Davide louigi...@yahoo.it 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 stan...@stanleygarvey.com A: dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@lists.armedslack.org; Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 Davide louigi...@yahoo.it 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@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: 0x7091 Device Boot Start End Blocks Id System slackwarearm-14.0-8GB-20130623.img1 32 97663 48816 c
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 -Original Message- From: Davide louigi...@yahoo.it Date: Thu, 26 Sep 2013 15:23:43 To: stan...@stanleygarvey.comstan...@stanleygarvey.com; dowe...@netscape.netdowe...@netscape.net; armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org Reply-To: Davide louigi...@yahoo.it 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@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: 0x7091 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@darkstar:/tmp# echo $((32 * 512)) 16384 root@darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img root@darkstar:/tmp# modprobe vfat root@darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root@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@darkstar:/tmp# Is there something obscure that need to be done to the dor partition ? Regards David Da: stan...@stanleygarvey.com stan...@stanleygarvey.com A: Davide louigi...@yahoo.it; dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@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 louigi...@yahoo.it Date: Thu, 26 Sep 2013 13:38:21 +0100 (BST) To: stanley garveystan...@stanleygarvey.com; dowe...@netscape.netdowe...@netscape.net; armedslack@lists.armedslack.orgarmedslack@lists.armedslack.org ReplyTo: Davide louigi...@yahoo.it 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 stan...@stanleygarvey.com A: dowe...@netscape.net dowe...@netscape.net; armedslack@lists.armedslack.org armedslack@lists.armedslack.org; Davide louigi...@yahoo.it; Slackware ARM port armedslack@lists.armedslack.org Inviato: Giovedì 26 Settembre 2013 13:15 Oggetto: Re: [ARMedslack] A quick primer for the PI On Sep 26, 2013 08:25 Davide louigi...@yahoo.it 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
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 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
Re: [ARMedslack] A quick primer for the PI
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 louigi...@yahoo.it Sender: ARMedslack armedslack-boun...@lists.armedslack.orgDate: Wed, 25 Sep 2013 15:46:29 To: Slackware ARM portarmedslack@lists.armedslack.org Reply-To: Davide louigi...@yahoo.it, Slackware ARM port armedslack@lists.armedslack.org Subject: [ARMedslack] A quick primer for the PI ___ 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
-Original Message- From: Davide louigi...@yahoo.it To: Slackware ARM port armedslack@lists.armedslack.org 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@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: 0x7091 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 87884815751167 7436160 83 Linux root@darkstar:/tmp# echo $((32 * 512)) 16384 root@darkstar:/tmp# losetup -o 16384 /dev/loop0 slackwarearm-14.0-8GB-20130623.img root@darkstar:/tmp# modprobe vfat root@darkstar:/tmp# mount /dev/loop0 /mnt/floppy/ root@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@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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
