From owner-freebsd-mobile Tue Nov 11 14:27:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA28357 for mobile-outgoing; Tue, 11 Nov 1997 14:27:09 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA28345 for ; Tue, 11 Nov 1997 14:27:01 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with ESMTP id PAA03991; Tue, 11 Nov 1997 15:26:59 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA18604; Tue, 11 Nov 1997 15:26:57 -0700 (MST) Date: Tue, 11 Nov 1997 15:26:57 -0700 (MST) Message-Id: <199711112226.PAA18604@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John-Mark Gurney Cc: Nate Williams , FreeBSD Mobile Subject: Re: interesting pcmcia card behavior... In-Reply-To: <19971111140322.45272@hydrogen.nike.efn.org> References: <19971111131657.37693@hydrogen.nike.efn.org> <199711112145.OAA18382@rocky.mt.sri.com> <19971111140322.45272@hydrogen.nike.efn.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > and that was with no card in the machine... so I then tried to put > > > the ethernet card back in, but no go... > > > > What happenned there? Did you wait about 5-10 seconds for things to get > > done? Define 'no go' please. > > I get a: > Card inserted, slot 0 > > then nothing else... if I remove the card, then reinsert it... then > it comes up fine.. Hmm, it *should* work fine at this point, but I can see where it might not. (Again, it's based on my 'fake' insertion message which would get pccardd confused.) > > > so then I suspended my machine, > > > put the card in, then resumed the machine... I got a: > > > ep0: eeprom failed to come ready. > > > ep0: failed to come ready. > > > Nov 11 12:58:51 note pccardd[37]: driver allocation failed for 3Com Corporation > > > > This could be related to (what I consider to be) the interrupt problem > > that Guido is also seeing, or something that I have no idea on. It's > > hard to debug remotely, so I'm just guessing here. I need more > > information and someone willing to go in and find out what's going > > wrong. > > yeh.. I was thinking that might be the case... basicly the removal of > the card would release the interrupt, which would enable the second time > I insert the card to work... > > I might take a look at what's up, but the major problem is that I don't > have enough hard disk space on my notebook (340megs isn't much), and > working/looking at code over a 500ms latency connection isn't fun... You only need the kernel/include sources online, which are about 20-30MB, plus another 10MB for the 'built' kernel. > > > I also tried to insert my modem while it was in the above state (thinking > > > a card was really in the slot), and I got the sio2: probe test 3 failed > > > message.. and now the card doesn't work, even after I get the ethernet > > > card to behave properly... > > > > > > Toshiba T1960CS, Intel 82365, old 486dx2/50, video is standard VGA, not > > > local bus (isa)... 3c589b, Megahertz 14.4k (XJ144).. > > > > *shot in the dark* > > > > Can you try (before doing a suspend) enabling the pcic_resume sysctl and > > see if that makes any difference? > > that makes it work the first time I insert the card.. But not after the suspend? Didn't it always work the first time you inserted the card, since the resume sysctl is never even in the picture until suspend/resume. Nate