WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 ... 8 9 [10]
91
Corepure64 / Re: VT needs gpm.
« Last post by labeas on February 13, 2017, 02:11:05 AM »
OK, If WiFi works: the BIG gcc can be fetched, to be able to run gpm.

But judging from net-posts re. <Linux setup WiFi> I expect big problems there.
Which surprised me since it's so automatic under M$.
92
Corepure64 / Re: Need WiFi connection.
« Last post by labeas on February 13, 2017, 02:05:42 AM »
Notaion:--------
-> : Keyin to system
== : resulting output from system
=> : extra observations/ideas related to above in/out function
<...> : not verbatim/pasted text

]]What are commands to test & use WiFi ?

]]So far `ping <IPs>` fails.
...

] Yes the Wifi icon?  click on it

Of course I did that: it opens a <sudo labeled TextFrame> which
disapears when a char is keyed into it.

]r as explained eirlier..
]
]ode: [Select]
]sudo wifi.sh
]from a command prompt

-> sudo wifi.sh == <no device found>
=> must go back to M$ to see if WiFi <router> is still <enabled>.

 It goes <off> regularly; not under my control.
 I stopped on the way at 32-bit-Debian7 very slow USBstik, and
when I got to M$: its WiFi is/was working.

] then select from a suitable access point.
---------------------------
PS. I posted the following on NNTP:--
Re. 64-bit wily: I'm can't d/l [& install] with my.
 [very slow USBstik based] debian7 which is 32-bit; and the TinyCore64
 where I want it installed has no inet-connection yet.

 If I had the 64-bit binaries, I could perhaps just copy them to TC,
 like I've migrated 32-bit wily to several installations.

 Does Debian make the binaries available?

93
TCB Talk / Re: TCL Repository file listing
« Last post by centralware on February 13, 2017, 02:05:05 AM »
Goes to show what I know! :)
I was just scripting a new repo checker (to compare md5/info files) and went by what's within.
http://tinycorelinux.net/8.x/x86/tcz/
94
Programming & Scripting - Unofficial / Re: depfinder: script to find dependencies
« Last post by centralware on February 13, 2017, 02:03:19 AM »
@halma:
-b should default to the running version as opposed to assuming x86_64 (ie: uname -m)
-v I assume is the repo version; this should not be hard-coded to "6" but in fact can easily be scripted
Code: [Select]
$ version
8.1.5
For older TCL look in the share/doc/tc folder for the release text file to get the version number.
95
TCB Talk / Re: TCL Repository file listing
« Last post by Misalf on February 13, 2017, 02:02:08 AM »
x86 isn't at version 8.x yet.
96
TCB Talk / Re: TCL Repository file listing
« Last post by coreplayer2 on February 13, 2017, 01:55:26 AM »
http://tinycorelinux.net/8.x/x86/tcz/info.lst
Might be a glitch or possibly intentional...  don't know...
Try
http://tinycorelinux.net/7.x/x86/tcz/

At present, there is no 8.x repo for x86
97
Raspberry Pi / Re: USB gadget kernel module with RPi zero
« Last post by johannkraus on February 13, 2017, 01:55:23 AM »
Okay, I think I've resolved the dependencies but still I can't load the module with the same error. Do I have to manually specify all the parameters listed by `modinfo` to the kernel module?

Just to be curious: What happens if you load g_multi? I just tried to modprobe g_ether and got a "No such device error". But g_multi works on my Pi.

According to this site (http://trac.gateworks.com/wiki/linux/OTG) there seem to be alternative modes for ethernet:
- cdc eem
- rndis

This might be switched in g_ether via use_eem parameter (but probably only when compiled with support - and I was not able to switch).

From dmesg I don't see which one (rndis / eem) is used with g_multi. But my host tells me:
[1210370.212087] cdc_acm 1-4:1.2: ttyACM0: USB ACM device
[1210370.212363] usbcore: registered new interface driver cdc_acm
[1210370.212365] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[1210370.287192] usbcore: registered new interface driver cdc_ether
[1210370.293888] rndis_host 1-4:1.0 usb0: register 'rndis_host' at usb-0000:00:1a.7-4, RNDIS device, 12:88:92:94:83:ca
[1210370.293911] usbcore: registered new interface driver rndis_host
[1210370.317397] usbcore: registered new interface driver rndis_wlan
[1210370.319988] rndis_host 1-4:1.0 enp0s26f7u4: renamed from usb0
98
TCB Talk / Re: TCL Repository file listing
« Last post by centralware on February 13, 2017, 01:49:05 AM »
http://tinycorelinux.net/8.x/x86/tcz/info.lst
Might be a glitch or possibly intentional...  don't know...
99
Raspberry Pi / Re: tce-load replacement potential
« Last post by centralware on February 13, 2017, 01:47:39 AM »
@curaga: lol...  yes, at the kernel's build time :)
Thank you for the x64 processor flag (God forbid we ever see/hear about an 80x86/128bit :) )
Thank God I don't have to get a list of all of the processor flags for the past 35 years!!

And to think...
The first IBM PCs (and eventually their "Compatibles") were built around an 8088, or "XT" processor.  Eight whopping bits and a handful of memory running at a few MHz if you were lucky.  Hard drive?  Universal Serial What?  LOL...  this heavy-weight (steel enclosure) computer like the IBM 5150 came to exist about the same time the Audio CD was invented...  can't say for sure which was more powerful at the time!

The next generation was the 8086 processor with its overwhelming...  oh wait... it's just a faster XT.

The 80286 processor was the true paving of the future (and most all flaws that existed with this architecture have been replicated for thirty years now! :) )  Sixteen bits which opened the door to more memory addressing, a dual IRQ chip and more times than not, the need for an RTC. Anyone still have some old ISA expansion cards...  for nostalgia, maybe?

Adventure and technical improvements have climbed the 80#86 ladder over the years, but one would think we'd be in the double-digits by now considering it's been years (early 1980s) since the 286/287's were common-place.
100
TCB Talk / Re: TCL Repository file listing
« Last post by Misalf on February 13, 2017, 01:28:39 AM »
Pages: 1 ... 8 9 [10]