Tiny Core Base > piCore Test Releases
piCore-7.0alpha8
bmarkus:
--- Quote from: Paul_123 on November 21, 2015, 01:39:15 PM ---I typically do an in place upgrade, so my onboot.lst file contains references to KERNEL, rather than specific kernel versions. Extensions with a reference to KERNEL do not load from within onboot.lst
tce-bootload just reports that it is not available. it appears KERNEL is not expanded properly. The odd thing is that it does properly expand references to KERNEL when in the .dep files.
--- End quote ---
Confirmed, it is a bug, thanks for reporting. Will fix in next release.
Paul_123:
--- Quote from: andyj on November 22, 2015, 09:17:28 AM ---Which is faster to set up? Copy2fs clearly reads the whole file into RAM. What about mounting via loop and linking? Does that read through the whole file too or is it clever enough to just read the file system structure from the file and then create the links? How much actual RAM does a loop mounted device use? We would need some really granular timing data.
--- End quote ---
Loading extensions during the boot process is handled with a micropython script tce-bootload. This is already much faster than the old method of loading extensions. Take a look at the file /var/log/tce-bootload
Creating the symbolic links still takes the bulk of the time. If you use copy2fs, it still mounts the extensions, but it copies the files rather than making symlinks.....then it un-mounts the extension. This would definitely take longer.
--- Code: ---Deplist creation for 20 extensions ready: 0s
Mounting 48 extensions ready: 2s
ldconfig return value: 0
depmod return value: 0
Symlinking ready: 6s
Script finished: 6s
--- End code ---
bmarkus:
--- Quote from: andyj on November 13, 2015, 10:30:08 AM ---Upon further research it may be because that option that wasn't compiled in. Where can I find the compile options that have been used for busybox VI? It still seems like it would be easier to port the vim extension.
--- End quote ---
vim.tcz added to 7.x repo.
curaga:
--- Quote from: andyj on November 22, 2015, 09:17:28 AM ---Which is faster to set up? Copy2fs clearly reads the whole file into RAM. What about mounting via loop and linking? Does that read through the whole file too or is it clever enough to just read the file system structure from the file and then create the links? How much actual RAM does a loop mounted device use? We would need some really granular timing data.
--- End quote ---
Read up on squashfs internal structure to find how the data is placed. Symlinking does not read the whole file, but just the directory info (file names, etc.). A single loop mount at our default 4kb blocksize used some tens of kb of RAM.
Gerrelt:
--- Quote from: sbp on November 19, 2015, 01:45:47 AM ---The onboard audio card is now enabled by:
audio=on
in the config.txt
--- End quote ---
Hi Steen,
Yes, that worked! This is wat I did, first mount partition 1, and then open the config.txt :
--- Code: ---sudo mount /dev/mmcblk0p1
sudo nano /mnt/mmcblk0p1/config.txt
--- End code ---
And I then added ",audio=on" to the end of the "dtparam" line. It now looks like this:
--- Code: ---dtparam=i2c=on,spi=on,i2s=on,audio=on
--- End code ---
Thanks.
Greetings,
Gerrelt.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version