Off-Topic > Off-Topic - Tiny Core Lounge

Tiny core on Eden ulv 500MHz cpu

<< < (3/6) > >>

WombatCrew:
When transitioning from Damn Small Linux to Tiny Core make sure all necessary libraries are available. Try using tools like tc-install for managing applications. You might also consider installing aditional extensions that could assist in the migration ;)

Stefann:
Thanks,
Yes I make sure to have all libraries
the transition is basically a brand-new OS install and brand-new application install, no re-use of the dsl-applications but all from the tc apps browser
By now I have it running on my second test system:
tiny core,
vnc, ssh, samba, apache, php, gcc, libusb: all standard from the apps browser
Getting it to work meant "editing the configuration files" and making sure they are persistent using the .filetool.lst file.
I lso was able to compile and test my application and it succeeded to compile and run on my test system, still without I/O.
I also was able to boot the target system with a Tinycore USB so that is confirmed as well.
Next step will be to test the application on the target system,. That will likely be next weekend.

Leee:
I'm curious to hear how it works out.

Stefann:
Holy moly…….. it works!

I’m not surprised I got it to work.
I AM surprised how easy that went.

Basically…
- I had to navigate my way on getting tiny core and all packages to work on my “development station”, a used 10euro hp t510 thin client. Nothing very difficult but as it’s my first journey into tiny core “some growing pains”.
- biggest pain was actually to get my 1st bootable tiny core usb. I had to manually get the syslinux bootloader on it which was difficult as I had to do that with my old damn small Linux that refused to do the newer syslinux versions. I had to select a “half way” version of syslinux to get it to work.
Once I had the 1st crippled tinycore functioning I used the internal tool to create  non compromised  bootable  tiny core USB’s. That was easy peasie.
- I was able to compile my application. The biggest challenge was that I use some pretty low level code that works with both libusb (via compact library) and libusb-1.0. This is not ideal but unless I rewrite my x10 drivers I have no way of leaving the old libusb.
- tested the compiled program on the hp510 which nicely worked, but all I/O still disabled as that is connected to my target machine.

Then today…
- I got everything on a bootable usb
- and booted the target machine.
Bang… worked at 1st try.

So…
- I had compiled the program on the hp510 which is a dual core 1G Eden 64bit cpu, on which I had put the 32bit tinycore.
- not only had I created a bootable usb with tinycore on that. I also had compiled my application on that.
- tinycore worked at 1st try
- application worked at 1st try without recompilation on the 500MHz single core 32bit machine.
- usb drivers for 1wire network and x10 gateway functional at 1st try. Application running at 1st try.

Wow… as said… I definitely had expected to get this to work. But not as smooth as this.

Only inconvenience I currently have is that the target device ignores the bootorder settings from the bios. I did set it to “usb first”, but it ignores that. I have to completely disable boot from internal drive (to disallow the baseline damn small Linux to boot) to het tiny core booting from usb.
The inconvenience is that this requires to hookup monitor and keyboard which is inconvenient as the computer is in  a crammed utility area.

Any advice is welcome but I can live with it.
It now works. I will let it run for a few days. Than load all to the internal drive so will need to hookup monitor/keyboard one more time to re-enable boot from internal drive.

Cool!

And many thanks to especially @Rich for helping me through.

Stefann:
A,
No need to help me…

I guess running fdisk on the active disk and toggle the bootflag with the “a” command will make the active disk non-bootable and will at next boot start at the other disk.

A bit risky if you have only 1 computer but as I have my hp t510 to create bootable usb drives I can always get back to live.

Did not test this yet but I think it will work. And if not I need to hook on monitor/keyboard.

Note: I never knew “a” was a toggle. I so far used it only to “set” the bootflag.

Navigation

[0] Message Index

[#] Next page

[*] Previous page