As Simon 'corecode' Schubert wrote:
> my kernel can't detect fdc anymore when loading acpi. does anybody else
> have such issues?
Hmm, not here. However, my fdc driver is modloaded, too (from the
bootloader). I just tried to unload it, then load acpi (which yields
module_register_init: MOD_LO
> my kernel can't detect fdc anymore when loading acpi. does anybody else
> have such issues?
>
> i know that it worked with a Aug 6 or a Aug 3 kernel, this was the last
> time i accessed my fd0.
>
> though reverting to a -D 08/06/2002 src/sys doesn't bring the desired
> effect (working fdc).
H
On Tue, Aug 20, 2002 at 08:43:20AM +0200, Mark Santcroos wrote:
> put:
> exec="unset acpi_load"
> in your /boot/loader.conf
Or:
hint.acpi.0.disable="1"
Nice to have several solutions to a problem in the UNIX world :-)
--
Anders Andersson <[EMAIL PROTECTED]>
UNIX, Networking and Security consul
On Tue, Aug 20, 2002 at 12:34:52PM +0200, Simon 'corecode' Schubert wrote:
> On Tue, 20 Aug 2002 08:43:20 +0200 Mark Santcroos wrote:
>
> > > if i prevent acpi from being loaded on boot time (don't know the right
> > > procedure, just `set module_path=/' in /boot/loader) fdc is detected
> > > cor
On Tue, 20 Aug 2002 08:43:20 +0200 Mark Santcroos wrote:
> > if i prevent acpi from being loaded on boot time (don't know the right
> > procedure, just `set module_path=/' in /boot/loader) fdc is detected
> > correctly.
> put:
> exec="unset acpi_load"
> in your /boot/loader.conf
ah, thanks. stil
On Mon, Aug 19, 2002 at 05:00:55PM +0200, Simon 'corecode' Schubert wrote:
> if i prevent acpi from being loaded on boot time (don't know the right
> procedure, just `set module_path=/' in /boot/loader) fdc is detected
> correctly.
put:
exec="unset acpi_load"
in your /boot/loader.conf
--
Mark S
