Date: Sun, 27 Jan 2002 17:39:50 -0800 From: "Jeff Shevlen" <jeff@dsl.ca> To: "Kevin Oberman" <oberman@es.net> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: new kernal config errors Message-ID: <082801c1a79c$ad8536d0$b300a8c0@wenk> References: <20020127205554.EBE775D0B@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
That did the trick! Thanks for the tip Kevin. Now that I've fixed kernel.conf, I'm wondering if you or anyone else can shed some light on what kernel.conf does. Man kernel.conf doesn't have an entry; nor does apropos. I'm also curious what the single reference to "q" does in my new version of kernel.conf. Lastly, I don't know if this is a genuine candidate for the documentation project, but given my experiance I'd like to cast a vote for adding a note about kernel.conf to chapter 9 of the handbook. ----- Original Message ----- From: "Kevin Oberman" <oberman@es.net> To: "Jeff Shevlen" <jshevlen@passedpawn.com> Cc: <freebsd-questions@FreeBSD.ORG> Sent: Sunday, January 27, 2002 12:55 PM Subject: Re: new kernal config errors > > From: "Jeff Shevlen" <jshevlen@passedpawn.com> > > Date: Sun, 27 Jan 2002 15:44:50 -0800 > > Sender: owner-freebsd-questions@FreeBSD.ORG > > > > Hola, > > > > I've got two questions in regards to a new kernal I've made: > > > > (1) In an effort to get rid of some serial port messages in my GENERIC > > configuration: > > > > dmesg from GENERIC > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > sio2: configured irq 5 not in bitmap of probed irqs 0 > > sio3: configured irq 9 not in bitmap of probed irqs 0 > > > > ... I now get some "config> ... no such device" errors or warnings or > > something, as shown in the new kernal's demsg below. > > > > What I have done with the new kernal configuration is comment out the sio1, > > sio2 & sio3 entries all together since I'm not using anything other than my > > ethernet card. (There is an old SB16 card, and an old 56k modum I've just > > left in the machine though I'm not using either.) I don't understand what > > these mew dmesg's are, whether I should worry about them, and if so how to > > fix them. What's more, I'm not sure that removing support for these 3 > > serial ports is even a good idea in the firstplace! I'm newbie... > > A common question. When you installed, you were asked to indicate > interfaces you didn't want to use to avoid conflicts. What is not made > clear is that these interfaces were disabled in the file > /boot/kernel.conf. As soon as you built a new kernel without these > devices, they were no longer there to be disabled and the annoying > messages started up. > > Just edit /boot/kernel.conf and remove the 'di' lines for interfaces > you don't have. (You might want to "en apm0" there, while you are at > it, if you want APM services.) > > In the meantime, the message are simply indicating that the drivers > for these devices are not in the kernel, so they are not a > problem. Just an annoyance. > > > > (2) In an effort to remove nonexistant NIC card drivers I didn't think I > > needed, I get similar "config> ... no such device" messages, also shown > > below. My ethernet card is a D-Link 530TX, which showed up as a Rhine > > compatible card (vr0: <VIA VT6102 Rhine II 10/100BaseTX>") in the original > > install. I commented out support for all the other network interfaces I > > could see, but again, I have the complaining dmesg's. And again, I don't > > understand what these errors are, whether I should worry about them, and if > > so how to fix them. It is worth noting that I seem to have full and happy > > network access inspite of the complaints on boot! > > > See above. Same thing. > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > > 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?082801c1a79c$ad8536d0$b300a8c0>