A Tale of Wizards and Song (alpha):

 

Submitting a Bug Report

There are many possible reasons for failures in this driver. Some of them are bugs in the driver, but other possible problems include extensnion conflicts (yes, it's possible for someone to out-match us) and firmware issues.

The procedure for debugging differs according to the type of failure. In any case, the information listed below should be submitted to our bug tracking database, provided by SourceForge. Please make sure the bug is not already listed in the database before filing a new one.

Note: bugs against the latest version of the driver may not necessarily be marked as "Open". Some bugs may have already been fixed in CVS, but not released as an installable driver. Those bugs are marked as "Pending", which means that they won't show up unless you set the status to "All", then click "Browse".

Types of Failures

If you get a bunch of hex numbers in white against a black background, you have either a panic or system failure. Please skip to Reporting a Panic or System Failure.

If the driver mostly works but causes data corruption, gets I/O errors, or some other minor error, but otherwise works to some degree, skip to Corrupted Data, I/O Errors, etc..

If the driver makes noise, but the disk never shows up, skip to Only Noises

If the driver does nothing, keep reading.

Does Nothing:

File these bug reports as "incomplete implementation". In the bug report, please include your computer's model, speed, configuration, Mac OS X version, and floppy driver version. In addition, include the output of:

sudo kmodstat

and

ioreg -l

Corrupted Data, I/O Errors, etc.

Before reporting this failure, please do whatever you were trying to do in Mac OS 9 or earlier to make sure that the problem isn't being caused by a bad disk or a bad floppy drive.

Please set the "Group" field for these bugs to "Data Loss". In the bug report, please include your computer's model, speed, configuration, Mac OS X version, and floppy driver version. In addition, include the output of:

ioreg -l

and a description of the failure. Also be sure to indicate if the problem is reproducible across reboots.

Finally, if you are able to reproduce the problem consistently, please type:

/System/Library/Extensions/swim3.kext/Contents/Resources/swim3.setdebug 255 255

After you have reproduced the problem, type:

/System/Library/Extensions/swim3.kext/Contents/Resources/swim3.setdebug 0 0

If you were able to successfully reproduce the bug, please look in the file /var/log/system.log. Find the first line that mentions the swim3 driver, and copy the remainder of the log all the way down to the last line that mentions the swim3 driver. (This will be very long.) Save that material in a separate file and attach it to the bug report.

Drive Only Makes Noises

Please set the "Group" field for these bugs to "Incorrect Behavior". In the bug report, please include your computer's model, speed, configuration, Mac OS X version, and floppy driver version. In addition, type the following:

/System/Library/Extensions/swim3.kext/Contents/Resources/swim3.setdebug 255 255

Then try to reproduce the problem. When you are done trying (regardless of whether you succeed or fail), type 

/System/Library/Extensions/swim3.kext/Contents/Resources/swim3.setdebug 0 0

If you were able to successfully reproduce the bug, please look in the file /var/log/system.log. Find the first line that mentions the swim3 driver, and copy the remainder of the log all the way down to the last line that mentions the swim3 driver. (This will be very long.) Save that material in a separate file and attach it to the bug report.

Panic or System Failure

Please report the -entire- panic message and what you were doing at the time. In addition, please include your computer's model, speed, configuration, Mac OS X version, and floppy driver version. Finally, please indicate if the problem has occurred more than once. If you are able to find a way to reproduce it consistently, that's even better.