Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: Scampada on March 28, 2015, 12:00:34 PM
-
Hi there,
I'm trying to set up as much minimalistic environment as I can to be able to:
1) Play videos with mplayer;
2) Listen to music with mplayer or something;
3) Edit files with vi;
4) Browse Internet with text-based browsers.
I want the core to boot in about 7 seconds, up to 10. The base core do this as quick as 5 secs. (My English may be rather poor.)
The issue is, which modules do I extend the core with to do the trick. I've tried with setting up wifi.tcz, mplayer.tcz, pulseaudio.tcz (dunno if it needed), and some more things but, it didn't work. The first is, mplayer couldn't open fb0; I ls-ed my /dev/ and /dev/fb0 was in there. I tried to add user 'tc' (default one, eh) to 'staff' group (which is named in the output of ls -l /dev/fb0), tried to do sudo mplayer or even sudo su; mplayer, nothing worked. So I decided maybe the base core doesn't work with frame buffer or something eh?
The second is, when I tried to run 'mplayer test.mp3' I've got something like 'couldn't open /dev/dsp: no such file or directory'. I checked it out, indeed there is no such file. I googled and tried to install pulseaudio but it won't work claiming there is no dbus files. I did it rather at a guess.
Well. I can provide more detailed outputs (however it may be complicated task to do). But first I would like to get some theory advices. I know little of how to set up such a minimalistic environment. I can view videos with mplayer using fb in my openSUSE virtual terminals, after the X server's started.
-
Have you loaded Xfbdev.tcz (frame buffer)? I believe you also need Xvesa loaed - someone correct if wrong. Also, the last time i tried the boot code 'vga=788' it was reportedly deprecated and did not work - so this FAQ is likely out of date. Running xsetup.sh will, however, allow you to set resolution.
How to use framebuffer X server?
In order to use framebuffer (Xfbdev) you will need to have a persistent store, e.g., a PPR.
Boot Tiny Core as follows, using an appropriate vga code from the f2 boot help screen and an appropriate disk partition.
boot: tinycore tce=hda1 text vga=788
At the system prompt:
$ tce-load Xfbdev.tce wget install # This is for TC 2.2 and below
$ tce-load -w -i Xfbdev.tcz # This is for TC 2.3 and above
$ xsetup.sh
$ startx
From the X desktop, shutdown with backup. Your Xfbdev X settings will be saved and used on the next boot.
Do not use the text boot code and your framebuffer X server should start successfully.
http://distro.ibiblio.org/tinycorelinux/faq.html#framebuffer
Vi and text browsers should work no problem. Can't comment on mplayer or music. If you use the Apps GUI, just perform an extension search for music or video, etc and see what is available. I believe there was a CLI music player somewhere in the repository (not on TC ATM/can't check).
Edit: Also search old forum posts, example:
http://forum.tinycorelinux.net/index.php?topic=17976.0
-
you'll need alsa or oss loaded to get rid of the /dev/dsp error
-
you'll need alsa or oss loaded to get rid of the /dev/dsp error
But I've got it already! When I tried to 'tce-load -wi alsa' it replied that it was already installed. And mplayer printed something of alsa, and these weren't error messages, I believe...
-
Have you loaded Xfbdev.tcz (frame buffer)? I believe you also need Xvesa loaed - someone correct if wrong. Also, the last time i tried the boot code 'vga=788' it was reportedly deprecated and did not work - so this FAQ is likely out of date. Running xsetup.sh will, however, allow you to set resolution.
Vi and text browsers should work no problem. Can't comment on mplayer or music. If you use the Apps GUI, just perform an extension search for music or video, etc and see what is available. I believe there was a CLI music player somewhere in the repository (not on TC ATM/can't check).
Edit: Also search old forum posts, example:
http://forum.tinycorelinux.net/index.php?topic=17976.0
Aye, I installed Xfbdev with no result; I also tried Xvesa. After installing the Xfbdev I typed 'sudo xsetup.sh' but nothing happened (it said there were not such file).
I have wifi and browsers working fine, yeah; however I had a problem using lynx. It won't work with HTTPS. I have googled that maybe I should install lynx-cur or compile it with --enable-ssl (or something) but how do I do it in TC? When I do 'tce-load lynx', it installs the only one lynx that's in the repo. Links works fine but it hasn't pretty colors as lynx do.
There won't be any problem finding CLI music player; there is no sound for now at all. It's much worse.
I know little of TC repositories, too. Are there many of them?
-
Mplayer works fine with alsa. Make sure you have alsa working. Make sure you read the info files ( the info screen in Apps ).
Mplayer does not work with pulseaudio. For pulseaudio you will need vlc for videos. xmms-pulseaudio works well for audio.
If you do not use pulseaudio, then mplayer and xmms work fine with alsa.
Do not use sudo when running 'xsetup'.
-
If you use the Apps GUI, just perform an extension search for music or video, etc and see what is available.
Nah. I installed the TC manually, with no use of GUI. Just copied vmlinuz and core.tz from iso to my /boot/ partition and booted them with grub2. Then I set up a persistent TCE folder in some way I didn't realized, really. Probably by using the very first 'tce-load -i /mnt/sda9/tinycore/tce/optional/wifi.tcz'.
And now I HAVE NO GUI! And can't make any use of Apps or something. It boot's right into CLI.
-
In addition to alsa.tcz , alsa-config.tcz might also be needed.
-
Core comes with tce-ab a command line apps browser. It also displays the info files.
-
Alsa's installed, I even ran alsamixer and it worked. But I still couldn't test any sound; mplayer complained of /dev/dsp being unavailable.
-
Then I set up a persistent TCE folder in some way I didn't realized, really.
To have a persistent TCE folder, you would either just create a folder at the root of /mnt/sda9 and name it tce (so it will be found automatically), or specify another location via boot code:
tce=/tinycore/tce
Or:
tce=UUID="1234567-8910111234-abcdef..."/tinycore/tce
(including quotes but the UUID is just an example)
Or:
tce=LABEL="YOUR_DRIVE_LABEL"/tinycore/tce
-
Okay thanks, it's clear for me now.
Well, I'll go and test somewhat in TC to get video and sound working... Does the order of modules in onboot.lst matter?
-
No, it cannot mean that. You get ENOENT (No such file or directory) if
the device node doesn't exist in the filesystem. If you see ENODEV (No
such device), then the device node has major/minor number which the
kernel does not recognize as a valid device, i.e. you haven't compiled
in the driver or loaded the module.
Oh, that's it. I see definitely ENODEV error, "No such device", yeah. So..? (Continue reading...)
-
During a fresh install i back up .xsession so it's easy to restore default settings if GUI breaks. Backing up the default onboot.lst is also a good idea.
For alsa on my system, alsa and alsa-config need to be loaded for sound to work.
To confirm what's loaded via CLI, use tce-status -i command.
-
I've tried all as I was advised and still got nothing.
Here are my outputs:
onboot.lst
Xvesa.tcz
Xlibs.tcz
Xfbdev.tcz
wifi.tcz
alsa.tcz
links.tcz
mplayer.tcz
mplayer -vo fbdev Lowrider.avi (errors 2> )
MMX supported but disabled
MMX2 supported but disabled
SSE supported but disabled
SSE2 supported but disabled
Can't open /dev/fb0: No such device
Error opening/initializing the selected video_out (-vo) device.
Unknown/missing audio format -> no sound
Requested audio codec family [vorbis] (afm=libvorbis) not available.
Enable it at compilation.
[AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or directory
[AO_ALSA] alsa-lib: conf.c:3512:(snd_config_hook_load) cannot stat file/directory /usr/local/share/alsa/cards/aliases.conf
[AO_ALSA] alsa-lib: pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.default
[AO_ALSA] Playback open error: No such file or directory
DVB card number must be between 1 and 4
standart outputMPlayer 1.1-4.9.1 (C) 2000-2012 MPlayer Team
Playing Lowrider.avi.
libavformat version 54.6.100 (internal)
AVI file format detected.
[aviheader] Video stream found, -vid 0
[aviheader] Audio stream found, -aid 1
VIDEO: [FMP4] 640x360 24bpp 25.000 fps 350.8 kbps (42.8 kbyte/s)
Clip info:
Software: Lavf52.64.2
Load subtitles in ./
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
libavcodec version 54.23.100 (internal)
ADecoder init failed :(
Opening audio decoder: [tremor] Ogg/Vorbis audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 96.0 kbit/6.80% (ratio: 12000->176400)
Selected audio codec: [tremor] afm: tremor (OggVorbis audio)
==========================================================================
AO: [null] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A: 0.0 (unknown) of 890.6 (14:50.5) ??,?% [J
alsactl init
alsactl: parse:1670: Unable to open file '/usr/local/share/alsa/init/00main': No such file or directory
(there isn't init folder at all)
whether there is dsp
ls: /dev/dsp: No such file or directory
I have dmesg output too, but it exceeds maximum length. And there isn't any obvious clue.
Any idea? What am I doing wrong?
Btw I'd got also something like... er, failed waiting X or something alike after the very booting...
-
During a fresh install i back up .xsession so it's easy to restore default settings if GUI breaks. Backing up the default onboot.lst is also a good idea.
For alsa on my system, alsa and alsa-config need to be loaded for sound to work.
To confirm what's loaded via CLI, use tce-status -i command.
I didn't want to do GUI install... Thought it'll be more complicated and encumbered... So... I just copied the files and boot them...
-
Scampada wrote:
And now I HAVE NO GUI! And can't make any use of Apps or something. It boot's right into CLI.
and later wrote:
I didn't want to do GUI install...
Hmmm...what could have possibly led me to believe your GUI was broken? Just trying to provide a way to fix things. When you mess with Xvesa and fbdev the .xsession file gets overwritten. If you don't want GUI great, but you may want to be a little more precise with your reporting. 'And now I HAVE NO GUI!' to most would imply something broke!
onboot.lst
Quote
Xvesa.tcz
Xlibs.tcz
Xfbdev.tcz
wifi.tcz
alsa.tcz
links.tcz
mplayer.tcz
I've tried all as I was advised and still got nothing.
No you didn't. As was already mentioned twice in this thread, also try loading alsa-config.
This isn't a foot race, stop and breath and read a bit. For newcomers setting up TC is not a 5 minute project. Also read through the manual when you get a chance. It's not a typical distribution.
-
You also need
Xprogs.tcz
aterm.tcz
flwm_topside.tcz ( or some other window manager )
and probably
wbar.tcz
-
Scampada wrote:
And now I HAVE NO GUI! And can't make any use of Apps or something. It boot's right into CLI.
and later wrote:
I didn't want to do GUI install...
Hmmm...what could have possibly led me to believe your GUI was broken? Just trying to provide a way to fix things. When you mess with Xvesa and fbdev the .xsession file gets overwritten. If you don't want GUI great, but you may want to be a little more precise with your reporting. 'And now I HAVE NO GUI!' to most would imply something broke!
Yeah, got it))) indeed, perhaps it was poor wording. I HAVE NO GUI AND I HAVE NO NEED IN IT! I have openSUSE + KDE4 for fancy-shmancy GUI. :)
No you didn't. As was already mentioned twice in this thread, also try loading alsa-config.
This isn't a foot race, stop and breath and read a bit. For newcomers setting up TC is not a 5 minute project. Also read through the manual when you get a chance. It's not a typical distribution.
Ah, well. But doesn't alsa.tcz depend on alsa-config and install it automatically? Hmmm... I checked in the alsa.tcz.dep, it doesn't.
-
You also need
Xprogs.tcz
aterm.tcz
flwm_topside.tcz ( or some other window manager )
and probably
wbar.tcz
Do I need it for working in CLI-only mode? I mean, if I install them, won't it boot right into GUI? OK, I'll try and see.
-
Well, if you are not running X then why do you load Xlibs, Xvesa and Xfbdev ?
I suggest you spend some time reading the book and the wiki.
Random extension loading is not going to work well for you.
-
Well, if you are not running X then why do you load Xlibs, Xvesa and Xfbdev ?
I suggest you spend some time reading the book and the wiki.
Random extension loading is not going to work well for you.
Umm... I don't know. I have read that if I wanna use framebuffer features in Mplayer and Links I kind of must install Xfbdev.
-
But what should I read in the Wiki, I can't even find something like 'frame buffer' article.
-
My .xsession is not rewritten because I still have no /home directory working in proper way. I use boot code -home=LABEL="grub"/tinycore/home but it gives me an error like "Wrong disk" and continue booting without HOME
-
- You cannot setup a sub-directory to be home. You can only specify a drive.
- alsa.tcz does not depend on alsa-config.tcz, but alsa-config.tcz depends on alsa.tcz.
You can edit your onboot.lst to load alsa-config.tcz instead of alsa.tcz .
- I use boot code vga=789 which is working fine.
However, I also use this in my extlinux.conf :
MENU RESOLUTION 1024 600
While processing/loading extensions at boot, the resolution gets reset (to the same value).
I don't know which extension is causing this. Anyway, I don't think any extra extensions are needed for the framebuffer to be used in CLI. You can remove Xvesa.tcz , Xlibs.tcz and Xfbdev.tcz from your onboot.lst file.
-
- You cannot setup a sub-directory to be home. You can only specify a drive.
I'll try. 'A drive' means I can do -home=sda9 or exactly -home=sda? I couldn't undestand it clearly in FAQ.
I don't know which extension is causing this. Anyway, I don't think any extra extensions are needed for the framebuffer to be used in CLI. You can remove Xvesa.tcz , Xlibs.tcz and Xfbdev.tcz from your onboot.lst file.
OK, but with pure core it won't work too for me.
-
Hmm.. I wonder if graphics-KERNEL.tcz is needed for MPlayer (?).
-
Alsa-config worked so now I can hear a sound track in avi. If I type mplayer -vo fbdev file.avi it goes fine (sound only), if I do mplayer without -vo fbdev it starts lagging and croaking (with still no video), and then I press '->', and rewind it, and mplayer shows me that my computer is too slow and starts playing sound track normally but not from the beginning. Okay, maybe I should go on trying to deal with fbdev.
-
I had big performance problems with MPlayer too. So, for personal use, I compiled it from source and made sure it included MMX and SSE instructions, which are not present in the build available from the 6.x repo.
-
I had big performance problems with MPlayer too. So, for personal use, I compiled it from source and made sure it included MMX and SSE instructions, which are not present in the version available in the 6.x repo.
In that case I believe it only depends on proper use of fbdev and correct video output, for it may not be able to synchronize both tracks correctly when not playing one of them or something.
Graphics-KERNEL.tcz (?)
You're quite right, dear sir. After installing that mplayer made an effort to start playing video but I didn't set the size for video output so it crashed. I don't know nothing of which size do I choose, now I gotta google.
But, to return to what Misalf was saying, what the source building process looks like in TC? What should I do to preserve all built and installed options, configs and libraries after reboot? Must I compile it and pack as tcz extension?
-
If you want to compile MPlayer, have a look here:
http://forum.tinycorelinux.net/index.php/topic,18142.0.html
You would load compiletc.tcz to have the basic build tools.
I might be able to send my build to you for testing. Not before tomorrow though and it currently has more deps than actually needed.
-
You do not need graphics-KERNEL.tcz for Mplayer-nodeps.
I am playing a video right now on CentOS 6 with onboot.lst
alsa-config.tcz
libpng12.tcz
libjpeg-turbo.tcz
freetype.tcz
libXext.tcz
Mplayer-nodeps.tcz
-
With a onboot.lst of:
alsa-config.tcz
mplayer.tcz
I can also play videos, but the video performance is much worse than the mplayer-nodeps from Core 5.
-
With a onboot.lst of:
alsa-config.tcz
mplayer.tcz
I can also play videos, but the video performance is much worse than the mplayer-nodeps from Core 5.
I couldn't with "/dev/fb0: No such device" error.
mplayer -vo fbdev file.avi
-
It works for me with graphics-kernel, but now I'm getting trouble with mplayer. It doesn't want to play some videos because of some scale or colorspace issue. Here:
MPlayer 1.1-4.9.1 (C) 2000-2012 MPlayer Team
MMX supported but disabled
MMX2 supported but disabled
SSE supported but disabled
SSE2 supported but disabled
Playing Lowrider.avi.
libavformat version 54.6.100 (internal)
AVI file format detected.
[aviheader] Video stream found, -vid 0
[aviheader] Audio stream found, -aid 1
VIDEO: [FMP4] 640x360 24bpp 25.000 fps 350.8 kbps (42.8 kbyte/s)
Clip info:
Software: Lavf52.64.2
Load subtitles in ./
Opening video filter: [scale w=1024 h=600]
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 54.23.100 (internal)
Unsupported PixelFormat 61
Unsupported PixelFormat 53
Unsupported PixelFormat 81
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
Unknown/missing audio format -> no sound
ADecoder init failed :(
Requested audio codec family [vorbis] (afm=libvorbis) not available.
Enable it at compilation.
Opening audio decoder: [tremor] Ogg/Vorbis audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 96.0 kbit/6.80% (ratio: 12000->176400)
Selected audio codec: [tremor] afm: tremor (OggVorbis audio)
==========================================================================
[AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or directory
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
[swscaler @ 0x8774380]BICUBIC scaler, from yuv420p to bgra using C
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [fbdev] 1024x600 => 1024x838 BGRA
Can't put VSCREENINFO: Invalid argument
FATAL: Cannot initialize video driver.
FATAL: Could not initialize video filters (-vf) or video output (-vo).
Exiting... (End of file)
tried mplayer -vo fbdev -fs Lowrider.avi
-
Another one video I tried to view was OK, but it won't get fullscreen, even with -fs set. Nor did -zoom option do. It played in the middle of screen, right "above" the console.
-
I had big performance problems with MPlayer too. So, for personal use, I compiled it from source and made sure it included MMX and SSE instructions, which are not present in the build available from the 6.x repo.
As long as your version follows "-march=i486 -mtune=i686", please feel free to submit to replace the current version
-
I definitely consider to do so, but only if it works out well. It will need at least one rebuild (I hope not more than that since it takes quite some time). I'm not sure if I can make a -nodeps version but I want to slim it down as much as I can. Now that I know how to compile MPlayer, it should be just a matter of time. (:
-
I definitely consider to do so, but only if it works out well. It will need at least one rebuild (I hope not more than that since it takes quite some time). I'm not sure if I can make a -nodeps version but I want to slim it down as much as I can. Now that I know how to compile MPlayer, it should be just a matter of time. (:
Does it? I'd built Wesnoth and it did not take lot of time. I left it in VT and watched some video, or played some game or something. If you have no time you can explain me what do I need to make a build in TC (you said I need compiletc.tcz, is it enough?), send me your configure settings and tell where to get the same source as yours. Then I would test it on my own and share the results, does it work and do I see any improvements etc.
It would be great if there were no X libraries dependence in mplayer.tcz. I have no X, so what for am I waiting longer? It concerns also graphics.kernel; in its dep file there are lots of X libraries that I do not need necessarily... But the graphics kernel I do need; hmmm; what if I load manually only those dependencies from it that I need? And leave all X libs behind... I'll try and see. I tried to throw X library out of the mplayer.dep file, but it won't work then. Even in no X environment.
-
Different software takes different amounts of time to compile.
IIRC, MPlayer took about 50 minutes to compile on my netbook (OC'ed @ 2GHz, 2GB RAM, 460MB compressed Swap in RAM + No Swap Drive).
You can get valuable hints about compiling MPlayer in the thread I posted a link to @ Reply #30, so you don't need to do the same mistakes I did.
compiletc.tcz contains only the basic build tools. Anything else needed is either mentioned in MPlayer's readme or will be told to you via error message when running ./configure or make .
Also read this:
http://wiki.tinycorelinux.net/wiki:creating_extensions
And this:
http://tinycorelinux.net/book.html
-
The bootcode
home=hdXY
will automatically setup /home/tc
to "bind" to /mnt/hdXY/home/tc. The home boot code lets Tiny
Core coexist with other Linux installations by inserting the tc user
directory under a pre-existing /home directory. Also, Tiny Core
cannot auto-detect a persistent home directory, so the home boot
option is always required.
Ah, so da naa! There was another explaining somewhere in an old installation FAQ that I misunderstood concluding that boot 'home' option will sort of format my partition or something... ;D
So that option will only create a directory inside an existing partition, even in existing /home folder? I have a /sda5 partition including /home for my openSUSE distro and some other sensitive files (old /home deprecated folders), I can just mount it to TC as home=sda5 ? It'll be okay, then?
-
Correct. home=sda5 will simply use /sda5/home as the home directory, and, if not already present, will also create the directory tc in /sda5/home .
The boot code opt= works the same way, but may interfere with already installed versions of Linux.
The boot code home= is quite safe to use though.
-
Well, I have read the book and based on what I understood I would like to ask if my onboot modules are copied to RAM or mounted. There are several modes, mount and copy. It is said in the book to get a module copied you must mark it with some kind of copy2fs flag. But no examples were given. Here I have my own onboot.lst:
wifi.tcz
links.tcz
mplayer.tcz
alsa-config.tcz
graphics-3.16.6-tinycore.tcz
I want them all loaded to RAM. What do I add to my onboot.lst?
-
Run the following 2 commands:
ce
touch copy2fs.flg
-
Before I reboot: is it ok to create a symlink
/sda5/home -> /sda5/tinycore/home and pass home=sda5 to kernel?
I want to keep all tc files into tinycore folder... wouldn't like to scatter all those folders...
-
Before I reboot: is it ok to create a symlink /sda5/home -> /sda5/tinycore/home and pass home=sda5 to kernel?
I want to keep all tc files into tinycore folder... wouldn't like to scatter all those folders...
It's okay, yeah. I also created links in my /home to big video and music folders on other drives. /home and /opt point to /tinycore/home and /tinycore/opt, respectively. Won't have to deal with a whole bunch of folders later, being able to just move one /tinycore. Nice.
So okay, now I gotta make my mplayer work properly, probably got to read some else threads reporting similar problems...
However, I feel that mine [problem] concerns my colorspace; maybe framebuffer's colorspace is different from those are expected by mplayer or by video format?
Here's my fbset output, matching the /etc/fb.modes contents.
mode "1024x600-0"
# D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
geometry 1024 600 1024 600 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode
And here is the video I'm trying to play. It's old, and it's 640x360 of size.
(More modern-looking one I'm trying to play works quite nice -- an .avi movie somewhat of that size too. But it also rejects playing fullscreen... And the clip won't even start playing, ever. Only, if I do -vo null, it plays music, normally.)
http://www.youtube.com/watch?v=1rrsj_auEKs (http://www.youtube.com/watch?v=1rrsj_auEKs)
-
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 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.
-
Setting Xfbdev didn't help. Nothing changed. Now'll try Xvesa but with a small hope.
It appears I even have some libX libraries, including libX11 and like. I don't know what could dependence-chain them and will investigate it later to purge them if they're not required.
I wonder if I could set up a VM with the same environment in openSUSE and record a video of what's happening? Or maybe I can record a video from CLI, some kind of one more framebuffer trick?
Xvesa didn't help. Is it possible my system lacks some kind of codecs? Even in openSUSE, after fresh install, when I set vlc up it won't play some videos claiming it has no codecs. Does mplayer.tcz contain them all?
-
I didn't know where to post it, it's not good to overburden the topic with non-related posts but, I just wanted to say, in the repo there are either Links with no cookies and no tabs or ELinks with cookies and tabs but with no SSL support (so no https connections). :\
I wonder if I can build that one with ssl-enable... Have to read 'Build FAQ'... If I build it with all compatibility options required it may even be uploaded to repo... Maybe someone else needs ELinks features including SSL, too...
-
Contact the author of that package for update requests. Do not update packages without permission unless the author as abandoned the package.
-
Things became a little clearer to me, my CLI seems to be not using framebuffer at all. Look, I do "cp /dev/fb0 test.img" and "cp test.img /dev/fb0" and nothing happens! However I checked the image size it's 2457600, that is, it doesn't fail copying from framebuffer to it, the image contains some data. But when I try to restore it to fb, my screen remains intact. I even tried "cat /dev/urandom > /dev/fb0" with no visible effect! So maybe it doesn't use fb0 at all somehow, that's why I might not be able to play videos in fullscreen with mplayer and all these errors, eh?
[TIP] When I had not graphics.KERNEL yet installed and worked in pure 80x25, this joke with flooding fb0 with urandom worked. :D
So?... *hmmm*
-
, Well, I... OH SHI- was trying to do that job to fb again... ahem... I'm not sure it will loook okay on forum... I see just strange things mystifying, if I'd say... But surely this was a visible effect!!!
Still, when I was playing with it earlier, cat-ting urandom to fb0 led to appearing of rgb noise on my screen. And now it was a flood of strange mystifying symbols.
UPD: Yeah, I give up. Now I repeated it again and here it is -- an rgb noise on the screen. But- but- it was all the same-
UPD2: I was able to restore my old buffer state from an image file. Well, okay, but what for did you mislead me, dear framebuffer? What was all these bug-looking symbols (Dozens...) about?
-
post the output of 'showbootcodes' and the contents of your onboot.lst.
-
post the output of 'showbootcodes' and the contents of your onboot.lst.
Hai.
1. BOOT_IMAGE=/tinycore/vmlinuz tce=LABEL=grub/tinycore/tce home=sda9 opt=sda9 quiet
2.
wifi.tcz
links.tcz
mplayer.tcz
alsa-config.tcz
graphics-3.16.6-tinycore.tcz
kmaps.tcz
nethack.tcz (complains of not finding some X lib and doesn't start working)
-
As was explained on page one of this thread, you need a vga=788 ( or some other valid vesa mode ) boot code to setup the frame buffer.
-
As was explained on page one of this thread, you need a vga=788 ( or some other valid vesa mode ) boot code to setup the frame buffer.
I've tried. Then it had no effect but it may be before I installed graphics.tcz. I'll try again. Over
But, there is some kind of framebuffer stuff... One of the two video files plays normally but in the centre of console, between all those command outputs and all... Won't go fullscreen... And I can save and restore the screen state through fb0... So framebuffer is kinda set, eh? Well, okay, I'll do as you said.
-
It worked for fullscreen. The first video still won't play, but I believed it was due to some format incompatibility. I set up ffmpeg and converted it from avi to avi (in the purpose of making it more UP-TO-DATE avi). It didn't do, but struggled harder, so I converted it to mpeg and it was working and over at last (well, not ideally but it's my business for now. Some kind of old-crap-issue). Still don't understand why did not it work earlier for I tried this vga= option. Maybe I misprinted then or something. By the way, after the vga option worked I could see two small pictures presenting 'Tiny Core' in the upper left corner for a fraction of second. Then there was all that 'loading' strings. Why did it disappear so quickly and why were there two of them and just so small?
For a post scriptum: it's a pity that ffmpeg dep-chains so many of some X libraries I won't need anymore and it won't as well. I mean, ffmpeg needs all those X libraries only in X environment, right?
I think my problem is over, except of some questions above.
-
By the way, after the vga option worked I could see two small pictures presenting 'Tiny Core' in the upper left corner for a fraction of second.
That image is only displayed if framebuffer is used. (;
Why did it disappear so quickly [...]?
Core boots fast - and - when /etc/init.d/tc-config takes control, the screen gets cleared.
(I'd like it to stay visible too, actually, but don't know how to do)
You can disable it via boot code:
logo.nologo
[...] and why were there two of them [...]?
I think that indicates the number of processor cores (and/or multi-threading)
[...] and just so small?
Video resolution.
-
Why did it disappear so quickly [...]?
Core boots fast - and - when /etc/init.d/tc-config takes control, the screen gets cleared.
(I'd like it to stay visible too, actually, but don't know how to do)
You can disable it via boot code:
logo.nologo
Well, maybe somewhere there in tc-config we could find that command clearing the picture and making output messages... For example it's surely possible to add one more boot code e.g. logo.stay or something, disabling all boot output in total.
[...] and why were there two of them [...]?
I think that indicates the number of processor cores (and/or multi-threading)
[...] and just so small?
Video resolution.
Okay, maybe. I've got two.
Yeah... but surely it's possible to make it go fs! ;)
Or not?..