Date: Tue, 20 Mar 2001 03:09:04 -0600 From: Sean Kelly <smkelly@zombie.org> To: Mike Smith <msmith@freebsd.org> Cc: Kris Kennaway <kris@obsecurity.org>, freebsd-stable@freebsd.org Subject: Re: Booting with modules Message-ID: <20010320030904.A757@edgemaster.zombie.org> In-Reply-To: <200103200851.f2K8pVg16380@mass.dis.org>; from msmith@freebsd.org on Tue, Mar 20, 2001 at 12:51:31AM -0800 References: <20010320021855.A433@edgemaster.zombie.org> <200103200851.f2K8pVg16380@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 20, 2001 at 12:51:31AM -0800, Mike Smith wrote: > > > I *suspect* that what's happening is that the dependancy checking code is > > > incorrectly not registering the if_xl module when it discovers that its > > > dependancy (miibus) is already loaded. ... > > Very poetic. Can you confirm that during the actual load process, if_xl > was loaded before if_dc? I'm not certain that the ordering in > loader.conf actually represents the order in which things are loaded. Hmm... I should have been smart enough to do that in the first place. I did it again, and if_dc.ko is still going before if_xl.ko even though if_xl is listed first in loader.conf. Guess order doesn't matter. > > On another similar note, a few minutes ago I realized that the > > snd_emu10k1.ko module wasn't loading because: > > Preloaded elf module "snd_emu10k1.ko" at 0xc037f544. > > link_elf: symbol sndbuf_getbps undefined > > You need to get a grip on how things work here. The above is not > indicative of a failure to load, but a failure to *link*. > > The process goes basically as follows: ... Thanks for clearing that up. > Did kldstat -v show it already loaded? If 'it' is snd_pcm.ko, then no. If 'it' is snd_emu10k1.ko, then no. I was goign to load snd_pcm and then snd_emu10k1, but the system locked upon my attempt for snd_pcm so I didn't get to the second... > > On the reboot after that, I went back to the 'ok' prompt in loader, > > and decided to try 'load /modules/snd.ko'. It registered 5342532 different > > sound modules (all of them I think), yet doing 'lsmod' in loader showed > > NONE of them except the snd_emu10k1.ko from my loader.conf. > > lsmost should show loaded files, not modules. It sounds like it may not > be working right, however. Sort of a misleading command name then. But still, shouldn't it have shown the sound modules that it registered just seconds before when I did 'load /boot/snd.ko'? It shows the other modules that it registered as specified in loader.conf (except if_xl.ko, but that is a separate issue, maybe). > > Upon boot, > > none of them were there. So, what happened to my 'load /modules/snd.ko'? > > Good question. I'll try to reproduce this, but I'm kinda hard up for > time right now, so if anyone else feels like getting involved, I'd be > much obliged. -- Sean Kelly | PGP KeyID: 77042C7B smkelly@zombie.org | http://www.zombie.org For PGP key, send e-mail with subject "send pgp key" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010320030904.A757>