Xircom XE2000 card problem

[jvk-list at thekrafts.org]

   -------- Original Message --------
   Subject: RE: Xircom XE2000 card problem
   From: "Wood, Russell" <Russell.Wood at rac.com.au>
   Date: Mon, November 20, 2006 9:53 pm
   To: <jvk-list at thekrafts.org>
   Cc: <freebsd-questions at freebsd.org>
   > -----Original Message-----
   > From: jvk-list at thekrafts.org [mailto:jvk-list at thekrafts.org]
   > Sent: Tuesday, 21 November 2006 12:40 PM
   > To: Wood, Russell
   > Cc: freebsd-questions at freebsd.org
   > Subject: RE: Xircom XE2000 card problem
   >
   >
   > > Try:
   >
   > > kldunload if_ed
   > > kldload if_xe
   >
   > > ... and see if it detects to card.
   >
   > kldunload complained:
   > kldunload: can't find file if_ed: No such file or directory
   >
   > and kldload:
   > module_register: module pccard/xe already exists!
   > Module pccard/xe failed to register: 17
   >
   > Do I need to rebuild a kernel without ed or xe first and then try to
   > load them dynamically?
   >
   > Joe.
   >
   If_ed is probably compiled into your kernel so you can't unload. So
   yeah, try to recompile with that out.
   Regards,
   Russell Wood



   Thanks for your time in helping me work through this.  If nothing else
   I'm learning something about how the driver system works in FreeBSD...



   I recompiled the kernel without either ed(4) or xe and loaded them one
   by one.  Loading xe did nothing, loading ed again gave the
   "device_attach: ed1 attach returned 6" messege.  Guess I expected
   that.



   I'm still convinced it should be supported by the xe driver though,
   unless anyone can tell me that for sure it isn't.  I've looked through
   the man pages for NetBSD, OpenBSD and Linux and they all appear to use
   the same driver for the xe2000 as for the other xircom cards listed in
   the FreeBSD man page for xe.



   Where does the magic of matching a driver to a card happen?  The card
   with the ed(4) driver attaches to the pccard0 device, which makes
   sense.  I'm pretty sure it's a 16bit card not one supported by
   cardbus.



   Also do you know where the "attach returned 6" message is generated?
   I'm curious to know what condition causes it, but I can't find it in
   the source.  I assume it's in the device attach function but I'm not
   finding it.  Maybe I'm blind.



   Thanks again for helping out,

   Joe Kraft