WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Pi 3 - Model B+  (Read 488 times)

Offline rodrigo

  • WikiUser
  • *
  • Posts: 1
Pi 3 - Model B+
« on: September 17, 2018, 12:56:06 PM »
Hello,

Can someone help me, I need to create an image for raspberry Pi 3 b +, it will only be used to connect to an RDP server, so I would like the image to be booted via tftpd

Thank you,

Offline centralware

  • Sr. Member
  • ****
  • Posts: 313
Re: Pi 3 - Model B+
« Reply #1 on: September 17, 2018, 10:17:49 PM »
3B+ (if memory serves) requires a newer kernel if I'm not mistaken, which is currently in the works (piCore 10 Beta5 was the last test release I believe.)
I have a few dozen 2B and 3B cards here (and a hand-full zeros) but have not yet picked up a 3B+ to see what all the fuss is about.


If you're willing to be a beta tester with the knowledge that things are NOT finished yet, click here.
Additionally (I was testing 10b5 on a Pi3 a week or so ago, the repository is far from being copied over from v9 so I created a script/program to help locate extensions which tce-load may not find.)
This can be found here.  (Once v10 is installed, paste the code into a file called tce-find, place it in the /bin directory as it sounds like you're going to remaster.)
Good luck!


Offline core-user

  • Full Member
  • ***
  • Posts: 143
  • Linux since 1999
Re: Pi 3 - Model B+
« Reply #2 on: September 20, 2018, 05:51:11 AM »
Hopefully, there will be a RPi3B+ version of CorePlus, that would have me putting it on mine. :)

I did try putting the 9.0 series TinyCore on a 3B, but I couldn't work out how to get my downloaded programs into my tce directory, they kept dissappearing on reboot.

(I had set up home, tce, & opt on my disk & boot).
AMD, ARM, & Intel.

Offline centralware

  • Sr. Member
  • ****
  • Posts: 313
Re: Pi 3 - Model B+
« Reply #3 on: October 12, 2018, 08:38:52 PM »
For 3B with vanishing extensions (after rebooting)


You need a PERSISTENT TCE directory (and optionally /opt, /home, etc.)


    Boot into your 3B with PiCore v9.x

    The SD card is going to be split into two pieces, Partition's 1 and 2

    /mnt/mmcblk0p1 is the DOS/boot partition which for most of us we leave alone unless we have to tweak something, in your case, the command-line text files.

    run sudo fdisk /dev/mmcblk0 and if the second partition exists (mmcblk0p2), DELETE it and create a new one (filling the remainder of the card.)

    Reboot and format your new partition with mkfs.ext2 /dev/mmcblk0p2 -L tcedisk which also gives the partition a name of "tcedisk"

    Either using PiCore or your desktop, you'll need to edit the cmdline[].txt files and add tce=LABEL=tcedisk to the end of the line in order to make your tce (extension) directory a part of your SD card which will be there after you reboot.


* If your SD card is 16GB or higher you might want to use gdisk instead of fdisk (tce-load -wi gdisk) though for the rookie it might be a bit more complicated than fdisk - start off with 8GB or less if it poses and issue.
« Last Edit: October 12, 2018, 08:41:50 PM by centralware »

Offline core-user

  • Full Member
  • ***
  • Posts: 143
  • Linux since 1999
Re: Pi 3 - Model B+
« Reply #4 on: October 13, 2018, 01:06:41 AM »
Thanks for the info, will copy it & try again with 10 when it comes out. :)

(I was trying to use sda1 for tce, opt & home.)
AMD, ARM, & Intel.

Offline centralware

  • Sr. Member
  • ****
  • Posts: 313
Re: Pi 3 - Model B+
« Reply #5 on: October 13, 2018, 01:34:17 AM »

SDA (usb device) is do-able, too.
1. Partition and format the device (ext2 if flash, ext3 or ext4 if HDD.  FAT or NTFS can't work properly with linux permissions.)
2. Using either the UUID or LABEL, add the following to cmdline[].txt in mmcblk0p1


tce=LABEL=[Disc Label]
or
tce=UUID="[Long ID #]"
To get the UUID number, simply type in blkid while it's plugged in and look for /dev/sda1.

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5935
Re: Pi 3 - Model B+
« Reply #6 on: October 13, 2018, 06:47:48 AM »
Hi core-user
To get the UUID number, simply type in blkid while it's plugged in and look for /dev/sda1.
Don't do that. You'll also get all your loop mounted extensions which you're not interested in. Try this:
Code: [Select]
blkid /dev/sd*
That way it will only return all your  SD  devices:
Code: [Select]
tc@box:~$ blkid /dev/sd*
/dev/sda1: UUID="77f3e5df-806f-480c-b6cc-905cb3132753" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: UUID="cf1bbc2f-abba-4032-8609-1d3789d269fe" TYPE="swap"
/dev/sda3: UUID="6b92c5e1-f49e-480e-87a0-8c1391a873c7" TYPE="ext3"
/dev/sda5: LABEL="TC3TEST" UUID="6789140d-3ba7-473c-8482-56b96be213f0" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: LABEL="TC4TEST" UUID="370f7985-bd2f-4f46-8e73-4cddc36d624b" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: UUID="9edab6c2-65a6-46db-81ab-96ed98c46c83" TYPE="ext2"
/dev/sdb3: UUID="ff319800-2bb5-4f06-a98b-b039135e1b16" TYPE="ext2"
/dev/sdb5: UUID="cb8b05d1-b8c6-4d15-87c3-bdb9a0097468" TYPE="ext2"
/dev/sdb6: UUID="3407FD0E1A577308" TYPE="ntfs"
/dev/sdb7: UUID="4471b471-2327-494a-9744-2cf400eebc6d" TYPE="ext2"
tc@box:~$