Skip to content

Control RGB Leds of a Kingston Fury Beast/Renegade DDR5 RAM

Shell · active 2023-09-282026-06-17 (UTC)

Complete coverage26,755 / 26,755 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
172
Pushes
31
Pull requests
10
Issues
22
Stars
33
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 994 days from 2023-09-28 to 2026-06-17. Pushes: 31 total, peak 7 in a day. Pull requests: 10 total, peak 4 in a day. Issues: 22 total, peak 2 in a day. Comments: 62 total, peak 5 in a day. Stars: 33 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#39KeyofBlueS2026-06-17 00:48
    Kingston Fury DDR5 RAM in slot 1(~8) not found on SMBus i2c-3.
  • Issue comment#39sousaesilvarafael2026-06-13 00:04
    Kingston Fury DDR5 RAM in slot 1(~8) not found on SMBus i2c-3.
  • Issue comment#38KeyofBlueS2026-03-22 21:43
    One of my FURY BEAST stick isn't recognized.
  • Issue#36KeyofBlueS2026-03-11 23:47
    No Kingston Fury BEAST\RENEGADE DDR5 RAM found!
  • Issue comment#36KeyofBlueS2026-03-11 23:17
    No Kingston Fury BEAST\RENEGADE DDR5 RAM found!
  • Pull request#37KeyofBlueS2026-03-11 21:47
  • Issue comment#36ChuckNorrison2026-03-10 21:49
    No Kingston Fury BEAST\RENEGADE DDR5 RAM found!
  • Issue#32banderlog2025-06-17 12:15
    Kingston Fury DDR5 RAM not found because of a single byte
  • Issue#26KeyofBlueS2025-06-17 08:06
    Ram bank ID not equal ram slot index
  • Issue comment#32KeyofBlueS2025-06-17 06:50
    Kingston Fury DDR5 RAM not found because of a single byte
  • Issue comment#32KeyofBlueS2025-06-14 14:32
    Kingston Fury DDR5 RAM not found because of a single byte
  • Issue comment#32banderlog2025-06-14 13:03
    Kingston Fury DDR5 RAM not found because of a single byte
  • Pull request#33KeyofBlueS2025-06-13 05:05
  • Issue comment#32KeyofBlueS2025-06-12 19:21
    Kingston Fury DDR5 RAM not found because of a single byte
  • Issue comment#32banderlog2025-06-12 14:16
    Kingston Fury DDR5 RAM not found because of a single byte
  • Issue#32banderlog2025-06-12 14:08
    Kingston Fury DDR5 RAM not found because of a single byte
  • Issue comment#30eclipsek202025-04-11 23:33
    RAM stick not found on SMBus
  • Issue comment#31KeyofBlueS2025-03-26 12:23
    Values for two_check_hex differ
  • Issue comment#31mattvink2025-03-26 00:46
    Values for two_check_hex differ
  • Issue#31mattvink2025-03-26 00:46
    Values for two_check_hex differ
  • Issue comment#31KeyofBlueS2025-03-25 19:48
    Values for two_check_hex differ
  • Issue#31mattvink2025-03-24 23:48
    Values for two_check_hex differ
  • Issue#30KeyofBlueS2025-02-21 13:53
    RAM stick not found on SMBus
  • Issue comment#30Sduck8652025-02-16 14:52
    RAM stick not found on SMBus
  • Issue comment#30Sduck8652025-02-16 12:12
    RAM stick not found on SMBus

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 33 stars here means stars gained during the window, not the repo's star count.