Tiny Core Base > piCore Test Releases
piCore-5.1.rc4
bmarkus:
piCore-5.1.rc4 is available for testing. Changes:
* BusyBox updated to 1.22.0
* added resize2fs
Image comes with preinstalled openssh, mc and usbutils. sshd starts automatically so it is ready for headles operation out of box:
login: tc, password: piCore
For fast boot there are preinstalled ssh keys. You can regenererate them if you whish any time.
Applications are installed in /mnt/mmcblk0p1/tce Do not use it to install additional packages, it is small and FAT partition. If you want to use it not only for debugging, craeate an ext4 partion on the remaining part of your SD card with fdisk, move /mnt/mmcblk0p1/tce there and reboot. It will be used automatically. I advice to have a minimum of 512M size for second partition. You can create a swap partition too.
If you have an issue with a not working USB keyboard or mouse (or anything else), plese post output of
- dmesg
- lsusb
- lsmod
- uname -a
- version
Download link: piCore-5.1.rc4 md5
Gerrelt:
Hi bmarkus,
First: thanks again for this new release, I am very happy with the pre-installed openssh!! 8) 8)
But, I do encounter a problem during install.
I burned the image to the SD card and started the raspberry while connected to a (wired) network.
Next I connect succesfully to it from my PC over SSH using Putty (woohoo 8) ).
Then I create a new second partition and format it.
After that I want to move the tce directory to the new partition, and I use these commands for it:
--- Code: ---tc@box:~$ sudo mv /mnt/mmcblk0p1/tce /mnt/mmcblk0p2
tc@box:~$ filetool.sh -b
tc@box:~$ ls /mnt/mmcblk0p2
tce/
tc@box:~$ sudo reboot;
--- End code ---
But after this, I cannot connect anymore to the raspberry with ssh. If I connect a TV and keyboard to it, it still works, but openssh seems to be gone?
Am I doing something wrong?
Greetings,
Gerrelt.
bmarkus:
Looks like /mnt/mmcblk0p2 not mounted (no lost+found directory listed by ls). Most likely you moved /mnt/mmcblk0p1/tce to RAM.
filetool.sh is not needed as nothing to mackup at the moment, just relocating tce dir which is location independent. Even it makes things worst, as tce already moved but system still think it is at the old location. Right procedure:
create new Linux type (ID 83, default) primary 2 partition with fdisk and reboot to make sure kernel is using the new partition table. After reboot:
--- Code: ---sudo su
mkfs.ext4 /dev/mmcbl0p2
rebuildfstab
mount /mnt/mmcblk0p2
mv /mnt/mmcblk0p1/tce /mnt/mmcblk0p2
reboot
--- End code ---
Before reboot check that tce is really copied to the card. mc (Midnight Commander) may be more convenient to copy and view content.
Gerrelt:
Yes, thanx, that worked! :)
Previously I didn't have to do the rebuildfstab and mount. I guess this was done automatically by the tce-setdrive command?
I will continue my install now.
EDIT: btw, thanx for the midnight commander tip, didn't know that one yet. Very handy.
Mithotyn:
Hi Bela,
many thanks for this release!! It makes everything very easy to me. My Logitech Keyboard is working now and with SSH/Putty i can configure my box easygoing from the couch.
I can confirm that copying tce to a second partition works like a charm.
Greetings
Joachim
Navigation
[0] Message Index
[#] Next page
Go to full version