Now I tried to load all available modules:
ls /modules | grep -v acpi | sed -e 's/.ko/_load="YES"/g' > /boot/loader.conf
In this case it crashes immediately when acpi.ko gets loaded.
Without acpi it works fine.
Perhaps it's related to a buggy bios on my laptop (Thinkpad T42)?
Johannes
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>
> :When I try to load more than 5 modules via loader.conf, my kernel
> :no longer finds the root filesystem.
> :Booting in "Safe Mode" still works.
> :As far as I can tell this is independent of which modules I actually
> :load.
> :I'm running 2.0 releas
YONETANI Tomokazu <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 30, 2008 at 03:31:46PM +, Johannes Hofmann wrote:
>> When I try to load more than 5 modules via loader.conf, my kernel
>> no longer finds the root filesystem.
>> Booting in "Safe Mode" still works.
>> As far as I can tell this is indepe
On Wed, Jul 30, 2008 at 03:31:46PM +, Johannes Hofmann wrote:
> When I try to load more than 5 modules via loader.conf, my kernel
> no longer finds the root filesystem.
> Booting in "Safe Mode" still works.
> As far as I can tell this is independent of which modules I actually
> load.
> I'm run
:When I try to load more than 5 modules via loader.conf, my kernel
:no longer finds the root filesystem.
:Booting in "Safe Mode" still works.
:As far as I can tell this is independent of which modules I actually
:load.
:I'm running 2.0 release more or less, so I don't yet have the
:latest changes
When I try to load more than 5 modules via loader.conf, my kernel
no longer finds the root filesystem.
Booting in "Safe Mode" still works.
As far as I can tell this is independent of which modules I actually
load.
I'm running 2.0 release more or less, so I don't yet have the
latest changes to gpt.
