On Fri, 13 Nov 2009 04:26:44 -0800 J.C. Roberts wrote: > On Thu, 12 Nov 2009 17:11:47 -0800 rhubbell <rhubb...@ihubbell.com> > wrote: > > > On Thu, 12 Nov 2009 14:52:48 -0800 > > J.C. Roberts wrote: > > > > > On Thu, 12 Nov 2009 12:45:24 -0800 rhubbell <rhubb...@ihubbell.com> > > > 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") (^: > > > > Bob Beck{,se} is a comedic genius! > > You might not realize it, but in said "time wasting" thread you actually > learned something memorable and valuable. Of course, the downside is > the next time you consider using non-x86 hardware in production, you'll > remember the long term relation prospects of having sex with someone in > a coma. But at least you remembered.
Remembered what? (^; > > > > > > > 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. > > > > The only reason why you got lucky is because I got lucky. --You never > want to count on other people getting lucky... with corpses, coma > patients, or otherwise. Your long term relationship prospects of getting > help on misc@ depends on you remembering to post your full dmesg. > > More seriously, most people will see the partial or missing dmesg in a > request for help, and just ignore the message. The *only* reason why I > didn't ignore you is, you said you were new. Seems reasonable. > > > > > > > > The device 3CCFE575CT exists already and I added the entries for > > > > 3CXFE575CT. > > > > > > The product model number is not always indicative of the chips used > > > inside the product. But in your case, this is irrelevant. > > > > Right. According to notes in the source they were same except by name > > and how you physically connect the cable. > > > > Though it's encouraging to see you digging into the source for your > own answers in your first week of using OpenBSD, it's a bummer that you > needed to do it. Typically, if you are using supported hardware, > OpenBSD just works. Of course, the conundrum is, for hardware to be > supported in OpenBSD three things need to happen; (1) hardware > documentation must be available, (2) a developer needs access to the > hardware, and (3) a developer needs to find the time/inclination to do > the work. Right. This hardware combo has worked on windows and linux. So my guess is that it might just need some sorting out. > > > > > > > > cbb1 at pci1 dev 4 function 0 "TI PCI1620 CardBus" rev 0x01: apic > > > > 2 int 16 (irq 11), CardBus support disabled > > > > > > > > cbb2 at pci1 dev 4 function 1 "TI PCI1620 CardBus" rev 0x01: apic > > > > 2 int 16 (irq 11), CardBus support disabled > > > > > > Take a look inside /usr/src/sys/dev/pci/pccbvar.h > > > HINT: The "TI PCI1620" is not listed. > > > > > > In short, there might not be anything "wrong" with your 3com card, > > > but instead, the PCMCIA/CardBus controller (i.e. slot) is not > > > supported. > > > > Ah, ok, so looks like I am tsol, thanks for the help. > > FWIW, am on 4.6-stable, have been using OpenBSD for one week. > > > > You may, or may not, be TSOL... --You've got two options. > > (1) The driver(s) for the other "TI PCI1xxx CardBus" chipsets *might* > actually work with your PCI1620. But since no one has ever tried it, > there's no way to claim it is "supported." You would need to add the > PCI device ID so it is recognized. Okay I hadn't done that. I will do that and see what happens. > > Adding support for the PCI1620 might be dead simple, or it might be > somewhat more involved. Either way, if you make the effort, you will > most likely get help. This is good to know. > > NOTE: Finding the documentation for the device is always a good start. > > (2) Offer to provide one of these PCMCIA/CardBus devices to one of the > developers so support can be added. OpenBSD has a long history of great > human beings sending gifts of hardware to each other, because without > hardware, code doesn't happen. Right, but I only have one of these. > > Alternatively, if you find an interested developer and can set up > remote access to the machine (preferably with an additional serial > console), they might try to add/fix support for the device remotely. Interesting option I hadn't considered. > > Welcome to OpenBSD! Thanks and thanks for the assistance. > > -- > J.C. Roberts
