Recent Posts

1

Extension requests / Re: REQUEST me-tv for TC 9.x86

« Last post by Juanito on Today at 12:46:47 AM »

There is an uptodate version of me-tv here:

https://github.com/Me-TV/Me-TV/releases

..however, it looks like it needs cargo/rust to compile.

2

Extension requests / Re: Request for XFig

« Last post by Juanito on December 09, 2018, 11:02:01 PM »

posted in tc-9.x x86 repo

3

TCB Talk / Re: tinycore => mulinux => android ?

« Last post by Juanito on December 09, 2018, 10:56:14 PM »

tce-load -wil extension_name

4

TCB Talk / Re: tinycore => mulinux => android ?

« Last post by labeas on December 09, 2018, 09:42:40 PM »

Remind me again how to D/L individual packages?
When I go to <core> Download, it only lists the full installation/S.

 Sorry.

5

TCB Talk / Re: tinycore => mulinux => android ?

« Last post by labeas on December 09, 2018, 08:59:32 PM »

Thanks, that boots core, which writes <bad chars> at the end
of its <boot trace>; which <bad char mode> I clear/reset with
 `reset`.

Also working is more difficult than I anticipated;
 even with the brilliant e3 editor from Mulinux.
I've long claimed that gpm is the most powerful tool;
 but installing Mul's gpm [first copy it's libs to /lib]
 leads to </dev/mouse not found>; although these days,
 including for TC64 my gpm uses /dev/psaux.
I vaguely remember, years ago, having to create a /dev/*
 with a short command. Now I'm suspecting that the gpm
 installation must create the /dev/psaux for gpm to use?
 So then installing Mul's-gpm to core isn't just copying
the binary and libs? My whole idea of grafting Mul's
code [admittedly, mostly ash-scripts] onto core is perhaps
not viable.

What ideas about gpm & /dev/psaux ?

I've just realised that my aim is to have access to some of
the smart/novel facilities of Mulinux [mostly ash scripts];
so there's no good reason NOT to install/use core's gpm.
But I needed to write this text to clear my rusty brain;
even after "sleeping over it".

Still I'm interested in the theory re. </dev/mouse not found>.

6

General dCore Talk / Re: Trying to boot from iso dCorePlus-bionic

« Last post by Jason W on December 09, 2018, 05:42:15 PM »

I have added this info to the wiki under "What are the recommended system requirements?"

http://wiki.tinycorelinux.net/dcore:faq  -- 

dCorePlus images require at least 1GB of RAM to boot and run as they have all available hardware support and the X window system designed for new users to be able to boot and access a wireless network and install dCore in a graphical environment.

7

Raspberry Pi / Re: Python 3 cant find RPi.GPIO

« Last post by Rich on December 09, 2018, 05:02:48 PM »

Hi johnwmcc
According to:
http://tinycorelinux.net/9.x/armv6/tcz/python-RPi.GPIO.tcz.list
that extension contains:

Code: [Select]

usr/local/lib/python2.7/site-packages/RPi.GPIO-0.6.2-py2.7.egg-info
usr/local/lib/python2.7/site-packages/RPi/_GPIO.so
usr/local/lib/python2.7/site-packages/RPi/GPIO/__init__.py
usr/local/lib/python2.7/site-packages/RPi/__init__.pyIs it possible python3 doesn't know to look under  /usr/local/lib/python2.7/  ?

8

Raspberry Pi / Python 3 cant find RPi.GPIO

« Last post by johnwmcc on December 09, 2018, 04:50:24 PM »

After a lot of hassle, i've installed piCore 9.03 on an RPi Zero W, got it to reboot and run WiFi, SSH, a desktop, python3.6, and x11vnc.

I've got onboot.lst to run these of modules on startup.


I've hit a number of roadblocks, which use of Google has mostly (eventually) resolved. Unfortunately, most of the instructions I found for installing piCore on Pi Zero W are incomplete or even inconsistent, but eventually I figured things out and have got most of what I want to do to work.

But I'm stuck, and can't find an answer using Google. I can load python3.6 (using sudo - naughty, I know, but it won't run the IDLE IDE unless I do that). At the python prompt, I get the IDE to run using
>>> import idlelib.idle


I've also run in a terminal the commandtce-load -iw python-RPi.GPIO to install the GPIO module, and put that in onboot.lst too. And if I run it a second time, it tells me it's already loaded.

But python can't find it. A python program using import RPi.GPIO fails, and creates an error.

Using Midnight Commander to search the mounted filesystem can find no file corresponding to a file search pattern of *RPi.GPIO* except .tcz files in tce/optional, anywhere.

What can I do to get GPIO to work in python3?

Is my problem to do with running python with sudo? If so, how do I get IDLE to work without that?

Any help would be welcome. At the moment I'm completely stuck.

9

Tiny Core Netbooks / Re: downloading tiny core with wireless

« Last post by coreplayer2 on December 09, 2018, 04:00:36 PM »

Hi!
I try to turn on wi-fi in tinycore plus 9, but after starting firmware-getB43 I see in the terminal:
Loading Dependencies
squashfs-tools installed
b43-fwcutter installed
Downloading Broadcom driver...
wget: bad address 'www.lwfinger.com'
Error: Downloading source. Exiting.

What is this driver that I can’t download because I don’t have a network connection?
Why it can not be included in the distribution?
I don’t understand why core plus it doesn’t work not only out of the box, but even after manual loading!

The error is generated because the firmware installer cannot connect and retrieve the source.

Broadcom do not allow their firmware to be distributed.  So, they expect you to initially download their firmware via an Ethernet connection. Thereafter your wireless connection should function as expected.
For older WiFi devices you might manage with one of the other available firmware’s

For the best support use firmware_getb43 extension over an Ethernet connection by any means possible

Good luck




Sent from my iPhone using Tapatalk

10

Tiny Core Netbooks / Re: downloading tiny core with wireless

« Last post by Rich on December 09, 2018, 11:32:31 AM »

Hi lt.columbo

... What is this driver that I can’t download because I don’t have a network connection? ...

The driver is probably located at  www.lwfinger.com/b43-firmware.

... Why it can not be included in the distribution? ...

Some companies don't allow their firmware to be distributed by third parties.