Ekkehard Ellmann wrote:
> Ekkehard Ellmann wrote:
>> Lawrence Bowie wrote:
>>> Understood ... :)
>>> Can you post 'fglrxinfo -t' and 'cat /var/log/Xorg.0.log', please?
>> The mailer is very restrictive. He does't love lengthy postings.
OK, I put everything on my www-Server at
but this address is only active at normal German office-hours,
Hope you can get it.
Ich zieh' das mal wieder auf die Liste, da findet sich vielleicht
einer, der bessere Tipps auf Lager hat als ich...
On Wed, 26 Oct 2005 19:19:46 +0200
Hendrik Engelhardt <hendrik(a)engelhardt71.de> wrote:
> Also Ingo!
> Ich habe einen IIyama Vision Master Pro 452, der wird korrekt erkannt
> und eine Geforce Ti 4600 von MSI.
Ok, soweit nicht ungewoehnlich.
> Das Testbild bei der Konfiguration mit
> SaX2 kann ich herstellen aber nach dem Speichern des Testbildes und
> Neustart X-Server hat er die Änderungen nicht übernommen.
Mach' doch mal
egrep 'WW|EE|Using' /var/log/Xorg.0.log
Dann siehst Du, welches Konfigfile er benutzt (da mal reingucken, ob
das die Werte enthaelt, die Du angegeben hast) und ob/welche Probleme
P.S.: Wenn ich mich recht entsinne ist das eine englisch-sprachige
Mailingliste, vielleicht haette die Anfrage in Englisch mehr Resonanz
"What're quantum mechanics?"
"I don't know. People who repair quantums I suppose."
--Rincewind, Terry Pratchett "Eric"
Matthias Hopf wrote:
> Will do. Though I don't have any register documentation, so I have to
> wait for patches from upstream.
Well, I've been wrestling with this still, just can't let go of it. I
was able to successfully build a dual-head configuration file that is
functional. It is not perfect, but it works for now. I'm using the
merged framebuffer solution rather then xinerama.
My main gripe is that I can't get my two monitors to the resolution I'd
like. The primary is running at 1024x768 but can do 1280x1024. My
second monitor will do at least 1600x????
What I would like is a configuration that runs my primary at 1280x1024
and doesn't scroll. I can't seem to get it past 1024x768. Right now
I've got a bit of a scroll. The worse thing about that is that when I
scroll down, I get a vertical bar that's about an inch wide that flashes
across the screen. Ugly.
I figured I'd post the relevant portions of the config file for the
archives. Do you think I should still file a bug on the xinerama approach?
Here's the relevant config stuff:
DisplaySize 375 305
# HorizSync 30-81 # analog
HorizSync 30-63 # digital
Identifier "mergedfb screen"
Device "Radeon mergedfb"
BoardName "RV280 5961"
Identifier "Radeon mergedfb"
Option "MergedFB" "True"
Option "CRT2VRefresh" "50-180"
Option "CRT2HSync" "28-127"
Option "CRT2Position" "RightOf"
Option "MonitorLayout" "TMDS,CRT"
InputDevice "Keyboard" "CoreKeyboard"
InputDevice "Mouse" "CorePointer"
Option "Clone" "off"
Option "Xinerama" "off"
Screen "mergedfb screen"
Until later, Geoffrey
On Oct 28, 05 07:46:20 +0200, Anette Seiler wrote:
> >> If it would not work in Failsafe mode, I would say, that I had a driver
> >> problem or something like that. But it must be something else causing the
> >> problem. What could that be?
> >Perhaps you want to play around a bit with the options that are used
> >during failsafe login. E.g. select failsafe, press F2, and delete all
> >options (which only leaves framebuffer mode disabled, so you won't get
> >the splash screen).
> I did that. Even with all options deleted during failsafe mode, I could
> start sax or X-Windows without any problems. However, in normal mode, the
> problem persists.
Ok, the short term solution is to change all 'vga=XYZ' to 'vga=normal'
in /boot/grub/menu.lst. That will disable the framebuffer console on the
For the long term solution, please open a bug report on
http://www.opensuse.org/ and assign it directly to me
(mhopf(a)novell.com). I don't think we will commit much time into this (as
there is an easy workaround), but I would like to track the information
and whether the problem is solved in later SUSE Linux releases. Please
attach all information that is noted on http://www.opensuse.org/Bugs:X
I will add the workaround myself.
Matthias Hopf <mhopf(a)suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat(a)mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de
Dual head functioning in 9.1,9.2,9.3 as follows:
ati 9200 with dvi and vga outputs.
19" samsung syncmaster 910t digital lcd
22" viewsonic p225f pro crt
I've had a dual head configuration working since 9.1. I've upgraded
thsi same box through 9.2 and 9.3. Each time I had to use the old
config file from 9.1 to get my dual head configuration working again.
I just upgraded this same box to 10 and I can not get my dual head
configuration working now.
Worse, it appears that sax2 has removed much of the functionality of the
previous versions. In previous versions, I could add/delete a
particular video card. With 10, I have no such option. It identifies
the proper card, ati 9200, but does not see the second output. The
only way I can get sax2 to 'see' two video is to manually edit the
xorg.conf file. I'm up to it, but can't get it to work.
After fighting with it for a while, it suddenly properly identifies my
samsung monitor and I have finally got it to properly recognize the
viewsonic, yet when X starts, the secondary monitor (viewsonic) does not
get a signal.
The only warnings I receive in the log file are:
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode
I assume the last one might have something to do with it, although when
the box starts up, the console is displayed on the secondary (viewsonic)
monitor. When X runs, it's on the primary (samsung).
Any suggestions would be wonderful.
Until later, Geoffrey
After successfully installing Suse 10 on my Averatec Notebook, I installed
Suse 10 on my Dell Latitude CPx (Pentium III) Notebook. The installation went
without any problems.
But when I started the new system on the Dell, all troubles began. Instead of
getting the normal splash screen that, after a while, opens the KDE system, I
get a black screen, that slowly gets grey-white. It is as if something is
burning up the monitor from the left bottom corner. Later pink and blue
vertical stripes appear and the normal chimes that KDE has started. I cannot
I first thought, that I had configured the graphics hardware wrongly. I
installed Suse again - same results.
Then I started Suse in Failsafe Mode. After I logged in and entered "starx"
X-Windows and KDE started as they always do. I left X-Windows and started
sax2 and could configure X as normal. I made sure that all the settings were
right (of course they were, as in Failsafe Mode I had no problems with X).
Then I restarted in Normal mode. I still have the same problem with X-Windows.
When I start sax2 the same happens. When I start Yast and try to configure
the display, the same happens.
If it would not work in Failsafe mode, I would say, that I had a driver
problem or something like that. But it must be something else causing the
problem. What could that be?
On my SuSE 10.0 box I'm running multiple X-Servers parallely (one
instance on VT7 and another one on VT8). As Desktop manager I use KDM,
so this was done by simply adding one more static Server in my kdmrc.
Until this point everything works fine, but trying to make these two
displays remotely controllable by enabling the option "Allow Access to
Display using VNC Protocol" in SaX2 results in the following problem:
After Booting I'm switched to the display on VT8 (not VT7 as usual)
where I find a KDM login screen. Trying to switch to VT7 by pressing
Ctrl-Alt-F7 results in a black screen with ablinking bar cursor in the
upper left corner - no X Display there! :-( Switching back to another VT
is not possible because there is no response on any input from the
keyboard any longer. Logging in on VT7 via VNC does not work, while VT8
is acassible via VNC as expected.
How can I make both of the Displays available via VNC?
Stefan Dirsch writes:
> > >
> > > I know, that this is offtopic question, but why mach64 isn't supported?
> > >
> > > I have to made magic things to makes it works, but successfull...
> > >
> > It is supported. I've tested at least one card.
> I think he's talking about mach64 DRI support ...
The original question wasn't clear about this...
I went from 9.3 PRO to 10.0 by following the manual. I booted off of the 10.0 CD, selected "Upgrade", chose my partition that had 9.3 PRO installed from the list and it worked flawlessly for me.
From: on4hu [mailto:email@example.com]
Sent: Tuesday, October 18, 2005 10:01 AM
Subject: [suse-xfree86] upgrade from 9.2 to 10.0
i will know if existe the possibility tu upgrade from the version SuSe Novell
9.2 PRO to the new 10.0 and How to?? because i found SuSe not to friendly to
if no possibility exist i thing i will move to Mandriva onother distribution
Please use mailto:firstname.lastname@example.org or on4hu(a)belgacom.net
WEB server: http://on4hu.be
FTP server: ftp://on4hu.be
Computer are like air-conditioners, they stop working
properly as soon as you open windows.
To unsubscribe check the List-Unsubscribe header
For additional commands, email: suse-xfree86-help(a)suse.com