Date: Sat, 11 Nov 2000 14:17:37 -0600 (CST) From: Mike Meyer <mwm@mired.org> To: Drew Tomlinson <drewt@writeme.com> Cc: questions@freebsd.org Subject: RE: What Is config> During Boot? Message-ID: <14861.43361.822875.484924@guru.mired.org> In-Reply-To: <BA5D0CE1CBB2D411B6AA00A0CC3F02390AF70D@ldcmsx01.lc.ca.gov> References: <14860.49919.242784.217200@guru.mired.org> <BA5D0CE1CBB2D411B6AA00A0CC3F02390AF70D@ldcmsx01.lc.ca.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Drew Tomlinson <drewt@writeme.com> types: > > -----Original Message----- > > > Then thinking that "at isa?" means "probe and see what you > > find", I removed > > > everything after "at isa?" and recompiled again. This time > > only ed0 was > > > found but it still worked. > > > > Put that stuff back. "at isa?" means "I don't know which ISA bus it's > > on, try these values at all the ones in the machine." Removing the > > information about port, irq, etc. means to try the default values for > > that device, and there isn't one there. > So if I understand the other part of your message properly, ed0 worked only > because it is defined in the kernel.conf file? And otherwise, neither card > would work? No, that's not the case. The system has to have this information from *somewhere*. The places that it tries are the driver defaults (if available, and won't work here), via pnp (again, it won't work here), from the config file at build time (i.e. "device ed0 at isa? ..."), and the userconfig stuff you saw. > That someone would be the installation program. :) I didn't know ANYTHING > about Unix or FreeBSD before I installed this system in September. But I'm > learning... Thanks for all of your help!!! So you think that the ultimate > problem is an IRQ conflict? If I remove ed1 NIC, is there some way to scan > the system and see what is available? Is vmstat -i a good option? I usuually use dmesg. You might check the BIOS setup as well, to see what it can tell you. But the only thing I know of that will make it time out if it shows up in dmesg with the right values is not getting interrupts. That doesn't mean it won't be something I don't know of, though. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14861.43361.822875.484924>