I’m happy that the Sax2 command is working with KDE, this is a great result.
But now I’m in a great doubt: why has no worked for me? Maybe I have pressed the “Cancel” button when the test screen has been displayed? Uffff!.. now I’m sure of nothing. But I think I’ve pressed the right button.:\
In anycase, I’m sure that the Sax2 command has not recognized my chipset (K8M890). This has never happened.
This bring me at a final consideration: all owners of the K8M890 VIA-chipset must always edit the xorg.conf file manually following the procedure descibed in this thread.
Do you agree?
Very significative is you discover of the double-driver installation performed by the unichrome rpm. This confusion about name has blocked me initially. So, suggestion from oldcpu was right: uninstall all drivers and re-install only the unichrome driver.
Honestly speaking, I think that experiments over the chrome9 driver can be skipped. If I remember right, selecting the openSuse 11.2-chrome9-package by Yast, there was a message like this: “Do not install this driver cause…[omissis]”
It is true, or I remember wrong? Did you see that message?
I don’t remeber exactly where message was located, after selecting the package (in Yast) you must check “Changelog”, or “Author” or “Dependencies” or something like that.
I used to be bitten by such warnings all the time (albeit with different warnings) during installations, and I could never pin down exactly where I saw them. I could never remember their exact detail, and I detested writing down all the stuff I saw. I honestly tried but it was too muich of a pain to write things down.
I seemed for the longest time be caught in this circle of repeated warnings that I would forget, and it was a constant source of irritation to me. In the end, I started using my digital camera, keeping it right by my PC, for everytime I got a warning I would take low quality pix (low quality because of my ineptness with the camera). … In cases where messages scrolled by the screen too fast, if repeatable, I would put my digital camera in movie mode, and repeat the activity to cause the warnings. Then I would play back the warning message frame by frame.
The end result being I had a record of the warnings, and my learning curve finally started to move upward, instead of the downward frustrating spiral it was in previous.
So if you are fortunate enough to have an inexpensive digital camera, an idea would be to keep it handy beside your PC.
Now I was searching the exact location where I saw that message and… I could find it!
I have installed the old repositories before but… nothing… I really cannot find where the message was located… grrrr.
The digital camera is the best solution for the bug-hunter, nothing to say about that. But I’m not that kind of user… maybe can I ask fo it to my wife! lol!
Anyway, a message for consused: please ignore my previous post! I cannot post the proof comcerning the quality of chrome9 drivers!
Don’t lose sleep, but that may be the answer. I have the same doubt about some of my earlier failures to cleanly handle the driver switch using sax2. Then, I probably went for the Change Configuration option and subsequently messed up. At least the Cancel option should leave xorg.conf unchanged. I have survived for several years with the K8M800 and a manually maintained xorg.conf even after sax2 began to correctly identify my chip. Look on the bright side, you will learn more by having total control over xorg.conf for now, especially with the current status of the developing drivers. The chrome9 h/w is still relatively new, for linux. At least VIA have chosen open-source, as their early attempts at a proprietary linux driver were not good and came with security exposures.
In anycase, I’m sure that the Sax2 command has not recognized my chipset (K8M890). This has never happened.
This bring me at a final consideration: all owners of the K8M890 VIA-chipset must always edit the xorg.conf file manually following the procedure descibed in this thread.
That’s because h/w manufacturers must release with Windows drivers or perish! I agree that your final statement appears to be true for openSUSE. But also consider that only the openchrome driver is currently included by more than 50% of the top twenty most popular linux distros. Even Xorg provide it, and they are incredibly cautious and slow to make those decisions.
If I remember right, selecting the openSuse 11.2-chrome9-package by Yast, there was a message like this: “Do not install this driver cause…[omissis]”
It is true, or I remember wrong? Did you see that message?
I don’t remember exactly where message was located, after selecting the package (in Yast) you must check “Changelog”, or “Author” or “Dependencies” or something like that.
You may be referring to the message in chrome9 rpm’s Changelog about not installing this driver by default on any Via h/w.
Yes! That’s it! pffffewwww… I was thinking that I’m ready for hospital for mental disability…lol!
Yes, is good that their choosed the open-source direction, but If I go on their website (VIA drivers)… well… they still are stopped to openSUSE 10
Yes, that’s true… but I think that a normal user could be not so much happy like you and me… I cannot imagine my wife setting up the xorg.conf file lol!
What I mean is that Linux is not yet “the computer for the rest of us”
I agree that your final statement appears to be true for openSUSE.
