Menu
▾
▴
uuu-testing — Public calls for pre-release testing of binary images
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dave P. <ek...@vo...> - 2002-02-13 20:18:47
|
Two more images are available today: [bzip2] http://void-core.2y.net/download/img-20020213-0003.bin.bz2 http://void-core.2y.net/download/img-20020213-0004.bin.bz2 [zip] http://void-core.2y.net/download/img-20020213-0003.bin.zip http://void-core.2y.net/download/img-20020213-0004.bin.zip (for the curious, -0002.bin is the same as -0001.bin but disables the FDC motor in the boot record) Description: Both images setup a timer and displays the realtime clock. You have a 'scheduler' time, which is based on computed PIT ticks and time since last call. By pressing the spacebar this time is reset to 0. This is compared to the RealTime Clock time located in CMOS. 0003 specific: 1 timer every 1ms, for a total of 1000 timers per seconds. The scheduler time should not be off from the realtime by more than 5% 0004 specific: 1 timer every second. The scheduler time should not be off from the realtime more than 0.0001% Things to test: Verify that the scheduler time is within given allowance with the real time. For image 0003 this should be +/- 5%, and for image 0004 this should be +/- 0.0001% Where to report: mail to: in...@us... subject: report img-20020213-0003 and -0004 Thanks again for your dedication, -- EKS - Dave Poirier (in...@us...) "may the hairs on his toes never fall out" http://uuu.sf.net/ |
|
From: Dave P. <ek...@vo...> - 2002-02-13 16:14:58
|
Image Location: [bzip2] http://void-core.2y.net/download/img-20020213-0001.bin.bz2 [zip] http://void-core.2y.net/download/img-20020213-0001.bin.zip Description: This image tests the U-Burn boot record, which is expected to safely replace GRuB, making loading faster and removing 106KB of bloat from the floppy. The boot record switches to 320x200 and display a small progress bar on the right hand of the screen. Once loading is completed, it switch back to text mode and gives control to the os wrapper. Things to test: 1. Is the boot record recognized? (is the floppy a valid boot disk?) 2. Do you see a blue/gray progress bar on the right hand of the screen? 3. Was the progress bar progressing smoothly from bottom to top? 4. Was text mode restored once the progress bar reached the top? 5. Did the os wrapper received control ? Note: The sequence/behaviour once the os wrapper is given control did not change, so if you had problem with that part it will not be solved in this image. It is really only to test the boot record. Where to report: email to: in...@us... subject : report img-20020213-0001 Thanks, -- EKS - Dave Poirier (in...@us...) "may the hairs on his toes never fall out" http://uuu.sf.net/ |
|
From: Dave P. <ek...@vo...> - 2002-02-04 04:41:21
|
I have a small test image, located at: [bzip2] http://void-core.2y.net/download/img-20020204-0001.bin.bz2 [zip] http://void-core.2y.net/download/img-20020204-0001.bin.zip * What to expect * If all goes well, you should get a blue status bar on the top of the screen displaying "[I] Test cell - for learning purposes" and a "0" on the line just under. It should stay like that for _exactly_ 5 seconds. Then it should go from 1 to 9, changing at _exactly_ each second. When the count reach 9, the status will display "[-] System tests completed..." and lock. There will not be anything else shown or whatever. * What to check * 1.) See if you get to "[I] Test cell - for learning purposes" 2.) See if the "0" is displayed for 5 seconds. It is uterly important that you check the time as precisely as possible. This will allow me to make change in the programmation of the timer for the realtime engine. 3.) See if after the 5 seconds the 0 start changing at a constant rate of +1 per second. Again, it is very important that you time this as best as you can. If the value is off even so slightly, please tell me. * Where to report * Send an email directly to me: in...@us... * What to report * 1.) did the image worked like expected? 2.) were the timings exactly matching the real time? a.) 0 displayed for exactly 5 seconds? b.) increasing from 1 to 9 at +1 per second? Thank you for taking the time to test :) -- EKS - Dave Poirier (in...@us...) "may the hairs on his toes never fall out" http://uuu.sf.net/ |
|
From: Dave P. <ek...@vo...> - 2002-01-24 14:02:37
|
Here's a test image that implements I/O delay between both FDC operations and DMA programming. Hopefully this will fix the problem people have been reporting with the fdc code. bzip2: http://void-core.2y.net/download/img-20020124-0001.bin.bz2 zip: http://void-core.2y.net/download/img-20020124-0001.bin.zip * things to test * test #1: See if you can get to the prompt test #2: run 'dmesg' and see if any error is reported for the fdc. * what to do after testing * If possible, please submit your results via the SF uuu-testing trakcer at http://sourceforge.net/tracker/index.php?group_id=23202&atid=430301 (please log in first if you have a SF account) If you are unable to submit via the tracker you can email me directly. Example of report expected for this test: | change: no | was working before: no | fdc: part of the 82430 VX chipset. Thank you for your help in testing Uuu. Good luck! -- EKS - Dave Poirier (in...@us...) "may the hairs on his toes never fall out" http://uuu.sf.net/ |
|
From: Dave P. <ek...@vo...> - 2002-01-17 05:56:56
|
Here's a test image which is expected to fix the memory corruption as well as many boot problems: bzip2: http://void-core.2y.net/download/img-20020117-0001.bin.bz2 zip: http://void-core.2y.net/download/img-20020117-0001.bin.zip This image features the new the core format with an accordingly modified os wrapper. The memory detection is currently bypassed and hard-set to 4MB. The bug located in meitnerium is fixed. known issue: memstat displays the wrong memory statistics. * things to test * test #1: See if you can get to the prompt, then try to type and see if any command is understood. test #2: just do your best to make the system crash. * what to do after testing * If possible, please submit your results via the SF uuu-testing tracker at http://sourceforge.net/tracker/index.php?group_id=23202&atid=430301 (please log in first if you have a SF account) If you are unable to submit via the tracker you can email me directly. I'd like to get a quick message from all people if the test works or not. In your results please include: - your type of CPU (intel/amd, 386/486/etc) - how much RAM you have installed - what type of keyboard you have (AT or PS/2) - any other hardware information you think could be relevant Include the last 5 or so lines of text output. Also look up in the upper-left corner for any numbers and note them, if present. A complete list of everything you did from the time uuu booted until the bug was found is extremely helpfull. Thank you for your help in testing Uuu. Good luck! -- EKS - Dave Poirier (in...@us...) "may the hairs on his toes never fall out" http://uuu.sf.net/ |
|
From: Phil F. <da...@xg...> - 2001-12-19 04:11:01
|
I have created 2 beta floppy images for FRuSTRaTiON 0.4. They include the new strontium ][ thread engine and a few misc. tweaks. They are located at: bzip2: http://xgs.dhs.org/uuu-testing/uuu-test-20011218-0001.bz2 http://xgs.dhs.org/uuu-testing/uuu-test-20011218-0002.bz2 gzip: http://xgs.dhs.org/uuu-testing/uuu-test-20011218-0001.gz http://xgs.dhs.org/uuu-testing/uuu-test-20011218-0002.gz zip: http://xgs.dhs.org/uuu-testing/uuu-test-20011218-0001.zip http://xgs.dhs.org/uuu-testing/uuu-test-20011218-0002.zip the 0001 images are what's on CVS as of Wed Dec 19 03:48:40 UTC 2001. The 0002 images are the same but with a suspected memory corruptor disabled: the log buffer. * things to test * test #1: Most of all, just thrash the system. Run programs over and over in rapid sucession, start 20 ishes, run some programs, close a few, run more. When all processes have terminated you should get a message to press enter to reboot. test #2: Also, test the beeping by hitting tab in ish. It should be a high A for a duration of 0.1 secconds. Also try holding down tab or hitting it in rapid sucession so that many beeps are beeping at once. test #3: Also try cding to a directory that doesn't exist (it should work) and then executing ls. Ish should say "app returned error 17" and nothing should crash. test #4: If the 0001 image won't work for you, try the 0002 image. Also there have been some reports of different behaviour between tries, so if it doesn't work, or if it does and you have some extra time. test #5: Run the 'memstat' program. Nothing incredibly impressive here; you should get a total amount of memory that's a little less than the total you have installed and about 100KB used. used+free should equal total :P * what to do after testing * If possible, please submit your results via the SF uuu-testing tracker at http://sourceforge.net/tracker/?func=add&group_id=23202&atid=430301 (please log in first if you have a SF account) If you are unable to submit via the tracker you can email me directly. I'd like to get a quick message from all people if the test works or not. In your results please include: - your type of CPU (intel/amd, 386/486/etc) - how much RAM you have installed - what type of keyboard you have (AT or PS/2) - any other hardware information you think could be relevant Include the last 5 or so lines of text output. Also look up in the upper-left corner for any numbers and note them, if present. A complete list of everything you did from the time uuu booted until the bug was found is extremely helpfull. Thank you for your help in testing Uuu. Good luck! Phil Frost |
|
From: Dave P. <ek...@vo...> - 2001-12-05 22:42:04
|
sorry for any of you that had to download the uncompressed binary, I didn't quite think of it. I have on the other hand created compressed image of it, so those of you who haven't yet tested the binary can acquire it in various formats: - Uncompressed: http://void-core.2y.net/uuu-testing/img20011205-0001.bin - GZip: http://void-core.2y.net/uuu-testing/img20011205-0001.bin.gz - BZip2: http://void-core.2y.net/uuu-testing/img20011205-0001.bin.bz2 - Zip: http://void-core.2y.net/uuu-testing/img20011205-0001.bin.zip Again, sorry about that. EKS - Dave Poirier |
|
From: Dave P. <ek...@vo...> - 2001-12-05 17:38:54
|
Image ID: 20011205-0001 Location: http://void-core.2y.net/uuu-testing/img20011205-0001.bin Specific: For those of you getting a blue screen only at boot, if you get to the prompt, test is successful Test report should be filled at: https://sourceforge.net/tracker/?func=add&group_id=23202&atid=430301 or sent to the uuu...@li... mailing list with: Subject: img20011205-0001 test report EKS - Dave Poirier |