Date: Wed, 14 Mar 2001 07:51:32 -0500 From: Peter Radcliffe <pir@pir.net> To: mobile@freebsd.org Subject: Re: Bridging with 3C589D-COMBO on 4.2-RELEASE? Message-ID: <20010314075132.A8440@pir.net> In-Reply-To: <3AAF047F.341981B2@babbleon.org>; from bts@babbleon.org on Wed, Mar 14, 2001 at 12:41:20AM -0500 References: <3AAC4C03.13000DE@babbleon.org> <3AAC4E83.2C281B90@babbleon.org> <15021.46309.150521.925816@nomad.yogotech.com> <3AADBAB8.36039542@babbleon.org> <20010313104711.B6592@pir.net> <3AAF047F.341981B2@babbleon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The Babbler <bts@babbleon.org> probably said:
> Peter Radcliffe wrote:
> > PCMCIA under freebsd seems far more stable than Linux PCMCIA support
> > when _correctly_ _configured_. I've helped dozens of people get
> > wavelan support working at conferences and getting it as stable with
> > Linux requires the exact correct versions (and the only way to find
> > them is to test) of half a dozen things ...
> I haven't used WaveLANS, but every PCMCIA I ever stuck in my Linux box
> just worked.
It sometimes took a couple of _days_ of hackery to get wavelan cards
working with some linux boxes, the only fast way at the first
conference was to find the person who already had it working and ask
them what they did. Certainly not "just working".
> in January or so for the saga on *that*. Similarly, I could *never* get
> two identical cards to work on my gateway machine; I finally bought a
> card to make FreeBSD happy. With Linux it just worked. Easy.
I've had identical cards working perfectly in the same machine.
> To say the least, then, my experience does not concord with yours in
> this regard.
Mine nor dozens of other people.
> I read the FreeBSD readme. And I've had a nubmer of posting in the
> emultors group as I got things working there, too. The bridging would
> never work for me, but my final conclusion is that my card doesn't work
> with bridging, I guess. Only some cards do. (It says *that* in the
/usr/ports/emulators/vmware2/files/README.FreeBSD
- Support only for Host networking. Doesn't have a bridgink networking
But really this mean, that you are need to enable gateway on
our FreeBSD box. And after that virtual machine can communicate
with a rest of the world.
> > I would assume you have a misconfiguration or a hardware problem.
> > I've had freebsd boxes doing routing/filtering/pcmcia up for
> > _months_ with no problems.
> PCMCIA-based laptops or desktops?
Both. Two examples are an old 486 laptop as a wavelan <-> ether
gateway and a desktop box that wasn't rebooted with an ISA pcmcia
controller which I used CF cards in. My current laptop only gets
rebooted for upgrades, basicly, has been suspended/resumed thousands
of times and it's primary net access is pcmcia wavelan. I'm typing on
it right now.
> Happened to me twice within days of my install. Both times it was
> "cal.vcs," for what it's worth. That's the calendar database for
> korganize, which *is* loaded, but would have had no reason to be writing
> to disk when I crashed.
Sounds like bad hardware to me, then. Have you been reading the write
cache thread ?
I currently run soemthing like 10 heavily used desktops/laptops for
my group at work. I hammer my machines. I've _never_ seen this happen.
> I never lost any files under Linux except once when I had a physical
> disk failure.
I've never lost any files under FreeBSD except for physical disk
failure. Your point ?
> No manual entry for diagnostic. Also, I did a "make search" on ports.
> No "diagnostic" there, either.
It's a kernel entry;
# The DIAGNOSTIC option is used to enable extra debugging information
options DIAGNOSTIC
> As for ddb, what you do, leave it up for two weeks waiting for the
> elusive crash? Wouldn't that have a severe impact on performance at
> least?
No. My laptop runs with DDB in the kernel dating from when there was a
problem with removing/reinserting ATA cards a few times in 4.* and I
was trying to assist in debugging the issue. Never saw any reason to
turn it off after the issue was fixed properly and have noticed no
performance issues.
> Besides, when it hangs, it *hangs*. It won't even respond to keyboard
> input, not even CTL-ALT-DEL or ALT-F2. How would I use an interactive
> debugger in this context? Use the remote debugging? To do that, do I
Thats the point of DDB. You drop to the debugger, which is below
everything else.
You don't seem to be able to drop to DDB while running X, which is
unfortunate, but crash dumps can still help assuming one happens
or can be provoked and you have collection turned on.
http://www.freebsd.org/docs/en/books/handbook/kerneldebug.html
P.
--
pir pir@pir.net pir@net.tufts.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010314075132.A8440>