WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 ... 8 9 [10]
Extension requests / Re: minicom
« Last post by valuequest on October 03, 2015, 03:13:39 PM »
I appreciate your prompt response nitram! I would like to test drive the compilation you've done if you wouldn't mind sending me a link. Thanks!
Extension requests / Re: minicom
« Last post by nitram on October 03, 2015, 02:36:54 PM »
Hi valuequest.

I was able to compile latest minocom v2.7 no problem, just needs ncurses-dev.tcz during compile. Would you like to try compiling yourself or would you like me to PM you a link so you can test drive the extension?

Welcome to minicom 2.7

Compiled on Oct  3 2015, 16:32:43.
Port /dev/ttyS1, 15:35:01

Press CTRL-A Z for help on special keys

Extension requests / Re: ClamAV 0.98.7
« Last post by roborob on October 03, 2015, 01:16:41 PM »
Very nice.  Thank you.
Raspberry Pi / Re: building a IQaudIO rotary encoder control
« Last post by squeezypeas on October 03, 2015, 12:14:17 PM »
It's working again but if a soft min and/or max is set then the initial volume is relative to the soft values and not the hard values. The executable is in github (https://github.com/alidaf/raspberryPi.git), which can be run from the command line if anyone wants to use it until I can get the packaging sorted. Run sudo ./rotencvol -? to get a list of all of the command line options.
Raspberry Pi / Re: Step by step guide to building a package.
« Last post by squeezypeas on October 03, 2015, 12:10:42 PM »
Thanks. That will help a lot.
Extension requests / minicom
« Last post by valuequest on October 03, 2015, 11:26:38 AM »
Can someone please package minicom for /tinycorelinux/6.x/x86/ ?
Raspberry Pi / Re: Step by step guide to building a package.
« Last post by Rich on October 03, 2015, 09:54:38 AM »
Hi squeezypeas
Are the EXPORT flags commands to be typed into the console or entered into a config file?
They can be entered at the command line if you wish.
Can't I just compile with gcc and set flags on the command line?
If so, do I still need to make, and how?
Is /tmp the assumed compilation folder?
It often is used for compilation, but you could use a subdirectory under  /home/tc.
In “mkdir -p /tmp/package/usr/local/tce.installed”, is tce-installed an assumed name for something?
No, that's the actual name of the subdirectory. If your package requires a startup script, place it in that subdirectory.
The script should have the same name as the package without the  .tcz  suffix. If you don't require a startup script,
place an empty file there with the same name as the package without the  .tcz  suffix.

The compiletc extension is deprecated.
No, that's what the build package is called under X86. Under PI it was named compile-essentials.
Should I add a version number to the executable/package?
Version information should be listed in the  .info  file and be accessible by the program itself.

    [EDIT]: Crossed out incorrect statement.  Rich
Raspberry Pi / Trouble getting resize2fs to work correctly.
« Last post by neophyte on October 03, 2015, 09:21:02 AM »

I've been following the instructions in the README file and run into an issue. I've resized my second partition, mmcblk0p2, to the full size of the card but resize2fs isn't resizing it up to that size.

 Before resizing, the partition started on cylinder 49152 and ended on 104447. The df utility says that there is 25.1 megabytes total for this partition. I followed the instructions and used fdisk to delete the second partition and recreate another primary partition on cylinder 49152 and ended it on cylinder 30898175 which is as large as you can get on this microSD card. I rebooted and went to resize the filesystem. After running resize2fs on mmcblk0p2 I get a total size of 30.1 megabytes, far short of the roughly 16 gigs of space on this card.

I've checked fdisk again and it says that the partition is still definitely ending on cylinder 30898175. I've checked dmesg and it says:
Code: [Select]
EXT4-fs (mmcblk0p2): resizing filesystem from 27648 to 15424512 blocks
[   69.404444] ------------[ cut here ]------------
[   69.404526] WARNING: CPU: 0 PID: 2481 at fs/jbd2/transaction.c:269 start_this_handle+0x5f0/0x694()
[   69.404543] Modules linked in: i2c_dev spi_bcm2708 i2c_bcm2708 evdev uio_pdrv_genirq uio
[   69.404597] CPU: 0 PID: 2481 Comm: resize2fs Not tainted 3.18.10-piCore+ #1
[   69.404665] [<c001550c>] (unwind_backtrace) from [<c00129e8>] (show_stack+0x20/0x24)
[   69.404765] [<c00129e8>] (show_stack) from [<c0564bbc>] (dump_stack+0x20/0x28)
[   69.404809] [<c0564bbc>] (dump_stack) from [<c0023150>] (warn_slowpath_common+0x7c/0x9c)
[   69.404847] [<c0023150>] (warn_slowpath_common) from [<c002322c>] (warn_slowpath_null+0x2c/0x34)
[   69.404882] [<c002322c>] (warn_slowpath_null) from [<c0211320>] (start_this_handle+0x5f0/0x694)
[   69.404917] [<c0211320>] (start_this_handle) from [<c02117f0>] (jbd2__journal_start+0xf8/0x20c)
[   69.404969] [<c02117f0>] (jbd2__journal_start) from [<c01f7cd4>] (__ext4_journal_start_sb+0x68/0xf8)
[   69.405073] [<c01f7cd4>] (__ext4_journal_start_sb) from [<c01eb7b4>] (ext4_flex_group_add+0x550/0x1b44)
[   69.405149] [<c01eb7b4>] (ext4_flex_group_add) from [<c01ee1dc>] (ext4_resize_fs+0x8f4/0xf88)
[   69.405185] [<c01ee1dc>] (ext4_resize_fs) from [<c01d14b4>] (ext4_ioctl+0x128/0x10a8)
[   69.405222] [<c01d14b4>] (ext4_ioctl) from [<c0150868>] (do_vfs_ioctl+0x40c/0x5e4)
[   69.405251] [<c0150868>] (do_vfs_ioctl) from [<c0150a84>] (SyS_ioctl+0x44/0x6c)
[   69.405284] [<c0150a84>] (SyS_ioctl) from [<c000eb60>] (ret_fast_syscall+0x0/0x48)
[   69.405301] ---[ end trace d5c64d244b071e6f ]---
[   69.405319] JBD2: resize2fs wants too many credits (155 > 128)
[   69.405352] EXT4-fs (mmcblk0p2): resized filesystem to 15424512

Not really sure where to go from here. I'm on the version 6.1-X image. Using an old Raspberry pi Model B+.
General TC Talk / Re: undefined reference to in time.h functions
« Last post by blackdiamond on October 03, 2015, 08:58:49 AM »
Thanks !!!

I will test it next monday, we use tiny core for magnetic ticket encoding using a shaft encoder, the resolution of the encoder is well to record the ticket, but for reading we want to use time comparision with nanoseconds measuring.

Tiny core is the platform we use on Automatic Fare Collection Equipment we renew in my job ....

dCore X86 / Re: latest jessie dcore
« Last post by cast-fish on October 03, 2015, 07:27:57 AM »
OK  will try that....

thanks Jason

Pages: 1 ... 8 9 [10]