> do some 2>/dev/null to quiesce the error.
or if that's not possible (because it's the kernel who spits out errors, but that's unlikely), it could also do "if modinfo vesafb >/dev/null 2>&1; then modprobe -q vesafb; fi"
> do some 2>/dev/null to quiesce the error.
or if that's not possible (because it's the kernel who spits out errors, but that's unlikely), it could also do "if modinfo vesafb >/dev/null 2>&1; then modprobe -q vesafb; fi"