Jump to content
HWBOT Community Forums

Strunkenbold

Crew
  • Posts

    2195
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by Strunkenbold

  1. Since there will be CPU-Z support for this, I moved now (hopefully) all E6 results over to the Toledo category. The 3700+ results still missing out.
  2. AFAIK this category goes back to a request on Discord. It has some sort of legitimation. The E6 is actually indeed a Toledo. These are harvested dual cores with one core disabled. AMD however actually never named them Toledo and CPU-Z doesn't detect them, which makes this topic complicated. You can read more after this post in german hwluxx forum. The question however is, if this category should stay. I postponed a decision on this for some time now. If I think about some other AMD CPUs which unlocks to different cores because they used different harvested cores for their lowcost variants, it wouldn't be the same logic for these, means I would have to separate them too.
  3. For some reason, results didnt update after you updated them. I did this now manually.
  4. https://hwbot.org/hardware/motherboard/pn63_s1/
  5. https://hwbot.org/hardware/motherboard/x12dpu_6/
  6. Already there: https://hwbot.org/hardware/motherboard/lnvnb161216_ryzen_soc/
  7. https://hwbot.org/hardware/motherboard/6515_104_xm6515_106_xm/
  8. Correct, you take the original part hwbot category and select how many cores you unlocked. The problematic part is, that CPUs change their names when they get unlocked. This was consistent source of confusion over the years though. https://www.cpu-world.com/info/AMD/Unlocking_cores_and_L3.html
  9. https://hwbot.org/hardware/motherboard/6abx2v/
  10. Is this pre-production / prototype board? Do you have a CPU-Z verification?
  11. No. It doesnt matter to what they unlock. I think its no secret that AMD used different harvested cores
  12. https://hwbot.org/hardware/motherboard/tusl2_m/
  13. https://hwbot.org/hardware/diskproduct/force_le/
  14. https://hwbot.org/hardware/motherboard/pro_h610t_d4/
  15. https://hwbot.org/hardware/videocard/radeon_pro_v520/
  16. https://hwbot.org/hardware/processor/xeon_e3_1205_v6/
  17. https://hwbot.org/hardware/motherboard/k8t8as/
  18. https://hwbot.org/hardware/videocard/verite_v2200_pci/ https://hwbot.org/hardware/videocard/verite_v2200_agp/ https://hwbot.org/hardware/processor/vortex86dx/ https://hwbot.org/hardware/motherboard/pca_6743/
  19. Yes I mean Device ID. https://pci-ids.ucw.cz/read/PC/10de Very likely subsystemID is different. Which is the reason, new driver get installed. IMO, if the new installed card doesnt match registry item under Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} a driver reinstall happens.
  20. Likely CPU-Z bug. Some other KM266 boards show also KM400 on their valid page. https://theretroweb.com/motherboards/s/asrock-k7vm3#expchips
  21. If there is no different PCI ID and specs are the same, we create no separate category, if that was your intention.
  22. Thx for this massive write-up. What you see here is a big mess because of some limitations the bot has since the beginning. If a GPU model is used in multiple product families, we have to add a second GPU Core like GA102' or GA102GL. I have only with a new core the possibility to link it to a new Subfamily. So most of the problems you see here is our laziness. And I honestly dont want to inflate our db with gazillions of the same cores just with an apostrophe on their end. I proposed years ago to have a similar organisation like the CPUs in the db. Means: Manufacturer >> Family (architecture) >> Subfamily (Product range) >> Specific Model. I dont know if this scheme is accepted by our owner and will be programmed. Until I dont have an answer, I wont do much work on this cause I dont want to do things twice and the effort for Nvidia would be huge. In the end we would need to a massive cleanup anyway, touching every card, but thats something I dont have time for at the moment. Mistakes like wrong GPU cores and specs will be fixed though, its best to write me a PM if you spot something. The question why AMD is organised another way is simple: I had the time for it back then and it felt necessary. The reason was AMD spawned multiple recycled cards with same specs but different names even under other under product families but GPU-Z cant distinguish them. To combine the cards I also had to remove the subfamilies and group every model under their specific architecture. I could ofc do the same for nvidia but again, it would be better to fix this the proper way. Fixed: Quadro RTX 5000/6000/8000 are listed as RT102/104GL cores, but I think should be TU104/102 cores Quadro RTX A6000 is listed as having a TU102 core, but I think it should be a GA102 core Geforce GTX 780 (2880 Shaders) is under Geforce 600 series, should this be under Geforce 700 series? Geforce 830A is under Geforce 900 series, should this be under Geforce 800 series?
  23. https://hwbot.org/hardware/videocard/geforce_gt_640_gf116_ddr3_192bit/
×
×
  • Create New...