12.2 and ATI issues HELP!

I just upgraded from 12.1 to 12.2 and now I cant boot without going into safe mode.
I have read most the docs about the issues with ATI drivers.
I am using a x1300 that supports 2 monitors off one connection but the new 12.2
only sees one? I have tried different drivers and work arounds. Both monitors work in safe mode but I cannot get a spanned desktop and obviously having to boot into safe mode always is messed up.
Anyone know how to fix this…
I used to just have to enter nomodeset at the boot screen but that doesnt help in 12.2
Help?
Thanks

Here are the hardware specs
32: PCI 200.0: 0300 VGA compatible controller (VGA)
[Created at pci.319]
Unique ID: B35A._2VwIu82JQ8
Parent ID: _Znp.XC+doSVaZZA
SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: graphics card
Model: “ATI Radeon X1300/X1550”
Vendor: pci 0x1002 “ATI Technologies Inc”
Device: pci 0x7146 “Radeon X1300/X1550”
SubVendor: pci 0x1545 “VISIONTEK”
SubDevice: pci 0x2292
Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable)
Memory Range: 0xd0500000-0xd050ffff (rw,non-prefetchable)
I/O Ports: 0x2100-0x21ff (rw)
Memory Range: 0xd0000000-0xd001ffff (ro,non-prefetchable,disabled)
IRQ: 10 (no events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: “pci:v00001002d00007146sv00001545sd00002292bc03sc00i00”
Driver Info #0:
XFree86 v4 Server Module: radeonhd
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #14 (PCI bridge)

33: PCI 200.1: 0380 Display controller
[Created at pci.319]
Unique ID: 2Oa+.+yiCCARzn5C
Parent ID: _Znp.XC+doSVaZZA
SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:02:00.1
SysFS BusID: 0000:02:00.1
Hardware Class: graphics card
Model: “ATI RV515 [Radeon X1300] (Secondary)”
Vendor: pci 0x1002 “ATI Technologies Inc”
Device: pci 0x7166 “RV515 [Radeon X1300] (Secondary)”
SubVendor: pci 0x1545 “VISIONTEK”
SubDevice: pci 0x2293
Memory Range: 0xd0510000-0xd051ffff (rw,non-prefetchable,disabled)
Module Alias: “pci:v00001002d00007166sv00001545sd00002293bc03sc80i00”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #14 (PCI bridge)

xrandr output
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 77.0*

lspci output

02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV515 [Radeon X1300]
02:00.1 Display controller: Advanced Micro Devices [AMD] nee ATI RV515 [Radeon X1300] (Secondary)

This thread should have gone in the hardware forum, as its a driver related issue. Anyway:

Likely a DMS-59 connector: DMS-59 - Wikipedia, the free encyclopedia

12.2 only sees one? I have tried different drivers and work arounds.
yeah, from your randr output it is clear that the video adapter is not being configured correctly … to avoid repeating myself, see: http://forums.opensuse.org/english/get-technical-help-here/hardware/475440-how-define-dual-monitors-radeon-driver-opensuse-12-2m4.html#post2466761

Both monitors work in safe mode but I cannot get a spanned desktop and obviously having to boot into safe mode
Anyone know how to fix this…
Lets start by seeing the contents of your xorg log (if unfamiliar, its found in /var/log and you have to be root to access it … then use SUSE Paste )

SUSE Paste

Thanks Tyler_K
Just put log in SUSE Paste Link is above…
I will review your doc

Hi, that’s a log from when you boot in safe mode, but we need to see a log from when you do a regular boot

I will review your doc
Its just a similar case, so provides some background of what’s going on …

Yes i had reviewed that thread before and I think I understand pretty much the problem…I hope this is what your needing…It never successfully boots outside of safe mode…it hangs at “ATI EVENTS” so I switched consoles and created the logs while it was hung. And by hung I should clarify
hung just before the splash/logon screen. I also saw threads regarding this and older hardware.

SUSE Paste

Current Operating System: Linux linux-cb 2.6.27.42-0.1-pae #1 SMP 2010-01-06 16:07:25 +0100 i686
Build Date: 02 July 2009  08:02:13AM

between these two lines (5 and 6), I would have expected the kernel command line … can you report what your grub kernel boot command line is

(==) Using config file: "/etc/X11/xorg.conf"

line 15 … you’re using a user supplied xorg.conf file
1 - provide us with the contents of that file
2 - more interestingly, I would want to see your description and the xorg log results of what happens when you rename the xorg,conf and let automagic configuration of X take place




  1. (--)  PCI:*(0@2:0:0) unknown vendor (0x1002) unknown chipset (0x7146) rev 0,  Mem @ 0xc0000000/0, 0xd0500000/0, I/O @ 0x00002100/0, BIOS @  0x????????/131072 
  1. (--) PCI: (0@2:0:1) unknown vendor (0x1002) unknown chipset (0x7166) rev 0, Mem @ 0xd0510000/0 



lines 99-100 … Its saying it doesn’t recognize the graphics adapter (which is not surprising and is what I mentioned earlier) … in any regard, vendor 1002 is AMD so that isn’t really the case that it is “unkonwn”… and I doubt on the chipset too.

What is the subsystem id for that card too? ("/sbin/lspci -vnn") … you might want to submit to the PCIIDs site.

Lastly, later in the log I see that it sets things up using the antiquated “radeonhd” driver.
Which further begs the question if you are passing nomodeset in the kernel boot code (you mentioned something about it earlier … but there is no kernel boot command given in the log so I can’t confirm)? Or are you calling that driver (radeonhd) from the xorg.conf file?

Ideally you want to get the “radeon” driver going for this card.

Please try again under automagic detection and configuration conditions.

Kernel Commandline
http://paste.opensuse.org/51084736

Xorg.conf
SUSE Paste

Video Subsys
SUSE Paste

I have tried several options…added nomodeset to Kernel Commandline but Ihave it removed now…I also
tried nomodeset to option GUI commandline…
I will remove the xorg.conf file and let automagic try…then capture that log.

Okay, quick read to refresh my memory …

Absolutely get rid of that xorg.conf file – besides there being a lot of cruft in there, the fglrx driver is being called … while the prop driver would have supported your card in the past, it most certainly doesn’t any more … nor the legacy fglrx for that matter … (I suspect, though don’t know for sure, that an fglrx installation attempt would fail/exit because of unsupported hardware) … I mention that only in case you were unaware … i.e. bottom line, support for your card is left to the OSS drivers.

Anyway, the nomodeset option has got to go to if you want to use the KMS supporting radeon driver … passing it (nomodeset) on the kernel boot command should trigger the radeonhd driver loading for your card (as evidenced) … whereas recent adapters fall back to the fbdev (likely only because they are not supported by the radeonhd).

I couldn’t really follow the suse paste for your kernel command line (as it looks like a highly redacted CIA document LOL), but from what I see, you should also get rid of the video mode info that you’re passing … (that stuff is only for the console framebuffer driver … which is fine if you are not going to use the radeon driver … but if you are going to use the radeon driver, know that it is a KMS (kernel mode setting, as opposed to UMS, user mode switching/setting) driver, which will do double duty – both for the console framebuffer and for X … And, being of the KMS variety, it handles mode switching itself, or at least, will do a much better job. Hence there is no need to be passing such parms…doing so may actually be problematic.

02:00.0  VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI  RV515 [Radeon X1300] [1002:7146] (prog-if 00 [VGA controller])
        Subsystem: VISIONTEK Device [1545:2292]

....
02:00.1 Display controller [0380]: Advanced Micro Devices [AMD] nee ATI RV515 [Radeon X1300] (Secondary) [1002:7166]
        Subsystem: VISIONTEK Device [1545:2293]

Yeah, you should consider submitting that info to The PCI ID Repository
I not sure how you’d do it for a card like yours … while I know that there are others that are dual GPU, offhand, I can only think of the FirePro 2450, and its info is not in the database (so no reference to go by)

Never heard back on this one, but I just thought of something in regards to this case:

while the prop driver would have supported your card in the past, it most certainly doesn’t any more … nor the legacy fglrx for that matter … (I suspect, though don’t know for sure, that an fglrx installation attempt would fail/exit because of unsupported hardware) … I mention that only in case you were unaware … i.e. bottom line, support for your card is left to the OSS drivers.

dual GPU
If this truly is a dual GPU card, then the only choices for using the two adapters would mean either configuring the system:

  • as two X Display Screens (i.e. one X session, two separate Screens … :0.0 and :0.1) or
  • as two separate X Displays (i.e two X sessions, and one Screen per session … :0.0 and :1.0)

I highly doubt the use of the latter, but rather the former. Specifically, I suspect that, in the past, he was using the fglrx and that it simply joined the two screens via Xinerama or Big Desktop or whatever ATI calls it.

Similar can be done with the OSS drivers, though with manual configuration of Xorg, as I doubt the automagic would work in this case (two adapters).

So, if the above assumptions are correct, the only thing I’m not clear on is that the OP said that they were using the system in 12.1 prior to upgrading to 12.2 (whereupon they encountered the problem). The trouble with that is the old graphics adapter and support for it via fglrx. I don’t know when it (support for that adapter) would have been cut off by the prop driver, but 12.1 strikes me as being too far after the fact. So, something doesn’t mesh…

Sorry for the stupid question … but would be buying a cheap ATI card ( ~ $35 ) supported by the fglrx driver not be an option - or even a cheap Nvidia for about the same price? I might have missed something in this thread though.

I’m darn sure that a $20-35 HD 5-6000 series card, or an equivalent nvidia based GTwhatever, supported by either the prop drivers or the OSS drivers, would do just fine … but where is the fun in that lol!

I can personnally think of some ways to have fun which do not involve fighting with old ATI chipsets, but you do what you want. :wink:

I kind of suspect that the OP has already decided that upon their own … but anyways, the information may be helpful to someone else, either here in openSUSE land or out in the great yonder opened up to us by the way of google.