Well...it's a balance between having some useful info and making it into a soup of myriads of different variants of the sam thing. I guess ethernetcards could be added, but one has to draw the line somewhere. Are there any examples known where *the same* motherboard exists with a different chipset where one works and the other doesn't? Or when the exact same videocard with 32 MB works, but with 64 Mb doesn't? I think the chances are pretty minute.
Normally, when it works for one class (a cmedia 8738 soundcard for instance) will work for the whole class. It comes as no surprise then, that my 8738-C3DX version also works, because the 8738 as a whole is supported.
"The devil is in the detail." Back in the Athlon and KT133 chipset era, there were motherboards that would support the newer 133MHz CPU bus if there was a . (dot) at the end of the of the PCB revision
. Just a dot, all the other numbers/letters identical.
You have seen it
Webunny wrote:I already had a bit doubts with point 2, for instance. Are there any cases where a rig with ROS works with 512 RAM, but not with 1 GB ram, for instance? (below a certain threshold I could imagine, but more ram, if the ram is good, hardly ever leads to suddenly it not working anymore. At least, I've never seen such a thing with ROS testing anywhere.)
Granted, the bug could not be reliably replicated, but something was fishy
. (We can speculate on many more or less plausible "theories" as to why it would stop working with more memory, but considering the fragile state of the current ROS MM should be enough. Same goes for a potential race condition on a faster CPU/bus, i.e. works on P4 1500 but not 3000).
Webunny wrote:Maybe I could make a general point for additional info for those that really want to add to it, but some of it hardly seems worth the clutter.
I think that right now the "formular" is sparse enough, so it can support additional info. I gave a shoot with your config (to the best of my understanding of course):
1) Intel Pentium 4 (shouldn't it be "generic/custom-build PC"? As opposed to some specific manufacturer model?)
2) P4@1,8Ghz(400MHz FSB) potentially an sSpec/id string from Intel CPU id/CPU-Z;
3) Aopen mx4bs (82845/82801BA) 512 Mb RAM (SD or DDR, 1 or 2 modules, which sizes?);
4) NVIDIA Vanta (NV6) AGP 16 MB SDRAM card using build-in SVGA driver
5) CMedia 8738-C3DX soundcard using build-in driver
6) HDD (manufacturer, model?) 40 GB;
7) Network: n/a;
6) REL 0.3.15
Webunny wrote:The ethernetcard and the bios...well, if the devs think it's really wortwhile to have that info, I could make seperate points of it. The rest I would do with a general point (or maybe placing it with 7)comments?)
The more unstructured data you have, the harder it will be to extract it later to put in the database, for one thing.
Also, initially I don't expect more than a douzen hardware testers, so there won't be that much information clutter. And since each one will not test more than 2-3 configs (most likely one), they can afford to spend 5-10 more minutes to have it written down really detailed. Finally, if wiki page space is really such a problem, the detailed info can be put on separate pages in the wiki/forum user profile and linked there. It can then be called simply "Webunny's test rig #1"(2, 3, etc.), but then one will have to click more links to know what hardware was working, and this is counterproductive.