On Thu, 12 Nov 2009 21:39:56 -0500 Nick Guenther wrote: > On Thu, Nov 12, 2009 at 8:11 PM, rhubbell <[email protected]> wrote: > > On Thu, 12 Nov 2009 14:52:48 -0800 > > J.C. Roberts wrote: > > > >> On Thu, 12 Nov 2009 12:45:24 -0800 rhubbell <[email protected]> > >> wrote: > >> > >> > I'm new to OpenBSD and so far so good. > >> > One thing I am floundering around on is that I cannot get my 3Com > >> > card working. > >> > >> You're new, so you might want to read the following: > >> > >> http://www.openbsd.org/mail.html > >> [quote] > >> "Include important information > >> Don't waste everyone's time with a hopelessly incomplete question. > >> No one other than you has the information needed to resolve your > >> problem, it is better to provide more information than needed than one > >> detail too little. Any question should include at least the version of > >> OpenBSD (i.e., "3.2-stable", "3.3-current as of July 20, 2003"). Any > >> hardware related questions should mention the platform (i.e., sparc, > >> alpha, etc.), and provide a full dmesg(8)." > >> [/quote] > > > > Ok. I guess once I'm here for a while I can waste everyone's time with > > nasty analogies (see other thrd about "platform of choice") (^: > > > >> > >> The reason for that last bit about providing a "full dmesg" is the > >> full dmesg shows lots of important details. In a sense, you can think > >> of the full demeg as showing a picture of your full environment. > > > > Yes, sure does. I guess I got lucky this time and picked the right > > lines to include from dmesg. > > Not really. It's really important to know what your processor is, and > in some cases if you're running APM or ACPI. There can be a lot of > variables involved in a hardware problem (think: IRQ conflicts) and > and after years on this list I've seen plenty of cases where someone > (more than once myself) has thought a problem simple when it was > actually anything but.
Before I have anyone else solve my issues I'd like to understand more about how the kernel build is deciding how to handle hardware. For example I see references to the TI 1620 in the src but the existence of something else seems to have made the kernel decide that this slot shouldn't be enabled. Also I thought that IRQ conflicts were an ISA, and old, problem. Is it still a problem? > > Welcome to OpenBSD, though! Do make yourself at home, only Theo bites. Thanks. > -Nick
