https://bugzilla.novell.com/show_bug.cgi?id=343734
User funtasyspace@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=343734#c23
--- Comment #23 from Jörg Hermsdorf 2008-04-22 12:40:24 MST ---
I just installed Catalyst 8.4. Now the situation is the following:
# init 3
# sax2 -r -m 0=fglrx
-> SaX2 Suggestion -> "Change Configuration"
-> Change pre-selected resolution from "1280x1024 (SXGA)" to "1600x1200 (UXGA)"
-> Change pre-selected Monitor from "VESA 1280x1024@60HZ" to "ELSA AG ECOMO
21M98"
-> Press "OK"
-> Press "Test"
OK, up to here it works again. My system doesn't freeze and test screen (2nd
Xserver instance) is working fine.
-> Press "Save"
-> "Configuration Saved" dialog apears in previous SaX2 session. Exit SaX2 now?
-> Press "Yes"
Now screen goes black, Monitor On-Screen-Display says "No Input Signal". Can't
switch between consoles anymore (well, maybe it switches, but I don't see
anything). Framebuffer is gone!
But using Catalyst 8.4 I can at least login via SSH from another machine and
switch to runlevel 5 again, which starts Xorg/KDM on virtual console 7 again. I
can login to my KDE session and everything seems fine so far. Only framebuffer
has crashed / is still missing.
With Catalyst 8.4 I can also switch the user now and start a second Xserver
without freezing the system. I switched 20 times between the two sessions
(CTRL+ALT+F7 and CTRL+ALT+F8) and also did not experience any freezes or
oddities so far. After I rebooted, the framebuffer is back again and I can
switch to the other virtual consoles, too.
So the only remaining issue is, that SaX2 still kills the framebuffer. And on
virtual console 10 I see these two error messages now:
kernel: [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* IRQMGR returned error
1 when trying to enable interrupt source 20008000
kernel: [fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* IRQMGR returned error
1 when trying to enable interrupt source 10000000
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.