WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
I know you don't want X in the mix, but having our lightweight Xvesa or Xfbdev in between will help with those colorspace and fullscreen issues.
I'll try. I had them installed two days ago but someone had told me I need not them. Someone else even told that he could play video with no even graphics.KERNEL, using only alsa-config and mplayer in onboot.lst, but I could never do the same, I mean, make my mplayer work with fbdev without graphics.tcz.
22
TCE Q&A Forum / Re: How to setup cyrilic fonts?
« Last post by Scampada on Today at 03:22:37 AM »
Hi there one more time, yet in another thread. I've read it and tried to reproduce all actions needed to set cyrillic keymap (I need no locale, just want to be able to type in Ukrainian). So I have:
1. installed kmaps.tcz
2. made sudo loadkmap < /usr/share/kmap/qwerty/ua (in various combinations) [.kmap]
3. then sudo loadfont < /home/tc/console-fonts/pfs/ (various combinations of UniCyr, Cyr, etc.) [.psf]
4. Nothing happened except of that I could type plenty of ?????????? in the CLI. Then I tried to load yet another font from the folder above and started typing with blank symbols.
5. I tried to do it in reverse, that is, first I made loadfont and then loadkmap and gained no profit again.

I'm using pure CLI with graphics.KERNEL.

What's wrong?
23
dCore X86 / Re: wifi and dCore...
« Last post by Jason W on Today at 03:07:28 AM »
Ok.  It seems to be how the programs are interacting and not something I can control from my end.  Probably the same behavior between links and wifi is seen in Core.
24
dCore X86 / Re: wifi and dCore...
« Last post by sbaguz on Today at 01:45:20 AM »
Not only that one: from that moment on, even rebooting, I haven't been able to use wifi script anymore in any terminal session...
To solve this issue I basically had to make a new install and to avoid changing language in Links2.
I suppose it would have been the same simply deleting .links folder in my home/tc.
25
TCE Q&A Forum / Re: Installation Problem -- no GUI, no startx.
« Last post by curaga on Today at 01:22:29 AM »
You really do not get the isolinux boot menu when booting a TinyCore cd?

screenshot:


That would be the first I've heard of such.
26
I know you don't want X in the mix, but having our lightweight Xvesa or Xfbdev in between will help with those colorspace and fullscreen issues.
27
dCore X86 / Re: Who is using dCore and why?
« Last post by yoshi314 on Today at 01:05:14 AM »
i use it on an ancient laptop with pata-ssd, so that i don't wear it down too fast. plus, it's fairly lightweight.

other options are thin client environments and general purpose liveusb's.
28
TCB Talk / Re: splash screen feature is enabled ?
« Last post by imaad on March 29, 2015, 11:33:10 PM »
Hi andyj,

It's correctly what you say to use splash screen in another location and not in tc-config, but fbv is closing when the video driver is loaded because the resolution change. For this reason I must to restart fbv. In the other hand it allow to know the percentage of the operating system load.
I have not found another solution to create a splash screen with a minimum modification of the system such as fbv.
29
TCE Q&A Forum / Re: Installation Problem -- no GUI, no startx.
« Last post by Juanito on March 29, 2015, 11:14:56 PM »
So does anyone know how to install TinyCore (15 MB) with its GUI to a USB thumb drive using the command line tools available on a DVD boot of Core (9 MB) which has no GUI? I am sure someone has done this already.

There are many posts in the forums and an explanation in the wiki.

You could use dd to copy the iso directly or fdisk/mke2fs to partition/format the usb stick, grub/grub2/syslinux (assuming you have a wired internet connection to download the extensions) to make the usb stick bootable and then copy the boot files.
30
TCE Q&A Forum / Re: Installation Problem -- no GUI, no startx.
« Last post by coreplayer2 on March 29, 2015, 09:49:57 PM »
I suspect the boot menu to add a waitusb delay is not available in your grub menu.  In this case you'll have to add the boot waitusb option into your grub stanza to make this happen, editing your ISO then burning a new cd should not be too difficult

It doesn't matter how long a delay you add because as soon as the drive has been detected boot will immediately continue

Core boots so fast that I add waitusb=5 to all installs, even hdd's. This saves on troubleshooting


Sent from my iPad using Tapatalk HD
Pages: 1 2 [3] 4 5 ... 10