Your message dated Fri, 11 Apr 2025 13:23:45 +0000
with message-id <[email protected]>
and subject line Bug#1100889: Removed package(s) from unstable
has caused the Debian Bug report #562625,
regarding rovclock: Floating point exception on ATI Mobility Radeon HD 4570
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
562625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562625
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rovclock
Version: 0.6e-6
Severity: normal

On an Acer Aspire 5536G with an ATI Mobility Radeon HD 4570:

Pulska:~# rovclock -i
Radeon overclock 0.6e by Hasw ([email protected])

Found ATI card on 02:00, device id: 0x9553
I/O base address: 0x1000
Video BIOS shadow found @ 0xc0000
Invalid reference clock from BIOS: 0.0 MHz
Memory size: 0 kB
Memory channels: 1, CD,CH only: 0
tRcdRD:   3
tRcdWR:   1
tRP:      3
tRAS:     6
tRRD:     1
tR2W-CL:  1
tWR:      1
tW2R:     0
tW2Rsb:   0
tR2R:     1
tRFC:     13
tWL(0.5): 0
tCAS:     0
tCMD:     0
tSTR:     0
Floating point exception
Pulska:~#

The floating point exception shouldn't happen, I think.
/usr/share/doc/rovclock/README suggests trying -x 1432 or -x 2950
if -i does not show the correct frequency by default.
I tried those but they didn't make any difference in the output.
Then, if I try to change the memory clock:

Pulska:~# rovclock -m 400
Radeon overclock 0.6e by Hasw ([email protected])

Found ATI card on 02:00, device id: 0x9553
I/O base address: 0x1000
Video BIOS shadow found @ 0xc0000
Invalid reference clock from BIOS: 0.0 MHz
Pulska:~# echo $?
0
Pulska:~#

So, the exit code seems to indicate it worked, but the "Invalid
reference clock" message makes me suspect it didn't.  As rovclock
-i does not display the memory clock, I seem to have no way to
tell what rovclock did.

Please make rovclock support this display adapter, or if that is
not possible, at least clearly say so instead of terminating with
a floating-point exception, and set the exit code correctly.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rovclock depends on:
ii  libc6                         2.10.2-2   GNU C Library: Shared libraries

rovclock recommends no packages.

rovclock suggests no packages.

-- no debconf information

Attachment: pgpUtDV2Qv0Oj.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 0.6e-7.1+rm

Dear submitter,

as the package rovclock has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1100889

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to