SliTaz Forum

slitaz on raspberry pi

(44 posts) (9 voices)

• Started 10 years ago by tiziano
• Latest reply from Bellard
• This topic is not resolved

Tags:

No tags yet.

1. 

   emgi
   

   offline

   Member

   Partition type for /boot must be 'c' instead of 'b'.
   At least that is what works for me...

   /emgi

   Posted 10 years ago #
2. 

   tiziano
   

   offline

   Member

   changed partition with 'c' - same problem - I'm really ....

   

   Attachments

   1. part_c.jpg (122.7 KB, 1,450 downloads) 10 years old

   Posted 10 years ago #
3. 

   tiziano
   

   offline

   Member

   Hi Paul

   thanks for your hint -unfortunately I'm a newbie and I don'to even know what hacking a script does mean - I did try a manual installation checking into the istall.sh script and trying to repeat the commands on a terminal as I mentioned in a previous mail with no result as well - I'm really pissed because if it goes like this I'm going to get frustated and abandon my intention to test slitaz in my rpi which is a pity cause I'm using it in one of my old pc and it runs fast and flawless - honestly no comparison with other more famous linux distribution....

   Posted 10 years ago #
4. 

   tiziano
   

   offline

   Member

   Hi Paul

   thanks for your hint -unfortunately I'm a newbie and I don'to even know what hacking a script does mean - I did try a manual installation checking into the istall.sh script and trying to repeat the commands on a terminal as I mentioned in a previous mail with no result as well - I'm really pissed because if it goes like this I'm going to get frustated and abandon my intention to test slitaz in my rpi which is a pity cause I'm using it in one of my old pc and it runs fast and flawless - honestly no comparison with other more famous linux distribution....

   Posted 10 years ago #
5. 

   Paul
   

   offline

   Key Master

   Hi tiziano

   I think I confused myself (that's why I deleted the post)

   Are you using a card slot or a card reader?

   Basically I partitioned my SD and hacked the install.sh using an internal card slot on a Debian based system where the card showed up as: /dev/mmcblk0

   Though it looks like your card shows up as /dev/sda on slitaz

   Posted 10 years ago #
6. 

   tiziano
   

   offline

   Member

   Actually I'm using a card reader in a SliTaz environment - tested also debian with a card slot with no success either - with debian though
   Only used Gparted instead of fdisk in order to partiton SD card but I think it doesn't matter in the end. Only the /dev name changes... Isn't it?

   Posted 10 years ago #
7. 

   Paul
   

   offline

   Key Master

   Hi tiziano

   OK, go back to your Debian system with a card slot (and Gparted) and run:

   $ sudo fdisk -l

   And post the results.

   Hopefully it should look something like this:

   /dev/mmcblk0p1 * 63 96389 48163+ b W95 FAT32
   /dev/mmcblk0p2 96390 931769 417690 82 Linux swap / Solaris
   /dev/mmcblk0p3 931770 62332199 30700215 83 Linux

   Posted 10 years ago #
8. 

   emgi
   

   offline

   Member

   Something goes wrong while mounting the SD card.
   What error message do you get when you try to mount /dev/sda1 manually?
   Syntax: mount /dev/sda1 -t vfat

   Perhaps the partion is not formatted?
   Try to format it using mkfs.vfat -F 32 /dev/sda1
   (I did the formatting om my windows PC so the above is untested.)

   /emgi

   Posted 10 years ago #
9. 

   tiziano
   

   offline

   Member

   @emgi

   first - I'd like to thank you for the useful information you posted - particularly appreciated by a newbie like me

   second - see what I got by typing your latest commands

   

   Attachments

   1. vfat.jpg (63.2 KB, 1,431 downloads) 10 years old

   Posted 10 years ago #
10. 

    tiziano
    

    offline

    Member

    @Paul

    here you go

    

    Attachments

    1. Screenshot_from_2014-11-16_19_33_16.png (74.6 KB, 1,343 downloads) 10 years old

    Posted 10 years ago #
11. 

    emgi
    

    offline

    Member

    Please show us the output of /etc/fstab
    The error occurs while there is no entry for /dev/sda1

    The line should look like:
    /dev/sda1 /boot vfat defaults 0 2

    If there is another device for /boot, you can probably suffice by changing it.

    Also: there is supposed to be a space between -F 32 and /dev/..
    I cannot see that on your output.

    /emgi

    Posted 10 years ago #
12. 

    tiziano
    

    offline

    Member

    emgi you're right - no entry in /etc/fstab for /dev/sda1

    space between -F and /dev/.. was missing

    did it meanwhile again (with space between) and let install.sh run again
    here the outcome together with the fstab information

    

    Attachments

    1. fstab1.jpg (88.3 KB, 1,430 downloads) 10 years old

    Posted 10 years ago #
13. 

    emgi
    

    offline

    Member

    Sorry to let you linger for so long. This is mainly because I'm not too intimate with the procedure myself and I had to make time to check it. ;-)
    However, meanwhile I managed to get slitaz-arm booted and, like you I created the SD card manually on a slitaz machine.
    Here are my findings:

    Starting point: logged in as root in the directory containing install.sh. In my case, the SD reader showed up as sdb; this will probably be sda for you.
    Step 1: You have to use fdisk to create the partitions. That already looks fine. All three MUST be primary partitions.
    Then, you have to make the FAT32 partiton bootable using fdisk with the a-option (toggle bootflag).
    Last entry before exiting fdisk is the w-option for writing the changes to the card.

    Next step: format partitions 1 and 3:
    mkfs.vfat -F 32 /dev/sdb1
    mkfs.ext4 /dev/sdb3

    You will notice that after this step, you are able to mount both partitions by hand when you specify the fs-type.
    This will be vfat for /dev/sdb1 and ext4 for /dev/sdb3. Syntax:
    mount /dev/sdb1 /media/rpi/boot -t vfat
    mount /dev/sdb3 /media/rpi/rootfs -t ext4
    If you still get error messages here, the partions may have been automounted and you have to unmount them first using: umount /dev/sdb1 /dev/sdb3

    When the mount is successful you can execute the two copy commands from the script, without the status option:
    cp -a boot/* /media/rpi/boot/
    cp -a rootfs/* /media/rpi/rootfs/

    You may verify the copy action with:
    ls /media/rpi/boot/
    ls /media/rpi/rootfs/
    Both commands should show a familiar(?) output; at least there must be a bunch of files.

    Then umount both partitions again, remove the SD card and test your work in a raspberry pi.
    Due to some trial & error and the fact that I also attempted to use the script, it worked upon the second attempt.
    The biggest issue probably was the proper formatting of the partitions.
    In hindsight, the script might work as well if the SD card is fully prepared like described here.
    Goodluck!

    /emgi

    Posted 10 years ago #
14. 

    tiziano
    

    offline

    Member

    @emgi

    got that bloody ownership error again which I had in previous tests already by copying boot files - even if ls command shows the files in the SD card by booting into the raspi it goes panic again...

    also at the end was unable to umount both partitions - please see screenshots

    I'm gonna try to do the partiton anew and try again for the nth time

    

    Attachments

    1. palette.jpg (31.5 KB, 1,382 downloads) 10 years old
    2. files.jpg (120.4 KB, 1,316 downloads) 10 years old

    Posted 10 years ago #
15. 

    emgi
    

    offline

    Member

    It will be hard to spell it out more explicit than I already did.
    All I can say is this worked for me. Erase the card and format it properly.
    umount before you start to remove automounts. Only write to an empty disk.
    Take small steps and verify each step thoroughly. I did it, you will get there too!

    Meanwhile I have also created a disk image from my 1G card.
    It even boots under Qemu version 15.3 for windows.
    I will try to get it uploaded (64MB .rar file). No luck!

    /emgi

    Posted 10 years ago #

RSS feed for this topic

Reply »

You must log in to post.