WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
1
Raspberry Pi / Re: Help Starting RPi0 Headless
« Last post by Juanito on Today at 01:32:32 AM »
I don't have an RPi0 to test, but I suggest the first thing to do would be to make an extension out of the missing gadget kernel modules - you should find them here:

http://www.tinycorelinux.net/9.x/armv6/releases/RPi/src/kernel/4.9.22-piCore_modules.tar.xz
2
You have a third option, framebuffer and Xfbdev. Please see the FAQ for samples of the vga= bootcode.
3
Raspberry Pi / Re: Copy2fs.lst
« Last post by vladosam on February 22, 2018, 11:15:28 PM »
Ok. Thanks for the info. Have a nice day. :)
4
Raspberry Pi / Re: Copy2fs.lst
« Last post by bmarkus on February 22, 2018, 11:10:13 PM »
Is copy2fs.lst gone forever in piCore?
In this post they mention it will be reintroduced in next release.
http://forum.tinycorelinux.net/index.php/topic,19578.msg121189.html#msg121189

It will come at a later time.
5
Raspberry Pi / Help Starting RPi0 Headless
« Last post by profhuster on February 22, 2018, 05:51:43 PM »
I am looking for a tutorial.

I have used linux a lot, but never dug into boot configurations, etc., and I am new to TCL. I want to set an RPi0 up as a standalone data logger that students can set up, then after a week plug it into a laptop and download the data. I can handle the programming so it would start or resume at power up and log the data to the microSD card. I need 20 of these units, so to keep it cheap I thought a $5 RPi0 + $3 card + $10 i2c interface board would be a good solution.

So, I think the solution is a RPi0 that operates in the gadget mode. When it is plugged into a laptop I could log in with Putty from Windows or Terminal -> ssh from a Mac or Linux machine.

The problem I am having is setting up and programming the RPi0 to start with. I am having trouble following instructions from http://forum.tinycorelinux.net/index.php/topic,20195.0.html, for example because I don't know how to do several of the things they mention. For example in the first post in the thread:

* _trying modprobe dwc2_ I can't figure out where this command goes. In a start up shell file? Which one?
* _I copied dwc2 and the gadget modules to lib/modules/.../usb and also copied modules.dep_ What is this about? And I can't find the _gadget_ module.
* I don't see how to _modprobe dwc2_ because I can't get the RPi0 booted and connected.

I have successfully got Raspian Jessie working by following directions like these: https://gist.github.com/gbaman/975e2db164b3ca2b51ae11e45e8fd40a

But I am stumped with TCL. I can burn the zip, then edit files on it on a mac before plugging it into the RPi0, but I need more help. Step by step. I've looked through the book. Maybe I'm in over my head.

Any help would be appreciated/
6
TCB Q&A Forum / Re: Solution!
« Last post by HeartOfGermany on February 22, 2018, 01:11:30 PM »
Solution - if anyone ever has the same problem:


to the shell just add a sleep timer (mine is 30s which is plenty!) and than sudo mount....

The problem seems, that the RAID is not ready to mount, when the command is run - just let the system boot up a few more secounds and it will/should work!

Good luck to everyone.


BTW: Read-speed on average is about 30-35MB/s and write is on average 25mb/s. Since the CPU is not at 100% and RAM is only 100/500, it seems the PCI add-in-card slows down the whole raid - so if you expect performance, stick to PCIe if possible. A single PCIe lane is much faster than that!


Guys, have a nice day! And still thanks.  ;)
7
TCB Talk / Tiny Core 8 with Intel HD Graphics 500 on Intel Atom E3930 CPU
« Last post by dspence on February 22, 2018, 12:50:41 PM »
Hi all,

I'm having trouble getting Tiny Core 8 to work on a new machine that has an Intel Atom E3930 CPU, with integrated HD Graphics 500.  lspci identifies the graphics as "Intel Corporation Device 5a85 (rev 0b)".

I want to run Xvesa on it, but it reports "Interrupt pointer (seg d0 off 20) doesn't point at ROM" four times, before reporting "Fatal server error: no screens found", followed by a segmentation fault.

I have also tried Xorg.  I installed that with libva-intel-driver.tcz, xf86-video-intel.tcz, and also firmware-i915.tcz, and from /var/log/messages and /var/log/Xorg.0.log, it looked like it was working, but I only had a black screen.

Xvesa is really the one I want to have working, though.

Has anyone managed to get Tiny Core 8 to work with graphics on this chip?  Any help would be appreciated.

Thanks.
8
TCB Q&A Forum / Re: MDADM with TinyCore - system hangs
« Last post by HeartOfGermany on February 22, 2018, 10:40:31 AM »
Yes, it is a bit chaotic. Definitely!

It gets written to the RAID and the CF? Wow, did not think about that.


I guess the problem is, that the system mounts the home directory to the CF first on bootup and than the raid - so how do I stop the system from mounting the user "nas" to the CF, instead only to the RAID?

I mean, I guess it does not matter, where I mount my RAID - all files will be mounted to the CF. Is there some sort of exclusion list or so?



Edit:

Ok life sucks...

I manually ran the command "sudo mount /dev/md0p1 /home/nas/raid and it properly worked! I found out, that the RAID did not mount properly on bootup - the folder did show as a drive, but it was not working as a drive. Going on with troubleshooting... man I hate it, if it does not work as it is supposed to work.
9
TCB Q&A Forum / Re: MDADM with TinyCore - system hangs
« Last post by curaga on February 22, 2018, 10:25:53 AM »
Maybe something in your samba config has a wrong dir, and so the files went to RAM? edit: I see you backed up /home/nas/raid! That means everything gets saved to both your RAID and your 512mb CF.

Also, your setup between bootlocal and bootsync is quite curious, competing mount and password commands. Those should be in one file only.
10
Doesn't Vim already do this?
Well yes, vim already do this, and there are tons of similar programs out there that do the same.

The real fun of this project is the understanding of C/C++ and coming up a way to parse the shell syntax.

The thrill of segmentation fault and stackoverflow sure helps a lot in my learning curve.  :P

Besides, the binary size is 32K (on TC64) while vim.tcz is 1.3M

Why would I load a fat extension along with its dependencies when I can use a small one instead ?

Quote
Are the editor commands going to be compatible with vi or something else?
Well, I've never thought about that.

What's in your mind ?

Care to share an example ?
Pages: [1] 2 3 ... 10