Well, nowadays at least switching between Eyefinity and non Eyefinity profiles works quite well.
However whenever I return from Eyefinity I have to exchange both DVI-Cables.
Otherwise I couldn't rotate my monitor. Bliss! Maybe a clean reinstall of the Catalysts might solve that?
I also enjoyed a brief time, after either installing new drivers or after my PC was used for some LAN gaming at an so far unknown screen, when I could actually boot up my PC with all 3 screens turned on.
Then I finally felt the urge to Eyefinity some more, and after that the old issue popped up with a vengeance. Now it's not enough to boot with just the Display Port connected monitor turned off, no I also need to turn off my primary DVI connected Dell monitor.
However that might have changed as of today as I again played a bit of L4D2 in Eyefinity and had to do the dvi-switcharoo at back of the card. So my newly primary DVI connected Samsung monitor might be able to stay turned on, as it had been the case previously during the boot sequence? I shall see tomorrow and report!
That however has lead me to believe that the boot issue might actually be a driver issue, strange as it sounds.
Otherwise I couldn't think of a reason why it started happening exactly after I returned to Eyefinity. And not just this once I believe exactly that was the case before once or twice.
Showing posts with label problem. Show all posts
Showing posts with label problem. Show all posts
Tuesday, April 13, 2010
Friday, February 12, 2010
Thinking about things
Well again, as is obvious profiles are not yet working as they should.
After a quick read over at WSGF I did indeed come to the conclusion that profiles that switch between eyefinity and non-eyefinity definitely do not work as of now. Well, I can live with that, painful as it may be.
I can even live with having to reload the same profile 3 times, before Catalyst correctly remembers the location of the monitors, when switching between two non-Eyefinity profiles.
What I still can't live with, is Catalyst changing my desktop when I turn one screen off.
E.g.: Yesterday night, I would have liked to watch a streaming video (NFL Network on NFL Gamepass HD) while going to sleep.
I would have preferred to watch it on my middle monitor, my Samsung 2493HM that is connected via DVI. I would have liked to turn off my other two screens though.
So I did.
And well, as soon as I turned my display port connected HP off, the image vanished from the other two screens too.
So where did it go? Well obviously to my HDMI-connected LG TV. While that in this instance is actually an okay outcome, it still goes to show the problem.
Suddenly and only by turning monitors off, I'm in 1 screen mode.
And as previous experience shows, had I changed the channel on the TV, it probably would have fucked up the desktop again.
*sigh*
After a quick read over at WSGF I did indeed come to the conclusion that profiles that switch between eyefinity and non-eyefinity definitely do not work as of now. Well, I can live with that, painful as it may be.
I can even live with having to reload the same profile 3 times, before Catalyst correctly remembers the location of the monitors, when switching between two non-Eyefinity profiles.
What I still can't live with, is Catalyst changing my desktop when I turn one screen off.
E.g.: Yesterday night, I would have liked to watch a streaming video (NFL Network on NFL Gamepass HD) while going to sleep.
I would have preferred to watch it on my middle monitor, my Samsung 2493HM that is connected via DVI. I would have liked to turn off my other two screens though.
So I did.
And well, as soon as I turned my display port connected HP off, the image vanished from the other two screens too.
So where did it go? Well obviously to my HDMI-connected LG TV. While that in this instance is actually an okay outcome, it still goes to show the problem.
Suddenly and only by turning monitors off, I'm in 1 screen mode.
And as previous experience shows, had I changed the channel on the TV, it probably would have fucked up the desktop again.
*sigh*
Monday, February 8, 2010
The overclocking issue revisited
Today, about 5 days after first having the problem with my processor overclock not working anymore I found the time to do some testing.
I shall repeat the issue:
CPU was overclocked for nearly 3 years without an issue. About a week ago, about the same time I received my Display Port capable HP Monitor my PC would only boot when not overclocked. Otherwise it reset itself right after the memory check / message showing the "Memory runs in Dual Channel Interleaved". This is right before the detection of SATA/IDE devices. It did't matter how minor or major the overclock was. Even it technically wasn'T a overclock it still wouldn't boot completely.
My configuration is:
Intel Core2Duo Conroe E6400 2.13ghz (overclocked to 3.2ghz)
Gigabyte 965P-DQ6
2*1024 Corsair XMS2 8500
2*2048 AData Vitesta
Asus Radeon 5850
2* Seagate Barracuda 7200.10 500gb
Samsung F2 640gb
Sasmung F3 1000gb
Cougar 750W Poer Supply
Aerocool ExtremEngine 3T (which is annoyingly small)
Well, first I tried to check the Ram, while Memtest86 didn't find any issue with it I decided to better be safe than sorry.
Taking out both 2048 sticks it booted... hm!
Installing one of the 2048 again - no boot.
Taking out both 1024 sticks while leaving both 2048 in - no boot.
Installing just one 2048 - booting.
Hm... so I guess it ain't the ram after all.
Well I remember not yet feeling quite at ease with the F3 which found its way into my cramped case just before Christmas. So lets take 'em out. Disconnecting all HDDs but leaving all the ram in - no boot.
*sigh*
Well... what else is new? And what did I change right about the time the trouble started? Yeah... that's right, the Display Port-Screen arrived and I connected it instead of the DP-VGA Adapter that lead to my TV.
Hm... Well, so let's imagine that this might be the general area of where to look.
So what's the difference? The TV was never turned on when I turned the PC on. The Display Port capable HP Monitor on the other hand always was.
Lets have a look... or rather no look and disconnect the Display Port. Surprise, surprise, it lives! Reconnecting the DP-Cable and leaving the monitor off, it boots again. Turning the monitor on, no boot.
So there we go, for whatever reason there might be, overclocking a Core2Duo in a Gigabyte 965p-DQ6 mainboard with more than 2gb of RAM and a Radeon 5850 and a Display Port connected device that is turned on results in not being able to overclock anymore. Brilliant!
Anyone care to explain this phenomenon to me or if it happens in different configurations as well?
I shall repeat the issue:
CPU was overclocked for nearly 3 years without an issue. About a week ago, about the same time I received my Display Port capable HP Monitor my PC would only boot when not overclocked. Otherwise it reset itself right after the memory check / message showing the "Memory runs in Dual Channel Interleaved". This is right before the detection of SATA/IDE devices. It did't matter how minor or major the overclock was. Even it technically wasn'T a overclock it still wouldn't boot completely.
My configuration is:
Intel Core2Duo Conroe E6400 2.13ghz (overclocked to 3.2ghz)
Gigabyte 965P-DQ6
2*1024 Corsair XMS2 8500
2*2048 AData Vitesta
Asus Radeon 5850
2* Seagate Barracuda 7200.10 500gb
Samsung F2 640gb
Sasmung F3 1000gb
Cougar 750W Poer Supply
Aerocool ExtremEngine 3T (which is annoyingly small)
Well, first I tried to check the Ram, while Memtest86 didn't find any issue with it I decided to better be safe than sorry.
Taking out both 2048 sticks it booted... hm!
Installing one of the 2048 again - no boot.
Taking out both 1024 sticks while leaving both 2048 in - no boot.
Installing just one 2048 - booting.
Hm... so I guess it ain't the ram after all.
Well I remember not yet feeling quite at ease with the F3 which found its way into my cramped case just before Christmas. So lets take 'em out. Disconnecting all HDDs but leaving all the ram in - no boot.
*sigh*
Well... what else is new? And what did I change right about the time the trouble started? Yeah... that's right, the Display Port-Screen arrived and I connected it instead of the DP-VGA Adapter that lead to my TV.
Hm... Well, so let's imagine that this might be the general area of where to look.
So what's the difference? The TV was never turned on when I turned the PC on. The Display Port capable HP Monitor on the other hand always was.
Lets have a look... or rather no look and disconnect the Display Port. Surprise, surprise, it lives! Reconnecting the DP-Cable and leaving the monitor off, it boots again. Turning the monitor on, no boot.
So there we go, for whatever reason there might be, overclocking a Core2Duo in a Gigabyte 965p-DQ6 mainboard with more than 2gb of RAM and a Radeon 5850 and a Display Port connected device that is turned on results in not being able to overclock anymore. Brilliant!
Anyone care to explain this phenomenon to me or if it happens in different configurations as well?
Quirky Catalyst
Well as indicated before there is something not working as I would have hoped for it to:
This includes saving of profiles in the Catalyst Control Center as well as turning monitors on and off.
In normal operation I have my Dell 2407wfp (DVI) in portrait mode on the left, in center my Samsung 2493HM (DVI) in landscape and to my right my HP LA2405wg in landscape.
My Samsung is my primary screen. On it are: mail client, ICQ, other stuff that periodically asks for attention.
On my Dell I primarily surf. Using Firefox and Internet Explorer.
And the HP as latest addition is still kind of looking for a job.
I'm running Windows 7 Pro 64 bit and the latest Catalyst 10.1 drivers.
I also have my LG 32LF2500 connected to my card via HDMI to watch streaming TV from time to time.
Ideally I would save three profiles:
1) Eyefinity: Dell+Samsung+HP 5760*1200
2) Non-Gaming: Dell (portrait), Samsung (landscape), HP (landscape)
3) Movies: LG, Samsung, HP
I actually can save those profiles. Regrettably what isn't loaded when trying to load a profile is the position of the screens. Though sometimes it actually loads that correctly too.
Also forgotten is which screen is the primary one. Annoying.
And after using the TV with 120 pixels less in height, sometimes the driver seems to think that the PC Monitors (or at least any one of them) is also lacking in height.
Well, that's annoying but wouldn't even be that bad.
Much worse is that it also switches the configuration when screens are turned off.
E.g.: When using setup 3 with the TV I like to turn off the PC Screens. If I then switch away from the HDMI Input on the TV one of the turned off Monitors suddenly switches its windows with the TV (i.e.: The video stream from the tv is now on the pc monitor while the mail client, icq and web browser are on the tv instead of the monitor. The funny part of this is, that the Monitor stays the primary display through all of this.)
And that is really annoying. Especially when lying in bed and not wanting to get up again to return the settings to what they are supposed to be.
I've got a tough time wrapping my head around this. I don't really understand why it is hard to just leave the windows on the screen I left them on, and ignore any change in what is turned on and what is turned off.
I also don't quite get why it doesn't actually restore my profiles the same way I saved them. Or rather, why it seems to guess what I saved and most of the time guesses wrong.
Oh well, that's the breaks I guess.
This includes saving of profiles in the Catalyst Control Center as well as turning monitors on and off.
In normal operation I have my Dell 2407wfp (DVI) in portrait mode on the left, in center my Samsung 2493HM (DVI) in landscape and to my right my HP LA2405wg in landscape.
My Samsung is my primary screen. On it are: mail client, ICQ, other stuff that periodically asks for attention.
On my Dell I primarily surf. Using Firefox and Internet Explorer.
And the HP as latest addition is still kind of looking for a job.
I'm running Windows 7 Pro 64 bit and the latest Catalyst 10.1 drivers.
I also have my LG 32LF2500 connected to my card via HDMI to watch streaming TV from time to time.
Ideally I would save three profiles:
1) Eyefinity: Dell+Samsung+HP 5760*1200
2) Non-Gaming: Dell (portrait), Samsung (landscape), HP (landscape)
3) Movies: LG, Samsung, HP
I actually can save those profiles. Regrettably what isn't loaded when trying to load a profile is the position of the screens. Though sometimes it actually loads that correctly too.
Also forgotten is which screen is the primary one. Annoying.
And after using the TV with 120 pixels less in height, sometimes the driver seems to think that the PC Monitors (or at least any one of them) is also lacking in height.
Well, that's annoying but wouldn't even be that bad.
Much worse is that it also switches the configuration when screens are turned off.
E.g.: When using setup 3 with the TV I like to turn off the PC Screens. If I then switch away from the HDMI Input on the TV one of the turned off Monitors suddenly switches its windows with the TV (i.e.: The video stream from the tv is now on the pc monitor while the mail client, icq and web browser are on the tv instead of the monitor. The funny part of this is, that the Monitor stays the primary display through all of this.)
And that is really annoying. Especially when lying in bed and not wanting to get up again to return the settings to what they are supposed to be.
I've got a tough time wrapping my head around this. I don't really understand why it is hard to just leave the windows on the screen I left them on, and ignore any change in what is turned on and what is turned off.
I also don't quite get why it doesn't actually restore my profiles the same way I saved them. Or rather, why it seems to guess what I saved and most of the time guesses wrong.
Oh well, that's the breaks I guess.
The story so far...
My first Eyefinity trial happened about 3 weeks ago at the dawn of the new year.
It was quite interesting but rather short lived and not in a very harmonic way.
There were my two 24 inch PC-screens, a Dell 2407wfp and a Samsung 2493HM both natively running in 1920*1200 and connected via DVI. And then there was my TV, a LG 32LF2500 running 1920*1080 connected to my Radeon 5850 by a Display Port - VGA adapter.
While obviously just seen as a first taste of what was yet to come, with my two PC-screens stretching the image a bit to their native resolution and differently sized displays, it still was very impressive.
The first impression of Race Driver: Grid blew me away. And mind you, I'm not even talking about playing, but just the menu. Incredible.
Racing was rather nice too, however I noticed some not so slight slowdowns with everything turned to maximum (except FSAA which was turned off).
Oh well, off to Team Fortress 2 I went and validated my first impression. Yep... Eyefinity is what I imagined it to be. Actually much more than that.
I also used my TV to watch streaming videos from my PC (NFL Gamepass), and noticed the dreaded screen flicker. While not necessarily enough to annoy it was a slight negative. But for the time being the screen turning black for a second once per hour would have to make do.
Until this Tuesday when I finally received my 3rd 24" PC screen with 1920*1200 pixels. And also a display port. Granted it was the lowest priced one I could find, a HP LA2405wg but due to a number of mix ups I got it for a great price. Downside to this was a rather long waiting time.
Anyhow, that was this Tuesday, and I connected it.
And it worked. Beautifully indeed. However Grid, Dirt2 did not run as smoothly as I would have hoped. Admittedly 5760*1200 is a whole lot of pixels for a Radeon5850, but still, I would have hoped for fewer slowdowns while playing.
Even TeamFortress2 did dip down to 20 fps frequently.
*sigh*
Then again I certainly could have turned down the graphics setting by a fair margin to receive playable frame rates. Indeed I was set on doing his when a slight disaster struck.
My venerable Core2Duo E6400 (I nicknamed him Conroe), overclocked to >3Ghz since I got him nearly 3 years ago on his Gigabyte 965P-DQ6 mainboard suddenly didn't want to be overclocked anymore.
Or rather it did want to as I certainly managed to validate by using easy tune instead of the BIOS setting that worked before. But after the Memory Check and the Message that my Memory "run in Dual Channel Interleaved" right before taking stock of the attached SATA/IDE Drives the PC would reboot only to start with stock speeds again. That would happen even with very moderate overclocks. Actually even if just setting PCIe frequency to 100mhz instead of "Auto" it wouldn't completely boot.
Well that certainly was quite a downer right there. Especially considering that I didn't quite understand the reasons for. I would come to learn and understand. But before I found time to test for the faulty component I did notice some quirks with the Catalyst 10.1 drivers.
It was quite interesting but rather short lived and not in a very harmonic way.
There were my two 24 inch PC-screens, a Dell 2407wfp and a Samsung 2493HM both natively running in 1920*1200 and connected via DVI. And then there was my TV, a LG 32LF2500 running 1920*1080 connected to my Radeon 5850 by a Display Port - VGA adapter.
While obviously just seen as a first taste of what was yet to come, with my two PC-screens stretching the image a bit to their native resolution and differently sized displays, it still was very impressive.
The first impression of Race Driver: Grid blew me away. And mind you, I'm not even talking about playing, but just the menu. Incredible.
Racing was rather nice too, however I noticed some not so slight slowdowns with everything turned to maximum (except FSAA which was turned off).
Oh well, off to Team Fortress 2 I went and validated my first impression. Yep... Eyefinity is what I imagined it to be. Actually much more than that.
I also used my TV to watch streaming videos from my PC (NFL Gamepass), and noticed the dreaded screen flicker. While not necessarily enough to annoy it was a slight negative. But for the time being the screen turning black for a second once per hour would have to make do.
Until this Tuesday when I finally received my 3rd 24" PC screen with 1920*1200 pixels. And also a display port. Granted it was the lowest priced one I could find, a HP LA2405wg but due to a number of mix ups I got it for a great price. Downside to this was a rather long waiting time.
Anyhow, that was this Tuesday, and I connected it.
And it worked. Beautifully indeed. However Grid, Dirt2 did not run as smoothly as I would have hoped. Admittedly 5760*1200 is a whole lot of pixels for a Radeon5850, but still, I would have hoped for fewer slowdowns while playing.
Even TeamFortress2 did dip down to 20 fps frequently.
*sigh*
Then again I certainly could have turned down the graphics setting by a fair margin to receive playable frame rates. Indeed I was set on doing his when a slight disaster struck.
My venerable Core2Duo E6400 (I nicknamed him Conroe), overclocked to >3Ghz since I got him nearly 3 years ago on his Gigabyte 965P-DQ6 mainboard suddenly didn't want to be overclocked anymore.
Or rather it did want to as I certainly managed to validate by using easy tune instead of the BIOS setting that worked before. But after the Memory Check and the Message that my Memory "run in Dual Channel Interleaved" right before taking stock of the attached SATA/IDE Drives the PC would reboot only to start with stock speeds again. That would happen even with very moderate overclocks. Actually even if just setting PCIe frequency to 100mhz instead of "Auto" it wouldn't completely boot.
Well that certainly was quite a downer right there. Especially considering that I didn't quite understand the reasons for. I would come to learn and understand. But before I found time to test for the faulty component I did notice some quirks with the Catalyst 10.1 drivers.
Subscribe to:
Posts (Atom)