If I (or another trusted developer) gives you a new driver binary to test (i.e. one that is not in master yet), here are the…
Testing instructions
- Download the new driver and verify it against the posted SHA256sum.
- Blacklist the old driver. (If you’re unfamiliar with blacklisting files, see this page for an introduction.) In general, this will mean creating a file
/system/settings/packages/
with contents like this:
Package haiku {
EntryBlacklist {
add-ons/kernel/drivers/bin/drivername0123
add-ons/kernel/drivers/dev/net/drivername0123
}
}
… where drivername0123
should of course be replaced with whatever the driver’s name is.
- Check if there is already a driver with this name in
/system/non-packaged/add-ons/kernel/drivers/bin
. If there is, delete it before the next step. - Reboot, so the package blacklist will take effect.
- Copy the new driver to
/system/non-packaged/add-ons/kernel/drivers/bin
.- If this directory doesn’t exist, create it first, using
mkdir -p ...
which will make the whole path for you.
- If this directory doesn’t exist, create it first, using
- Try to use the driver, and report back with whether it works or not. If it doesn’t, be sure to attach your
syslog
so we can see what the issue is.