Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Sounds like a problem with the X server (hw overlay, to be more specific).
What is your hardware? You should use a specific driver for your card,
not the VESA driver, as it probably won't supply overlay support. If you're
using an Nvidia card, you will need to download the driver from www.nvidia.com (the .sh shell script for SuSE >= 8.1).
> It is an ATI RAGE PRO TURBO AGP 2X card, autodetected by yast.
> I also saw an X11: ati version 4, server: ati
> entry among the hardware info of the card.
If it's of the Rage 128 type, it has overlay. If it's of the
Rage II type, I don't think it has overlay.
> I think the X11 entry shows that the system uses an ati server (i.e. ati
> driver??) for the card.
> But how to know if it is the correct driver?
Go to a console (ctrl+alt+F[1-6]), kill the X server if it's running,
type sax2 at the console. You will find the current settings there.
> Anyway, I could watch movies "out of the box" with my old S3Trio card
> and old old SuSe 6.4;
Probably without hardware overlay, as the Trio didn't have one (I owned
one myself), which means bad quality; most modern player support overlay
only, as the newer cards all have it.
> and now SuSe 9.0 gives me a black screen with an
> Ati Rage card?????
> That is a shame.
Probably neither SuSE nor Linux fault, forward your complaints to the
graphics card manufacturer.
Probably you are right, it is a great fault of hardware manufacturers that they do not support Linux very much.
But given the situation as it is, why do the open source programmers insist on making programs that will simply not work on most computers?
(I know some 60 computers around me, of which maybe 15 have a graphic card that is new enough to have overlay)
After the third full working day of trying in vain to install a simple Linux system that has multimedia, Internet and e-mail (SSL) support, I am too much frustrated to tolerate such stupidity.
When I started the installation I had a Linux experience of three years behind me. I knew of the hardware issues, but I thought things get better, and SuSe 9.0 will have better support of old hardware.
I was wrong. It has worse.
I did not know that:
- yast and sax2 are still as unusable and hell of a slow tools as ever, (I could not find in sax2 if the card is ATI Rage 128 or ATI Rage II, it only knows the card as ATI RAGE 3D PRO TURBO 2x, as I mentioned in my previous card. It does not even mentions any drivers)
- yast and the kde control center are there just to confuse you, since one of them does not know how the system was configured by the other,
- though SuSe 9.0 has Lucent winmodem support, the modem will start dialing after a 10 MINUTES delay, meanwhile the computer is practically frozen,
- mozilla 1.6 will not be able to communicate SSL with the smtps server by which Mozilla 1.5 on SuSe 7.3 had no problems,
- just after downloading, installing and fully setting up the mail client of mozilla 1.6, it turns out that it can be thrown away, as it cannot import Outlook Express mails (despite the fact that its help pages claim that it can)
- a SuSe 9.0 system will not be able to play an mpeg file in the year of 2003 (My god: even win98 can do it out of the box)
Now I feel I should not have started this installation for my colleague trying to make him convert to Linux. It needed too much effort and gave me too much frustration.
>- yast and sax2 are still as unusable and hell of a slow tools as ever, (I
>could not find in sax2 if the card is ATI Rage 128 or ATI Rage II, it only
>knows the card as ATI RAGE 3D PRO TURBO 2x, as I mentioned in my
>previous card. It does not even mentions any drivers)
Can be all the same, as it probably is a combi driver
>- yast and the kde control center are there just to confuse you, since one
>of them does not know how the system was configured by the other,
Right, it's a bit of a mess here. Lucky him who knows in which configuration
files to look things up
>- though SuSe 9.0 has Lucent winmodem support, the modem will start
>dialing after a 10 MINUTES delay, meanwhile the computer is practically
I've heard that this is still not working well
>- just after downloading, installing and fully setting up the mail client of
>mozilla 1.6, it turns out that it can be thrown away, as it cannot import
>Outlook Express mails (despite the fact that its help pages claim that it
Never tried this, I'm using KMail only. BTW I think it's rather Outlook
Express that you can throw into the dustbin, as it can not export it's stuff
to other software easily
>- a SuSe 9.0 system will not be able to play an mpeg file in the year of
>2003 (My god: even win98 can do it out of the box)
Yes it is, it's just that SuSE happened to miss to QA 9.0 on your
machine; besides, it's well known that *.0 versions are likely to have
issues, and 9.0 certainly does. But that's part of the fun, eh?
I just want to tell you that I succeeded on the fourth day: it turned out that the mpeg playback problem was possibly due to insufficient RAM. I added 128M to 64M that had already been there, and xine began to play well.
The modem trouble had vanished, too, even before I added the RAM: I just modified the init sting "ATZ" to "ATZ0" in wvdial.conf, then reset the system (like I did several times before) since wvdial crashed it, than changed the init sting back to "ATZ" after reboot.
Ever since the modem dials immediately.
Only the screen and colour resolution problem remained: I do not know why but I could not configure a screen resolution of 1024x768 and true colours, with an ATI Rage card and a monitor with hsync 30-70kHz and vsync 40-120Hz.
I had to setup 65k colours in order to have the 1028x768 resolution. This will not give very realistic pictures especially with photos; and the user has too little Linux knowledge to re-configure X11 with sax2 to have true colors when needed.