PDA

View Full Version : two minor problems with 1.6b3

energyman
01-15-2009, 09:29 AM
Hi,
first minor problem, ramspeed, is it intentional?
building for Linux 2.6.28r4 AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
compiler is gcc, linker is gcc, assembler is as
compiler's flags are -Wall -O
linker's flags are -Wl,-O -Wl,-s

WARNING! BUILDING FOR AN UNSUPPORTED OPERATING SYSTEM AND\OR ARCHITECTURE!
Please don't be shy to tell us some information about your CPU architecture,
OS version, compiler, linker, assembler and their optimisation flags.

because if you tell ramspeed the system, more tests are built AND it runs a bit faster.

Second problem:
as soon as pts runs - and I am talking about install, not any tests, my screen starts to blink. Very annoying. It also blinks when running the memory bandwidth test or ramspeed.
Hardware: AmdX2 6000, Amd 770 chipset, HD3870 card, 9.2preview driver.
Michael
01-15-2009, 02:16 PM
Regarding the ramspeed problem, that would be a problem with the test itself not being optimized for the Athlon 64 X2 6000+ evidently.

Regarding the blinking problem, can you explain it more? Is it after each test or how frequent? Does it happen with any other tests?
energyman
01-15-2009, 05:18 PM
it happens as soon as pts runs. Installing tests? Display blinks infrequently. System-info? It doesn't even stop blinking anymore - it is like the blinking it does when amdcccle starts and spams Xorg.0.log with all the resolutions. Running a test? (ramspeed, memory-bandwidth) it blinks.
The thing about ramspeed - it optimizes well, if you give it the Linux amd64 option - would be nice to pass options to the tests when installing.
Kano
01-15-2009, 05:37 PM
Does it blink when running

xrandr

in the console?
energyman
01-15-2009, 06:29 PM
yes, a lot.
Michael
01-15-2009, 06:30 PM
yes, a lot.

That's the problem there. Some graphics information is parsed using xrandr.
energyman
01-15-2009, 06:38 PM
yeah, but while installing tests? or running a test like ramspeed? I would understand this while running system-info or graphics tests, but memory-bandwidth?
Michael
01-15-2009, 07:13 PM
yeah, but while installing tests? or running a test like ramspeed? I would understand this while running system-info or graphics tests, but memory-bandwidth?

Because it still needs to report the GPU and other graphics information in the results and also there are some graphics-related variables that are exported to test scripts, which is done to all tests, just not ones marked Graphics or anything.
Kano
01-15-2009, 07:52 PM
That's a problem of the graphics driver.
energyman
01-15-2009, 11:15 PM
Because it still needs to report the GPU and other graphics information in the results and also there are some graphics-related variables that are exported to test scripts, which is done to all tests, just not ones marked Graphics or anything.

but installing? installing ramspeed?
Michael
01-16-2009, 05:09 AM
but installing? installing ramspeed?

Yeah, some graphics-related variables are still exported there, such as the amount of video RAM.