WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
Raspberry Pi / Re: fbtft
« Last post by nowhinjing on Today at 08:08:45 AM »
thanks, will try this tomorrow...
Raspberry Pi / Re: Trouble getting resize2fs to work correctly.
« Last post by jncl on Today at 07:13:51 AM »
Hi neophyte,

  I subsequently noticed that if you run the command fdisk -lu that the values appear higher as they are being displayed in sectors as opposed to cylinders. So my previous comments about the values being high are irrelevant.

  I successfully built a 6.1-X image and ran the fdisk command but after a reboot I'm unable to resize the second partition, it fails with the message: resize2fs: No space left on device While checking for on-line resizing support and looking at the dmesg output I get a similar set of trace messages to those in your OP.

  I will investigate further and report back.

TCB Q&A Forum / Re: How to add Wbar applications?
« Last post by pjz on Today at 07:02:00 AM »
Someone in IRC says that /home/tc/.wbar will also work.
Raspberry Pi / Re: Trouble getting resize2fs to work correctly.
« Last post by jncl on Today at 05:56:35 AM »
Hi neophyte,

  I've just tried putting the 6.1-X image onto a 16GB MicroSD card and running disk.

  This is the output from the command:
Code: [Select]
The number of cylinders for this disk is set to 486192.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help):
Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
4 heads, 16 sectors/track, 486192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1             129         768       20480   c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/mmcblk0p2             769        1632      27648  83 Linux
Partition 2 does not end on cylinder boundary

Command (m for help): Partition number (1-4):
Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-486192, default 1): Last cylinder or +size or +sizeM or +sizeK (769-486192, default 486192): Using default value 486192

Command (m for help): Command (m for help):
Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
4 heads, 16 sectors/track, 486192 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1             129         768       20480   c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/mmcblk0p2             769      486192    15533568  83 Linux

Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy

Looking at this the ending cylinder is 486192, you said in the OP that your ending cylinder was 30898175, that seems very large to me. You also said that the starting cylinder was 49152 which again seems very high to me as mine is 769.

Can you post the output of fdisk -l /dev/mmcblk0 please?

Raspberry Pi / Re: fbtft
« Last post by jgrulich on Today at 05:05:14 AM »
You need to load the kernel drivers first.

Use these simple script:

Code: (bash) [Select]
echo "dtparam=i2c=on,spi=on
dtoverlay=ads7846,speed=1000000,penirq=17,penirq_pull=2,swapxy=1,xmin=200,xmax=3900,ymin=200,ymax=3900,pmax=255,xohms=60" >> /mnt/mmcblk0p1/config.txt
echo "fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo" >> /mnt/mmcblk0p1/command.txt
echo "modprobe flexfb  width=320  height=480  regwidth=16 init=-1,0xb0,0x0,-1,0x11,-2,250,-1,0x3A,0x55,-1,0xC2,0x44,-1,0xC5,0x00,0x00,0x00,0x00,-1,0xE0,0x0F,0x1F,0x1C,0x0C,0x0F,0x08,0x48,0x98,0x37,0x0A,0x13,0x04,0x11,0x0D,0x00,-1,0xE1,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0xE2,0x0F,0x32,0x2E,0x0B,0x0D,0x05,0x47,0x75,0x37,0x06,0x10,0x03,0x24,0x20,0x00,-1,0x36,0x28,-1,0x11,-1,0x29,-3
modprobe fbtft_device debug=3 rotate=90 name=flexfb speed=16000000 gpios=reset:25,dc:24" >> /opt/bootlocal.sh

Backup, reboot and you'll get the shell on the TFT just after the kernel driver is loaded.
Extension requests / wvdial
« Last post by johand on Today at 04:23:00 AM »
wvdial for armv6 and armv7
TCE Talk / Plan 9 from User Space
« Last post by yiyus on Today at 02:38:13 AM »
I would like to submit plan9port [1] packages for tinycore.

I currently have a package with a script that downloads the latest version (tip, there are no releases), compiles it, and create the corresponding package. I would like to know what is preferred, to include the package with the installer, or to include the generated packages.

On the one side, the script is very small and would require (almost) no maintenance, while the packages would need to be updated with some frequency (but not too much, p9p changes very slowly nowadays). These packages would take much more disk space in the repos (about 70Mb). On the other hand, with the installer package, people would need the compiletc packages (I don't think this is a crazy requirement for potential p9p users) and would have to wait to compile them, which can take a bit long.

In case compiled packages are preferred, then we would have to decide how to split them, if at all. I know the standard here is separating doc and devel packages and so on, but these limits can become fuzzy when talking about p9p. There is some partitioning already defined by p9p, but in fact a user would need to load most of them to do anything. In my opinion, a huge package would be more practical, but it goes against all the tinycore guidelines, so this may be another argument for the script.

What would you suggest? I am more inclined for the installer, but any idea will be appreciated.

[1] https://swtch.com/plan9port/
Sure, such patches are welcome.
(Please, let me know if there is other board better for this topic, I was looking for a "development" board or something like that, but this is the closest I found).

I will assume you are familiar with the filetool.sh script and how it handles permanent storage in tinycore [1].

During the last months, I have been using tinycore with a custom filetool.sh which, instead of tar and gzip, uses zpaq to store the data. zpaq [2] is an incremental backup tool which deduplicates the data before compressing it. It is a journaling archiver, so it allows you not only to keep your data, but also to keep snapshots at different points in time, which I find extremely useful. (I have already submitted a zpaq extension which I hope will arrive at the official repos soon).

I am also working in some plan9port [3] packages (I will talk about this in more detail in another message in the extensions board). One of the tools included in plan9port is venti [4], which also allows to perform incremental backups. I would like to have the possibility of using venti to store my tinycore backups too.

So, I propose to modify filetool.sh and the tools that use it in such a way that the archival system to use becomes an option. I think I will be able to do it without complicating things too much. The configuration for the user will be straightforward (just load the package you want to use) and all the changes will be backward compatible, so it will not affect at all people who just want to continue using their mydata.tgz files.

At this point, I just want to know if there is any interest in these changes and if there is any other backup tool people may want to use in addition to tgz, zpaq and venti. If there is no opposition, I will investigate a bit more and will send a more detailed proposal.

Thanks for reading!

[1] http://wiki.tinycorelinux.net/wiki:backup
[2] http://mattmahoney.net/dc/zpaq.html
[3] https://swtch.com/plan9port/
[4] https://swtch.com/plan9port/man/man1/vac.html
Raspberry Pi / Re: Trouble getting resize2fs to work correctly.
« Last post by neophyte on Today at 01:35:26 AM »
@Greg Erskine

The head and sector are 2 and 8 for the 6.0 image that works. For the 6.1 image that doesn't they are at 4 and 16.


Unfortunately, I don't have any wired internet connection. Only wireless. Unless there is a way to SSH into it via. wireless I can't really try out the test release.
Pages: [1] 2 3 ... 10