Hello,
I have problem with nvidia GeForce FX 5200 graphics card on Suse 9.1
64bit. When some specific output should be displayed (mostly
scrolling in xterm/Mozilla etc.), display
is switched to black for 1 second. It's like blank screen saver, but
I'm pretty sure
that it's not misconfigured screen saver :-)
I have tried both 1.0-5332 and 1.0.6106 drivers, I have tried Option
"AGPMode" "4"
or Option "NvAgp" "1", but nothing has changed. The problem is both
with kernels 2.6.5-7.75
and 2.6.5-7.95.
Has anyone else the same problem?
Mirek Ruda
Hello
I am using SuSE 9.1 on an athlon 1.8 and A7N266vm motherboard machine. I
installed the nvidia driver with 5336-run from nvidia site. And the amount of
video memory is 32 mb. My default run-level is 3. And mostly i use kde for X.
Now some problems are happening there.
1. At times the mouse is becoming a rectangular block, which happen usually
when 8 mb of ram is given to vga.
2. During some vga-memory hungry application like mplayer (which i installed
from source and that happened without any error message of any kind) all
other part of the screen is going black and the display is not working
properly too -- exactly the same that happens with low vga mem.
3. Once i logout from kde, i cannot re-log-in, the X server gives error 11.
Is the problem specific to kde? Or some other driver i should install? Should
i install that from yast-online update? Or, some configuration has to be
changed?
das
Hi,
I'm getting desperate, as I haven't found a solution in 2 weeks of
trying.
I upgraded from 9.0 to 9.1, using a reformat and clean install
approach. This machine has run 8.x and 9.0 quite happily, so I didn't
expect any problems with 9.1.
It's an IBM T30 Thinkpad (2GHz CPU, 2G RAM); it has a built in display
(1024x768x60Hz), and an external LCD panel at 1280x1024x60Hz. The
problem is that, no matter what I try, the X server (or the ATI driver?)
will only drive the external panel at 1024x768. The result is that
fonts look awful, and headaches are frequent. It seems that the server
is querying the display at startup, only finding the built-in panel, and
deciding that1280x1024 is outside the permitted range. It seems that
the X server is setting the primary display to always be the built-in
panel, and setting the resolution to 1024x768. even when using the
1280x1024 external monitor. I can't find a way to change this
behaviour. Does anyone know if it's possible (9.0 did it OK, so I guess
it is)?
Sax2 always reverts to 1024x768 at the "test" stage after manually
setting the monitor and resolution to 1280x1024.
I've tried loading the newer patches for radeon fro the SuSE downloads
area, but no luck so far. Am I faced with having to go back to 9.0?
Have I included enough info?
TIA,
Paul
The log file shows.....
(--) Chipset ATI Radeon Mobility M7 LW (AGP) found
(II) RADEON(0): I2C bus "DDC" initialized.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 4, Detected Type: 0
(II) RADEON(0): Non-DDC laptop panel detected
(II) RADEON(0): I2C device "DDC:ddc2" registered at address
0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 1
(II) RADEON(0): Displays Detected: Monitor1--Type 2,
Monitor2--Type 1
(II) RADEON(0): Monitor2 EDID data ---------------------------
(II) RADEON(0): Manufacturer: PHL Model: 808 Serial#: 14377
(II) RADEON(0): Year: 2004 Week: 6
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Analog Display Input, Input Voltage Level:
0.700/0.300 V
(II) RADEON(0): Sync: Separate Composite SyncOnGreenSerration
on. V.Sync Pulse req. if CompSync or SyncOnGreen
(II) RADEON(0): Max H-Image Size [cm]: horiz.: 36 vert.: 29
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): DPMS capabilities: StandBy Suspend Off;
RGB/Color Display
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.633 redY: 0.340 greenX: 0.295 greenY:
0.591
(II) RADEON(0): blueX: 0.141 blueY: 0.096 whiteX: 0.313
whiteY: 0.329
(II) RADEON(0): Supported VESA Video Modes:
(II) RADEON(0): 720x400@70Hz
(II) RADEON(0): 640x480@60Hz
(II) RADEON(0): 640x480@67Hz
(II) RADEON(0): 640x480@72Hz
(II) RADEON(0): 640x480@75Hz
(II) RADEON(0): 800x600@56Hz
(II) RADEON(0): 800x600@60Hz
(II) RADEON(0): 800x600@72Hz
(II) RADEON(0): 800x600@75Hz
(II) RADEON(0): 832x624@75Hz
(II) RADEON(0): 1024x768@60Hz
(II) RADEON(0): 1024x768@70Hz
(II) RADEON(0): 1024x768@75Hz
(II) RADEON(0): 1280x1024@75Hz
(II) RADEON(0): 1152x870@75Hz
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported Future Video Modes:
(II) RADEON(0): #0: hsize: 640 vsize 480 refresh: 75 vid:
20273
(II) RADEON(0): #1: hsize: 800 vsize 600 refresh: 75 vid:
20293
(II) RADEON(0): #2: hsize: 1024 vsize 768 refresh: 75 vid:
20321
(II) RADEON(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid:
32897
(II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 108.0 MHz Image Size: 359 x 287 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1440
h_blank_end 1688 h_border: 0
(II) RADEON(0): v_active: 1024 v_sync: 1025 v_sync_end 1028
v_blanking: 1066 v_border: 0
(II) RADEON(0): Serial No: HD 014377
(II) RADEON(0): Monitor name: Philips 180P2
(II) RADEON(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H
max: 82 kHz, PixClock max 140 MHz
(II) RADEON(0): End of Monitor2 EDID data --------------------
(II) RADEON(0):
(II) RADEON(0): Primary Display == Type 2
(II) RADEON(0): Clone Display == Type 1
(II) RADEON(0): Panel ID string: 1024x768
(II) RADEON(0): Panel Size from BIOS: 1024x768
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Total number of valid DDC mode(s) found: 0
(WW) RADEON(0): Mode 1280x1024 is out of range.
(WW) RADEON(0): Valid modes must be between 320x200-1024x768
(II) RADEON(0): Valid mode using on-chip RMX: 1024x768
(II) RADEON(0): Valid mode using on-chip RMX: 800x600
(II) RADEON(0): Valid mode using on-chip RMX: 640x480
(II) RADEON(0): Total number of valid FP mode(s) found: 3
(**) RADEON(0): Virtual size is 1280x1024 (pitch 1280)
Hello all.
I'm running Suse 9.1 on an HP Pavillion laptop. I have all the acpi controls
enabled, which has a great impact on battery life. Only problem is that
sometimes my LCD flickers. It seems to alternate (many times per second)
between minimum brightness and whatever my current brightness level is. I
haven't been able to isolate why this occurs. Any suggestions?
Someone suggested that I turn off "Enable Display Power Management" in Control
Center-->Power Control -->Display Power Control, but that hasn't made any
difference.
Thanks--
Chris Freyer
Hello,
I'm running Suse 9.1 (amd64 - 64bit) version on my Opteron machine.
When debuging problems with my NVIDIA graphics card, I have decided
to test also Matrox G550 (dual head)
card which I was successfully using with 32bit version. I'm able to
run Xserver, but without GLX support -
libdri.a has unresolved symbol __glXActiveScreens and I don't see
libglx or libGLcore other then comming
from nvidia drivers.
Is GLX/DRI supported for Matrox G550 on 64bit linux? Did I missed
some package I should install?
--
Mirek Ruda
Hello List:
Has anyone every configured XFree86 to work with a display which can run at
1365 x 768 resolution? I guess I just need to edit my XFree86 config file to
use this resolution, but how do I do that? I'm using a NEC PlasmaSync 50MP2 on
SuSE 9.1 Pro, with an NVIDIA FX card (1.0-6106 driver).
Thanks,
Matthew
Hello!
I have up-to-date instalation of 9.1 and I'm /expiriencing/
following /feature/.
Pressing four time shift activates sticky keys mode. I beleive it is
called sticky keys. In this mode double pressing shift works as Caps
Lock, single press of shift make next typed letter uppercased and all
other annoyances.
Most of other OSs (Windows, Mac OS X) has a nice feature to turn
forementioned sticky keys mode hard off. So if I'm not disabled/impaired
and do not need this mode - I just with single mouse click cat forget
about it forver.
Is there any way to deactivate this feature in SUSE?
So four times mistakenly pressed shift will be just it - unharmful
four times pressed shift?
P.S. I have found mentions of sticky in /etc/X11/xkb/compat/accessx.
Turning off AccessX in SaX does nothing. On next run SaX always happily
shows that AccessX is still here. What I'm missing?
P.P.S. And SaX does not read keyboard configuration from XF86Config.
Change group shortcuts are never gets displayed (they always stuck in
Default), thou they were choosen and generated in XF86Config by SaX on
previous run. Annoying, since you have to manually make up keyboard
configuration every time - or it will be reset to defaults.
--
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
"In the event of a percieved failing of the project |_|*|_|
leadership #debian is empowered to take drastic and |_|_|*|
decisive action to correct the failing, including by |*|*|*|
not limited to expelling officials, apointing new
officials and generally abusing power"
-- proposed amendment to Debian Constitution
Hi.
I recently installed X.org from www.x.org from source and everything went
well, except now I do not have access to the QT version of YaST 2 and I am
unable to install any program related to X in anyway (even some programs
like Python wont install). I'm wondering if there is a way for me to include
some sort of 'dummy' RPM file or something along these lines that will trick
YaST2 and will at least allow me to install programs that depend on Xlibs (I
removed it after I noticed X.org was working fine). I also will be manually
installing QT, and I would like to do something similar in this situation
where YaST will find my manually installed version.
Is there an open source version of YaST QT? (KDE broke, so I removed
everything.) I do not see a 'yast2-qt' source package in search. In short,
what I want to know is, is there anyway for YaST to be able to detect
programs that other programs depend on that I have installed from source?
If this is not possible, I would like to know more about "System Update" and
the availability of X.org from SuSE. I notice the provide .rpms for users of
version 9.1, but I am using 8.2. Will "system update" update my system to
SuSE version 9.2? If yes, I would gladly use the text based YaST2 as I
mostly depend on that to install programs rather than install them from
source.
Here is the output from X -version:
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.20-4GB i686 [ELF]
Current Operating System: Linux linux 2.4.20-4GB #1 Wed Apr 16 14:50:03 UTC
2003 i686
Build Date: 14 July 2004
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
As I mentioned I'm using YaST2, any help would be greatly appreciated.
AIM: Kicarus17
MSN: kidicarus19(a)hotmail.com
_________________________________________________________________
Dont just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> However if I log as root on a remote machine from the pc on
> my desk where I am a regular user, and from that window I type
> "ssh <myusername>@<mymachine> /sbin/yast2"
> the yast2 windows opens empty with no command icons component, probably
> a sign of no root permission.
If i try that, I get an "Error opening terminal: unknown".
And that's more or less what I've always got since SUSE changed the default
X forwarding... some time ago (8.0? I can't remember)
To enable X forwarding, you have to use
ssh -X <username>@<machine> /sbin/yast2
Obvously if username isn't root, you get a message stating that you don't
get to see the modules that require root access (and you se no modules at
all).
Using
ssh -X root@<machine> /sbin/yast2
does the trick for me.
Ciao,
Roberto
I upgrade to 9.1 on all my machines and now I have a problem to open
yast2 window on the net.
I am aware of the security setup change in X server and now I use ssh to
foward X clients connection
However if I log as root on a remote machine from the pc on my desk
where I am a regular user, and from that window I type
"ssh <myusername>@<mymachine> /sbin/yast2"
the yast2 windows opens empty with no command icons component, probably
a sign of no root permission.
Should the server be started as root? Hardly I can figure out why?
Any clue on my wrong understanding and suggestion on how to manage yast2
remotely?
Regards
