Recent Posts

1

Other architectures / Re: Odroid-C1

« Last post by roborob on Today at 09:33:35 PM »

Hi,

When you wrote "compile" I thought you meant via gcc. 

Thanks for the link I had not seen that post yet and I have searched the TC forums for hours.  I have been trying to follow bmarkus's instructions but I am stalled out at the symlink step.  I am writing a bash script to automate the process.  I think the post you pointed to may be enough to get me going again.

regards,
rob

2

TCB Q&A Forum / Re: oopsed bootsync.sh, now won't boot

« Last post by Rich on Today at 09:23:19 PM »

Hi nitram

Thanks Rich it worked great!

How about that, I got it right.

3

Raspberry Pi / Concatenate initramfs on Windows

« Last post by sodface on Today at 08:02:50 PM »

I was goofing around tonight with picore 6.0 and made a small initramfs with just the w1 kernel module tcz in it (~62k).  As an experiment, on my windows laptop I wrote the picore 6.0 image to sd card as usual.  I moved the 6.0.gz file off the card into a directory on my laptop where I had my extra initramfs file (my_initramfs.gz).  Then I renamed 6.0.gz to 6.0.gz.orig and tacked the two together to create a new 6.0.gz:

Code: [Select]

copy /b 6.0.gz.orig + my_initramfs.gz 6.0.gz
Then I moved the 6.0.gz back onto the sd card and inserted into pi and booted... it booted fine and the contents of my_initramfs.gz were in the root file system where expected (I built my_initramfs.gz to extract to /tmp/builtin/optional).

I didn't have to edit any boot files or anything else other than combine the two initramfs files and replace the original.  Not sure what the use case is but I was pleasantly surprised that it worked first try.

4

TCB Q&A Forum / [solved] Re: oopsed bootsync.sh, now won't boot

« Last post by nitram on Today at 07:19:34 PM »

Thanks Rich it worked great!

Wasn't sure if filetool.sh -r would take so after fixing bootsync.sh issued ctrl-alt-del to terminal, startx again to confirm restored/proper setup and shutdown TC with a fresh backup. Learned my lesson and after the reboot promptly made a backup copy of mydata.tgz. Never used an OS that was so simple to backup - no excuses for me now.

marty

5

TCB Talk / Re: Mouse hangs on launching X

« Last post by Rich on Today at 06:10:39 PM »

Hi centralware

fixit app: change the mouse pointer to "wait" and for the next 'x' seconds simply move x+1, y+1 then back a few and so on, then reset the cursor.  If getting elaborate, call for the cursor position and if/when it begins to show the changes, break the loop.  I'm not overly confident on my c++ skills in 'nix else I wouldn'tt even make such a request.

Maybe  xdotool.tcz  is what you are looking for. There's some information about it here:
http://tuxradar.com/content/xdotool-script-your-mouse

6

TCB Q&A Forum / Re: oopsed bootsync.sh, now won't boot

« Last post by Rich on Today at 05:36:42 PM »

Hi nitram
Try booting with  norestore. Then execute:

Code: [Select]

filetool.sh -rwhich should perform a restore and give you access to your  /opt/bootsync.sh.

7

Raspberry Pi / Dual head

« Last post by andyj on Today at 05:11:16 PM »

Does anyone know what I need to do to get dual head working on the Pi? I have an HDMI and a USB display. The HDMI works in console mode only. It did work as the X display on /dev/fb0 until I got the USB display working, and now it goes black when I startx and only the USB display works as /dev/fb1. /dev/fb0 doesn't appear in Xorg.0.log.

8

Raspberry Pi / Re: Camera Module

« Last post by andyj on Today at 05:05:01 PM »

FWIW, I got it working by doing this:

set clipid [open "|raspivid -n -v -h 300 -w 400 -fps 10 -rot 180 -g 2 -sg 1000 -sn 001 -wr 300 -t 0 -pf baseline -o clips/vid%03d.h264 </dev/zero 2>@1"]

Then later I do this:

exec -ignorestderr -- cat $cfilea $cfileb $cfilec | ffmpeg -r 10 -i - -vcodec copy $vidid >/dev/null 2>/dev/null &

once I know which three clips I need. FFmpeg seams like a BFH for just concatenating three files and putting some mp4 information along with them. Is there a lighter faster way?

9

TCB Q&A Forum / oopsed bootsync.sh, now won't boot

« Last post by nitram on Today at 04:22:36 PM »

Playing around with my configuration and i oopsed my /opt/bootsync.sh file.

Tried forum search and didn't see anything - thought this would be a common rookie mistake.

Tried booting with multivt but the system doesn't boot far enough to allow.

Booted with norestore, boots but then of course just get default bootsync.sh file, how to modify my saved version?

Do i need to boot with liveCD, dual boot or norestore option, manually unzip mydata.tgz, fix file, rezip and hope it works? Anyway more elegant?

10

Other architectures / Re: Odroid-C1

« Last post by Paul_123 on Today at 04:17:17 PM »

It's much faster.   the ubuntu image that hardkernel builds boots to a full desktop in about 20 seconds.

Problems.....

Think of the rpi when it was first released.  The drivers are still getting the bugs kinked out.

1- UHS mode doesn't work with most cards, and causes conflicts.
2- Ethernet.  they are still working out the speed issues.  Although it is sort of patched
3- USB has some dropouts.
4- They are still playing around with assigning irq interrupts to the various cores.
5- HDMI does not work well with some monitors, and non HDMI monitors don't work well at all.   I don't have my monitor working with tinycore yet.   I'm using the serial console to monitor the boot process, and then using ssh to connect headless.

But they are fixing and releasing binary updates daily,  And the kernel is available via git.   

If you have the Odroid Ubuntu image running, read the odroid wiki to build the kernel.   You can build the kernel an modules in an hour.    If you have not built an initrd for core yet, then you need on read up on that.  This post is a nice summary. http://forum.tinycorelinux.net/index.php/topic,14634.msg88856.html#msg88856    After you build the initrd, you will also need to run mkimage to wrap the image for uboot. 

Code: [Select]

mkimage -A arm -T ramdisk -C none -d initrd.gz initrd The other trick to uboot is tell uboot to relocate the ramdisk to high memory, otherwise it gets overwritten but he kernel when it decompresses.   Add

Code: [Select]

setenv initrd_high 0xffffffff just before the bootm command.   That step should not be necessary once we can remove enough modules from the initrd to get the ramdisk down in size.