Disabling toxic drivers
By setje on Nov 14, 2005
Unfortunately all code is not perfect. Even drivers (particularly ones under development) can on occasion have problems that may wedge a specific system during boot. Back in the days of the DCA (provided it wasn't the real-mode driver that was hanging), one could edit the fake prom-tree and keep such drivers from binding.
Equivalent functionality does exist post new-boot. It's however
not officially documented yet as the syntax may still change a little
as there currently is no way to only disable a specific instance. It
currently (snv_28, s10u1_18) uses the generic -B property passing
mechanism. A all instances of a driver are disabled by setting
So to disable both sd and usbms, one would boot with a kernel line like this:
kernel /platform/i86pc/multiboot -B disable-sd=true,disable-usbms=true
This will cause no instances of either driver to bind. This gives the system a chance to boot, allowing a less buggy driver to be installed, or toxic features to be disabled.