I usually don't get the USB mailing list in my inbox. However,
for some reason I fished this out of spam. Indicating to me
I should answer this.


Hot swapping has never been a strong point for BSD.
Basically they think, "hot swapping" means, flip a
mechanical switch, remove the device. They DON'T
think like a USB device; which is "plug in and pull"
- at will. 

In the Linux world, there is an army of people that
attack problems like this 'ad hoc'. The BSD
community is far too formal to get it done in
any reasonable time frame.

In the Linux world, there are a host of "post-boot"
solutions, such as systemd, busd, etc. They all
generally trap an event, be it real (such as an IRQ),
network, program, or user.  This is usually
leverage by /proc, dmesg or similar. 

Hope this helps.
FWIW: I'm living in El Paso Texas for the next 6 months.

Best of Luck,

On Fri, 11/28/14, Alfred Perlstein <> wrote:

 Subject: Question on ue devices autoconfigure versus Linux.
 Cc: "Hans Petter Selasky" <>
 Date: Friday, November 28, 2014, 5:37 PM
 We have a widget here, basically a "beagleclone" that runs
 When I plug it into an ubuntu host it shows up as:
 usb0      Link encap:Ethernet  HWaddr
 addr:  Bcast: 
            inet6 addr:
 fe80::8818:9fff:fec4:a902/64 Scope:Link
            UP BROADCAST
            RX packets:3
 errors:0 dropped:0 overruns:0 frame:0
            TX packets:56
 errors:0 dropped:0 overruns:0 carrier:0
            RX bytes:626
 (626.0 B)  TX bytes:10727 (10.7 KB)
 Requires no special setup.
 However on a FreeBSD machine I need to do this:
 USBDEV=$(shell dmesg | grep '^ugen.*LCD' | sed -E 
 # target to make the device show up on freebsd.
          usbconfig -d
 $(USBDEV) set_config 1
          sleep 5
          ifconfig ue0 inet  up
 Basically I need to grep dmesg for "ugen" and the string
 "LCD", then I 
 need to run:
   usbconfig -d 3.3 set_config 1  # (3.3 comes from
   ifconfig ue0 inet  up
 Any idea why Linux can do this all automagically but FreeBSD
 manual help?
 I even tried putting some stuff into devd.conf, however devd
 seem to the right thing if the device is plugged in at boot
 time. This 
 is because devd only seems to know when a device is plugged
 in, however 
 it doesn't trigger events when the device has been present
 since boot.
 Any tips on this?  We can get around this with some
 custom rc scripts, 
 but I was just wondering if FreeBSD could make it more plug
 and play.
 mailing list
 To unsubscribe, send any mail to ""
_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to