Hello,
I am currently running Suse 9.1 Professional. It seems that the latest
updates for Opera and XFree86 conflict with each other:
Preparing... ###########################################
[100%]
file /usr/share/applications/Xkill.desktop conflicts between
attempted installs of opera-7.51-1.1 and XFree86-4.3.99.902-43.28
file /usr/share/applications/Xrefresh.desktop conflicts between
attempted installs of opera-7.51-1.1 and XFree86-4.3.99.902-43.28
file /usr/share/applications/xcalc.desktop conflicts between
attempted installs of opera-7.51-1.1 and XFree86-4.3.99.902-43.28
file /usr/share/applications/xclipboard.desktop conflicts between
attempted installs of opera-7.51-1.1 and XFree86-4.3.99.902-43.28
file /usr/share/applications/xload.desktop conflicts between
attempted installs of opera-7.51-1.1 and XFree86-4.3.99.902-43.28
It seems strange that opera provides the .desktop files for xload, xkill,
and such tools. Are you guys planning on building a fixed opera RPM that
does not conflict with XFree86?
If not, where do I get the *.lng.bz2 files mentioned in the opera .spec
file, so I can build my own fixed RPM?
thanks for any help,
Jim Faulkner
Hello suse-xfree86,
Sorry about following up my own post...
I have now installed SuSE 8.1 and been able to compile and install the
Matrox drivers so I have dual screens :-))
But...
When I close down X or use Ctrl+F1, F2 etc. to switch to a console my
monitors immediately go blank (thank goodness) and report out of timing
- with a vertical refresh of 268Hz and a horizontal refresh of 120kHz -
a bit much for the 60Hz / 63kHz these LCD's are used to.
So it's now fine in X but not at a terminal outside X.
What affects the monitor timings outside of X? XF86Config seems fine
and the monitors report timings well within their range within X but
I've never had to adjust monitor timings for use away from X.
Any pointers would be appreciated.
--
Best wishes
Jeff Gaines Damerham Hampshire UK
Hello suse-xfree86,
I have just installed SuSE 9.1 Pro and have it working fine, I can
connect to my home network and browse the web, I have also
downloaded some newsgroups.
I had dualhead working fine with a Matrox G400 DH card which I have
now changed to a Matrox P650 with dual DVI out.
I cannot get dual head working with this new card :-((
Matrox have drivers for RedHat v9 which I have downloaded and
although I can extract the driver I cannot properly install or
compile this driver - it doesn't like X v 4.3.999 or whatever 9.1
comes with.
I have tried the generic driver (fbdev) with xinemara - according to
the SuSE manual dualhead should just work - but no success.
Do any of the generic drivers support dualhead or am I wasting my
time trying?
What version of SuSE used XFree 4.3.0? Is it possible to uninstall
4.3.999 and put 4.3.0 in its place?
My intentions is to make the transition to Linux over the next
couple of years but I have been using dualhead in Windows for so
long now I feel absolutely lost on a single monitor machine.
--
Best wishes
Jeff Gaines Damerham Hampshire UK
Hi, all!
Can anybody confirm that after installing the NVIDIA drivers (currently
using NVIDIA-Linux-x86-1.0-5336-pkg1.run from the NVIDIA site) it is
necessary to set SCRIPT_3D to "no" in /etc/sysconfig/3ddiag to prevent
SuSEconfig.3ddiag from setting the symbolic links to MESA's GL libs (and
deleting the GLX link in /usr/X11/lib/modules/extensions/libGLX.so)?
Btw: I'm using SuSE 8.2 with a 2.4.24 kernel and a Asus 9570TD (NVIDIA
FX 5700) graphics card.
Thanks in advance!
Regards,
Oliver
Hello list,
After upgrading my Celeron 500 to a bleeding edge technology P-III-1 GHz
CPU, I am experiencing problems with the NVidia driver (using a Riva TNT
card) and SuSE 9.1.
When booting for the first time after the upgrade, X started up but hang
almost immediately. So I removed the nvidia drivers and used the nv
driver, which worked.
The reinstallation of the driver package also worked, but when I do sax
-m 0=nvidia, the display (and the rest of the system) freezes again
almost immediately (the NVidia logo is displayed; shortly after the
mouse pointer apperas the system stops) and I have to reboot. (I cannot
use YOU to install the driver because I do not have internet access
under Linux.)
I also tried "upgrading" the Kernel to the one from the DVD without
success. I should also mention that the NVidia drivers did work with the
old CPU.
In which way could exchanging the CPU bring harm to the display drivers?
I didn't change one piece of software.
Any hint is appreciated.
Thanks in advance
Christian
Hi,
I've installed Suse 9.1 on a Dell Inspiron 8600 (with ATI Mobility
Radeon 9600 PRO Turbo card and 1920x1200 laptop display panel). Sax2
wouldn't recognize the 1900x1200 panel, so I googled a bit and managed
to put together an XF86Config file (attached) that works quite well
using the unaccelerated "radeon" driver.
Then I decided to install the latest version of the ATI 3.9.0 driver
available from Suse's ftp site following instructions in the README.
Driver installs successfully, however when I run
"sax2 -r -m 0=fglrx -b /usr/X11R6/lib/sax/profile/firegl", the screen
goes blank, then parts of the screen go white, then green, :-) , at
which moment I usually kill Sax with Ctrl-Shift-Backspace, and it exists
generating the attached log file. The log says a) "DRI initialization
failed"; and b) there are lots of unresolved symbols. I've already fixed
error messages about MTRR overlaps using instructions from
http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_mtrroverlap.
I'd appreciate any suggestions.
These are the relevant (I think) package versions:
fglrx-3.9.0-2.1
km_fglrx-3.9.0-2.1
kernel-source-2.6.5-7.95
kernel-default-2.6.5-7.95
Regards,
Vadym
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.