Date: Tue, 15 Jul 2008 15:20:19 +0200 From: "Vincent Barus" <vibarus@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: difference between loading kernel module during boot and after boot manually? Message-ID: <e4207650807150620i5e7efd7ex4736e2947fec89ef@mail.gmail.com> In-Reply-To: <200807142258.34757.fbsd.questions@rachie.is-a-geek.net> References: <e4207650806221429y4e9c01d2i6d082bbad8a54c54@mail.gmail.com> <200807082011.23341.fbsd.questions@rachie.is-a-geek.net> <e4207650807141129je2b7aa5p557546176bdb0f65@mail.gmail.com> <200807142258.34757.fbsd.questions@rachie.is-a-geek.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 14, 2008 at 10:58 PM, Mel <fbsd.questions@rachie.is-a-geek.net> wrote: > On Monday 14 July 2008 20:29:07 Vincent Barus wrote: >> On Tue, Jul 8, 2008 at 8:11 PM, Mel <fbsd.questions@rachie.is-a-geek.net> > wrote: >> > On Tuesday 08 July 2008 16:48:26 Vincent Barus wrote: >> >> does anyone have an idea what's the difference or what _could_ be the >> >> difference on loading a kernel module during boot or manually? >> > >> > There's one major difference. File systems aren't mounted at loader >> > stage, so any reference to modules/libraries that exist on a different >> > partition, will fail. > >> Right now i have only one partition and the same problem occurs. Other >> modules e.g. for sound or the nvidia module work as a charm. >> So I think that's not the only difference. >> I can live with a module loaded at the end of the boot process/after >> login but I don't think that's the real solution. > > Hmm, I can only guess here. Is the machine booting to xorg? As in, is the > nvidia card actually initialized, not just in VGA mode? If so, does it work > when it stays in console mode and/or when nvidia.ko is removed from the > loaded modules? > > -- > Mel > > Problem with today's modular software: they start with the modules > and never get to the software part. > I start X manually after login. You want me to unload nvidia.ko while on console? I never tried it --> have to try it. The card gets initialized during boot as it should instead of the nic which causes: re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xd800-0xd8ff mem 0xfebff000-0xfebfffff irq 17 at device 0.0 on pci4 re0: couldn't map ports/memory device_attach: re0 attach returned 6 as described in kern/123563 How do I track down mapping problems on boot time? Regards, Vince
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e4207650807150620i5e7efd7ex4736e2947fec89ef>