xine is very slow and mplayer does not run the fs mode
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
if you have an ati-rage, you can just fill-in that part in tha xorg.conf of Slack.
and make sure that in the section "screen ", the device refers to your device identifier ( "Device[0]").
then logout of X, and restart, or just reboot the pc.
Both mplayer and xine are working fine now. I got even higher resolutions and more refersh rates.
I will try to update my xorg.conf and replace "Device[0]" and see what happens.
no need to try the "Device[0]" thing.
it's just an identifier ( name ) that you give to the "device "
now it's named "VESA Framebuffer" and your screen section refers to the device with that name.
( well the name is not covering the load )
you could rename it to anything, as long as it's referred to in the screen section.
and restarting X ?
i myself boot to runlevel3 ( textmode ) and use "startx" to start X
so, i just click " logout " in the menu and X is stopped.
then just typing "startx" again does it here.
if you boot to runlevel 4 ( graph. login ) then i wouldn't know.
( i never do that... )
i thought i just wrote that...
-if you login on a command line on a textscreen( all black bg with a lot of white text)
--->that's runlevel 3; you use " startx" to go graphic.
-if you have a colored screen to login:
---> that's runlevel 4
well X login is normally 5, not 4. most distro officially don't use 4 at all, although to be neat it's often equivalent to 5.
and to restart X in runlevel 5... just log out. that'll normally kill it, and it is then reloaded by the time you get the login screen back. you could always just zap it on the login screen anyway (Ctrl + Alt + Bksp)
Originally posted by acid_kewpie well X login is normally 5, not 4. most distro officially don't use 4 at all, although to be neat it's often equivalent to 5.
and to restart X in runlevel 5... just log out. that'll normally kill it, and it is then reloaded by the time you get the login screen back. you could always just zap it on the login screen anyway (Ctrl + Alt + Bksp)
well...in Slackware it's called 4, and that's official enough.
and as Slackware is the oldest distro, i would say :
5 ( in other distros ) is often equivalent to 4.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.